---
category: [Administration & Integrations, Platform and Product Extensions, Platform and Product Extensions/Integration, Administration & Integrations/Custom Integrations & Apps, Platform and Product Extensions/Workday Extend]
keyword: [Integrate, Workday Integration, Orchestrate for Integrations]
nav: wcp_docs
parent_url: /wcp_docs/
title: >- 
  Reference: Workday Developer Site Glossary
layout: subsection
---

## <a id="section_a"></a>A

-   <b>Aggregations</b>

    The process of condensing data items into a single output item by applying a function called an aggregation strategy to each iteration of a loop.

-   <b>AMD file</b>

    JSON file containing the App Metadata of a custom app that uses Presentation Components. The AMD contains global properties about an app and information about how pages interact.

-   <b>Amazon Web Services Integration</b>

    An Extend Integration with Third Party Platform Services that's available to Extend Professional customers. The Extend Integration with AWS includes:

    -   Workday-provided AWS accounts that work optimally with AWS storage and ML-related services.
    -   Orchestrate components that get and store Amazon S3 objects, invoke AWS Lambda functions, and put events on Amazon EventBridge.

-   <b>AMU</b>

    Alma Mater University: Less common than GMS tenants, this tenant is a Workday tenant with staged data of a typical higher education customer. Only AMU tenants support Student APIs. Enterprise Accounts have access to AMU tenants.

    Standard sign-in user: bking (Dean, Enrollment Services).

    Other common users: pwhitcomb (President), jjones (Vice President), kmartinez (Manager, Public Safety).

-   <b>Analytics dashboard</b>

    A tool on the Developer Site that provides statistics, graphs, and logs that developers and administrators can use to gain insight into their apps. Administrators can view data usage statistics, page and API performance, and transaction logs.

-   <b>API client</b>

    A named credential that's registered on the Developer Site, which generates a client ID and secret necessary for OAuth authentication and authorization to access Workday REST APIs in your tenant. External apps, orchestrations using OAuth, and Extend ISUs need to create API clients to authenticate REST API calls.

-   <b>API Gateway</b>

    Workday Extend component that provides a common endpoint for APIs.

-   <b>App attributes</b>

    App-level custom attributes with tenant-specific values that apps can access during runtime. You can reference attributes in your app components.

    Example: An app attribute named resourceLocation stores the URL of some resource or file used by an app. In each tenant where the app is installed, you can assign the appropriate resource location that applies to the specific tenant.

-   <b>App Builder</b>

    An integrated development environment (IDE) on the Developer Site that enables you to build app components, validate, view logs, upload to App Hub, and deploy to Development tenants. In App Builder, you can build pages using App Preview and visual mode (also known as Page Builder).

-   <b>App Hub</b>

    Workday's tool for end-to-end application lifecycle management.

-   <b>App Preview</b>

    A tool in App Builder that enables you to view and interact with PMDs without having to deploy to a tenant, helping you to iterate on app development much more quickly.

-   <b>Attachment objects</b>

    A type of business object that you can use to store file data and images.

    Also known as attachments, model attachments.

-   <b>Authentication and Authorization Service</b>

    Workday Extend component that provides an endpoint for authorization.



## <a id="section_1"></a>B

-   <b>Business objects</b>

    Business objects extend Workday’s single object model to create new objects. You can use business objects to persist and store app data, and to create sophisticated data models by relating objects to each other and to Workday-delivered objects. When you create business objects, Extend automatically provides report data sources and REST API endpoints.

    Also known as model component business objects (MCBO).

-   <b>Business processes</b>

    Business processes extend Workday’s Business Process Framework to create new business proceess types, and intelligently process app data by capturing approvals, triggering orchestrations, and more. You can report on and audit business process events, you can also use Extend business process of the subprocess of Workday delivered business processes.

    Also known as Extend BPs, Extend business processes, model business processes.



## <a id="section_c"></a>C

-   <b>Canvas Design System</b>

    An open source design system that consists of reusable UI components, assets, and guidelines that enable teams to create scalable, unified experiences in Workday's look and feel. External Extend apps that don't use the Extend presentation components can use Canvas Kit to create user experiences consistent with Workday's design principles.

-   <b>Code mode</b>

    A toggleable mode in App Builder that enables a developer to build an Extend app using a coding interface.

