Relationships Between Business Objects

There is no automatic connection between business objects and business processes. The burden is on the developer to ensuring data integrity and syncing to proper states.
The system does not automatically lock a record after a business process completes, nor does the system automatically persist data to an object once complete. If this is a requirement, consider an orchestration.
Updating business objects once a business process completes requires additional considerations. A best practice for this requirement is to use a "staging/proposed" business object for the business process. This will ensure data integrity in the business process event history.
Do not invoke multiple business object events for the same business object instance.

Vaccination record with a multi-instance field to capture information for all vaccinations
Pilots license object with a field to capture certificates for each plane/license type.

{
  "type": "dropdown",
  "id": "ddnSelectExpense",
  "label": "Select a Mobile Expense",
  "values": "<% expenseData.data %>"
}

displayKey Attribute

A

dropdown

has additional atrtibutes. You can specify the

displayKey

, which allows you to display a specific field instead of using the

descriptor

.

{
  "type": "dropdown",
  "id": "ddnSelectExpense",
  "label": "Select a Mobile Expense",
  "displayKey" : "date",
  "values": "<% expenseData.data %>"
},

The

dropdown

now displays the expense

date

from the API response instead of the

descriptor

.

dropdown Widget with date as the displayKey Attribute

idKey Attribute

You can also use the

idKey

attribute when defining a

dropdown

. In the code, we added a

text

widget to the page containing the

dropdown

. We set the

text

widget's

value

binding to reference the value chosen in the

dropdown

. Here is that code:

{
  "type": "dropdown",
  "id": "ddnSelectExpense",
  "label": "Select a Mobile Expense",
  "displayKey" : "date",
  "values": "<% expenseData.data %>"
},
{
  "type" : "text",
  "label" : "Data from Drop Down Widget",
  "value" : "<% ddnSelectExpense.value %>"
}

With this code, the

text

widget receives the WID of the item selected in the

dropdown

, not the

date

. To summarize, the:

Default
displayKey
is the
descriptor
.
Default
idKey
is the WID.

idKey Passed from the dropdown Widget

In the image above, brackets enclose the WID, as if it was in an array. The user can choose only one item in a

dropdown

. That item will be the

[0]

item. To avoid this, change the value binding in the

text

widget, as displayed here:

{
  "type" : "text",
  "label" : "Data from Drop Down Widget",
  "value" : "<% ddnSelectExpense.value[0] %>"
}

The WID is no longer enclosed in brackets.

Corrected: idKey Passed from the dropdown Widget

You may not want to show the WID. Instead, you may want to display the expense's

descriptor

in the

text

widget when the user selects a date from the dropdown. To do that, you need to add the

idKey

binding in your

dropdown

code.

{
  "type": "dropdown",
  "id": "ddnSelectExpense",
  "label": "Select a Mobile Expense",
  "displayKey" : "date",
  "idKey" : "descriptor",
  "values": "<% expenseData.data %>"
},

Now, the

descriptor

for the chosen expense appears in the

text

widget.

Descriptor Passed in the idKey

The user to select multiple items.
The user to search items in the list.
The developer to define multiple levels of items within the widget.

{
  "id": "ilRegions",
  "type": "instanceList",
  "label": "Regions",
  "multiSelect": "true",
  "values": "<% regionData.items %>",
  "idKey": "name",
  "displayKey": "name"
}

Implementing InstanceList Search

You can implement search in the

instanceList

. By default,

instanceList

will display the items per its

values

binding. At the top of the list, there is a search box.

Unfiltered instanceList Widget

The user can enter a value, like "all active", and press Enter to search.

Filtered instanceList Widget

Normally,

instanceList

depends on one

endPoint

. To implement search, you will need a second

endPoint

.

