Process Steps
The processing of an authorization involves sequential execution of Process Steps. A process step groups various related and interdependent process rules - callout rules, event rules, validation rules and pend rules - to be executed in an order. A process step forms a 'unit' for processing.
A process step has the following fields:
| Field | Description |
|---|---|
Sequence |
The sequence of the process step |
Display Name |
The display name of the process step |
Access Restriction |
The access restriction for resolution of pend reasons and denial of authorization |
The sequence of the process step determines the order in which the steps are executed. The steps are shown in the UI in the order in which they will get executed. This order can be changed by using up/down arrows (as shown in the mock up). It is not possible to have multiple process steps with the same sequence.
Execution of a process step may result in an authorization to be 'Pended' that is, the processing of the authorization gets suspended for manual intervention. It is possible to attach an access restriction that defines who can take actions like resolve the pend reasons or deny the authorization when pended at that step. This access restriction also applies to resolution of pends and denial of the authorization when the authorization is brought to the 'Change' status from the 'Pended' status.
Rule Step
Rule steps identify which process rules are executed within a process step and the order of execution of these rules within the process step. A step can have zero, one or more rule steps.
The configuration and processing order of call out rules, validation rules and event rules is slightly different from those of pend rules. Call out rules, validation rules and event rules can be sequenced as part of configuration. It is not possible to have multiple rule steps for the same process step with the same sequence.
The pend rules are always executed after that the call out rules, validation rules and event rules have been successfully executed. Execution of pend rules is irrespective of an order, so no sequence is registered.