CCNA Core HR Applications And Employee Center Questions

The HR Service record holds the Case Template field, which defines the default template applied when that service generates a case. Configuring the link there satisfies the requirement, since templates themselves carry no reference back to services.

Topic Category groups HR services into logical classifications, driving catalogue navigation and filtering for employees while feeding reporting dimensions. It satisfies the stem's requirement by organising services rather than defining fulfilment, approval, or assignment logic — those belong to separate configuration records such as workflows and assignment rules within HR Service Delivery.

The sn_hr_core_profile table holds the HR profile record and references sys_user via its user field, so it is the correct store for core HR data linked to a user account. Other HR tables handle cases, tasks or documents rather than the profile itself.

A Record Producer allows you to define a catalog form that captures user input and maps variables to fields on the HR Case record. By associating it with the HR Service, the form appears when an employee selects that service on the Employee Center, ensuring destination city and move date are collected before case creation.

Updating case status is permitted because HR Agents hold the case-writer role, which grants write access to the state field on HR cases within Agent Workspace. This satisfies the stem's requirement for actions an HR Agent can perform, as status transitions remain within their delegated case-management permissions rather than requiring elevated admin rights.

Topic Category groups HR Services into logical classifications, driving catalogue navigation and enabling reporting breakdowns by service area. It does not control access or approval routing, so it satisfies the stem's classification purpose for reporting and navigation.

HR Criteria are conditions evaluated against the employee's profile and location attributes to determine which HR services, catalog items, and knowledge articles are visible. By defining criteria such as Country equals a specific value and applying them to services and articles, the administrator ensures each employee sees only relevant content from the single Employee Center portal.

HR case records are stored in the `sn_hr_core_case` table, which extends the base Task table and holds HR-specific fields such as case type, HR service, and employee subject. This satisfies the stem's requirement for the dedicated HR Case data table, distinguishing it from generic case or task tables.

Flow Designer supports multi-step approval logic, conditional branching and record actions, meeting the stem's complex approval workflow requirement. It supersedes legacy Workflow Editor for HR Service automation, letting you trigger approvals and actions on HR case records without custom scripting.

Assignment rules route new HR cases to the correct group based on field values, so a rule matching category 'Payroll' directs those cases to the Payroll group. This satisfies the routing constraint; assignment rules run on case creation, unlike business rules or UI policies.

HR Criteria evaluates HR-specific fields such as department, job title and location, which User Criteria cannot reference. This directly satisfies the stem's requirement for the primary benefit: targeting approvals and tasks by organisational data held in the HR system, rather than by generic user attributes.

An HR Case Template supplies default values for fields such as category, assignment group and short description when a case is created. This satisfies the requirement by pre-populating fields, reducing manual entry and enforcing consistency.

HR Tasks records are stored in the 'sn_hr_core' scope, satisfying the requirement for items belonging to the core HR application. This scope holds foundational HR data such as cases, tasks and profiles, distinguishing it from scoped applications like HR Service Delivery Advanced, which use separate scopes.

User Criteria define which users or groups may read, write or cannot access a Knowledge Base, evaluated against user attributes and roles. This satisfies the requirement to control visibility, restricting each knowledge base to its intended audience rather than exposing it to all portal users.

The Record Producer's own HR Service field is empty, so the value never populates onto the created case. Record Producers map their field values directly onto the target record; when that mapping source is blank, the case inherits nothing. This satisfies the scenario's constraint that only one specific producer is affected.

The Help text field on the Record Producer variable definition stores the custom guidance shown to the user beside that variable. Populating it satisfies the stem's requirement, as this field is the native mechanism for per-variable help text.

The My Cases widget on the Employee Center portal lists cases the signed-in user has submitted, giving direct visibility of their own open and closed requests. This satisfies the stem's requirement to locate submitted cases without navigating to the full case list, which shows records beyond the user's own.

The HR Profile extends the user record with HR-specific data such as employee number, hire date and job details, keeping sensitive HR information separate from the standard user profile. This matches the stem's stated purpose.

HR criteria records are stored in the `sn_hr_core_criteria` table, which holds the conditions defining which employees belong to a given HR profile or case. This satisfies the stem's requirement for the criteria storage table, distinguishing it from profile and case tables such as `sn_hr_core_profile`.

Mapping the variable to the Department field on the Record Producer's Map to field tab writes the employee_department value directly into the HR Case Department column on submission. Mapping to a variable set or description would not populate that specific field.

HR skills are stored on the user record's Skills related list, so assignment happens through the agent's User Profile rather than the HR Profile or group membership. This directly satisfies the stem's question of how skills reach an agent.

Record Producers render variables, not table columns, so adding a variable places the new input field on the producer's form. The variable then maps to the HR case field during submission, satisfying the requirement to extend the producer's data capture.

