Table of Contents

Search

  1. Preface
  2. Workday Connector
  3. Workday connections
  4. Workday operations
  5. Mappings and mapping tasks with Workday
  6. Appendix A: Workday data type reference
  7. Appendix B: General considerations when using Workday V2 Connector
  8. Appendix C: Workday target approaches

Workday V2 Connector

Workday V2 Connector

Rules and guidelines for Workday operations

Rules and guidelines for Workday operations

Consider the following rules and guidelines for Workday Connector read and write operations:
  • When you use a Workday V2 connection to configure a source or target operation and try to modify the object by manually typing a valid name in the
    Operation
    field, the task fails with the following validation error:
    Error occurred validating object: Selected connection does not support this operation.
    Workaround: Select the same operation from the
    Select...
    dialog box and run the task again.
  • When you use in-out parameters of type DateTime, the task fails as Workday does not support the format used for DateTime.
  • If a task fails when you write data to a Workday V2 target, the statistics generated for rejected and applied rows is incorrect.
  • When you configure a Source transformation in a mapping to fetch instant updates from Workday, you must pass the Date Time attributes in Pacific Time. For example, when you specify the update to and from fields, use the
    yyyy-mm-ddThh:mm:ss
    format.
  • When you read data from Workday that contains the Date Time attributes and then write to a flat file, the Secure Agent writes the Date Time in Eastern Standard Time (EST).
  • When you use Workday Connector to read or write data, the Secure Agent maps binary data to string. To read documents or images from Workday, you must convert base64 string to binary and then load it to the target. To write images and documents to Workday, you must read the images and documents in binary format from the source, convert it to base64 string, and then load it to the Workday target. If the source contains the base64 string value representing the file, you can directly map the field to the Workday target.
  • When you configure a Workday connection, test connection validates only for the Human Resources module. When you specify a module other than Human Resources in the Workday connection, you can verify that the connection is valid only if the mapping task runs successfully.
  • You do not need to set the WorkdayBatchSize property in the
    pmrdtm.cfg
    file. Instead, set the batch size in the advanced source property.
  • When you configure a request to retrieve more than one page from Workday, specify the value for As_Of_Entry_DateTime parameter in the XML request to ensure that the data set that you retrieve does not change when you process the data. This parameter filters the data returned in the response property by the date and time when the data was entered into the system. If you do not specify a value, the property value defaults to the current date and time.
  • When you configure a task to update data in Workday, and if Workday does not provide a response XML for that operation, you do not receive a response message for the number of rows or columns successfully updated in Workday.

JVM Options and Cache Size Configurations for Workday Connector

To read large number of records from Workday, you must perform the following steps:
  • Set the JVM options for type
    DTM
    to increase the
    -Xms
    and
    -Xmx
    values in the system configuration details of the Secure Agent, and then restart the Secure Agent.
  • You can perform one of the following tasks when you specify the cache size:
    • You can increase the cache size for the web service response in the advanced properties of the Workday source transformation to a size equal to or more than the memory required for a SOAP response. The value may differ for different Workday modules and count specified in request.xml.