User Identification

Define Document Routing - A summary of the activity

What you can do in this page

Glossary

This page can be used to define the user identification basis across area document routing. Additionally, it can be used to define the resource rule, if the user identification basis is rule-based, on which the users will be identified by the workflow.

The ‘User Identification’ page appears.

The system displays the following fields:

Date Format

The format in which the date fields must be entered in this page.  The specified format is DD-MM-YYYY only.

From Component Name

The name of the component in which the ‘From Task’ is present.

From Activity Name

The name of the activity in which the ‘From Task’ is present.

From Task

The name of the task from which the document must be routed.

From Org. Unit Description

The description of the organization unit from which the document must be routed.

To Component Name

The name of the component in which the ‘To Task ‘ is present.

To Activity Name

The name of the activity in which the ‘To Task’ is present.

To Task Name

The name of the task to which the document must be routed.

To Org.  Unit Description

The description of the organization unit to which the document must be routed.

 Effective From

The date on or after which the document routing will be effective.

 Effective To

The date on or before which the document routing will be effective.

 Path ID

The ID of the path.

 Path Description

The description of the path.

User Identification Basis

Use the drop-down list box to specify the basis for selecting the user. The basis can be ‘Direct Entry’, ’Rule-based’, ’Direct Span of Control’ or ‘Stored Procedure-based’. The user is identified based on the option selected here.

SP Based User

The name of the stored procedure, to be given in case the ‘User Identification Basis’ is ‘Stored Procedure- based’ (Alphanumeric, 25).

Help facility available.

Resource Rule ID

The ID of the resource rule (Alphanumeric, 30). If the resource rule is already defined, click on the lens icon near the ‘Resource Rule’ to launch the ‘Help on Resource Rule’ page. The resource rule ID can be selected from this page.

Help facility available.

Resource Rule Description

The description of the resource rule (Alphanumeric, 40).

Stored Procedure Name

The name of the stored procedure (Alphanumeric, 25). Click on the lens icon near the ‘Stored Procedure Name’. This will launch ‘Help on Stored Procedure’ page. The procedure name can be selected from this page.

Help facility available.

Note: When the ‘User Identification Basis’ is rule-based, either “Stored Procedure Name” or “Rule” must be entered in the multiline.

Parameter Description

Use the drop-down list box to select the description of the parameter.

Relational Operator

Use the drop-down list box to select the relational operator to define the rule. Based on the parameter, relational operator and parameter value, the rule will be evaluated. The relational operator can be one of the following:  ‘=’, ’<>’, ’>’, ’<’, ’>=’, ’<=’, ’IN’ and ’NOT IN’.

Parameter Value

The static value of the parameter to be considered for rule evaluation (Alphanumeric, 256).

Value List

The list of values for the selected parameter. This can be used in conjunction with the relational operator ‘IN’ and ‘NOT IN’. After selecting the parameter and relational operator ‘IN’ or ‘NOT IN’, select the hyperlink ‘Value list‘ and the list of values can be specified in ‘Value List‘ page.

Parameter Description

Use the drop-down list box to select the description of the parameter.

Logical Operator

Use the drop-down list box to select the logical operator. It can either be  ‘AND’ or ‘OR’.

Brace

Use the drop-down list box to select the brace, which can either be '(‘ or ‘)’.

Sequence No

The sequence number of the condition defined for the rule (Integer). The conditions will be evaluated sequentially.

Note: "Parameter Description" can be used to create a rule by comparing two parameters instead of comparing it with static values. This can be done by selecting parameters from two columns in the same row and a required relational operator.

Note: For a single record in the multiline, either logical operator or brace or a combination of parameter, relational operator and value can be selected.

The system displays the condition defined.

Note: For example, if the user has chosen “Parameter Description” as ‘Login Language’, “Relational Operator” as ‘=’ and “Parameter Value” as ‘1’ then the condition would be: Login Language = 1.

To proceed

Top

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

What you can do in this page

In this page you can define rules based on which the users will be identified and also you can map those rules to the org. units.

Top