Flows
What are Flows?
Salesforce Flows extend standard product functionality in Sage People by collecting data or performing actions. Flows offer more options than Salesforce Workflow Rules or Process Builder and can replace functionality you developed with those tools.
Salesforce blocked the creation of new Workflow Rules in their Winter '23 release. They also blocked the creation of new Process Builder Processes in their Summer '23 release. For new automation tasks, you need to use Flows.
A Salesforce Migrate to Flow tool is available for existing Workflow Rules and Process Builders. If you use the tool, you must validate output before activating in a production environment. For more information, see Migrating from Workflow Rules and Process Builder to Flow and Migrating to Flows: Process to follow.
Salesforce ended support for Workflow Rules and Process Builder at the end of 2025.
How are Flows used in Sage People?
Salesforce Flows includes a full software development environment, that Sage People uses to automate parts of the application. Each Flow works as a mini-application, automating a process by collecting data and doing something with it. Sage People uses Flows extensively in Candidate Experience Portal, and increasingly across all Sage People applications.
How can I use Flows in my org?
Salesforce provides extensive training and support content for Flows. Sage People recommends using that material to build your knowledge and help you use this powerful feature set. In addition, Sage People provides a Flows Basics training module that we designed to help bring you up to speed on using Flows with your Sage People content.
Remember that Sage People needs to ensure your org remains supportable. It does this by minimizing changes to the way the system operates, and by avoiding conflicts with the functionality we deliver. You can create your own Flows to work with Sage People features and deliver:
-
An update to a field on the same object
-
An update to a field on another object
-
An email alert
-
A custom Action Event
Supported Flow Types are:
-
Record triggered
-
Scheduled
-
Autolaunched, if constructing a sub-flow
Supported elements are:
-
Action, for custom Action Events
-
Assignment
-
Decision
-
Send email alert
-
Update record
-
Update triggering record
If you're planning to use a Flow to update a record, ensure the field isn’t a key field for Sage People delivered functionality. Fields you add for your own implementation and text fields are safe to update.
If these guidelines don't cover the Flows you’ve planned, contact your Customer Success team. Make sure Sage People can continue to provide you with support for your org.
Learn more
The following resources from Salesforce and Sage University provide more information about Flow terminology, concepts, and setting up Flows:
-
Trailheads:
Flow examples
For examples of Flow configurations, see the following topics:
-
Example: Populate Preferred Name with First Name. An example of using a Flow to populate a field with the value of another field within the same record
-
Example: Update the Hire Date field with Employment Start Date. An example of using a Flow to update the value of a field in one record with the value in a related record
-
Example: Send an email alert to HR team. An example of using a Flow to send an email alert
-
Creating a custom Action Event. An example of using a Flow for a custom Action Event email notification
Icons used in Flow Builder diagrams
Flow Builder displays the Flow as a diagram. Flow Builder includes screenshots of the Flow diagram in the Flow examples. We've listed the standard icons linked by connectors here in alphabetical order:
| Icon | Description |
|---|---|
|
|
Assignment: sets values for variables. |
|
|
Create records: uses a value from the Flow to create a single record, or uses a record collection variable to create multiple records. |
|
|
Decision: evaluates conditions and uses the result to direct users through the Flow. |
|
|
Delete records: identifies records for deletion by specifying conditions or by using IDs stored in a variable. |
|
|
Email Alert: sends an email |
|
|
Get records: find records meeting conditions and store values in variables. |
|
|
Screen: collect information from users or show information to users. |
|
|
Subflow: launch another Flow, known as the referenced Flow. |
|
|
Update records: identify records to be updated and set the values to change. |