| Term | Definition |
|---|
| Abandonment rate | The percentage of call or chat requests that disconnect before a CSR responds to their contact attempt. |
| Abstract class | A class that supports the definition of rules, including other classes. Rules with a class as a key part (including properties, activities, flows, and data transforms) can apply to an abstract class. An abstract class can be inherited by subclasses of the abstract class and can be a child of a higher abstract class. |
| Access Manager | A landing page that you can use to view and authorize operator access to case types, data, and tools in your applications. |
| Access group | A set of users who receive access to application or network resources through their membership in the group. When a user is added to an access group, that user receives the permissions that are associated with the group. If a user belongs to more than one access group, that user acquires the set of access permissions that are associated with each group. You can create multiple access groups within an application to convey different levels of access based on user roles. |
| Access role | A role that defines the classes that a user can view, update, and delete through the Access of Role to Object and Access Deny rule types. |
| Acknowledgment | A letter, email, or other correspondence that is sent to the originator of a work item that identifies the work item ID. |
| Action section | The area in a harness in which the action is performed. The section shows users the actions that they can complete. |
| Activity list | A queue that contains a list of activities that are waiting to run. Each user has the following activity lists: activity (default), workflow, and current. |
| Activity loop | A step in an activity that can run repeatedly, such as for each element in the Value List or Value Group property. |
| Activity type | A definition that describes the characteristics of an activity. Some activity types (Assign, Rule Connect, Route, Notify, and Utility) identify activities that you can reference directly in flows.
The Activity Type field on the Security tab of an Activity form corresponds to the property Rule-Obj-Property.pyActivityType. |
| Activity | The sequential processing unit in Pega Platform that consists of one or more steps. Each step can call a Pega Platform method, transfer control to another activity, or run custom inline Java. |
| Actor | A user, external service, or agent that participates in application processes and specifications.
You can view and define actors for the current application on the application rule, or by clicking the Actors link in the Details section of the Application Overview landing page. |
| Ad hoc case | A case that you can create to handle a business exception or track a related task in the case that you are currently processing. Because ad hoc cases are not instances of a case type, they are not part of your case type hierarchy. |
| Adapter control | A component that is displayed in Pega Robot Studio Object Explorer and used by automation developers. The properties, methods, and events of these controls provide a way to interact with native controls. |
| Adaptive model | A type of scoring model that captures customer responses in real time to make and adapt predictions, typically in the absence of historical records. An adaptive model is used in decision strategies to help identify the most appropriate propositions or next best actions. |
| Administration tab | A tab in Workforce Intelligence where you map applications, map screens and webpages, maintain Off Computer Reason Codes, specify opportunity settings, and manage Pega Workforce Intelligence users. |
| Adopt | The final phase of the Pega Express methodology that encompasses business readiness including training, go-live planning, production deployment, and release retrospectives. |
| Agent availability | A setting that indicates how many CSRs are actually available to handle interactions (and not otherwise busy or unavailable). |
| The percentage of time that CSRs are busy with customers. |
| Agent | An internal background process that operates on the server that runs activities on a periodic basis. In a multinode cluster, an agent can run on multiple nodes. |
| Alert event | An entry in the alert log. Alert events use the naming format PegaRULES-Alert-YYYY-MMM-DD.log. |
| Alert log | A sequence of text files (known as alert events) that support performance-related monitoring. The alert log supports the optional Autonomic Event Services (AES) Enterprise Edition product, which summarizes and monitors alerts across multiple nodes in a cluster. |
| Alternate path | A set of actions that lead your business process to a resolution in a scenario that is different from a default, primary path. You create alternate paths when your business process might result in more than one outcome.
For example, in the process of hiring a new employee, a default path results in accepting a candidate. For better flexibility of your application, create an alternate path that the case follows after rejecting a candidate. As a result, you ensure that your cases can be resolved in many dynamically changing scenarios. |
| Analysis tab | A tab in Workforce Intelligence where you identify opportunities and see how much time has been spent in each application screen or on each webpage. |
| App Studio | The low-code development environment of Pega Platform. |
| Application Explorer | A tool that you can use to quickly access records in the current and built-on applications that are available to your operator. These records are organized by work pool, case type, category, and record type. |
| Application Validation (AV) mode | A mode of rule validation that determine which rules are valid to reference at design time without having to use ruleset prerequisites. AV mode offers performance advantages over the alternative Ruleset Validation (RV) mode. |
| Application administration | The process of identifying applications and web domains, mapping them to a user-friendly application name and a work category to support analysis, and turning on or off the tracking of screens. |
| Application bundle | A .zip archive file that contains an XML document that is known as the manifest. During the import of an application bundle, the manifest controls the order in which rulesets, rules, or other items in the bundle are imported. |
| Application document | (Deprecated) A high-level business overview, including information on case types, flows, user interface, specifications, and requirements. You can create an application document by running the Document Application tool.
For new applications, the product overview and gap analysis documents replace the legacy application document. |
| Application name | A meaningful and unique name that conveys the purpose of your application.
You specify an application name as a key part for the following application rules:
- Rule-Application
- Rule-Application-UseCase
- Rule-Application-Requirement |
| Application profile | (Deprecated) An aggregate of rules and project-related information, such as your implementation methodology or proposed timeline. You can create a legacy application profile to share with stakeholders.
For new applications, the product overview and gap analysis documents replace the legacy application profile. |
| Application rule | A set of ruleset versions that added as a unit to a user's ruleset list. An application rule is an instance of the Rule-Application rule type, which is part of the Application Definition category. |
| Application ruleset | The container for the building blocks that define the behavior of your application. With application rulesets, you manage the versions of your application logic that are used to create the desired outcomes in your application. The order in which the system lists application rulesets on the application determines the priority of rules in that ruleset.
For example, an application that is used for hiring new employees includes two rulesets, MyJobApp and MyHR, in that order. The system gives priority to rules that are located in MyJobApp over the rules located in MyHR because MyJobApp ruleset is first and MyHR is second in the list. |
| Application scoping control | A reusable gadget that filters by application layer, class name, and specified search term. The combination of filters that are used depends on how the control has been configured. This control is used throughout Pega Platform, but is most commonly found on landing pages. |
| Application | A business solution that automates workflows in your organization. Multiple, unrelated applications can be hosted in the same system. You create an application by running the New Application wizard. |
| Application-Based Assembly cache | A set of rules for which the rules assembly on the current node is completed. Each rule that generates and runs Java code is a candidate for the ABA cache.
Note: ABA caching is a legacy mode of caching technology for Pega Platform. UI (stream aspect) rules run with ABA caching, and all other rule types run with VTable caching |
| Application-editing mode | A view that you can enable to access tools and information. To enable application-editing mode, click Turn editing on. |
| Archiving and purging of cases | A Pega Cloud solution that you can use to define when your inactive cases are purged from your database and moved to a secondary storage, so that you can lower your database costs and improve application performance. For example, you can archive resolved Auto Loan cases that are older than two years. If you need to access an archived case, for example, for audit or compliance purposes, you can search for or navigate to the case in the secondary storage. |
| Area chart | A chart that displays data points with filled space rather than points, curves, or lines. You can specify the chart type and subtype for a report definition by using the Chart Editor. |
| Artifact | An object that you create to provide information about a capability or piece of functionality in your application. Examples of artifacts include design documents, requirements, specifications, and user interface mockups. |
| Assign- base class | An abstract class above other classes that contain assignments. |
| Assignment | A task that a user completes so that the business process can advance towards the final resolution. You can add assignments to the business process to collect information or seek approvals from users with different roles or levels of expertise.
For example, in an online credit card application, a customer needs to fill out the online credit card application form by providing a range of personal and financial details. When the application form is completed, the process advances to the bank employees who can process the request by either approving or rejecting the application. |
| Associate | An office worker or employee whose job function is primarily performed on the desktop and whose activities are reported on and summarized by Pega Workforce Intelligence. Associates must have Pega Robot Runtime installed on their computers. Pega Robot Runtime collects the information that Pega Workforce Intelligence presents. Associates are also called data collectors. |
| Associated ruleset | A ruleset that is linked to instances of data classes. Associated rulesets help to identify which data instances to include in an application package or when you export rulesets. |
| Attachment category | A setting that controls the security of attachments in your application. Attachment category restricts user operations on an attachment, based on privileges, when conditions, or attachment types. |
| Attachment type | A setting that defines the media and format of items that users attach to work in your application. An attachment type is implemented in your application as a class that inherits from Data-WorkAttach-. The following standard attachment types are supported: file, note, screenshot, scanned document, URL, and content. |
| Attachment | A file that you can add to the business process to provide additional information, such as relevant correspondence and documentation. You can group attachments into categories to enhance efficiency and speed up the resolution process.
For example, in a car accident insurance claim process, the user can add photographs of a damaged car to the Vehicle damage category and the medical care receipts into the Bodily injury category. Categorization of attachments helps to provide clear separation and context for each file that is associated with the business process. |
| Audit trail | The history of events that took place during the business process so that you can access secure and immutable records of business transactions. The data includes information about which individuals worked on the business process and when, and what automatic processes were performed.
For example, a healthcare company can review an audit trail of a healthcare insurance claim if there is a dispute to prove their compliance with industry standards or government regulations. |
| Authentication | The process or action of verifying the identity of a user or system. Authentication in Pega Platform ensures that only users and systems with verified identities can access resources such as web pages, APIs, and data. |
| Autocomplete field | A field on a form that supports user selection of a text value from a list of candidate values. When you enter characters in this field, the list is filtered to display only qualifying text values. You can configure the styles for this control in the Skin rule. |
| Automatic call distributor (ACD) | A device that distributes large volumes of incoming calls to CSRs. The ACD contains logic that drives routing decisions based on multiple input parameters. Routing parameters can include a combination of data about available CSRs and their skills, and specific information about the call and caller. Common vendors include: Avaya, Aspect, and Cisco. |
| Automatic number identification (ANI) | A series of numbers associated with a call. These numbers identify the phone number of the caller. Sometimes referred to as a CallerID. |
| Automation | An action that does not require human involvement but can instead be done programmatically. |
| Autonomic Event Services | An optional product that monitors, retrieves, organizes, and displays Pega Platform system statistics and warning conditions at the enterprise, cluster, and node levels. |
| Autopopulated property | A Page or Page List property that automatically obtains data directly from a specified data page. The values can be an entire object from the PegaRULES database or copies of pages developed by a Data Page rule. To enable autopopulation for a Page mode or Page List property, configure the Data Access fields on the General tab of the Property form. |
| Available rule | A rule that is visible and can run during rule resolution processing. For an available rule, the value of the pyRuleAvailable property is set to Available or Final (and is not blocked). |
| Average handle time | Length of time, on average, to process one customer interaction. |
| Average speed of answer | Average length of time a caller is on hold before a CSR answers the call. |
| Back-to-back assignments | A situation when a user completes an assignment for a specific work item and then works on a second assignment for the same work item. The second assignment can be from the same flow execution or an unrelated flow execution. |
| Backward chaining | A feature that allows for a computation to advance even when the value of an input or parameter property is not available. This capability is provided by the Rule-Declare-Expressions rule type and the Property-Seek-Value method working together, and can be seen in standard flow actions including VerifyProperty and VerifyPropertyWithListing. |
| Bar chart | A chart that displays property values as horizontal bars. You can specify the chart type and subtype for a report definition report by using the Chart Editor. |
| Base class | A standard abstract class that is immediately below the top class in the hierarchy. This top class, known as the ultimate base class, is identified by the symbol @baseclass. |
| Base rule | The original version of a rule that has been circumstanced. A base rule must exist for every circumstance. |
| Benefit value analysis | An approach that decomposes processes and journeys into low-level steps and explores the value that each step brings to the overall experience. This is achieved through a series of workshops that: introduces the objectives of the process; identifies the key functions of the process; explores new ideas for improving the process; prioritizes the ideas based on the value |
| Best Bets | A subset of options that are likely to have the choice for which you are looking. Best Bets are classes in your application that are the Applies To key part of one or more rules. |
| Blended agent | An employee in the role of contact center agent who divides their time and attention between multiple communication channels (voice, email, SMS) to service customer needs. |
| Bounded workflow | A workflow that starts on a specific application or view and ends on a specific application or view. These workflows are based on Production and Other work applications. Your system administrator defines those applications and screens, and assigns the workflow tags that represent this workflow. |
| Branch ruleset | A ruleset that is based on another ruleset and contains rules that are in active development in the associated branch. |
| Branch | A container for rulesets with rules that are undergoing rapid change and development. |
| Breadcrumbs control | A UI element that shows each task, or entry point, in a flow execution. Application users can click a task based on settings in the flow. The flow can allow users to jump to any task in a flow, or just to the completed tasks. |
| Breadcrumbs | An indicator of which area of the hierarchy is being shown on the screen. You can click on a breadcrumb to jump to a previous level of the hierarchy. |
| Bubble chart | A chart that displays three dimensions of data in a two-dimensional format. With a bubble chart, all three dimensions are numeric, as opposed to column or line charts, where one axis is numeric and the other is a category.
The horizontal and vertical axes represent two of the three dimensions, as in other charts. The size of the colored circle, or bubble, for each data point represents the third dimension.
You can specify the chart type and subtype for a report definition report by using the Chart Editor. |
| Build order | A part of the delivery approach that specifies the sequence in which rules and data instances are created when earlier phases are complete. The build order might differ in separate iterations of the implementation. |
| Build | The third phase of the Pega Express methodology that describes how to iteratively build and test an application and how to refine more user stories during each sprint. The output is working software that both meets the definition of done and passes all the relevant tests. |
| Business Architect | A role that drives working sessions to further understand microjourney steps and to create the user stories used by the technical team. Different levels are Senior, Lead and Principle BA. |
| Business Intelligence Exchange (BIX) | An optional add-on that integrates Pega Platform data with information from other systems of record. Enabling the BIX ruleset allows extraction of data from the Pega Platform database. The BIX Extract rule defines the class, page, and properties from which to create extract files. |
| Business Value Assessment (BVA) | A phase of the implementation methodology during which stakeholders define the success factors and expected return on investment of the project. Business Architects play a major role in this phase. |
| Business day | Scheduled work days for users. Business days are not identified as holidays or other days with no work on a calendar data instance. If your application includes multiple calendar data instances, a non-business day for some users might be a business day for others. |
| Business exception | An unusual condition within a business process that warrants investigation or external review. A business exception might indicate fraud, error, compliance failure, or other potential harm to the organization, customers, or other parties. |
| Business process management (BPM) | The organizational activity of developing and managing processes that are responsive to change and improve business performance outcomes. When an organization uses BPM, they coordinate the presentation of the user interface, logic, and data access for an application with the process for how work gets done. |
| Business rules engine (BRE) | A Java-based rules engine that separates business logic from applications and enables the enterprise to capture, manage, and execute business policies and practices as business rules. The business rules engine supports declarative rules, multithreaded execution, and a large number of industry interfacing standards. |
| Calculation Builder | A tool that provides a guided interface to help you define SQL expressions for use in report definition rules. |
| Calendar | A data instance that records the work schedule of an organization or group of people, including holidays and shift start and stop times. Calendar data instances can be referenced in organization, work queue, and operator ID data instances, and service-level agreements. The calendar allows due dates and similar calculations to be based on business days rather than calendar days. |
| Case ID | The permanent, unique identifier of a case. You can use case IDs to find cases that are relevant to your application or organization. |
| Case Manager portal | A portal that supports users who manage cases and their related subcases and tasks across multiple channels, lines of business, departments, and systems. Users can create, view, and work on cases and assignments. |
| Case Type Backlog (CTB) | A tool whose primary role is to capture the key constructs (data, interfaces, personas, and channels) that are required to build the selected high-value Microjourneys and to define the scope for the first MLP release. The CTB also facilitates quick project sizing and is a key handover document from the Discover phase to the project team at the beginning of the Prepare phase. |
| Case Type Explorer | A tool that you can use to manage case types and browse sample case types. By using the Case Type Explorer, you can create a hierarchy of case types in your application. |
| Case collaboration | A method to quickly and conveniently share and exchange information by instant messages, spaces, and shared documents.
For example, in a business process of reviewing a job application, an HR worker and a hiring manager might exchange messages about the course of the process and attach relevant documents to the messages. You can collaborate with other members of your organization, such as your coworkers, but also with outside customers without access to your application. To reach target recipients of your communication, you can use different channels, such as email or text messaging. |
| Case dependency | A relationship between your main business process and supporting business processes that need to be resolved before the main process reaches resolution. Pega Platform refers to the main business process as a parent case type, and to supporting business processes as child case types.
For example, a parent case type that represents hiring a job candidate can only be resolved after child case types for running a background check and completing a review process are completed. Parent and child cases interact with each other, for example, by copying data from a parent case to child cases. By creating case dependencies, you can resolve complex business processes without creating long and complicated case types. This modularity also helps you save time and costs, because you can reuse child case types in different scenarios. |
| Case instance | See case. |
| Case instantiation | The way that a case is created in your application. You can manually create a case or automate this process based on the creation of a parent case, a set of when conditions, case-type dependencies, or received email. |
| Case management | A method of delivering goal-oriented results by handling business cases from start to a resolution and combining human actions with digital automations. In case management, you use data and people that are involved in a business process to visualize and model work, so that you can prepare a set of actions that lead to your objective.
For example, you can model a process of approving candidates after reviewing job applications, from collecting documents from a candidate, through the job interview, to the final approval. |
| Case manager | An application user who can view and update delegated business rules, in addition to performing work. |
| Case resolution | An act of completing your business process. When the case reaches resolution, you can view the resolution status that describes the process outcome. By analyzing the resolution status, you can learn whether the case was successfully completed or rejected.
You can configure how your business process behaves after reaching the resolution stage. For example, when a loan request dispute reaches resolution, your application displays a Resoled-Approved status to inform that the loan request was approved.
If your business process supports child processes, you can configure their behavior after the main process is resolved. For example, if the loan request is rejected, your application withdraws all the supporting processes. |
| Case status | The primary indicator of the current state of your business process. By using case statuses, you communicate progress to people that are involved in case processing to ensure a common understanding on the path to reaching your business objectives.
For example, you can use a status In-Progress to communicate that a case worker is working on a case, and Resolved-Completed to announce that the case reached a successful resolution. You can use default statuses, or you can create custom statuses to meet your unique business needs. |
| Case type | A template for a case in an application. |
| Case | Actual work that is performed by application users and automations that consists of a sequence of tasks and leads to an intended business goal.
An example of a case is a process of hiring a particular job candidate, where an HR worker collects necessary documents, a hiring manager conducts a job interview, and an application sends an automated email with onboarding information after the candidate is approved.
To create a case, you first build a template of your business process that is a case type, and then apply the template in multiple cases, for example, to review applications from many candidates. |
| Case-type dependency | A condition that must be met before a child case is created or an assignment is automatically completed. Each condition defines a case and a status. |
| Certificate set | A place that gathers all keys and certificates that are needed to properly configure, build, and run a mobile app for Android or iOS. |
| Certified Lead System Architect (CLSA) | A person who is responsible for the design and quality of Pega solutions. This person has passed a certification exam issued by Pega that tests their knowledge of design and implementation of Pega solutions. These people typically lead implementation teams and ensure that solutions use the technology to provide an optimum business outcome. |
| Certified System Architect (CSA) | A Pega Platform application developer or technical staff member who has passed an exam that acknowledges the acquisition of foundation-level knowledge of Pega solutions. |
| Change request (CR) | Anything that impacts the objectives, cost, timeline, or resources on a project. Even changes that have no cost impact should be logged. A change may be instigated by the project team or the customer. Change requests should be recorded on the weekly Project Status Report and in a change log. |
| Channel interface | A portal that includes predefined layouts and navigation. You can use channel interfaces to quickly customize the user interface of your application by selecting headers, menus, and a page that is displayed when a user logs in. |
| Channel | A digital medium through which users access your application. Depending on your business needs, you can set up various channels for the same application.
For example, customers can access an application for booking flights through a browser-based web channel, or through a mobile channel that relies on a mobile app. In addition, you can also build a Facebook chatbot for customers who want to ask questions about their booking. At the same time, you can set up a second, more utilitarian web channel to accommodate professional users, such as travel agents.
By making an application accessible over several channels, you can reach a wide variety of audiences, and provide each user group with the most appropriate content and user experience. |
| Chart Editor | A tool that you use to create and edit charts for summarized reports. You can use the Chart Editor to select a chart type and subtype, define the appearance and formatting of titles and information, and specify the report data that populates the chart. You can access the Chart Editor from the Charts tab of a Report Definition rule form or from the Report Editor. |
| Check-in process | The process of replacing a base rule version with a private copy of a Rule- instance that you checked out and updated. |
| Checkout | A private copy of a Rule- instance that you update and later check in to replace a base rule version. All checked out rules reside in a personal ruleset that is only visible to your operator. |
| Child case type | A supporting business process that adds up to your main business goal and that you need to resolve before you reach our ultimate objective.
For example, a business process that represents hiring a job candidate can only be resolved after child case types for running a background check and conducting a job interview are completed. By using child case types, you save time and increase flexibility of your application, because you can reuse individual child case types in different scenarios. |
| Circumstance | An optional qualification that is available for supported rule types and is built upon an unqualified rule known as the base rule.
By using circumstances in your application, you can easily support a variety of use cases. |
| Class group | An instance of the Data-Admin-DB-ClassGroup class that corresponds to tables in the PegaRULES database. Class groups cause the system to store instances that correspond to two or more concrete classes that share a common key format in a single database table, which is known as a work pool. The name of the class group is a prefix of the names of its member classes. |
| Class hierarchy | The way classes are organized in the application to ensure sharing of rules and data. When you create a class hierarchy, you define which classes contain other classes and, as a result, you define how classes reuse or inherit rules. A class that contains another class is called a parent class, while a class that is contained by another class is called a child class.
The ultimate base class (@baseclass) is the topmost class in the hierarchy. All other classes are derived from this class. The names of all classes that belong to a common class group start with the class group name, followed by a hyphen.
For example, if you define a class group Work-Object-App-Task, you can name the child classes in this class group Work-Object-App-Task-Ordering, Work-Object-App-Task-Shipping, and Work-Object-App-Task-Billing. Child classes can use rules that belong to parents (for example, user data). |
| Class inheritance | While a class contains rules which define the behavior of your application, class inheritance allows your application to reuse the existing rules for other cases or applications. Rule reuse reduces development and testing time without sacrificing application quality. Thanks to inheritance, a child class can use all of the rules that are defined for the parent class.
The system supports two types of class inheritance: directed inheritance and pattern inheritance. Pattern inheritance allows you to reuse rules within a single application only, whereas directed inheritance allows you to reuse rules in other applications. For example, you design a banking application that contains two divisions: Customer Support and Business. The divisions can use pattern inheritance to share rules related to the customer data because they belong to one organization. In turn, two separate applications that require to share the customer data can only use directed inheritance. |
| Class name prefix | A series of characters that precede the class name. Class name prefixes are used during pattern inheritance when Pega Platform searches the class structure to find a rule by using a sequence of prefixes of the class name. The hyphen delimits segments of the name. |
| Class | The rules that define the behavior of your application. You can create classes to gather rules related to a specific object in your application.
For example, in a recruitment application, you can create a class that contains rules that define the flow of the recruitment process. Classes can contain other classes, hence a class that contains another class is called a parent class, while a class that is contained by another class is called a child class. A child class can reuse, or inherit, any of the rules that are defined for its parent class, which helps to build your application faster and more efficiently. |
| Classification | A text value in the prconfig settings or dynamic system settings that is used to group nodes that share specific setting values in a multinode or clustered system. |
| Clipboard message | A text clipboard value that is generated by the system and associated with a property or page. A clipboard message can convey error conditions, progress, or exceptions to the user. |
| Clipboard tool | A debugging and troubleshooting aid for application developers. The tool lets an application developer examine a snapshot of the structure and contents of their own clipboard and change these settings in their workstation browser. The clipboard resides on the server. |
| Clipboard | A temporary memory area on the server that is associated with every connected Pega Platform requestor, including browser-based users and unauthenticated guest users. Your application uses information from the clipboard to process work and make decisions about the next action.
For example, when a courier opens a delivery application to check the address of a customer, the system populates the address field in the application with the information stored in the clipboard. In this way, the clipboard acts as a temporary memory for your application and the case. |
| Code- base class | A class that contains all the classes that define the objects used by a Pega Platform implementation. Application developers can work with properties and clipboard pages associated with classes derived from the Code- base class. |
| Collection | An ordered sequence of rules to run. In each step of a collection, you can define a precondition that is evaluated before execution, and a response action that runs after the step is completed. |
| Column Populator | A utility that you can use for database and schema maintenance. Column Populator is a command-line script that allows you to update rows of database tables after database schema changes.
This utility can populate values for a new column that corresponds to a newly exposed property, expose values that were previously stored only in the Storage Stream (BLOB) column, and optionally rebuild database indexes and Index- instances that are defined by Declare Index rules. |
| Column chart | A chart that displays values as vertical bars.
You can specify the chart type and subtype for a report definition report by using the Chart Editor. |
| Combo chart | A chart that combines and displays the data from both a column chart and a line chart. A combo chart has either a single y axis (vertical) or two y axes. The two data sets share the same x axis (horizontal).
You can specify the chart type and subtype for a report definition report by using the Chart Editor. |
| Committed hotfix | A permanent part of the system. You cannot roll back a committed hotfix. |
| CommonConfig.xml file | A file that contains information that is necessary to connect to and work with systems that are external to Pega Robot Studio and Pega Robot Runtime. This file is copied to your computer when Pega Robot Studio and Pega Robot Runtime are first installed. |
| Compensating action | An action that allows a custom activity to update the Pega Platform application data to negate the effects of a connector failure. This type of action is an optional feature of Connect SOAP and Connect dotNet rules. |
| Complex question | A survey question that captures information from users in a multianswer format. For example, you can ask users to list their five favorite movies. |
| Complexity score | A numeric value that indicates the variability that is required to complete a workflow, including total applications and screens, unique applications and screens, and the number of steps in a workflow. Higher scores indicate lower levels of complexity. |
| Compliance score | A weighted score for each application that measures overall compliance with Pega Platform best practices and guardrails. This score is available on the Guardrails landing page. |
| Compliance | Rate of compliance with regulations, scripts, policies, procedures, and full disclosure rules. |
| Component ruleset | A ruleset that contains rules that are designed to define reusable applications or functionality that executes as embedded within an object. When a component ruleset is installed in multiple systems, the class of the object might vary from system to system. |
| Composite portal | A user portal that is defined by a collection of harnesses that each references a screen layout. Each harness defines an entire portal window. |
| Composition grid | A Data Designer grid that lets you review and manage the selected data type's properties. The composition grid appears on the Definition tab of a data type. |
| Computer telephony integration | Computer control and functionality applied to telephony hardware. |
| Concrete class | A class that is displayed anywhere below the top level of the class hierarchy, often near or at the bottom of the list. There are several types of concrete classes: internal classes, external classes, rule types, and work types. |
| Configuration bundle | A set of application-specific configuration definitions. You can use a configuration bundle to store historical configuration information or export the configuration bundle to a JSON file to port the definitions and values to other instances of the application. |
| Configuration definition | A rule that you can use to set an application-specific parameter. You can export a set of all configuration definitions and values to a configuration bundle JSON file. |
| Connection pooling | A cache of database connections that are maintained so that the connections can be reused when future requests to the database are required. Connection pools are designed to improve performance by minimizing the opening, closing, or maintaining of a separate database connection for each requestor. When you use connection pooling, a database connection is returned to a pool when it is no longer needed by a requestor and made available for future requests. |
| Connector flow action | A task that users perform to move a case closer to resolution. You create connector flow actions when you add a step to the life cycle of a case that collects information. |
| Connector | A means that enables Pega applications to use data and capabilities in remote systems by using standard network protocols while staying within the recommended model.
The term connector is used in the following ways:
- On a flow diagram, a connector is a line that connects two shapes. Typically, connectors leaving an assignment shape represent flow actions. Other connectors might link to a When condition rule.
- On external systems of record, a connector defines and implements an interface between a Pega Platform application that acts as a client and an external system that acts as a server. |
| Constraint | A relationship between values that is always expected to return a true result. For example, if you want to set a status of your business process to Resolved-Completed, you always need to provide a completion date as well. Creating constraints help you maintain compliance and avoid errors in your application. |
| Contact preference | A setting that indicates how a work party wants to be contacted.
For example, some parties might prefer to receive correspondence as email, by fax, by phone, or through mail. The contact preference is always email for users that are identified as a party of the Data-Party-Operator class. |
| Container class | A concrete or abstract class that unifies a set of classes in the PegaRULES database. A container class has a name that corresponds to a class group. A class group, in turn, has a name that matches a class rule. |
| Content Security Policy | A set of directives that is used to control what is displayed in a client browser by informing the browser of the locations that can be used to obtain content. Each directive governs a specific resource type. |
| Corporate governance meeting | A meeting that ensures understanding at a corporate level and provides an overview of all interactions between companies. Corporate governance meetings also review and resolve escalated issues between companies. |
| Correspondence type | A setting that defines whether a correspondence is a printed letter, a fax, an email, or a text message. |
| Correspondence | An outgoing email, letter, fax, or text message that is produced by the system and its users. Correspondence is typically associated with one work item, or a cover or folder, and can include text and images.
Correspondence that is sent to the originator of a work item is known as an acknowledgment. |
| Cover | A parent case of one or more related cases. Typically, one work party, such as the customer party, is present in the cover case and in all of the covered cases that are associated with it.
The covered cases are the children in a parent-child relationship. A cover can be a parent of other cover objects (and their children). Use a case type rule in the cover class to define the covered objects for the parent cover. |
| Credentials | Parameters that authenticate users or external processes that need to access applications, enabling users to log in with appropriate security permissions. Credentials typically consist of a user name and password. The user name is the key to an operator ID instance. The password can be stored in that instance (in encrypted form), or in a corporate directory service, such as the one provided by Microsoft Active Directory. |
| Custom field | An instance of the Index-CustomFields class that has two parts, a name and a value. Associating custom fields with rules provides a flexible way to supplement your application with metadata, such as a change order number or a log file attachment.
Custom fields are not available for Data- objects. |
| Customer satisfaction | A metric that measures how a case was completed as assessed by your organization. Customer satisfaction is a perception of the customer's viewpoint, unrelated to whether your organization performed the work properly or in accord with your standards or industry standards.
Use the standard property Work-.pyStatusCustomerSat to record customer satisfaction. |
| Customer | A work party that typically initiates a case. In many applications, only one customer can be associated with a case. |
| Daemon | A reserved background Java thread that executes as a BATCH requestor type. Daemons behave similarly to agents, but daemons are not defined by a Rule-Agent-Queue rule type, are not full requestors, and operate continuously and automatically. Pega Platform includes the following daemons: License Compliance, Master-for-Agent, Master-for-Requestors, Node, Passivation, and Usage. |
| Dashboard | One of the following UI elements:
- A centralized workspace that displays operational information about your application and key performance indicators, such as the number of assigned items or the average time to resolve a case. A dashboard can include charts, reports, worklists, and other widgets.
- A single webpage that shows the current status and ongoing trends of your organization’s behavior. This data helps you to make informed decisions and guides you to specific investigations or outcomes. |
| Data Designer | A view that you can use to review and manage data types in your application. When you select a data type in the Data Explorer, the data type opens in the Data Designer. |
| Data collectors | Office workers or employees whose job functions are primarily performed on the desktop and whose activities are reported on and summarized by Pega Workforce Intelligence. Data collectors must have Pega Robot Runtime installed on their computers. Pega Robot Runtime collects the information that Pega Workforce Intelligence presents. Data collectors are also called associates. |
| Data element | A pairing of two pieces of information: the name of the data element and the value that is assigned to the data element.
Data elements are stored in memory on a page. |
| Data exploring | A term that denotes one of the following activities:
- Understanding the relationships among your case types, data objects, and fields in your application.
- Browsing and searching for records and instances in the Report Browser. |
| Data instance | A data instance is an instance of a concrete data class, a concrete class derived from the Data- base class. For example, a work queue is an instance of the Data-Admin-WorkBasket class. |
| Data mapping | A table or array that associates data fields that are received from or sent to an external application with properties or other sources or destinations in Pega Platform. Data mapping is defined in service and connector rule forms. |
| Data model | A collection of entities and attributes that describes the objects that are modeled in an application, and their relationship to each other. |
| Data page | An entity that you use to cache data on demand to a clipboard page for use by one or more applications. A data page rule defines the source, scope, refresh strategy, editability, and structure of the cached data. Data pages were previously known as declare pages. |
| Data record | An instance of a data type that is stored for your application.
For example, customer records include data specific to each customer, such as the name, email, phone number, and so on. You can manually create data records or import a set of existing data records in Data Designer. Use the Data Type Explorer to view the list of supported data types in your application. |
| Data reference | A type of field that you configure on a form. At run time, a data reference displays a list of data type instances, or data records. |
| Data source | Any source of data that an application uses, such as a connector, report definition, or lookup. Data sources are referenced in data pages. |
| Data table | A data storage that is superseded by the local data storage feature. Click Convert for each data table that is displayed on the Data Tables landing page to convert it to the new format. |
| Data type | A characteristic that defines and holds data for your application. For example, the Customer data type might be used to manage customer contact information. It might include the customer's name, email, phone number, and so on. Data types are managed using the Data Explorer. |
| Data | Information that is captured during the life cycle of a case. |
| Data- base class | A top-level abstract class that defines and contains static data and cumulative data. Pega Platform applications often retain essential and frequently used data in the PegaRULES database, which is organized into concrete classes that are derived from the Data- base class. |
| DataGrid control | (Deprecated) A control for presenting data in rows and columns. Update an existing DataGrid to a Grid control. |
| Day 1 Live Plan | A deliverable that describes the difference, from the business’s perspective, between the current state and the moment when the Minimum Lovable Product (MLP) goes live. |
| Deadline | An interval of time that is defined in a service-level agreement. A deadline is the required resolution time for an item, such as a case or stage. |
| Decision data definition class | A class where you define the set of decision properties. You can add these properties to be displayed on the Decision Data form. |
| Decision table | A table that consists of one or more rows that contain test conditions and a result to return. Evaluation proceeds from top to bottom; when the conditions in all cells in a row are true, the result of that row is returned. If no row returns a value, the table provides the Otherwise row result. Decision tables are instances of the Rule-Declare-DecisionTable class. |
| Decision tree | A rule that defines a series of tests on property values to allow an automated decision. Decision trees capture and present business logic in the form of one or more if/then/else conditions. Decision trees are instances of the Rule-Declare-DecisionTree class. |
| Declarative expression | An expression that helps you configure your application to automatically update property values. By setting up declarative expressions, you define a computational relationship between properties.
For example, you can define the total order amount as the sum of all line items. |
| Declarative network | An internal data structure that defines the relationship between properties whose values are automatically (declaratively) calculated based on changes to other property values. You can configure and visualize complex relationships by using the declarative network display, which shows the target property and all potential input that might affect its final value. |
| Definition of Done | The criteria that developers must meet before they declare that their development work is complete for user stories. |
| Delegated rule | A rule that is visible to a specified access group. Rule delegation facilitates rule management outside of the development environment.
A delegated rule can be a paragraph, decision table, data type, correspondence, map value, or data type. |
| Delivery Handoff meeting (Sales-to-Service transition) | A meeting that ensures that Pega and partner project teams prepare effectively by knowing what has been sold and what is expected in the delivery. This meeting must be held during the end of the Discovery phase and has to provide continuity from the Discovery phase to the project team. |
| Deployment Manager | An application that provides a low-code, model-driven experience to configure and run continuous integration and delivery (CI/CD) workflows for your application. |
| Deployment level | A stage which a Pega Robot Studio solution goes through as it moves from development to production. The first and last stages, Development and Production, are built into the system for you. You can define any intermediary stages that you need, such as stages for testing and staging. |
| Design Sprint | A five-day design thinking process for answering critical business questions through design, prototyping, and testing ideas with customers.
For more information, see
https://community.pega.com/knowledgebase/articles/pega-express/design. |
| Design thinking | Design thinking is a human-centered approach to innovation that draws from the designer's toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success. (IDEO Definition) |
| DevOps | A set of practices that bridge application development and operational behavior to reduce time to market and create a standardized deployment process so that you can deploy predictable, high-quality releases. |
| Dialed Number Identification Service (DNIS) | A feature of 800 or 900 lines that identifies the phone number that the caller dialed to reach the attached computer telephony system. |
| Digital Experience API (DX API) | A way of structuring your technology and systems to support customer and business outcomes, which is part of the Center-out approach to business architecture. |
| The ability to directly and visually capture business outcomes while improving the way business and IT collaborate to achieve them. The Pega Express methodology encompasses Pega delivery methodology, and DCO is a tool and approach that supports it. |
| Directed inheritance | A method by which a class inherits characteristics directly from a specified parent class, regardless of any defined pattern inheritance.
For example, the PegaSample-CustomerRequest class (part of the PegaSample sample application) employs directed inheritance, and its directed parent class is Work-Cover-DupByCus. Based on pattern inheritance, the parent class is PegaSample. |
| Directive | (Deprecated) A message for a JavaScript container. For improved performance and debugging, use JavaScript tags to develop new applications. |
| Discover gadget | A visual representation of the layers of your application. By seeing where an item exists in the application, you can understand whether an object is inherited from another layer or comes from your own definition. From that visualization, you can click a layer to open the application rule. The Discover gadget is displayed for case processes in Dev Studio and App Studio, and for sections (including work areas and views) in App Studio. |
| Discover | The first phase of the Pega Express methodology that is typically conducted as part of the sales cycle or during the development of a business case. The Discover phase includes a decision on the journey to build, agreement on the Minimum Lovable Product (MLP), graphical representation in a service blueprint, and project readiness to start. The output is an agreed scope, and a delivery team and all the necessary infrastructure necessary is in place. |
| Division | The middle level of the three-level organization hierarchy that is available for use in every application. Divisions are below the organization level and above the organization unit level.
Divisions are referenced in organization units and in operator ID instances. A division is an instance of the Data-Admin-OrgDivision class. |
| Document Application tool | A tool that captures information and images from any application in your stack and generates customizable product overview and gap analysis documents that you can share with stakeholders. This tool was previously called the Application Document wizard. |
| Dot notation | Syntax in an expression that precedes the name of a property with a period. You can use dot notation to reference single-value properties and complex properties.
For example, .CurrentSalary and .Customer.FirstName are both valid user inputs in a field that supports expressions. |
| Draft mode | A setting on the Flow form that supports references to rules that are not yet defined or completed. By enabling draft mode, you can choose the order in which you develop your flow and its dependencies. |
| Drill down | An icon that you can use to move through the hierarchical view of data, from general to more specific data, to find the data that is relevant to the areas that you supervise.
For example, you can drill down on the Summary and Analysis pages. |
| Dual-tone multi-frequency signaling (DTMF) | Touchtone dialing. In DTMF, pushing a button sends a combination of two tones: one high-frequency tone and one low-frequency tone. |
| Duplicate case | An open instance of your business process that is very similar to a case that already exists and both cases are designed to reach the same result. For example, if your business objective is to review loan requests, your application creates a duplicate case when a user creates the same request twice.
To maintain good quality of your business processes and save time, avoid researching, updating, and resolving both cases by identifying and eliminating duplicate cases. For example, you can identify all loan requests that include the same customer email address. |
| Dynamic Select control | An optional feature that you can add to user forms (through HTML rules, harnesses, or sections) and other HTML forms to make user input faster. The Dynamic Select control is deprecated, but supported. Use the Drop-down control (pxDropdown) instead. As a best practice, upgrade Dynamic Select controls to Drop-down controls. |
| Dynamic layout | A layout that organizes UI elements on the screen in a variety of ways. For example, you can use dynamic layouts in forms to determine item and label placement depending on the size of the screen that you use, such as desktop monitors or mobile displays. You can also define how dynamic layouts behave on mobile devices to improve readability by defining how much content is displayed on the screen at a time. |
| Dynamic system setting | A data instance that is used to change the performance of Pega Platform. Dynamic system settings that have Pega-Engine as the owning ruleset and key names that start with prconfig are known as prconfig settings.
For easier maintenance, create a dynamic system setting data instance and set the value of the data instance to a prconfig setting, instead of directly updating prconfig settings. |
| Dynamic view | A standard form that is automatically managed by your application for each case type that you define. A dynamic view displays fields from your data model during different events, such as creation and resolution, in the life cycle of a case. |
| EForm file | A file that contains a PDF file that is used as a template for generating new PDF documents. The corresponding eForm map specifies the relationship between the form fields in the PDF form and properties in your application. The eForm file and eForm map rule forms constitute the SmartForms feature. |
| Efficiency score | A numeric value that indicates the amount of waste in a workflow. This score compares production and other work time to total time. Higher scores indicate lower levels of waste. |
| Embed- base class | A parent to other classes that, by design, should not be used as top-level structures. No saved instances of concrete Embed- classes exist. A class that is derived from the Embed- base class is used only for embedded clipboard pages.
Developers can create rules that apply to embedded instances and execute the clipboard instances of the Embed- class, but the embedded instance is either saved as a page within another object or is not saved at all. |
| Embedded page | A clipboard page that is a child of another page. |
| Empathy mapping | A technique that ensures a human-centered focus during a Design Sprint. Users are interviewed and observed in the context of their environment as they perform real tasks; the user narrates what they are doing as they complete the task, the observer asks questions to gain insight into the discrete steps and get to the underlying thought process. |
| Employee focus | A measure of how employees allocate their time and actions during the day. This usually falls into one of the following categories: Production Work, Other Work, Non Work, Idle, and Unknown. |
| End-to-end (E2E) testing | A testing approach that systematically tests all paths through a Microjourney to prove interfaces, low-level user acceptance criteria, and Microjourney-level acceptance criteria. Testing may be done on incremental chunks of the Microjourney as they are completed in sprints and then on the full E2E journey after its completion. |
| Entity | A piece of data that can be extracted from text, including names, locations, amounts, IDs, and so on. |
| Entry point | A point in a flow that controls to which places in the flow users can move. Assignments and subprocesses are commonly marked as entry points, because these are places in a business process that require human input. |
| Epic | A description of a capability that takes more than one sprint to implement. |
| Escalation | An action that your application runs to facilitate faster resolution times, based on a specified service-level agreement. For example, you can send correspondence to interested parties when a case is five days overdue.
Use the Service-level agreement form to configure escalation behavior in your application. |
| Executable | A computer file that contains an application that you can run. |
| Execution context | A single run of a Pega Robot Studio automation. Each execution context is started with an event, such as a button click. Any links started as a result of a button click are part of the same context. If an automation calls another automation, the links executed in the second automation are part of the same context. Any child threads that are created are also part of the same context. |
| Expected employee hours | Associate’s hours for a specific workday. This information is used to complete the picture of associate focus for a day. |
| Exposed property | A single-value property that is stored as a column in a database table, in addition to the Storage Stream BLOB, to enhance record selection operations in reporting. Exposed properties are also referred to as "optimized properties." |
| Expression | A single line of Pega Platform syntax that provides computation of a value by using arithmetic operators, logical operators, Java operators, standard functions, and properties.
On many forms, you can start the Expression Builder to provide prompting and guidance while entering an expression. |
| Extension point | An activity (or other rule) that is designed to be overridden to meet application needs. Many such rules are empty stubs that contain no steps. Typically, the overriding rule is in a derived class. |
| External assignment | A task that an external user performs in response to an email message. By collecting information from stakeholders who are outside your organization, you can broaden the scope of your application. |
| External class | A concrete class (an instance of the Rule-Obj-Class rule type) that corresponds to a table in an external relational database, rather than to a table or view in the PegaRULES database.
You can create an external class and associated properties by using the Connector and Metadata wizard or the New External Database Table Class Mapping button on the Data Model Classes and Properties landing page. |
| External data entity | A class that is a data type of the current application and appears in the Data Explorer. Records of the data type come from an external data source. |
| External data source | A data source of the connector type, a lookup with an externally mapped Applies to class, or a report definition with an externally mapped Applies To class. |
| External user | A person outside your organization who processes external assignments. External users do not log in to your application because they receive an email with a direct link to an assignment instead. |
| Family name | A text string that consists of all the key parts concatenated with exclamation points, excluding the Applies To or class name portion.
For example:
- Two activities named Work-MyCo-Mortgage.Reopen and Work-MyCo-.Reopen both have REOPEN as the family name.
- When a binary file rule has three key parts defined as webwb, pegalogo, and gif, the family name is WEBWBPEGALOGOGIF. |
| Favorite | A link to a rule or data instance. Use a favorite to quickly find items while working in Dev Studio or the Case Manager portal. You can create favorites that are visible to your operator exclusively, another operator, or all operators within a specified access group. |
| Feature | A capability that you implement in your application. By defining features that are linked to rules and work items, you can improve the traceability of capabilities to their respective implementations. |
| Federated Access Manager (FAM) | An application that Pega staff can use to request access to a company system and to a Pega facility for themselves or another person. |
| Federated Case Management (FCM) | A centralized database where each local application in a federation publishes its own cases and data. FCM uses the Pega Web Mashup connectivity to link Pega Platform applications in a federation.
Users in a federation work in their local application portal, which can display cases and assignments from other applications in the federation. |
| Federated Case Management Repository (FCMR) | A centralized repository for cases and work performed by users in a federation. The FCMR consolidates work items and makes them available to all users in the federation. |
| Field-level auditing | A method of tracking changes over specific fields in your business process. You can analyze progress and maintain compliance as to who made the changes and when.
For example, in a shipping order process, you can track how a shipping address changes, and who and when performs the change. In case of any issues with the shipping address, you can view details about the change and further investigate the problem. |
| First call resolution (FCR) | See First Contact Resolution. |
| First contact resolution | Percentage of interactions resolved on the first interaction and thus not requiring a repeat interaction initiated by the consumer. |
| First touch resolution (FTR) | Percentage of interactions that are resolved during the initial interaction by a single CSR, also known as "transfer rate". |
| Flow action | An activity that controls the way that users interact with forms that they need to fill in to complete their tasks. The flow actions associated with a task determine the choices that are available to users as they perform the task.
For example, in a damaged goods claim process, the buyer can select to have the goods either reimbursed or replaced. |
| Flow error | An error condition that prevents a flow execution from continuing. An example of a flow error is if the flow references a rule that is not found at run time.
Click Dev Studio > Processes and Rules > Processes > Flow Errors to view the flow errors in your current application. |
| Flow marker | A rule of type Rule-AutoTest-Case.RunRecursiveTestSuites that supports the testing of flows. If an operator has the AutomatedTesting privilege, that operator can create and use these flow markers.
Flow marker rules belong to a RuleSet and version, but they are not included in the Application Explorer display. |
| Flow shape | An element that represents a task that a user or application completes as part of a business process. Shapes are differentiated by color, symbol, and name. |
| Flow | A graphical representation that models a business process in your application by using graphical shapes and connectors to define a sequence of events. You can edit a flow in the life cycle of a case or by using the Flow form. |
| Folder | A case in a concrete class that inherits from the Work-Folder- class. A folder object holds a collection of one or more cases, including covers and other folders, to provide access for analysis and reporting. |
| Form | A view of your data that displays information or collects input from users as they create, update, and resolve cases in your application. Open your case type from the Application Explorer to access the options for configuring a form. |
| Forward chaining | The automatic propagation of changes in one property value to changes in other property values or to indexes. This process only operates when the source properties are not marked as invalid. If a property has an associated message, forward chaining halts. |
| Fragment | Text or HTML markup that is expected to have broad reuse. You can reference a fragment in the Include JSP tag to cause the system to incorporate the fragment rule into other HTML or correspondence rules as they are processed.
A fragment is an instance of the Rule-HTML-Fragment rule type or the Rule-Corr-Fragment rule type. |
| Framework application | An application that you can extend and modify to create implementation applications for a specific organization, division, or organization unit. |
| Framework class | A class that defines a common work processing foundation that you extend and modify as implementation applications for an organization, division, or organization unit.
Framework classes belong to the framework layer of an application. |
| Framework layer | A layer that contains reusable application elements and provides an application that you can use as the basis for many production applications. |
| Friction score | A numeric value that indicates how much interaction is required to complete a step or workflow. This score is based on the steps, key presses, clicks, and scrolls in a workflow. Lower scores indicate higher levels of friction. |
| Function | An element that defines a Java function and makes the function callable from activities and expressions. A function is an instance of the Rule-Utility-Function rule type. |
| Funnel chart | A chart that displays the progressive reduction of data as it passes from one phase to another.
You can specify the chart type and subtype for a report definition report by using the Chart Editor. |
| Gauge chart | A chart that displays a single value as a meter reading. If the gauge chart includes thresholds, a manager can quickly review the chart to determine whether the value is within a targeted range.
You can specify the chart type and subtype for a report definition report by using the Chart Editor. |
| Geolocation tracking | A method of capturing the longitude and latitude coordinates of case workers as they process a case. When you enable this feature for a case type, you can view the location of the case worker in Google Maps.
You must include the UI-Kit-7 ruleset in your ruleset stack to use geolocation tracking in your application. |
| Get Next Work | A function that helps you define the order in which users work on open assignments. Each time a user completes an assignment, Get Next Work selects another assignment for that user based on a set of criteria, such as user authority, skills, or urgency of the work.
For example, if a CRS is skilled in credit card compliance, the Get Next Work function might assign that person to first work on cases which require that skill. By choosing the best, most appropriate assignment to work on next, your application can promote user productivity, timeliness of processing, and customer satisfaction. |
| Global resource setting | A property value on a data page that is referenced through specific syntax on a connector rule, or by a data instance that supports a connector. A global resource setting can reference any property of the appropriate type on a data page.
The use of global resource settings for references to external systems, rather than fixed text values in rule forms, provides greater flexibility for changing values such as port numbers, addresses, and URLs. |
| Goal | An interval of time that is defined in a service-level agreement. It is the suggested resolution time for an item, such as a case or stage. |
| Grid Controls | Controls that display the relationships between large quantities of data and provide a convenient interface for editing or adding to that data. Grid controls appear in Harness and Section forms. For large or complex data displays, use the Grid, Tree, and Tree Grid controls. |
| Grid layout | A layout that displays values of a Page List, Value List property, data page, or a report definition in a spreadsheet format. When a grid is bound to a data page or report definition that accepts parameters, and the parameter value uses a property reference, the grid is automatically refreshed whenever the property value changes. The grid is created dynamically and has as many rows as needed to display the requested data. The grid can be read-only. |
| Guardrail compliance | The Pega Platform feature being used influences what constitutes guardrail compliance. Generally, guardrail compliance avoids the use of custom code in the application model. This is important because the features of Pega Platform are designed to protect the security of an application, and often times, cannot be adequately applied to custom written code. |
| Guardrail | A setting that determines which elements in your application do not comply with Pega best practices. For example, guardrails typically flag custom components that require manual changes during upgrades. You must respond to guardrail warnings to ensure that your application meets the latest requirements for efficiency and ease of use, and save development time.
By following the guardrails, you can secure a good compliance score. High compliance scores are a sign that the application is well-designed, efficient, and easy to expand. |
| Guided tour | A sequence of tour stops that provides information, tips, and instructions about the key features in your application. Use the guided tour form to define the content that is displayed in each tour stop. |
| Handle | A permanent, unique identifier for a class that includes certain key parts, and the creation date and time of a single instance for rules and some classes. A handle is sometimes known as an internal key.
The pzInsKey property holds the handle value for an object. The pzInsKey property is undefined until you save the object. |
| Harness | A container that organizes the content and structure of a page in the user interface. The layout of a harness is defined by a template. For example, you can base a portal harness on a template that divides the portal into three separate areas: a header, a navigation pane, and a large content pane for displaying documents. |
| Headless application | An application that uses flows and other elements, but either does not have a user interface or presents forms, assignments, and other information to users through an external mechanism.
An application that delivers straight-through processing can be named headless. |
| Heat map | A graphical representation of data where the values taken by a variable in a two-dimensional map are represented by colors.
From the Heat Map tab on the Application Inventory landing page, you can view a heat map of the rule types in your application, summarized by category. |
| Hierarchy | A definable structure that you can use to organize your workforce into logical groupings and reflect who reports to whom. Pega Workforce Intelligence uses the hierarchy that you define for reporting and analysis. You can label the levels in the hierarchy to match the company's business structure, such as divisions, departments, supervisors, managers, associates and so on. |
| Historical processing | A feature that enables an application (for the current requestor) to operate based on how rules were defined on a specific date. Such processing is useful to reconstruct past behavior or apply past policies.
Historical processing applies to an entire ruleset version, not a single rule. |
| History type | A setting that identifies the event that corresponds to a history instance for a case. The history type is recorded as a single letter value in the pyHistoryType property. |
| History- base class | An abstract class that is parent to numerous other classes that define cumulative tracking data about the objects in your application, including rule instances. History instances identify the date, time, and user who updated a work item, rule, or other object in the system. |
| Hotfix catalog | A repository of information about all Pegasystems hotfixes. The catalog describes the changes in each hotfix and is used for dependence checking.
Obtain the latest hotfix catalog from the Support area of Pega Community. |
| Idle time | One of the two characteristics:
- The time that a CSR is unavailable for servicing customer requests while they are working.
- The amount of time that is spent idle, with no input from the associate, shown as both an amount and a percentage of total time. This value is defined by the Workforce Intelligence team. |
| Idle | An extended period of time during which the associate does not interact with the keyboard or mouse. |
| Implementation class | A class that defines the extension, reuse, and specialization of assets in a framework class layer to meet the business requirements of an organization, division, or organization unit.
Implementation classes belong to the implementation layer of an application. |
| Implementation layer | A layer that contains application elements that are specialized for a specific business audience or purpose. The contents of the implementation layer extend the elements of the framework to create a composite application that targets a specific organization or division. |
| Implementation methodology | An adaptable process framework for managing an application development project. When you align your organization's approach to project management with an implementation methodology, you can quickly define and implement the objectives of your application. |
| Inbound email processing | A utility for managing the email messages that you receive in your application. When an email message arrives, Pega Platform reads the message, pulls it into your application, and creates a work item.
For example, you can configure your application to create cases based on the information in the body of inbound email messages. |
| Index | A value that identifies one element (or member) of an aggregate data structure. These indexes are sometimes called subscripts.
In addition, an index is a PegaRULES database feature that provides faster access and improved database performance. Use Declare Index rules to add and delete index objects. |
| Index- base class | An abstract class that is the ancestor of other concrete classes that define indexes, sometimes called secondary or alternate keys, that are stored in the PegaRULES database. These alternate keys are used by the system to speed searches and provide sorted lists to help users find instances (such as work items) where the external key is not known but some other fact or property is known. |
| Indirect page | A page that the system finds by searching the clipboard at run time. The page reference to an indirect page starts with the keyword prompt followed by the page name.
This type of page is deprecated but still supported for rules that used this feature before Pega 7.1. |
| Inheritance | A mechanism in which one object inherits the properties of another object.
In Pega Robot Manager, inheritance applies to package assignments. For example, when you join a department, you inherit the package assignments and configuration settings made for that department. Conversely, if you leave that department, you are no longer associated with those assignments. |
| Insight | A notification that alerts you to ways in which you can improve workflows and paths by highlighting certain events that occur in workflows or paths or both. For example, an insight might note that there is excess waste in several workflows, and recommend that you review the Waste tab to determine ways to lower the amount of waste. |
| Instance | A durable, potentially permanent, saved representation of a concrete class that is stored in the database. An instance corresponds to a row in the relational database, or to a record. An instance consists of properties and values, and some of these property values form a unique key to the instance. |
| Instruction | A command that initiates an action for a row on an activity form. The instruction keywords are Call, Collect, Branch, Queue, Rule, and Java. |
| Integration Designer | A tool that shows all the business objects, data views, object dependencies, and external systems in an application. |
| Integration service | A facility that supports interfaces between Pega Platform and external systems. Integration services include both connector and service capabilities.
They are supported by the Pega-IntSvcs ruleset. |
| Integrator shape | An activity that connects your application to an external system. For example, a work item reaching an integrator shape in a flow diagram might run an activity that automatically queries an external database to obtain current prices or current inventory levels. |
| Intelligent routing | The process of comparing the characteristics of a new assignment with the characteristics of the workforce to route the assignment to the most appropriate operator. Like a supervisor who thoughtfully distributes work to their team, intelligent routing in your application can significantly affect the productivity and throughput of a work group. |
| Interaction.xml file | A file that defines the contexts, activities, and plug-ins for the implementation that you are designing. |
| Interactive chart | A chart that provides options, such as a slider control, for increasing and decreasing the level of detail that is displayed. Summary view reports can include interactive charts. |
| Interactive voice response (IVR) | An interactive phone system that can respond to a caller input (voice or keypad) and either complete predetermined services or assist in properly routing the call to the appropriate CSR. An older term for an IVR is voice response unit (VRU). Common vendors include Avaya, Genesys, Syntellect, and Nuance. |
| Interest page | The primary page that against which a flow runs. An interest page might be an embedded page of the case, or it might be the case itself. |
| Interested party | A work party whose role is to receive information about a case. This party does not actively participate in processes or directly influence the outcome of the work.
For example, the spouse of a cardholder can be an interested party in a credit card dispute.
By default, you can associate more than one interested party with a case type in your application. |
| Internal class | A concrete class (instance of the Rule-Obj-Class rule type) for which instances are stored in the PegaRULES database, rather than in an external database. The properties @baseclass.pzInsKey and @baseclass.pxObjClass are defined for every internal class. |
| Internal key | The text value of a reserved property @baseclass.pzInsKey of an instance. This property is defined in the ultimate base class and is available in every class. This value is also known as the handle.
For rule instances, the date and time that the rule was first saved becomes part of the internal key. As a result, the pzInsKey property is undefined until the new rule instance is saved and committed. |
| Issues per contact | Average number of issues that are handled per contact based on the number of processes that are run. |
| Iteration | The process of repeating the same set of actions on any given list.
The Split For Each shape in a flow and the ForEach JSP tag in a stream rule both support iteration. |
| Java Object Mode | A property that contains references to Java objects. The Java Object property contains a reference to an instance of a Java object.
The Java Object List and Java Object Group properties identify arrays of Java objects, or an unordered set of Java objects. These properties are primarily useful within the Java steps of activities and in function rules. |
| Java Property Mode | A property that supports the Java pages feature, which enables applications to interact with external Java objects as though they were pages and properties on the clipboard. |
| Java identifier | An identifier that must start with a letter, and contain only letters, numbers, and hyphens.
Java identifiers in Pega Platform are similar to those defined in the Java language specifications, except that a hyphen (-) is displayed in place of an underscore character (_). |
| Journey map | A way of capturing the end-to-end process in a format that helps align the team around the end objective and allow the journey to be broken down into stages and steps, and then user stories. |
| Journey | The series of interactions between a customer and an organization that occur as the customer pursues a specific goal. |
| Key part | One to three fields that you specify on the Create form for every rule instance and data instance. The class rule determines the properties that form the key part for objects of a specific class, and in what order. If an object has only one key part, that value is often called the name of the object. |
| Keyring file | A keyring file is an encrypted file that contains the user name and password needed to access the PegaRULES database. The keyring file is usually named pegarules.keyring.
If your application server supports Java Cryptography Extensions (JCE), you can identify an encryption algorithm in the cryptoelements of the prconfig.xml file to create the keyring file. |
| Keystore | A file that contains security certificates. To support Web Services Security and outbound email security, you can attach a keystore file to a data instance of the class Data-Admin-Security-Keystore. |
| Keyword | A type of entity that looks for verbatim matches of a word. Examples include salutations (Mrs., Dr.), units (feet, lbs), or days of the week. |
| Landing page | A single source of information that presents categorized content, such as tabs or tools. You can access information on a landing page with focus on a single category that you want to select. A number of landing pages can be accessed right at the launch of your application.
For example, on the Application Quality landing page, you can view the health of your current application and identify improvements to make before you deploy an application. |
| Language pack | A collection of language-specific rulesets that support localization of applications. A language pack provides field value rules that localize buttons, prompts, and labels. |
| Layout group | A container that displays a set of content and allows you to responsively present information that is normally shown within one control type. A layout group can contain any number of dynamic layouts, column layouts, repeating dynamic layouts, or other layout groups. |
| Lead System Architect (LSA) | An application developer who provides technical leadership in design and project management tasks to an application development project. |
| Lean usability testing | A fast and effective way to test designs with a small number of users from your target audience. Embracing the lean principle of moving from uncertainty to confidence, designs are tested iteratively throughout the delivery cycle. |
| Least privilege access | The practice of restricting access rights for users and other requestors to only the data and application functions and features that are absolutely required to perform their job function. |
| Legacy agent | An agent where the Queue Mode setting on the Schedule tab is set to Legacy. Legacy agents do not use queues; instead, they process each item to completion in a single pass.
Agents created before version 5.4 appear as legacy agents in later versions until they are upgraded to Standard. |
| License Compliance | A tracking and reporting system that provides evidence that operations of the system comply with provisions of the Pega contract and software license. An automatic background thread known as the License Compliance daemon supports data gathering for this functionality. |
| Lightweight list | A run-time format for the Code-Pega-List page that supports the report display. This format is more efficient than the default format but does not support certain kinds of processing.
You can specify that results display in a lightweight list for Obj-Browse methods and lookup lists. Report definitions automatically use lightweight lists. |
| Likelihood | A value between 1 and 100 that is an assumed or known probability associated with a flow action. For example, a likelihood of 66 on a flow action labeled Accept means that users completing an assignment linked to that flow action are expected to choose the Accept flow action two out of three times. |
| Link- base class | An abstract class that is an ancestor class to other classes and identifies paired object instances in your system. |
| Linked property | A single-value text property that has values that are expected to match the key of an instance of a concrete class. In certain user interface and other rule configurations, linked properties can improve performance and eliminate the need to create a special-purpose activity.
You can reference properties of a linked object, retrieved by a linked property, in a rule form or expression using the syntax .LinkedPropertyName.ObjectPropertyReference. |
| List view rule | (Deprecated) A rule that defines a list view report that displays unsummarized or detailed data.
Re-create the custom list view reports that you need as report definitions. The last version of Internet Explorer that list view rules support is Internet Explorer 11. |
| Load balancing | A technique or facility that attempts to provide an even backlog of demand across multiple processors or production facilities. |
| Local data storage | A feature that lets you store data records for a data type without having to manually create or maintain database tables.
In the Data Designer, you can access the local data storage on the Sources tab for the data type. Use the Local Data Storage wizard to create a local data source. |
| Local flow action | An optional task that users perform while processing a case. This type of flow action does not move a case closer to resolution. |
| Local variable | A text string that is stored in a Java StringBuffer object rather than in a page structure. Local variables require less memory and can be accessed with less computer overhead than parameters. Activities can access local variables. |
| Locale | One of the standard codes in the format aa_BB_CC, where aa represents the language and _BB or _BB_CC represents a country variant suffix. Every user session has a locale setting that can affect the language presented by the Pega Platform user interface when displaying or entering dates, times, and monetary values. |
| Locatable page | (Deprecated) A page that reduces the need for the page to be explicitly named in the rule. At run time, the system uses backward chaining and an activity with type Locate to find and add the correct page to the clipboard. Locatable pages can be used with Constraints and Declare Expression rules.
Locatable pages are not supported; use a data page instead. |
| Lock | A mechanism that secures an object or a ruleset version against changes. You can lock ruleset versions, instances of a concrete class, and the Rule-Application rule type. |
| Log- base class | An abstract class that is the parent of several standard classes that record cumulative chronological data about events in the system. You can access Log- classes and (for concrete classes) their instances through the Application Explorer. For concrete classes that are derived from the Log- base class, the property @baseclass.pxCreateDateTime is usually the final (or only) key part. |
| Lookup list cache (LLC) | A cache of recent search results that are available for display and reuse. This cache includes the results of certain reports and other searches that users run, which are saved automatically. |
| Map value | A rule that converts one or two input values, such as latitude and longitude numbers, into a calculated result value, such as a city name. The rule uses ranges for the input values and a matrix to look up the result. |
| Map | A chart type that displays geographical data distributed by categories, regions, or entities on the map. For example, you can show sales activity by state, by country, or by continent, depending on the map that you select and the data that is available in the report.
On the Maps tab of the Reporting Settings landing page, you can set default mappings between specific maps and the properties of specific classes. |
| Method | A Pega Platform method, distinct from a Java method. An operation that can be performed by one step of an activity ( Rule-Obj-Activity rule type), or by a Parse Structured rule ( Rule-Parse-Structured rule type). |
| Microjourney | One of the business outcomes included in a journey. |
| Minimum Lovable Product (MLP) | The first release of a product delivered with the least amount of effort that gives the customer something they would love, focusing on a major pain point or opportunity that provides a real benefit to the customer. Minimum Loveable Product can also be extended to subsequent releases. The main value of an MLP is to start with something small that will increase customer satisfaction. This is different from the Minimum Viable Product (MVP) which typically delivers a functional but scaled-down product that aims to relieve a number of pain points all at once but may not necessarily increase customer satisfaction. |
| Missing hours | The difference between the hours an associate or team was expected to work and the actual hours captured by Pega Workforce Intelligence. For example, if an associate was expected to work 40 hours and only 36 hours were captured, that associate would have four missing hours. |
| Mixin | A reusable style pattern defined in the skin. Mixins can define a combination of reusable text, border, or background styles. |
| Mobile Preview | A set of interactive icons that allows you to emulate the appearance of your application on different devices and orientations. Use this tool to understand how your user interface is displayed on a full screen, laptop browser, tablet, or phone.
To enable Pega Mobile Preview, select Mobile preview from the operator menu in the Case Manager and Case Worker portals. |
| Mobile | Tools to develop apps that work on a wide range of mobile devices. By building native apps that users can install on their Android and iOS devices, you can use mobile capabilities and improve the user experience.
For example, Pega Mobile users can access their content at all times, which helps them be productive regardless of network connection status. |
| Modal dialog box | A form to complete or a statement to acknowledge that opens in its own window. Users cannot continue with other work until they submit the form or dismiss the modal dialog box. A flow action provides the sections that contain the fields that the user must complete. |
| Modal flow | Representation of a process in a series of modal dialog boxes. The modal dialog boxes display only action sections; harnesses are not displayed. You start modal flows by clicking button, link, or icon controls, or from context menus or menu bars. When the flow starts, you cannot continue working in the main user form until the modal dialog box closes. |
| Named user | A classification of an operator ID that is used in the License Compliance facility. Typically, an operator ID instance identifies a named user if the License Type field on that tab is set to Name. |
| Native control | A control in the application that you are automating. |
| Navigation pane | The left panel of a portal that provides access to data and tools that are relevant to your role. |
| New Application wizard | A tool that uses customizable application types to create applications. After you specify the required information in the wizard, the system creates an application with the required case types, data types, access groups, and operators. |
| Node ID | A unique 32-character identifier for each node of the Pega Platform system. |
| Non Work | A defined category of associate focus that indicates the time that is spent in non-work-related applications and websites. For example, this time could indicate that the associate was on Facebook, Pinterest, or some other social media site. Your Pega Workforce Intelligence administrator defines which applications and websites are categorized as Non Work. |
| Notification channel | A communication medium through which the application notifies users about important events. For example, a bank can send push messages to users to inform them about transactions in their accounts. Pega Platform includes desktop, email, and mobile notification channels, but also supports the creation of custom channels, such as those using text messages or Facebook posts. |
| Notify activity | An activity that sends an email as correspondence to one or more of the work parties that are identified in the work item, and reports progress to that party. For example, when referenced in a flow, a notify activity sends correspondence when an assignment is created. |
| Occasional user | A classification of usage for an operator ID instance for a time period, such as a calendar month, by the License Compliance facility. This facility can classify an operator ID as an occasional user during one period, but include the operator in another classification in other periods. |
| Off-computer reason code | A code that defines what the associate was doing away from the desktop, creating idle time on their computer. |
| Open assignment | A task in your business process that has not been completed yet. By analyzing open assignments, you can determine what actions you need to take to resolve a business process.
For example, in a process of reviewing job candidates, an open assignment might inform you to collect personal details from a candidate. |
| Open instance | An instance that is copied from the database to a clipboard page. Usually, an open instance is locked so that only one requestor can update it at a time. |
| Operator menu | A menu that provides access to your operator profile and a number of features, depending on which workspace you are using and your application configuration. |
| Operator profile | A collection of facts and values about the operator and the requestor. Many details are derived from the operator ID instance and other data instances.
To display your profile in Dev Studio or from the Case Manager, Case Worker, WorkManager, or Manager portals, select Profile on the operator menu. The system assembles this information as you log in. |
| Operator | An application user that is identified by the user name, password, and other details. Each operator has a role, such as caseworker or customer service representative, that determines what actions the user can perform. |
| Opportunity Finder | A tool that identifies and presents areas of opportunity for you to potentially increase the efficiency of your organization. For example, using this tool on the Analysis tab can show times when the expected production goal was not met, or when too much time was spent using non-production applications, such as an instant messenger application. |
| Opportunity tag | A label that indicates the default opportunity types. |
| Optimized property | A single-value property that is stored as a column in a database table, in addition to the Storage Stream BLOB, to enhance record selection operations in reporting. Optimized properties are also known as exposed properties. |
| Organization hierarchy | The structure of your organization in three levels. The top level is an organization, for example a bank. The middle level is a division that includes all resources and functions necessary to operate, such as an HR department. The most granular level is a unit that represents a team or a group of related teams, such as an HR payroll unit or an HR benefits unit.
Aligning a user in the hierarchy can impact the management reports, statistics, and application elements that are available to a user. When routing work items, the system considers the user's alignment in the hierarchy to enable efficient and intuitive management of work. For example, you can ensure that the application routes approval tasks only to managers. |
| Organization ruleset | A ruleset that applies to all operators in an organization.
You specify this optional ruleset in the Default Ruleset field of the Details section of the Organization data instance (Data-Admin-Organization class). |
| Organization unit | The lowest level of the three-level organization hierarchy that is available for use in every application. An organization unit is an instance of the Data-Admin-OrgUnit class. |
| Organization | The top level of the three-level organization hierarchy that is available for use in all of your applications. The organizational structure affects the management reports, statistics, and rules that are available to users in that organization. One system can support multiple organizations.
An organization is an instance of the Data-Admin-Organization class. |
| Other Work | A defined category of associate focus that indicates work performed outside of production applications or websites. For example, this category could indicate that the associate was preparing a training class or documenting procedures for new associates. Your Pega Workforce Intelligence administrator defines which applications and websites are classified as Other Work. |
| Overall score | The overall health of the workflow, based on the efficiency, complexity, and friction scores of all paths in the workflow along with other criteria. This score is a weighted average that helps you determine which workflows might require more analysis. |
| Overlay | A container that launches the local action in a panel that overlays the current window. You can dismiss an overlay by clicking outside the overlay area, or through an explicit Display > Close action configured in the local action. Use an overlay to display simple forms or flows. |
| Package | One of the following solutions:
- A file that contains code or a code library that you can import in a library rule or function rule. You can import external Java packages or customer packages (also known as service packages).
- A deployable solution that is ready to be used by Pega Robot Runtime. A deployment package contains two files with the .openspan and .manifest extensions. The .openspan file contains the specific adapter, translators, and custom components that make up the solution. The .manifest file contains a list of the contents of the .openspan file, along with project version information. |
| Page group property | A data structure that consists of an unordered list of zero or more pages, where the sequence of pages is not significant. |
| Page list property | A data structure that consists of an ordered list of zero or more pages, where each page is identified by a numbered subscript. |
| Page message | A text clipboard value that is generated by the system and associated with a page. A typical page message conveys error conditions, progress, and exceptions. |
| Page | A data structure that holds name-value pairs. Pages are stored in the system memory or in the database. Various types of pages are defined in the system, such as data pages that are created when the data is referenced, named and unnamed pages, parameter pages, clipboard pages, and so on.
Every unit of information in an application is a pairing of a name and a value, known as a data element. For example, a data element that stores the email address of a customer has the name "email," and the value "john.smith@company.com." Pages store data elements so that the application can use it to process the case. |
| Panel set | (Deprecated) A configuration of panels (areas) in a harness that support a composite portal. Existing panel sets continue to function. As a best practice, upgrade panel sets to screen layouts. |
| Parent case type | A case type that sums up results of supporting business processes to lead to an ultimate, expected goal. Pega Platform refers to the supporting processes as child case types. For example, if your parent business process is to review car accident insurance claims, then reviewing bodily injury and vehicle damage claims are child case types. By creating parent case types, you can resolve complex and multifactored business processes by reusing smaller, modular child case types. For greater flexibility, you can start working on a child case type only when it is applicable to your current business needs. As a result, you save time and make your application relevant in various scenarios. |
| Parent flow | A flow that contains a shape, such as the Subprocess shape, that calls another flow. You can view the parent flow for a process by clicking the Where am I icon on a case at run time. |
| Participant | A person who is directly involved in a business process, such as a customer service representative (CSR), or a person who does not directly work on a business process but has a stake in the process, such as a manager. Participants can be members of your organization, for example a CSR, and users without an account in your application, such as a customer that creates a loan request though a website. To speed up case resolution and enhance communication, you can create participant categories, so that you can communicate with an entire group at the same time, for example, by sending an email to everyone in a group. |
| Path | A set of variations of the same workflow. Paths allow an analyst to compare process steps between these variations and see what differences have affected any KPIs that the analyst is monitoring. |
| Pattern inheritance | An optional method where a class inherits characteristics from other classes and affects the first steps in the rule resolution algorithm. The name of the parent class is based on an initial portion or substring of the name of the class. Pattern inheritance is set in the Rule-Obj-Class rule. |
| Pega Catalyst | A design thinking (workshop-based) approach for the Discover phase that helps identify the problems that the solution needs to solve and how these desired business outcomes can be achieved. |
| Pega Cloud | A solution that provides services for customers to augment their staff. Pega Cloud supplies the infrastructure, operational support, and life-cycle management to support Pega applications as a cloud-delivered solution. Customers sing up for services through the Pega Cloud service catalog to address their application needs. |
| Pega Express Delivery | An agile and design-centered delivery approach based on successfully delivering a Minimum Lovable Product (MLP) release made of up one or more customer journeys that are quickly implemented. There are four phases: Discover, Prepare, Build, and Adopt. |
| Pega Express test plan | A path through the application that guides the test team towards testing use case by use case, in the order in which journeys, microjourneys, and solution capabilities are developed. |
| Pega Web Mashup | A tool, previously known as the Internet Application Composer (IAC), for embedding a Pega Platform application as a gadget on the pages of a Pega composite application. Pega Web Mashup supports the rendering of user interfaces in the HTML5 document type. |
| Pega Workforce Intelligence administrator | A person who has been set up to administer the Pega Workforce Intelligence application. You must be assigned the Administrator role to view all the options on the Administration tab. |
| Pega Workforce Intelligence analyst | A person who has access to the Dashboard, Summary, Timeline, and Analysis tabs of Pega Workforce Intelligence, and is typically focused on improving processes. The information on these pages is helpful when in automating tasks. You must be assigned the Analyst User role to view the Analysis tab. |
| Pega Workforce Intelligence report user | A person who has access to the Dashboard, Summary, and Timeline tabs in Pega Workforce Intelligence, but not the Analysis tab. Report users can also view the Administration > Shift Updates menu. |
| Pega Workforce Intelligence | A cloud-based analytics solution that is designed to improve the understanding and productivity of your workforce. |
| Pega composite application | A Pega Platform application that is embedded on your company web pages as a gadget, without using a portal rule.
Pega composite applications do not support all operations that are normally allowed in Pega Platform applications. You can use Pega Web Mashup to build and test a Pega composite application. |
| Pega log | A log, also known as the console log or system log, that contains error messages, debug messages, information messages, and Java-related diagnostics that have been created since the server was most recently started. The Pega log uses the naming format PegaRULES-YYYY-MMM-DD.log, where the date portion of the name indicates the date the application server was recently started on the current node. |
| Pega unit testing | A feature that automates the testing of rules. Use unit testing to automate the out-of-the-box Pega features that are available to the delivery team during the Build phase. |
| PegaRULES Log Analyzer (PLA) | A Java program that can parse, consolidate, and summarize logs from the Pega log, the alert log, and Java virtual machine. Use PLA results to identify, diagnose, and resolve issues that might affect performance, stability, or scalability. |
| PegaRULES database | A relational database that holds the rules, data instances, work items, history, and other concrete objects from the internal classes of the Pega Platform system. External classes are not part of the PegaRULES database. |
| Pending status | A status on a work item that indicates that the work item is open, but progress is paused or halted temporarily while the organization is waiting for information, a decision, a signature, or other events from a party outside the organization. A pending status does not alter the goal times or deadline times for the assignment.
Your flows can use the standard router activity named Work-.ToDeferredWorkbasket to place work items with a pending status into a work queue named deferred@org.com. |
| Performance testing | The traditional tests of load, stress, soak, and scale. This testing type is typically performed by the client’s team. |
| Performance tool | A utility that provides server demand statistics for the current user since their login, or since the last time you reset the Performance tool statistics to zero. These statistics include detailed performance information about running activities, when condition rules, and data transforms that you run in your requestor session. You can use these results to tune your rules for improved server performance. |
| Persistent object | An object instance that was saved from a requestor's clipboard into the PegaRULES database. A persistent object can be accessed and used by other requestors and remains in the database after the requestor session ends. Generally, pages can become persistent when they belong to a concrete class, have a non-blank key defined, and have passed validation. |
| Persona | A user type that might interact with your application. For example, in an application for hiring job candidates, you can create personas that represent a hiring manager and an HR worker.
By creating personas, you analyze what people you need to involve in your business process to reach a successful resolution. You also define what channels you need to provide so the users can interact with your application. For example, job candidates can access a recruitment application through a browser-based web channel or through a mobile channel that relies on a mobile app. At the same time, you can set up a second, more utilitarian web channel to accommodate professional users, such as HR workers. |
| Personal ruleset | A ruleset with copies of rule instances. Personal rulesets are used with the check out and check in features. A personal ruleset is sometimes called a private ruleset. |
| Pinned class | A pinned class allows you to access objects across inheritance hierarchies without explicitly switching contexts. Pinned classes are stored by access group for your operator ID and persist between sessions until removed.
To pin a class, add the class to the static Pinned Classes section of the Application Explorer. |
| Portal gadget | A rectangular area on a traditional (fixed) portal, as opposed to a composite portal. Each gadget contains a control with which the user can interact. For example, the worklist area of the worker's home page is implemented through a gadget.
Gadgets are defined through activities that apply to the Data-Gadget class. By creating a portal rule (Rule-Portal rule type), a developer determines which gadgets are visible to which groups of users. Using such rules, you can control the appearance, labeling, and location of gadgets on a portal layout. |
| Portal | An interface that provides users with an organized set of work tools. Users navigate the application, collaborate, and complete work assignments mainly through portals. Typically, you create a separate portal for each user group within your application. For example, you can create a portal for regular employees, and a separate one for their managers.
Most portals contain a navigation menu that leads to various pages and dashboards, as well as a menu for creating new work items. Additionally, portals might also include widgets that improve work efficiency. For example, you can design a portal that has a widget for frequently used reports, which helps managers save time and oversee their projects. |
| Prconfig setting | A name-value pair that affects the operation of the Pega Platform system. Many prconfig settings have a default value. If no other value is explicitly assigned, the default value is used. |
| Prconfig.xml file | A file that defines installation and operating parameters for a Pega Platform node. |
| Precondition | A reference to a when condition rule (Rule-Obj-When rule type) or an expression that is associated with one step of an activity. After the previous step of an activity runs, before the method in the current step runs, the system evaluates whether the rule or expression is true or false, and performs user-specified behavior based on the result. |
| Preference | A setting in Dev Studio that is associated with your operator, or an access group tied to your operator, that you can use to customize your development experience. Some preferences are manually managed, and others are automatically detected and updated by the system. All preferences persist between sessions. |
| Prepare | The second stage of Pega Express Delivery that describes day to day tasks during the first weeks of the project and the expected outputs: a detailed journey map, draft working software in Pega Platform, at least two sprints of user stories and effective governance structures. The goal is a more detailed understanding of the target software, which provides enough knowledge to configure rules and start all the project processes to track and measure success. |
| Primary page | A clipboard page with the same class as the activity (or selected other rules), designated when the activity is called. This page is the default location of properties that are referenced with a period and without a preceding page name. |
| Primary path | A set of actions that your business process follows to reach an expected goal. For example, in a hiring a job candidate process, you can create a primary path that starts with collecting documents from a candidate, goes through a job interview and a background check, and finishes with approving the candidate.
Creating a primary path helps you define the order in which your business process moves most often towards resolution, and model the process in a way that most precisely matches your work. To ensure that you can resolve work in different scenarios, create alternate paths. |
| Priority | The urgency of a case on a scale from 0 to 100. The higher the priority, the more important addressing the open work item is. Case priority depends on the time that has passed since the case was created, and manual or automatic adjustments that you can introduce to make some cases more urgent than others. For example, a credit card company may assign higher starting priority to cases that deal with reporting stolen credit cards. Consequently, these cases are handled first.
Managing case priority helps you ensure that your team works on what is most important to your business, and improves efficiency and resource allocation. |
| Privilege | An application-specific access control element that is associated with a class and an access role. Using privilege rules in an application is optional, but they can offer improved control over access than access roles alone. |
| Prlog4j2.xml file | A control file for the Pega Platform logging facility that is located on each node and controls the contents of the server console output and Pega log files. |
| Problem assignment | An assignment that remains open for a long time or references a work object or rule that is no longer available. When either of these conditions is detected, the assignment status (the Assign-.pyAssignmentStatus property) is changed to Error.
Problem assignments, or assignments in error, require review and analysis. To research problem assignments, use the available reports by clicking Configure > Case Management > Tools > Work Admin > Worklist Assignment Errors. |
| Process API | An API with rules for standard activities, flows, and flow actions that you can use to start and advance flows without using user forms. These rules can support Pega Platform business processing through service-oriented architecture (SOA) facilities, including agents and service activities. |
| Process architect | A member of an application development team who provides knowledge of business rules, including processes (flows), business objectives, service-level agreements, reporting requirements, and business policies. A process architect might also be called a business architect. |
| Process page | A reserved, top-level clipboard page (pxProcess) that contains information from the Data-Admin-System instance. Only standard activities update the properties on the process page. The contents of the process page are identical for every requestor on a node.
This page has a class of Code-Pega-Process. Use the Clipboard tool to view this page. |
| Process step | A task that helps move a case toward resolution. Steps can be performed by users, your application, or an external application. Use the life cycle of a case to add steps to existing processes. |
| Process | The actions that are taken during a stage, in parallel or one after another. Processes can include assignments, automations, decisions, and sub-processes |
| Product Owner (PO) | An empowered role that sets priorities, owns the backlog of development tasks, and holds responsibility for meeting the business objectives of the solution. The PO also represents the business, acts as a single point of contact for business decisions, sets stakeholder expectations, and accepts or rejects user story completion. |
| Production % | The percentage of time spent in production applications and websites during the expected hours or shift. |
| Production Mirror | A separate sandbox service that provides an architectural replica of the scaled production environment that can be used for production staging, scale benchmark testing, and load performance testing. |
| Production Work category | A defined category of associate focus that indicates the work that is needed to complete a production item. This associate focus can be used for application and off-computer time reason code mapping. |
| Production Work time | The amount of time that is spent in applications or away from the computer that is categorized as Production Work, shown as both an amount and a percentage of total time. |
| Production hours | The time spent during a shift in production applications. |
| Production level | A property in the System data instance (Data-Admin-System class) with a value between 1 (experimental system, low security) and 5 (production). The current level is recorded as the value of the pzProductionLevel property on the Process page. |
| Production ruleset | A ruleset that contains rules that you can modify after the application is deployed. On the Category tab of the Ruleset form, the Ruleset Type for a production ruleset must be Standard. |
| A meeting held to address cross-program issues, resolve relationship issues, and communicate current status and priorities. Program Sponsor governance meetings also confirm actions by all stakeholders. |
| An application that implements best practices for the management and tracking of Scrum projects across multiple development and quality assurance environments. |
| Project worklist | A list of open assignments for a user, including user stories, tasks, bugs, and issues. |
| Project | An entity that bundles functionality when you develop solutions with Pega Robot Studio. You can integrate applications, monitor events, and automate tasks. Adapters, automations, and global containers are stored as .os and .xml files in the solution and project folders. |
| Property Optimizer | A tool that you can use to optimize, or expose, a single-value property so that the property values are stored as a column in a database table, in addition to the Storage Stream BLOB. Optimizing a property improves the efficiency of data retrieval for reporting.
The Property Optimizer tool creates an exposed column or a declarative index, changes the database schema, and populates the new column or table with values for existing class instances. |
| Property message | A text clipboard value that is generated by the system and associated with a property. A property message can convey error conditions, progress, or exceptions to a user. |
| Property mode | A setting that defines whether a piece of data in your application stores a single value, such as a name, or a collection of related values, such as a mailing address that includes a street, a city, and a postal code. By using the property mode, you organize information in your application efficiently.
For example, you can organize shipping addresses of your customers into an ordered list, and then reference an address that is relevant to your business process. You also save time and maintain consistency because you do not need to reference single elements such as a street and a postal code separately. |
| Property qualifier | A reference in a property that determines the appearance and allowable values of a portion of the property value.
A property qualifier rule is an instance of the Rule-Obj-Property-Qualifier rule type. |
| Property reference | A notation for a run-time reference to the name or value of a property that you can use in activities, data transforms, HTML, and other places. This notation is also called dot notation. |
| Property type | A setting that defines schema of data in your application. For example, if you create a date type field in which a user provides the date of birth, you ensure that date is the only format the user can enter. A property type determines how data can be processed in your application, integrated with external resources, for example by using REST APIs, and stored in a database. |
| Property | An entity that models data in your business processes and defines what information you need to provide to reach your business goal. For example, in a process of hiring new employees, you can create properties that correspond to the personal details of a candidate, such as a name, a surname, and an address. Then, when you review applications from different candidates, you provide values specific to each candidate.
To save time and make your application more relevant to customers, you can reference properties in different elements of your application, and then populate them with data at run time. For example, you can include a property that references a customer name in an email that your application sends automatically. As a result, each time that the email message is personalized and includes an actual customer name.
Properties help you collect and provide consistent data irrespectively of the method in which users interact with your application. By referencing properties, you ensure that a user receives the same information through a website, an email, or a mobile app. |
| Proposition | An offer of a tangible product (a handset or a subscription) or less tangible goods (benefits, compensations, or services). |
| PublicAPI | The supported public interface to the rules engine. As such, PublicAPI is sometimes referred to as the Engine API. |
| Pulse | A gadget that adds social activity streams to your application. When you embed Pulse in your application, users in the same work group can create posts with instant messages, files, and URLs. |
| Pyramid chart | A chart that displays the hierarchical structure and quantity of data in each segment of the pyramid. The height of each segment, and not its width, is significant.
You can specify the chart type and subtype for a report definition report by using the Chart Editor. |
| Question page | A survey page that organizes questions into logical groups. By putting related questions on the same page, you can help users complete surveys more quickly. |
| Queue Manager | The internal server facility that supports queued items created by the Queue-for-Agent method. Agents with a Queue Method value of Standard (on the Schedule tab of the agents rule form) use the Queue Manager. |
| Quick Create | An option for certain rule types that you can use to configure rules directly in the Create dialog without having to open the rule form. Rule types with this option include properties, field values, when conditions, flows, and activities. |
| RUTA | An entity type that looks for patterns such as Social Security number, account number, and so on. RUTA entities work like regular expressions. Pega Platform provides several examples. |
| Readiness assessment | An activity that ensures that the various prerequisite processes are in place to create a successful project environment. Readiness assessment is held during the Discover phase. |
| Record editor | A tool for adding, editing, and deleting data type records. You can access the record editor on the Records tab of a data type in the Data Designer. |
| Record | A collective term that describes a rule instance or a data instance. For example, a customer record would include data specific to a given customer, such as name, telephone number, and customer account number. |
| Refactoring | The process of changing the Applies To key part of a rule, the ruleset name and version, or both. |
| Reference property | A property of mode Single Value, Value List, Value Group, Page, Page List, or Page Group, that can operate to maintain what appears as an automatic copy of properties on another page. Reference properties can eliminate the need for copying the contents of one value or page into one or more other values or pages. |
| Referencing Rules tool | A tool that displays where a rule is referenced, for the purpose of learning about and debugging applications. For several rule types, the Referencing Rules tool provides two lists:
- The left column lists other rules that reference the current rule.
- The right column lists rules that the current rule references. |
| Regular user | A classification of usage for an operator ID instance for a time period by the License Compliance facility. An operator ID can count as a regular user during one time period, but not count as a regular user in other periods. |
| Remote logging | A feature that streams the contents of a log file to your workstation. While running a service, you can watch the log for an entire node, or use filters to view the log for a listener or service requestor, rather than opening the log file repeatedly. |
| Remote system | Any system in a Federated Case Management (FCM) network that provides cases and work for other systems in the federation. |
| Report Browser | A tool that provides access to all the reports that are available to you. In the Report Browser, you can complete many tasks, such as browsing and searching for existing reports, running and scheduling reports, creating and modifying reports, and sharing reports with colleagues.
The Report Browser is available in the Case Manager portal. |
| Report Editor | A tool that displays a report and provides options for editing it. |
| Report List | A tool that provides access to all the reports that are available to you. In the Report List, you can click the report shortcut to run a report and view the report category. |
| Report Viewer | A tool that displays the results of a report and provides options for analyzing the results. Options for working with the results might include formatting, filtering, saving, printing, and exporting the report. |
| Report category | A way for you organize reports in the Report Browser. Application developers create public report categories, and managers can create private report categories for their own use. |
| Report definition rule | A rule that defines a report definition report. This rule generates an SQL query that retrieves and sorts information from the PegaRULES database, an external database, or an Elasticsearch index, and displays the results in a variety of formats.
The two types of report definition reports are summarized reports and list reports. |
| Report definition | (Pega Platform version 7.2.2. and later) A rule for creating advanced reports that show detailed information. Replace the Summary View Rule.
A report definition rule provides more advanced options for displaying and managing data than the standard reports that you can create in App Studio. |
| Report shortcut | A named link in the Report Browser that provides an efficient way to retrieve and run reports. You can use report shortcuts to organize reports into one or more categories. |
| Reporting | A Pega Platform feature for retrieving, analyzing, and using data from business processes. For example, you can create a report with the number of resolved cases per user, and then use the report to assess user performance. You can also sort and filter data to make your report readable and organized. |
| Reports Database | A mirrored replica of all or part of the PegaRULES database. To reduce the performance impact of report generation, you can specify that some or all reports obtain data from the reports database. |
| Requestor ID | A system-generated hash identifier that uniquely identifies a requestor session. A requestor ID is sometimes called the connection ID. |
| Requestor Page | A named, top-level clipboard page that contains information about your access roles, RuleSet list, and HTTP protocol parameters. |
| Requestor Scheme | The pxReqScheme property on the requestor page. The requestor scheme indicates the protocol used by the browser that connects to Pega Platform. |
| Requestor Type | Data instances that define the types of requestors that can access Pega Platform, such as a browser session, an external application, or an internal background process. |
| Requestor | The process and data associated with a Pega Platform user (guest or authenticated). A requestor is also the processing and data associated with a request to your system started by an outside system, such as a web application server or an Active Server Page on a web site. |
| Required Field | An input field on a form that must have a non-blank value to be valid. Many flow action forms mark a required field with an orange asterisk. (The asterisk is only a label to notify users that the field is required, and does not affect input editing or processing.) |
| Requirement | Used to generate legacy document types. A requirement is an event, condition, or function that must be satisfied and tracked by an application. Requirements can be functional (a capability) or non-functional (a quality or constraint). One or more requirements can be used to define the criteria for the successful implementation of a specification. |
| Resolution | The act of closing a case by recording in the properties that work is complete.
As a case advances through a flow, information stored in its properties becomes more complete through user input and automatic processing. When the work for a case is complete, the case is marked as "resolved", or "closed". |
| Responsive Behavior | Enables a layout to adjust itself according to screen size, providing an optimal user experience on a desktop, tablet, and phone. |
| Restore Point | Create restore points to save the state of your system, including rules and data, at a significant point in time, such as before a system update. You can then perform a system rollback to a restore point to return the system to an earlier state. |
| Results Page | A clipboard page that stores the results of running the Obj-List-View, Obj-Browse, and RDB-List methods. The Obj-Filter method operates on results pages. |
| Robotic Processing | The use of software robots, or "bots", to perform repetitive tasks for you. Depending on your needs, these robots can either operate with (attended) or without (unattended) human interaction. For example, for handling customer calls, you could create an attended robot that prompts the employee to enter the customer’s account number and then retrieves all pertinent information about the client, including information from multiple software applications. If the employee changes any of the customer’s information during the call, the robot could then automatically apply those changes everywhere.
You can also create unattended robots that process transactions from a queue during non-work hours.
In addition to performing tasks much quicker, the use of robots to perform everyday tasks minimizes the chance of mistakes by ensuring that tasks are completed in a standardized manner. Robots can perform the mundane and repetitive tasks for you, so that you can concentrate on more important issues. |
| Roles | Applications have users, though not all users perform the same tasks. Roles define how users interact with the application by, for example, determining the user interface, page permissions, and routing that are available to a user. For example, in Pega Workforce Intelligence there are several user roles, including administrator, analyst, and report user. |
| Rollback | Perform a system rollback to revert any recent changes. |
| Router Activity | Used to evaluate assignment criteria, such as required skill sets and user availability, to determine whether an assignment moves to a worklist or work queue for processing. Router activities have the Usage field set to Route on the Activity form, and return a result by assigning a value to the AssignTo output parameter. |
| Routing | The process of assigning tasks in a business process to an individual or group of individuals who are the most capable of completing those tasks.
For example, when creating an expense report, an employee creates the report, a manager approves it, and a payroll employee then sends the payment. To process employee compensation payments, you can route the task to the work queue of the payroll team, in which any member of that team can access, select, and process the work item.
If you need a specific person to work on the assignment, you can route the assignment to a work list. For example, when a human resource manager needs to approve employee time off requests, you can route the assignment to the worklist of the human resources manager.
If you need a person with a particular skill set to work on the assignment, you can route the assignment using business logic to a skilled group by defining a specific condition. For example, in an automobile quote request, a prospective customer fills in a form and selects an Electric vehicle check box. The request is then routed to the electric car insurance underwriters work queue, members of which specialize in electric cars. |
| Rule Assembly | A technique for improving performance by only generating and compiling the Java code that corresponds to a rule when needed. |
| Rule Cache | An in-memory cache of recently found rules that is used to improve the performance of the Pega Platform engine, especially during rule resolution searches. |
| Rule Form | Displays the fields and values that comprise a rule or data instance in your application. Rule form types include form-based, harness-based, and custom. |
| Rule Resolution | The search algorithm used by Pega Platform to find the most appropriate rule instance to apply in a situation. Rule resolution applies to most, but not all classes derived from the Rule- base class. |
| Rule Type | The general classification or particular use of a rule. For example, the System screen in an application used for hiring employees contains Property rules that define the information that needs to be captured from the user, for example, full name, email address, phone number, and résumé. The screen also contains a Section or View rule that defines how the properties are displayed to the user.
Rules of different types are linked together to define your application. Rule types also help to categorize key concepts and behavior in your application, saving you time during the development cycle. You can use another instance of the same rule type to define other sections of the application. |
| Rule | The basic building blocks of an application, rules define the behavior of an application. There are many types of rules, each defining a different type of behavior. For example, rules define the display of a form, the fields that are used in your application, and the flows that define the process of completing work.
The system can reuse rules throughout your application. For example, in an application for ordering replacements parts, you can define a user interface to capture an address, and reuse the same rule for the UI to capture both the mailing address and the billing address for the order.
You define rules in an application to create a business solution for your organization and customers. Rules provide flexibility during the development process and help you design applications more efficiently, so that they can be implemented again in future projects. |
| Rule-Base Class | An abstract class that contains all rule classes. Rules are the basic building blocks of an application and define its behavior. |
| Ruleset List | An internal data structure that the system uses to determine which rule instances a requestor can run.
When you log in, the system assembles this list from several sources. The list influences a phase of rule resolution processing. |
| Ruleset Lock | Secures rulesets and ruleset versions to prevent them from being changed. A ruleset is a set of rules that define an application or a major portion of an application, and the way you use rulesets in your application has important design and deployment consequences.
Securing rulesets helps maintain data integrity and compliance. By using a ruleset lock, you can prevent potential conflicts when two or more users attempt to change one rule at the same time. For example, you can control who can change rules in a ruleset. |
| Ruleset Resolution | The search algorithm used by Pega Platform to find the most appropriate use to apply in a situation. For example, in version 2 of a hiring process application, the system uses rule resolution to assemble the rules that are needed to run the application.
Rule resolution ensures that the system uses the latest version of each rule to run an application, because some rules will be found in the original version and some rules may be found in a subsequent version.
There are several factors that are considered when the system is trying to find the right rule, including (among others), the ruleset order, ruleset version, and the context class of the rule.
For example, an application used for hiring new employees includes two rulesets, MyJobApp and MyHR, in that order. The system gives priority to rules located in MyJobApp over the rules located in MyHR, because MyJobApp appears first and MyHR appears second in the list.
To facilitate application evolution, testing, and patching, rules can have multiple versions with the use of rule resolution. In addition, rule resolution provides flexibility as rules defined at a higher level can be overwritten by more specific rules at a lower level of an application.
A class contains rules which define the behavior of your application. |
| Ruleset Version | The ruleset version characterizes the evolution and development of a rule instance, and the application it belongs with. The version number, in the format NN-NN-NN, defines the major version (first two digits), minor version (middle digits), and patch version (last digits). Rules in versions below the major version are not visible to rule resolution. |
| Ruleset | A collection of rules (the basic building blocks of applications built with Pega Platform) that describe key components and how part of an application works. Rulesets help you store, categorize, and version the rules in an application.
A ruleset consists of ruleset versions that store the updated versions of rules. For example, in an application used for hiring new employees, the application might include several rulesets, one dedicated to defining the UI and processes used to hire employees, and another ruleset that defines the application's integration with a Job website.
You usually implement several rulesets when developing a large application. Once the rulesets are adequately tested and make it into a production environment, you can create a new version of the rulesets to develop and test during the next development cycle. |
| Runtime user | A named Pega Robot Runtime user whose desktop usage is being actively captured. |
| Runtime-only users | Users who only use Pega Robot Runtime, and do not use other Pega Robotic Automation products, such as Pega Robot Studio or Pega Workforce Intelligence. |
| RuntimeConfig.xml | Contains the configuration settings that are primarily used by Pega Robot Runtime. Pega Robot Runtime is installed as a stand-alone application and is also installed with a Pega Robot Studio installation. |
| SQL function alias | A rule that helps to simplify the creation of complex SQL queries. You can reference an SQL function alias rule in a report definition rule, to define SQL expressions for querying a database for reporting purposes. |
| Sample Application | The PegaSample sample application lets you view and study basic elements without creating new rules. This sample application is built completely from standard rules in Pega Platform. |
| Scheduled Task | A case that is automatically created to support running reports on a scheduled basis. Scheduled tasks belong to the Pega-ScheduledTask class, and have the work ID prefix px-ST. |
| Screen Analysis page | A page in Workforce Intelligence that shows how much time has been spent in each application screen or on each webpage. The information presented on the screen analysis page can help you determine which processes to automate, in order to improve the overall efficiency of your organization. This information is typically used by business or data analysts. |
| Screen Flow | A type of flow with actions that are configured on shapes instead of connectors in the flow diagram. Screen flows are typically used to present a series of assignments to a single user, and allow the user to go back and change or review the input on each screen. |
| Screen Layout | Screen layouts help you determine the overall presentation of your portal. While harnesses function as containers for various sections in your portal, screen layouts define the general appearance of the portal. For example, you can insert a screen layout that defines the width, alignment, and background of your screen into your portal harness.
Screen layouts support responsive display and can be configured to automatically adjust your interface to scale its width and height to various screens, for example, on a mobile device. Screen layouts also include Accessible Rich Internet Applications (ARIA) roles by default, which help assistive technology users to navigate the main areas of the application, such as the primary menu and the search. |
| Section | The building blocks of your user interface, sections can use design templates for their structure and contain such interactive UI elements as fields, buttons, lists, and so on. A section creates a functional chunk of a user interface, and can be reused throughout your application for improved consistency and efficient development.
For example, your application may need to display user data as a list of ID cards. You can create a section for the contents of a card, and then reuse that section so that the design of every card is consistent. |
| Security Auditing | An optional feature that you can use to add information to the default details captured in the History Details of a data instance or rule. |
| Security Role | A user access role that is used on application servers to control access to servlets. |
| Security Testing / Penetration Testing | Security testing (also known as penetration testing) is performed to ensure that a system is safe and cannot be compromised by hackers. Security testing is typically performed by either the client team or a specialist third party company at the end of an engagement, shortly before go-live. |
| Sentiment | In text analytics, sentiment is the overall emotion of a customer message or piece of text, for example, positive or negative. |
| Service Activity | An activity that is referenced by a service rule. At run time, the activity operates as a BATCH requestor type to perform background processing, and returns the results to the client or calling external system. |
| Service Blueprint | A method of visualizing a customer’s end-to-end journey and the operations on the business side that are necessary to service that experience. |
| Service Invocation | A call from an external system to run a Rule-Service- rule in your application that creates, updates, or operates on a work item. |
| Service Level | Indicates how quickly service is initiated. For example, how quickly a phone call or chat request is answered, an email is reviewed, etc. If a contact center answers 78% of all calls within 30 seconds, the service level achieved is said to be 78/30. You can apply a service-level agreement to cases, stages, steps, flows, and assignments. |
| Service Package | A name that groups one or more service rules that are designed to be developed, tested, and deployed together. For some service rule types, a service package corresponds to a package of Java classes.
Service packages are instances of the Data-Admin-ServicePackage class, and comprise the first key part of most service rules. |
| Service | A program component that defines and implements an interface between an external application acting as a client, and a Pega Platform system acting as a server. An external system can send a request to a Pega Platform application and receive a response.
For example, the Pega Cloud Services SFTP service provides Pega Cloud clients with simple, secure file transfers to and from their Pega Cloud applications. |
| Service-level agreement | A commitment that you make to customers and stakeholders that defines the timeline for delivering your work. You can define goals that indicate the suggested time required to resolve individual assignments, and an overall deadline that states the ultimate time in which to resolve the assignment.
You can also define escalation actions that your application performs when the goal and deadline expire. For example, if a worker does not resolve their task by a week, that worker receives a notification reminding them to do so. If the worker does not resolve the task for another week, the manager of that worker receives a notification. By applying SLAs, you ensure the timely resolution of your business processes.
For greater efficiency, you can apply SLAs to an entire business process or elements of it, such as assignments or stages. |
| ServiceExport Directory | The ServiceExport directory (StaticContent/global/ServiceExport), is a subdirectory of the temporary files directory on a server. The ServiceExport directory path cannot be changed, but the entire temporary directory can be changed. |
| Shared Ruleset | A ruleset that contains a small number of rules that each operate on a common, top-level page of a single class (or of subclasses of that class). |
| Show and Tell | A show-and-tell session is an opportunity for a team to share their progress with stakeholders and get immediate feedback for action. Show-and-tells are done throughout a sprint, as well as at the end of a sprint to show all the work completed according to the Definition of Done. |
| Sibling Rule | An instance of another rule that has the same visible key. Two rule instances are siblings if they are both visible to you and have a common value for the pxInsName property. |
| Simple Question | In a survey, a simple question collects information from users in a single-answer format. For example, you can ask users to enter a mobile phone number in a text box, or select a type of insurance plan from a list. |
| Single Value Property | Also knowns as a scalar property, a Single Value Property contains a single text string. Text, numbers, dates, Boolean values, and amounts are stored in single value properties. |
| Skill | Skill rules are instances of the Rule-Admin-Skill rule type. A skill rule gives a name and a range of proficiency value to different user skills. These skills can then be associated with users (in the Operator ID instance), and can form the basis of skill-based routing decisions. |
| Skill-Based Routing | Skill-based routing uses skill information, such as skill rules, to define which workers are qualified to carry out a given assignment. For example, a customer of an insurance company might want to insure a vintage car. To accurately appraise the value of the car, the insurance case must be handled by an employee with the proper expertise. To this end, you can set up a routing logic that assigns vintage car cases to users who have 'vintage car appraisal' as a skill.
This type of routing helps you distribute work efficiently and improve your organization's productivity. |
| Skimming | The process of saving the highest version of a rule into a new, higher ruleset version. Skimming applies mainly to rule-resolved rules. The two types of skims are minor and major. During a minor skim, rules are stored in a higher minor version, and during a major skim, rules are stored in a higher major version. |
| Skin | Skins determine the general visual style of your interface and let you define the typography, placement, and appearance of UI elements. The skin separates content from presentation, so that you can reuse your configurations and keep a consistent UI design. For example, you can reuse a section anywhere in your application and retain a uniform style that is specific to your company. |
| SmartInfo | A feature that displays a pop-up window when you hover over specific elements in a report or form. The content of the pop-up display is determined by a section rule, and are displayed in read-only mode. |
| SmartLayout | A formatting option for a UI section, in which the layout is presented as a grid of paired cells that has columns of uniform width, style, and characteristics. Each pair of cells holds one label and one property value or other form control. Use dynamic layouts instead of SmartLayouts to separate content from presentation. |
| SmartPrompt | A SmartPrompt field on a form supports user selection of a text value from a list of candidate values. When you enter characters in this field, the first value that matches your input is selected. |
| Smoke Test | Simple tests that quickly cover a broad range of functionality to ensure that a newly deployed release works correctly. These should be performed in every environment on receipt of a new deployment. |
| Solution | Within Pega Robot Studio, solutions and projects are containers for all the items required to build and run a project. Solutions can include multiple projects. Once you deploy a solution to the Pega Robotic Automation Deployment Portal, it is known as a package. |
| Spark Chart | A microchart that displays graphical information, such as lines and columns, in a compressed format. Because spark charts are small, you can embed them in a form or layout to show a lot of information in a single view.
You can specify the chart type and subtype for a report definition report by using the Chart Editor. |
| Specification | Represents a unit of processing that is performed by one or more actors for a given case type within an application. In other words, a specification defines what an application does. One or more requirements define the criteria for the successful implementation of a specification.
Specifications are also used to generate legacy document types. |
| Spin-off Flow | A process that runs in parallel with the calling process, or parent flow. Spin-off flows can work on the same case as the parent flow, or they can work on a different case, based on the context that you provide. |
| Split schema | A database configuration in which rules are kept in a separate schema from work and data. |
| Sprint Planning | The time-boxed activity at the beginning of each sprint that identifies what will be delivered in the Increment resulting from that sprint, and how the work needed to deliver that Increment will be achieved. |
| Sprint Retrospective | A meeting held at the end of each sprint in which the whole sprint team meets to transparently discuss what went well, what can be improved and what they would like to repeat. The actions are owned by the team and reflected in the next sprint. |
| Sprint Review | A meeting held at the end of each Sprint in which the Scrum Team and stakeholders discuss what was achieved in the Sprint. Based on the Sprint Review and any changes that were made to the Product Backlog during the Sprint, attendees together work out their next objectives. |
| Staff Availability | A function that helps you manage the planned absences of your workers. For example, when a member of your team goes on vacation, you can route their assignments to a substitute user or team until they return to work. |
| Stage | The first level of organization of the tasks that are required to complete your business process. By providing stages, you organize work into logical phases that users of your application follow to reach an outcome. Stages visualize milestones or significant events in your business process and can also indicate a transition of work from one person to another. For example, if your business process is to review job applications, you can create Submission, Review, and Approval stages, each of which includes a different set of actions and is performed by a different person. Stages that are necessary to resolve a case through the basic, default path are called primary stages.
In a Microjourney™, stages are the milestones that leads towards an outcome. |
| Standard Rule | The rules provided with Pega Platform. You can use standard rules as-is, or you can copy them into your application and modify them. |
| Starter Flow | A flow that supports the creation of a case. Also known as a starting process. |
| Static Assembler | A utility for preassembling and caching the rules of an application. |
| Static Content | Information that is extracted once from a rule to an HTTP server or web server and is unaffected by user input, such as the use of an application or the contents of user clipboards. |
| Step Page | A reference to a clipboard page that is available to an activity, or to a new page that is created by a step. Each step in an activity could have a designated step page. The step page becomes the primary page for the duration of the step's execution. |
| Step | The smallest element of your business process, a step represents a single task. A step can be a user action, such as collecting information from a customer, or an automation that an application performs, for example, sending an email to a customer when a business process reaches resolution. When you visualize your work, you order steps in a sequence that communicates what actions are required to reach your business objective. You can select from a wide choice of steps to ensure that you reach your goals in the most efficient way. |
| Storage Stream | A column in a PegaRULES database table that contains property data in a compressed format. Most tables in the database contain a Storage Stream column, identified as the pzPVStream column. |
| Straight-through processing | Automatic processing that occurs without operator intervention. Straight-through processing is implemented by using a flow rule that does not contain any assignments. |
| Strategy Result Class | Defines the results that a decision strategy produces. The Strategy Result (SR) class is a subclass of the standard Data-pxStrategyResult class (either through pattern or direct inheritance).
The Data-pxStrategyResult class contains a set of predefined properties (for example, pyIssue, pyGroup). The SR class can be extended with application-specific properties. |
| Stream Processing | The run-time conversion of an HTML or XML text block containing JavaServer Page (JSP) tags or HTML directives into a final form that does not contain JSP tags or directives. JSP tags and directives are evaluated as they are encountered from the start of the string, in the context of the current clipboard. |
| StudioConfig.xml | The StudioConfig.xml file contains the configuration settings used by Pega Robot Manager. |
| Subprocess | Also known as a "subflow", a subprocess is a flow that is called by another flow. Subprocesses are represented by the Subprocess, Split Join, or Split For Each shapes in a flow diagram. |
| Subreport | A report that is called by another report to provide data. When you designate a report as a subreport, the original report is not altered, and you can still access it. However, a subreport cannot have its own subreports.
You can designate a subreport within a report definition report to simplify the assembly of data from several classes, or to satisfy complex conditions. |
| Subscription | Subscriptions are a way of notifying developers and users of actions that are related to an application, a report, or an event. Notifications are sent to subscribers by using an RSS feed, an email, or a notice on a dashboard. |
| Summary View Rule | (Deprecated) Defines a summary view report that displays summary counts, totals, or averages, in which you can drill down to view supporting information.
In Pega Platform version 7.2 and later, you create custom summary view reports that you need as report definitions. Internet Explorer 11 is the last version of Internet Explorer that the summary view rule supports. |
| Summary page | A webpage within Pega Workforce Intelligence that shows the high-level view of utilization and application usage. Users responsible for multiple levels in the organization can drill up or down through the various levels of the hierarchy. |
| Survey | From Pega Platform version 7.2.2, the previously standalone Pega Survey application has been included in Pega Platform as a standard ruleset. Four survey APIs can be used to programmatically ask survey questions or retrieve survey results. |
| Suspended Case | An open case for which work is halted because an unusual or suspect value is detected.
All of the flow executions in process for the suspended case are stopped, and the value for the property Work-.pxSuspended changes to true. |
| Swimlane | A shape in a flow diagram that is used to organize and graphically identify related groups of shapes that are performed within specific work contexts, typically teams. |
| Symbolic Date | A system-derived date value that is used in the selection criteria of reports to choose values related to the current date.
You can use symbolic dates as values in Date and DateTime properties. |
| System Architect | The role assigned to a person who designs and builds components of Pega applications. A system architect (SA) is typically a person with some programming skills, but more importantly, is someone who loves to build – to move quickly and not be tied down to building lines of code. SAs also have different levels: Senior, Lead and Principle. |
| System ID | The system ID (also known as a system name), identifies your Pega Platform system, including all instances (nodes) that share a single database and the same system name. The system ID is stored in a System data instance record (Data-Admin-System class). |
| System Pulse | The system pulse synchronizes rule changes across nodes on Pega Platform. Two types of pulse processing are available: a database pulse, and a cluster-based pulse. |
| System administrator | A person who is responsible for system installation and setup, security and access, and other operational functions. |
| System of Record | The primary data source for a data object, such as a connector, external database, or local data storage. For example, for an Employee data object, you might connect to a system of record that populates the data object with employee information fields such as Name, Department, and Start Date. |
| System-Base Class | A standard, top-level abstract class that contains concrete subclasses that hold real-time status information about the server software as it runs. |
| Tag | A text value that case workers and case managers can associate with one or more cases. Users can select from a list of available tags or create new tags. Case managers can then search, access, and report on tagged cases. |
| Target | An object created in the adapter control that represents a native control in an application that you are automating. There are many types of targets and each target represents a specific type of control. For example, a GridTarget knows how to get cell values, set cell values, and so on. A ListBoxTarget provides a count of items and returns the items as a list. |
| Task workflow | Your organization sends start and end times that create task workflows to track specific activities. Workforce Intelligence then matches the timestamps for those tasks with the data that it collects from associate desktops to analyze what occurred during that task. |
| Team | 1) In user portals, a "team" is equivalent to a "work group".
2) One or more associates who work semi-autonomously on recurring tasks or towards a common goal. In a Pega Workforce Intelligence hierarchy, departments are comprised of teams. (Defined by the WFI team) |
| Temporary Case | A temporary case is created and resolved by a single operator, or by straight-through processing, and is not saved as a database object. You can use temporary cases in screen flows and regular flows.
To create a temporary case, select the "Creates temporary object?" check box on the flow that creates the object. |
| Test ID | A property that supports the automated testing of Pega Platform applications.
To generate Test IDs, configure the Test ID field on the General tab of the UI control property panel. |
| Test Management Framework | The Test Management Framework (TMF) is an optional application that implements best practices for the testing and deployment of new applications and incremental changes to existing applications. |
| Thread | A PRThread, or thread, is a data structure that allows a requestor to have separate clipboard page name spaces that do not interact with each other. |
| Threshold | A target range of values. When a threshold is exceeded, an alert is generated.
You can manage threshold settings and specify whether alerts display by updating the prconfig.xml file, or by using dynamic system settings. |
| Throughput | A measure of work accomplished or completed during a calendar interval. |
| Ticket | A named location that you add to a flow diagram. Tickets identify processing, such as a transaction rollback, that occurs when the normal flow progression of a case is interrupted. |
| Time-Qualified Rule | A circumstance that is only resolved during a specified range of time. This type of rule is commonly referred to as a "date range circumstance", or "temporary rule." |
| Timeline page | A webpage within Pega Workforce Intelligence that provides a supervisor with a daily view of the details and patterns of their associates’ utilization and application usage. You can use this page to compare behavior and drive improvements. |
| Top-Level Case Type | Represents work in your application that can contain other case types, known as children or child case types. Unlike child case types, top-level case types are not covered by a parent, and are typically instantiated by case workers using the Case Manager portal.
Your application can have many top-level case types. You can view your top-level case types in the Case Type Explorer. |
| Top-Level Class | A non-standard, abstract subclass of the ultimate base class, @baseclass. |
| Top-Level Page | A clipboard page that is usually created through the Page-New method. Applications create many top-level pages during the course of their operations, and activities can also create top-level pages. Most top-level pages are named, and have an associated class. |
| Topic | A way of classifying the intent of a block of text. Used to decide which action to take (creating a case, sending a reply, or routing to a specific queue). The topic is determined by a keyword match or by using a machine learning model. |
| Tracer Tool | A tool for debugging flows, data transforms, activities, services, parse rules, and declarative rules. The Tracer tool provides full debugging facilities, including step-by-step execution, breakpoints, and watch variables. |
| Traditional Portal | Portals that have a fixed layout and are built from HTML rules with Data-Gadget as the Applies To key part. Traditional portals are referred to as "classic" portals in some menus and selection lists.
Composite portals are recommended for new application development, as traditional portals are not supported in Pega Platform. |
| Transfer | The reassignment of a worklist or work queue by a user or manager with appropriate privileges. |
| Transient property | A property that is not persisted to the database. Transient properties can have non-null values on the clipboard, but when a clipboard page containing transient properties is saved to the PegaRULES database, the values are removed from the Storage Stream column. Similarly, when an instance containing a transient property is retrieved from the database and opened on the clipboard, the transient properties have no initial values on the clipboard. |
| Transition | A reference to a when condition (Rule-Obj-When rule type), or an expression that evaluates to true or false. |
| Translator | In Pega Robotic Automation, translators are objects that are injected into the adapter application and operate directly against the native control. Translators are designed to operate against a specific type of control. For example, the .NET DataGrid translator works against System.Windows.Forms.DataGrid, or any objects that inherit from DataGrid. |
| Tree Layout | Allows you to view the embedded pages of a Page List as a tree. You can click branches to display or hide their leaves. The tree can display embedded relationships as deep as 20 levels. Each branch of the tree corresponds to a single embedded page or property. The tree is created dynamically and can have as many branches as needed to display the requested data. |
| Trend Report | Displays counts of events, objects, or actors as a series of points along a continuum, typically a timeline. The x-axis of a trend report displays data points that represent weeks, months, or quarters in a year, or some other meaningful increment. One column of the data that supports the trend report displays one or more single value properties of a DateTime type. |
| Trend | A trend compares desktop usage for a specified part of the hierarchy over a defined time period, such as from this week to last week. Trends are usually calculated by comparing percentages. |
| Trigger Rule | A trigger rule identifies an activity that runs automatically when an object of a specific class is saved or deleted in the PegaRULES database. This rule is an instance of the Rule-Declare-Trigger rule type. |
| Trigger | The event or method that starts the processing of a specified action in response to another event or method. |
| UI Connector | A C# class that is created and compiled into your Pega Robot Studio project. UI Connectors contain the logic for mapping a target implementation to a native control. The adapter control communicates with the UI Connector and the UI Connector uses the target to make reflective calls to the native control. |
| Ultimate base class | The topmost class in the class hierarchy, identified by the symbol @baseclass. All other classes are derived from this class. This class is similar to the root class in Java.
The abstract classes Assign-, Rule-, Work-, and others that are direct subclasses of the ultimate base class are known as base classes. |
| Uncommitted hotfix | A hotfix that is installed in your system and active, but you can still remove it. You can use uncommitted hotfixes to test your system with the changes in place before permanently committing the changes. |
| Unknown Time category | In Workforce Intelligence, the default work category for all applications and websites until they are mapped to a more specific work category. |
| Unknown time | In workforce Intelligence, the amount of time spent in applications or away from the computer that is not categorized as Production Work, Other Work, or Non Work. Unknown time is shown as both an amount and a percentage of total time spent at the computer. |
| Unoptimized Property | An aggregate property, a property within an embedded page, or a Single Value property that is stored in a specially formatted Storage Stream or BLOB column. |
| Update Controls | A feature that helps render your application user interface in the HTML5 document type. You can also use this feature to upgrade deprecated controls in a section to improved alternatives. |
| Urgency | A numeric value that brings visibility to unresolved work in your application. The number can range from 0 to 100 and is displayed in worklists and case details. The higher the urgency, the more important it is to address the unresolved work, such as an assignment or a case. |
| Usage Daemon | A background Java thread that collects data supporting the analysis of performance statistics. The daemon saves this data in an instance of the Log-Usage class.
The usage daemon adds one instance to this class every hour for every requestor, including agents. On a busy system, the associated PegaRULES database table pr_perf_stats can grow to contain thousands of rows. |
| Usage Report | Contains statistics about the usage and performance of report definition reports in the current application. Several standard usage reports are provided with Pega Platform, or you can create your own usage reports.
You can run usage reports from the Report Usage tab of the Reporting Settings landing page. |
| User Acceptance Testing | User acceptance testing (UAT) is a methodology for testing specific business scenarios to ensure that a system behaves as the business expects. |
| User Action | A task performed by a worker, such as a customer service representative (CSR), while working in a business process. For example, a user action could be a CSR entering income details in a loan request dispute. Other user actions can include changing the stage of a business process, creating assignments, and adjusting goals and deadlines. By incorporating user actions into your business processes, you ensure that the work that you create can be manually adjusted to meet dynamically changing circumstances. |
| User Page | A top-level clipboard page created by an activity. User Pages appears in the User Pages section of the Clipboard tool. |
| User Reference | A type of field that you configure on a form. At run time, it displays a list of existing users in your application. |
| User Story | Short, simple descriptions of a feature that are told from the perspective of the customer. |
| Utilization | In Workforce Intelligence, utilization is the measurement of how much of a user's time is spent in a specific time category, such as Production Work (work that contributes directly to the main business of the team or department). |
| Validate Rule | Validate rules help you to ensure that users enter valid values in forms and that the system can process the information correctly. A validate rule tests input values against conditions that you define as part of the rule. If a value that a user enters does not meet the conditions, the system displays an error message when the user submits the form. For example, you can ensure that customers provide their name and address before placing an order, or that the date of birth they provide is not in the future. |
| Value Group Property | A Value Group property is a container for an unordered list of values of different types, and can contain an unlimited number of values. |
| Value Group | An unordered collection of related text values. A value group can be used by more than one property in an application. |
| Value List Property | A Value List property is a container for an ordered list of text values, and can contain an unlimited number of values. |
| Value list | An ordered collection of related text values, such as department names, countries, or telephone number types. A value list improves the accuracy of data entry by limiting the value in a field to a set of predefined words or phrases. A value list can be used by more than one property in an application. |
| Verbalization | A structured, English-language text description of an activity. The system can generate a verbalization file (in HTML format) for any activity. Verbalization files are a useful form of documentation for activities. |
| Verification | An independent review in a workflow by one person of some part of another person's work (and of the system's work), before that work becomes final. Verification is common in financial workflows involving large dollar amounts or sensitive legal commitments. |
| Virtual Rules Table Cache | The Virtual rules table (VTable) cache is the default caching setting for all Pega Platform applications. VTable caching is a higher-performance replacement for Application-Based-Assembly (ABA) caching, and is automatically primed during system startup with rules that have been either statically assembled or built dynamically as they were used in the system. |
| Visible Key | The visible key of an instance is the text value of a reserved property, @baseclass.pxInsName. This property is defined in the ultimate base class and is available for use in every class. The value of this property is sometimes called the instance name, or informally, "insname." |
| Vision Alignment meeting/Kick-off meeting | In the Pega Express methodology, a Vision Alignment meeting brings together all of a project's team members and orients them to the objectives, plan, and work methodologies of the project. This meeting should happen at the start of the Prepare phase of a project taking the Pega Express approach. |
| Voice Response Unit (VRU) | An older term for an interactive voice response (IVR) system. |
| Wait time | In Workforce Intelligence, the period of time that a user waits for an application to become usable or for a browser to load a website or web application. |
| Waste | In Workforce Intelligence, time recorded as Non Work, Unknown, Wait Time, and Idle is categorized as Waste. |
| Web Node | A server that hosts the Pega Platform part of a composite application. A web node has "web" as the value of the nodetype entry in the prconfig.xml file, or in dynamic system settings. |
| Web domain | The portion of a website’s URL that allows for application identification for many business applications. |
| When Condition | A when condition rule defines a true-false test based on comparison of one or more property values with constant values, or with other property values. |
| Where-am-I? | Clicking the Where-am-I? icon marks the user's current position within a case life cycle (stages and steps) and displays the current process diagram. This icon appears only to users who hold the Perform privilege. |
| Widget | A GUI element in your portal that displays operational information about your application, for example, key performance indicators. By personalizing a portal dashboard with widgets that are relevant to a role, you can increase the dashboard's usability and the user's productivity. For example, you can design a workspace that includes a widget for frequently used reports, to help managers save time and effectively oversee their projects. |
| Work Focus categories | In Workforce Intelligence, desktop usage and captured off-computer time can be classified into different work focus categories, to give insight into how much time is spent on different types of work. The following work categories can be used: |
| Work Group | A work group consists of one or more supervisors and one or more workers who report to that supervisor. Work groups are instances of the Data-Admin-WorkGroup class. |
| Work Party | A person, business, or organization that is involved in a case. A work party receives correspondence, such as email, and can be an active or passive participant based on its role. |
| Work Pool Name | The name given in the Short Description field of a class group (also known as a container class), which is a collection of work types. |
| Work Pool | A class group that consists of a set of work items or cases that a user is allowed to access and work on within an application. The parent Work- and Work-Cover- classes for these work items and cases are specified in the user's access group. |
| Work Queue | A list of open assignments for a group of users. Assignments stay in the work queue until a user assigned to the work queue selects an assignment, or a manager sends an assignment in the work queue to a specific user. By associating many users with a single work queue, you ensure that even if individual workers are busy with other tasks, the work is processed efficiently.
To view the work queues in your application, in Dev Studio, open the Case Management > Work Management > Work queues landing page. |
| Work Type | A concrete class derived from the Work- base class. Work types derived from the Work-Cover- base class are referred to as case types. |
| Work- base class | A superclass to all of the classes that define work items. A work item is the fundamental unit that records processed work in an application. |
| Workbasket | This is a deprecated term for what is now known as the work queue. |
| Workflow dashboard | A dashboard in Workforce Intelligence that includes scores, insights, and a chart of workflows. You can interact with data on the dashboard to access more detailed information, select metrics to update the workflow chart, or open a table summary showing, for example, workflows filtered by a specific insight. |
| Worklist | Displays open assignments, ordered by urgency, for a specific operator. Use to view the ID, status, and relevant instructions for each item on the worklist. The system routes assignments to appropriate operators. For example, the system routes assignments that require a human resources manager to approve employee time off requests to the worklist of a human resources manager. |