Core HR Applications And Employee Center practice questions

Use the Branding Editor to update logo and primary colors

The Branding Editor directly modifies the Employee Center portal's header logo and primary colour scheme, satisfying the requirement to customise header branding. It applies theme variables across the portal without code changes, making it the intended no-code mechanism for logo and colour updates in ServiceNow Employee Center.

Modify the CSS in the portal theme record

Portal theme records hold the CSS controlling Employee Center header styling, so editing that CSS applies custom branding such as colours, fonts and layout. This targets the header without altering core portal widgets or page content.

Apply the HR Criteria to the Topic record within the Employee Center configuration

Attaching the HR Criteria directly to the Topic record is what binds the audience restriction to that content. Without this association, the criteria exist but never filter the topic, so the stem's requirement for correct restriction fails.

Ensure the 'Available for' field is populated on the Topic record

Populating 'Available for' on the Topic record defines which audience types may see it. This field gates visibility alongside criteria, satisfying the stem's requirement that HR criteria correctly restrict access rather than leaving the topic broadly exposed.

Create a custom HR Criteria record specifying the audience

A custom HR Criteria record defines the audience conditions themselves. It supplies the actual filter logic the topic references, so without it there is nothing for the Topic record to evaluate against when restricting access.

sn_hr_core.case_reader

The sn_hr_core.case_reader role grants read access to HR cases, satisfying the requirement to view the HR Case module in the navigator. Without it, the module stays hidden despite other HR roles. This role specifically controls visibility of case records, matching the reported symptom precisely.

HR Service record

Approval configuration lives on the HR Service record itself, within its approval-related fields, so the manager sign-off fires before the case transitions into Work in Progress. Defining it here binds the approval to that specific service rather than to a workflow or catalogue item.

HR Criteria

HR criteria target content by employee attributes such as region, so the North America banner reaches only that population without duplicating widgets or portals. This satisfies the stem's efficiency constraint by reusing existing user criteria rather than building separate audience-specific configurations.

Update the HR Assignment Rule to include mandatory skill conditions

Assignment rules evaluate conditions before routing a case, so adding a mandatory 'Payroll' skill condition ensures only agents holding that skill are selected. This directly satisfies the constraint that HR cases reach solely Payroll-skilled agents, rather than relying on manual assignment.

HR Service definition

An HR Service definition is mandatory because the record producer must reference it to determine the case type, assignment, and fulfilment flow generated on submission. Without a linked HR Service, the producer cannot create a correctly classified HR case.

Variable mapping

Variable mapping is required so the answers captured on the record producer form populate the corresponding fields on the generated HR case record. Without mapping, submitted values would not transfer to the target table, leaving the case incomplete.

Target table selection

Target table selection is required because the record producer must specify which table receives the created record, typically an HR case table. This determines where the submitted data lands and which fields and processes apply.

HR Criteria

HR Criteria define the conditions, such as department, location or employment type, that determine which HR cases a user may view. Applying them to HR case security restricts visibility to HR users matching those criteria, exactly as the scenario requires.

Branding Editor

The Branding Editor provides theme settings, including primary colour, logo and banner, for Employee Center. Editing it applies the organisation's chosen palette across the portal, satisfying the requirement to change branding colour without custom CSS or portal record alterations.

Knowledge Base access list

A Knowledge Base access list restricts which users or groups can read articles within a specific knowledge base, satisfying the requirement to limit Employee Center visibility. It operates at the knowledge base level, blocking unauthorised users before article-level rules apply.

User Criteria

User Criteria define conditions based on user attributes, such as department or role, that determine article visibility in the Employee Center. This satisfies the restriction requirement by filtering articles per user, complementing knowledge base access lists.

Record Producer

Required to create the case from the portal.

HR Criteria

Required to determine visibility.

HR Service record

Required to define the process.

Using an HR Task of type 'e-Signature'

e-Signature tasks link to document templates.

Topic Detail

Topic Detail is a component of HR Service configuration, linking the HR service to its topic category so employees can locate it through the HR portal taxonomy. It governs how the service is classified and surfaced within the HR service catalogue.

Record Producer

Record Producers let employees raise HR requests through a catalogue-style form, and each HR Service references one to define how the case is created. This satisfies the configuration requirement by binding the service to a structured intake mechanism rather than free-form case entry.

Topic Category

Topic Category groups HR Services into a navigable taxonomy within the HR portal, so employees browse related services together. It is a required part of HR Service configuration because it determines where the service appears in the service catalogue hierarchy.

Name

The Name field is mandatory because every HR Service record requires a unique identifier for referencing in workflows, catalog items and reporting. Without it, the platform cannot distinguish or retrieve the service, so creation fails validation. This satisfies the stem's requirement for fields that must be supplied when creating a new HR Service.

Topic Detail

Topic Detail is a mandatory field when creating a new HR Service, satisfying the stem's requirement for two compulsory fields. It captures the specific subject matter of the request, routing the case accurately within the HR service catalogue. Omitting it prevents service creation, confirming its mandatory status alongside Short Description.

sn_hr_core.admin

The sn_hr_core.admin role grants the administrative privileges needed to configure and manage HR Workspace components, satisfying the requirement for full agent functionality. Without it, agents cannot access the configuration and case-management capabilities the workspace depends on, so it is one of the two roles commonly required.

sn_hr_core.case_writer

The sn_hr_core.case_writer role grants write access to HR case records, satisfying the requirement that an HR Agent create and update cases within the HR Workspace. Without it, the agent can view cases but cannot modify them, blocking core casework. This role is commonly paired with sn_hr_core.basic for full agent functionality.

Record Producer

A Record Producer creates HR Cases from the service portal and is linked to an HR Service, which defines the case type and fulfilment. This association routes submitted catalog items into the correct HR Service.

ACLs

Access Control Lists are the definitive way to restrict record view access.

Manage HR Services

Manage HR Services provides the central dashboard listing every active HR service record, satisfying the requirement to view all active HR Services. Unlike case- or request-based modules, it queries the HR Services table directly, so the full catalogue appears without filtering by assignment or state.

Variable configuration

Marking the variable mandatory in its own variable configuration enforces completion before the Record Producer submits, satisfying the requirement that the user cannot bypass it. This is a field-level constraint on the variable record, not a UI policy or catalogue client script.

Quick Links module

Quick Links are configured in the Quick Links module, which stores the widget records that render as shortcuts on the Employee Center portal. This module is the designated configuration point, satisfying the stem's requirement for where the links are defined.