Starling Connect Hosted - One Identity Manager Administration Guide

Dayforce is an HCM software platform that helps in data unification across each phase of employee lifecycle enabling better reasoning and decision-making. It offers a vantage point view and control from a single platform covering benefits, HR, payroll, workforce and talent management.

To configure the connector, following parameters are required:

• Connector name

• Username for the cloud account

• Password for the cloud account

• Target URL (Format:- https://{instance_name}.dayforcehcm.com/Api/{clientNamespace}/V1)

• Request Delay (in ms)

• Instance DateTime Offset (refer Configuring additional datetime offset in connectors for more details)

Supported objects and operations

Employees

Departments

Locations

Organizations

Mappings

The mappings are listed in the tables below.

Filter Resource

Dayforce target APIs supports filtering on employees and hence the Starling Connector for Dayforce has the filter feature implemented in employees endpoint. Below are the details on the supported attributes and operations on filter functionality on the Employee resource on the SCIM connector.

Supported attributes for Dayforce

More information about Filtering Resource

• As the Dayforce API support only AND conditions in the request filter criteria, the connector has implemented to support only AND in SCIM filter condition.

• In the connector filter functionality any invalid or non-supported filter criteria will be ignored in the filter. If no valid criteria found then normal LIST employees will be carried out.

• When 'meta.lastModified' is used with 'lt' | 'le' as the filter criteria then the target APIs demands filter condition on 'meta.lastModified' with 'gt' | 'ge' | 'eq' since a date range is expected by the target APIs. When 'meta.lastModified' is applied with 'gt' | 'ge' | 'eq' but no 'meta.lastModified' with 'lt' | 'le' criteria is provided, then the current date time will be used within the connector logic to acomplish the date range requirement.

• The filter functionality looks generously for the filter condition and values instead of performing a greedy and strict match. For example: the 'meta.lastModified' with below are some of the valid formats:

  filter=meta.lastModified gt xxxx-xx-xxTxx:xx:xx

  filter=meta.lastModified gt xxxx-xx-xx xx:xx:xx

  filter=meta.lastModified gt xxxx-xx-xxTxx:xx:xx.xxx

  filter=meta.lastModified gt "xxxx-xx-xxTxx:xx:xx"

  filter=meta.lastModified gt xxxx-xx-xx xx:xx:xxZ

  filter=meta.lastModified gt xxxx-xx-xxTxx:xx:xx.xxxZ

  filter=meta.lastModified gt 'xxxx-xx-xxTxx:xx:xx'

For more information about Filter Resource, see Documentation of filtering on Dayforce endpoints.

Connector SCIM Configuration

The Dayforce connector supports configuring custom attributes for Employee object type. Supported data types are integer, decimal, string, datetime, boolean and binary.

One IM Configuration for Delta Synchronization

Modifying the FullProjection process

1. In Designer, locate the 'DPR_DPRProjectionStartInfo_Run_Synchronization' process click to edit it. Under 'Pre-script for generating' add the script as mentioned below:

   'Starling Delta Sync Handling (search sync project variables with their names staring with dprRevisionDate and put the corresponding revision data value in)

   Dim f = session.SqlFormatter

   Dim nameSchema as String

   Dim nameVariable as String

   Dim variableValue as String

   values("OverrideVariables") = ""

    

   'search project variables dprRevisionDate*

   Dim qVariables = Query _

   .From("DPRSystemVariable") _

   .Orderby("UID_DPRSystemVariable") _

   .Where( f.AndRelation( _

   f.Comparison("Name", "dprRevisionDate%", ValType.String, CompareOperator.Like, FormatterOptions.IgnoreCase), _

   f.UidComparison("UID_DPRSystemVariableSet", $UID_DPRSystemVariableSet$, CompareOperator.Equal))) _

   .Select("Name")

   Dim colVariables = Session.Source.GetCollection(qVariables)

    

   If colVariables.Count > 0 then

   'fetching revision data from last synchronization of that sync project configuration

   Dim qRevStore = Query _

   .From("DPRRevisionStore") _

   .Where( f.AndRelation( _

   f.UidComparison("UID_DPRProjectionConfig", $UID_DPRProjectionConfig$, CompareOperator.Equal), _

   f.UidComparison("UID_DPRSystemVariableSet", $UID_DPRSystemVariableSet$, CompareOperator.Equal))) _

   .Select("Value", "SchemaTypeKey")

    

   Dim colRevStore = Session.Source.GetCollection(qRevStore)

   Dim dictRevStore = new System.Collections.Generic.Dictionary(of String, String)()

    

   For Each elemRevStore As IEntity In colRevStore

   nameSchema = elemRevStore.GetValue("SchemaTypeKey").String 'Schema[FTP#C04A6567-9EAE-4121-973E-AF1EE514D728].Type[Employees]

   If string.IsNullOrEmpty(nameSchema) OrElse not nameSchema.Contains(".") then

   Continue For

   End If

   nameSchema = nameSchema.Split("."c)(1)

    

   dictRevStore.Add(nameSchema, elemRevStore.GetValue("Value").String)

   Next

    

   'put the revision date into the variables if available, else provide the revision data as 1900-01-01

   Dim lstVariables = new System.Collections.Generic.List(of String)()

   For Each elemVariable As IEntity In colVariables

   nameVariable = elemVariable.GetValue("Name").String 'e.g. dprRevisionDateEmployees

   nameSchema = string.Format("Type[{0}]", nameVariable.Trim().Substring(15)) 'e.g. Type[Employees]

    

   If dictRevStore.TryGetValue(nameSchema, variableValue) then

   values(nameVariable) = variableValue.Replace(" ", "T")

   Else

   values(nameVariable) = "1900-01-01"

   End If

   lstVariables.Add(nameVariable)

   Next

   values("OverrideVariables") = string.Join(";", lstVariables.ToArray())

   End If

2. Under 'Run Synchronization' select 'Parameters' tab and provide the below script under 'OverrideVariables'.

   If not String.IsNullOrEmpty(values("OverrideVariables").ToString()) then

   Imports System.Data.Common

   Dim sb as DbConnectionStringBuilder = new DbConnectionStringBuilder(false)

   For each varName as String in values("OverrideVariables").ToString().Split(";"c)

   sb.Add(varName, values(varName).ToString())

   Next

   Value = sb.ConnectionString

   End if

3. 'Commit to database' and then 'Compile database'.

Modifying the synchronization project

1. Make sure that the local cache is turned off for the Synchronization project.

2. Select the SCIM synchronization project and select 'Variables' to add a new variable 'dprRevisionDateEmployees' (the variable name should be dprRevisionDate<schema name>).

3. Create a new 'Schema Class' from Employee in the 'Target system'. For example: "Employees for Delta Sync".

4. On the Schema Class set the System Filter: meta.LastModified gt $dprRevisionDateEmployees$. Under 'Select Objects' tab, use 'meta_lastModified' as the attribute, '>' as the operator and $dprRevisionDateEmployees$ as the text field value.

5. As required, other supported attributes also can be added under filters.

6. Create a new Mapping using the new Schema Class dialog box.

7. Create a new Workflow using the new mapping. This workflow updates the existing records based on the revision filter.

8. To improve the syncs performance, remove the update steps from the existing default Initial sync Work Flow.

9. Create a new Startup Config using the new workflow. Select 'One Identity Manager' for the 'Synchronization in direction'. Use 'default variable set' for the 'Variable Set'.

10. Use hotfix #33601 for One Identity Manager version 8.1.2 and 8.1.4.

Connector limitations

• Pagination is not supported for Employees, Departments, LocationAddresses and OrgUnits resources.

• List response for Employees, Departments and OrgUnits return only xRefCode (ID).

• Meta attributes are not retrieved for Employees, Departments, LocationAddresses and OrgUnits resources.

• In absence of necessary access rights for the employee attributes EmployeeProperties and OrgUnitInfos at the Dayforce target instance, the Dayforce connector would need to make additional requests to retrieve these attributes which impact the Identity Manager synchronization performance.

• Dayforce generally applies rate limiting to the API requests. If a request exceeds the defined rate limit, the request is rejected with the HTTP status 429 - Quota exceeded for number of requests response.