User allocation rules
An allocation rule is associated with a Workflow rule. It is used to define the destination users by means of a value grid named [L]USER, with indices from 1 to a maximum value defined by the AWR activity code.
These destination users are specified in the form of users codes, entered in a screen intended for the person responsible for the defintion of the signature circuits, via the rule values entry function. Each list of destination users is drawn up using criteria that depend on the context. The user responsible for defining the signature circuit will then be in a position to enter the criteria value combinations and to assign them the corresponding destinations users.
This parameterization function is used to create and update the allocation rules, by defining the maximum number of signers returned by a rule, as well as the criteria whose combination defines the signers.
When executing the allocation rule:
- The criteria are calculated by simple evaluation or by aggregation on a group of lines by an operator such as sum, average, minimum, maximume etc. Each of the criteria thus calculated is compared (using an operator that can be freely defined) to the values entered in the rule.
- The result of the criteria evaluation is stored in a variable grid named VALEXP, the index ranging from 1 to the number of columns of criteria. Thus, they can be used in the rest of the Workflow rule. It should be noted that some criteria, whose values are interesting for the rest of the Workflow process, can be unable te determine the destination users (they will be given the Indifferent operator).
- Depending on the obtained combination, the [L]USER grid is transmitted and can be used by the Workflow rule.
Prerequisite
Refer to documentation Implementation
Screen management
Only one tab is necessary to manage the allocation rules.
Entry screen
Presentation
It contains on the one hand the maximum number of destination users that can be entered, and, on the other hand, the criteria list and the associated rules that will enable the concerned destination users to be defined. It should be noted that the execution right related to the access code assigned to the rule controls the right to enter values for this rule.
Close
Fields
The following fields are present on this tab :
Block number 1
| This code identifies the created records in a unique manner. |
| An allocation rule can be defined for specific companies (and in this case, a record will be ceated to mention the company code for each concerned company). It can also be defined for all the other companies (then, this code is empty). |
| [object Object] |
Characteristics
| This access code makes it possible to prohibit access to the current record for some users. As a matter of fact, if the field is completed, only the users having this access code with read rights (respectively write rights) can view (respectively modify) the concerned record. |
| This compulsory field is used to define the data model whose tables are accessible when evaluating the allocation rule. This model must necessarily be the same as the one asociated with the Workflow rule using the allocation rule. |
| This field can only be entered if the data model contains line tables associated with a header. If one of the line tables is entered, this is the table that will be run through to determine the Workflow recipients. A Workflow using the corresponding allocation rule will necessarily be of Line type. |
|
|
| This field defines the maximum number of users returned by the rule in the USER grid. The screen generated by the validation of the rule will contain, in addition to the criteria columns, as many User columns as there are returned values. This number can range from 1 to a maximum value defined by the AWR activity code. |
| The table entered here is the table being run through to evaluate the line criterion. If this table is linked to the line table of the rule (or to the main table of the model, in the absence of the line table) by means of a (1,N) type link, a synthesis operator will be entered to specify how to aggregate the N values contained in the lines. |
|
|
| This field is entered when the field used as criterion is located in a table linked to the model main table a with a (1,N) link. In this case, the value obtained for the criterion corresponds to the aggregation of a group of lines, and the operator entered here is used to specify the calculation method. The Sum and Average aggregation operators can only be used if the criterion is a numerical one. The Minimum and Maximum operators can be used in all cases. |
| This expression is evaluated when using the allocation rules, and the resulting value (which may be aggregated on several lines depending on the following operator) is compared to the list of values entered in the rule, in order to determine which lines should be used (and hence which users must be returned by the rule). |
| The operator entered here is used to compare the criterion value with the fields entered in the rule values. Beside the standard equality and inequality operators, the As operator is used, to allow character values to be entered with jokers, and the Indifferent operator is also used, to signify that the value is not used as a user allocation criterion but is transmitted to the calling Workflow rule to be used elsewhere. |
| This expression is used to give a title to the entry column for the criterion corresponding to the operating rule. It is then evaluated when entering the rule values. If this field is empty, and the criterion is a field extracted from one of the database tables, the title of the dictionary is the one to be automatically used (in the user language connection). |
| This field defines the data type associated with the criterion entry. When a field extracted from one of the tables in the database is chosen as a criterion, its type is proposed by default. |
| When the value to be entered in the criteria screen is of character string type, it is possible to specify the maximum field length. |
| When the value to be entered in the criteria screen is of Local menu type, it is possible to specify the number of the local menu to be used. |
| When the field associated with the criterion is controlled by a table with a key subdivided into several parts (for instance, the miscellaneous tables, the translatable texts), the additional key component is entered here to establish a link with the table. |
| When the value to be entered in the criteria screen in controlled by another table, it is possible to display a title associated with the entered value: The possible choices are No(no display), Long(display of the long title), Short(display of the short title). |
| This expression, if it exists, is evaluated when entering the allocation rules to give a default value to the field. |
Close
Specific Buttons
The following fields are included on the window opened through this button : Block number 1
Block number 2
Close This button is used to recopy an allocation rule to another folder. |
The following fields are included on the window opened through this button : Block number 1
Grid Default user
Grid Values
Close This button is used to access the entry function of the rule values. The current rule is proposed by default. |
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
XXX: This table cannot be attached under table YYY.
The table entered at the level of a rule line is not linked to the basic table of the rule by a (1,1) or (1,N) link. The attachment is thus impossible.
Table not referenced
The table entered as line table is not present in the data model to which the rule is connected.
Value too high (maximum NN)
A maximum of NN destination users can be defined in an allocation rule (NNdepends on the AWR activity code).