Best practices for avoiding hard-coded usernames in Purchasing Approval Conditions

Hi everyone,

The Purchasing team is looking for a more dynamic way to manage approval routing in the Manage Purchasing Document Approvals setup. Because they frequently move people into different roles, they want to avoid hard-coding specific usernames into the rule Conditions.

Since Approval Groups cannot be used in the Conditions section (only Actions), I wanted to reach out and see how others in the community handle this. What attributes or strategies have you used to keep your Conditions dynamic and avoid hard-coding users?

Thanks in advance for your insights!