Study guide

15.3 Discovery Boards

Workday Pro HCM Core Certification Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts & Format 1.2 Eligibility, Learning Path & Access 1.3 Study Strategy & Blueprint Map

2 Navigation & Business Objects

2.1 Navigation Techniques in Workday 2.2 Business Objects & Finding Data

3 Organizations & Hierarchy

3.1 Organization Types & Subtypes 3.2 Supervisory Organizations & Reporting Structure 3.3 Cost Centers, Company Hierarchies & Locations 3.4 Leadership Roles & Worker Organization Assignments

4 Staffing Models

4.1 Position Management Staffing Model 4.2 Job Management Staffing Model 4.3 Hiring Restrictions on Organizations

5 Job Profiles & Job Structure

5.1 Creating & Editing Job Profiles 5.2 Job Profiles, Jobs, Positions & Workers 5.3 Job Families, Family Groups & Job Requisitions

6 Compensation Fundamentals

6.1 Compensation Framework Components 6.2 Eligibility Rules & Compensation Defaulting 6.3 Packages, Grades & Grade Profiles 6.4 Salary Plans, Allowance Plans & Worker Comp Events

7 Jobs, Positions & Staffing Events

7.1 Creating Positions & Position Hiring Restrictions 7.2 Managing Filled, Unfilled, Close & Freeze 7.3 Hire Process End-to-End 7.4 Job Changes & Additional Staffing

8 Termination & Contingent Workers

8.1 Terminate Employees 8.2 Contracting Contingent Workers 8.3 Ending Contingent Worker Contracts

9 Configurable Security

9.1 Functional Areas, Domains & Business Processes 9.2 User-Based, Role-Based & Workday-Assigned Groups 9.3 Domain Security Policies 9.4 BP Security Policies, Org Access & Activation

10 Business Process Framework

10.1 Organizations, Security & BP Relationships 10.2 Default, Org-Specific & Rule-Based Definitions 10.3 Definition, Type, Event & Step

11 Business Process Steps & Approvals

11.1 Actions & Subprocesses 11.2 Approvals & Approval Chains 11.3 Completing Tasks During Business Processes

12 Business Process Configuration

12.1 Condition Rules 12.2 Advanced Routing, Labels & Help Text 12.3 Custom Notifications 12.4 Step Ordering Letters & Validation Conditions

13 BP Management & Security

13.1 Mass and Individual BP Management 13.2 BPs and Configurable Security Interaction

14 Report Writer Fundamentals

14.1 Standard Reports & Copy/Modify 14.2 Building Custom Reports: Index vs Standard 14.3 Sorting, Filtering & Prompts 14.4 Report Security, Sharing & Ownership

15 Advanced Reporting & Calculated Fields

15.1 Scheduling Reports 15.2 Matrix Reports 15.3 Discovery Boards 15.4 Calculated Fields & Report Performance

15.3 Discovery Boards

Key Takeaways Explain This Topic AI

Discovery Boards use indexed data sources directly; an existing Matrix report is not a prerequisite.

Build a visualization by selecting an appropriate indexed data source, then choosing fields, groupings, measures and a useful chart type.

Data-source prompts establish supported runtime context; filters refine the selected population and visual exploration.

A compatible visualization can be exported to a Matrix or Advanced custom report; support depends on the visualization and its features.

Sharing a board never replaces domain and data-source security; test the experience with the intended audience’s access.

Last updated: September 2026

15.3 Discovery Boards

Study index: T-numbers here refer to this guide’s index of an older Workday topic list. They are not current Workday task IDs or published exam weights.

Quick Summary: Discovery Boards are Workday’s interactive visual analytics experience for exploring indexed data sources directly as charts, graphs, and related visuals. An existing Matrix report is not required. You create visuals , drive them with prompts , and apply filters so leaders can slice headcount and workforce metrics without exporting everything to a spreadsheet.

