Workflows and Employee Multicompany

Workflows allow you to create conditions for which you want alerts or emails to be sent or for which you want other actions to be taken. With Workflows, you can automate the process of being alerted each time a specific action takes place.

There are two types of workflows that you can configure for use with Multicompany:

• User Initiated — Use these workflows to specify conditions for events that occur in the Info Center, as well as other applications that automatically trigger actions.
• Scheduled — Use these workflows to create queries that run at regular intervals via the process server.

When you use the Multicompany feature and you create a workflow that is related to an Employee Info Center record, there are additional columns and conditions available for use. 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 only look at the home company record for an employee. Conversely, you can set the Operator to Is Not Home Company to look at all company records except the employee's home company.

With Multicompany, a user may associate an employee with a new company. This is like creating a new employee record in the new company, so the Insert/Associate Workflow Type will fire when a new employee record is inserted or an existing record is associated with a new company in the Employee Info Center. Vision treats the new "associated" record like a brand new record. Any other workflows that would have fired from a change to an existing employee field will 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 is changed, you associate an employee with a new company, and you then change the employee's address, the workflow to send the email would not fire. In this case, Vision treats the record's Workflow Type that you set on the User-Initiated Workflows grid as Insert/Associate, not Change.