-   <b>Company</b>

    For Workday enterprise customers, a group of Developer Site users that are associated with or employed by the same organization. Personal account users don't interact with Companies.

-   <b>Console for PMD debugging</b>

    A PMD Scripting object that receives logging messages and sends them to the Extend app's log.

-   <b>Context-free task</b>

    Context-free model tasks enable users to directly access Workday Extend apps in a tenant, either by searching the task name from Global Search Bar, or allowing end users to access Workday Extend apps from various Workday User Interfaces, such as Hub, Journeys, Cofigrable Alerts, Dashboards, Landing Pages, Shortcuts, To-Dos, Announcements.

-   <b>Custom app</b>

    An app type that runs in Workday using the Extend app components.



## <a id="section_d"></a>D

-   <b>Developer Forum</b>

    A space for Workday Developers to directly collaborate, ask and answer questions, and share solutions with each other. In the Developer Forum, you can find answers, find contributed solutions, provide feedback, and directly engage with Workday product managers, engineers, and developer relations. Developers sign in the Developer Forum using the same Workday Community login account.

-   <b>Development tenant</b>

    Workday-issued tenant for Extend developers to build and test apps, before they promote the apps to Implementation, Sandbox, Sandbox Preview, then Production.

    Access varies depending on if you access the Developer Site as a Workday customer or as Workday Developer Personal Account:

    -   Development tenants are issued to customers with Workday Extend subscriptions. Only Company Administrators can create and delete Development tenants. The Company Administrator who created the tenant will receive access information by email, and can then share this information with the rest of their team. Development tenants contain only staged data for testing purposes and do not contain any customer data.
    -   Personal Account users can create Development tenants. These tenants expire if not logged in for 7 days.

    See also: GMS, AMU, GOV.



## <a id="section_e"></a>E

-   <b>Enterprise Account</b>

    An account for a Workday customer or partner organization who has purchased products on Workday Build.

-   <b>Enterprise Interface Builder (EIB)</b>

    A simple, secure no-code data import and export integration tool for Workday functional administrators. EIB enables scalable mass imports, exports, and initiation of business processes within Workday, streamlining data management for all enterprise functions.

-   <b>Entitlements dashboard</b>

    A tool on the Developer Site that enables administrators to view and manage your usage of Workday Extend. The dashboard provides usage statistics as well as thresholds that are determined by your Workday Extend contract.

-   <b>Expression Builder</b>

    Orchestration Builder's tool for defining and evaluating simple expressions.

-   <b>Extend app</b>

    An app that may contain presentation, model, and orchestration components.

-   <b>External app</b>

    An app type that runs outside of Workday with data provided by Workday APIs.



## <a id="section_g"></a>G

-   <b>GMS</b>

    Global Modern Services: A Workday tenant with staged data of a typical global corporate customer. Personal and Enterprise Accounts have access to GMS tenants.

    Standard sign-in user: lmcneil (CHRO).

    Other common users: smorgan (CEO), tserrano (CFO), jlee (VP of Sales).

-   <b>GOV</b>

    Green Oak Valley: Less common than GMS tenants, this tenant is a Workday tenant with staged data of a typical government customer. Enterprise Accounts have access to GOV tenants.

    <b>Standard sign-in user:</b> jjones (Director of HR).

-   <b>Graph API Explorer</b>

    A Developer Site tool for Extend app developers to explore the Graph API schema and to run queries and mutations.



## <a id="section_2"></a>I

-   <b>Inbound endpoint</b>

    A REST API endpoint in Extend presentation components that fetches data.

-   <b>Integration apps</b>

    An app that may contain only BP and Integration System triggered orchestration templates.

-   <b>Integrations</b>

    The general name for Workday technology that enables you to streamline data exchange between Workday and external systems, or within Workday itself. Integrations enable efficient data flow, reducing manual data entry. Example: you can extract worker information from Workday and populate it automatically into external systems for demographic data updates. Additionally, you can build automated processes entirely within Workday, further enhancing efficiency and productivity.

-   <b>ISU authentication</b>

    Authenticates data access with an Integration System User (ISU), which is a type of Workday user account that apps can use to access data as a system user. ISU access might not align with regular user permissions, so developers need to implement extra security checks within their apps to ensure data security. In App Manager, you can assign ISUs to your app and create an API client for that ISU.

    Also known as Simplified ISU. Note that the previous version of ISU authentication is the legacy WCPISU.



