error while login into ESc portal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2022 12:27 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2022 11:59 PM
Hi Sriram,
Usually these issues gets fixed by taking these steps :
1. go to Application cross scope access
2. check the record in the not allowed state and mark them as allowed
3. go to Restricted Caller Access Privileges
4. update record status to allowed.
If not fixed then religiously follow these steps :
Step 1: Install the latest Employee Center Pro – with the demo data
Install the latest version of Employee Center Pro from the ServiceNow store. Follow the steps below:
- Navigate to System Applications -> All
- Search for “Employee Center Pro”
- Install at least the Employee Center Pro 22.0.11 or later version. Make sure to check Load Demo Data
Below are the apps that will get installed as part of installing Employee Center Pro —if you haven’t already installed them separately.
- Employee Center (and its dependent apps: Employee Center Core, Employee experience taxonomy, and employee experience foundations)
- Content Experiences (and its dependent Content Publishing app).
After these steps, below is what the /ESC page will look like — this is expected, as we haven’t finished loading the right demo data to create the experience.
Step 2: Load demo data for dependent apps.
Applications that get installed as a dependency, don’t load the demo data associated with it automatically. So, we will need to repair the dependent apps and load demo data for them. Follow the below process:
- Navigate to System Applications -> All
- Find the Content Experiences
- Click Repair and check the box to load demo data
Repeat the above three bullets for:
- Content Publishing
- Employee Center
- Employee Experience Taxonomy
Note: Don’t attempt to repair the Employee Center Core application.
Below is what the /esc portal will look like after this step:
You will notice the “relevant for you” widget is not visible and the search isn't working. While setting up with Demo Data or the OOB employee taxonomy, you need to do the next step.
Step 3: Run “Set Primary topics for taxonomy” fix script
The “Set Primary topics for taxonomy” fix script is required for the “relevant for you” widget and search to function properly on Employee Center while using the OOB "employee" taxonomy. Technically, it sets the “taxonomy_topic” field for the knowledge articles and Catalog items associated with the demo data.
Note: This script is not required if you are using a new/cloned taxonomy, which is then manually associated with the Employee Center Portal.
Follow the steps below to run this script:
- Navigate to System Definition > Fix Scripts.
- Search for Set primary topics for Employee taxonomy script, and click to open.
- Click Run Fix Script.
At this point, you may see some errors pop up when you go to the portal view. Follow the next step o resolve them:
Step 4: Check and allow Requested Caller Access i.e. RCA privileges requested by Employee Center
Follow the instructions on this product docs page to resolve RCA errors. You will need to download a script provided on the ServiceNow Store listing for Employee Center Pro (you may have to press “show more” to see the script, see screenshot below), and run in within your instance:
Note: Sometimes it takes time for the RCA requests to show up on the instance, so you may want to load the /esc page a few times, before running the script.
Alternative to running the script, you can manually approve any RCA requests stuck in the requested state by going to System applications -> Application Restricted Caller Access
After resolving the errors, below is how the /esc portal will look like:
You will notice that the nice looking banner that you see on top (the Content Experiences Widget) is missing, this is expected because OOB, we don't have any demo data associated with the widget. Thus it doesn't appear on the home page.
Mark my answer correct & Helpful, if Applicable.
Thanks,
Sandeep
