To configure Dayforce for web services use:
- Identify the web services consumers that need to be set up.
- Determine which web services features each consumer will use.
- Identify the data elements required by each consumer.
Identify Consumers
A good process for identifying web services consumers (defined above) is to:
- List all of the client systems that will receive or retrieve data from Dayforce.
- For each system identified in step 1, note the application that will be used to interact with Dayforce Web Services. This will likely be a new client application built (or existing application updated) specifically for Dayforce integration.
- The list of applications noted in step 2 are the consumers requiring configuration in Dayforce.
Determine Which Features to Use
See the Dayforce Web Services Introduction Guide for a description of each available Dayforce Web Services feature and information about each feature’s intended use.
Identify Required Data Elements
If any Dayforce web services other than Get Report Data
requests are used by a consumer, the consumer must have field-level access defined. To determine which fields a consumer requires, all systems that the consumer interacts with should be considered, and the cumulative list of data elements will likely be what is required for the consumer
For a complete list of fields available for field-level access configuration, see the “Appendix – Data Elements Available in Get Employee Requests”. It is helpful to note both the field name and the associated access authorization given that both aspects need to be configured.