Workday Platform Admin flashcards
Workday Platform Admin · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Supervisory Organization
- An organization that groups workers under a manager and forms the primary hierarchy used for staffing, routing, and security in Workday HCM.
- Job Management
- A staffing model where a worker is hired into a job profile without a predefined position; headcount is tracked by job, not by position.
- Position Management
- A staffing model where each worker occupies a defined position with position restrictions, headcount, and availability; positions must be created before hiring.
- Job Catalog
- The hierarchy of job family, job group, job profile, and job level that defines job attributes, compensation ranges, and competency requirements.
- Effective Dating
- A Workday design where records carry effective dates; future-dated changes create future effective records and as-of dates determine which record displays.
- Security Group
- A container of users that grants domain and business process permissions; types include role-based, user-based, job-based, aggregate, segment-based, and integration system.
- Domain Security Policy
- A policy that grants permissions such as View, Modify, Get, Put, Approve, or Execute on a data domain to specified security groups.
- Role-Based Security Group
- A security group whose membership is calculated from role assignments; role assignment conditions determine which workers receive the role and its permissions.
- Aggregate Security Group
- A group built from other groups using intersection, where members must belong to all included groups, or union, where members belong to any included group.
- Segment-Based Security Group
- A group whose membership is limited to workers in specified segments, such as organization, location, or pay group, restricting access by those dimensions.
- Integration System User
- A non-worker account used by integrations; it must be placed in an integration system security group with the required domain and business process permissions.
- Business Process Definition
- The configuration of a business process type that lists steps, approvals, conditions, routing, and security; it controls how transactions move from initiation to completion.
- Approval Step
- A business process step that requires one or more approvers to act; the approval requirement can be all, any one, or a percentage of approvers.
- Condition Rule
- A rule attached to a business process step that evaluates worker or transaction data to include, skip, or route the step to a specific approver group.
- Delegation
- A date-bounded reassignment of approvals from one worker to another, often used for out-of-office coverage; delegation can be limited to specific roles or business processes.
- Parallel Routing
- A routing pattern where multiple approval steps are active at the same time and do not depend on each other's completion order.
- Calculated Field
- A reusable field defined with a calculation type, such as arithmetic, lookup, aggregate, or text, that returns a value used in reports and business processes.
- Aggregate Calculated Field
- A calculated field that summarizes values across related multi-instance objects using count, sum, minimum, maximum, or concatenation.
- Lookup Calculated Field
- A calculated field that follows a relationship path to a related business object and returns a specified field value from that object.
- Composite Report
- A custom report that combines multiple sub-reports into a single output; each sub-report can have its own data source, prompts, and layout.
- Matrix Report
- A report layout that pivots data into rows and columns and displays aggregated values, often used for trend and cross-tab analysis.
- Report as a Service
- A custom report exposed as a web service endpoint; integrations can call its URL and receive XML, CSV, or JSON output.
- Enterprise Interface Builder
- A configurable Workday integration tool for inbound and outbound data movement using spreadsheet or XML templates; integrations can be scheduled or launched manually.
- Integration Event
- A trigger that launches an outbound integration when a business process or data change occurs; it passes context such as the affected worker or transaction.
- Cloud Connect
- A Workday integration type for predefined connections to external systems such as banks, benefits providers, and payroll vendors, configured with templates.
- Workday Studio
- An Eclipse-based development environment for building complex integrations with custom orchestration, transformations, and multi-step logic.
- Get and Put Operations
- Web service operations where Get retrieves Workday data and Put creates or updates data; both are used by integrations and require security permissions.
- Preview Tenant
- A Workday environment that receives a new release before production so administrators can test business processes, integrations, reports, and security changes.
- Sandbox Tenant
- A non-production environment used for configuration and testing; it can be refreshed from production and is commonly used for release validation.
- Audit Trail
- A Workday report or task that shows setup, security, and configuration changes with who made them and when.
- Data Change Audit
- A Workday report that tracks changes to worker and transaction data, including before and after values and the user who made the change.
- Release Cycle
- Workday delivers two major releases per year, R1 in March and R2 in September, with preview access before production deployment.