In this article

Overview

You can use Workday Cancel Snap to cancel the objects in Workday, based on the field values in the input document that match the Workday object schema field names. These field names are defined by the Workday Web Service Definition Language (WSDL). The fields that match the object to be canceled are provided on the input view of the Snap and can be mapped using an upstream Mapper Snap.

Learn more about Workday Web Services (WWS) Directory for information on the Workday objects.

Snap Type

Workday Cancel Snap is a Write-type Snap that cancels the Workday objects that have been created.

ETL Transformations & Data Flow

This Snap enables the following ETL operations/flows:

  1. Transform SnapLogic input document data to Workday SOAP XML request

  2. Loads the update data into Workday and provide the respective data which has being written, in the output view as JSON format

This Snap creates a SOAP request based upon the Workday Cancel object input schema and the input data passed into the snap. The Snap then submits the SOAP request to Workday and deletes the respective object in Workday and and converts the Workday SOAP XML response to JSON in the output view.

  1. The Snap collects the Workday service and object input for the Workday server to process with the expected upstream information.
    Field can be mapped using an upstream Mapper Snap which will allow the mapping of fields or values to the field that are available on the selected service object.

  2. The Snap transforms the input document data matching the Workday input schema to create and submit a SOAP request.

  3. On successful Workday server response, the Snap displays one output document for every record updated, hence any document processing Snap can be used down stream.

  4. The Snap converts the returned SOAP XML response into JSON for the output view.

  5. If there is an exception, the Snap writes an error to the output view.

Prerequisites

Support for Ultra Pipelines

Works in Ultra Task Pipelines.

Limitations and Known Issues

None.

Snap Views

Type

Format

Number of Views

Examples of Upstream and Downstream Snaps

Description

Input 

Document

  • Min:1

  • Max:1

  • Mapper

  • JSON Generator

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

  • JSON Formatter

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 running the Pipeline by choosing one of the following options from the When errors occur list under the Views tab. The available options are:

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

  • Discard Error Data and Continue: Ignores the error, discards that record, and continues with the rest of the 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.

Snap Settings

  • Asterisk (*): Indicates a mandatory field.

  • Suggestion icon ((blue star)): Indicates a list that is dynamically populated based on the configuration.

  • Expression icon ((blue star)): Indicates whether the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.

  • Add icon ((blue star) ): Indicates that you can add fields in the field set.

  • Remove icon ((blue star)): Indicates that you can remove fields from the field set.

Field Name

Field Type

Description

Label*

Default Value: Workday Cancel
Example: Cancel Cost Center List from Workday

String

Specify a unique name for the Snap.

Timeout*

Default Value: 60
Example: 0

Integer

Specify the timeout value for each Workday SOAP request. The value of 0 indicates no timeout. As the Workday Cancel supports Workday SOAP pagination, multiple SOAP requests can occur for one execution. Consequently, the timeout can be less than the time it takes to complete writing documents to the output view. 

Service*

Default value: [None]
Example: Revenue_Management

String/Expression/Suggestion

Specify the name of the web service that you want to use for cancelling the objects. Though all available services are selectable, only Resource_Management, Revenue_Management, Financial_Management, Integrations, Cash_Management may have objects that provide cancellations.

Object*

Default value: [None] 
Example: Cancel_Customer_Invoice

String/Expression/Suggestion

Specify the object to write. The objects are suggested based on the selected service, such as selecting the service Payroll will retrieve all objects for Payroll that are retrievable from Workday.

Number of Retries 

Default Value: 0
Example: 3

Integer

Specify the number of attempts the Snap should make, in case of connection failure or timeout.

Retry Interval (seconds)

Default Value: 1
Example: 3

Integer

Specify the time interval in seconds between the retry attempts.

Snap Execution

Default Value: Execute 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 validation. Subsequently, performs full execution of the Snap (unlimited records) during Pipeline runtime.

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

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

Troubleshooting

Error

Reason

Resolution

HTTP/1.1 407 Proxy Authentication required.

The Snap is unable to tunnel through proxy.

Add the following key-value pair values to your Groundplex configuration and restart the plex to reflect the changes.

Key: jcc.jvm_options
Value: -Djdk.http.auth.tunneling.disabledSchemes=""

Examples

Canceling an Invoice Using the Revenue Management Service

This example Pipeline demonstrates how to cancel an invoice using the Revenue_Manangement service..

Download example Pipeline.

note

This Pipeline does not work for any Workday tenant since they are read by WID.

This Pipeline does not work for any Workday tenant since they are read by WID.

note

For each expression field, you must provide a corresponding Workday ID (WID). You can get the WID using the Workday Read Snap.

For each expression field, you must provide a corresponding Workday ID (WID). You can get the WID using the Workday Read Snap.

First, configure the Mapper Snap to map the customer invoice type and its value. Next, configure the Workday Cancel Snap to use the Revenue_Management service with the Cancel_Customer_Invoice object.

In the output preview, you can see the customer invoice reference ID that is canceled.

Handling an Error After an Attempted Cancellation

The second example showcases error handling. Invoice cancelation can only happen once per invoice. This example shows an error when we try to cancel an object that was already canceled.

Download the example Pipeline.

note

This Pipeline does not work for any Workday tenant since they read by WID

This Pipeline does not work for any Workday tenant since they read by WID

The mapping and the Workday Cancel Snap are configured as in the first example, except that you need to add an Error View to the Workday Cancel Snap.

The error view shows the following:

Downloads

  1. Download and import the Pipeline into SnapLogic.

  2. Configure Snap accounts as applicable.

  3. Provide Pipeline parameters as applicable.

Snap Pack History