Task T67 closes the “presentation” side of Report Writer for HCM Core. Alongside Advanced reports (T57–T64), scheduling (T65), and Matrix summaries (T66), Discovery Boards answer: how do business users explore the story visually?

  • What a Discovery Board Is
  • Purpose

A Discovery Board is a configurable analytics surface that presents interactive visuals built directly from supported indexed data sources . Consumers open the board, answer prompts, apply filters, and drill into visuals to understand patterns (headcount by org and job family, attrition slices, hiring funnels where data allows, and similar HCM stories).

  • Discovery Board trait Meaning
  • Visual-first Charts/graphs/scorecards, not only tabular grid dumps
  • Interactive Filters, prompts, and drill change the view live
  • Indexed-source based Starts with an indexed data source, then fields and visualizations
  • Consumer UX Aimed at exploration by HR partners and leaders
  • Security-bound Still constrained by the runner’s domain access

Exam definition to memorize: Discovery Boards turn indexed data-source fields into interactive charts and visuals on a configurable analytics board—with prompts and filters , and often drillable paths into detail.

What Discovery Boards are not

  • Not this Why
  • Edit Tenant Setup Global configuration, not analytics UX
  • Reorganization Moves supervisory structure, not charts
  • Switch Active Tenant Environment context, not reporting
  • RaaS endpoint Integration pull pattern
  • Security group type Access model, not visualization
  • Replacement for domain security Visuals never bypass Get/View rules
  • Creating a Discovery Board Visual
  • High-level create flow

Identify the data need — define the population, required fields, measures, effective-date context and audience.

Open / create Discovery Board experience available in the tenant for authorized users.

Select a supported indexed data source with the needed fields and available prompts; confirm access and population.

Choose a visualization type (bar, column, pie, line, scorecard-style tiles—as offered in product).

Map dimensions and measures — what sits on axes, what is colored/sliced, what number is shown.

Arrange the board — multiple visuals can tell a multi-angle story (headcount + average tenure + openings).

Add prompts and filters for runtime control.

Validate with a realistic role account (Manager vs HR Partner vs CHRO see different populations). Indexed data source (secured HCM data)

  • │
  • ▼
  • Discovery Board
  • ├── Visual A: Headcount by Region (bar)
  • ├── Visual B: Headcount by Job Family (pie)
  • ├── Prompts: As of Date, Company
  • └── Filters: Worker Type, Location Hierarchy
  • │
  • ▼
  • Interactive exploration + drill to detail

Configuration scenario: Contoso people analytics selects an indexed worker data source and checks that its fields support active headcount, Region and Job Family Group. The analyst builds region and job-family visualizations from that source, validates grouping and counts, and adds appropriate filters. HRBPs open the board Monday morning instead of waiting for a static PDF.

Design tips that show up as exam judgment calls

Prefer clear measures — “Count of Active Workers” beats an unexplained calculated blob.

Limit dimension explosion — boards with hundreds of tiny slices are unreadable.

Check source grain — understand what each returned instance represents before counting; avoid confusing workers, positions and events.

Plan drill — if leaders will ask “who is in this bar?,” detail drill paths must exist on the underlying design.

  • Name for business language — “Q3 Active Headcount Explorer,” not “RPT_MX_472_final_v9.”
  • Using Prompts on Discovery Boards
  • Why prompts matter

A prompt captures a runtime value from the consumer—Company, Supervisory Organization, as-of date, Region, Job Family Group—and uses it to scope the data. The same board definition serves many audiences without cloning a board per org.

  • Prompt use Example
  • Org scope Supervisory Organization = Engineering
  • Legal entity Company = North America Ops
  • Time As of Date = today or quarter end
  • Catalog slice Job Family Group = Customer Support

Prompts on Discovery Boards follow the same reporting idea you learned for custom reports (T63): one definition, many parameter values . They are not the Scheduling Report task, not ownership transfer, and not a way to lock the report from edits.

