hmmm what you are asking is if Ashwanth is the Requester here for the Change Request, then you are expecting that CR should go to Ashwanth user for the Approval during Business and Implementation Phase right?
hmmm not sure how inherent based Approval Mappings would set for this Role Mapping of Requested By/For....
give it a try with Inherent Type in the Approval Mappings form based upon the Role Requested For.... lucky if it is there just a guess for me
We have this scenario:
"Sch for Approval" status needs to set "Requested for" user name in Approval Central to approve change request.
In status "Completed" we need to set "Requested for" user name in Approval central to approve implemented change request.
Can we do this configuration using Approval Administration Central?
I have the same question,
I want to have an approval rule for the Change Manager identified (Group/Name) on the change during the business approval.
I have played with inherent Role, but the problem is that I always have a list of approvers, because many coordinators, managers, ans approvers belong to the group.
i think within that group also only the person who has 'Infrastructure Change Approver' functional role would be considered as the approver(this you can designate based on the Functional Role Mapping) when defining 'Group' mapping in the Approval Mappings form...so its not all change manager, coordinators its the Change Managers who has functional role of Change Approver...
1 of 1 people found this helpful
Using inherent group/role will not help here, because inherent group/role fetches approvers dynamicaaly based on approvers coord/mgr/... group and role and here the user wants the "requester for" user to be the approver. I would assume here, that the need is to make "requested for" user the approver irrespective of what role/perm the "requested for" user has. Bases on this assumption, below are two ways to achieve this:
1. First of all , identify the field on the change form that stores the "requested for" users login id. If this is not there, than first you have to create this field and populate this on the CHG form so that the RequestedFor user's userid is stored on the CHG form. say you name this field as "RequestedForUserID". This may be a customization.
2. Create a new ap:process (same as "change adhoc" process). Set the 'First approver field" as $RequestedForUserID$. Say you name this new process as "Change requested for"
3. Goto the approval process config form and modify the phase record to use the "Change requested for" process. No need to create any mapping record for this phase.
Once these 3 steps are done, the requested for user will be automatically picked as the approver.
i tried with the same,it worked out..Thanks for sharing this.
Good to know that it worked. In fact I forgot to mention before that for the new ap:process I suggested , the ap:rules also need to be written (similar to the rules for change adhoc process).
Note: To add "requested by" user as approver, in step-1 no need to create and populate the field. It is already there as fieldid (1000000337)