Workflow Best Practices
Avoid using Notification Activities
Notification Activities can be used to notify individual users or groups the events taking place in a Workflow. However, they introduce a degree of rigidity in terms of workflow definitions which should be avoided.
This is so for the following three reasons:
- Updating Notification Activities requires re-publishing the whole workflow
- Any Workflow(s) which are in flight will not update with the changes, and so the effects of the changes will not be immediate
- Your notification logic can become spread out in different areas of activities
The best way to avoid these pitfalls is to use a Workflow Event and trigger all Notifications from the Events table. This allows your notification logic to be centralised and decoupled from your workflow processing logic.
Timer workflow activity
The Timer activity pauses the workflow for a specified period of time. If there are many timer activities in a workflow, its execution time can be very long.