HR events allow you to associate submitted forms with one or more workflows that are triggered when the submitted form is processed.
You can configure HR events in Workflow Administration > HR Events.
There are two types of HR events:
| Type | Description |
|---|---|
|
Custom |
Custom events are generated when a triggering form is submitted, and the transactions are approved. Custom HR events cannot be generated by background job. You can add, edit, and delete custom HR events, and Dayforce comes configured with four of them. |
|
Template |
Template (or system) events can be generated by running the Benefits HR Event Generator background job, updates to certain employee properties, or the approval of triggering forms. You can’t add new template HR events, and usually you can’t edit their basic settings, but you can configure them with triggering forms or triggered workflows. Dayforce comes configured with 21 template HR events. Like custom events, if you want Dayforce to perform any tasks as a result of these HR events being generated, you must associate them with triggered workflows. You can also associate template events generated by the background job with triggering forms. Best practices for configuring these events are described in Template HR Events. Note: If Dayforce generates an HR event for an employee because a submitted form was processed, the event isn’t generated again for the employee by the Benefits HR Event Generator background job. |
The HR Event table in the database contains each generated HR event record, and each record reflects the event type and event date. When Dayforce generates an HR event, the associated triggered workflow is initiated immediately.
Note: You can also configure the HR Import to generate certain HR events. See Events Triggered by HR Import.
The most common use of a triggered workflow is to initiate the benefits recalculation process using the Benefits Enrollment object in the workflow. For example, benefit elections need to end upon termination of employment. You can use an HR event to trigger the benefit recalculation when the termination form has been submitted and processed as illustrated by the example that follows.
Configure a workflow with a Benefits Enrollment object:
Associate the appropriate HR event with triggering forms:
If you have any custom (rather than default) forms that you are using as part of a workflow, make sure to use those ones in your HR event configuration. Any changes you make to a form, including the name, are reflected in the Triggering Forms section.
Lastly, associate the HR event with the workflow that you configured:
Now, when the configured termination forms are submitted, both the workflow to complete the termination and the benefits related workflow are triggered, because you associated the form with the HR event. If more than one workflow is associated with the HR event, the workflows are queued and executed sequentially.
Additionally, when the HR event is triggered, Dayforce calculates employee benefit eligibility and employees are presented with an enrollment if they are newly eligible for benefits on the event date. See Benefits Enrollment Node.
If you want employees to be able to declare an HR event by submitting the Life Event Declaration form, the Employee Declarable checkbox in the General section of the event configuration allows you to enable that functionality:
When the checkbox is selected for an event, Dayforce shows the event in the Life Event drop-down list in the form. If you make an event employee declarable, you must add a triggering form for it, and it’s recommended that you enter a description for the event because that description is also shown in the Life Event Declaration Form.
You can select this checkbox for all custom events and the following five template HR events:
- Dependent Added
- Dependent Disability Status Changed
- Dependent Ended
- Dependent Student Status Changed
- Dependent Tobacco Usage Changed
For these template HR events, you can also update the default description, unlike other template HR events.
Important: If any template HR events not in the list above were configured to be employee declarable prior to updating to Release 57, Service Pack 2, then the Employee Declarable checkbox and the Description field are both editable. However, if you clear the Employee Declarable checkbox and save the event, those fields will become read-only, and you will not be able to make the event employee declarable again, as is the case with other template HR events. It is recommended that you do this for any template events not listed above to avoid having employees trigger Life Event Enrollments for events that aren’t intended to have this effect.
There are 21 template HR events, and the following table lists these HR events and their cross-reference codes.
| HR Event | Cross-reference Code |
|---|---|
| Address Changed | AddressChanged |
| Age Changed | AgeChanged |
| Assignment Changed | AssignmentChanged |
| Benefit Compensation | BenefitCompensationChanged |
| Dependent Added | DependentAdded |
| Dependent Address Changed | DependentAddressChanged |
| Dependent Age Changed | DependentAgeChanged |
| Dependent Disability Status Changed | DependentDisabilityStatusChanged |
| Dependent Ended | DependentEnded |
| Dependent Student Status Changed | DependentStudentStatusChanged |
| Dependent Tobacco Usage Changed | DependentTobaccoUsageChanged |
| Employee Property Changed | EmployeePropertyChanged |
| Employee Tobacco Usage Changed | EmployeeTobaccoUsageChanged |
| Employment Status Changed | EmploymentStatusChanged |
| Job Application Status Changed | JobApplicationStatusChanged |
| Marital Status Changed | MaritalStatusChanged |
| New Hire/Rehire | NewHireCompleted |
| Number Of Days Since Hire | NewHireXDays |
| Payroll Qualification Reached | PayrollQualificationChanged |
| PPACA Override Date Changed | PPACAOverrideDateChange |
| Spouse Coverage Verification Changed | DependentOfferedCoverageChanged |
| Years of Service Changed (Hire Date) | YearsOfServiceChangedHD |
| Years of Service Changed (Original Hire Date) | YearsOfServiceChangedOHD |
| Years of Service Changed (Seniority Date) | YearsOfServiceChangedSD |
Important: If, in a release prior to Release 57, Service Pack 2, you created custom HR events using any of the same cross-reference codes as in the list below, those HR events are considered template events and are shown in the Template section of the left sidebar going forward.
For more information on each of the template HR events, see Template HR Events.
Dayforce comes configured with four custom events that can be edited (including their cross-reference codes) or deleted. Typically, these events are set up to be triggered by the Life Event Declaration form. The following table lists these events along with their default cross-reference codes.
| HR Event | Default Cross-reference Code |
|---|---|
| Dependent Gained Coverage | DependentGainedCoverage |
| Dependent Gained Medicaid | DependentGainedMedicaid |
| Dependent Lost Coverage | DependentLostCoverage |
| Dependent Lost Medicaid | DependentLostMedicaid |
The following topics describe how to configure HR events: