conditional Business Rule Component

A Conditional business rule component allows you to determine whether to perform an action based on the result of a comparison of values or the result of a logical operation.

The following is the syntax for a Conditional business rule component.

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

Note: For each business rule component, most elements and attributes are optional, but you should specify enough to achieve the functionality that you intend. In most cases, you can omit attributes that are not relevant to your task and default values will be used. You must specify a name and a namespace. Except where otherwise indicated, attributes accept string values.

About the syntax documentation

<conditional name="This_component" namespace="Parent_of_component"
configuratorType="Block_type_ID" alias="Data_reference">

<!-- Triggers -->

<!-- Required. Specify which event will cause this business rule component to run. For more information, see Triggers. -->

<triggers>

<trigger eventTrigger="ENQUEUE|PRINTJOBDETAIL|LABEL|Custom_Event" priority="integer" propagation="NONE|BEFORE|AFTER"/>

</triggers>

 

<!-- Execution condition -->

<!-- You can specify a condition that must be true for this business rule component to run. For more information, see Conditions. -->

<executionCondition>

<!-- Logical expression resulting in a condition of true or false. You can perform a logical operation, a comparison, or a data map entry state operation. You can nest operations to create a more complex expression. For more information, see Logical Operations and Comparisons. -->

</executionCondition>

 

<!-- Default data -->

<!-- You can specify default data to be added to the data map. For more information, see Default Data. -->

<defaultData>

<!-- Default data entries are stored as data map entries that include a name (key) and a value. When defining an entry, name and value are required. -->

<entry name="Name_of_data_map_entry"
dataType="STRING|INTEGER|BOOLEAN|NUMBER|BINARY|DATE"
mergePolicy="MERGE_ALL|MERGE_NONE|MERGE_FROM_CHILD|MERGE_TO_PARENT"
action="OVERRIDE|NOT_EXISTS|DELETE|APPEND|PREPEND">

<value>Value_of_data_map_entry</value>

</entry>

</defaultData>

 

<!-- Common custom events -->

<!-- You can define pre-processing events, post-processing events, and error processing events that you can use as triggers. By using these events as triggers for other business rule components, you can cause a state to occur before or after this business rule component is run, or you can respond to an error. For more information, see Events. -->

<preProcessingEvents>

<preProcessEvent eventName="Custom_Event" includeSiblings="true|false" />

</preProcessingEvents>

 

<postProcessingEvents>

<postProcessEvent eventName="Custom_Event" includeSiblings="true|false" />

</postProcessingEvents>

 

<errorProcessingEvents>

<errorProcessEvent eventName="Custom_Event" includeSiblings="true|false" />

</errorProcessingEvents>

 

<!-- Child business rule components -->

<!-- You can create child business rule components to be run whenever the trigger event for this business rule component occurs. -->

<children>

<!-- The child business rule components have the potential to run once per triggering of the business rule component. However, a child business rule component will not run unless its own trigger event occurs. -->

<!-- To allow a child to run only if the condition is true, set the trigger in the child business rule component to an event name specified in trueConditionEvents. -->

<!-- To allow a child to run only if the condition is false, set the trigger in the child business rule component to an event name specified in falseConditionEvents. -->

</children>

 

<!-- Conditional functionality -->

<condition>

<!-- Logical expression resulting in a condition of true or false. You can perform a logical operation, a comparison, or a data map entry state operation. You can nest operations to create a more complex expression. For more information, see Logical Operations and Comparisons. -->

</condition>

 

<trueConditionEvents>

<!-- Definition of an event that occurs if the condition is true. -->

<trueEvent eventName="Event_if_true" includeSiblings="false|true"/>

</trueConditionEvents>

 

<falseConditionEvents>

<!-- Definition of an event that occurs if the condition is false. -->

<falseEvent eventName="Event_if_false" includeSiblings="false|true"/>

</falseConditionEvents>

</conditional>

Syntax Tips

Additional information is available about the following items.

alias

configuratorType

name

namespace

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.