Using the Workday Read Snap for Error Handling

This example demonstrates how you can use the Workday Read Snap for error handling. Here, we assume a bad mapping.

In the following mapping, we assume that the data types that we mapped together are incompatible. Usually while mapping an object, you may have to make several attempts to map the data you need to appropriate fields; so it is good to understand how you can manage problematic mappings.



Download this Pipeline
Note: You may need to update your tenant details in the downloaded example, because Workday reads queries by the WID of the requester.
  1. Configure the Workday Read Snap with the service and object for data retrieval.
  2. In the Mapper Snap, configure the mapping of aaa to the $Request_References[*].Worker_Reference[*].ID[*].type field to simulate a bad mapping with an incompatible data type.

    Workday Read Snap configured with bad mapping in the Mapper Snap
  3. Add an Error View to the Workday Read Snap to handle any errors during execution.
  4. Run the pipeline. The invalid type mapping of aaa to $Request_References[*].Worker_Reference[*].ID[*].type triggers the Workday Read Snap to write to the error view. (The error view on the Snap must be enabled explicitly.)

    Error view output showing the invalid type mapping error

Understanding Workday Read Error Views

  • The error key provides the message returned from Workday. In this case, the error key indicates that mapping the value aaa to the type field is invalid.

  • The envelope key contains information related to the SOAP envelope that was populated by applying the variables from the input view into the generated SOAP envelope.

  • The stripped envelope key carries the information of the SOAP envelope that will be sent to Workday.

  • The original key carries the document that came in on the input view.

To reuse the example pipelines:
  1. Download and import the SLP file into your Environment.
  2. Configure Snap accounts.
  3. Provide Pipeline parameters, if any.