These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Workflow Automation Engine
- Who it's for
- Shared services
Shared services
A shared services group may run similar automations for several organizations. Keep each definition tied to its organization, owner and connector. That relationship lets the group review the right policy and connection context before executing a revision. The same team can use common operating practices while preserving the source and decision trail for each organization.
How Workflow Automation Engine is set up for you
Assign responsibility
People records identify the owners, reviewers and follow-up assignees. Each definition carries its own owner and organization.
Review per revision
Validation writes a run trace and opens a pending decision. The Reviewer records a decision for that source revision rather than a blanket approval of later edits.
Trace outside actions
A run and its steps carry the operation key, result reference and external receipt details needed to investigate a service call.
Follow corrections
The correction workflow retains the earlier revision and creates a successor, with a follow-up assigned for verification.
A shared services group may run similar automations for several organizations. Keep each definition tied to its organization, owner and connector. That relationship lets the group review the right policy and connection context before executing a revision. The same team can use common operating practices while preserving the source and decision trail for each organization.
Start with one organization and one connector before extending the process to another group. Use a source request that can be checked in the provider system. Ask the Automation Owner to validate a revision and the Reviewer to inspect the step trace. The Operations Operator then checks the first result and a failed attempt. Record a correction and verify its follow-up. Compare the records across teams to confirm that ownership, evidence and provider context stay clear when work passes between people.
Before expanding, agree how each organization names its source records and who maintains its connector policy reference and field mappings. A shared procedure should still identify the person who can decide on a reviewed revision and the person who can reconcile an uncertain outside result.
[Prepare access](/workflow-automation-engine/roles) and [plan implementation](/workflow-automation-engine/implementation).
Features to start with
Roles on the team
- Admin
- Owns organization setup, access and connector configuration.
- Automation Owner
- Prepares definitions and follows their results and corrections.
- Reviewer
- Makes the independent decision on a validated definition revision.
- Operations Operator
- Starts reviewed runs and investigates attempts and receipts.
- Integration Steward
- Maintains the connection and field mapping context for outside services.
- Audit Reader
- Reads decisions, state changes, evidence and execution traces.
Set up Workflow Automation Engine your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.