Workday Studio is an integrated Eclipse-based setting that allows clients to build and extend their own complicated integrations running in the Cloud.
Beginners Guide to Workday Studio
The Workday Studio platform is an open whiteboard that gives users a great amount of suppleness to build integrations across any two systems. Workday Studio is an integrated Eclipse-based environment that allows Workday customers and third parties to develop, deploy, debug, and support their own sophisticated integrations running in the Workday Cloud. Workday Studio extends to multiple data sources, transformation, and destination unlike EIB. Workday Studio extends to multiple data sources, reports, Workday Web Services, transformations, and delivers outputs to destinations unlike EIB.
Workday Studio offers setting which helps the consultants to focus on the critical business logic. Workday delivers EIB, packaged integrations and connectors.
Unlock the power of Workday’s integration using Workday Studio training:
Run Workday Studio integrations
Utilize development tools for interacting with Workday tenant.
Build custom integrations without servers.
Robust integrations unlike Enterprise Interface Builder (EIB) or connector templates.
Debug XML of custom integrations.
Transform text datasets into XML.
Client Use Cases for Workday Studio Integrations
A custom integration that isn't available through EIB or connector templates. Example: An integration that implements XML-to-text (TXT) transformations on a dataset.
An inbound integration to import bulk data to Workday from multiple data sources.
An outbound integration that exports bulk data from Workday in a specific format.
Conduct unit tests on the XML source code of custom integration.
Connect to third party using Connectors
Enterprise Interface Builder (EIB)
A developer who has a development skill-set and is comfortable with integration programming concepts using an Integrated Development Environment.
Cloud Repository Integration Collection
Integration Design: In Studio, develop the assemblies that form integration. Create assembly modules, which can be reused and shared with integration patterns and configurations.
Integration Deployment: In Studio, connect to the Workday Cloud Repository to deploy integration.
Integration Configuration: In Workday, configure certain aspects of integration, including permissions and notifications.
Integration Launching: The integration system enables Workday to launch and track integration.
Monitor and troubleshoot the progress of integrations
Studio interacts with different parts of Workday depending on the product area, purpose, and data sources of your integration:
Inbound integrations add and update data in Workday.
Outbound integrations extract data from Workday but don't change the data in Workday
WORKDAY STUDIO NAVIGATION
A workspace is a collection of projects.
A perspective defines layout of views.
Views support editors and navigates workspace.
Projects contain the files and resources needed to build and deploy a Workday Studio Integration System.
The Project Explorer is the default project navigator which displays the assembly at the top level of the project structure.
The Cloud Explorer is a "view" into your tenant. What you see in this view is what is deployed in the tenant identified in the connection details.
Assemblies provide a unified environment for all the core functions of Workday Integration System (transportation, routing, transformation, and error handling). This is a graphical editor that allows you to define a flow of messages exchanged between Workday and other systems.
Configure integrations using Workday Delivery Service that allow documents to be delivered over a range of different transports such as AS2, FTP, FTPS, and SFTP.
INTEGRATIONS, COLLECTIONS, AND THE CLOUD REPOSITORY
Assemblies provide a simple framework for implementing integrations. Within Workday Studio training, collections are a deployable unit and are the basis for deployment to the Cloud Repository. A collection can contain one or more integrations. Integrations are applications designed to integrate and run within Workday's Web service environment. Studio organizes integrations into groups called collections and deploys the integrations to Workday's Cloud Repository. Workday's network hosts the Cloud Repository.
The Workday application: The Workday application maintains information about the integrations that you deploy to the Cloud Repository in an abstraction called the integration system. This allows configuring various aspects of the integration such as security and setup data from within the Workday User Interface (UI). The Workday application also maintains a Process Monitor, which is used to track the execution history of integrations.
Cloud Runtimes: When the Workday Studio platform launches integration, it allocates a Cloud Runtime to the integration. This acts to ensure that integrations are protected from each other. Instead of executing integration events immediately, the Workday network server places each event in a queue, awaiting access to an available Cloud Runtime. When one becomes free, it retrieves the integration from the repository and deploys it to the Cloud Runtime for execution.
Workday STUDIO Best practices
Arrange the assembly components so that messages flow from left to right and top-to-bottom. Break assembly components up into logical and functional concerns sub-assemblies (using local-in and local-out transports). This will aid the readability of the main assembly flow and permits isolated and logical unit testing.
Group-related components use horizontal lines to separate functional areas of an assembly. Add notes as appropriate to individual steps to explain important/complex processing. Add notes to individual components explaining anything of interest.
This is particularly useful in routing steps are components where an "Execute When" condition has been added. Add more HTTP out or Workday out transports if that makes it easier to layout the components. If there are multiple calls to a single web service, it is better to have multiple kinds of transport, than to complicate the assembly diagram by trying to route all messages to one transport.