The right hand side of the panel displays detail views of the conditions or decisions corresponding to the selection marked in the tree. If a condition node is chosen, the user is able to select one of the available risk indicators. If a decision node is chosen, the properties of this decision may be changed.

 

Condition Details

Condition Details are displayed if a condition node is chosen in the tree. The user can choose a risk indicator for evaluation and can specify the match criteria by setting operator and range of the match operation.

 

 

The Risk Indicator field is a drop-down box containing all risk indicators that have been specified for this customer by configuration. Please note that the condition detail view does not offer access to risk indicators that have been disabled in the settings dialog.

 

The Operation field is a drop-down box offering all available operations based on the selected risk indicator type. The type of the risk indicator can be found in the risk indicator configuration dialog. Operations that are available for a specific type are listed below. The display of operands changes depending on the selected operation. Some operators may need two operands while others need only one operand. The ‘not available’ operation does not need any operand at all.

Furthermore the client will check the input of an operand field depending on the selected operation. This may be string type, or value type, and includes value range verification as well. Value ranges for a risk indicator are defined by configuration.

The following table lists all available operations by risk indicator type.

 

 

The following panels display some examples of operations and how they are displayed in the conditions panel:

 

Risk Indicator of type Long or Double:

 

Risk Indicator of type Boolean:

 

Risk Indicator of type String

 

There is also the possibility to specify a configuration variable for a condition in an operand. For this reason, the check box labeled ‘use configuration variable’ must be checked. If it is checked, the client displays a drop-down box for each available operand where the user can select an existing variable.

 

Usage of configuration variables:

 

A list of already defined variables can be displayed via the settings dialog for variables.

It is also possible to specify a further risk indicator in an operand for a condition in an operand. To do this, the check box 'use risk indicator' must be checked. If it is checked, the client displays a drop-down box for each available operand where the user can select an existing risk indicator.

 

Usage of risk indicators:

 

Decision Details

Each risk scenario is terminated by a decision. A decision specifies the queue where the item is routed to if the scenario matches.

 

 

A decision is specified by an ID. The ID is of type String and is mandatory for a risk scenario. The client has to ensure that the specified ID for each decision is unique within the rules tree.

A Comment can optionally be specified.

The Score is a mandatory field where the user can specify the importance of this risk scenario by using a value between 0 and 100.000. Together with the specified weight algorithm, it finally results in the risk value of this scenario. This is also the new priority of the item in the next queue.

The Weight algorithm defines the way in which the Score of this risk scenario is weighted. It can be one of the following:

•None: The score value is the final risk value for this risk scenario

•Amount: The score is multiplied with the amount of the item. The result is the final risk value for this risk scenario. This is the default for all decisions.

•VIP: The score is additionally multiplied with a VIP value to determine the final risk value for this risk scenario. This operation is only performed if the reference data for this item specifies that the item is for a VIP person (VIP field in SignBase must be set)

The calculated risk factor is used for target evaluation. It is compared with a global threshold. The global threshold can be used to control the daily load for different queues, especially visual queues.

 

Targets define the queue(s) where the item is routed to. A target is defined by a queue name, an optional result value that defines the value of the item in the new queue and a type. All these fields are mandatory. Optionally, a comment may be specified.

A new decision always receives a default target with the OUTPUT as destination, and a type 'Always'. The user can change target values at a later time. A context menu, available via right mouse click on the target table, enables the user to create new targets, or to delete defined targets. The last target cannot be removed because one target always must be present.

 

Note The presence of more than one target indicates a parallel workflow. If the risk scenario matches, the item is routed to more than one queue in parallel.

 

 

The Queue of a target can be selected via a drop-down box after clicking into the queue column of the target table. The user can select one of the queues defined in the queue setting dialog.

The Result is the new result value the item will receive in the next queue. If the next queue is the OUTPUT queue, this value will be the final result. If no result value is specified, the value remains the same as in the prior queue.

The Priority is calculated by the system in the event there is no value specified. If you enter a value here, the system takes this priority without calculating it.

The Type triggers whether or not a target becomes active or not. The following types are available by drop-down box selection:

•Always: The item will always be routed to this target, independently of the global threshold

•Above Threshold: The item will be routed to this queue if the calculated risk factor is above or equal to the global threshold.

•Below Threshold: The item will be routed to this queue if the calculated risk factor is below the global threshold.

•Below Continue: The item will be routed to this queue if the calculated risk factor is above or equal to the global threshold. If it is below the global threshold, evaluation continues with the next available risk scenario within the evaluation tree.

Important If at least one target is of type ‘Below Continue’, all other targets must be of type ‘Always’ or ‘Above Threshold’!

•Wait: The Item will not be routed to a queue.

 

Additionally, you can enter a Comment for this target.

Decisions may also contain a list of interim results.

If the CRS Workflow reaches are decision, and there are interim results defined, they will be added to the results to be written and recorded in the database.

An interim result consists of an interim variable, a value, and a comment.
The interim variables can be defined in the settings dialog.

The user can create, edit, or delete interim results by using the context menu via right mouse click.

 

 

An interim variable must be chosen from the combo box of available variables. Each interim variable can only be used once per decision.

The value depends of the type of interim variable, and can be either a Boolean, a String, a Long, or a Double.

It is also possible to enter a Comment for the interim result.

 

Once an interim result is created, it is not possible anymore to change its interim variable within the edit dialog.

 

Target Details

In the target details panel, you can edit the properties of the default target node.

The only difference to the Target Dialog in Decision Details above is that there is no priority field here.

 

 

 

---