We setup a position creation workflow in the system where there are 3 approver steps.
The first step is the Management Forum Member who needs to approver (=custom manager).
All approvers are setup with respect permission=yes.
However, when doing several tests, we notice that the view for the first approver is different depending on the start date of the position.
Reproducing the Issue
Position request where Approver needs to approve Position with effective date: (in the future)). Here only 7 fields are visible, coming from the 'Employee - Public view' role.
Position request where Approver needs to approve Position with effective date: (today or in the past)). Here all the fields are visible as expected, as per setup of the role of EC Manager.
The permission of EC Manager role should always to see more than the 7 fields of the employee - public view role.
1- Why is the view different depending on the effective date of the position request?
2- How can we workaround this, without setting the 'respect permission' to no in the workflow or the switch the access in the EC Manager role to 'all positions' instead of restricted.
The EC Manager's target population is defined as hierarchy of the user's position.
The current configuration is not yet supported for future position visibility, it cannot be included in the hierarchy of the login user.
So for a future Position the EC Manager role is not applied actually.
As a workaround you can change the target population of this role to ALL to make future Position work.
Future position Target population Respect permissions , KBA , LOD-SF-EC-RBP , Roles & Permissions (EC Core only) , LOD-SF-EC-POS , Position Management , Problem