Defining Authorization Process
|
|
|
|
This page can be used to define authorization process for the selected task.
Select the “Define Authorization Process” link at the bottom of the ‘Define Authorization Process - Choose Task’ page.
The “Define Authorization Process” page appears.
The system displays the following:
|
Date Format
|
The format in which the date fields must be entered in this page. The specified format is DD-MM-YYYY. |
|
Component Name |
The name of the component in which the task is present (Alphanumeric, 128). |
|
Activity Name |
The name of the activity in which the task is present (Alphanumeric, 128). |
|
Task Name |
The name of the task for which authorization process need to be defined (Alphanumeric, 256). |
Enter the details in the following fields:
|
Effective From |
The date from which the path is effective (Date format). |
|
Effective To |
The expiry date of the path (Date format) Mandatory. |
Click the ‘Previous’ pushbutton to view the details of the previous set of "Effective From" and "Effective To" details.
Click the ‘Next’ pushbutton to view the details of the next set of "Effective From" and "Effective To" details.
Enter the details in the following field:
|
Path ID |
The unique ID for every path defined for the selected task (Alphanumeric, 30). If the path is already defined, select the lens icon near the ‘Path Id‘ to launch the ‘Help on Path‘ page and to choose an appropriate path. |
Click the "Get" pushbutton to retrieve the path details.
Modify the details in the following fields, if required:
|
Process Rule ID |
The ID of the process rule (Alphanumeric, 30). Click on the lens icon near ‘Process rule id‘ to launch the ‘Help on Process Rule‘ page. The process rule id can be selected from this page. |
|
Path Description |
The detailed description of the path (Alphanumeric, 40). |
|
Process Rule Description |
A detailed description of the selected process rule (Alphanumeric, 40). |
|
Rule Driven Process Identification |
Check this check box to indicate that the path defined will be selected only after evaluating the given rule. It helps to emphasize the rule evaluation for a path. |
Note: The process rule must be attached to those paths for which ‘Rule-driven process identification’ is selected.
Note: If the authorization process is already defined, the system displays the following details.
Enter the following details in the "Specify Steps" multiline:
|
Sequence No |
The sequence of the state if the authorization has multiple steps (Integer). |
|
State Name |
The name of the state (Alphanumeric, 10). Click on the lens icon near ‘State Name’ to launch the ‘Help on State’ page and to select an appropriate state. Both intermediate and application states can be selected from this page. |
The system displays the following field in the multiline:
|
State Description |
The detailed description of the name of the state. |
Enter the following details in the multiline:
|
Mandatory |
Use the drop-down list box to identify the state as mandatory for the authorization process. Select "Yes" to set the state as mandatory else select "No". |
Note: If a state is identified as Non-mandatory, then skipping this state is at user’s discretion.
Note: If the authorization process is already defined, the system displays the following details.
Enter the following details in the "Specify Initiating Org. Units" multiline:
|
Org. Unit Code |
The document initiating organization unit code to which the path is applicable (Alphanumeric, 16). This must be the initiating organization unit code. Click on the lens icon near the ‘Help on Org. Unit‘ page. The organization unit can be selected from this page. |
The system displays the following field in the "Specify Initiating Org. Units" multiline:
|
Org. Unit Description |
The description of the organization unit. |
Click the ‘Save’ pushbutton to save the details.
Click the ‘Delete’ pushbutton to delete the details.
To proceed
Select the “User Identification” link at the bottom of the page to define user identification basis.
Select the “Enable Notification” link at the bottom of the page to attach messages to each state.
You can define multiple paths for authorization process of a document.