## <a id="section_j"></a>J

-   <b>JSON</b>

    JavaScript Object Notation: A standard file format for data that uses a human-readable notation.

-   <b>Journeys</b>

    A toolset that enables you to guide your employees through their critical professional and personal milestones through an immersive experience. It includes the Journeys and Cards workspaces that enable you to distribute and manage both Journeys and External Cards for your users. You can create custom cards using Orchestration Builder.



## <a id="section_m"></a>M

-   <b>Model Components</b>

    Enable Workday Extend app developers to create data, logic, and security components for apps that are:

    -   Standalone.
    -   Relatable to other Business Objects.
    -   Native to the Workday stack.



## <a id="section_o"></a>O

-   <b>Orchestrate for Integrations</b>

    Workday technology that enables you to design, build, manage, and share integrations between Workday and external systems.

-   <b>Orchestration</b>

    A real-time, event-driven process created with Orchestration Builder. An Orchestration can be part of an Extend App or an Integration App.

-   <b>Orchestration Builder</b>

    A Developer Site tool that enables you to create orchestrations for use in apps.

-   <b>Outbound endpoint</b>

    A REST API endpoint in Extend presentation components that adds, updates, or deletes data.



## <a id="section_p"></a>P

-   <b>Page flow</b>

    A sequence of edit pages that provides users a guided experience for completing a multistep transaction in an Extend app. A flow definition in the Application Metadata (AMD) defines the page sequence and transitions.

-   <b>Page widget</b>

    A runtime object that displays data on a view page or enables user interaction on an edit page in an Extend app. A widget's characteristics and runtime behavior depends on its corresponding PMD tag definition.

-   <b>People Experience</b>

    A suite of features that provides employees with a central place to engage with company information. You can customize each employee's experience so that they can view relevant information when they need it. Features included in People Experience include Workday Home and Workday Journeys.

-   <b>Personal Account</b>

    A free account that's not associated with an Enterprise Account nor any customer or partner organization. Workday Build allows anyone to create an account and gain access to platform features for exploring and learning. Tenants created from personal accounts expire if not logged in for 7 days.

-   <b>PMD file</b>

    JSON file containing the Page Metadata of a custom app. The PMD defines the page layout and content, including:

    -   How to get and display data on a view page.
    -   How to persist data from an edit page.

-   <b>PMD Scripting</b>

    A server-side scripting language that enables you to embed multiline scripts or invoke functions in shared script modules in an Extend app. Use scripts to call PMD functions, widget methods, and event handlers.

-   <b>PMD tag</b>

    A JSON tag definition containing attributes that customize the appearance and behavior of the widget on an Extend page. The PMD tag also enables you to bind its value to the data you want to display on the widget. Its valueOutBinding attribute enables you to send the widget value to an outbound endpoint.

-   <b>Pod</b>

    A unit of PMD code containing reusable PMD tags, which can be referenced in multiple pages of an Extend app.

-   <b>Predefined app variables</b>

    A set of default variables that provide useful runtime information to Extend apps, such as attrstore, endpoints, environment, queryParams, self, site, and others.

-   <b>Presentation Components</b>

    A set of building blocks that create the user interface and page interactions of an app. Presentation Components include metadata tags that define Workday UI widgets and other components that interact with Workday and external data.

    Also known as UI components.



## <a id="section_3"></a>R

-   <b>Reports-as-a-Service (RaaS)</b>

    A tool that enables custom reports within your tenant to be available as web services, which you can access as SOAP or REST APIs.

-   <b>REST API Explorer</b>

    A Developer Site tool for app developers to explore and run Workday REST APIs. To access data on a specific tenant, you must sign in, connect to the tenant, and have the appropriate permissions to run the API operations.



## <a id="section_s"></a>S

-   <b>Script module</b>

    An Extend app component containing PMD Scripts, which you can define a single time and invoke multiple times from different pages.

-   <b>Security domains</b>

    Security domains extend Workday’s configurable security model to secure app data confidently. You can use security domains to secure a page of Workday Extend app, secure accessing app and app data of a Extend business objects, secure Extend business processes, and secure orchestrations. The process of configuring Extend security domain is the same as configuring other Workday delivered security domains.

    Also known as Extend domains, model domains.

