OOTB New Hire Onboarding (demo) issue

[ChunjiJ]

The following issue is really troubling me, and I hope to get help.

It's still about the HRSD OOTB New Hire Onboarding (demo) issue.

submitting a record from the Employee Center should automatically create entries in the user table and HR profile table due to the script under the item.

However, I found that if I delete the

Account Notification activity from the lifecycle, although it can create an entry in the user table, the user ID remains empty.

If I keep the Account Notification activity , the user ID is created normally. I don't understand what relationship exists between user generation and the Account Notification activity. I request your assistance. Thank you！

[SP22]

Hello @ChunjiJ,

I believe below link can answer you.

https://www.servicenow.com/community/hrsd-forum/user-id-not-populating-automatically-when-new-user-i...

If this helped to answer your query, please mark it helpful & accept the solution.

Thanks
Santosh.p

[Ravi Gaurav]

Hi @ChunjiJ 

• In OOTB New Hire Onboarding (demo), the Account Notification activity in the Lifecycle Event is not just a “notification” step — it actually triggers parts of the account creation / provisioning flow.

• Specifically:

  • When you submit onboarding, a Lifecycle Event execution plan runs.

  • The Account Notification activity calls the HR integration / provisioning subflow (sometimes referencing the Create HR User or Provisioning - Create User activity).

  • That subflow is responsible for filling in details like User ID on the sys_user record (based on HR profile and new hire details).

• If you remove that activity, the record in sys_user is created because the initial script on the catalog item inserts a stub, but the logic to generate and assign a unique User ID never runs.

• Catalog Item Script: Creates HR Profile + Sys_user shell entry.

• Account Notification Lifecycle Activity:

  • Calls into OOTB subflow Generate User ID (uses transform logic or naming convention from config).

  • Populates user_name field.

  • Ensures proper sync with HR profile.

So, the dependency is: User ID generation is tied to Account Notification flow → not just email sending.

What You Can Do

1. If you must delete/replace the activity:

   • Copy the subflow logic from Account Notification that handles user_name generation.

   • Add it as a standalone activity in your lifecycle.

   • Or call the OOTB subflow sn_hr_core.Create HR User / sn_hr_core.Generate User ID before sending your own notifications.

2. If you just want to suppress the email:

   • Keep the Account Notification activity but disable or replace only the notification action inside it.

   • That way, the user creation logic still runs, but you won’t spam with unnecessary notifications.

[ChunjiJ]

Thank you very much for your answer. It has been very helpful to me.

I would like to delete this activity.

May I ask where I can find the OOTB subflow sn_hr_core.Create HR User / sn_hr_core.Generate User ID? I haven’t been able to locate it.

[Bhuvan]

@ChunjiJ 

You can refer below articles that should help to understand the relationship

https://www.servicenow.com/community/hrsd-forum/new-hire-onboarding-demo-auto-generate-account-in-ta...

https://www.servicenow.com/community/hrsd-forum/user-id-not-populating-automatically-when-new-user-i...

https://www.servicenow.com/community/hrsd-forum/auto-create-new-hire-when-a-lifecycle-is-initiated-f...

As per community guidelines, you can accept more than one answer as accepted solution. If my response helped to answer your query, please mark it helpful & accept the solution.

Thanks,

Bhuvan