[HR Lifecycle Events Cases] How user is created when submitting Onboarding Request

[solonxu]

When user submit a Onboarding Request from HR portal, a new user record and HR profile is generated by the system. Can anyone explain how this process work because we want to customize the generation process (have some custom fields to map to user fields).

Thank you.

[Kiel Sanders]

@rhysbrennan 

The Account Notification HR Service and associated workflow were introduced in Jakarta. You will want to add that HR Service to the first Activity Set of your lifecycle event. You can use the Onboarding lifecycle event in the demo data as an example of how this is configured.

[rhysbrennan]

Thanks @Kiel Sanders 
Sorry I misunderstood it sounded like the Account Notification HR Service replaced the functionality of the complex script include calls.

For anyone else to start from, this is what I have mapped so far. It's by no means complete, I took a couple of shortcuts but it's a start on mapping all the calls and may serve others to help reuse or understand the script includes. If I finish it I'll update the attachment but I know enough about the process to move forward on our project.

Our requirements are to generate and create a AD login from the starting RP. The best way to simplify this process seems to be form data validation and changing the new onboarding script to use the workflow, change all the variables and copy the service, activities etc. We have complex identity challenges to manage, including a separate recruitment pre-onboarding system, returning employees with different identities in our HR system and a requirement to maintain a single identity in Active Directory. To do this we are pulling AD, the HR system data from employees, positions, position reporting and organisational roles in as data sources.

[Martin Pavlov]

Hi all,

Thank you for your contribution! This is the only post I saw regarding this topic. 

I have a question regarding the lines 19-20 of the script include. Does this mean that only an HR service with value "request_onboarding" will create a user in the sys_user table?

I have a request to create two different record producers, each one attached to a different HR service and different Lifecycle event, however, each lifecycle will have the Account Notification activity at the beginning. Unfortunately, a user is created only from the record producer which is attached to the service with value "request_onboarding". The other lifecycle, which also has an Account Notification activity, but an HR service with different value, does not create a subject person.

Does this mean that I have to include the HR service's value in that ScriptInclude as additional line? For example: { 'request_external_onboarding': '' } Will this work? Would be there a problem if there is an instance upgrade since this is an OOTB ScriptInclude?

Thanks in advance!

[Jim Coyne]

Yes, as you said, you would have to add that line like so:

this._requiresUserOrProfileCreation = {
	'request_onboarding':'',
	'request_external_onboarding':''
};

It's really dumb how they've done this, because, as you said, the Script Include has now been customized.  To me, it should be a checkbox on the Service record.

[anand-bhosle]

Hello @Kiel Sanders , I see the profile is getting created and i also see the workflow "Account Notfification" but i am unable understand how the credentials are getting generate?

what script is setting the value of variable  "workflow.scratchpad.user_credential_pwd"?

What is the trigger conditions for this workflow?

Btw, we are on orlando version.

Thank you in advance

Anand