HR Integrations

The HR Integrations application provides a way to keep employee profile and leave of absence (LOA) information synchronized between HR Service Delivery and third-party HR systems.

HR Integration provides a two-way synchronization with third-party HR systems. The base system provides integration with Workday.

HR Integrations supports Workday API version 24.1.

By default, the following information is pulled (inbound) from the third-party HR application:
  • Departments
  • Locations
  • Job Profiles
  • Worker Profiles
  • Effective Worker Profiles
  • Future Worker Profiles
Also by default, the following information is pushed (outbound) to third-party HR applications:
  • Leave of Absence (LOA) service
  • Contact information
  • Legal first and last name

The process to integrate with a third-party HR application is:

The steps to configure and run HR Integration are:
  • Configure the integration source information:
    • Configure credentials.
    • Configure properties.
      Note: The base system supports Workday 24.1. Other versions should be tested in your development environment before attempting to use in your production environment.
  • Configure inbound (pull) integration.
    • Create or check that integration services have correct staging tables and order.
    • Create or check that webservices have correct WSDL and SOAP message functions.
    • Create or check integrations service mapping.
    • Change dry run and debug properties to true.
    • Run scheduled sync job.
    • Ensure that integration data is correct.
    • Generate schema mapping from .xml response.
    • Change dry run and debug properties to false.
    • Create or check that transform maps are correct.
  • Configure outbound (push) integration.
    • Configure what information and corresponding core table that HRSM pushes (outbound) to the third-party HR application.
    • Pull together the HRSM core table and information, the target column in the third-party HR application, and the script on how to map the data.
    • Map the service to the SOAP message and the function.
  • Run scheduled sync job.
    • Create schedule to run integration sync or run on demand.
    • Check data moved from staging tables to core tables is accurate.