Process Roles 
Use
A process role defines a set of tasks that a user assigned to the role can execute on a process. The assignments are made at process initiation in the Guided Procedures (GP) runtime. The concept is specific to GP and should not be confused with portal roles.
GP provides pre-defined process roles, but also allows the process designer to create additional roles.
The process designer also defines when the assignment of users to process roles is completed – either at process instantiation, or at process runtime, or the initiator is automatically assigned to the relevant process role. For more information, see Consolidating Roles.
Features
Standard Process Roles
The following roles are defined at process level.
Standard Process Roles
Role |
Description |
Administrator |
The administrator of the process can: ● Maintain assignments of users to process roles ● Maintain process instances using the GP administration tools |
Overseer |
The overseer can: ● See the process instance in the GP runtime ● See all actions in a block |
Owner |
The owner role is similar to a superuser concept for processes. The owner of a process can: ● Access all steps of the process ● Maintain process instances |
Customizable Roles
In addition to the standard process roles, there are also the following roles, which you can customize at design time.
Customizable Roles
Role |
Description |
Execute role |
When you insert an action into a block, the system automatically creates a role for the action processor. At block level, you can consolidate the roles for various action processors into a block processor role. For more information, see Consolidating Roles. |
Display role |
At block level, you can define the visibility of each action in the block to the processors for the other actions. At process level, you can define such view permissions for the processors of the blocks. The authorized roles can only see the relevant action or block. For more information, see Granting View Permissions. |
See also: