ProcessRequirements
This business rule is attached to a transaction in order trigger the processing of requirements. This rule supplements the ability of requirements to schedule execution. Processing a transaction with this rule attached will trigger the processing of requirements that are not necessarily scheduled to be executed at the given moment.
Element/Tag | Definition | Attribute | Element/Attribute Value and Description |
---|---|---|---|
<ProcessRequirements> |
Required element: The opening and closing tags for the business rule. |
||
<Process> |
Required element: This element defines the condition that dictates whether the rule will execute. This element should not be given a value, as the execution condition is set in the value of the IF attribute. |
||
IF |
Required attribute: This attribute should contain an expression that resolves to a Boolean value, which will dictate whether the rule executes. This attribute can also be left empty, in which case the rule will always execute. |
||
<RequirementGUID> |
Optional element: If this element is present, only the requirement whose GUID is contained in the specified field will be processed. |
The name of the field that contains the requirement GUID. | |
<RequirementName> |
Optional element: If this element is present, only requirements with the specified name will be processed. |
The requirement name as listed in AsRequirementDefinition. The rule will process the requirements with the specified name. | |
<ClientGUID> |
Optional element: If this element is present, only requirements with the specified name that exist for the specified client will be processed. |
A client GUID. | |
<NewStatus> |
Optional element: If this element is present, the requirement will take on the specified status upon processing. |
A status code from AsCodeRequirementStatus. |
XML Example
<ProcessRequirements>
<Process IF="expr"/>
<RequirementGUID></RequirementGUID>
<ClientGUID></ClientGUID>
<RequirementName></RequirementName>
</ProcessRequirements>