Overview
Notifications in Risk Cloud can only be sent to users referenced in user fields within the workflow where the job is triggered, or from workflows that are directly linked to it. This means that cross-workflow notifications have specific limitations depending on how your workflows are connected.
The limitation
If there is no direct link between Workflow A and Workflow C, you cannot send a notification directly to the owner in Workflow A when Workflow C is completed.
Why this happens
Each workflow operates within its own context. Notifications are scoped to the users and fields available in the triggering workflow or its directly linked workflows. Without a direct relationship between Workflow A and Workflow C, the system has no way to reference the owner field in Workflow A from within Workflow C.
Workarounds
Consider the following options to achieve cross-workflow notifications:
- Create a direct link between the workflows. If your process allows it, establish a direct relationship between Workflow A and Workflow C. Once linked, user fields from Workflow A become accessible for notifications triggered in Workflow C.
- Use a shared intermediary workflow. If a direct link is not feasible, consider routing through a workflow that is linked to both Workflow A and Workflow C. This intermediary can carry the notification to the appropriate owner.
- Manually notify the owner. As a fallback, configure a step in Workflow C to prompt the assigned user to manually notify the Workflow A owner upon completion.
Need more help?
If you're unsure how to link workflows or need guidance on your specific setup, contact LogicGate Support and include details about your workflow structure.