Trigger Lifecycle events based off fields from Record Producer?

[Logan10]

Hello,

I have a Record Producer being used to handle HR Onboarding. However, on the RP we have a field which would select different types of onboarding which should then trigger a different lifecycle event; as the activities/acitivity sets would be different depending on what type of onboarding is selected.

For example, in the field there is  "Contractor" and "Full time" options, depending on which option is chosen it should trigger different lifecycle events to start sending off the activities. 

any suggestions?

Or perhaps a different solution?

[Christian Prob2]

I don't think that can easily (eg without redundancy) be done. You could assign the same record producer to multiple HR service definitions. But in case of a hiring the hr_profile is most likely created as part of that, so you can't really control which HR service is executed using HR Criteria / Audiences.

Once the HR profile is there - assuming you have the onboarding / employment type on it - you can control which activities are executed in the activity sets by using HR Criteria/ Audiences, but you still would have to put all that are possibly needed in there. So you would end up with one giant HR service to serve them all... 

[Kiel Sanders · Accepted solution]

This isn't part of the delivered functionality but I have a few different suggestions based on your situation.

1. My first option to stay out of box would be to create separate record producers assuming that the type of information captured based on employment type varies. This keeps things simple and allows unique forms for the different request types without scripting.
2. Another option is to use the same lifecycle event type and tailor the activities within the activity type by HR criteria/audience (assuming these contractor/full time values are populated to the HR Profile). This allows you to have one lifecycle event that is easy to maintain while controlling activities for the two varying populations.
3. If you must keep the form the same with different lifecycle events, you should be able to control this in the script of the record producer. The HR Service (and therefore the lifecycle event) is assigned on the case based on the script in the record producer. It searches for the HR Service associated to that record producer and then creates a case using that HR Service.
   
   
   
   You would want to call the createCaseFromProducerByService function instead of createCaseFromProducer. This function is part of the original createCaseFromProducer chain of actions but now let's you pass the sys_id of the HR Service to use. You can then build the necessary logic around this function based on the selected Contractor/Full Time options.

[Logan10]

Thanks! ended up creating various hr criteria /audiences which are chosen from the Record Producer and stored on that individuals HR Profile, then assigning activities based on audience.