Prompt vs schedule criteria (keep them straight)

  • Mechanism When values are supplied Typical consumer
  • Interactive prompt on board/report User answers when opening HRBP exploring live
  • Schedule Specify Value Fixed when schedule saved Automated Monday email
  • Schedule Calculate at Runtime Recomputed when schedule fires Automated rolling window

Exam trap: “Primary purpose of a custom prompt” is still runtime filter/parameter input —whether on a report or experienced through a board—not scheduling, not PDF export, not edit locking.

Built-in vs custom prompt mindset

You already distinguish built-in prompts (delivered with certain data sources, often effective date / organization context) from custom prompts authors add. On boards, the practical exam skill is: identify that the board can be driven by prompts so consumers can explore different supported scopes without rebuilding each visualization.

  • Applying Filters on Discovery Boards
  • Filters refine the live view

Filters on a Discovery Board further restrict which instances or categories appear during exploration . Examples:

  • Worker Type = Employee (exclude contingent)
  • Location Hierarchy under EMEA
  • Exempt status
  • Specific Cost Center hierarchy nodes

Filters work with prompts: a prompt might set Company = Acme US, while a filter temporarily hides contingent workers for a leadership conversation.

  • Control Typical intent
  • Prompt Required or primary runtime parameters for the session
  • Filter Additional slicing while analyzing
  • Source and visualization design Define the intended population and measures before sharing
  • Filter design hygiene

Configure and validate the source population and visualization filters for the intended analysis; document essential exclusions.

Expose audience-variable dimensions as prompts .

Leave ad-hoc exploration to board filters .

Remember security still filters rows —a board filter cannot reveal data the runner’s domains hide.

Configuration scenario: Northwind’s Discovery Board prompts for Region. During a store-ops review, the analyst applies a board filter Job Family = Store Associate to focus the charts. The visual’s design and filters restrict the analysis to active workers. A store manager with constrained security never sees other regions’ bars even if they try to clear filters.

  • Discovery Boards in the HCM Analytics Stack Indexed data source → Discovery Board visualization
  • │
  • └─ Optional export of compatible visual
  • to Matrix or Advanced custom report
  • Need Prefer
  • Audit list of every termination last month Advanced report (detail)
  • Headcount cube Region × Job Family Matrix report
  • Interactive leadership visual with supported prompts Discovery Board using an indexed data source
  • Nightly Excel to a shared mailbox Scheduling Report task
  • Integration extract RaaS + ISU Get (as designed)
  • Security and Sharing Reminders

Discovery Boards do not create a parallel security universe:

Domain security still governs field and data visibility.

Sharing / access still governs who can open the board; its indexed source and fields remain subject to security.

Runner security still wins over “the designer could see everything.”

Constrained roles still see only their population—empty charts can be correct, not broken.

Exam scenario: “User opens a board shared by an admin but sees fewer regions.” → Expected if the user’s constrained HR Partner scope is smaller. Sharing is not a data grant.

Common Confusions Table

  • Statement Verdict Why
  • Discovery Board = Edit Tenant Setup Incorrect Analytics vs tenant config
  • Boards ignore prompts Incorrect Prompts are core runtime control
  • Filters replace domain security Incorrect Security still applies

A Matrix report must exist before a board Incorrect Boards start from indexed data sources; compatible visuals may later be exported as reports

Board creation is the same as RaaS Incorrect Visual UX vs web service

Detail access is automatic for everyone Incorrect Available exploration and detail remain limited by source capabilities and security

Study Links

T66: Matrix grouping concepts help interpret summaries, but a Matrix report is not a board prerequisite. Compatible board visuals can be exported to Matrix or Advanced reports.

T63: Prompt literacy transfers directly to board prompts.

T64: Sharing controls access; it does not grant underlying data permissions.

T65: Scheduling is a separate report-delivery workflow; opening a board is interactive analysis.

T69: Source population, field complexity and visualization design affect board performance; validate with realistic data volumes.

When a stem mentions interactive charts , visual dashboard , or Discovery Board with prompts and filters , choose Discovery Board—not Reorg, not Tenant Setup, not a security group.