1. Click the Workflows menu.
2. Click the Create New button.
   
3. Select the Onboarding option and click the Create New button.
   
4. Click the When field.
   
5. Complete the following fields:
   • When: 
     • Employee has completed onboarding setup.
     • Employee record created.
     • Employee has accepted contract.
     • Employee has been issued a contract.
     • Employee's start date is approaching.
6. Click the Save button.
   
7. Click the Conditions field.
   
8. Click the Add Condition button.
9. Complete the following fields:
   • Field.
   • Condition.
   • Value.
10. Click the Save button.
    
11. Click the Then field.
    
12. Complete the following fields:
    • Then:
      • Trigger onboarding checklist.
      •  Create task:
        • Name.
        • Description.
        • Owner.
        • Send this task to an email address.
        • Subtasks.
        • Due date.
        • When will this action be performed.
      • Create Microsoft account.
      • Create Google Workspace account.
      • Send email notification:
        • Type of recipients.
        • Subject.
        • Content.
        • When will this action be performed.
      • Create 1:1:
        • Meeting title.
        • Meeting template.
        • Time.
        • Remind type.
        • Subject.
        • Content.
13. Click the Save button.
    
14. Click the Save and Publish button.
    
    

    Helpful Hint

    To add an additional step, click the  button below the last step. You need to publish this workflow for it to become active.

    

1. Click the Workflows menu.
2. Click the Manage Workflows tab
3. Click Onboarding button.
4. Click the Three Dots button. 
5. Click the Publish button.
   

1. Click the Workflows menu.
2. Click the Workflows menu.
3. Click the Manage Workflows tab
4. Click Onboarding button.
5. Click the Three Dots button. 
6. Click the Unpublish button.
   

1. Click the Workflows menu.
2. Click the Manage Workflows tab
3. Click Onboarding button.
4. Click the Three Dots button. 
5. Click the Edit button.
6. Edit the workflow as needed.
7. Click the Save button.
   

1. Click the WorkFlows menu.
2. Click the Workflows menu.
3. Click the Manage Workflows tab
4. Click Onboarding button.
5. Click the Three Dots button. 
6. Click the Delete button.
   

The Employee File Change Workflows feature lets you create a set of steps that the HR platform will take regarding expense claims. Each step follows the When-If-Then sequence, which is like this:

• When this happens -> If this condition is met -> Then do this.
  • "When" is the situation that will trigger the workflow.
  • "If" is the condition that decides what action should be taken.
  • "Then" is the action that the platform will take.

To visualise this better, please see the examples below relating to expense claims. "X" and "Y" in these scenarios refer to values you can pick and enter on the HR platform.

1. When an employee submits an expense claim request, If the expense claim amount is more than "X", Then the request will be sent to the executive leadership team for approval.
2. When an employee submits an expense claim request, If the expense claim category is "X", Then the request will be automatically declined.
3. When an employee submits an expense claim request, If the expense claim currency is "X", Then the request will be automatically approved.
4. When an employee submits an expense claim request, If purchase start date is after "X" AND end date is before "Y", Then the request will be automatically approved.

When you click the "IF" field when creating a workflow, the "Add conditions" panel will slide out. There, you will have to fill in the following: Field, Condition, and Value.

Below those is the Add condition button, which lets you set up an additional condition to come with the first one. When you click this button, you will be asked to choose between:

• And condition: This means the platform will take action only if BOTH the original and additional conditions are met.
• Or condition: This means the platform will take action if EITHER the original or additional condition is met.

To demonstrate this, here are some examples:

 And condition:

For the image below, the platform will act only if the expense claim amount is over 5,000 and has a category of Miscellaneous. The platform will not take the specified action in the "THEN" field if both are not met, even if one of the conditions is followed.

 Or condition:

For the image below, the platform will take action if the expense claim amount is over 5,000 OR has a category of Meal Allowance. There just needs to be at least one condition met for the platform to act. So, the workflow will still function if two, three, or more conditions were met.

For our example, this means the workflow will act if the expense claim amount is over 5,000, even if it falls under a different expense category. The platform will also function if the request is under the Meal Allowance category, even if the amount is less than 5,000.