The HR case form can be customized to include fields from related records, such as the employee's HR profile. By adding the job title, department, and manager fields to the form layout, the HR agent can view this information directly on the case. This is the standard way to display related data on a form without navigating away.

ACLs evaluate group membership against the record, restricting read access to Payroll members only. This satisfies the stem's requirement to limit sensitive HR case visibility by group, which a simple role or assignment rule cannot enforce at field level.

Assignment rules evaluate the skills held by HR agents and match them against the skills required on an HR case, routing work to appropriately qualified staff. This satisfies the scenario's routing constraint directly: skills act as a routing criterion within assignment rules, ensuring cases reach agents whose skill profiles fit the case requirements.

The sn_hr_core.admin role grants full configuration rights over HR Services and HR Criteria. It satisfies the stem's management requirement, unlike scoped admin or case-only roles that lack authority to create or modify these HR configuration records.

The 'Quick Links' widget queries the sn_ex_sp_quick_link table, which stores the link records configured for the Employee Center portal. This satisfies the stem's requirement that the widget sources its data from a dedicated ServiceNow table rather than from a static UI page or hard-coded markup.

The HR Case table records employee enquiries and their resolution, storing each request's details, status and assigned agent. It satisfies the stem's requirement to define the table's function by acting as the central repository for HR service interactions, distinct from tables holding employee records or knowledge articles.

Roles are a supported HR criteria type, letting service visibility be restricted to users holding specified roles. Selecting Roles satisfies the stem's requirement, as HR criteria combine role-based and condition-based rules to determine who sees a service.

The sn_hr_core.admin role grants full write access to HR criteria records, satisfying the requirement to manage them. Unlike sn_hr_core.manager or sn_hr_core.case_writer, which permit only case and profile actions, this role carries the elevated configuration privileges needed for criteria table administration. Microsoft Entra ID plays no part here; authorisation is enforced natively within ServiceNow.

Automatic case creation for new hires is typically achieved through a Business Rule or Flow that triggers on the creation of a user or HR Profile. The flow would use the HR Service to create the case. This is the most reliable method to ensure cases are generated for each new hire.

Location is one of the user-profile attributes evaluated when HR Criteria run, so a service or task can be restricted to employees at particular sites. This satisfies the visibility requirement by matching the user's location field.

The 'My Cases' widget filters on the case's Opened for or Subject person field matching the logged-in user. If that field references someone else, the case will not appear, making this the first thing to verify.

To enforce the tenure requirement, the HR Criteria must include a condition on the employee's start date, such as 'Employment start date before [one year ago]'. This ensures only employees with more than one year of service qualify.

HR Services are published catalogue items in Employee Center that surface HR information and requests to employees, such as policies, forms and case creation. They satisfy the requirement by delivering HR content directly through the portal's topic and service structure.

A Record Producer is the catalog item that allows employees to submit an HR case. It defines the form fields and the target table (HR Case). Linking a Record Producer to the HR Service enables employees to create cases for that service from the Employee Center. Without it, there is no submission mechanism.

e-Signature is a discrete HR task type that routes a document to a subject person for signing within an HR case or lifecycle event, satisfying the stem's requirement for a task category alongside Approval and Upload Document.

HR Criteria Diagnostics evaluates the criteria attached to an HR service and reports why a given user does or does not match, exposing the failing condition. That directly answers why the service is not appearing for that specific user.

Widgets are configurable components placed on HR Service Portal pages, so they form part of the portal configuration. They render content and functionality within the portal layout, satisfying the stem's request for a portal configuration feature.

HR Criteria act as a user-based filter controlling whether a service is visible in the Employee Center. If the criteria conditions are unmet, the service is hidden from that user, explaining the absence during testing. This directly satisfies the stem's visibility constraint, unlike publishing or catalogue issues.

The Condition Builder on the HR case list allows the agent to construct a filter using fields such as Assignment group, Active, and Due date to return exactly the open, overdue cases for their group. This is the standard, efficient way to filter records in the HR case list and produce a focused work queue.

Trigger Condition defines the event-driven logic that initiates an HR Lifecycle Event, such as a new hire or termination, satisfying the requirement for a configurable activation setting. It specifies the criteria the system evaluates to determine when the lifecycle event fires, making it one of the three settings found within the event configuration.

An HR Task is a child record under an HR case that represents a discrete unit of work assigned to a fulfiller, such as gathering documentation. It exists to perform work as part of an HR case, not to define the case itself.

Audience targeting allows HR administrators to define conditions based on user attributes, such as department, to control which content is displayed. By applying audience targeting to the Quick Links widget, different sets of links can be shown to employees in different departments without creating multiple portals. This is a scalable and maintainable solution that leverages the personalization capabilities of Employee Center.

