Yes, it is possible.
- Click on Approved item in your chain.
- Use the right side to select the Ad Hoc process.
- Open form AP:Administration and look at the Ad Hoc process
- You'll see that it's looking for the approver in the z1D_Approver field
- Determine how to set z1D_Approver on submit of your service request.
I see what you mean. I'll try this first thing tomorrow. Thanks already for the great tip!
Keith Fawcett <firstname.lastname@example.org>schreef:
SRM: Is it possible to have a "Level" approval being followed by an "Ad Hoc" approval?
reply from Keith Fawcett<https://communities.bmc.com/people/kfawcett?et=watches.email.thread> in Service Request Management - View the full discussion<https://communities.bmc.com/message/377900?et=watches.email.thread#377900>
1 of 1 people found this helpful
It works as a charm, thank you very much!
I have created an approval chain containing three consecutive processes:
- Service Request - Level
- Service Request - Ad Hoc
- Service Request - Management Chain
Next to that, within the form SRD:ServiceRequestDefinition_Base, for the SRD's covered by the approval chain, I have:
- Unchecked the 'Request Manager' check box
- Filled in the loginid of the Ad Hoc approver in the z1D_Approver field
The approval behavior is now as desired, meaning:
- First all the approvers defined in the Approval Mappings form linked to the Service Request - Level phase need to approve
- Then the Ad Hoc user defined in the SRD definition needs to approve
- Then the user's manager as defined on the People form needs to approve
Furthermore, in my approval chain, in the "Approved" part of the 1st process (Service Request - Level), next to calling the second process (Service Request - Ad Hoc), I also do a Set Fields of the Status_Reason field to a customized value. This allows my Service Target to stop after the first approval, by the Service Desk.