Troubleshooting Heritage Coaches

IBM BPM, V8.0.1, All platforms > Create processes in IBM Process Designer > Create user interfaces for business processes > Building Heritage Coaches
Troubleshooting Heritage Coaches

Learn how to identify and fix common problems with Heritage Coaches.
If you experience problems running services that include Heritage Coaches, check for the issues described in the following table:

Common Heritage Coach problems
Issue Potential cause and resolution
Dynamic values are not displayed in a Heritage Coach as expected. You might be using null values in the variable (that is, the variable has no value versus the value 0). When initializing variables in the service that contains the Heritage Coach, assign default values to them.
Input values are not captured as expected at run time. This can happen when using multiple sections in a Heritage Coach. Each section is its own HTML form; submitting data in a section does not submit data in another section, unless it is a nested section. Always design your Heritage Coaches with this rule in mind.
Unexpected behavior of nested visibility rules at run time. An example of nested visibility rules is described in Displaying a control based on the input value of another control. If possible, design your Heritage Coaches such that you can distribute the rules across more than one Heritage Coach. Another option is to use custom JavaScript to express cascading rules. An example is provided in Use a custom script to control visibility.
A configured onClick event for a button does not take place at run time. Ensure that the onClick event is assigned to the individual button instead of a Button Group control.

Building Heritage Coaches

Related concepts:
Building Heritage Coaches

Issue	Potential cause and resolution
Dynamic values are not displayed in a Heritage Coach as expected.	You might be using null values in the variable (that is, the variable has no value versus the value 0). When initializing variables in the service that contains the Heritage Coach, assign default values to them.
Input values are not captured as expected at run time.	This can happen when using multiple sections in a Heritage Coach. Each section is its own HTML form; submitting data in a section does not submit data in another section, unless it is a nested section. Always design your Heritage Coaches with this rule in mind.
Unexpected behavior of nested visibility rules at run time.	An example of nested visibility rules is described in Displaying a control based on the input value of another control. If possible, design your Heritage Coaches such that you can distribute the rules across more than one Heritage Coach. Another option is to use custom JavaScript to express cascading rules. An example is provided in Use a custom script to control visibility.
A configured onClick event for a button does not take place at run time.	Ensure that the onClick event is assigned to the individual button instead of a Button Group control.