The HR Service name is stored in the HR Service field on the case record, which directly satisfies the stem's requirement for locating where that value resides. This reference field links the case to its associated HR service definition, making it the authoritative location queried when reporting or routing on service name.

HR Assignment Rules evaluate case attributes, such as the HR service or category selected, and route the case to the matching assignment group automatically. This satisfies the stem's requirement that Payroll cases be assigned without manual intervention, since the rule triggers on case creation rather than relying on agent triage.

The sn_hr_core.admin role grants the elevated privileges needed to create or modify HR Services, including their configuration and associated records. Standard HR agent roles lack this administrative access, so the stem's create-or-modify requirement is satisfied only by this role.

HR skills reside in the `cmn_skill` table, which holds the skill definitions referenced across ServiceNow, including HR Skill records used by HR Service Delivery. This satisfies the stem's requirement for the table storing HR Skills, distinguishing it from HR-specific profile or case tables.

Date of Birth is a core HR Profile field because it stores employee-specific personal data on the HR profile record, distinct from IT-facing identity attributes. It satisfies the stem's requirement by belonging to the HR-managed data set, not the Microsoft Entra ID user object, so it qualifies among the three correct selections.

Upload Document is the HR task type that presents a file-upload control to the fulfiller, letting them attach the required file to the task. It satisfies the stem's upload requirement directly, unlike standard form or approval tasks that cannot accept file attachments.

My HR Cases is a module filtered on the assigned-to field set to the logged-in user, so it lists only HR cases currently owned by that agent. This directly satisfies the stem's constraint of viewing cases assigned to you.

The Employee Center delivers a single, unified portal experience where staff access HR services, content and tasks from one destination, rather than navigating separate siloed applications. This satisfies the stem's requirement for a consolidated entry point for employee services across the organisation.

The 'Map to field' attribute on the variable binds it directly to the target case field, so Short Description populates automatically on submission. Configuring this in the Record Producer's Variables related list satisfies the mapping requirement without scripting.

HR Assignment Rules evaluate case attributes and route the case to the appropriate group or agent, satisfying the requirement to direct HR cases automatically. They determine assignment targets, unlike SLA definitions or notification rules, which govern timing and messaging rather than ownership.

Taxonomy organises catalog items and knowledge articles into hierarchical categories and topics, grouping related content so users browse a structured Employee Center. This satisfies the stem's requirement to group related items and articles, whereas portals, topics alone or search configurations do not provide that hierarchical grouping.

Automatically routing cases to appropriate groups or agents is precisely the HR Case Assignment engine's core purpose, satisfying the stem's demand for its primary function. It evaluates case attributes against defined assignment rules, then dispatches each record to the correct resolver group or individual, eliminating manual triage and ensuring cases reach the right queue without human intervention.

Categories provide the taxonomy that classifies knowledge base articles, enabling HR agents to browse and filter content by topic. Without at least one category, articles cannot be organised or surfaced through the knowledge base interface, so this component satisfies the structural prerequisite the question demands.

The HR Profile table is stored under the physical name sn_hr_core_profile, holding employee HR profile records used across HR Service Delivery. This satisfies the stem's requirement to identify the correct table name rather than a label or related table.

Selecting an HR Service Type is mandatory because it determines the fulfilment path the platform applies when the service is requested. The type governs which workflow, approval routing and task generation logic activate, so the service cannot be saved without it. This directly satisfies the stem's requirement for creating a new HR Service.

HR Service configuration is the correct location because the subflow trigger is bound to the service record itself, not to the catalogue item or workflow. The stem's constraint—triggering on creation of the HR Service—requires the subflow to be attached within the HR Service definition, where the creation event and its associated subflow are declared.

Assignment routes the HR Case to the target group's queue, where it remains pending until an active agent becomes available to work it. This satisfies the stem's constraint: no active agents in the assigned group, so the case simply waits rather than being reassigned or closed.

Conditions form one of the three factors driving HR Case assignment logic: the criteria evaluated against the case and employee to select the appropriate assignment. They determine which assignment rule fires, alongside assignment group and skills.

The HR service record includes a case creation setting that determines whether a case is generated automatically upon submission, and an assignment group field that routes the case to the correct team. Configuring both ensures the offboarding request creates a case and assigns it to HR operations without manual intervention.

The Localization/Internationalization framework stores translated labels and content against language records, so HR Services display in each user's locale. It satisfies the global-audience constraint by resolving text at runtime per user language preference, rather than duplicating services per region.

Lifecycle Events is a genuine HR Service Delivery component, orchestrating onboarding, offboarding and transitions by triggering tasks, cases and notifications across departments. It meets the stem's criterion of being a valid component of the application.