Note: This guide only describes the product’s configuration requirements. It assumes that you already reviewed the information in the Dayforce Web Services Introduction Guide, which provides a description of current Dayforce Web Services features.
Moreover, developers who will create code to interact with the Dayforce Web Services API should see the Dayforce RESTful Web Services Developer Guide.
The following topics are covered in the Dayforce Web Services Configuration Guide:
Note on terminology: The term "consumer" is used throughout this guide to refer to any external application that a client builds to use the Dayforce Web Services API. While reviewing this content, keep in mind that one client might have multiple consumers, and one consumer could be used by more than one of the client's systems.
Configuration Guidelines
To ensure that access to features and data isn’t compromised by configuration changes made for web services and vice-versa, you should observe the following guidelines:
- User accounts, roles, report definitions, etc., used for web services should be configured specifically for use with a given consumer. This means that existing items shouldn't be reconfigured to support web services, and, once created, web services items shouldn't be attached to existing roles.
- Separate user accounts, roles, etc., should be configured for each web services consumer, allowing a greater amount of flexibility as our features and client use of web services become more complex.