Concept: Integration Development Lifecycle

You develop and monitor Studio integrations in these distinct phases, using either Workday Studio or the Workday application as appropriate:

Phase	Description
Integration Design	In Studio, develop the assemblies that form your integration. Optionally, create assembly modules, which enable you to reuse and share integration patterns and configurations. Each assembly has at least 1 workday-in transport, which denotes where execution begins. Each workday-in transport can optionally define: Launch parameters, which enable a client to pass information to the integration as input. Example: A payroll integration might specify that it requires 2 launch parameters: payPeriod and payGroup . This enables the integration's users to specify the month and employee group to use when calculating payroll. Workday services that the assembly uses at runtime. Workday provides generic integration services for attribute mapping, sequence generation, transaction logging, document retrieval and delivery. It also provides a listener service, a report service, and a custom object service.
Integration Deployment	In Studio, connect to the Workday Cloud Repository to deploy your integration. For each workday-in transport defined in an integration, Workday registers an abstraction called an integration system. An integration system includes any required launch parameters and services.
Integration Configuration	In Workday, you can configure certain aspects of your integration, including permissions and notifications.
Integration Launching	The integration system enables Workday to launch and track your integration. But to make development and testing easier, you can also launch from Studio.
Integration Monitoring and Troubleshooting	Track the progress of your integration in either Studio or Workday. In Studio, you can monitor the execution of the integration on the Process Monitor . You can also view a consolidated report of the integration process after it has completed.