Announcing the Global SNUG Board of Directors. Learn more here
10-24-2022 02:45 AM - edited 04-16-2024 04:08 AM
Workflow Automation CoE > Playbooks > Best Practices
When creating new process definitions, keep track of existing business logic like flows and business rules triggering at the same conditions (e.g., categories, types, states,…) that run potentially conflicting logic.
Flow Designer is the tool of choice to automate self-contained units of logic, always keep reusability in mind. While you can use flows to power your activity definitions, we recommend using subflows and flow actions instead, because they allow you to specify inputs and outputs, which simultaneously serve as activity inputs and outputs.
When creating declarative actions for activity definitions that may be used in other processes as well, don’t script visibility conditions based on activity/lane names. Base the conditions off of record fields instead (e.g., state, category,…). The same rule applies to lane or activity conditions as well.
This will be specifically important with the (new in Tokyo) copy process feature. Once you start copying and adjusting an existing process definition to another process’ needs (for example by renaming lanes), you may run into issues down the line if you don’t heed this recommendation.
Optional activities allow your processes to be more flexible and meet real agents’ daily requirements. Processes will not always follow the prescribed path and there will inevitably be unforeseen detours. With optional or adhoc activities you allow your agents to still follow the playbook on a high level, while accounting for situations that require a more flexible approach.