In the first step of the Validation Process Flow tutorial, the Human Resources director at Sampco Holdings, Inc. requires that all Sampco employees be linked either to the parent organization or one of its subsidiaries but not to any inventory warehouses, which also appear as Organizations records. The director has requested validation logic to prevent users from linking any employee to an inventory warehouse.

In the data, Organization records 1 to 6 correspond to the parent company and its subsidiary while records 7 to 10 corresponds to warehouses.

Rather than write a field validation script for Employees. OrganizationID, the Sampco implementation team has decided to write a validation process flow to check that new employees are not linked to an Organizations record that corresponds to a warehouse location.

Outlining the Validation Process Flow

The first step in any process flow configuration is to outline the process.

How Many Steps?

To add this validation logic to Aptify as a process flow, you need to create a two-step process flow. When Employees records are saved within Aptify, the process flow must validate that the employee is not linked to a warehouse organization. So, the first step in the process flow will be to retrieve and test the value returned for the employee's organization.

The second step in the process is to display an appropriate Validation Message if the employee is linked to an inappropriate organization. (If linked to an appropriate organization, the process flow would end after step 1).

What Data Will the Process Flow Use?

The process flow will need to retrieve the Organization ID from the current GE object for the Employees record that is being saved.