Trigger another service request when a specific task is completed

Question

Can you setup a condition that when a specific task is completed another service request is triggered? 
 Use Case Branch reports a new hire. They start the a new hire service request. During the hiring process, the potential employee changes their mind. We would like to have a tasks for "Did not Hire". If the branch selects, did not hire, it would trigger the creation of a different service request.

MitchKiah · Accepted Answer

I think the following should achieve what you're trying to do: 
 
 Example Process 
 
 You'll want to put the entire process in a Group and set the group to "concurrent". Then create two non-concurrent groups, one for your Cancel task logic and the rest for your normal workflow process. This way, the Cancel task flow won't impede the normal workflow, but can still cancel out the process. 
 The only caveat with this setup is that there's no way to clean up open Tasks/Approvals from either group. So, if you finish the whole process normally, the Cancel task will still be open. Same for any approvals/tasks in the normal process if you click the cancel task. 
 
 Process Integration 
 This should open the related service request. You'll need to update the JSON to match the fields in your service request. You only need to provide the Required fields in the form. You'll also need to update the URL so the ID after "catalog_items" matches your service request ID. You can find your service request ID by opening the service request, and copying this number from the URL:

This should be what the top portion of your Process integration should look like

And this is an example of the payload at the bottom of the Process Integration. Anything you see in double brackets is a variable from the current incident. You can hard code any of these values if you need to. Variable example: "{{New Hire Name}}" 
 {
 "incident":{
 "requester_name":"{{requester_email}}",
 "request_variables_attributes":[
 {
 "name":"What type of change is this",
 "value":"New Hire"
 },
 {
 "name":"Requester Name",
 "value":"{{New Hire Name}}"
 },
 {
 "name":"Current Phone Display Name",
 "value":"{{Current Phone Display Name}}"
 },
 {
 "name":"Desired Phone Display Name",
 "value":"{{Desired Phone Display Name}}"
 },
 {
 "name":"Branch Name/Number or Corp Cost Center",
 "value":"{{Four Digit Cost Center}}"
 },
 {
 "name":"Phone Options",
 "value":"{{Phone Options}}"
 },
 {
 "name":"Mac/Serial Number (Listed on the bottom of existing phone)",
 "value":"{{Existing Phone MAC Address or Serial Number, if possible}}"
 },
 {
 "name":"Additional Notes or Comments",
 "value":"{{Notes/Comments}}"
 },
 {
 "name":"Best Callback Number (Cell)",
 "value":"{{Delivery contact's name, phone, and email}}"
 },
 {
 "name":"Preferred Area Code",
 "value":"{{Preferred Area Code}}"
 }
 ],
 "incident_ids":["{{context_id}}"],
 "due_at":"{{New Hire Start Date}}"
 }
} 
 
 As a note, the above JSON payload is from before the 4/3 Custom Fields update. I haven't bothered updating the format since it is still the documented format for creating Service Requests from the API.

Trigger another service request when a specific task is completed

Top Replies