Getting Started with Employee Center - Best Practices?

[Jesse_H]

Hello, we upgraded to Rome recently and will build an employee center for the first time. We have never implemented the service portal either (employees use the self-service dashboard views).

I have a few questions about best practices for getting started:

• I read you should clone the OOB taxonomy, but should we clone anything else to avoid trouble down the road? (e.g. the EC theme, the OOB employee center page or portal, etc.)
  
  
• Update sets and application scope: I noticed there are employee center, employee center core, employee experience taxonomy and employee experience foundation application scopes. Is it necessary to make update sets for each scope and switch between them depending on what you're doing to ensure all necessary changes are captured and then batch them up later?
  
  
• If we are not using any demo data is there any need to run those fix it scripts I've read about? All RCAs related to the employee center are set to active.

Are there any other best practices you can think of for getting started?

Thank you!
Jesse

[Community Alums]

Hi Jesse,

This is a official article from ServiceNow using demo data to help you get started and follow the best practices:

https://community.servicenow.com/community?id=community_article&sys_id=8f9b2539db54c9d0457ae6be13961...

You don't need anything else apart from above article.

Mark my answer correct & Helpful, if Applicable.

Thanks,
Sandeep

[Jesse_H]

Thank you, Sandeep.

I have read through that article but would like to know:

• if it is recommended to clone anything else besides the taxonomy (e.g. portal, theme, portal page, etc.) and,
  
  
• if it is best practice to create multiple update sets for each application scope that will be modified for the employee center project (e.g. employee center core, employee center, employee experience taxonomy).

Apologies for the rookie questions. I am new to SN and want to make sure I build the employee center properly for easy migration to production.

Best,
Jesse

[Community Alums]

Hi Jesse,

Glad to see my answer helping you, Kindly mark the answer as Correct & Helpful both such that others can get help.

1.if it is recommended to clone anything else besides the taxonomy (e.g. portal, theme, portal page, etc.) and,

Any widgets you feel you would be using as per your requirements please do clone the widget and do the customizations , that's the best practice.

2.if it is best practice to create multiple update sets for each application scope that will be modified for the employee center project (e.g. employee center core, employee center, employee experience taxonomy).

You will have to capture the updates as per the application scopes in different update sets.

Thanks,
Sandeep

[Sharad S · Accepted solution]

Hi Jesse,

I am more than happy to share my experience with EC implementation. But before that pls check inline comments on your requested queries,

• I read you should clone the OOB taxonomy, but should we clone anything else to avoid trouble down the road? (e.g. the EC theme, the OOB employee center page or portal, etc.)

Sharad- Don't modify OOB provided employee taxonomy. Instead, clone and make necessary changes. 

• Update sets and application scope: I noticed there are employee center, employee center core, employee experience taxonomy and employee experience foundation application scopes. Is it necessary to make update sets for each scope and switch between them depending on what you're doing to ensure all necessary changes are captured and then batch them up later?

Sharad- Yes, stick to the scopes provided by OOB, so you need to create scope specific update sets. I know it's bit hectic but that's one of the best way to do it.

• If we are not using any demo data is there any need to run those fix it scripts I've read about? All RCAs related to the employee center are set to active.

 Sharad- Would suggest following the steps provided in docs instruction. You might need to do some manual changes afterwords. 

Apart from that, if you have the plan to customise home page or any widget then the best way will be to clone OOB objects and make necessary changes.

Below are additional suggestions,

> Adding knowledge topic as the main topic is more helpful if you have more KBAs as OOB catalogue items and KB might be overwhelming for end users. 

> Pls check and configure what to populate in to-do list config

>Would suggest start with min, socialised often instead of just one demo at the end.

> Try to keep OOB, major efforts may go to taxonomy, todo-list config, styling etc

> Don't move existing portal customisation as is, instead check new features available in EC

Let me know if you have any specific questions. 

Please mark as correct answer or helpful if the provided response resolved your query!