Classic | Creating a Workflow Path

Classic | Creating a Workflow Path


The Company Workflow Setup Screen allows you to create rules for workflow items to move through a defined number of approval steps. Examples of workflow items are Claim Components, Employee Requests and Leave Applications. These workflow items need to be set-up before the workflow path can be created. Once the workflow path has been created, the workflow item is submitted via the Employee Self Service Portal.

Please note: Click on any image in the article to enlarge.

NextGen or Classic

The Classic version is the name given to the previous look and feel of the system. Important to note, both NextGen and Classic point to the same database. No data migration is therefore applicable. 

This article covers Creating a Workflow Path for the Classic version of the system.

An Example of the Classic Landing Page

The article that explains the same for the new and improved NextGen version, is coming soon.

An Example of the NextGen Landing Page


This feature is available on Master.
Please note: Basic Workflow Functionality that limits you to a 1 Step Approver-Workflow for a Claim Item, is available on Premier.

Navigation:Company Menu>Configuration>Workflow Configuration


Workflow Company Settings

Navigation:Company Menu>Configuration>Company Settings

Examples of Workflow Items submitted via a Workflow Path on ESS

Important Comments

  1. Workflow paths can be created per Leave Type or Leave Scheme.
  2. Workflow paths need to be configured for each Employee Request and Claim created.
  3. The last step of a workflow path should always be Commit.
Workflow Roles
Should you want to apply Workflow Roles, the roles should be created before applying it in a workflow path.  One option exists to access the Company Workflow Roles Screen.

Navigation: Company Menu>Configuration>Company Enumerations>Workflow Roles

Once the Workflow Role has been created it will have to be linked on the Employee Position Screen.
Based on Workflow Role, Region or Security Role
Should you select, for example, Region to base the workflow path on, it is advisable that a workflow path for every Region created on the payroll, is configured.  The same principal applies when basing a workflow path on a Workflow – or Security Role.

You may also be interested in

    • Related Articles

    • Classic | Set-up of Leave for Workflow Paths

      About When approving leave applications, the system offers a default workflow path from the employee to the directly reports to person on Premier and Master Payroll Edition. Should the user want to accommodate more levels of authorisation, a workflow ...
    • Classic | Set-up of Employee Requests for Workflow Paths

      About You can create Employee Requests to formalise and simplify processes in the company. An employee request is a workflow item which requires approval. It will, however, not have a direct impact on the employee’s payslip. Employee Requests need to ...
    • Classic | Set-up of Claim Components for Workflow Paths

      About Certain components that have been added on the Company Payroll Component Screen can be configured as a Claim Component. Examples of Claim Components include the reimbursement of kilometres, subsistence and overtime. Claim Components need to be ...
    • Classic | Maintaining Security Roles

      About Once a Security Role has been added, you will need to specify the access required on screens and/or fields within the system. Please note: Click on any image in the article to enlarge. NextGen or Classic The Classic version is the name given to ...
    • Classic | Creating Pay Rate Categories

      About Pay Rate Categories link a defined pay rate value to an employee. Once you have created the categories, it is linked on the Employee Pay Rate Details Screen. When adding a new employee or applying an increase, the package will default to the ...