You might want to look into java actions for this as the on change action is ‘hard coded’. The mapping is set in the MF and can’t be influenced at runtime. Maybe with some actions to find the changed member (community commons) and some splits you would be able to implement this in a MF, but maybe some more flexibility is available when implementing this in a java action.
Erwin 't Hoen
Not certain, but this might work:
Create 4 different specializations of Approver each for one type of sales person. No extra attributes.
Create 4 different specializations of Approver each for one type of financial person. No extra attributes.
Connect the associations to theses specialization entities. Now your microflow, which still takes the generalization as the input parameter, can know what type of entity called the microflow.