HR flows and triggers

  • Versão de lançamento: Australia
  • Atualizado 12 de mar. de 2026
  • 1 min. de leitura

    • HR flows created in Workflow Studio use natural language to automate approvals, tasks, notifications, and record operations without coding.

    Three new flows are available to automate the triggering of Lifecycle Events. The triggers are based on changes in the HR Profile [sn_hr_core_profile] or Job [sn_hr_core_job] tables. These flows reduce or eliminate the need to write business rules to trigger Lifecycle Events.
    Nota:
    Customize these flows to use in other Lifecycle Events other than on boarding events.
    The following flows are installed with the Human Resources: Core application. These HR flows are deactivated by default.
    New Hire on Boarding Case Trigger HR Profile

    The trigger is based on the employee's start date in the HR Profile Table [sn_hr_core_profile]. If the employment start date is at or after today, the flow creates an HR Onboarding case. This flow runs every time an HR profile is created or updated.

    For more information about the HR Profile, see Employee Profile table and HR Profile.

    New Hire on Boarding Case Trigger Job

    The trigger is based on the employee's start date in the Job Table [sn_hr_core_job]. If the employment start date is at or after today, the flow creates an HR Onboarding case. This flow runs every time an HR profile is created or updated.

    For more information about the Job Table and related profile records, see Capturing multiple job records for a user.

    Case Trigger Custom Condition
    Table: HR Profile [sn_hr_core_profile]

    This flow can be used as a template to create a customized trigger. The trigger is based on a custom date check for the employee start date. The default trigger is initiated two days prior to the employee start date. For more information about flows and triggers, see Flows.

    These flows create an HR case adding an entry in the HR Lifecycle Events Case [sn_hr_le_case] table. If multiple flows are active at the same time, there is a high probability of creating duplicate records and cases.
    Nota:
    Only one of these flows should be active at any given time for a particular lifecycle event.