Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

You can use the Workday REST Snap to connect to the Workday REST APIs. This Snap supports all standard REST operations and provides a few enhancements over from the traditional SOAP APIs such as , including better object models , and better performance with faster API query responses. The=is Snap identifies the REST APIs using the OpenAPI specification specified for the service and connects to endpoints under the chosen selected service. It also supports authentication mechanisms such as OAuth2.0.

...

You must have a valid Workday REST Account, data to query, and Workday access to the specified objects. Contact your organization's Workday Security Administrator for appropriate access.

...

The Workday REST Snap does not support certain specific Unicode, Special, and UTF-8 byte characters due to because of the API limitation. This Snap produces an unexpected preview in the output when you pass input data with special or Unicode characters.

...

Type

Format

Number of Views

Examples of Upstream and Downstream Snaps

Description

Input 

Document

  • Min: 0

  • Max: 1

  • JSON Generator

  • Mapper

A document that conforms to the input view schema of the Snap. The input view schema is provided to an upstream Mapper Snap based on the selected service object.

Output

Document

  • Min: 1

  • Max: 1

  • Mapper

  • Router

A document that represents the record structure of the retrieved Workday service object. Each record is represented as one document on the output view.

Error

Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter while when running the Pipeline pipeline by choosing one of the following options from the When errors occur list under the Views tab:

  • Stop Pipeline Execution: Stops the current pipeline execution if the Snap encounters an error.

  • Discard Error Data and Continue: Ignores the error, discards that record, and continues with the remaining records.

  • Route Error Data to Error View: Routes the error data to an error view without stopping the Snap execution.

Learn more about Error handling in Pipelines.

...

Field Name

Field Type

Description

Label*

Default ValueWorkday REST
ExampleOnboarding newhires

String

Specify a unique name for the Snap.

 

Service*

Default Value: N/A
ExampleCompensation

String/Expression/Suggestion

Specify or select the Workday Service to connect to Workday.

Version*

Default Value: N/A
Examplev2

String/Expression/Suggestion

Select the version corresponding to the service.

OpenAPI Path*

Default Value:N/A
Example: /workers

String/Expression/Suggestion

Enter the path for the REST Endpointendpoint. Based on the service and version, the Snap downloads the open API specification and populates the list.

Operation*

Default Value: N/A
Example: get

String/Expression/Suggestion

Specify the operation to perform on the selected OpenAPI path or select from the suggestions list. The available options are:

  • GET: Reads and retrieves content and data.

  • POST: Creates a new resource with a new ID.

  • PUT: Updates and replaces the existing resources.

  • PATCH: Updates and modifies the resources. PATCH operation only modifies the content of the resources , but and does not entirely replace the resources entirely.

  • DELETE: Deletes Entirely deletes the resources entirely.

Number of Retries

Default Value:0
Example:3

Integer/Expression

Specify the number of attempts the Snap must make to perform the selected operation in case of connection failure or timeout.

The Snap retries the request if the value is greater than zero or retries only if it encounters 401 or 500 error.

Retry Interval (seconds)

Default Value: 1
Example: 2

Integer/Expression

Specify the time retry interval in seconds between retry attempts.

HTTP Headers

Use this field set to add additional headers to the HTTP request defined in the Workday OpenAPI specification. 

Header

Default Value: N/A
Examplecontent-type

String/Expression

Specify a name for the HTTP header.

Values

Default Value: N/A
Exampleapplication/json

String/Expression

Specify a value to assign to the HTTP header.

Pass through

Default Value: Deselected

Checkbox

Select this checkbox to enable the Snap to pass the input data to the downstream Snap and display in the output document.

Enable Pagination

Default Value: Selected

Checkbox

Select this checkbox to enable the Snap to return the response in multiple pages when the input document contains the limit and offset query parameters.

  • The maximum limit value of the page size is 100—that is, the Snap fetches all records until the last page with 100 records on each page.

  • If the limit field is blank, the default limit value is 20 and the Snap displays only one page of records.

When you deselect this checkbox, the Snap limits the number of output documents to 100, with only one page of records.

Snap Execution

Default ValueExecute only
Example: Validate & Execute

Dropdown list

Select one of the three modes in which the Snap executes. Available options are:

  • Validate & Execute: Performs limited execution of the Snap, and generates a data preview during Pipeline pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during Pipeline runtime.

  • Execute only: Performs full execution of the Snap during Pipeline pipeline execution without generating preview data.

  • Disabled: Disables the Snap and all Snaps that are downstream from it.

...

This example Pipeline demonstrates how to retrieve the compensation details with the scorecardResults object using the following operations:

  • POST: Creates the scorecardresults object.

  • GET: Retrieves the compensation details.

  • PATCH: Updates the details.

  • DELETE: Deletes the IDs of the scorecard results.

This Pipeline contains consists of the following key steps:

  1. Creating Create a JSON document to send the input data.

  2. Retrieving Retrieve the scorecardResults object from Workday.

  3. Updating Update the data in the scorecardResults object.

  4. Deleting Delete the updated data in the scorecardResuts object.

Step 1: Configure the JSON Generator Snap as follows with the scorecardResults object and validate the Snap.:

...

Step 2: Configure the Mapper Snap to pass the scorecard details as an input to the Workday REST Snap.

...

After validating the Snap, you can view it in the output that the object is created.

...

Step 5: Configure the Workday REST Snap with the compensation Service and get Operation. After validating the Snap, you get the object value.:

...

Step 6: Configure the Mapper Snap to extract the scorecardResults.

...

After validating the Snap, you can view the output with the deleted path ID values.

...

Download this Pipeline

...

Step 1: Configure the Mapper Snap with the limit as 100 and offset at 0—this limits the worker records to 100 records on each page.

...

Step 2: Configure To configure the Workday REST Snap as follows. Select , select the Enable Pagination checkbox to enable the Snap to paginate the response.

...

Step 3: Execute the Pipelinepipeline. The Snap returns all worker records (365 records in this case) with 100 records on each page.

...

Download this Pipelinepipeline.

...

Downloads

Info
  1. Download and import the Pipeline pipeline into SnapLogic.

  2. Configure Snap accounts, as applicable.

  3. Provide Pipeline parameters, as applicable.

...