Which out-of-box actions lead to the creation of an HR profile?

[Werner1]

Hello

I want to avoid that an HR Profile is created for a user when the usertype = "external". 

What are the different ways to create an HR Profile out-of-the-box?

For now I am aware of the BR "Synchronize fields to sn_hr_core_profile" on table "sys_user" and BR "Create HR Profile for users" on table "HR Case".

If I deactivate those business rules, the HR Profile is still created. 

Question: are there any other functionalities in general to create an HR Profile?

Many thanks in advance.

- 

[Ankur Bawiskar]

@Werner1 

I believe I also shared a working solution i.e. shared the details

As per new community feature you can mark multiple responses as correct.

💡 If my response helped, please mark it as correct ✅ as well so that this helps future readers find the solution faster! 🙏

[Werner1]

Hi Ankur

As you confirmed, your answer was partially correct as the creation via an HR Case and by logging into the portal was not mentioned. FYI, this last option was my solution in the end.

But if someone else faces the same problem, the partially solution will probably not be satisfactory.

For that reason I considered it as helpfull but not as the solution, I hope I did the right thing.

Best regards

Werner

[kaushal_snow · Accepted solution]

@Werner1 ,

Oob HR profiles can be created in several built in ways beyond just the synchronize fields to sn_hr_core_profile business rule on sys_user and the create HR profile for users business rule on HR case.......

for example, automated creation happens when a user logs into the HR portal (triggered by script in the portal header/footer) which checks and inserts a profile if none exists.......the client script that runs on the HR case form when a fulfiller selects a user (Set HR profile on subject person change) will create a profile if needed....... manual creation via the UI or bulk HR profile actions is supported......profiles can also be created via integrations or lifecycle events (like onboarding flows) that run through flow designer or HR core api......and portal header scripts or login logic can auto create profiles on first visit, so simply disabling the two business rules won’t stop all creation because these other mechanisms will still insert a profile if conditions are met.......

If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.