You can configure Approval Mappings for each stage of Change Approval.
There are 4 stages in Change Management where in you can configure Approvals from Approval Mappings Form.
You can configure the approval process in Approval Process Configuration form (APR:SYS-Approval Definition) and approvers can be configured in Approval Mapping form (APR:Approver Lookup), for each phase which you defined in the Approval process .
In Change management we can find a Field called manager group:this is nothing but to which group it is related and another Field called Change Approver: this is nothing but the approvers of that manager group these people can approve the change application.
Make sure that approvers can have the permission and rules, then only the approver can approve the our application.( after creating a new change, we we should login with that particular approver login name and the approver can approve that change appalication to get into next stage)
if you want u can see approval Mapping form.
I hope it will help full for you.
You should NOT have to got into the ARP forms to configure approvals for Change Management. That should be a last resort if you need to configure things differently than the default. Change Management has two components for the approvals:
1) approval process records (located on the App Admin console, Custom tab under Foundation > Advanced Options > Approval Process configuration. OOTB, there are five approval process records for the -Global- company: Review, Business Approval - No Impact, Business Approval, Implementation Approval, and Close Down Approval. These OOTB process records are set to work with Impacted Area, but can be modified to support both Impacted Area and CI (I believe as of 7.6.03). These records indicate the status value in the change that starts the approval process as well as the status value to set if the approval is approved, rejected, or no approvers are found mapped for the phase.
2) Approval Mappings (located on the App Admin console, Custom tab under Change Management > Approval > Approval Mappings. These records indicate the group or individual to approve for the particular phase (process record above).
There is an entire chapter dedicated to "Configuring Approvals" in the ITSM Administrator Guide.
ofcourse but according to original question, we should use Approval Central form to approve the next stage in change management(The change approver can approve to the next stage). or else in the change management console itself we can approve to the next stage.
Approval Central Form: in this we can see weather the approver has approved to the next stage or not.
Approval Mapping Form:we can observe the Approver Indicator is in which status, assignment avaialbility and Phase name like this we can find many things.
Yes, Approval Process Configuration and Approval Mappings are the two forms which will be used to configure the Approval Process and the corresponding Approvers for that Process.
However one thing to note down in 7.6.04 ITSM is nothing but the one who is actually having Infrastructure Change Approver Functional Role only and not having any Change Coordinator or Change Manager Functional Role. Then those Approvers can only Approve the Request loggin in to the Approval Central only.
Not directly from the Change Request(As the Change Request will be locked down for them if they dont belong to the Assigned Coordinator or Assigned Manager Groups.)
Please tell me know can I configure approval process that Requester of a specific change will approve change request after implementation?
We need to assign approve for a user which submit a request, so he is the only one that can say change is implemented ok.
As far as I can see I do not see this OTB possibility right?
this is just a hint
hmmm if you want to map the Requester as the approver for the close down then i don know whether Inherent Group supports this or not...
basically if you want to determine the Approver dynamically we go for this Inherent Group in the Approval Mapping Form(Approval For) Field. But as far as i know it supports the Functional Roles of Change, as Requester is not a functional role i am no sure about this....