To help with config and system maintenance, it would be better if we formed the approver tag journey first e.g. Line Manager < Head Teacher and then selected from a drop down list that we would like to apply this to reasons. Would save time, speed things along and make the system feel less clunky.
This is because currently we have to create all General Absence Reasons and then repeat the approver tag journey over and over again. This can be laborious if you are working with a large trust with lots of general absence reasons
Hi Lewis, my understanding from reading this is the control over application of an approval route and approver tags would be better being pulled out from the reasons? Making it easier to manage and setup? I assume this would also include distribution of the tag to jobs as well?