Children

For each business rule component you have the option of specifying child business rule components. Whenever an event occurs that triggers a business rule component to run, its child business rule components also have the potential to run. However, a child business rule component will only run if its own trigger event occurs.

Events in a business rule component can be used as triggers for child business rule components. For example, in a conditional business rule component, you can configure individual child business rule components to be triggered only when the condition is true or only when the condition is false.

Including child business rule components is not required. However, some types of business rule components (such as a forLoop) may have no practical effect if they do not have child business rule components.

Each child business rule component can have child business rule components of its own.

Best Practice

Use priority values to control the execution order of business rule components. Additionally, within a business rule it is recommended that you list peer business rule components in execution order so that the business rule will be easier for others to understand.

Important! Content in a business rule is case sensitive. This includes business rule component names, attributes, and values.

Note: There is no element named child.

<children>

<!-- Specify child business rule components. -->

</children>

Tip: For assistance with a business rule that you have created or to have Loftware create business rules for you, contact Loftware's Professional Services Group.