Two different approval workflow for same Action Reason - Change Assignment

Summary:

Content (please ensure you mask any confidential information):

We have a requirement to create an approval workflow for Line Manager. So when a line manager submit a change assignment transaction (with custom Action - Extend Projected End date) it needs to follow below path :-

Management Hierarchy (Manager’s immediate Line manager)->HRBP(Representative)->FD Representative->Workforce Manager (Application Role)

The above configuration works for most of the cases, however, in our client’s organization we have some employees (Executive Directors, CEO) which they identify as L1 Managers and if their direct reports raise a change assignment transaction then the approval workflow should not be triggered to Line managers (i.e. it should skip management hierarchy) and continue the rest of the approval process.