Core HR Applications and HR Service Portal
About 41% of the CIS-HR exam — see all 4 domains.
This is the heaviest-weighted domain. It covers how employees and HR agents actually interact with HRSD: the case lifecycle, HR services, the catalog, lifecycle events, the document/employee-file layer, and the Employee Center portal.
HR Services and HR Cases
An HR case is the central work record that an HR agent fulfills. The HR service is the configuration object that defines what a case is about: it carries the COE it belongs to (with its topic category and topic detail), the HR case template, the fulfillment type, the HR criteria that limit which employees an agent can request it for, and the record producer through which employees request it. SLAs come from SLA definitions, not from the HR service. Think of the HR service as the catalog-and-process definition, and the HR case as the live instance of work created from it.
A single HR service can be exposed to employees in more than one way at once:
- as a record producer / catalog item in Employee Center,
- through Virtual Agent or chat,
- created directly by an agent in the Agent Workspace,
- generated automatically by a lifecycle event activity.
When you configure an HR service you choose its HR service categorization (the COE, topic category, and topic detail chain; the COE determines which case table the case lands in), the case creation form (the producer the requester fills in) and the case form (what the agent sees). You can also build a child HR service so that fulfilling one service automatically spawns a related downstream case.
Case and Knowledge Management (CKM)
The HR Case and Knowledge Management application is the core fulfillment engine. It provides: case states and the case lifecycle, HR tasks (sub-units of work attached to a case), checklists, approvals, special-handling notes, case transfer/reclassification, escalation, suspend/resume, knowledge article linking, and response (templated) snippets. HR knowledge lives in knowledge bases (the base system provides Human Resources General Knowledge), and user criteria control who can read or contribute to each knowledge base.
HR Service Catalog and Record Producers
In HRSD, employee-facing requests are surfaced through the HR service catalog. The mechanism that turns a form submission into an HR case is the record producer: a record producer presents catalog variables to the employee, then maps those answers onto fields of the target HR case record. Each HR service that is requestable has a record producer behind it. HR catalog items are organized with HR service catalog categorization so they appear in the right place in Employee Center. Editing the record producer for an HR catalog item lets you change the variables, the variable-to-field mapping, and the HR case table it produces.
Lifecycle Events (Enterprise Onboarding and Transitions)
Lifecycle Events (LE) orchestrate multi-step employee journeys such as onboarding, offboarding, and job transfers. The building blocks:
- Lifecycle event: the overall journey (e.g., Onboarding).
- Activity set: a grouped phase of the journey (e.g., "Before Day 1," "First Week"). Activity sets can be triggered conditionally.
- Activity: an individual step. Activity types include approvals, employee tasks, fulfiller activities (HR task, HR service, catalog item, flow), notifications, flows, content, activity containers, and pulse surveys.
- Audience (HR criteria) decides which activity sets and activities apply to a given subject (e.g., only US employees, only a given department), and the activity set trigger type (Immediate, Date, Other activity sets, Condition, Combination, Advanced) decides when a set starts.
You can attach an HR service to a lifecycle event so the LE produces cases, and you can use the Test Activity Sets tool to dry-run which activities would fire for a sample employee before going live. The Performance Improvement Plan (PIP) is delivered as a lifecycle event.
Employee Files, Document Templates, and Document Generation
- Document Templates generate populated documents (offer letters, confirmations) from data on the record. Template types include HTML templates and PDF (Advanced forms) templates; PDF/advanced forms support fillable fields and signature flows.
- HR document generation runs a template against a case/profile to produce a document that an agent can edit before sending.
- Employee Document Management stores employee-related documents in secure storage (the "employee file"). Each document has a document type, and the security policies on the document type control who can access it.
- E-signature is integrated via DocuSign and Adobe Acrobat Sign services.
HR Service Portal and Employee Center
Employee Center (and the unified Employee Center Pro) is the current cross-departmental employee portal that replaced the older standalone HR Service Portal. Key concepts:
- User criteria control who can see a catalog item, category, knowledge base, quick link, or portal content. User criteria match on attributes such as role, group, department, location, or company. A piece of content can have "Available for" criteria (grant) and "Not available for" criteria (deny); deny wins.
- Taxonomy / topics organize content into browsable categories on the portal.
- Employee Center surfaces the HR catalog, knowledge, Virtual Agent, requests/case status, and journey content. Personas/roles determine what each user can do in the portal.
Sample questions from this domain
Three of the 122 in this domain, with the reasoning. The full set is in the question bank.
What is Employee Center in HRSD?
- A. A configurable agent workspace where HR agents triage, work, and resolve HR cases across their COEs
- B. A unified, multi-departmental service portal where employees can request services and find information ✓
- C. The legacy HR Service Portal, which presents HR catalog items and HR knowledge to employees in a single HR site
- D. The HR Administration module where administrators define HR services, COEs, and HR case templates
Why: Employee Center is the unified, multi-departmental portal experience where employees request services (including HR) and find information. Working cases across COEs is the job of HR Agent Workspace, the agent-facing workspace. The legacy HR Service Portal, a single-department HR site, is the older experience that Employee Center replaced, and HR services, COEs, and HR case templates are configured by administrators in HR Administration (HR Service Configuration), not in the employee portal.
Which feature of Employee Center allows different employee populations to see tailored content based on who they are?
- A. HR criteria set on each HR service record
- B. Data policies on content records by group
- C. Taxonomy and user criteria applied to content ✓
- D. HR assignment rules keyed to the employee's location
Why: Employee Center uses its taxonomy and user criteria applied to topics and connected content to tailor what each audience sees. HR criteria on an HR service only filter which services an agent can request for an employee in Create New Case, so they do not tailor employee-facing content. Data policies enforce mandatory and read-only rules on data, and HR assignment rules route cases to groups or agents; neither personalizes portal content.
How does HRSD typically control which catalog items appear to a given employee in Employee Center?
- A. User criteria (available for / not available for) ✓
- B. UI policies on the record producer's variables
- C. HR criteria on the associated HR service record
- D. COE security policies (read and write groups)
Why: User criteria on the HR catalog item (Available for and Not available for) control which employees can see and request it in Employee Center. UI policies only show, hide, or require variables inside a form the employee has already opened. HR criteria on the HR service only filter what an agent can request for an employee in Create New Case, and user criteria on the item have no relation to them. COE security policies restrict which agent groups can read or write a COE's HR cases, not which catalog items employees see.