--- 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: >- Reference: Trigger Integration layout: subsection --- ## Purpose Use this component to configure and execute other integrations in your Workday tenant. An integration that you trigger in this way is said to be a child of the orchestration that calls it. The child integration can be any of these types: - Workday-delivered packaged integrations. - Custom Studio integrations. - Other Workday Integration Systems orchestrations. You can place the component in the top-level workflow, in error handlers, in branches, in loops, and in suborchestrations. ## Template Availability This component is available in this orchestration template only: - Workday Integration System. Note: You can't use this component in join loops. ## Properties Provide a meaningful Reference Name for the step as it will appear in your orchestration. The Auth Tab Use this tab to specify the authentication method for the child integration that the step will trigger. From the Authentication drop-down menu, select either Default Workday API Credential or Access Token from Initiating User. Note: If the child integration system has an ISU configured as part of its definition, that ISU will be its "run as" user when it's triggered. The user configured in the Trigger Integration step, regardless of authentication type, will be the "initiating" user. This initiating user must have the necessary permissions to be able to launch the integration. If the child integration system doesn't have an ISU configured, the user specified in the Trigger Integration step will be both the "run as" user and the "initiating" user for the child integration. This user must have the necessary permissions to both run and launch the integration. The Launch Parameters Tab Use this tab to link to the child Integration System and import its launch parameter definitions. To do so, you must be connected to the relevant tenant. Click Manage Connections at the top of the Launch Parameters tab. Select the tenant from the drop-down menu and connect to it. When the connection has been established, search for the Integration System by name, and link to it. Orchestration Builder imports and displays the launch parameter definitions from the linked child integration system, grouping them according to their service Provider type. Note: Instead of using Orchestrate's automatic grouping, you can optionally create your own groups. ClickCreate Parameter Group, then specify the service Provider ID and Provider Type. Use Expression Builder to provide the values that will be passed to the child integration as its launch parameters, incorporating upstream data from your orchestration as required. Use the Send in Launch checkbox beside each parameter to specify whether or not it's included when the child integration is triggered. Click Refresh Launch Parameters at the top of the Launch Parameters tab to reimport the latest parameter definitions from the child integration system. If parameter definitions have been added to or removed from the child integration, the list updates accordingly. If a parameter that had an expression assigned has been removed, Orchestration Builder prompts you to either exclude the parameter or remove the expression. The Document Tab Use this tab to pass a document to the child integration. Complete these Expression Builder fields to tell Orchestration Builder what it needs to know about the document:
FieldDescription
Document to StoreAn expression that specifies the document to attach.
Document TitleAn expression that specifies the name the document under which the document will be stored.
Description(Optional) An expression that provides a brief description of the document's contents.
Collection to Store Document In(Optional) An expression that specifies the collection where the document will be stored. If you don't specify a collection, Workday creates a new collection using the child integration system WID as its name.
Storage Expires InAn expression that specifies when document storage expires. The default, if no value is set, is 7 days. The maximum retention period is 1 year. Example: to set expiry for 1 month, use the expression zoneddatetime.now().plusMonths(1).
Tags(Optional) An expression that provides descriptive tags to help categorize the document. Tags entered here are only valid if they already exist in the tenant.
Add "Retrieved" Workday Tag(Optional) A boolean expression that evaluates to true or false. If true, makes the child integration treat the document as if it had been sourced from the Integration System retrieval service. Entering a nonboolean expression will lead to an error.

The Settings Tab Use this tab to configure these request and response details: - Overall Timeout: the total time allowed for the operation. - Connect Timeout: the time allowed for a client-server connection to establish. - Response Timeout: the time allowed for establishing a connection. - Response Type: the type of response requested. - Retry Settings: select a predefined retry policy. You can create retry policies on the HTTP Retries tab of your orchestration's Settings. Note that these retry mechanisms support retry on failure to trigger the integration, not on failure of the integration itself. ### Related Information [Concept: Triggering Integrations](/wcp_docs/GUID-a1697f20-c5b9-4c96-94f6-90868152ea21.html)