Using Action Events (HCM)
You can use Action Events to send the form to a user when a trigger condition occurs in Sage People. This can be things like a team member starting employment or leaving employment.
Add the form to an action event pattern
-
In the HR Manager portal, go to the Action Event Patterns tab.
-
Select an action event pattern, such as Standard Action Events.
-
Select an existing action event that you want to use to send the form. Or select New to create a new one.
-
Select Edit.
-
In the HCM Form Definition field, click the search icon. Find the form definition you want to add to the event and select it.
-
Select Save.
To ensure that the form sends to and is accessible by the manager in WX:
-
On the Action Event, ensure you've populated the HCM Form in the HCM Form Definition. Also select Send to Manager is in the Recipient section.
-
On the Form Start email, make sure you check Send email to... To Manager.
-
On the Form Policies tab, ensure you select Manager Starts.
-
Create a Salesforce Flow to update the 'Concerning' field to the Team Member name.
Create the Salesforce Flow-
In the HR Manager portal, open the App Launcher and select Flows.
-
Select New.
-
Select Start From Scratch.
-
Select Record-Triggered Flow.
-
Under Select Object, search for and select the object: HCM Form (fHCM2__Form__c).
-
Under Set Entry Conditions:
-
For Condition Requirements, select All Conditions Are Met (AND)
-
In the Field box, search for and select the Concerning field (fHCM2__Concerning__c)
-
Select the Operator Is Null
-
For Value, select $GlobalConstant.True
-
-
Leave Optimize the Flow as Actions and Related Records.
-
In the Flow diagram on the left of the screen, select the Plus (+) node below the Start box.
-
In the Add Element box, select the Update Triggering Record shortcut.
-
In the Update Records panel on the right of the screen, enter a Label. For example, "Update Concerning Value".
-
The system generates an API Name from the text you enter automatically.
-
Leave the other settings in the panel at their defaults. In Set Field Values for the HCM Form Record, search for and select the Concerning field (fHCM2__Concerning__c)
-
For Value, construct a path to find the Team Member name. Type or select the following path:
{!$Record.fHCM2__Employment__r.fHCM2__Team_Member__r.Name}
-
Select Save and enter a Flow Label. For example, "Set Concerning Value for HCM Form". The system generates an API Name from the text you enter automatically.
-
Select Save.
-
To make the flow active, select Activate.
-
If some managers are still unable to see the form in WX, ensure that the Team Member name, User name, and Actor name are all in sync. Differences in the name can cause the form to not be visible.
Form action events
You can create action events to trigger notifications when users approve, reject, start or submit forms.
-
In the HR Manager portal, go to the Action Event Patterns tab.
-
Select an action event pattern, such as Standard Action Events.
-
Select New to create a new action event.
-
For the Event, select Form.
-
Select the event:
-
Approve
-
Reject
-
Start
-
Submit
-
-
Select the Email Template you want to use.
-
Select the HCM Form Definition that triggers this event.
- Complete the configuration for the action event by configuring conditions and recipients. See Creating an action event.
-
Select Save.
Action event email notification
You can select an email template for the system to send when the event triggers. If you configure both an email template in the action event and a form start email in the form definition, the system sends both emails. It sends them to the team member when the action event triggers.
The system only sends action events emails when the action event triggers. It sends form start emails in the form definition whenever the form triggers, whether manually or by an action event.
We recommend you use the Start email in the form definition. This allows the system to trigger notifications when the form sends. This can be either manually or when an action event triggers it, without duplication.





