Insight on TransitionInitiatingAction?

michael-anastasia

Good morning, 

When setting up a Transition Program under Transition Management, you can set the Initiating Action that kicks off that program. Defining on that field brings you to a unique business class, TransitionInitiatingAction, where we see values like this: 

Transition Initiating Action	Type
ACCEPT OFFER	Candidate
ADD ASSIGNMENT	Resource
HIRE	Resource
PROMOTE	Resource
REHIRE	Resource
RESIGN	Resource
TERMINATE	Resource
TRANSFER	Resource

And, obviously, I know what these pertain to. What I'm been spending hours trying to figure out without luck, however, is where precisely these are calculating/how they're specifically working. I've been all through the LPL of TransitionTask, ResourceTransition, ResourceTransitionTask, TransitionProgram, TransitionCongifuration, TransitionContent, etc. and I have not been able to find anything that specifically says "if TransitionInitiatingAction = "HIRE" then _________". 

The issue we're trying to troubleshoot pertains to the creation of tasks we're using for new/transferring employees. We want them to get a task to sign off on some paperwork but individuals who we don't want to get the task are currently getting it. This is because the initiating action for "Transfer" is somehow calculating simple HRIS updates (such as changing the manager on a position) as transfers when we only want transfers stemming from job requisitions or manager actions to actually count for these tasks. Similarly, I'm concerned that undoing terms with a 'rehire' action is going to generate those when we only want them for a rehire on a job req, etc. 

I can surmise that these are somehow scanning a resource's audit log for Actions of a specific type (or otherwise referencing business classes within EmployeeHistory or EmployeeTransactions) but I haven't been able to actually find that logic to consider configuring it. Does anyone know where this actually lives? I submitted a ticket but they said it basically lives in the background and to just deal with it. 

Assuming we can't configure these actions, has anyone had success with Custom Groups (BusinessClassGroup) for assigning Transition Programs? I'd consider doing a custom group with something like "EmployeeTransactionHistory.Action = "TA TRANSFER" but my fear would be that this audit entry would only exist after the Transition Program already exists. Thanks for reading!

Joseph Van Denburg

Check the "Hire" action on both JobApplication and Employee.  "Transfer" action on both JobApplication and WorkAssignment, etc.  In short, both the GHR and TA versions of the actions check for the TM initiating action.  You will likely need to go down the Custom Group path to somehow differentiate between them.