Catch workflow configuration errors before they go live
Also listed as: Enforce BPM deployment validations
What is it?
Xelence will check a workflow for configuration errors, such as a send step with no template set up, before it can be deployed.
Why does it matter?
A configuration mistake may only show up when a live case reaches the faulty step, disrupting staff and constituents.
Fewer workflow failures in production, and problems found while they are still cheap to fix.
Getting it into your solution
- Needs an upgrade to the Xelence release
Start thinking about
- Have workflow configuration errors reached production in your environment before?
- Who in your team deploys workflows, and what checks do they run today?
- When would a move to Xelence 10.0 fit your release calendar?
Terms used on this card
- Business process management (BPM)
- Designing, automating and tracking the steps of a business process, such as who approves what, and in what order.