"endPoints": [
  {
    "name": "dataSources",
    "_comment": "Return all dataSources (limited).",
    "baseUrlType": "WORKDAY-WQL",
    "url": "dataSources?limit=20",
    "authType": "sso"
  },
  {
    "name": "dataSourcesSearch",
    "baseUrlType": "WORKDAY-WQL",
    "url": "<% 'dataSources?searchString=' + instanceListQuery + '&amp;limit=50' %>",
    "authType": "sso",
    "deferred": "true"
  }
…

The

dataSourcesSearch

endPoint

will return all WQL

dataSources

that match the specified

searchString

. You will create an expression to define the

searchString

parameter in the

url

binding. An implicit variable, named

instanceListQuery

, contains the search string the user enters in the

instanceList

widget. By setting this endpoint's deferred attribute to

true

, the

endPoint

will not execute on page load. This

endPoint

will only execute when explicitly called via another element.

The final step is to configure the

instanceList

to be aware of the

dataSourcesSearch

endPoint

. In the following code, the

values

binding uses the

dataSources

endpoint

. Both the

searchEndPoint

and

searchResultValues

bindings use the

dataSourcesSearch

endPoint

.

{
  "id": "ilSelectDataSource",
  "type": "instanceList",
  "label": "Data Sources",
  "helpText": "Find Data Sources by entering a search string.",
  "values": "<% dataSources.data %>",
  "searchEndPoint": "<% endpoints.dataSourcesSearch %>",
  "searchResultValues": "<% dataSourcesSearch.data %>",
  "idKey": "id",
  "displayKey" : "descriptor",
  "required": "true",
  "multiSelect": "false"
}

{
  "type": "checkBoxList",
  "id": "cbxListExp",
  "label": "Expenses",
  "values": "<% expenseData.data %>",
  "maxSelectable" : 3
}

{
  "type": "radioGroup",
  "id": "rgListExp",
  "label": "Expenses",
  "values": "<% expenseData.data %>"
}

FROM
: one data source
WHERE
: one or more optional filter conditions
GROUP BY
: one or more optional fields to group data
HAVING
: one or more optional filter conditions for the group
ORDER BY
: one or more optional sort fields
LIMIT
: to optionally restrict the number of rows returned

SELECT employee, hireDate, isManager, supervisoryOrganization, cf_TotalBasePayAnnualizedInUSD_Amount
FROM allActiveEmployees
WHERE hireDate > '2017-01-01'
ORDER BY cf_TotalBasePayAnnualizedInUSD_Amount DESC
LIMIT 10

SELECT fullName, hireDate, yearsOfService

Users must have the proper Workday security to access the fields.
Fields Authorized Usage must be "Report Writer" or "Default Areas."
Developers cannot use wildcards, like "
SELECT *
".
Fields cannot have required prompts.
If two or more fields resolve to the same web service alias, WQL will use the first field defined in the system.

FROM allActiveEmployees

There is no support for joins since developers can only specify one data source.
Users must have the proper Workday security to access the data source.
Data sources cannot use loop effective date processing.
If two or more data sources resolve to the same web service alias, WQL will use the first data source defined in the system.

AND
OR
NOT

WHERE hireDate >= '2016-01-01' AND hireDate <= '2016-12-31'
WHERE (totalBasePayAmount > 50000 AND totalBasePayAmount <= 100000) OR isManager = TRUE

Filtering on text fields
primaryAddressCity = 'San Francisco'
lastName > 'X'
primaryAddressCity IS EMPTY
Filtering on numeric and currency fields
totalBasePayAmount != 0
age >= 50
Filtering on date fields
hireDate > '2017-01-01'
dateOfBirth IS EMPTY
Filtering on instance fields
supervisoryOrganization IN (5b9d7cd02cb84615a683209c9d99d0a9)
supervisoryOrganization NOT IN (5b9d7cd02cb84615a683209c9d99d0a9, 2eace1eb4d9a4ef48dd74cd5bd8906d9)
Filtering using reference IDs
supervisoryOrganization IN (Organization_Reference_ID = Global_Modern_Services_supervisory)
worker IN (Employee_ID=21001)
worker IN (Employee_ID=21001, 21002, 21003)
Filtering using a mix of instance fields and reference IDs
worker IN (Employee_ID=21002, 21003)
worker IN (3aa5550b7fe348b98d7b5741afc65534,3895af7993ff4c509cbea2e1817172e0)
supervisoryOrganization IN (1223ba8478644aa4bd3df3a749792fcf,e50d309a6d8540e3b533219cfa2c330b)
supervisoryOrganization IN (Organization_Reference_ID ='Global_Modern_Services_supervisory', 'Information_Technology_supervisory')
supervisoryOrganization_Superior IN (Organization_Reference_ID=Executive_Management_supervisory) <<multi-instance>>
Filtering on Boolean fields
isHighPotential = TRUE
isManager = FALSE

SELECT location, max(yearsOfService), age FROM allWorkers GROUP BY location, age HAVING age > 5 AND count( ) > 5
SELECT location, max(yearsOfService), avg(age) FROM allWorkers GROUP BY location HAVING avg(age) >= 10 AND count( ) > 5
SELECT count( ), location, max(yearsOfService), avg(age) FROM allWorkers GROUP BY location HAVING avg(age) >= 10 AND count( ) > 5
SELECT count( ), location, max(yearsOfService), avg(age) FROM allWorkers GROUP BY location HAVING avg(age) >= 10 OR count( ) > 5
SELECT count( ), location, max(yearsOfService), age FROM allWorkers GROUP BY location, age HAVING max(yearsOfService) >= 3 OR count( ) > 5 ORDER BY age DESC
SELECT location,max(yearsOfService),avg(age) FROM allWorkers GROUP BY location HAVING avg(age) >= 100 AND max(yearsOfService) >= 5 AND count( ) > 5

ORDER BY totalBasePayAmount DESC
ORDER BY primaryAddressStateProvince ASC, primaryAddressCity DESC

SELECT
statements can include calculated fields and custom fields defined on the business object.
SELECT
statements run with Entry Moment and Effective Moment set to the current moment.
WQL provides no direct access to multi-instance custom objects.
WQL does not support SQL functions.
Submit Read-only POST requests queries that are longer in length (2048+ characters) to avoid a query timeout at runtime.

You can perform specific searches of your organization's Workday data.
You have more flexibility over how you programmatically export Workday data.
You can explore available data sources and data source filters and fields.

Search for data sources by entering a search string, like "employee".
Get information about a specific data source if you already know the alias.

The descriptor (name) of the data source.
The WID for the data source is needed to locate the fields of the data source.
The alias for the data source, which you will need in your coding.

You must specify the WID of the data source whose fields you want to retrieve.
You can optionally enter a search string parameter to only return fields that match a particular pattern.

Name (descriptor) of the field.
Alias for the field (needed in coding).
WID for the field.