- SAP Managed Tags:
Hello All,
Please find the purpose of each option in Modify Task Settings in MSMP in the tab
1. Runtime Cnfg Chng Ok
If there are stage setting configuration changes after the workflow has been initiated, setting this action allows the workflow to use the new workflow settings.
2. Path Reval New Role
When Request is going to Multiple Paths and the Approver wants to add the Roles at their Stage, the Path needs to be re-evaluated. This functionality 'Path Reval New Role' is useful in evaluating when the Request is going to Multiple Paths.
If the option Only New Roles in Evaluation Path is selected, the request needs to be evaluated by the approver whenever new roles are added.
If the option No Path Revaluation for New Roles is selected, the request will not come back to the approver after approving.
If the option All Roles in Request (Re-Evaluate) is selected, the request needs to be re-evaluated by the approver for all the roles.
3. Reroute
Reroute functionality is to send request to one of the previous stages in the workflow. If the request workflow has only one stage it cannot be rerouted as there is only one stage. The minimum number of stages required to reroute is at least two.
For action “Reroute” to be enabled for approvers, the following three conditions need to be met
- Stage level setting for reroute should be active
- The present stage cannot be first stage (e.g. first approver attempts to reroute after request is submitted)
- Request should not have multiple paths to follow (e.g. at runtime request can't take two different paths)
4. Confirm Rejection
This functionality Provides the approver with an additional screen asking the approver to confirm whether the request has to be Rejected with YES or NO.
5. Approve By Email
This Functionality Enables approval through E-Mail
6. Approve Despite Risk
This setting will allow the approval of a request when there are unmitigated risks.
7. Reaffirm Approve
This functionality will prompt approver to supply user id and password while approving the request.
8. Change Request Det
Change request Details is required to make the field’s editable/non-editable for an approver. If it is set to "NO" then the approver cannot change few fields like User validity start date, User validity end date etc while approving the request. If this parameter is set to "Yes", approver can change the fields’ value. So set this setting as per your company's requirements.
9. Approval Level
In case of having Request line item, you can enable Approval at request level.
In case of having Role line item, you can enable Approval at role level. Approver can approve the role requested
In case of having System and Role line item together in one request and if Approver approves the System line item, application also approves the roles associated with that system automatically.
If the Approval Level is 'System and Role' or 'Request' the whole request gets forwarded and not just the specific role/s. If you want to forward roles in a request to different role approvers, then set the Approval Level to ‘Role’.
10. Comments Mandatory
The stage configuration parameter 'Comments Mandatory' is used to provide comments at the request level and not at line item level.
If it is set to Rejection, then the request will ask for comments if the request is rejected by the approver. It would not ask for comments in case the approver approves the request. Similarly if it is set to Approval, then it would ask the approver for comments if the approver approves the request and would not ask if the request is rejected. If it is set to Both, then it would ask for comments for both Approval and Rejection.
11. EUP ID
The End user Personalization helps the administrators to set the parameters that define the behaviour of the fields and the pushbuttons on the Access Request screen.
EUP helps to:
- Specify the number of visible rows
- Set Fields to visible or hidden
- Set fields as mandatory
- Define Default values for the fields
12. Override Assign Type
This functionality is used when both direct and indirect provisioning is utilized. Enabling this setting allows the approver to decide whether a specific role should be assigned directly or indirectly
13.Add Assignment
'Add Assignment', will allow you to add assignments such as roles during runtime of the request i.e. while approval process. However, this will not allow removal of any assignments which have already been added to the request and for those assignments, you will find 'Remove' button as disabled.
14. Request Rejected
This Functionality Allows Approver to reject the request.
15. Confirm Approval
Provides the approver with an additional screen asking the approver to confirm whether the request has to be approved with YES or NO.
16. Reject By Email
Enables rejection through E-Mail
17. Forward Allowed
This functionality Allows approvers to forward requests to be reviewed by another approver.
18. Display Review Scrn
This functionality will Display a review screen prior to a final approval or rejection of the request which would allow the final approver to see everything that has been approved.
19. Reaffirm Reject
This functionality will prompt approver to supply user id and password while rejecting the request.
20. RA Mandatory
The RA Mandatory will control whether the approvers need to perform risk analysis before approving of a request. It has three options.
YES - Risk Analysis is Mandatory
YAC - Risk Analysis is mandatory if Access id changed or if Risk Analysis Failed (This setting will not allow a approver to approve a request when RA fails)
NO - Risk Analysis is not mandatory
21. Rejection Level
In case of having Request line item, you can enable Rejection at request level.
In case of having Role line item, you can enable Rejection at role level. Approver can reject the role requested
In case of having System and Role line item together in one request and if Approver rejects the System line item, application also rejects the roles associated with that system automatically.
22. EMail Group
This functionality is not supported.
23. Allow Manual Prov
This functionality will be used on last stage of the workflow path. If enabled, it displays an option for provisioning manually.
Any Additions or Subtractions to this document is most welcome.
Regards,
Rakesh Ram M
15 Comments