-   <b>SMD file</b>

    JSON file containing the Site Metadata of a custom app that uses Presentation Components. The SMD contains global properties about a site, which is a logical collection of pages within a custom app.

-   <b>SOAP API Explorer</b>

    A Developer Site tool for app developers to explore and run Workday SOAP Web Services. To access data on a specific tenant, you must sign in, connect to the tenant, and have the appropriate permissions to run the API operations.

-   <b>Suborchestrations</b>

    A series of steps that you can reuse across multiple orchestrations in the same app.



## <a id="section_t"></a>T

-   <b>Tasks</b>

    Tasks enable users to directly access Workday Extend apps in a tenant, either by searching for the task by name, or by navigating to the task.

    Tasks authored in App Builder are native to a Workday Extend app, and don't need to be recreated in each tenant on which the app is installed.

    Also known as model tasks.

-   <b>Tenant alias</b>

    The tenant alias uniquely identifies the tenant in the API Gateway. Use the tenant alias when you sign in to your tenant through the API Gateway. Example: When you use API Explorer.

    Tenant aliases use the naming convention for the environment of the tenant:

    -   Production: `tenantname`
    -   Sandbox: `tenantname-sb`
    -   Sandbox Preview: `tenantname`
    -   Implementation: `tenantname`



## <a id="section_4"></a>V

-   <b>Visual mode</b>

    A toggleable mode in App Builder that enables a developer to build an Extend app using point-and-click interface.



## <a id="section_w"></a>W

-   <b>Workday AI Gateway</b>

    A set of REST APIs that give Extend Professional customers access to Workday-delivered and curated intelligence to manage your people and money.

    AI Gateway is available in:

    -   Development tenants for all Extend customers.
    -   Non-Development tenants for Extend Professional customers.

-   <b>Workday Cloud Platform API Gateway</b>

    The entry point for Workday APIs and serves Workday API traffic for Extend and Integration Apps.

    Also known as Extend API Gateway.

-   <b>Workday Extend</b>

    A set of tools and services that enable developers to build, manage, and monitor apps that run on Workday.

-   <b>Workday Extend app</b>

    An app built using Workday Extend tools and services.

-   <b>Workday Extend Developer Copilot</b>

    A generative AI tool that provides code generation, chat, natural language search, and summarization capabilities, enabling Extend Professional customers to supercharge development throughout the entire app lifecycle.

-   <b>Workday Extend Plugin for IntelliJ</b>

    An alternative Workday-provided tool for developing custom apps. The IntelliJ plugin is less user-friendly than App Builder.

-   <b>Workday Orchestrate</b>

    The general name for Workday technology that enables you to build and coordinate real-time, event-driven processes across Workday and other external systems. Orchestrate's primary tool is Orchestration Builder. The processes you create with Orchestration Builder are called orchestrations.

-   <b>Workday Graph API</b>

    An API that submits GraphQL queries and mutations in a unified schema that provides access to Workday data and business objects. Using Graph API, you can ask for the exact data you need in a single request, optimizing performance and resource usage for interactive, small-scale transactions.

-   <b>Workday Marketplace</b>

    The [https://marketplace.workday.com](https://marketplace.workday.com/en-US/home) website is where customers can find trusted apps and solutions delivered by industry experts to meet their evolving business needs.

-   <b>Workday Query Language</b>

    A SQL-like query language used to access Workday data directly from data sources and their fields.

    Also known as WQL.

-   <b>Workday REST APIs</b>

    The REST (Representational State Transfer) APIs that provide access to Workday services and data through the API Gateway and exchange of JSON data. Workday REST APIs enable self-service, interactive transactions with Extend apps.

    Also known as REST APIs.

-   <b>Workday SOAP Web Services</b>

    The SOAP (Simple Object Access Protocol) APIs that provide access to most Workday functionality and data through the exchange of XML data. Workday SOAP Web Services enable integrations with Workday for data transfers and orchestrations.

    Also known as Workday SOAP APIs, SOAP APIs.

-   <b>Workday tenant</b>

    A customer’s existing Workday tenant.

    Also known as: Customer Tenant, Implementation Tenant, Preview Tenant, Sandbox Tenant, and Production Tenant.



