---
category: [Administration & Integrations, Platform and Product Extensions, Platform and Product Extensions/Integration, Administration & Integrations/Custom Integrations & Apps, Platform and Product Extensions/Workday Extend]
keyword: [Extend, Orchestration Builder, Orchestrate, Orchestration]
nav: wcp_docs
parent_url: /wcp_docs/
title: Launch Orchestrations on Business Process Status Changes
layout: subsection
---

### Prerequisites

-   On the Workday Developer Site, create an Extend app.
-   In your Workday tenant, create a business process.


### Context

You can configure a business process to automatically launch an orchestration when a user takes one of these actions:

-   Cancel
-   Rescind
-   Correct
-   Deny


This can help ensure data consistency between Workday and external systems. Example: A <i>Hire</i> business process performs steps in Workday, then launches an orchestration to integrate with an external system that handles access provisioning. If the hire is rescinded, the business process launches a different orchestration that integrates with the external system to revoke the provisioned access.

These orchestrations must be based on the Workday Business Process template.

### Steps

1.  On the Workday Developer Site, add an orchestration based on the Workday Business Process template to your Extend app.

    <b>Note:</b> If your orchestration makes API calls, it must use ISU authentication.

2.  On the orchestration's <b>Business Process Trigger</b> step, configure input parameters to define the values the orchestration can receive from the business process.
3.  Add the steps that you want the orchestration to perform when the business process that calls it is canceled, rescinded, corrected, or denied.
4.  Deploy the application containing the orchestration to your tenant.
5.  In Workday, access the <b>Edit Tenant Setup - Business Processes</b> task. In the <b>User to Perform Orchestration Launches</b> field, specify an individual with the appropriate permissions to access fields and perform actions required by the orchestration.
6.  In Workday, from the related actions menu of the business process, select <b>Business Process</b> &gt; <b>Configure Orchestrations</b>.
7.  In the <b>Configure Orchestrations</b> task, click <b>Add</b> to begin pairing the business process status change with the orchestration.
8.  In the <b>Action</b> field, select the business process status change that launches the orchestration, <i>Cancel</i>, <i>Rescind</i>, <i>Correct</i>, or <i>Deny</i>.
9.  In the <b>Orchestration</b> field, select <i>Create Orchestration Launch Configuration</i>.

    <b>Note:</b> Workday doesn't create orchestration launch configurations automatically. Your orchestration might have successfully deployed to the tenant, but you can't select it here until you create a launch configuration.

10. In the <b>Create Orchestration Launch Configuration</b> task, provide a unique <b>Name</b> for the configuration and select the <b>Orchestration</b> that you deployed.
11. In the <b>Configurable Parameters</b> section, Workday displays the input parameters you configured on the orchestration's <b>Business Process Trigger</b> step. Configure the values that you would like the business process to pass to the orchestration.
12. Back in the <b>Configure Orchestrations</b> task, you can now select the orchestration launch configuration you created.

    You can additional pairings of business process status change and orchestration launch to cover other actions.

13. (Optional) Click the new <b>Create Condition Rule</b> button to define a new rule directly within the grid.

    <b>Note:</b> Workday evaluates these condition rules before it initiates an orchestration.

14. 15. (Optional) To view the status of an orchestration associated business process, use the <b>Find Events</b> task. Workday displays the orchestration's status on the <b>Orchestrations</b> tab.

    <b>Note:</b> A business process-triggered orchestration is typically launched by the Workday scheduler within 15 minutes. There might be a longer delay in Mass Cancel or Mass Rescind scenarios.

    The time taken for the orchestration status to change from <i>In Progress</i> to <i>Completed</i> is solely dependent on the orchestration's processing.

16. (Optional) When the orchestration's status changes from <i>Queued for Launch</i> to <i>In Progress</i>, a <b>Relaunch</b> option becomes available on the <b>Event Canceled</b>, <b>Event Rescinded</b>, <b>Event Corrected</b>, or <b>Event Denied</b> page. Click it to access the <b>Relaunch Orchestration</b> task, where you can adjust launch parameters, if necessary, before relaunch. When you relaunch an orchestration, Workday executes the workflow without re-evaluating the condition rules.

    <b>Note:</b>

    The action page displays <i>Completed</i> status for the orchestration only if the initiating user has View permission for the event.