Targeting the Ceridian Dayforce system
For each Ceridian Dayforce system, add a target system in Bravura Security Fabric (Manage the System > Resources > Target systems):
Type is Ceridian Dayforce
Address uses options described in the table below:
Options marked with a 
are required.
Option | Description |
|---|---|
Script file: | The pre-set agtdayforce.py script file used by the Dayforce connector. (key: script) |
URL: | The domain name URL for the Dayforce server. This is used for API calls other than authentication. (key: server) |
Authentication URL: | The domain name URL for the Dayforce authentication server. This is used for API calls that are specifically for authentication. (key: authServer) |
Company ID: | The Company ID on the Dayforce server that will be used to target. (key: companyId) |
Expanders to use for listing: | This is a comma-separated list that is used for additional fields to use to query on for details when listing. Example: "WorkAssignments,Contacts". See here for more information regarding Dayforce API documentation for possible expanders. (key: expanders) |
Numbers of threads to use for listing: | Specifies the number of threads. If no value is specified then three threads are used when listing. Dayforce can scale how many servers they have available for handling API calls so this option will allow to increase the number of threads to make use of them. However note that Dayforce does aggressively rate limit their API calls and significantly surpassing their rate limits can lead to exponential delays and potentially the server that runs the connector being temporarily IP blocked by Dayforce. See here for more information. (key: threads) |
Trace Logging: | Provides detailed multiline logging for connectors. Default is None. Other options include Low, Medium, and High. (key: trace) |
The full list of target parameters is explained in Target System Options.
The Trace Logging option provides detailed multi-line logging for the connectors and exposes a way to engage trace logging to a file. Trace logging are things that are generally multi-line such as input/output kvg options, http request/response data, and generally verbose data for diagnosing and troubleshooting issues. It provide a simple mechanism to redirect multi-lined information to an output file.
A trace log file is created within the <Program Files path>\Bravura Security\Bravura Security Fabric\Logs\<instance> directory and has a format of trc-<connector-name>-<unix-time>-<process-id>.log.
The Trace Logging option can be found in the advanced section when modifying the target system address configuration page for individual target systems. It can be set to the following values:
None | Default value. Log no trace information and no trace log file is created. |
Low | Contains kvgroup data for the Input KVG and for the Output KVG. |
Medium | Telemetry data for Http Post/Get request/response data. |
High | Not yet used, to be implemented in a future release. |
(key: trace)