Working with If Multiple Approvers field
This topic explains working with the If Multiple Approvers field in Remedy Approval Server.
In approval server, some of the forms that are related to the approval signature generation process contain a field called If Multiple Approvers. Approval administrators can use this field to manage signature generation in the cases where multiple approvers are configured for an approval phase in an application request. They can use this field at the process-level, role-level, or rule-level to specify the behavior of an approval process when there are multiple approvers configured.
For more information, see Creating-signatures-for-multiple-approvers.
You can use the If Multiple Approvers field at process definition level, role definition level, and rule definition level.
At process definition level
On the AP:Process Definition form, you can use the If Multiple Approvers field to specify the number of signature lines to be generated when a request enters into an approval phase.
- All Must Sign – If you select this option, for each qualifying approval-mapping record (for each record returned by the Get Next Approver rule qualification), a separate signature line is generated. That is, the number of signature lines is equal to the number of qualifying approval mappings or the number of records returned to the Get Next Approver rule.
- One Must Sign – If you select this option, for all approval mappings (all records returned to the Get Next Approver rule), only one signature line is generated. Each approver in that one signature line is delimited by a semicolon (;).
At role definition level
On the AP:Role form, you can use the If Multiple Approvers field to specify the number of signature lines to be generated for the members of the AP:Role record.
- All Must Sign – If you select this option, for each member in AP:Role record, a separate signature line is generated. That is, the number of signature lines is equal to the number of delimited members in the Member List field of the AP:Role record.
- One Must Sign – If you select this option, only one signature is generated for all members of the AP:Role record. That is, only one signature line for all delimited members in the Member List field.
At rule definition level
The If Multiple Approvers field in the Get Next Approver rule does not have any impact on the signature generation process because this field is not considered at the time of processing.
Examples
The following table explains some examples:
Sr. No. | Scenario | Result |
|---|---|---|
1. | You have the following mappings: apr1 (individual) and sup-grp1 (support group with apr2 and apr3 as approver members). You need either the individual or one member from sup-grp1 to sign. | The process level is set to One Must Sign (role level setting is not relevant here). Only one signature line - apr1; apr2; apr3 is generated. |
2. | You have the following mappings: two support-groups. You need one member from each group to approve. | The process level is set to All Must Sign and the role level to One Must Sign. One signature line for each sup-grp is generated that fulfills the requirement. |
3. | You have a mapping for a group where you need all members of the group to sign. | The process level is set to All Must Sign and the role level to All Must Sign. For each member in the AP:Role record, one signature line is generated. |
4. | You have the following mappings for groups: grp1 (apr1 and apr2 as members) and grp2 (apr3 and apr4 as members). You need all members of grp1 and only one member of grp2 to approve. | The process level is set to All Must Sign. The role level for grp1 is set to All Must Sign and role level for grp2 to One Must Sign. One signature for each member in grp1 is generated and one signature for all members in grp2 is generated. |
Related topics