How to use IBM App Connect with Workday

Workday delivers cloud-based solutions that incorporate human capital management, financial management, financial performance management, analytics, and other services.

Availability:

Cloud-managed connector
Local connector in containers (Continuous Delivery release)
Local connector in containers (Extended User Support release)
Local connector in containers (Long Term Support release)

The following information describes how to use IBM® App Connect to connect Workday to your other applications.

Connecting to Workday
- Creating an Integration System User in Workday
- Finding your domain and tenant names (from your Workday WSDL URL)
General considerations
Events and actions

Connecting to Workday

You can connect to Workday in the IBM App Connect catalog. Alternatively, you can connect to Workday in the flow editor when you add a Workday event or action to a flow. To connect IBM App Connect to Workday, you provide the following connection information.

Domain name: The domain name of your Workday instance or sandbox; for example: wd2-impl-services1.workday.com. Get the domain name from your Workday WSDL URL, for example, https://domain_name/ccx/service/tenant_name/service_name/version.; Tip: A way to determine your domain and tenant names is from the WSDL URL of a service endpoint from the list of your public Workday web services; the WSDL URL has the format: https://domain_name/ccx/service/tenant_name/service_name/version
For example: https://wd2-impl-services1.workday.com/ccx/service/my_company/Absence_Management/v37.0

If you do not already know the domain and tenant names for your Workday instance, see Finding your domain and tenant names (from your Workday WSDL URL)
Tenant name: The tenant name of your Workday instance or sandbox; for example: my_company. Get the tenant name from your Workday WSDL URL, for example, https://domain_name/ccx/service/tenant_name/service_name/version.; Tip: If you do not already know the domain and tenant names for your Workday instance, see Finding your domain and tenant names (from your Workday WSDL URL)
User name: The name of the Workday Integration System User that App Connect should use to connect to your Workday instance or sandbox; Tip: If you do not know the name of a Workday Integration System User to use, see Creating an Integration System User in Workday
Password: The password of the Workday Integration System User
API version: The current supported version is v35.1

Tip:

Before you use the account that is created in App Connect in a flow, rename the account to something meaningful that helps you to identify it. To rename the account on the Catalog page, select the account, open its options menu (⋮), then click Rename Account.

App Connect provides a default set of Workday actions. After you create a Workday connection account, you can see any more actions that are available in your Workday instance or sandbox.

Connections to Workday use a Workday Integration System User. If you do not already have an Integration System User ready, work with your company’s Workday administrator to create and configure an Integration System User; for example, as outlined in this section. For more detailed information, see the Workday documentation or ask your company’s Workday administrator.
1. Login to Workday as an administration user
2. Create an Integration System User then add the user to an unconstrained user group by completing the following steps in the Workday UI for the administration user:
  1. 1. Search for and open the Create Integration System User task.
    2. Configure and save an Integration System User. If you do not want the userid to be used with the Workday UI, select the Do Not Allow UI Sessions option.
    3. Save a copy of the user name and password values for use when connecting App Connect to Workday
    4. Search for and open the Create Security Group task
    5. In the Type of Tenanted Security Group field, choose Integration System Security Group (Unconstrained).
    6. Enter a group name and then click OK.
    7. Select the user you created from the Integration System Users choice list, click OK, and then click Done.
3. If the security policy changes aren't applied automatically, select the Activate Pending Security Policy Changes action, add the required comment, then click OK. On the next page, select the Confirm checkbox then click OK.

If you do not already know the domain and tenant names for your Workday instance, you can find the values from the WSDL URL of one of your Workday public web services; for example, as outlined in this section. For more detailed information, see the Workday documentation or ask your company’s Workday administrator.
1. Login to Workday as an administration user
2. Search for Public Web Services, then select the Public Web Services to view a list of all public web services.
3. Select the menu (...) for one of the web services; for example, Absence Management (Public), then select Web Service > View WSDL
4. Scroll to the bottom of the page to find the WSDL URL, which has the format: https://domain_name/ccx/service/tenant_name/service_name/version
  For example: https://wd2-impl-services1.workday.com/ccx/service/my_company/Absence_Management/v37.0
5. Save a copy of the domain_name and tenant_name values for use when connecting App Connect to Workday; from the example above:
  - Domain name: wd2-impl-services1.workday.com
  - Tenant name: my_company
Note: The domain name and tenant name values are case sensitive.

General considerations

Before you use App Connect Designer with Workday, take note of the following considerations:

(General consideration) You can see lists of the trigger events and actions that are available on the Catalog page of the App Connect Designer.
For some applications, the events and actions in the catalog depend on the environment (IBM Cloud Pak for Integration or App Connect on IBM Cloud) and whether the connector supports configurable events and dynamic discovery of actions. If the application supports configurable events, you see a Show more configurable events link under the events list. If the application supports dynamic discovery of actions, you see a Show more link under the actions list.
(General consideration) If you are using multiple accounts for an application, the set of fields that is displayed when you select an action for that application can vary for different accounts. In the flow editor, some applications always provide a curated set of static fields for an action. Other applications use dynamic discovery to retrieve the set of fields that are configured on the instance that you are connected to. For example, if you have two accounts for two instances of an application, the first account might use settings that are ready for immediate use. However, the second account might be configured with extra custom fields.

Events and actions

Workday events

These events are for changes in this application that trigger a flow to start performing the actions in the flow.

Note: Events are not available for changes in this application. You can trigger a flow in other ways, such as at a scheduled interval or at specific dates and times.

Workday actions

These are actions on this application that you want a flow to complete.

Absence Management

Get Time Off Plan Balances

Cash Management

Get Payments
Get Bank Statements

Financial Management

Get Statistics
Get Business Plan Details

Human Resources

Find Organization

Integrations

Get Subscriptions
Put Sequence Generator

Integrations

Get Subscriptions
Put Sequence Generator

Learning

Get Learning Enrollments

Payroll Interface

Get Period Schedules
Get Worker Costing Allocations

Performance Management

Get Degrees
Put Degree

Recruiting

Get Candidates

Resource Management

Get Timesheets
Get Projects

Student Records

Get Change Licenses

Talent

Get Job History Companies
Put Job History Company

Time Tracking

Put Time Clock Events
Import Time Clock Events

More items are available when you have connected App Connect to Workday.