Integration Studio

Updated Integration Studio to give users the ability to view the Integration Description Language, or IDL, for integrations. IDL is a custom scripting language used to map and transform data in Integration Studio. Currently, viewing IDL is supported in Integration Studio, but editing it is not. For more information, see “Reference: IDL” in the Dayforce Integration Studio Administrator Guide.

As part of this update, Integration Studio was updated with an expression editor. You can access this in Step 3. Map fields from Dayforce to Vendor, in the Source section, in the Source Details drop-down. The new Expression source type offers an extremely robust and powerful editor for power users to configure complex mappings.

For more information, see “Map Fields from Dayforce to Vendor” in the Dayforce Integration Studio Administrator Guide.

Updated Integration Studio with several enhancements to improve usability, such as refinements to navigation and adding drag-and-drop mapping actions.

You can now export your integration configurations from one Dayforce environment and import them into another.
For example, you can configure and test your integrations in non-production environments and then export them to production environments using the export/import functionality.

For more information, see the Dayforce Integration Studio Administrator Guide.

Updated Integration Studio to add the ability for users creating Build Your Own connectors to configure report-sourced integrations to use multiple filters and conditions for the same field. This functionality supports setting up OR conditions in the report configuration.

Also with this update, Integration Studio automatically generates the fields and mappings for these report-sourced integrations.

For more information about Integration Studio, see the Dayforce Integration Studio Administrator Guide.

You can now change the source of a saved integration in Integration Studio without losing the mappings that you previously configured.

For example, if you have a configuration that originally used the source Bulk Employee API, and you change the source to Dayforce Report, Integration Studio does not automatically change the mapping and transmission details. Instead, it shows the following message:

"Source has been updated and has impacted different areas in your configuration where Source Fields were already selected. Please review the new setup accordingly and update as needed. The Destination Profile has not changed."

For more information, see the Dayforce Integration Studio Administrator Guide.

You can now see a log in Integration Studio which shows all the previous times that you ran an integration with a selected configuration.

In Integrations > Integration Studio, in the Available integration configurations screen, you can click the ellipses icon to the right of a listed integration, and then click View Log.

For more information, see the Dayforce Integration Studio Administrator Guide.

Updated Integration Studio with functionality to maintain a dynamic count of data segments to be used in benefit enrollment exports of 834 format.

This functionality was added to Step 3. Map fields from Dayforce to <vendor>, and support is available for XML, JSON, and Block CSV hierarchical output, specifically for aggregations, which require destination data fields whose date type is Number.

For more information, see the Dayforce Integration Studio Administrator Guide.

Updated Integration Studio to add functionality to the Event Driven HR Changes (Outbound from Dayforce) connector so that users can configure a single integration that pulls from multiple events. In Step 2. Define the parameters of this integration, in the Source section, in the Event Type drop-down, users can select multiple event types to be pulled by the integration.

For more information, see the Dayforce Integration Studio Administrator Guide.

Updated Integration Studio to give you the ability to reference all arrays in the expression editor when you are configuring mappings using expressions in Step 3. Map fields from Dayforce to <vendor>.

For more information, see the Dayforce Integration Studio Administrator Guide.

Updated Integration Studio to give users the ability to define OR filters to configure integrations that can include two or more groups of employees. For example, you could configure an integration with filters to include Active status OR TerminationDate within last 30 days.

For each subsequent criteria row, you can select AND or OR as the OperatorType in a new Type column. When you add a new criteria row, the Type defaults to AND. You can select one or more criteria rows. If you select two or more consecutive criteria rows, where at least one row is currently not grouped, the Group Selected option becomes available.

For more information, see the Dayforce Integration Studio Administrator Guide.

Updated Integration Studio with the following MERCANS - HR Connectors:

• Mercans PAK Core HR
• Mercans PAK Confidential ID
• Mercans PAK Country Specific Information
• Mercans JOR Confidential ID
• Mercans JOR Core HR
• Mercans JOR Country Specific Information
• Mercans TUR Confidential ID
• Mercans TUR Core HR
• Mercans TUR Country Specific Information

You can view these connectors in Integration Studio by clicking Create Integration. Each of these connectors has the following specific elements:

In Step 1. Name this integration, the Vendor value is read-only, and contains Mercans by default.

In Step 2. Define the parameters of this integration, in the Source section, the Dayforce API contains only the Bulk Employee API option.

In Step 4. Define the transmission details of this integration, the Transmission Method is not automatically populated.

For general information, see the Dayforce Integration Studio Administrator Guide.