Employee Workflows and Multiple Companies

Use workflows to send automated alerts or emails, or to trigger additional actions, when an employee-related action take place. Certain rules apply in a multiple company environment.

You can configure two types of workflows for use in a multiple company environment:

• User Initiated: These workflows are based on events that occur in the hubs and other applications.
• Scheduled: These workflows are based on queries that run at regular intervals via the process server.

When you track multiple companies. additional columns and conditions are available for use in creating a workflow that is related to an Employees hub record. The Column options are prefixed with EMAllCompany because the conditions look at all company records for an employee unless you add further restrictions.

For example, you can select EMAllCompany.Company as the Column and set the Operator to Is Home Company to have the conditions look only at the employee's home record. Or you can set the Operator to Is Not Home Company to look at all company records except the employee's home company.

When you associate an employee with a new company, you create a new employee record in the new company. This action triggers workflows with the Insert/Associate Workflow Type. These workflows fire when a new employee record is inserted or an existing employee record is associated with a new company in the Employees hub. DPS treats the new "associated" record as a brand new record.

Any other workflows that would normally fire when you change an existing employee field do not fire when you associate an employee with a new company.

For example, if you have a workflow set to send an email when an employee address changes, this email will not be sent if you associate an employee with a new company and then change the employee's address. In this case, DPS treats the record's Workflow Type as Insert/Associate, not Change.