1. Log in to Employment Hero.
2. Click the WorkFlows option on the left-hand side menu.
3. Click on the Browse Templates tab.
4. Select the Forms option.
5. On your chosen form, click on Quick setup.
6. Under Who does this apply to, select from the filters. For proxy submissions, this evaluates the Affected Employee's attributes.
7. Under Form is one of, choose from your organisation's forms.
8. Under Approval flow type, select your preferred sequence (Sequential, Parallel, or Any).
9. Under Approver type, select from the following (updated for Slice 2):
   • Primary Manager of Affected Employee
   • Secondary Manager of Affected Employee
   • Group Leader of Affected Employee Group
   • Your chosen team or direct employee.
10. Click on Quick set up and publish.

1. Log in to Employment Hero.
2. Click WorkFlows > Create New > Forms.
3. Click the WHEN this happens field and select Form submitted.
   Note: This trigger now targets the Affected Employee context automatically.
4. Click IF these conditions are met. Conditions will evaluate against the Affected Employee's data.
5. Click THEN do this and select Request Approval.
6. In the Primary Approvers section, use the dynamic selectors:
   • Primary Manager of Affected Employee: Resolves using the reporting lines of the subject of the form.
   • Secondary Manager of Affected Employee: Resolves using the subject's secondary manager.
7. If using Send Email Notification or Create Task:
   • Use Affected Employee tags to reference the subject of the form.
   • Use Submitter tags (e.g., submitter_full_name) to reference the person who initiated the form.
8. Click Save and Publish.

With the Slice 2 update, the Workflow Engine operates on an "Employee-centric" model rather than a "Submitter-centric" model:

• Execution Context: All triggers and conditions evaluate the Affected Employee's profile (Location, Team, etc.), not the person typing the form.
• Approver Resolution: If you select "Primary Manager," the system looks for the manager of the Affected Employee.
• Audit Trail: The Submitter is recorded as "Created By" for transparency, but they do not dictate the workflow path.

Ensure your workflow is configured to use Primary Manager of Affected Employee. If your workflow was created before the Slice 2 update, it may still be referencing the "Submitter." Edit the workflow to update the approver dynamic field to the "Affected Employee" variant.

Check your dynamic field tags:

• Use Submitter fields when you want to reference the person who initiated the request.
• Use Affected Employee fields when you want to reference the subject/target of the form.