Offboarding journey tasks assigned to AOR based on termination date is causing issues?
Summary:
Our offboarding journey tasks are assigned to AOR. The AOR is determined based on the termination date. When AORs are reassigned, the previous AOR record is automatically marked as inactive. This is causing our offboarding tasks to be assigned to the initiator when a termination is back dated. This is causing confusion for our users. We are trying to encourage our line managers to enter actions in Oracle, but they will not know what to do if journeys are assigned to them incorrectly. Has anyone else experienced this and if so, how did you work around it?
Content (please ensure you mask any confidential information):