Create Subscriptions for Each Subscriber

Dayforce Web Services Configuration Guide

Version
R2024.2.0
Create Subscriptions for Each Subscriber

Dayforce contains a list of Notification Events (including Hire, Rehire, Termination, Workflow Validation, and their associated Cancel events).

The combination of Notification Events and Subscribers are called Subscriptions. As of version 7.47, consumers receiving notifications should have subscriptions for all events to ensure they're notified of data changes properly.

Cancel Events

It's up to the consumer to decide whether they take action based on a given Event Type. This is important to note because Dayforce Notifications include Cancel events that alert the consumer if a transaction has been reversed.

For example, if a New Hire occurs, the Dayforce notification publisher sends a notification to the consumer. If that Hire is then deleted or terminated as a way of canceling it with Dayforce, the Dayforce notification publisher sends another transaction to notify the consumer of this change. In this scenario, both Hire Cancel and Termination can be considered cancel events for the Hire event, and as such, both must have Subscriptions.

Configuration

Subscriptions appear in the data grid in the lower panel of the UI, however they're not added or edited within the grid.

Subscriptions list.

When you click New or click an existing subscription record, the Subscription dialog box opens, which you can use to create a grouping of events. The subscription must have a name, a start date, and at least one event. As noted above, in version 7.47, it's best practice to include all events in the subscription.

Subscription pop-up window.

Important: As changes are made in each field of the Subscription dialog box, they're reflected in the Subscriptions feature. The information is committed to the database when you click Save. Some fields aren't enabled in the Subscription dialog box after the subscription is saved. This is because the Notification Publisher might have previously or might be currently processing the notifications for the subscription based on the existing configuration.