Follow-up to #99694. On hold until the multiple approvesTo project is done (at least Release 1).
Problem
Today, to change one person's approval workflow, an admin has to update the workflow for everyone who shares the same approver. If a manager has 10 direct reports, the admin must remove the other 9 from the workflow just to change one person's approver. That's confusing and risks unintentionally changing the workflow for other members.
Proposal
When opening a member's details in the RHP:
- Display
Expenses for only that member, so there is no right caret to edit this information.
- Allow the admin to change both the first and second approvers.
If those changes match an existing workflow, add the member to that existing workflow. If they don't, create a new workflow for that member. For example, a member could have the same first approver as another workflow but a different second approver.
That way, admins can manage each member's approval flow individually.
Hold
Blocked on the multiple approvesTo project.
Reported in Slack.
Follow-up to #99694. On hold until the multiple
approvesToproject is done (at least Release 1).Problem
Today, to change one person's approval workflow, an admin has to update the workflow for everyone who shares the same approver. If a manager has 10 direct reports, the admin must remove the other 9 from the workflow just to change one person's approver. That's confusing and risks unintentionally changing the workflow for other members.
Proposal
When opening a member's details in the RHP:
Expenses foronly that member, so there is no right caret to edit this information.If those changes match an existing workflow, add the member to that existing workflow. If they don't, create a new workflow for that member. For example, a member could have the same first approver as another workflow but a different second approver.
That way, admins can manage each member's approval flow individually.
Hold
Blocked on the multiple
approvesToproject.Reported in Slack.