Currently if an AM User leaves you are unable to replace them as the requestor for any actions and any responses to these actions are directed to a User who is potentially no longer in the system. The workaround is to re-allocate the User email to someone else who is then required to log-in as the previous User to change the status of the actions. When a historical User has generated a lot of actions, following this process is very long-winded, frustrating.
Giving Administrators the ability to reallocate the 'requetor' to another User (the next person taking up the vacancy) would allow the action to be seamlessly handed on without the unnecessary workaround.
Totally agree, We are facing the same problem. The inability of an administrator or someone with the right access permission to manage actions is a major draw back and potentially adds significant workload in managing these actions.