1. TRANSITIONS
- Allow External Users To Transition is set appropriately. (Including on post-Decision Type steps)
- Set Submitted Date function is always done before creating a CoR
- All the transitions from a step are in the most intuitive order you can think of. If the same transitions (or set of transitions) exist on another workflow, then use the same order. This may mean reordering the transitions when adding new ones. Always check the order in an actual activity so you see what the menu looks like.
- Add a transition description if needed. If staff may be confused by when/why to choose the transition or need to know what will happen, then add a description. As Brief As Possible. They clutter up the menu, so they should be reserved for necessary information.
...
- Checkbox Data Prompt with the PIN request order is 2
...
- YouMUST set the transitions that should show the prompt. It will show up for all of them if this field is not set.
- Once you test a Data Prompt,it cannot be deleted. To get rid of it you have to replace the entire step that it’s on.
4. CROMERR COMPLIANT - TRANSITIONS
...
- Run through a real-world example as an external user and an internal user (use different browsers so that you can do this with both screens open at the same time.
- Test every transition and step at least once.
- Make sure the language displayed in the external activity overview fits in the standard size view and the user is shown what’s happening and what’s expected of them.
- Check all of the new notifications and check that they display well in the notification bell and in email. Is it listing the Status that you want it to? Note that triggers can be set to 0 days and you can go to Operations>Processes click Run Process and pick Run Workflow Triggers to test if a trigger is working as expected. That process is running at midnight every day. Remember to set the number of days back to what it should be after testing.