[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.

[Jim Coyne]

I'm looking at the "Account Notification" Activity in my PDI. The Description says:

This Activity creates a new profile in the sys-user and the HR Profile table for the New Hire if it does not already exist. It also generates a login name and password for the New Hire to access the HR Portal so they can complete tasks, see the status of their on-boarding, and access information provide by HR

But how does it create the sys_user record?  There's nothing really on the "Account Notification" HR Service that is specified on the Activity that leads me to see how it would be created?

[Kiel Sanders]

Hi Jim

The script shown above defines what HR Services will generate a new account based on the value field within the HR service form, Onboarding is the most common.  If a HR Service's value is listed as requiresUserOrProfileCreation in the script include, it will generate a new user and profile record for the employee starting with the setGeneralFields() method within the hr_CaseUtils script include.  The fields from the record producer are mapped to the profile within the hr_Profile (which is called from the setGeneralFields() method).  Fields from the record producer will automatically be mapped to the profile if the variable's Field value matches the name of the column on the profile.  You can also define additional mapping within the hr_Profile script include but it would be best to match them within the record producer.

The Account Notification that you are referring to the way we email the new hire's credentials to them.  The "Account and Internal Systems Access Automatically Granted" HR Service used for this process fires the "Account Notification" workflow.

[Christian Prob2]

@Kiel Sanders Hi Kiel - just out of curiosity: is there a specific reason why this is built so weirdly complicated, over multiple levels, hidden in code and slightly not making my life easier?

It would be great if there would be a simple way to define an activity - referencing the "HR Service" "Account Creation" that does just that - create the required records for a candidate, right away?

Cheers, Christian

[Kiel Sanders]

Hi Christian

I believe this thread was referring to our first release of Enterprise Onboarding & Transitions in Jakarta and how users were created. I agree that this was unnecessarily complex.

We now have an Account Notification HR Service that acts in a similar fashion to what you described. You can add this into a Lifecycle Event in order to trigger a workflow that checks whether the user already exists and if not, creates a new user account and sends a notification with a temporary password.

[rhysbrennan]

Hi @Kiel Sanders 
What release is updated process available in? I cannot see any difference from Madrid to Newyork in the Account Notification HR Service. Both are manual, is this change in Orlando?