Pega Academy Glossary

Term Definition

An abstract class supports the definition of rules, including other

classes. Rules with a class as a key part (including properties,
abstract class 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.
In PMF, acceptance criteria are the requirements on a user story or
epic that must be met for a story to be marked complete. The criteria
Acceptance Criteinria
defines what the product owner expects and what the team needs to
accomplish when implementing the user story or epic.
An access group restricts access to functionality within your
access group application. You can create multiple access groups for the same
application to achieve different levels of access control.
Access Manager is a landing page that you can use to view and
Access Manager authorize operator access to case types, data, and tools in your
applications.
An access role defines the classes that a user can view, update, and
access role delete through the Access of Role to Object and Access Deny rule
types.
An acknowledgment is a letter, email, or other correspondence that is
acknowledgment
sent to the originator of a work item and identifies the work item ID.
An acquirer is a financial institution that represents the merchants in
acquirer the transaction. An acquirer receives a financial transaction's electronic
data from a merchant and places that data into an interchange system.
The action section is the area in a harness in which the action is
action section
performed. It shows users the actions that they can perform.
An activity is the sequential processing unit of the Pega Platform
system. An activity consists of one or more steps. Each step can call a
activity
Pega Platform method, transfer control to another activity, or execute
custom inline Java.
An activity list is a queue that contains a list of activities that are waiting
activity list to run. Each user has the following activity lists: activity (default),
workflow, and current.
An activity loop is a step in an activity that can run repeatedly, such as
activity loop
for each element in a Value List or Value Group property.
An activity type describes the characteristics of an activity. Some
activity types (Assign, Connect, Route, Notify, and Utility) identify
activity type 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.
An actor is a user, external service, or agent that participates in
application processes and specifications. You can view and define
actor 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.
In Decision Management, the Adaptive Analytics Engine is the main
function of the Adaptive Decision Manager. The Adaptive Analytics
Adaptive Analytics Engine is responsible for storing and analyzing adaptive statistics and
Engine producing individual scoring models. The scoring models are then used
in Pega to perform calculations used for predictions defined in decision
strategies.
 In Decision Management, this is the database that stores the adaptive
Adaptive Data Store
statistics and adaptive models.
In Decision Management, this is an integrated technology that extends
Adaptive Decision predictive analytics with an adaptive mechanism to establish customer
Manager (ADM) preferences with customer responses in real time. Due to its adaptive
nature, no initial collection of data is necessary.
In Decision Management, an adapative model is a type of scoring
model that captures customer responses in real-time in order to make
adaptive model and adapt predictions, typically in the absence of historical records. An
adaptive model is used in a decision strategy to help identify the most
appropriate proposition, or next,best action.
In Decision Management, adaptive statistics refers to the persistent
adaptive statistics information that results from running a strategy that contains adaptive
models.
An ad hoc case is a case that you can create to handle a business
exception or track a related task in the case that you are currently
ad hoc case
processing. Because ad hoc cases are not instances of a case type,
they are not part of your case-type hierarchy.
A role-based authoring environment focused on system operations
Admin Studio such as agents and queues and APIs. Targeted for experienced
system admins.
An agent is an internal background process operating on the server
agent that runs activities on a periodic basis. In a multinode cluster, an agent
can run on multiple nodes.
(PRPC 6.x) An aggregate property stores more than a single value,
such as a Value List, Page List, Value Group or Page Group, or a page
aggregate property
that can contain a Java object. These are similar to arrays, repeating
groups, unordered sets or collections found in other development tools.
A tool that presents Pega's methodology of the Scrum Framework for
application development teams, product owners, and stakeholers to
Agile Studio
collaborate on features, plan releases, and execute development tasks
in the context of Agile or Scrum project.
A tool for project stakeholders that captures real-time feedback about
Agile Workbench
your application and tracks feature development.
An alert event is an entry in the alert log. Alert events use the naming
alert event
format PegaRULES-Alert-YYYY-MMM-DD.log.
The alert log contains a sequence of text files (known as alert events)
that support performance-related monitoring. The alert log supports the
Alert log optional Autonomic Event Services (AES) Enterprise Edition product,
which summarizes and monitors alerts across multiple nodes in a
cluster
An alternate path in a process consists of alternative steps that a case
alternate path might take from the primary path. You can add alternative steps to the
primary path of a starting process or to a subprocess.
An application is a business solution that automates work flows in your
organization. Multiple, unrelated applications can be hosted in the
application
same system. You create an application by running the New
Application wizard.
(PRPC 6.x) The Application Accelerator (AA) is a wizard that leverages
data captured in an Application Profile (or directly in the Application
Accelerator) to speed the creation of new applications or the extension
Application Accelerator of existing applications. The AA automatically creates a case, and a
(AA) baseline application that includes organization and class structure,
draft processes and UI elements. This baseline application can be
modified to implement functionality and create a functioning, production
application.
 The Application-Based Assembly (ABA) cache identifies rules for which
rules assembly on the current node is complete. Each rule that
Application-Based generates Java and executes is a candidate for the ABA cache. Note:
Assembly cache ABA caching is the previous generation of caching technology for the
Pega 7 Platform. UI (stream aspect) rules run using ABA caching, and
all other rule types run using VTable caching.
An application document contains a high-level business overview,
including information on case types, flows, user interface,
Application document
specifications, and requirements. You can create an application
document by running the Document Application tool.
Application-editing mode is a view that you can enable in Pega
application-editing
Express to access tools and information. To enable application-editing
mode
mode, click Turn editing on.
The Application Explorer is a tool that you can use to quickly access
records in the current and built-on applications that are available to
Application Explorer
your operator. These records are organized by work pool, case type,
category, and record type.
The Application Express is a wizard that you can use to quickly create
an initial application with a minimum of technical expertise. You can
Application Express
then add flows, user interfaces, and other rules to complete the
application.
An application menu in Designer Studio, that is identified by the name
application menu of the current application. This menu allows users to switch
applications, create a new application or switch work pools.
An application name is a meaningful and unique name that conveys
the purpose of your application. You specify an application name as a
application name
key part for the following application rules: Rule-Application, Rule-
Application-UseCase, Rule-Application-Requirement
The Application Packaging wizard allows you to create a product
Application Packaging archive that contains all of the classes, rules and data that make up an
wizard application. The result of the wizard can be exported to a ZIP file and
then imported or migrated to another Pega system.
An application profile is an auto-generated document, or set of landing
pages containing business-related information that is associated with
the implementation of a project. This information supports the Direct
application profile
Capture of Objectives (DCO) and includes the processes, case types,
reports, requirements, specifications, participants, collaborators, and
actors for a project.
A high-level scoping document that can be produced from content in
an Application Profile. This document contains application-specific user
Application Profile input that includes, but is not limited to, case types, specifications,
document requirements, objectives, interfaces, reports and correspondence
associated with the selected application. The user can control which
rules and sections appear in the document.
The Application Profiler is a wizard that allows users to enter
information about the application or framework that is being built or
extended. The Application Profiler creates an Application Profile and
Application Profiler
can also produce a printable project document. The Application Profile
generated by this wizard can be imported by the Application
Accelerator to create or extend an application or framework.
An application rule defines a set of ruleset versions added as a unit to
a user's ruleset list. An application rule is an instance of the Rule-
application (rule)
Application rule type, which is part of the Application Definition
category.
An application ruleset is a collection of rules that identify the
application rulesets
components of an application. You must be a member of a specified
 access group to work with an application ruleset The set of application
rulesets determines which rules are reflected in various tools in
Designer Studio, such as the Application Explorer, the Profile Explorer,
and the Guardrails tool.
The application scoping control is a reusable gadget that filters by
application layer, class name, and specified search term. The
application scoping
combination of filters used depends on how the control has been
control
configured. This control is used throughout the Pega 7 Platform, but is
most commonly found on landing pages.
Application Validation (AV) mode is used during rule validation to
Application Validation determine which rules are valid to reference at design time without
mode having to use ruleset prerequisites. Using AV mode offers performance
advantages over the alternative Ruleset Validation (RV) mode.
An application bundle is a .zip archive file that contains an XML
document known as the manifest. During import of an application
applicaton bundle
bundle, the manifest controls the order in which rulesets, rules, or other
items in the bundle are imported.
A role-based authoring environment focused on application
App Studio development targeted for use by business analysts, app develoers,
UI/UX developers and data engineers.
Arbitration is a process that involves a neutral third party - often a
retired judge - who hears arguments from both sides and makes a
decision. The decision is enforceable in court, meaning it may be used
arbitration
to garnish wages or seize assets. Arbitration is frequently used by
employers and service providers such as phone companies, as well as
by banks and card issuers.
An area chart displays data points with filled space rather than points,
area chart curves, or lines. You can specify the chart type and subtype for a
report definition report by using the Chart Editor
An artifact is an element of the application development process, such
artifact
as a design document, requirement, specification, or UI mock-up.
A collection of rulesets that represents an application, including the
Application rulesets defined for the Application rule, the Application
Assign-
rulesets defined for any built-on application and the local customization
ruleset.
The Assign- base class is an abstract class above other classes
Assign- base class
containing assignments.
An assignment is a task that must be completed before an open case
can continue through an executing flow. You configure assignments in
assignment
a flow by using Case Designer or Process Modeler. Either a user or
external system can act on an assignment.
An assignment (shape) identifies a task that must be completed by a
user or external system before an open case may continue through an
executing flow. An assignment indicates that the case is temporarily
assignment (shape)
paused until a user acts on the case. The user selects the appropriate
action to complete the assignment, and provides any information
required by the application to support the action the user selects.
An associated ruleset is a ruleset that is linked to instances of data
associated ruleset classes. Associated rulesets help to identify which data instances to
include in an application package or when you export rulesets.
An association is a rule type that defines a one-directional relationship
between two classes, used often in reporting to include properties from
another class in a report. The rule predefines a JOIN-type relationship
association
between instances of two classes, such as Operators and
Assignments, or between cases and custom data classes, such as
those created by data tables or external database connections. Unlike
 joins, association rules work automatically when a manager or
developer builds a report.
Asynchronous JavaScript and XML (AJAX) is a coding technique used
Asynchronous in interactive web applications to exchange small amounts of data as
JavaScript and XML needed, so that the entire web page does not reload each time users
(AJAX) request a change. Pega uses this technology when processing server-
side validation rules and for calculated value expressions.
An attachment is a document, image, or other file added to a case to
attachment
provide additional information.
An attachment category controls the security of attachments in your
attachment category application. It restricts user operations on an attachment, based on
(rule) privileges, when conditions, or attachment types. You can create
attachment categories for your cases in Case Designer.
An attachment type defines the media and format of items that users
attach to work in your application. An attachment type is implemented
attachment type 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.
An audit trail refers to the history of a work item. Open the Audit tab on
a user form to access the audit trail, which shows information that
audit trail
includes which operators worked on the work item and when, and what
automatic processes were performed by the application.
Authentication is the process of determining the identity of a user or
requestor of services. In Pega, authentication is accomplished by
authentication
matching the submitted user name and password to those stored in the
users Operator ID.
A user interface control that supports user selection of one text value
from a large list of candidate values. As the user types in the field, a
Autocomplete
filtered list of qualifying text values appears below the input field. Users
can then select a value from this list.
An autocomplete field on a form supports user selection of a text value
from a list of candidate values. After you enter one or a few characters,
a filtered list of qualifying text values displays below the input field. On
Autocomplete field
an input field, the icon indicates that autocomplete is available for the
field. You can configure styles for the Autocomplete control in the Skin
rule
Auto-generated is a term used to indicate that executable code was
automatically generated by Pega, rather than being written by
application developers. Auto-generated code is commonly created
when configuring UI rules (sections and controls). When a rule form is
auto-generated saved, Pega translates some types of rules (such as control, section,
flow action and harness) to HTML, JSP tags and JavaScript. These
auto-generated rules eliminate hand-coding and usually provide better
performance, security, browser independence and more consistent
branding and styles than hand-crafted rules.
An Automatic Call Distributor (ACD) is the equipment (or software)
Automatic Call
used to direct incoming calls to service representatives in a call or
Distributor (ACD)
contact center.
Autonomic Event Services (AES) is an optional product that monitors,
Autonomic Event
retrieves, organizes and displays Pega 7 Platform system statistics and
Services (AES)
warning conditions at the enterprise, cluster, and node levels.
An auto-populated property is a Page or Page List property that
automatically obtains its data directly from a specified data page. The
auto-populatied
values can be an entire object from the PegaRULES database, or
property
copies of pages developed by a Data Page rule. To enable auto-
population for a Page mode or Page List property, configure the Data
 Access fields on the General tab of the Property form.
A page or page list property that automatically obtains its data directly
auto-populating from a specified data page. The auto populate can be in the form of a
property pointer or a copy and is triggered whenever the parameter value for the
given data page changes.
Auto-processing is a feature that allows Pega to perform an
assignment automatically under certain situations. To auto-process an
assignment, the assignment must be configured with a set of when
Auto-processing
rules and corresponding flow actions. At run-time, Pega evaluates the
when rules in top-down order and performs the flow action that
corresponds to the first when rule that returns a true result.
The state or status of a rule, used to determine if a rule is visible and
can be executed when called during rule resolution processing.
availability Availability is determined by a developer. PRPC provides five possible
values: Yes, No/Draft Mode, Blocked, Final and Withdrawn. The rule is
available if the availability is set to Yes or Final.
An available rule is visible and can run during rule resolution
available rule processing. For an available rule, the value of the pyRuleAvailable
property set to Available or Final (and is not blocked).
A bacground process is an autonomous process that occurs with little
background process or no user intervention. Examples of a background process include
logging and system monitoring.
A backlog is a prioritized list of user stories, bugs, and issues for a
product. It is the responsibility of the product owner to prioritize the
backlog backlog. In PMF, you can associate items in your product backlog with
a release to create a release backlog or project teams to create a team
backlog.
The term back-to-back assignments describes a situation when a user
back-to-back completes an assignment for a specific work item and then works on a
assignments second assignment for the same work item. The second assignment
can be from the same flow execution or an unrelated flow execution.
Backward chaining 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
backward chaining
Property-Seek-Value method working together, and can be seen in
standard flow actions including VerifyProperty and
VerifyPropertyWithListing.
A bar chart displays property values as horizontal bars. You can
bar chart specify the chart type and subtype for a report definition report by using
the Chart Editor.
A base class is one of twelve standard abstract classes that are
base class immediately below the top class in the hierarchy. This top class, known
as the ultimate base class, is identified by the symbol @baseclass
The ultimate (topmost) parent class in the class hierarchy for any Pega
@baseclass (ultimate
application. All other classes are derived from this class. The standard
baseclass)
rules in this class are available for every object in the Pega system.
A base rule is the original version of a rule that has been
base rule circumstanced or time-qualified. A base rule must exist for every
circumstance or time-qualified rule.
In Decision Management, a behavioral profiles is a representation of a
behavioral profile univariate model that is based upon a single behavior variable, like
usage or loyalty.
Best Bets provide a subset of options that are likely to have the choice
best bet you are looking for. Best Bets are classes in your application that are
the Applies To key part of one or more rules.
binary file (rule) A binary file is a rule type in Pega that identifies static content files that
 contain information in a non-text format, such as images and PDF
documents. Binary file rules store data in a Base64 format to support
endian-independent, character-set independent processing. When
extracted or downloaded, the file is reconverted to its original format.
A collection of binary data stored as a single object in a database. A
BLOB can store any amount of digitized information, and supports text,
Binary Large Object
images, audio or video. PRPC uses BLOB fields to store all of the data
(BLOB)
for a case in a proprietary, compressed format that is highly optimized
for performance and flexibility. Also known simply as a "large object".
A blocked rule has an availability status that indicates to the rule
blocked resolution algorithm that the rule (and all others of that type with the
same name or key, in any ruleset) is not executable.
A branch is a container for rulesets with rules that are undergoing rapid
branch
change and development.
A branch ruleset is based off another ruleset and contains rules that
branch ruleset
are in active development in the associated branch.
The breadcrumbs control shows each task, or entry point, in a flow
execution. Application users can click a task based on settings in the
breadcrumbs control
flow. The flow can allow users to jump to any task in a flow, or just to
the completed tasks.
A bubble chart 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
bubble chart
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 for Change is Pegasystems' corporate slogan and application
development philosophy, that acknowledges the continuous evolution
Build for Change
of business processes through methodologies and tools that embrace
flexible procedures.
The Build Order is part of the Construction phase of the Pegasystems
Professional Services project methodology, and specifies the
build order 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.
A journey-centric phase in the Pega Delivery method. Continuously
build and test sprints. Incrementally complete and deliver work
Build phase
throughout the project and plan for the work of one iteration to be
improved upon in subsequent iterations.
Bulk processing is a term that inidcates an action is going to occur on
multiple assignments in an application. For example, a user could bulk
bulk processing
process either the approval or rejection of multiple purchase orders as
one action.
A Burndown Chart shows the amount of work planned, remaining and
completed in a release, sprint or by a project team. The horizontal X-
Burndown Chart axis shows time starting and ending based on the dates of your
release, project team or sprint. The vertical Y-axis shows effort in story
points or hours.
Business analysis defines needs and identifies solutions that add value
business analysis
to the business.
The Business Analyst portal is an alternative portal to the full Designer
Studio which provides access to those Pega facilities most useful to
Business Analyst portal
Business Architects. (In Pega 7, the Business Analyst portal has been
removed, and its functionality merged into Designer Studio.)
 A business architect is a member of an application development team
who defines and maintains business rules, service-level agreements,
and processes (flows). Business architects include subject matter
Business Architect (BA)
experts, business analysts, business executives, and business end
users. A business architect might also be referred to as a process
architect
Business data is a term that provides the context for a given task for a
business data
given participant.
Business days, also known as work days, are scheduled work days for
users. Business days are not identified as holidays or other days with
business day 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.
A business exception is an unusual condition within a business
process that warrants investigation or external review. A business
business exception
exception might indicate fraud, error, compliance failure, or other
potential harm to the organization, customers, or other parties.
Business Intelligence Exchange (BIX) is an optional add-on product
consisting of a ruleset and a stand-alone Java program that can be run
from a command line. BIX provides the extract functions of an ETL
(extract, transform, and load) utility by using the Pega-BIX ruleset,
Business Intelligence
which supports the Rule-Admin-Extract rule type. Data is extracted and
Exchange (BIX)
exported in a format suitable for use in popular business intelligence
applications, such as data warehouses. High-performance, multi-
threaded extraction operations operate independently of the Pega 7
Platform, and can occur even when the Pega 7 Platform is not running.
Business metrics describe a company's case performance, such as the
number of orders processed or how many orders are canceled.
business metrics
Business metrics represent the data that you have defined when you
create properties.
A business objective is an expected business outcome or goal for an
Business objective
application.
Business process management (BPM) is the organizational activity of
developing and managing processes that are responsive to change
Business Process and improve business performance outcomes. When an organization
Management (BPM) uses BPM, they coordinate the presentation of the user interface, the
logic, and the data access for an application with the process for how
work gets done.
Business Process Modeling Notation (BPMN) is a specification that
Business Process provides a graphical notation for expressing business processes in a
Modeling Notation diagram. The BPMN specification also defines the relationships
(BPMN) between the graphical elements and process execution languages
such as BPEL.
business rule A business rule is a requirement that defines, constrains, and enables
requirement organizational operations.
A business rules engine (BRE) is a Java-based rules engine that
separates business logic from applications and enables the enterprise
Business Rules Engine to capture, manage, and execute business policies and practices as
(BRE) business rules. The business rules engine supports declarative rules,
multithreaded execution, and a large number of industry interfacing
standards.
A Business Use Case is a type of use case (specification) that
describes a business process from beginning to end without regard to
Business Use Case
process ownership. It can involve many different actors and has a very
low likelihood of being reused within an enterprise.
Business Value Business Value Assessment (BVA) is a phase of the implementation
Assessment (BVA) 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.
Cache is a collection of data automatically maintained at an
intermediate point between the requestor and the ultimate source of
the data. Multiple types of caches, representing various types of data,
cache
exist in Pega, enabling faster access to rules or data stored in the
PegaRULES database or on another system, especially during rule
resolution searches.
The Calculation Builder is a tool that provides a guided interface to
Calculation Builder
help you define SQL expressions for use in report definition rules.
A calendar 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, workbasket, and Operator
calendar
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.
A call center is an office or location used by an organization to receive
call center
large volumes of calls from its constituents.
A card association is a network of issuing banks and acquiring banks
that process payment cards of a specific brand. The Visa and
Mastercard associations do not issue credit or debit cards directly.
They each collectively comprise thousands of banks worldwide. These
card association
banks pay membership fees to the associations, and are permitted to
issue cards. American Express, Diners Club, and Discover are not
associations. Each of these companies issues its card directly, and
maintains its own clearing network.
Case Designer is a tool that helps you visually model stages, steps,
and processes for all case types in your application. Its centralized
view lets you capture objectives without switching context between
Case Designer individual rule forms and your case type. Use it to design staged-based
case types, build user forms, and seamlessly integrate with other rules
in your application. To access Case Designer, open the Case Type
Explorer and click any case type name.
A case ID is a permanent, external identifier of a case. A case ID is the
case ID (work item ID) value of property pyID. The value is unique system-wide and contains
an optional prefix, a number, and an optional suffix.
Case instantiation is the way that a case is created in your application.
You can manually create a case or automate this process based on the
case instantiation
creation of a parent case, a set of when conditions and case-type
dependencies, or received email.
Case Management is a business practice that helps you deliver
outcome driven results. It relies on case types to model customer
processes, share information, and ensure that there is visibility into the
work that is completed by your application. Case Management
case management
automates service-level agreements, escalation, and audit trails so that
you can provide a quality, end-to-end customer experience. Use the
Case Type Explorer and Case Designer to build a Case Management
strategy in your application.
A collection of examples of case types that use many of PRPC's case
Case Management management capabilities and represent best practice implementations
Gallery that comply with Pegasystems’ guardrails. These examples can be
copied into an application and extended as needed.
A case manager is an application user who can view and update
case manager
delegated business rules, in addition to performing work.
Case Manager portal The Case Manager portal supports users who manage cases and their
 related sub-cases and tasks across multiple channels, lines of
business, departments, and systems. Users can create, view, and work
on cases and assignments.
A navigation feature in the Designer Studio that allows users to view
Cases Explorer
and modify case type relationships in an application.
Case status is the primary indicator of the progress of a case towards
case status resolution. Case status is the value of the standard property Work-
.pyStatusWork.
A case (step type) is a setting for a case step that configures the step
case (step type)
to generate another case of a specified type.
The Case Type Explorer is a tool that lets you view all of the case
types that are in your application. Use it to manage the hierarchical
structure of your case types, access Case Designer, and browse
Cases Type Explorer
examples of case management rules that you can leverage in your
application. To open the Case Type Explorer, click the Cases icon in
the explorer panel of Designer Studio.
A case type represents work in your application that follows a life cycle,
or path, to completion. Each case type has a hierarchical structure and
case type
can include attachments that provide relevant details about the work
that you are processing. Instances of case types are called cases.
The case type backlog is the inventory of the application's out-of-the-
box case types and should be updated with notes about what needs to
change in existing case types, and what additional case types and
case type backlog other requirements need to be developed and launched in a Minimum
Lovable Product (MLP) release. The backlog contains both the MLP
that will be delivered in the initial release plus items that may become
scope for future releases.
A case-type dependency is a condition that must be met before a child
case type dependency case is instantiated or an assignment is automatically completed. Each
condition defines a case and a status.
A case type (rule) establishes how to create a case, including the
case type (rule)
relationship between the case and any parent or child case.
A case worker is an individual responsible for creating, processing,
case worker (operator)
and/or resolving a case.
The Case Worker portal provides case workers with a standard
interface for creating, viewing, and working on their own cases and
Case Worker portal
assignments. Users cannot monitor and manage work among other
operators or workbaskets, or view work statistics.
A case is an instance of a case type and is a primary unit of work in an
application. You can manually create, or instantiate, a case in an end
user portal or through forms in an application. Your application can
case (work item) automatically create a case when a parent case is created, or email is
sent to an account that is associated with the starting process of a
parent case. In legacy systems, cases are commonly referred to as
work items or work objects.
A category is a systematic grouping of rule types and data types in
Pega. Categories are used in the Application Explorer, My Rules,
category
Records Explorer, Rules Explorer (in versions of Pega prior to 7.1),
attachments and reports to enhance navigation.
A category (rule) defines an organizational framework for reports
displayed in the Report Browser. Each category consists of a label and
category (rule)
an owner type, which exposes the category to a specific audience,
either an individual user, a group of users, or all users.
A certificate set gathers in one place all keys and certificates needed to
certificate set
properly configure, build, and run an Android or an iOS mobile app.
Certified System A Certified System Architect (CSA) is a Pega 7 Platform application
Architect developer or technical staff member who has passed an exam that
acknowledges the acquisition of foundation-level knowledge of the
Pega 7 Platform.
A change control requirement documents a modification to a Pega
change control
application. You can implement modifications before or after the
requirement
release of an application.
A channel is a mode of communication or interaction, such as
channel
telephone, email, or fax.
A chargeback is a movement of funds from the merchant back to the
customer, caused by the customer's denial of a charge on the credit or
debit card account. This usually happens when a customer calls the
credit card company to dispute a charge because the products or
chargeback
services were not received. This can also happen if a card number was
used fraudulently and the merchant cannot prove that the charge was
legitimate (made with the permission of the legal cardholder), then the
chargeback is made permanent.
The Chart Editor is 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
Chart Editor
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 / check out is a rule management process that allows
application developers to reserve a rule for editing, to avoid conflicts
arising when more than one developer simultaneously try to edit the
rule. Upon check out, a copy of the rule is added to a ruleset reserved
check in/check out
solely for the developer who checks out the rule. When the rule is
checked back in, the rule is copied back to the original ruleset,
overriding the previous version, and the updated rule is available to be
checked out again.
The checkin process replaces a base rule version with a private copy
of a Rule- instance that you checked out and updated. A checkout is a
checkin process 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.
A child case type represents work in your application that must be
completed to resolve a parent case type. Child case types can be
child case type
instantiated manually or automatically. You can view your child case
types in the Case Type Explorer.
A circumstance is an optional qualification available for supported rule
types. Commonly referred to as a ""circumstanced"" or ""specialized""
circumstance version, a circumstance is based upon an unqualified rule known as
the base rule. Using circumstances in your application allows you to
easily support a variety of use cases.
Circumstancing is the practice of creating additional variants of a rule
based on specific circumstances, such as property values. When the
circumstancing circumstancing criteria are met, Pega automatically executes
whichever version of the rule either the base rule or the qualified
circumstanced version of the base rule.
A class is a collection of rules or other objects. Each class defines
capabilities such as properties, activities, and HTML forms that are
available to other, subordinate classes, or to instances of the class.
class
Classes are organized into a hierarchy, where the system searches the
class hierarchy from the current class upwards when looking for a rule
to apply.
A class diagram provides an overview of an application by showing its
class diagram
classes and the relationships among them.
 Class Explorer is a navigation feature in the Designer Studio that
displays portions of the class hierarchy differentiating between abstract
Class Explorer
and concrete classes. In Pega 7.1 and later, the Class Explorer has
been merged into the Application Explorer.
A class group is an instance of the Data-Admin-DB-ClassGroup class
and corresponds to tables in the PegaRULES database. Class groups
cause the system to store instances corresponding to two or more
class group
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.
The class hierarchy is a hierarchical structure that supports the sharing
of rules and data. The ultimate base class (@baseclass) is the topmost
class hierarchy
class in the class hierarchy. All other classes are derived from this
class.
A classification is a text value in the prconfig settings or Dynamic
classification System Settings that is used to group nodes that share specific setting
values in a multinode or clustered system.
Class inheritance is the method by which a child class can use all of
the rules defined for a parent class. The Pega Platform supports two
types of class inheritance: directed inheritance and pattern inheritance.
class inheritance
Both types of class inheritance allow rules of ancestor classes to be
inherited. However, class inheritance does not apply to external
classes, even if the class name contains a hyphen.
A class name prefix is used during pattern inheritance when the Pega
7 Platform searches the class structure to find a rule using a sequence
class name prefix
of prefixes of the class name. The hyphen delimits segments of the
name.
The Client Event Editor is a tool you use to define the runtime behavior
of a control when an OnChange, OnBlur or OnClick event occurs for
Client Event Editor
non-auto-generated controls, or for auto-generated controls configured
with client events in versions of Pega prior to 6.3.
A clipboard is a temporary memory area on the server that is
associated with every connected Pega Platform requestor, including
Clipboard
browser-based users and unauthenticated guest users. The clipboard
has a hierarchical structure, consisting of nodes known as pages, most
of which have a name and an associated class.
A clipboard message is a text clipboard value, generated by the
clipboard message system and associated with a property or a page. A clipboard message
can convey error conditions, progress, or exceptions to a user.
The Clipboard tool is a debugging and troubleshooting aid for
application developers. The tool lets an application developer examine
Clipboard tool a snapshot of the structure and contents of his own clipboard and
sometimes change these from his workstation browser. The clipboard
resides on the server.
In Customer Service, a coaching tip helps improve employee
performance and reinforces best practices. Users with the appropriate
coaching tips
privilege can create coaching tips for any screen that is available in a
customer interaction.
The Code- base class contains all the classes that define the objects
used by the Pega 7 Platform's own implementation. Application
code- base class
developers can work with properties and clipboard pages associated
with classes derived from the Code- base class.
In Decision Management, a coefficient is a weight used for each
predictor in the logistic regression formula. The coefficient indicates the
coefficient
importance of a predictor. Negative coefficients imply the presence of
predictors with a very similar behavioral profile, and their presence may
 lead to over fitting and unreliable models.
In Decision Management, the Coefficient of Concordance (CoC) is a
non-parametric coefficient statistic that is used to measure and
compare predictive models. The CoC can measure how well the
scores generated by the predictive model separate positive from
negative outcome cases. These coefficients are sensitive to the
Coefficient of complete range of score bands regardless of their distribution. The
Concordance (CoC) CoC can vary between 50% a random distribution of positive and
negative cases by score band and 100% a perfect separation. The
minimum is 50% because the scores are simply used in reverse if a set
of scores orders negative cases before positive cases. If the desired
operational circumstances volume or quality of business are unknown,
CoC generates powerful and generalized models.
A collaboration flow supports discussion among co-workers. The
collaboration flow system saves each participant's inputs as note attachments, similar to
a discussion forum thread.
A collection defines an ordered sequence of rules to run. On each step
collection you can define a precondition that is evaluated prior to execution, and
a response action that runs after the step completes.
A column chart displays values as vertical bars. You can specify the
column chart chart type and subtype for a report definition report by using the Chart
Editor.
An advanced utility for database and schema maintenance that
updates rows of PegaRULES database tables after database schema
changes. It can populate values for a new column corresponding to a
Column Population
newly exposed property, exposing values that are previously stored
utility
only in the Storage Stream BLOB column. Optionally, it can also
rebuild database indexes and Index- instances defined by Declare
Index rules as part of the same operation.
The Column Populator is a utility for database and schema
maintenance. It is a command-line script that allows you to update
rows of database tables after database schema changes. This utility
Column Populator can populate values for a new column corresponding to a newly
exposed property, exposing values that were previously stored only in
the Storage Stream (BLOB) column, and optionally rebuilding database
indexes and Index- instances defined by Declare Index rules.
A combo chart combines and displays the data from both a column
chart and a line chart. A combo chart has either a single y axis
combo chart (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 hotfixes are permanent parts of the system. You cannot roll
committed hotfix
back a committed hotfix.
A compensating action allows a custom activity to update the Pega 7
Platform application data to negate the effects of a connector failure.
compensating action
This type of action is an optional feature of Connect SOAP and
Connect dotNet rules.
Compliance is the adherence to operational regulations set by the card
association. A compliance case may be initiated by the issuer or the
acquirer. For example, when a transaction dispute is outside the
chargeback time frame, a compliance case may be initiated by the
compliance
acquirer. A compliance case can be filed when; a member or its
affiliate has violated one or more of the MasterCard or Visa bylaws and
rules or the filing member documents a financial loss as a result of the
violation.
compliance score A compliance score is a weighted score for each application that
 measures overall compliance with the Pega Platform best practices.
This score is available on the Guardrails landing page.
A component ruleset contains rules that are designed to define
reusable applications or functionality that executes embedded within
component ruleset
an object. When a component ruleset is installed in multiple systems,
the class of the object might vary from system to system.
A composite portal is a user portal defined by a collection of harnesses
composite portal that each references a screen layout. Each harness defines an entire
portal window.
The composition grid in the Data Designer lets you review and manage
composition grid the selected data type's properties. The composition grid appears on
the Definition tab of a data type.
Computer Telephony Integration is a technology that enables computer
applications to interact with telephony systems. For example, a
desktop application may use CTI to control a users telephone and
Computer Telephony
place calls. In call centers, CTI software allows applications to monitor
Integration (CTI)
and act upon calls (such as transferring a call). Using PegaCALL,
Customer Service supports CTI capabilities such as screen pops and
desktop telephony control.
Concrete classes are displayed anywhere below the top level of the
class hierarchy, often near or at the bottom of the list. There are
concrete class
several types of concrete classes: internal classes, external classes,
rule types, and work types.
The Condition Builder is an editing tool used to define conditions and
Condition Builder
ensure that expressions are valid.
Connection pooling refers to 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
connection pooling
maintaining of a separate database connection for each requestor.
When using connection pooling, a database connection is returned to a
pool when no longer needed by a requestor and made available for
future requests.
The term connector is used in the following two 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. A connector is also a
connector
programmatic component that defines and implements an interface
between a Pega Platform application that is acting as a client, and an
external system that is acting as a server. A connector is implemented
by any of the rule types in the Integration Connectors category.
A connector flow action completes the current assignment and
advances the flow to the next shape in the sequence. Connector flow
connector flow action
actions are configured on the line shapes, or connectors, in a flow that
exit assignment shapes.
The Connector and Metadata wizard imports information about an
external application or system and configures direct table access
without the need for SQL connector rules. This wizard generates
connector rules or data mapping rules and creates a data class for
Connector & Metadata
each table in the database we want to work with, creates properties in
wizard
our data classes for each column in the tables we want to interact with
and creates the activities that allow applications to interact with the
database in an external system such as create, read, update, and
delete.
A connector rule is a type of integration rule that allows an application,
connector (rule)
acting as a client, to interact with an external system or database.
 A constraint is a comparative relationship between property values (or
constraint between a property value and a constant or expression) that is
expected to be true at all times.
A rule used to define and enforce a declarative rather than
programmatic comparative relationship between property values or
between a property value and a constant or expression that is
expected to be true at all times. Ensures that values entered by a user
do not deviate from the desired range for a single value or embedded
constraints
property when a specific condition is met, providing an automatic form
of property validation every time a property value is touched. If a user
enters a value that deviates from the intended range, a message is
displayed, the page is invalidated, the process is stopped and the user
cannot proceed until the entry is corrected. Contrast with validate rule.
In Pega BPM, the Construction phase is where application features are
configured, integrated into the application, and thoroughly tested. The
outcome of this phase is a user-ready product running on the adequate
Construction phase
platforms, with user manuals and a description of the current release.
A large project may have parallel construction activities to accelerate
deployment.
In Customer Service, a contact is the person with whom the user is
contact interacting. A contact can be a customer, prospect or other interested
third party.
In Customer Services, a contact center is an office or location used by
contact center an organization to serve customers over multiple channels such as
telephone, email and text chat.
The contact preference indicates how a work party wants to be
contacted. For example, some parties might prefer to receive
contact preference correspondence as email, by fax, by phone, or through the mail. The
contact preference is always email for users identified as a party of the
Data-Party-Operator class.
A container is a structural element of a harness that corresponds to a
visually distinct rectangle on the form, marked by a colorful border.
container
Harnesses are made up of containers, which contain sections, though
not every harness includes a container.
A container class is a concrete or abstract class that unifies a set of
classes in the PegaRULES database. It has a name that corresponds
container class
to a class group. The class group, in turn, has a name that matches a
class rule.
A Content Security Policy is a set of directives that is used to control
what displays in a client's browser by informing the browser of
Content Security Policy
locations that it can use to obtain content. Each directive governs a
specific resource type.
Continuous behavior is a range of values which is usually ordered, for
continuous behavior
example, the purchase amount, or length of a relationship.
A control rule used to dictates how properties appear on user forms,
correspondence and other HTML forms, for both display and accepting
control
user input. Pega provides many standard controls, which are preferred
over custom controls.
Co-production is the active involvment of the customer business or
technology staff in the development and testing of your Pega
application. Customer resources are trained on Pega technology, then
co-production
mentored by Pega to further develop skills. Over time, resources build
the competence to support and expand the Pega application with little
or no help from Pega.
Correspondence is an outgoing email, letter, fax, or text message that
correspondence
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.
The Correspondence Output Server is an optional Pegasystems
application that supports printing and faxing of correspondence. The
Correspondence Output
COS can convert correspondence into an attractive formatted print
Server (COS)
image using Microsoft Word and send the result to a hard copy printer.
Also known as PegaDISTRIBUTION Manager.
A correspondence template is a rule that is referenced in a flow to
correspondence
provide a template to specify the format, content and type of
template
correspondence.
The correspondence type defines whether a correspondence is a
correspondence type
printed letter, a fax, an email, or a text message.
A cover is a case that is a parent to 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.
cover 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.
In Customer Service, a CPM Data Source is a type of rule used in
Customer Service applications to access data from external systems.
CPM Data Source
The CPM data source rule abstracts the details of integrating external
data from the user of the data.
A Create Case command is an abstraction between the topic returned
Create Case command from the Natural Language Processing and a case in your Pega
application.
Credentials 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
credentials 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 that provided by Microsoft Active
Directory.
A Cascading Style Sheet (CSS) is a standard established by the World
CSS 3 Wide Web Consortium (W3C). A CSS allows a web application to
separate formatting instructions from content.
A customer is a work party, and typically, a case is initiated by or on
customer behalf of a customer. In many applications, only one customer can be
associated with a case.
In Customer Service, the Customer Composite is a UI area consisting
of individual tabs or sections that display information about the
account, contact and account owner. Information in the customer
Customer Composite
composite areas may come from the customer service database or
from other third-party applications and databases within an
organization.
Customer Process Manager (CPM) has been renamed to Pega
Customer Process Customer Service and is a Pegasystems flagship application, used to
Manager (CPM) enable multi-channel, intent-driven processes for customer relationship
management (CRM).
Customer satisfaction 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
customer satisfaction
performed the work properly or in accord with your standards or
industry standards. Use the standard property Work-
.pyStatusCustomerSat to record customer satisfaction.
 A Customer Service Representative is a person employed by an
Customer Service organization to serve its customers. CSRs may interact with customers
Representative (CSR) using several channels including the telephone, e-mail, letters and text
chat.
A custom field is an instance of the Index-CustomFields class that has
two parts, a name and a value. Associating custom fields with rules
custom fields provides a flexible way to supplement your application with metadata,
such as a change order number or log file attachment. Custom fields
are not available for Data- objects.
A customization ruleset is an application ruleset used as the default
customization ruleset
ruleset when copying an existing rule or creating a new rule.
A daemon is a reserved background Java thread that executes as a
BATCH requestor type. Daemons behave similarly to an agent, but
daemons are not defined by a Rule-Agent-Queue rule type, are not full
daemon
requestors, and operate continuously and automatically. The Pega
Platform includes the following daemons: License Compliance, Master-
for-Agent, Master-for-Requestors, Node, Passivation, and Usage.
The Data- base class is a top-level abstract class that defines and
contains static data and cumulative data. Pega 7 Platform applications
data- base class often retain essential and frequently used data in the PegaRULES
database, which is organized into concrete classes derived from the
Data- base class.
A database table is a set of related data in a database, organized into
rows and columns. Each column contains a different attribute, such as
database table
a property value, and each row corresponds to a single record, such as
a case.
A data class is a concrete class used to represent a data object, such
as a person Customer, Vendor in a Pega application. Each data class
data class
contains properties and other rules that describe the behavior of the
object represented.
The Data Designer lets you review and manage data types in your
Data Designer application. When you select a data type in the Data Explorer, the data
type opens in the Data Designer.
The Data Explorer is a navigation feature in Designer Studio that
provides an overview of selected data object types and their
Data Explorer associated data pages, and how often they are referenced. Use the
Data Explorer to view, understand and manage your data object types
and their associated data pages.
The DataGrid control is deprecated. Update an existing DataGrid to a
DataGrid control
Grid control.
A data instance is an instance of a concrete data class, a concrete
data instance class derived from the Data- base class. For example, a workbasket is
an instance of the Data-Admin-WorkBasket class.
A data mapping is a table or array that associates data fields received
from or sent to an external application with properties or other sources
data mapping
or destinations in Pega Platform. Data mapping is defined in service
and connector rule forms.
A data model is a collection of entities and attributes that describes the
data model
objects modeled in an application, and their relationship to each other.
A Data Model category is a grouping of rule types in Pega that store,
manipulate, and validate information about a case. The Data Model
data model (category)
category includes property, data page, data transform, field value, and
edit validate rules.
A data page is used to cache data on demand to a clipboard page for
data page (declare
use by one or more applications. A data page rule defines the source,
page)
scope, refresh strategy, editability, and structure of the cached data.
 Data pages were previously known as declarative pages.
Data propagation is the act of itializing a case or other item of work
data propagation
with data from another case.
A data record is an instance of a data type stored for your application.
For example, Customer records would include data specific to each
customer, such as name, email, phone number, and so on. You can
data record
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.
A data reference is a type of field that you configure on a form. At run
data reference
time, it displays a list of data-type instances, or data records.
A data source is any source of data that an application uses, such as a
data source connector, report definition, or lookup. Data sources are referenced in
data pages.
Data tables are superseded by the local data storage feature. Click
data table Convert for each data table displayed on the Data Tables landing page
to convert it to the new format.
The Data Table wizard accelerates the creation of properties in a
concrete data class by generating the class and supporting rules to
make the data table an interactive data entry tool. This enables
business users to use the Data Table Editor to interactively enter,
update and delete database table items for classes that have a simple
Data Table wizard
structure. The tool creates a concrete data class and the properties in
the data class, list rules, editing rules, validation rules, and a data
transform rule to supply initial values for properties. Optionally, it can
also create a dedicated table in the Pega database and a
corresponding database table data instance.
A data transform (model) is a rule used to set default values for
properties on a clipboard page, copy one clipboard page to another,
map properties from one page to another, append properties from one
data transform (model) Page List property to another, and iterate over pages in a Page List
property to map data on each page. These rules define a sequence of
steps, and are executed in order, except when a conditional action,
such as a when condition or a transition action, is encountered.
Data types define and hold data for your application. For example, a
Customer data type might be used to manage customer contact
data type
information. It might include the customer's name, email, phone
number, and so on. Data types are managed using the Data Explorer.
Data views define the data associated with a data type and contain the
data type's connection configuration to a system of record, separating
your application from the integration with the system of record.
Data views
Because of this separation, your application can easily adapt to
integration changes and access data from a range of sources on
demand.
A set of application development tools and best practices designed to
DCO (Direct Capture of
capture and tie business and project goals, objectives, processes,
Objectives)
specifications and requirements to implementations.
A Direct Capture Objectives (DCO) session is a focused meeting of
four hours or less. The session brings together business architects,
system architects, and subject matter experts (SMEs) to elaborate on a
DCO session
set of high-level application specifications to identify and catalog the
details necessary to implement a flow, user interface, or other
application specification.
A deadline is an interval of time that is defined in a service-level
deadline agreement. It is the required resolution time for an item, such as a case
or stage.
 In Decision Management, a decision is the result of running a strategy
decision in the interaction context. Several decisions can be involved in a single
interaction.
A decision category is a grouping of types of records in Pega that
automate decision-making to enforce business rules and statements of
policy. Decision rules describe a set of comparisons, each one consists
of one or more conditions and a return result. When evaluated, Pega
decision (category)
identifies the most valid condition and returns the corresponding
outcome, such as an expense report that does not exceed $400, then
additional approval is not required. There are four types of decision
rules in Pega; when, decision table, decision tree, and map value.
The decision data defintion class is where the set of decision
decision data definition
properties is defined. You can add these properties to be displayed on
class
the decision data form.
Decision Management is the technology that implements Next Best
Action principles using the Decision Strategy Manager (DSM) so your
application can determine which processes to run and which products
should be offered to customers. Successful Decision Management
results in increased customer loyalty and the ability to address multiple
Decision Management
issues in the decision making process. Decision Management
(DM)
functionality includes proposition management, strategy development,
using strategy, scorecard and predictive model rules to drive process
flows, capturing interaction results using Interaction Services (IS),
visualization and monitoring, and advanced adaptive analytics using
Adaptive Decision Manager (ADM).
A decision shape within a flow diagram that calls a decision rule such
decision (shape)
as a decision tree, decision table or map value.
Decision Strategy Manager (DSM) is a Pega product for proposition
management. DSM uses strategy, scorecard, and predictive model
Decision Strategy rules to drive process flows and strategy development.�It also
Manager (DSM) captures interaction results using Interaction Services (IS), Visual
Business Director (VBD), Adaptive Decision Manager (ADM) and the
batch execution of strategies.
A decision table is a decision rule that defines comparisons by using a
table format to specify a series of tests performed on property values to
decision table
allow an automated decision. A decision table lists two or more rows,
each containing test conditions, optional actions, and a result.
A decision tree is a decision rule that defines comparisons by using a
tree structure. A decision tree contains nested if... then... else
decision tree
conditions to specify a series of tests performed on property values to
allow an automated decision.
The declarative network is an internal data structure that defines the
relationship between properties whose value is automatically
(declaratively) calculated based on changes to other property values.
declarative network
Complex relationships can be configured and visualized by using the
declarative network display, which depicts the target property and all
potential input that might affect its final value.
A declarative rule that relationships between properties so the system
can automatically use one or more input values to determine the value
of a property. Pega provides six types of declarative records:
declarative rule Constraints, Declare Expressions, Declare OnChange, Declare
Trigger, Declare Index and Data Pages (Declare Pages in PRPC 6.3
and earlier versions). Unlike other types of rules, declarative rules are
not called explicitly.
A declare page rule creates a read-only page on the clipboard that is
declare page available to multiple requestors in an application. Typically used to
store data that changes infrequently and is needed by more than one
 user. For example, a page may contain daily prices for a set of
commodities or currencies, an organization chart or inventory quantity
data extracted hourly from an external system. These pages can be
globally"" available to all requestors on a node.""
Queue Processor rules that meet a specific need. Use these rules for
Dedicated queue
high-throughput, distributed processes critical to an application or for
processor
delayed queuing.
Define Properties The Define Properties wizard allows you to create multiple properties
wizard for the same class in a single form.
A delegated rule is visible to a specific user or group of users with a
specific access group. Rule delegation facilitates rule management
outside of the development environment. A delegated rule can be a
delegated rule
favorite that is accessible from Designer Studio or the Manager and
Case Manager portals, or it can be a paragraph, decision table, or data
type accessible from the Case Manager portal.
A dependency is relationship where one object requires (or relies on)
dependency
the functionality that another object provides.
An dependency network is an internal data structure that supports
forward chaining or automatic recalculation of certain property values
based on changes to other property values. Required relationships
dependency network among properties can be established using a Declare Expression,
Constraints or Declare Index rule. Such rules are sometimes known as
declarations. A dependency is depicted in a declarative network
display diagram as a dotted arrow between two objects.
dependent assignment See case type dependency.
A descendent class is derived from another class. Descendent classes
descendent class can use rules and/or data objects defined for a parent class by means
of either directed inheritance or pattern inheritance.
Designer Studio is a web-based integrated development environment
Designer Studio that you use to build applications. Designer Studio provides access to
tools, wizards, reports, and other features.
A role-based authoring environment focused on advanced functionality
Dev Studio such as system settings, complex rules or security. Targeted for
experienced app developers, account and security admins.
In Customer Service, a diagnostic process is a service process which
leads customer service representatives through a series of questions in
diagnostic process order to provide a suggested result. For example, diagnostic processes
may be used to suggest the best service plan or troubleshoot a billing
issue.
In Customer Service, a dialog script dynamically displays scripts
dialog script (dialog) to users which are personalized for the customer within the
context of the interaction. Displayed in the Interaction Thumbnail area.
In Decision Management, dimensions are a hierarchical context for the
facts and responses associated with an interaction. Currently, the
dimensions
following dimensions are implemented; customer, application,
proposition, channel, behavior, response context and time.
Direct Capture of Objectives (DCO) refers to a set of application
Direct Capture of development tools and best practices that are used to define business
Objectives (DCO) and project objectives, processes, specifications, and requirements,
and link them to implementations
Directed inheritance is the method by which a class inherits
characteristics directly from a specified parent class, regardless of any
defined pattern inheritance. For example, the PegaSample-
directed inheritance
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
 Work-Object-.
The Direct Feedback feature, intended for use with the Project
Management Framework (PMF), allows users, testers, and developers
Direct Feedback feature working with your system to record and submit ideas, suggestions,
bugs, issues, and proposed solutions through a real-time connection to
the framework.
The use of directives is deprecated. For improved performance and
directive
debugging, use JSP tags in new development.
The Discovery Map is a graphical design tool used to provide a high-
level presentation of the steps in an application's starting business
processes, including subprocesses and alternate paths, and the
sequence of the specifications and requirements for each case type.
Discovery Map
The Discovery Map captures the primary path in the flow and the
sequence of steps that users will most likely perform to resolve a piece
of work in the top row. In Pega 7.1 and later versions, process
discovery occurs in the application itself.
A dispute related to a credit card or debit card account is a situation in
dispute which a customer questions the validity of a transaction that was
registered to the account.
A division is the middle level of the three-level organization hierarchy
and is available for use in every application. Divisions are below the
division 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.
The Document Application tool captures information and images from
any application in your stack and generates customizable application,
Document Application
application profile, and specification documents that you can share with
tool
stakeholders. This tool was previously called the Application Document
wizard.
The Documentation wizard supports the generation of Microsoft Word
Document wizard documents that describe the application, including specifications,
(Application Document requirements and actors. Because this documentation can be
wizard) generated directly from rules at any time, it can be up-to-date and with
the actual implementation content.
Dot notation is syntax in an expression that precedes the name of a
property with a period. You can use dot notation to reference single-
dot notation value properties and complex properties. For example, .CurrentSalary
and .Customer.FirstName are both valid user inputs in a field that
supports expressions.
In Process Modeler, draft mode is a flow-editor setting that enables
users to create or update flows that reference elements, such as rules
and flow actions, that are not yet defined or complete. When you run a
draft mode
flow in draft mode, links are displayed on forms with missing elements.
You can use these links to create the missing elements without exiting
the flow.
A duplicate case is an open instance of your case type that matches a
set of conditions. In business processes, identifying and eliminating
duplicate case
duplicate cases as early as possible helps avoid the work of
researching, updating, and resolving both cases.
A dynamic layout is a DIV-based layout that allows for the flexible
display of content. Dynamic layouts separate content and presentation.
You add content, such as properties, controls, dynamic containers, and
Dynamic Layout
other sections, to a dynamic layout within a section. You set the
presentation of that content by using dynamic layout formats specified
in the skin.
Dynamic Select A control that displays a drop-down list of text value choices for an
 input field - returned from an activity, a list view, report definition, or
clipboard page - instead of a static list of values.
The Dynamic Select control is an optional feature you can add to user
forms (through HTML rules, harnesses, or sections) and other HTML
Dynamic Select control forms to speed user input. The Dynamic Select control is deprecated,
but supported. Use the Dropdown control (pxDropdown) instead. As a
best practice, upgrade Dynamic Select controls to Dropdown controls.
Dynamic System Settings data instances are used to alter the
performance of the Pega Platform. Dynamic System Settings that have
Pega-Engine as the Owning RuleSet and key names that start with
Dynamic System
prconfig are known as prconfig settings. Creating a Dynamic System
Settings
Setting data instance and setting the value of the data instance to a
prconfig setting value is recommended over directly updating prconfig
settings for easier maintenance.
An edit validate rule defines a Java routine to test the validity of an
edit validate
input value and/or format data; listed in the Data Model rule category.
An eForm file contains a PDF file that is used as a template for
generating new PDF documents. The corresponding eForm map
eForm file 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.
The Elaboration phase of the Pega BPM implementation methodology
is when a business analyst works with the customer to analyze the
problem domain, establish a sound architectural foundation, develop
the project plan and eliminate the highest risk elements of the project.
These activities ensure that the architecture, requirements and plans
are stable enough, and the risks are sufficiently mitigated, to
Elaboration phase predictably determine the cost and schedule for the completion of the
development. The output from this phase includes a use-case model
(80% complete), software architectural description, executable
prototype, a development plan and a revised risk list and business
case. At the end of this phase, the hard engineering is considered
complete and the decision is made whether or not to commit to the
Construction and Transition phases.
An abstract class used as the parent for all embedded classes that, by
design, are never to be used as top-level structures. By definition, a
Embed- class derived from the Embed- base class is used only for embedded
pages, rather than top-level, clipboard pages. Accordingly, no saved
instances of concrete Embed- classes ever exist.
The Embed- base class is a parent to other classes that, by design, are
never to be used as top-level structures. No saved instances of
concrete Embed- classes ever exist. A class derived from the Embed-
embed- base class base class is used only for embedded clipboard pages. Developers
can create rules that apply to embedded instances and execute on 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.
An embedded page is a clipboard page that is the child of another
embedded page
page.
An enterprise application is a full-scale application that is generated by
enterprise application the New Application wizard. It provides all the capabilities in the Pega
Platform and can be developed in Designer Studio or express mode.
The Enterprise Class Structure, or ECS, is an out-of-box class
Enterprise Class structure that provides a foundation for reuse. There are four layers
Structure (ECS) (Enterprise or Organizational, Divisional, Implementation) and each
layer is designed to hold rules that are specialized for that layer.
enterprise standard An enterprise standard requirement documents industry or enterprise
requirement standards that your application must include.
 An entity is a piece of extractable text or data that occurs within an
entity
utterance.
In a flow, entry points control to which places in the flow users can
move. Assignments and subprocesses are commonly marked as entry
entry point
points, because these are places in a business process that require
human input.
An environment is another system or instance that PMF integrates with
environment or that PMF is managing work for. This could be a Pega 7 instance or a
3rd party application.
An epic is a large user story that can be broken down into multiple
smaller stories. Epics typically cannot be completed in a single sprint.
Epics provide you with an additional level of managing the User Story
Epic hierarchy. You can manage Epics across multiple teams. Product
Managers can easily track the progress of stories being developed as
part of an epic. In PMF, Epics can be associated with products, goals
and releases.
An escalation is an action that is taken by your application to facilitate
faster resolution times, based on a specified service-level agreement.
escalation For example, you can send correspondence to interested parties when
a case is 5 days overdue. Use the Service-level agreement form to
configure escalation behavior in your application.
An exception path is the least-likely path a process may take to
exception path
complete a unit of work. Also called an alternate scenario.
The Explorers are part of the navigation menu that allows access to
Explorers parts of the application. Explorers include the Case types explorer and
Data explorer.
The Export gadget is a form in the Application Packaging wizard that
identifies the rules to be exported. Rules to be exported are copied to a
Export gadget specific ruleset and version. You can copy all rules in a ruleset, or all
rules and data instances defined in a specific product rule or patch
rule.
An exposed property is a Single Value property that is stored as a
column in a database table, in addition to the Storage Stream BLOB, to
exposed property
enhance record selection operations in reporting. Exposed properties
are also referred to as optimized properties.
An express application is a small-scale application that is generated by
the New Application wizard. An express application has access to a
express application
subset of the capabilities in the Pega Platform. Express applications
are ideal for new users or for quickly testing functionality.
In Customer Service, Express history is a link created in the composite
Express History to track important information that is shared with a customer regardless
of whether a service process has been executed.
An expression is a single line of Pega 7 Platform syntax that allows
computation of a value using arithmetic operators, logical operators,
expression Java operators, standard functions, and properties. On many forms,
you can start the Expression Builder to provide prompting and
guidance while entering an expression.
The Expression Builder is an interface used to construct sound Java
expressions by guiding the user's selection, locating functions,
Expression Builder
completing parameters to functions in a natural language format and
validating the format of an expression.
Express mode is a way for you to experience the Pega Express
environment on the premises. When you log in to an express
express mode
application, express mode is the default mode. For enterprise
applications, you can switch to express mode from Designer Studio.
extension point An extension point is 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.
An external assignment is an assignment sent by email to someone
who does not sign on to the system directly. An external assignment is
external assignment
an instance of the Assign-External class. The Directed Web Access
facility supports the use of external assignments.
An external class is a concrete class (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.
external class You can create an external class and associated properties by using
the Connector and Metadata accelerator or the New External Database
Table Class Mapping button on the Data Model Classes and Properties
landing page.
An external data entity is a class that is a data type of the current
external data entity application and appears in the Data Explorer. Records of the data type
come from, or will come from, an external data source.
An external data source is a data source of type connector, a lookup
external data source with an externally mapped Applies to class, or a report definition with
an externally mapped Applies to class.
An external operator is an operator who can process external
external operator assignments. The Directed Web Access facility supports sending
external assignments to such operators.
The extract marker file records the date and time of the initial startup of
a node that triggers initialization processes, such as function library
extract marker file extraction and compilation. This text file is named
PegaRULES_Extract_Marker.txt and is created during installation in
the temporary files directory.
The family name of a rule is a text string consisting of all the key parts
concatenated with exclamation points, excluding the Applies To or
class name portion. For example;Two activities named Work-MyCo-
Family name Mortgage.Reopen and Work-MyCo-.Reopen both have REOPEN as
the family name. Or, when a binary file rule has three key parts defined
as webwb, pegalogo, and gif, the family name is
WEBWBPEGALOGOGIF.
A favorite is a link to a rule or data instance. Use a favorite to quickly
find items while working in Designer Studio or the Case Manager
portal. You can create favorites that are visible to your operator
favorite exclusively, another operator, or all operators within a specified access
group. Favorites that are accessible by other users are delegated
rules. You can access your favorites from the operator menu in the
header of Designer Studio or the Favorite Explorer.
A feature is a capability that you implement in your application. By
defining features that are linked to rules and work items, you can
Feature
improve the traceability of capabilities to their respective
implementations.
Federated Case Management (FCM) uses the Pega Web Mashup
connectivity to link Pega 7 Platform applications in a federation. Users
in a federation work in their local application portal, which can display
Federated Case
cases and assignments from other applications in the federation. Each
Management (FCM)
local application processes and maintains its own cases and data, and
publishes data to a centralized database, the Federated Case
Management Repository (FCMR).
A Federated Case Management Repository (FCMR) serves as a
Federated Case
centralized repository for cases and work performed by users in a
Management
federation. The FCMR consolidates work items and makes them
Repository
available to all users in the federation.
 Feedback is a suggestion, idea or quality issues reported by an end
user or developer of a product. Feedback items can be voted on by
feedback
stakeholders. Product owners can review and triage their product's
feedback items to determine which items to implement.
A Field Value Inspector is a tool that supports testing, evaluation and
fine-tuning of localized applications, by allowing updates to field value
rules through a pop-up window that contains translations while viewing
the application. Displays visual indicators that link text elements on a
field value inspector
form to the associated field value rules and identifies missing field
value rules, for text labels, error messages, Tool Tips and so on. In
PEGA 7.1 and later versions, the Field Value Inspector is part of the UI
Inspector.
A Final rule that has the Available field set to Final and displays a
green stopped arrow on a rule form meaning that no one can create a
second rule with the same visible key in any ruleset other than the
final rule ruleset to which the first rule belongs; but this rule can be overridden
through a higher version in the same ruleset. Most standard rules that
are necessary to ensure the integrity and security of the system are set
to final.
A flow models a business process in your application by using
flow graphical shapes and connectors to define a sequence of events. You
can edit a flow in Case Designer or Process Modeler.
A flow action displays a task or a choice, such as Approve or Reject, to
users when they run flows. The two types of flow actions are connector
flow action
flow actions and local flow actions. You can edit flow actions in the
Process Modeler or Case Designer.
Flow data is Information needed by an application to determine what
flow data
action to perform and who should perform it.
Flow drafting is the process of iteratively testing and refining a flow rule
flow drafting before creating the UI, data model and decision rules. Flow drafting is
an integral part of the DCO process.
Flow errors are error conditions that prevent a flow execution from
continuing. An example of a flow error is if the flow references a rule
flow error that is not found at run time. Click Designer Studio > Processes and
Rules > Processes > Flow Errors to view the flow errors in your current
application.
A flow marker rule is 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
flow marker
and use these flow markers. Flow marker rules belong to a RuleSet
and version, but they are not included in the Application Explorer
display.
The fundamental rule that represents all or part of a business process,
governing how cases are created, processed, and ultimately resolved.
flow (rule)
A flow rule consists of a network of shapes and connectors or lines,
each with associated parameters and values.
A flow shape represents a task that is accomplished as part of a
business process. Shapes are differentiated by color, symbol, and
flow shape
name. You add standard, advanced, and smart shapes to a flow by
using Process Modeler.
A folder is a case in a concrete class that inherits from the Work-
Folder- class. A folder object holds a collection of one or more cases,
folder
including covers and other folders, to provide access for analysis and
reporting.
A fork is an optional configuration for a decision shape, in which
fork
decision logic is configured using when rules associated with the
 connectors emanating from the decision shape, rather than a decision
table, decision tree, or map value rule configured on the decision
shape itself. Pega selects the appropriate outcome for the decision by
evaluating the when rule on each connector, in order of likelihood from
high to low, until one returns a true result.
A form displays information or collects input from users as they create,
form update, and resolve cases in your application. Use Case Designer to
define the visual presentation of a form.
Forward chaining allows for the automatic propagation of changes in
one property value to changes in other property values or to indexes.
forward chaining This process only operates when the source properties are not marked
as invalid. If a property has an associated message, forward chaining
halts.
A fragment contains 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
fragment
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.
A framework application is an application that you can extend and
framework application modify to create implementation applications for a specific
organization, division, or organization unit.
A framework class defines a common work-processing foundation that
you extend and modify as implementation applications for an
framework class
organization, division, or organization unit. Framework classes belong
to the framework layer of an application.
A framework layer contains reusable application elements and
framework layer provides an application that you can use as the basis for many
production applications
A fraudulent application (sometimes called FRAP) is a specific type of
fraud where someone applies for credit with someone else's social
fraudulent application security number, and uses the credit but never pays the bills. As a
result, the credit report for the victim of a fraudulent application can be
severely impacted.
An F-score is a measurement of the accuracy of a natural language
F-score processing model. The F-score is determined by leveraging a test set
of training data to validate and evaluate the models for accuracy.
A Fully Qualified Name (FQN) is an unambiguous reference that
includes the name of the item being referenced and any contextual
information necessary to differentiate the item from another item with
Fully Qualified Name
the same name. Fully qualified names are most commonly used with
(FQN)
Pega properties to identify the property, the embedded page that
contains it, such as .PurchaseRequest.GrandTotal, though they can be
used to identify any rule.
A function defines a Java function and makes the function callable from
function activities and expressions. A function is an instance of the Rule-Utility-
Function rule type.
A function alias is a user-friendly label for a SQL or Java function rule,
function alias designed to help non-developers when creating or updating a decision
table or when rule, or when creating a report.
A functional requirement describes a capability that the application
functional requirement
must have to meet your business needs.
A funnel chart displays the progressive reduction of data as it passes
Funnel chart from one phase to another. You can specify the chart type and subtype
for a report definition report by using the Chart Editor.
gadget A gadget is a rule type such as the worklist display. A gadget provides
 information or tools that assist a system architect or system
administrator in building and maintaining applications and determines
the appearance, labeling and location of sections on the home page
(portal) and which parts of the portal are visible to different groups of
users.
A gauge chart displays a single value as a meter reading. If the gauge
chart includes thresholds, a manager can quickly review the chart to
Gauge chart 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.
In Decisioning, a geofence is a rule type used to define the latitude and
longitude of a location and a radius surrounding the location, known as
geofence
the fence. Geofence rules are in the Marketing category that is enabled
in a Next-Best-Action Marketing application.
Geolocation tracking captures the longitude and latitude coordinates of
caseworkers as they process a case. When you enable this feature for
geolocation a case type, you can view the location of the caseworker in a Google
Map. You must include the UI-Kit-7 ruleset in your ruleset stack to use
geolocation tracking in your application
A gesture is a movement or touch-based user interaction with an
gesture
application on a mobile device
A global resource setting is 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
Global resource setting reference any property of the appropriate type on a data page. The use
of global resources settings for references to external systems, rather
than fixed text values in rule forms, allows greater flexibility for
changing values such as port numbers, addresses, and URLs.
A goal is an interval of time that is defined in a service-level
goal agreement. It is the suggested resolution time for an item, such as a
case or stage.
Good faith is a generalized term to indicate that the issuer and
merchant desire to deal fairly with each other in the interest of the
cardholder or customer. Good faith can be initiated by either an issuer
good faith
or an acquirer. The good faith process is not mandated or managed by
any association rules. Instead each issuer or acquirer sets its own
rules for good faith.
Governance is the processes that help to guide projects to a
governance
successful completion.
Grid controls allow you to display the relationships between large
quantities of data and provide a convenient interface for editing or
grid controls 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.
A grid layout allows you to view (and possibly edit) values of a Page
List or 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
grid layout
property reference, the grid automatically refreshes 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.
Grooming/Elaboration The Grooming/Elaboration process is a sequence of ancillary activities
process used to prepare for, run, and close a Grooming/Elaboration session.
Grooming/Elaboration A Grooming/Elaboration session is a tightly moderated meeting (never
session more than 4 hours) with a fixed and clearly defined set of resources
 whose sole purpose is the gathering and capturing of detail related to a
fixed set of specifications.
Guardrails are guidelines that help developers achieve project
guardrail success, optimal performance, reuse, and maintainability for
applications.
guest A guest is an unauthenticated user. See authentication.
A guided tour is a sequence of tour stops that provides information,
tips, and instructions about the key features in your application. Use
Guided tour
the Guided Tour form to define the content that is displayed in each
tour stop.
A handle is a permanent, unique identifier for a class that includes
certain key parts, and the creation date and time of a single instance
handle 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.
A harness defines a run-time form and is an instance of the Rule-
HTML-Harness rule type. Each harness defines the appearance and
harness
behavior of a form. Harnesses are defined on the Harness rule form
that at run time produces a user form, rule form, or composite portal
A headless application uses flows and other elements, but either does
not have a user interface, or presents forms, assignments, and other
Headless application information to users through an external mechanism. An application
that delivers straight-through processing can be characterized as
headless.
A heat map is a graphical representation of data where the values
taken by a variable in a two-dimensional map are represented by
heat map 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
Historical processing is a feature that enables an application (for the
current requestor) to operate based on how rules were defined on a
Historical processing 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.
The abstract parent class for tracking changes to rules. See History-
History-
classes.
The History- base class is an abstract class that is parent to numerous
other classes that define cumulative tracking data about the objects in
History- base class 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.
History- classes are subclasses created automatically as a byproduct
History- classes
of the creation of other classes, to track changes to rules.
The history type of a history instance for a case identifies the event that
History type corresponds to the instance. The history type is recorded as a single
letter value in the pyHistoryType property.
A hotfix catalog is a repository of information about all Pegasystems
Inc. hotfixes. The catalog describes the changes in each hotfix and is
Hotfix catalog used for dependence checking. Either upload a catalog .zip file, or
check online for the latest catalog from Pegasystems Global Customer
Support.
HTML5 is the 5th iteration of the HTML standard set by the World Wide
HTML 5 Web Consortium (W3C), which includes standards to enforce cross-
browser compatibility.
An HTML fragment is a rule that defines reusable HTML not associated
HTML fragment
with a specific class, often used for frequently used HTML text,
 JavaScript or CSS text. HTML fragment rules are listed in the
Technical rule category.
An application developed for a specific business audience or need, and
Implementation
not intended to be reused for other audiences or needs. See also
application
framework application.
An implementation class defines the extension, reuse, and
specialization of assets in a framework class layer to meet the
implementation class business requirements of an organization, division, or organization unit.
Implementation classes belong to the implementation layer of an
application.
The implementation layer contains application elements that are
specialized for a specific business audience or purpose. The contents
implementation layer of the implementation layer extend the elements of the framework to
create a composite application that targets a specific organization or
division.
An implementation methodology is a software development
methodology that focuses on project management, return on
implementation
investment, conformance to best practices and compliance
methodology
requirements, communication with stakeholders, and the creation of
physical artifacts that help to ensure project success.
The Inception phase of the Pega BPM implementation methodology is
where you identify the business case and success factors (expected
revenue, market recognition, etc.). To complement the business case,
a basic specification model, project plan, initial risk assessment and
Inception phase
project description (the core project requirements, constraints and key
features) are generated. After these are completed, the project is
checked against the following criteria: Stakeholder concurrence on
scope definition and cost/schedule estimates.
An index is a value that identifies one element (or member) of an
aggregate data structure. These indexes are sometimes called
index 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.
The Index- base class is 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
Index- base class
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.
An indirect page is a page that the system finds by searching the
clipboard at run time. The page reference to an indirect page starts
indirect page with the keyword prompt followed by the page name. This type of page
is deprecated but still supported for rules that used this feature prior to
Pega 7.1.
Inheritance is the mechanism by which a child class can use all of the
inheritance rules defined for a parent class. Pega supports two types of
inheritance:;pattern inheritance and directed inheritance.
An instance is a durable, potentially permanent, saved representation
of a concrete class that is stored in the database. An instance
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.
To create a new case, whether automatically through operation of a
instantiate
case type rule or manually.
An instruction initiates an action for a row on an activity form. The
instruction
instruction keywords are Call, Collect, Branch, Queue, Rule, and Java.
 Integration Designer is a tool that provides a single location for viewing
all the business objects, data views, object dependencies, and external
Integration Designer
systems in an application. The Integration Designer clearly shows how
all of the application components are connected.
Integration services are facilities that support interfaces between the
Pega 7 Platform and external systems. Integration services include
Integration services
both connector and service capabilities. Integration services are
supported by the Pega-IntSvcs ruleset.
Integration Services The category of rules used to support service interfaces between Pega
category and external systems.
An integrator shape is 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
integrator shape
an external database to obtain current prices or current inventory
levels. Flows edited with the Process Modeler use the integrator
shape. The corresponding Activity Type is Connect.
Intelligent routing is 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
intelligent routing
thoughtfully distributes work to her team, intelligent routing in your
application can significantly affect the productivity and throughput of a
work group.
The practice of incorporating rule names, shape names, and UI
elements such as labels and instructions that clearly communicate the
intent of elements and actions to developers and users. With intent-
intent-driven processing
driven processing, a Decision shape in a flow might be named
“Require Additional Authorization”, rather than the more general
“AuthCheck”.
Contact, either in real-time or offline, between the individual or
organization responsible for processing a case and one or more parties
interaction
to facilitate case processing. See Live Interaction and Non-live
Interaction.
In Customer Service, the Interaction Driver is a UI component that
dynamically presents the user with a variety of service process options,
based on rules that are constantly evaluating customer context. It
Interaction Driver
consists of Suggested Tasks, a To Do list (queued Service Processes
for the user) and different categories of Service Processes that users
can choose from (such as Account, General, Contact).
In Customer Service, an Interaction Goal reflects an organization's
business rules and can be based on prior customer interactions,
Interaction Goal customer profile or other information. Customer Service may use this
goal to present different dialog scripts to the user or may use it to
present suggested processes.
In Decision Management, the Interaction Result is the reaction of a
customer to a proposition. Recorded in the IS database tables and
Interaction Result
propagated to Adaptive Decision Manager (ADM) and Visual Business
Director (VBD).
In Decision Management, Interaction Sevices (IS) provide the
interaction management services that persists the interaction result. An
interaction service also provides routing to the Adaptive Decision
Interaction Services (IS)
Manager (ADM) and Visual Business Director (VBD) in the service
layer, including updating the state of adaptive models, and saving
interaction results for monitoring and reporting purposes.
In Customer Service, the Interaction Thumbnail is an area of the user
interface that provides pertinent information for the current interaction
Interaction Thumbnail
(such as Customer Name, Duration Timer, Interaction Goal, and Call
Back Number.)
 In Customer Service, an Interaction Timer is a gadget on each
Interaction that indicates how the interaction is proceeding in relation to
Interaction Timer a defined service level agreement (SLA). The color of the timer icon
changes as the SLA goals and deadlines are reached (for example,
green to yellow to red.) Also known as the Duration Timer.
An interactive chart provides options, such as a slider control, for
interactive chart increasing and decreasing the level of detail that is displayed.
Summary view reports can include interactive charts.
Interaction Voice Reponse (IVR) equipment (or software) is used to
provide automated service to customers over the telephone.
Interactive Voice
Customers often interact with an IVR before being transferred to a
Response (IVR)
service representative in a call or contact center. Also known as Voice
Response Unit (VRU).
An interested party is 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
interested party
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.
An interest page is the primary page that a flow runs against. An
interest page interest page might be an embedded page of the case, or it might be
the case itself.
An internal class is a concrete class (instance of the Rule-Obj-Class
rule type) for which instances are stored in the PegaRULES database,
internal class rather than in an external database. The properties
@baseclass.pzInsKey and @baseclass.pxObjClass are defined for
every internal class.
The internal key of an instance is the text value of a reserved property
@baseclass.pzInsKey. This property is defined in the ultimate base
class and is available in every class. This value is also known as the
internal key handle. For rule instances, the date and time that the rule was first
saved becomes a portion of the internal key. As a result, the pzInsKey
property is undefined until the new rule instance is saved and
committed.
The Internet Application Composer is a tool that enables a Pega
Internet Application
application to be accessed from the pages of a Web application
Composer (IAC)
located on your intranet, extranet, or internet site.
In Decision Management, an interval is a mechanism typically used to
interval group the values of numeric predictors. Each interval provides a useful
building block for understanding behavior.
An issuer is a financial institution that issues the credit or debit card to
issuer
the cardholder.
Iteration is the process of repeating the same set of actions on any
iteration given list. The Split For Each shape in a flow and the ForEach JSP tag
in a stream rule both support iteration.
A Java Archive (JAR) is a file format that aggregates many files into
Java Archive (JAR)
one ZIP compressed-file.
A Java identifier is an identifier that must start with a letter, and contain
only letters, numbers, and hyphens. Java identifiers in Pega Platform
Java Identifier
are similar to those defined in the Java language specifications, except
that a hyphen (-) displays in place of an underscore character (_).
Java Object mode properties contain references to Java objects. The
Java Object property contains a reference to an instance of a Java
java Object mode 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 properties support the Java pages feature, which
Java Property mode enables applications to interact with external Java objects as though
they were pages and properties on the clipboard.
Job Scheduler A background process that schedules recurring tasks.
Journey Centric A methodology that focuses project efforts and application delivery on
Delivery customer goals.
A keyed data page is a list-structure data page. The keyed data page
references a key that returns one or multiple instances matching that
key. When the first reference of a keyed data page occurs, all the data
keyed data page stores on the data page according to the data source configuration.
When a data page receives a request later, the data is already on the
data page, and the system locates only the current instance by using
the provided key from the request.
A key part is one to three fields that you specify on the Create form for
every rule instance and data instance. Which properties form the key
key part part for objects of a specific class, and in what order, are determined in
the class rule. If an object has only one key part, that value is often
called the name of the object.
A Key Performance indicator (KPI) identifies, monitors and measures
key performance
the organizational performance of a business operation that is
indicator (KPI)
considered important by management.
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
keyring file
supports Java Cryptography Extensions (JCE), you can identify an
encryption algorithm in the crypto elements of the prconfig.xml file to
create the keyring file.
A keystore is a file that contains security certificates. To support Web
Services Security and outbound email security, you can attach a
keystore
keystore file to a data instance of the class Data-Admin-Security-
Keystore.
In Customer Service, Knowledge Topics allow agents to create,
Knowledge Topics
maintain and leverage relevant content during the processing of work.
A landing page is a presentation of one or more tabs or tools. Most
landing pages are reached from the Designer Studio menu. Each tab
landing page provides information or tools that assist a business analyst, system
architect, or system administrator in designing, building, and
maintaining applications.
A language pack is a collection of language-specific rulesets that
language pack support localization of applications. A language pack provides field
value rules that localize buttons, prompts, and labels.
A layout is a portion of a section rule, used to organize the labels,
layout fields, and other controls that comprise the user interface. Pega
provides several types of layouts that dictate how controls are arrayed.
A layout group displays a set of content and allows you to present
information responsively that is normally shown within one control type.
layout group
A layout group can contain any number of dynamic layouts, column
layouts, repeating dynamic layouts, or other layout groups.
A Lead System Architect (LSA) is an application developer who
Lead System Architect
provides technical leadership in design and project management tasks
(LSA)
to an application development project.
A legacy agent is an agent where the Queue Mode setting on the
Schedule tab is set to Legacy. Legacy agents do not use queues, and
legacy agent
instead process each item to completion in a single pass. Agents
created in releases before PRPC Version 5.4 appear as legacy agents
 in later releases, until they are upgraded to Standard.
A level-1 specification is a high-level specification created during the
Inception phase. Level-1 specifications contain sufficient information to
Level-1 specification facilitate project sizing, but may be missing key implementation details.
These application specification rules are later iterated upon in DCO
sessions and become level-2 specifications.
A level-2 specifricatiaon is more-detailed specification (when compared
to a level-1 specification) that is the result of a DCO session. In DOC
sessions, the level-1 specifications are iterated upon to identify and
address gaps in the content of the specification. The result of this
Level-2 specification
iteration is a more-detailed level-2 specification. Llevel-2 specifications
contain enough information for business and system architects to
create the process and/or UI described by the specification, and for QA
to create test scripts to test the implementation.
library (rule) A library (rule) is a container for a set of related function rules.
License Compliance is a tracking and reporting system. This feature
can provide evidence that operations of the system comply with
License Compliance provisions of the Pegasystems contract and software license. An
automatic background thread known as the License Compliance
daemon supports data gathering for this functionality.
A lightweight list is 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
lightweight list
can specify that results display in a lightweight list for Obj-Browse
methods and lookup lists. Report definitions automatically use
lightweight lists.
A likelihood is a value between 1 and 100, interpreted as 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
likelihood completing an assignment linked to that flow action are expected to
choose the Accept flow action two out of three times. When editing a
flow in Process Modeler, click the percent sign icon to display
likelihood values.
The Link- base class is an abstract class that is an ancestor class to
Link- base class
other classes and identifies paired object instances in your system.
A linked property is 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
linked property 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.
A listener is a background thread that monitors a TCP/IP port, mailbox,
listener
messaging facility or directory for arriving messages or files.
A list view rule defines a list view report that displays unsummarized or
detailed data. The list view rule is deprecated. Re-create the custom
list view rule
list view reports that you need as report definitions. The last version of
Internet Explorer that list view rules support is Internet Explorer 11.
A live interaction occurs over a synchronous channel, such as a
live interaction
telephone call, chat session, or in-person visit.
Load-balancing is a technique or facility that attempts to provide an
load-balancing even backlog of demand across multiple processors or production
facilities.
Local data storage is a feature that lets you store data records for a
local data storage data type without having to manually create or maintain database
tables. In the Data Designer, you can access local data storage on the
 Sources tab for the data type. Use the Local Data Storage wizard to
create a local data source.
A locale is one of the standard codes in the format aa_BB_CC, where
aa represents the language and _BB or _BB_CC represents a country
locale variant suffix. Every user session has a locale setting that can affect
the language presented by the Pega 7 Platform user interface when
displaying or entering dates, times, and monetary values.
A local flow action leaves the current assignment open and does not
advance the flow. In other words, you can update the assignment but
local flow action not complete it. If a service-level agreement is associated with the
assignment, the goal or deadline intervals continue to run. Local flow
actions are configured on assignment shapes.
The Localization wizard is a tool that assists developers and translators
with the localization of an application to multiple languages. It provides
the ability to extend and build on Pegasystems-provided language
Localization wizard
packs for French, German, Japanese, Spanish, Traditional Chinese
and Simplified Chinese. It can also import translations into the
language-specific ruleset.
Local variables are text strings stored in a Java StringBuffer object
rather than in a page structure. They require less memory and can be
local variable
accessed with less computer overhead than parameters. Activities can
access local variables.
A locatable page reduces the need for the page to be explicitly named
in the rule. At run time, the system uses backward chaining and an
locatable page activity with type Locate to find and add the correct page to the
clipboard. Locatable pages can be used with Constraints rules and
Declare Expression.
A lock secures an object or a ruleset version to prevent them from
lock being changed. You can lock ruleset versions, an instance of a
concrete class, and the Rule-Application rule type.
Lock and Rolls allows you to review and lock a ruleset version,
advance it to a new, higher version and optionally update the
Lock and Roll
application with a new ruleset version or create a new version of the
application.
The act of rendering a rule or case not editable to prevent unauthorized
changes. A ruleset can be locked to forbid users from editing the rules
locking that it contains. A case is locked upon opening to disallow multiple
users from updating the case at the same time, which prevents one
user’s changes from being overwritten by other users.
The Log- base class is 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
Log- base class
classes) their instances through the Application Explorer. For concrete
classes derived from the Log- base class, the property
@baseclass.pxCreateDateTime is usually the final (or only) key part.
Logging is the process of keeping records of server activity, called logs
or log files, for the use of system administrators. Pega automatically
logging
maintains several log files to track server activity, and application
warnings and errors.
The lookup list cache (LLC) is 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
lookup list cache
automatically. Although rarely necessary, you can cause your system
to clear the LLC at startup by deleting the extract marker file, or at any
time by using the System Management Application.
major version A major version is the first two digits of a ruleset version number. For
 ruleset version 01-02-03, the major version would be 01.
A map is 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 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.
A map value is a rule that converts one or two input values, such as
latitude and longitude numbers, into a calculated result value, such as
map value
a city name. The rule uses ranges for the input values and a matrix to
look up the result.
MasterCom is Mastercard s online disputes system, for issuers to file
chargebacks on behalf of their cardholders, and for acquirers to
MasterCom
respond on behalf of their merchant customers. MasterCom enables
member banks to provide quick resolution to cardholder disputes.
In Decision Management, a measurement is numeric information
associated with interactions, which can be used for Key Performance
measurement Indicators (KPIs). In the context of the simulation process there are two
types of measurements: strategy-driven and customer data-driven.
Decision Management supports up to 20 measurements.
A Pega 7 Platform method is distinct from a Java method which is an
operation that can be performed by one step of an activity (Rule-Obj-
method
Activity rule type), or by a Parse Structured rule (Rule-Parse-Structured
rule type).
A methodology is a set or system of methods, principles, and rules for
methodology
accomplishing a goal.
Minimum Lovable MLP is the minimum functionality you need to achieve real business
Product (MLP) benefit.
A minor version is the middle two digits of a ruleset version number.
minor version
For ruleset version 01-02-03, the minor version would be 02.
A mixin is a reusable style pattern defined in the skin. Mixins can
mixin
define a combination of reusable text, border, or background styles.
Mobile compliance indcates that harnesses, controls and behaviors
support the usage of an application on a mobile device. A mobile-
mobile compliance
compliant application does not require any user interface
enhancements to be enabled for mobile users.
Mobile preview is a set of interactive icons that allows you to emulate
the appearance of your application on different devices and
orientations. Use it to understand how your user interface displays on a
mobile preview
full screen, laptop browser, tablet, or phone. To enable mobile preview,
select Mobile preview from the operator menu in the Case Manager
and Case Worker portals.
A mobile ruleset is a special ruleset that is included automatically in the
ruleset stack for users connecting through a mobile device. The name
of a mobile ruleset matches a base ruleset with _mobile appended. For
mobile ruleset
instance, if an application includes a ruleset called MyRuleset, and if a
ruleset called MyRuleset_mobile exists, it will be automatically added
to the ruleset stack for any user who logs in on a mobile device.
Mobile specialization is the practice of creating a specialized version of
a rule that is resolved only for users on mobile devices. Rules may be
specialized using circumstancing, or by including them in a mobile
mobile specialization
ruleset. A Mobile specialization is typically used when a user interface
element such as a harness or section does not work well for mobile
users, but is optimal for desktop users. See also mobile compliance.
modal dialog A modal dialog box is a form to be completed or a statement to be
 acknowledged that opens in its own window. Users cannot continue
with other work until submitting the form or dismissing the modal dialog
box. A flow action provides the sections that contain the fields that the
user must complete.
In Decision Management, model attributes are the various descriptions
model attributes and settings created during model development that can be made
available to the decision making system at decision time.
Modeling is the process of generating a conceptual representation of
modeling an operational element of an application, such as a process, interface,
or data.
In Customer Service, multi-channel provides the ability to access and
use a process over multiple channels or modes of communication. For
example, a service process may be used regardless of whether the
multi-channel customer communicated with the organization using a phone call,
letter, email or a text chat request. Also, the same process may be
used by a service representative in a contact center, a specialist at a
retail location or the customer directly over a web self-service portal.
A process that groups two or more related collect information
assignments. All assignments within a multi-step form must be routed
Multi Step Form
to the same user. Navigation among assignments in a multi-step form
can be highly customized.
A Multi Step Process is a setting in the Case Designer that implements
a step as a multi-shape flow rule. When previewing a Multi Step
Multi Step Process
Process in the Process Outline, the system displays the flow diagram
for the process.
A Pega Multitenant system is a single system that is logically
partitioned into multiple heterogeneous business processing
environments, such that each environment operates as if on a
Multitenancy
dedicated, standalone system. In Pega’s Multitenancy, a tenant is a
flexible concept and can be a person, an organizational unit (e.g. a
division), or an entire company.
A Multitenant Administrator is an authorized user who can perform any
operation on the system. Users can perform product installs and
Multitenant
upgrades, apply patches, or perform any function that requires or
Administrator
involves changes to shared software, that can potentially impact all
tenants on the system.
A Multitenant system is a Pega Platform instance that has been
Multitenant system enabled during a Pega Platform installation to allow partitioning of the
system into one or more independent tenants.
My Rules is a list of rules delegated to a user personally or delegated
My Rules to everyone sharing an access group. Each delegated rule is identified
by a shortcut link (a favorite).
A named user is a classification of an Operator ID used in the License
named user Compliance facility. Typically, an Operator ID instance identifies a
named user if the License Type field on that tab is set to Name.
Natural Language Processing (NLP) is the process of deriving
Natural Language
understanding and determining an intent from piece of raw text or
Processing (NLP)
speech.
The navigation panel is the left panel of a portal. The navigation panel
for composite portals contains the Work Pool Selector, a broadcast
message, and the bars used by managers to switch from one
navigation panel
workspace to another workspace. For the Designer Studio, the
navigation panel contains the Explorer tools and is called the Explorer
area.
Net Promoter Score or A net promoter score is a measure of customer loyalty and whether
Net Promoter System they would be willing to recommend a company, product, or service to
(NPS) others. Also referred to as a Net Promoter System, because NPS
implies that a system is in place to track the score. In Decision
Management, practices have been designed to measure and improve
customer loyalty and build lasting relationships.
The New Application wizard quickly creates an application that
contains a class structure, business objectives, case types, and data
New Application wizard
types. You can create enterprise or express applications by using this
wizard.
In Decision Management, the Next Best Actions (NBA) is a strategy
Next Best Action (NBA) that allows applications to make the best decision in a multidimensional
context (retention, recruitment, risk, recommendation, etc.)
A node ID is a unique 32-character identifier for each node of the Pega
node ID
7 Platform system.
A non-functional requirement places constraints on how the system
non-functional
operates. Non-functional requirements specify criteria that may be
requirement
used to judge the operation of the system.
An non-live interaction that occurs over an asynchronous channel,
non-live interaction
such as email, fax, or mail.
A class of activity referenced that sends correspondence, such as an
email message, when a flow execution creates an assignment.
notify
Typically, the system addresses correspondence to a work party who
is identified in the case and reports progress to that party.
A notify activity sends an email as correspondence to one or more of
the work parties identified in the work item, and reports progress to that
notify activity
party. For example, when referenced in a flow, a notify activity sends
correspondence when an assignment is created.
An occasional user is a classification of usage for an Operator ID
instance for a time period, such as a calendar month, by the License
occasional user Compliance facility. This facility can classify an Operator ID as an
occasional user during one period, but count the operator in another
classification in other periods.
In Decision Management, the Omega XML Language (OXL) is the
Omega XML Language
XML file format generated by Predictive Analytics Director (PAD) when
(OXL)
exporting a predictive model.
An on-us item is a check or draft that is presented to the bank where
the check writer has the funds on deposit. The check can be cashed or
on-us
deposited into another account. The drawing account must have a
sufficient balance to pay the check.
An open assignment is one that has not yet been processed by a user.
open assignment
Open assignments are associated with a worklist or work queue.
The open authoring feature allows you to specify an editor for viewing
open authoring
or editing Java, HTML, or XML rule form source code.
An open instance is an instance copied from the database to a
open instance clipboard page. Usually, an open instance is locked so that only one
requestor can update it at a time.
An operator stores the user name, password, and other identifying
information for an application user. Each operator has a role, such as
caseworker or customer service representative, that determines which
operator actions the user can perform. Operators are implemented in your
application as instances of the the Data-Admin-Operator-ID class. To
view a list of the available operators, open the Designer Studio > Org &
Security > Organization > Operators landing page.
Defines an operator’s username, password, access group
operator ID
organizational setting, calendar and other values.
An operator menu provides access to your operator profile and a
operator menu
number of features, depending on where you access the menu and
 your application configuration. You can access the operator menu by
clicking your name in Designer Studio, Pega Express, and the Case
Manager, CaseWorker, WorkManager, and Manager portals.
The operator profile of a requestor session is a collection of facts and
values about the operator and the requestor. Many are derived from
the Operator ID instance and other data instances. To display your
operator profile
profile in the Designer Studio or from the Case Manager, CaseWorker,
WorkManager, or Manager portals, select Profile from the operator
menu. The system assembles this information as you log in.
Optical Character Recognition (OCR) is the process of turning image
Optical Character
based text (both printed and handwritten) into a format that can be
Recognition (OCR)
used within your application (text).
An optimized property is a Single Value property that is stored as a
column in a database table, in addition to the Storage Stream BLOB, to
optimized property
enhance record selection operations in reporting. Optimized properties
are also referred to as exposed properties.
An organization is the top level of the three-level organization hierarchy
and is available for use in all of your applications. The organizational
structure affects the management reports, statistics, and rules that are
Organization
available to users in that organization. One system can support
multiple organizations. An organization is an instance of the Data-
Admin-Organization class.
An organization (category) is a grouping of data classes in used to
organization (category) describe operators, organizational structure, work groups and
workbaskets.
The organization hierarchy governs the management reports, statistics,
and rules that are available to users in an organization, depending on
the division and unit in which the users reside. The organization
organization hierarchy
hierarchy also affects work item routing. The organization hierarchy
consists of three levels with organizations at the top level, divisions at
the middle level, and organization units at the lowest level.
The top level of the standard three-level organizational hierarchy
available in every Pega application. The organizational structure
Organization (record)
affects management reports, statistics and the rulesets visible to users
in that organization when they log in. See division and unit.
An organization ruleset is a ruleset that applies to all operators in an
organization. You specify this optional ruleset in the Default Ruleset
organization ruleset
field of the Details section of the Organization data instance (Data-
Admin-Organization class).
An organization unit is the lowest level of the three-level organization
organization unit hierarchy and is available for use in every application. An organization
unit is an instance of the Data-Admin-OrgUnit class.
In Decision Management, overfitting is a statistical term describing the
overfitting fact that a predictive model is more accurate in fitting known data, but
less accurate in predicting new data.
An overlay launches the local action in a panel overlaying the current
window. You can dismiss an overlay by clicking outside the overlay
overlay
area, or through an explicit Display > Close action configured in the
local action. Use an overlay to display simple forms or flows.
During rule resolution, override is the ability to mask other available
override rule instances with the same name but different rulesets or the same
ruleset but different version numbers.
An Owner is the party who directly caused a case to exist. Tan Owner
Owner can be a customer, an employee, a vendor representative or another
party.
ownership Ownership is a condition that defines the owner of a case. Cases are
 owned by organizational entities, not people. The initial owner is
usually the organizational unit of the user who entered the case. The
ownership can change during processing updating the owner and
organization property values. Business managers can access reports
that summarize cases by ownership.
A package is a file that contains code or a code library that you can
package import in a library rule or function rule. You can import external Java
packages or customer packages (also known as service packages).
Pages are data structures that hold name-value pairs. Pages are
stored in the system memory or in the database. Various types of
page 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.
Page Group An embedded unordered array of pages. See also property mode.
A Page Group property consists of an unordered set of pages, each
identified by a string subscript value. Use a Page Group property for
Page Group property large lists when you need to frequently look up specific pages by a
unique identifier and the order of the pages does not need to be
maintained.
A property mode that allows an embedded ordered array of pages. See
Page List
also property mode.
A Page List property consists of an ordered list of pages, each
Page List property identified by an integer index (starting with 1). The Page List property is
the most commonly used property mode for holding lists of data.
A page message is a text clipboard value that is generated by the
page message system and associated with a page. A typical page message conveys
error conditions, progress, and exceptions.
Pages are data structures that hold name-value pairs. Pages are
stored in the system memory or in the database. Various types of
Page (property mode) 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.
A panel set is a configuration of panels (areas) in a harness that
support a composite portal. Panel sets are deprecated; although,
panel set
existing panel sets will continue to function. As a best practice,
upgrade panel sets to screen layouts.
The parameter page is the location where parameter names and
parameter page
values are stored when an activity is called.
A Parent class is a class from which a descendent class inherits rules
and/or objects, through either directed inheritance or pattern
parent class inheritance. The term ""parent"" class is often applied in the context of
the relationship between two classes, as a class can be both a parent
to one class and a descendent of another class.
A parent flow contains a shape, such as the Subprocess shape, in the
parent flow flow diagram 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.
A parse XML rule contains parsing instructions to interpret XML. Used
with services and connectors to map data from an incoming XML
parse XML
document or text message into clipboard property values. The
message may be a request for a service or a reply from a connector.
party See work party.
The patch version is the final two digits in the ruleset version number.
patch version
For ruleset version 01-02-03, the patch version would be 03.
Pattern inheritance is an optional method where a class inherits
pattern inheritance 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.
The PDN, now Pega Community, is an online knowledge base of the
latest information and examples available to Pegasystems customers
PDN and partners. The PDN provides short articles, identified by a
knowledge base number. This content includes videos, forums, books
and other resources.
The PegaAccel- base class is the parent to classes used within
PegaAccel- base class Application Express and other wizards. Generally, you do not work with
these classes, except indirectly by using the tools.
A Pega Certified Business Architect (PCBA) possess the fundamental,
Pega Certified Business
essential skills needed for analyzing, designing, and creating business
Architect (PCBA)
requirements and specifications in the Pega application.
A Pega Certified System Architect (PCSA) is a Pega Platform
Pega Certified System application developer or technical staff member who has passed an
Architect exam that acknowledges the acquisition of foundation-level knowledge
of the Pega Platform.
Pega Cloud provides services for customers to augment their IT staff. It
supplies the infrastructure, operational support, and life cycle
Pega Cloud management to support Pega applications as a cloud-delivered
solution. Customers contract and are provided specific services from
the Pega Cloud service catalog to address their application needs.
A Pega composite application is a Pega 7 Platform application that is
embedded on your company web pages as a gadget, without using a
Pega composite
portal rule. Pega composite applications do not support all operations
application
that are normally allowed in Pega 7 Platform applications. You can use
the Pega Web Mashup to build and test a Pega composite application.
Pega Express is an accelerated environment that exposes key
elements and features of the Pega 7 Platform. You access this
Pega Express
environment when you switch from Designer Studio to express mode,
or when you log in to an express application
Pega Global Customer A Pega support organization dedicated to keeping customer
Support (GCS) applications up and running effectively.
The Pega log, also known as the console log or system log, contains
error messages, debug messages, information messages, and Java-
related diagnostics that have been created since the server was most
Pega log
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 mentors are Pega employees or Pega Partners who are
Pega mentors experienced Lead System Architects (LSA) or Business Architects
(BA).
Pega Mobile is an optional product that enables users on mobile
Pega Mobile devices such as smart phones and tablets to access a Pega
application.
The application development, case, data and decision management,
data integration, user interface, reporting, system administration,
Pega Platform
DevOps, mobility, security, robotic automation, workforce intelligence,
intelligent virtual assistant, Java, and activities.
A rich social platform built into Pega that supports collaboration,
Pega Pulse
discussion, and sharing documents in Pega applications.
The PegaRULES database is a relational database that holds the
rules, data instances, work items, history, and other concrete objects
PegaRULES database
from the internal classes of the Pega 7 Platform system. External
classes are not part of the PegaRULES database.
PegaRULES Log The PegaRULES Log Analyzer (PLA) is a Java program that can
Analyzer parse, consolidate, and summarize logs from the Pega log, the alert
log, and JVM. Use PLA results to identify, diagnose, and resolve
issues that might affect performance, stability, or scalability.
Pega Social Engagement is shipped with Pega Customer Service but
is licensed separately as an add-on. Pega Social Engagement enables
Pega Social your global services teams to work together to deliver relevant, fast
Engagement customer eperiences via social channels such as Facebook and
Twitter. Pega uses advanced analytics to cut thorugh the social media
noise and extract only those conversations that matter.
A tool that automates testing to verify the quality of the application
PegaUnit while a continuous integration system automatically packages the
application for export to the application code repository.
The Pega Web Mashup, previously known as the Internet Application
Composer (IAC), enables you to embed a Pega 7 Platform application
Pega Web Machup as a gadget on the pages of a Pega composite application. The Pega
Web Mashup supports the rendering of user interfaces in the HTML5
document type.
The Pega Web Mashup, previously known as the Internet Application
Composer (IAC), enables you to embed a Pega Platform application as
Pega Web Mashup a gadget on the pages of a Pega composite application. The Pega
Web Mashup supports the rendering of user interfaces in the HTML5
document type.
A pending status on a work item 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
pending status
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 workbasket named
deferred@org.com.
The Performance Analyzer (PAL) is a collection of counters and timer
Performance Analyzer
readings that a developer can use to analyze performance in a system.
The Performance tool provides server demand statistics for the current
user since log in, or since the last time you reset the Performance tool
statistics to zero. These statistics include detailed trace of performance
Performance tool
information about running activities, when condition rules, and data
transforms run by your requestor session. You can use these results to
tune your rules for improved server performance.
A Perfrom (harness) is a standard Pega user interface rule used to
Perform (harness)
display an assignment for processing by an end user.
A persistent object is 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
persisent object
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.
The Personal Edition is a limited-distribution, limited-capacity edition of
Pega that is distributed for training and experimental use. It contains a
Personal Edition small application that can be tested and enhanced. All features are
present, but performance is typically constrained by the laptop or
workstation's memory and disk capabilities.
A personal ruleset contains copies of rule instances. Personal rulesets
personal ruleset are used with the check out and check in features. A personal ruleset
is sometimes called a private ruleset.
A pinned class allows you to access objects across inheritance
pinned class
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 it to the static Pinned
Classes section of the Application Explorer.
The Performance Analyzer (PAL) is a collection of counters and timer
playback session
readings that a developer can use to analyze performance in a system.
In Pega Marketing, a population is a group of cases with known
behavior which is consistent with another group of cases whose
population
behavior is to be predicted. In predictive analytics, samples are
extracted for modeling and validation from the population.
Portals provide intuitive, results-focused workspaces that support
developers with the Designer Studio, and users that manage cases
with the Case Manager and mobile portals. Information in the user's
portal
access group, referencing a portal rule (Rule-Portal rule type), governs
the appearance and functions of the portals that are available to that
user.
A gadget provides a rectangular area on a traditional ('fixed') portal (as
opposed to a composite portal). Each gadget contains a control that a
user can interact with. For example, the worklist area of the worker's
home page is implemented through a gadget. Gadgets are defined
portal gadget 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.
A prconfig setting is a name-value pair that affects the operation of a
prconfig setting Pega 7 Platform system. Many prconfig settings have a default value. If
no other value is explicitly assigned, the default value is used.
The prconfig.xml file defines installation and operating parameters for a
prconfig.xml file
Pega 7 Platform node.
A precondition is a reference to a when condition rule (Rule-Obj-When
rule type) or an expression that evaluates to True or False that is
associated with one step of an activity. After the previous step of an
precondition
activity runs, but before the method in the current step runs, the system
evaluates the when condition or expression. If the result is false, this
step is skipped and processing continues at the next numbered step.
In Decision Management, a prediction is a specific to a form of
prediction
behavior that is expected at a given point in time.
A role-based authoring environment focused on defining AI models and
Prediction Studio assets such as predictive, adapative and text analytics. Targeted for
data scientist and decision architects.
In Decision Management, the Predictive Analytics Director (PAD) is a
separate Pega application used to develop and create predictive
models. These models are used to create and define predictive model
Predictive Analytics
rules, which can then be used directly in flows, or combined with other
Director (PAD)
components in a strategy. These models provide a way to differentiate
between cases based on likely future behavior, insights into
opportunities and risks, and the foundation for personalized strategies.
In Decision Management, a predictive model is an algorithm that
delivers predicted behavior and values for one or more segments,
predictive model
given the input of the required data about a case. Predictive models
are developed in the Predictive Analytics Director (PAD).
Predictive Model Markup Language (PMML) is an XML-based
Predictive Model
language that provides compatibility methods to define statistical and
Markup Language
data mining models, and further, shares these models between PMML-
(PMML)
compliant applications.
predictive performance In Decision Management, a predictive performance is one measure of
 the scores or segments generated by models. Performance can be
measured in terms of predictive power, value or rate achieved under
selected conditions.
In Decision Management, predictive power is a measure of the ability
of a scoring model to separate cases with a positive outcome from
predictive power those with a negative outcome using behavior defined in terms of two
opposite types of outcomes; either a symbol to indicate the type of
behavior or the probability of being one of the types.
In Decision Management, a predictor is a property having a predictive
relationship with the outcome. Predictors contain information available
about the cases whose values may potentially show some association
with the behavior you are trying to predict. Examples include:
predictor
Demographic - age, gender and marital status. Geo-demographic -
home address and employment address. Financial - income and
expenditure. Activity or transaction information - the amount of a loan
taken out or the price of the product.
In Decision Management, predictor groupiing is a collection of
predictor grouping predictors whose relationship with behavior is correlated at (or above)
a selected level.
A preference is a setting in Designer Studio that is associated with your
operator, or an access group tied to your operator, that allows you to
preference customize your development experience. Some preferences are
manually managed, and others are automatically detected and updated
by the system. All preferences persist between sessions.
Pre-inception are project processes that occur prior to the Inception
phase in Pega BPM. These usually include pre-sales activities and are
Pre-inception
primarily performed by Sales Executives, Sales Consultants and/or
Practice Leaders.
The journey-centric phase that creates the foundation for the project. It
includes training the project team, setting up environments as needed,
gathering data needed to execute the project, holding a kickoff
Prepare phase
meeting, refining the backlog with Direct Capture of Objectives (DCO)
sessions while you finalize development standards for the development
team and initiate project governance.
A preview is the run-time view of a rule, used to unit-test the
appearance or execution of the rule. Using the Preview function for a
preview
harness, section, flow action, activity or HTML rule, creates a clipboard
page and initializes properties on that page.
A primary page is a clipboard page with the same class as the activity
(or selected other rules), designated when the activity is called. This
primary page
page is the default location of properties referenced with a period and
no preceding page name.
The primary path is the most likely course of action a process follows
primary path
to complete a unit of work. Also called the normal course of events.
A privilege is an application-specific access control element associated
with a class and access role. Using privilege rules in an application is
privilege
optional, but they can offer finer control over access than access roles
alone.
The prlogging.xml file is a control file for the Pega 7 Platform logging
prlogging.xml facility that is located on each node and controls the contents of the
server console output and Pega log files.
A problem assignment, or an assignment in error, is an assignment
that remains open for a long time or references a work object or rule
problem assignment 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 require review and analysis.
 To research problem assignments, use the reports that are available
from Designer Studio > Process & Rules > Tools > Work Admin >
Worklist Assignment Errors.
A process is the path, or paths, a case follows as it is completed
process
(resolved.)
A process analyst also known as a business analyst who focuses on
process analyst
the data needed for reporting, metrics, and analysis.
The Process API consists of the rules for standard activities, flows, and
flow actions that you can use to start and advance flows without using
Process API user forms. These rules can support Pega 7 Platform business
processing through Service Oriented Architecture (SOA) facilities,
including agents and service activities.
A process architect is a member of an application development team
who provides knowledge of business rules, including processes
Process Architect (flows), business objectives, service-level agreements, reporting
requirements, and business policies. A process architect might also be
referred to as a business architect
A process (category) is the grouping of rule types. It includes rule types
process (category) that support business processes such as collection, correspondence,
service level and flows.
Process metrics or statistics are tracked by Pega and include how long
process metrics it takes to complete an assignment, the percentage of flow down a
given pathway or how often SLAs are violated.
Process Modeler is a tool that supports the development of business
Process Modeler processes in your application. You use it on the Flow form to add,
connect, and configure shapes in a flow.
The process page (pxProcess) is a reserved, top-level clipboard page
that contains information from the Data-Admin-System instance. Only
standard activities update the properties on the process page. The
process page
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.
The process participant has a task level view of the data in the
process participant application as they are responsible for entering data into the
application.
A process step represents a task that helps move a case toward
resolution. Steps can be performed by users, your application, or an
process step
external application. Use Case Designer to add steps to the processes
that are supported by each stage in the life cycle of a case.
A product or application that solves a business need, defined by its
product features which may already be built, and delivered through a series of
releases.
The production level of your system is a property in the System data
instance (Data-Admin-System class) with a value between 1 (least
production level
restrictive) and 5 (most restrictive). The current level is recorded as the
value of the pzProductionLevel property on the Process page.
A production ruleset is a ruleset that contains rules that you can modify
production ruleset after the application is deployed. On the Category tab of the Ruleset
form, the Ruleset Type for a production ruleset must be Standard.
The product owner closely collaborates with the team on an ongoing
basis, guides and directs the team by actively managing the product
product owner backlog, answering questions when they arise, providing feedback,
and signing off work results. The product owner decides what should
be done and when the application is ready for go-live.
In the Project Management Framework (PMF), the Project Explorer is a
Project Explorer
tool that lists the Task Groups (Scrum Stories) containing tasks and
 bug fixes assigned to the Operator ID.
The Project Management Framework (PMF) is an application that
Project Management
implements best practices for the management and tracking of Scrum
Framework (PMF)
projects across multiple development and QA environments.
A project worklist shows the open assignments for a user, including
project worklist
user stories, tasks, bugs, and issues.
In Decision Management, the propensity is the probability of positive
propensity
behavior or membership.
A property defines the format and visual presentation of data in your
application. Each property can be associated with a value and has a
mode and type. The property mode, such as Single Value or Page List,
property
defines the structure that is used to store the property value. The
property type, such as Text or Date, defines the format and allowable
characters in the property value.
A property message is a text clipboard value that is generated by the
property message system and associated with a property. A property message can
convey error conditions, progress, or exceptions to a user.
A property mode defines either a single value or a collection of related
property mode (mode) values. Each property has one property mode, as specified in the Rule-
Obj-Property rule.
The Property Optimizer is 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
Property Optimizer 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.
A Designer Studio tool used to allow a property to be retrieved
efficiently from the PegaRULES database so that it can be used in
reporting. Normally property values are stored as part of a BLOB in a
Property Optimizer tool database rather than in a separate column. This tool adds an exposed
column or a declarative index, changes the database schema, and
populates the new column or table with values for existing class
instances.
When referenced in a property, a property qualifier determines the
appearance and allowable values of a portion of the property value. A
property qualifier
property qualifier rule is an instance of the Rule-Obj-Property-Qualifier
rule type.
A property reference is a notation for a run-time reference to the name
property reference or value of a property that you can use in activities, data transforms,
HTML, and other places. This notation is also called dot notation.
A property type is a description of the data that can be stored by a
property type value-mode property, such as text, encrypted text, integer, date, or
true/false.
In Decision Management, a propostion is an offer extended to a
customer, often to resolve a case. The offer can be either tangible,
proposition
such as a handset or a subscription, or intangible offer, such as
benefits, compensation or services.
In Decision Management, proposition bundling is a method of
combining and presenting a number of propositions as a coherent and
proposition bundling
justifiable set in terms of cross-product eligibility, propensity and
likelihood of interest linked to the call reason.
The PublicAPI is the supported public interface to the rules engine. As
PublicAPI
such, the PublicAPI is sometimes referred to as the Engine API.
Pulse is a gadget that adds social activity streams to your application.
Pulse
When embedded in your application, this gadget allows users in the
 same work group to create posts that share instant messages, files,
and URLs.
A Personal Virtual Server (PVS) is a virtual machine (VM) that lets
system and business architects learn Pega without the hassles of
PVS
software installation and configuration. The VM is downloaded and run
on your local machine.
A pyramid chart displays the hierarchical structure and quantity of data
in each segment of the pyramid. The height of each segment, and not
pyramid chart
its width, is significant. You can specify the chart type and subtype for
a report definition report by using the Chart Editor.
The pyWorkPage is the name of the clipboard page that represents the
pyWorkPage current case being processed. This name is reserved by Pega, and
cannot be reused for another property or embedded page.
The Queue Manager is the internal server facility that supports queued
items created by the Queue-for-Agent method. Agents with a Queue
Queue Manager
Method value of Standard (on the Schedule tab of the Agents rule
form) use the Queue Manager.
Queue Processor An internal background process that identifies and queues tasks.
The Quick Create option for certain rule types allows you to create
rules directly in the Create dialog without having to open the rule form.
Quick Create
Rule types with this option include properties, field values, when
conditions, flows, and activities.
The Quick Launch is a portion of the Designer Studio toolbar in Pega 6
that provides access to various developer tools, including the Run
Quick Launch
menu, the Clipboard tool, Tracer tool, Help menu, Designer Studio,
Search, My Recent Rules and Checked Out Rules.
Quiesce is to temporarily disable or remove an application server from
service, usually for the purpose of system maintenance. It allows a
quiesce
system administrator to gracefully transfer activity to other servers in
the cluster without any impact to users.
Delivery that begins with small-scoped customer journeys to develop
Rapid delivery
an application using an iterative process.
Rational Unified Process (RUP) is an iterative software development
process created by the Rational Software Corporation (now a division
Rational Unified
of IBM). RUP is an adaptable process framework, tailored by
Process (RUP)
development organizations and software project teams according to
their needs.
A record is a collective term that describes a rule instance or a data
record instance. You use the Records Explorer to access records available to
you based on your RuleSet list.
The record editor lets you add, edit, and delete data type records. It is
record editor accessed on the Local Data Storage tab of a data type in the Data
Explorer.
Records Explorer (Rules Explorer) is a navigation feature in the
Designer Studio that allows users to quickly access rules and data
Records Explorer
objects; displays all rules regardless of application. In versions of
(Rules Explorer)
PRPC prior to 7.1, the Records Explorer is referred to as the Rules
Explorer.
Refactoring refers to changing the Applies To key part of a rule, the
refactoring
ruleset name and version, or both.
A reference property is a property of mode Single Value, Value List,
Value Group, Page, Page List, or Page Group that can operate to
reference property 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 For learning about and debugging applications, the Referencing Rules
 tool displays where a rule is referenced. For several rule types, the
Referencing Rules tool provides two lists. The left column lists other
rules that reference the current rule and the right column lists rules that
the current rule references.
A regular user is a classification of usage for an Operator ID instance
regular user for a time period by the License Compliance facility. An Operator ID
can count as a regular user during one time period
Related Rules is a button on the Designer Studio toolbar used to
Related Rules access a list of other rules that are alternatives or otherwise related to
this rule.
A set of user stories and bug fixes that are released together as a
release
product. Releases are versioned.
Remote logging is a feature available in the System Management
Application that streams the contents of a log file to your workstation.
remote logging While running a service, you can watch the log for an entire node, or
filter to view the log for a listener or service requestor, rather than
opening the log file repeatedly.
A remote system is any system in a Federated Case Management
remote system (FCM) network that provides cases and work for other systems in the
federation.
The term rendezvous describes the time when multiple flows must
rendezvous
come together at the end of the process.
A repeating layout is a way of presenting information on a form from
sources such as a Page List or Page Group property, a report
repeating layout definition, or a data (declare) page. There are six repeating layouts that
are available; Row Repeat, Column Repeat, Tabbed Repeat, Grid,
Tree Grid, and Tree.
The Report Browser is a tool that provides access to all of the reports
that are available to you. From the Report Browser you can complete
many tasks, such as browsing and searching for existing reports,
Report Browser
running and scheduling reports, creating and modifying reports, and
sharing reports with colleagues. The Report Browser is available in the
Case Manager portal.
A report category provides a way for you organize reports in the Report
report category Browser. Application developers create public report categories, and
managers can create private report categories for their own use.
A rule type used to query for and return case or process data. It
generates a SQL query and displays the query results in a wide variety
report definition of formats. Report definitions can be used to define sets of data used
by other Pega components, such as data transforms, data pages, and
UI layouts.
A report definition rule defines a report definition report. This rule
generates an SQL query that retrieves and sorts information from the
report definition rule 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.
The Report Editor is a tool that displays a report and provides options
Report Editor
for editing it.
Reporting is the process of using an SQL (Structured Query Language)
query to retrieve and sort information from the PegaRULES database,
reporting an external database, or the Elasticsearch index. This process
generates HTML that displays the query results in a variety of formats.
A report definition rule generates the SQL query.
The Report list is a tool in Pega Express that provides access to all of
Report list the reports that are available to you. From the Report List you can click
the report shortcut to run a report, and you can see the category that
 the report belongs to.
A reports database is a mirrored replica of all or part of the
PegaRULES database. To reduce the performance impact of report
reports database
generation, you can specify that some or all reports obtain data from
the reports database.
A report shortcut is a named link in the Report Browser that provides
report shortcut an efficient way to retrieve and run reports. You can use report
shortcuts to organize reports into one or more categories.
The Report Usage landing page provides convenient access to usage
reports that you can run to generate statistics about the usage and
Report Usage landing
performance of report definition reports in the current application. Open
page
the Report Usage landing page from the Designer Studio menu by
clicking Reporting > Tools > Report Usage.
The Report Viewer is a tool that displays the results of a report and
provides options for working the results. Options for working with the
Report Viewer
results might include formatting, filtering, saving, printing, and exporting
the report.
Chargeback representment is the process by which a merchant can
dispute a chargeback with an issuing bank. The representment
representment process allows merchants to present evidence to prove that a
chargeback is not warranted - that is, the merchant ""re-presents"" the
charge to the customer.
A requestor is the process and data associated with a Pega 7 Platform
user (guest or authenticated). A requestor is also the processing and
requestor data associated with a request into your system started by an outside
system, such as a web application server or an Active Server Page on
a web site.
A requestor page is a named top-level clipboard page that contains
requestor page information about your access roles, RuleSet list, and HTTP protocol
parameters.
The requestor scheme is the pxReqScheme property on the requestor
requestor scheme page. It indicates the protocol used by the browser that connects to the
Pega Platform.
Requestor type data instances define the types of requestors that can
requestor type access the Pega 7 Platform, such as a browser session, an external
application, or an internal background process.
A required field is 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
required field
orange asterisk. (This image is only a label to notify users that the field
is required, and does not affect input editing or processing.)
A requirement is an event, condition, or function that must be satisfied
and tracked by an application. A requirement can be functional (a
requirements capability) or non-functional (a quality or constraint). One or more
requirements define the criteria for the successful implementation of a
specification.
A requestor ID is a system-generated hash identifier that uniquely
rerquestor ID identifies a requestor session. A requestor ID is sometimes called the
connection ID.
Resolution is the act of closing a case by recording in the properties
that work is complete. As a case advances through a flow, information
resolution stored in its properties becomes more complete through user input and
automatic processing. When the work for a case is complete, the case
is resolved, or closed.
A Response command is an abstraction between the topic returned
Response command from the Natural Language Processing and a Response in your
channel.
 Responsive behaviors enable a layout to adjust according to screen
responsive behavior size, providing an optimal user experience on a desktop, tablet, and
phone.
Results pages are a clipboard pages that store the results of running
results page the Obj-List-View, Obj-Browse, and RDB-List methods. The Obj-Filter
method operates on results pages.
Reusability is a characteristic of a software component that supports its
use in any process or application beyond its original usage. Pega
reusability
offers multiple facilities to promote reusability, such as class
inheritance and library of standard rules.
In Decision Management, robustness is a statistical term that
robustness measures consistency and reliability for a predictive model based on
many data samples. It is used for model comparison.
role A role is a concise description of a party and their part in a process.
A router activity evaluates assignment criteria, such as required skill
sets and user availability, to determine whether an assignment moves
router activity 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.
A rule is a named business object that defines the behavior of part of
an application, and a single persistent instance of a class derived from
rule
the Rule- base class. Rules are saved in the PegaRULES database,
and the name acts as a unique key for storage and access.
Rule availability is a setting that governs the usability of a rule at
runtime. There are five options for rule availability. Rules with an
availability of Yes or Final are available for use during processing,
rule availability while rules with the availability of Not Available or No/ Draft, Blocked,
or Withdrawn are not. Rule availability is one of the factors considered
by Pega's rule resolution algorithm when determining which rule to use
at runtime.
The Rule- base class is the abstract class that contains all rule classes.
Rule- base class Rules define how an application and the organization that uses that
application run the business.
The rule cache is an in-memory cache of recently found rules that is
rule cache used to improve the performance of Pega Platform, especially during
rule resolution searches.
A rule form displays the fields and values that comprise a rule or data
rule form instance in your application. Rule form types include form-based,
harness-based, and custom.
A rule instance is a unique occurrence of a rule type, which may be
rule instance
differentiated by scope (class), version, or circumstance.
Rule resolution is 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-
rule resolution
base class. Rules assembly is a technique for improving performance
by generating and compiling the Java code that corresponds to a rule
only when needed.
Rule resolution cache is the internal cache of rules evaluated during
rule resolution cache the rule resolution process. Pega maintains a specific rule resolution
cache for each user.
Rules assembly is the process of generating and compiling Java code
rules assembly
to execute a rule.
A ruleset identifies, stores, and manages the set of rules that define an
application or a major portion of an application. A ruleset contains rule
ruleset
instances, which are divided into ruleset versions to support version
management. A ruleset is identified in the system by the ruleset name,
 which is an instance of the Rule-RuleSet-Name rule type.
The ruleset hierarchy is an ordered list of rulesets in applications. The
most general rulesets that provide basic functions are at the bottom,
ruleset hierarchy
rulesets specific to your application are in the middle and rulesets
customized for your organization are at the top.
The ruleset list is an internal data structure that the system uses to
determine which rule instances a requestor can run. When you log in,
ruleset list
the system assembles this list from several sources. The list influences
a phase of rule resolution processing.
A ruleset prerequisite is a ruleset that is required by another ruleset
ruleset prerequisite
that comprises an application.
A ruleset version characterizes the evolution and development of a rule
instance and the application it belongs with. The version number, in the
ruleset version 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.
The rule type is the class a rule belongs to, or is an instance of, and
rule type
must be a concrete class derived from the Rule- base class.
A sample is a subset of historical data extracted by applying a
selection and/or sampling method on a data source. To be meaningful
sample and reliable, the sample must include sufficient records and the
distribution of values and patterns of behavior must be representative
of those in the population.
A sampe application, PegaSample lets you view and study basic
sample application elements without creating new rules. This sample application is built
completely from standard rules in Pega 7 Platform.
A scheduled task is a case that is automatically created to support
scheduled task running reports on a scheduled basis. A scheduled task belongs to the
Pega-ScheduledTask class, and the work ID prefix is px-ST.
A schema is the structure and layout for a database. See PegaRULES
schema
database schema.
In Decision Management, the score is a value calculated by a model.
score
Score intervals are aggregated under a score band.
score band In Decision Management, a score band is aa set of score intervals.
In Decision Management, a scorecard is a decision rule that combines
scorecard a number of properties to calculate segments. The resulting
segmentation is translated into a score.
In Decision Management, a scoring model calculates a score value for
a case on a numeric scale. High scores are associated with good
performance and low scores are associated with bad performance.
scoring model
Typically, the range of scores is divided into intervals of increasing
likelihood of one of the two types of behavior (positive or negative),
based on the behavior of the cases in the development sample.
A screen flow is a type of flow with actions that are configured on
shapes instead of connectors in the flow diagram. Screen flows are
screen flow 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.
A screen layout determines the overall structure of your screen and
defines the structure of a harness in a composite portal. Screen layouts
screen layout
are available only to user interfaces rendered in HTML5 document type
(standards mode). Screen layouts replace the deprecated panel set.
A Scrum Board is an interactive tool that allows teams to view the work
in their sprint. The scrum board shows stories, bugs and issues
Scrum Board
associated with the sprint and allows users to update the status of
tasks, bugs and issues by dragging them across the board.
 A section is an area of a standard user form that is incorporated on a
harness form. The appearance, behavior, and contents of a section are
section
defined by a section rule (Rule-HTML-Section rule type). Sections can
contain other sections.
A rule that defines the content and behavior of a user interface,
section (rule) including property references, controls, and layout types, referred to by
flow action rules and harness rules.
Security auditing is an optional feature that you can use to add
security auditing information to the default details captured in the History Details of a
data instance or rule.
A security role is used by application servers to control access to
security role servlets. For example, the PegaDiagnosticUser security role provides
access to the System Management Application.
In Decision Management, a segment is a group of customers defined
by predicted behavior, score and characteristics. Segmentation
segment
components in a strategy drive the decision flow by placing a customer
in a given segment for which actions and/or results are defined.
A Senior System Architect (SSA) is someone who has taken additional
Senior System Architect
training, and understands advanced technical concepts such as class
(SSA)
structure, inheritance, and rule resolution.
A sequence diagram is an interaction diagram that is organized
sequence diagram according to the time and details of how operations are carried out,
including which messages are sent and when.
A service package is 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
servcie package
of Java classes. Service packages are instances of the Data-Admin-
ServicePackage class, and comprise the first key part of most service
rules.
A service is a programmatic component that defines and implements
an interface between an external application acting as a client and a
service
Pega 7 Platform system acting as a server. An external system sends
a request to a Pega 7 Platform application and receives a response.
A Service Accelerator is a wizard that creates service rules and data
objects for 13 service types, including SOAP, JSR94, .Net, JMS,
Service Accelerator
HTTP, MQ, EJB, File and Java. The Service Accelerator is also known
as the Service wizard.
A service activity is an activity that is referenced by a service rule. At
run time, the activity operates as a BATCH requestor type to perform
service activity
background processing, and returns the results to the client or calling
external system.
The ServiceExport directory is a subdirectory of the temporary files
ServiceExport directory
directory on the server.
A service invocation is a call from an external system to run a Rule-
service invocation Service- rule in your application that creates, updates, or operates on a
work item.
A service levei is an expectation of performance for completion of a
task or case. Service levels establish two time intervals ""a goal and a
deadline"" that define when a task or case should be completed, the
service level
goal and when the task or case must be completed, the deadline. A
service level for a case is defined as part of the case. A service level
for an assignment is defined with a service level rule.
A service-level agreement defines intervals of time, such as a goal and
Service Level deadline, that are used to standardize how you resolve work in your
Agreement (SLA) application. You can apply a service-level agreement to cases, stages,
steps, flows, and assignments.
 A service level rule is used to define the time interval required to
complete an assignment. It includes one or two time intervals, known
service level (rule) as goals and deadlines, which indicate the expected or targeted
turnaround time for the assignment or time to resolution for the case.
See deadline and goal.
A service package is 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
service package
of Java classes. Service packages are instances of the Data-Admin-
ServicePackage class, and comprise the first key part of most service
rules.
In Customer Service, a service process is a work flow that starts within
an interaction, creates a case, and then guides the user through a
service process process to address the case. The case can be completed during the
interaction or can continue processing after the Interaction is
completed. Also known as an Intent Task.
Service Process In Customer Service, a Service Process Accelerator is a wizard that
Accelerator automates the creation of service processes.
In Customer Service, a service request is a case or request to perform
service request a task, usually on behalf of a customer. A service request is processed
using a service process.
The Setup wizard prepares the environment for application
development by configuring the prerequisite elements for logging on to
Setup wizard Pega and building applications. This wizard creates a starter set of
operators, access groups and rules. Formerly called the Initial Setup
wizard and the External Setup wizard.
A shared ruleset contains a small number of rules that each operate on
shared ruleset a common, top-level page of a single class (or of subclasses of that
class).
A shortcut rule defines report shortcuts, which are an efficient way to
view, run, and share reports based on report categories. Report
shortcut (rule)
shortcuts are typically created and managed automatically in response
to user actions, but application developers can create them, too.
A sibling rule is an instance of another rule that has the same visible
sibling rule key. Two rule instances are siblings if they are both visible to you and
have a common value for the pxInsName property.
Simple Object Access Protocol (SOAP) is an XML-based protocol used
Simple Object Access
to exchange information in a decentralized, distributed environment.
Protocol (SOAP)
See SOAP Services.
A simulation is the representation of the behavior or characteristics of a
system, through use of another system. Simulation allows an
simulation
application developer to model the interaction of an outside party such
as a server or even a person without initiating contact with the party.
A Single Step Assignment is a setting in the Stage Designer that
implements a step as a flow rule that contains a single assignment.
Single Step Assignment
When previewing a Single Step Assignment in the Process Outline,
Pega displays the properties panel for the assignment shape.
A property mode that has built-in data types for lower-level elements
single value
such as an integer, decimal or true/false.
A Single Value property, or scalar property, contains a single text
single value property string. Text, numbers, dates, Boolean values, and amounts are stored
in single value properties.
A situational layer cake is a metaphor to describe how Pega interacts
with customers the right way at the right time. Each layer specializes
situational layer cake
on a different dynamic variable, such as customer attributes; country or
region; product or line of business.
 The Sizing tool is an Excel spreadsheet used to estimate the duration
Sizing tool
and size of an implementation project.
A skill rule is an instance of the Rule-Admin-Skill rule type. A skill rule
gives a name and a range of proficiency value for a specific skill.
skill
These skills can be associated with users (in the Operator ID instance)
and can be the basis of routing decisions.
Skimming is the process of saving the highest version of a rule into a
new, higher ruleset version. Skimming applies mainly to rule-resolved
skimming 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.
A skin defines the responsive behavior and formatting, such as colors,
skin fonts, images, and layout, of portals, cases, rule forms, and reports. A
skin generates the styling (Cascading Style Sheet) for the application.
The SmartInfo feature displays a pop-up window when you hover over
SmartInfo specific elements in a report or form. The contents of the pop-up
display are determined by a section rule, and are in read-only mode.
A Smart Layout is a formatting option for a section, in which the layout
is presented as a grid of paired cells that has columns of uniform width,
Smart Layout styles, 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.
A SmartPrompt is a text box used on rule and data forms that
dynamically creates a list of valid selections, providing faster and more
SmartPrompt
accurate data entry. SmartPrompts are identified by a small blue
triangle in the lower right corner of the field.
A Smart Shape is a standard flow shape pre-configured to perform a
Smart Shape
specific task, such as sending an email.
A smoke test is a type of software testing in which an application is
smoke test tested to ensure a minimum level of functionality, to qualify the
application for more-advanced forms of testing.
SnapStart is a data import facility used to generate and pre-populate
cases from an external application without a user log-in process.
SnapStart
SnapStart sends a user ID and password within the URL and uses
Pega's authentication.
Social Intercept No longer being used. See Social Engagement
A solution framework is an industry-specific starter application that
provides a head start to application development for specific industries
solution framework or lines of business. The applications are limited in scope, built on top
of Pega, and designed for use in the framework layer to facilitate
further development and customization.
A spark chart is a microchart that displays graphical information, like
lines and columns, in a compressed format. Because spark charts are
spark chart 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.
A specification represents a unit of processing that is performed by one
or more actors for a given case type within an application. In other
specification words, a specification defines what an application does. One or more
requirements define the criteria for the successful implementation of a
specification.
A high-level scoping document that can be produced for an application,
using the Document wizard. A Specification document consists of a set
Specification document of related specifications - sometimes referred to as a specification set -
produced in advance of a DCO session for review by an
implementation team.
 A spin-off flow is 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
Spin-off
flow or they can work on a different case, based on the context that
you provide.
A Split for Each shape in a flow diagram enabling synchronous
operations use to send a case through another flow based on
Split for Each information in the pages of a Page List or Page Group property. When
these subflows complete, the original flow continues. In some
programming environments, this is called enumeration or iteration.
A Split Join shape in a flow diagram causes processing of a case to
split into two or more independent subprocesses to rejoin and be
Split Join
completed before the current flow continues execution. This allows
subprocesses to execute asynchronously, in parallel.
Split schema is a database configuration in which rules are in a
Split-Schema
separate schema from work and data.
A sprint is a time boxed period in which the project team implements
sprint and delivers a set of stories and bug fixes. The life cycle of a sprint is;
Sprint planning > InProcess/Active sprint > Sprint Review/Resolution.
An SQL function alias is a rule that helps to simplify the creation of
complex SQL queries. You can reference an SQL function alias rule in
SQL function alias
a report definition rule to define SQL expressions for querying a
database for reporting.
A tool that provides a guided interface to help users construct SQL
SQL Function Builder
functions for use in Report Definition rules.
A stage is the first level of organizing work in your case type. It
Stage contains the workflows, or processes, that users follow before they can
move a case to the next phase in the case life cycle.
A stakeholder is a person who is interested in and influences the
development of an application. Project stakeholders provide the funds
stakeholder
or resources for the project. Business stakeholders determine and
evaluate the functionality of the solutions.
standard queue
Pega Platform default queue processor rules.
processor
Standard rules are those rules provided with the Pega Platform. You
standard rules can use standard rules as-is, or you can copy them into your
application and modify them.
A starter flow is a flow that supports the creation of a case. Starter
starter flow
flows are also called starting processes.
Starting workflow In Customer Service, a starting workflow activity used by you
activity application to start a service process.
The static assembler is a utility that you use to preassemble and cache
static assembler
the rules of an application.
Static content is information that is extracted once from a rule to an
static content HTTP server or web server and is unaffected by user input, such as
the use of an application or the contents of user clipboards.
In Decision Management, statistical significance is the degree to which
statistical significance a value is greater or smaller than it would be expected to be by
chance.
A step is a unit of processing that is typically executed as part of an
ordered sequence. Steps can be represented as numbered rows on a
step
rule form, such as the Activity or Collection form, or tasks within a
process.
A step page is a reference to a clipboard page that is available to the
activity, or to a new page that is created by the step. Each step in an
step page
activity could have a designated step page. The step page becomes
the primary page for the duration of the step's execution.
 A Storage Stream is a column in a PegaRULES database table that
contains property data in a compressed format. Most tables in the
Storage Stream
database contain a Storage Stream column, identified as the
pzPVStream column.
Straight-through processing is automatic processing that occurs
straight-through without operator intervention. Straight-through processing is
processing (STP) implemented by using a flow rule that does not contain any
assignments.
In Decision Management, a strategy is the reasoning built up by a set
of components that enables business strategy definition and provides
the decision support to manage an interaction in the context of a
strategy
decision hierarchy. A strategy can import data and propositions and
reference other decision rules (scorecards, predictive models, decision
tables, decision trees, adaptive models and strategies.)
Stream processing is the run-time conversion of an HTML or XML text
block containing JavaServer Page (JSP) tags or HTML directives into a
stream processing final form that does not contain JSP tags or directives. JSP tags or
directives are evaluated as they are encountered from the start of the
string in the context of the current clipboard.
The role-based authoring environments that speed application
studios development and enhance productivity. Studios include, App Studio,
Dev Studio, Admin Studio and Prediction Studio.
A sub-feature defines a capability that extends another capability. For
Sub-feature example, dynamic UI is a sub-feature of user interface because
dynamic UI is a capability of the user interface feature.
A subprocess, also called a subflow, is a flow that is called by another
flow. Subprocesses are represented by the Subprocess, Split Join, or
Subflow (subprocess)
Split For Each shape in a flow diagram. Use Case Designer or Process
Modeler to configure a subprocess in a flow.
A subreport is 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
sub-report
its own subreports. You can designate subreports within report
definition reports to simplify assembling data from several classes, or
to satisfy complex conditions.
A subscription is a way to notify developers and users of actions
related to an application, a report, or an event. Notifications are sent to
subscription
subscribers by using an RSS feed, an email, or a notice on a
dashboard.
A summary view rule defines a summary view report that displays
summary counts, totals, or averages, and you can drill down to
supporting information. The summary view rule is deprecated. Re-
summary view rule
create the custom summary view reports that you need as report
definitions. The last version of Internet Explorer that summary view
rules support is Internet Explorer 11.
The Survey Builder is a wizard that you use to create and manage
Survey Builder surveys. Access the Survey Builder from the My Surveys tab on the
Survey Management landing page.
A suspended case is an open case for which work is halted because
an usual or suspect value is detected. All of the flow executions in
suspended case
process for the suspended case are stopped, and the value for the
property Work-.pxSuspended changes to true.
A swimlane is a shape that organizes and graphically identifies a
Swimlane (shape) related group of shapes that are performed within a specific work
context, typically a work group.
symbolic date A symbolic date is 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 for values of Date and DateTime
properties.
An abstract base class used as the parent for all concrete classes that
System-
hold real-time status information about the server software as it runs.
A system administrator is responsible for system installation and setup,
System Administrator
security and access, and other operational functions.
A system architect is an application developer who contributes object-
System Architect (SA) oriented design and technical implementation skills to an application
development project.
A System- base class is a standard, top-level abstract class that
System- base class contains concrete subclasses that hold real-time status information
about the server software as it runs.
The system ID, or system name, identifies your Pega 7 Platform
system, which includes all instances (nodes) that share a single
system ID
database and the same system name. The system ID is stored in a
System data instance record (Data-Admin-System class).
The System Management Application (SMA) is a web application
System Management distributed with the Pega 7 Platform that enables system administrators
Application and developers to monitor and manage the resources and processes
of Pega 7 Platform applications.
Used by a queue processor or job schedular to figure out the privileges
System Runtime
and permissions available when processing a queued or scheduled
Context
task.
A tag is a text value that case workers and case managers can
associate with one or more cases. They can select from a list of
tag
available tags or create new tags. Case managers can search, access,
and report on tagged cases.
Talk off is a process where the customer service representative (CSR)
asks the cardholder questions to determine if a dispute is necessary -
that is, talk them out of filing the claim or dispute. For example, a
customer says, ""I don't recognize this transaction; it must be fraud.""
talk off The CSR asks, ""Does anyone else in your household have access to
that card? It was an Amazon purchase."" The cardholder says, ""Oh
yes, my son has access to my Amazon account, so it must be him.""
The CSR ffectively talked off the dispute, so the dispute is resolved-talk
off, and no other action is required.
A target property is a property for which a value is to be set, by either
target property
programmatic or declarative means.
In PMF, a task is the work that an operator performs to complete an
assignment. Sometimes used to refer to any shape in a flow diagram.
Tasks are typically created for a story during or after sprint planning.
task
They can be assigned to individual resources on a team and can be
estimated in hours. A scrum best practice is to keep tasks relatively
small -- between 4-16 hours per task.
The Technical category groups rule types and data classes for items
that require advanced skills including familiarity with Java, HTML, XML,
Technical (category)
and JavaScript. Includes 14 rule types, one data class, and one
System- class.
A temporary case is created and resolved by a single operator, or by
straight-through processing, and is not saved as a database object.
temporary case 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.
A tenant is a secure region of a Pega 7 Platform multitenant system. A
tenant
tenant shares a single database, rulesets, and code that support the
 Pega 7 Platform operations of the other tenants in the system. Tenant-
specific content is visible only to the users of that tenant. A tenant is
stored as an instance of the Data-Admin-Tenant class.
The Tenant Administrator is an authorized user who performs basic
tenant administration tasks, primarily the creation and maintenance of
Tenant Administrator
Operator accounts required to use or access the applications and/or
services exposed by the tenant.
The Tenant Proxy Administrator is an authorized user who can do
anything on behalf of the tenant. This user performs application
Tenant Proxy deployments on behalf of the tenant, or more generally, performs any
Administrator function that requires or involves elevated privileges and tenant-
qualified changes. This user can also customize tenant content directly
on the Multitenant System.
A Test ID is a property that supports the automated testing of Pega 7
Test ID Platform applications. To generate Test IDs, configure the Test ID field
on the General tab of the Dynamic Layout property panel.
The Test Management Framework (TMF) is an optional application that
Test Management
implements best practices for the testing and deployment of new
Framework
applications and incremental changes to existing applications.
A text file rule stores static HTML, XML, Cascading Style Sheet,
DHTML and JavaScript script files used in an application, to provide
text file (rule)
the security, inheritance versioning and deployment benefits of rule
resolution for a file.
Themes allow users to change the appearance of their Customer
Service display on PRPC 6 systems. Several standard themes are
Theme
provided or users can create and save their own. Themes are selected
and saved in Customer Service Desktop Preferences.
A PRThread, or thread, is a data structure that allows a requestor to
thread have separate clipboard page name spaces that do not interact with
each other.
A threshold is a target range of values. When a threshold is exceeded,
an alert is generated. You can manage threshold settings and specify
threshold
whether alerts display by updating the prconfig.xml file, or by using
Dynamic System Settings.
Throughput is a measure of work accomplished or completed during a
throughput
calendar interval.
A ticket is a named location that you add to a flow diagram by using
Process Modeler. Tickets identify processing, such as a transaction
ticket
rollback, that occurs when the normal flow progression is interrupted
for a case.
A time-qualified rule is a circumstance that is only rule resolved during
time-qualified rule a specified range of time. This type of rule is commonly referred to as a
date range circumstance or temporary rule.
A topic is an abstraction of the intent or subject that is returned from
topic
Natural Language Processing (NLP).
A 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.
top-level case type
They are typically instantiated by caseworkers 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.
A top-level class is a non-standard, abstract subclass of the ultimate
top-level class
base class, @baseclass.
A top-level page is a clipboard page that is usually created through the
top-level page Page-New method. Applications create many top-level pages during
the course of operations, and activities can create top-level pages.
 Most top-level pages are named, and have an associated class.
The Tracer tool is a feature that you can use to debug flows, data
transforms, activities, services, parse rules, and declarative rules. The
Tracer tool
Tracer tool provides full debugging facilities, including step-by-step
execution, breakpoints, and watch variables.
Traditional portals have a fixed layout and are built from HTML rules
with Data-Gadget as the Applies To key part. Traditional portals are
traditional portal referred to as ""classic"" portals in some menus and selection lists.
Composite portals are recommended for new application development,
rather than traditional portals.
A transfer is the reassignment of a worklist or workbasket by a user or
transfer
manager with appropriate privileges.
A transient property is 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
transient property 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.
A transition is a reference to a when condition (Rule-Obj-When rule
transition
type) or an expression that evaluates to true or false.
In the Transistion phase of the Pega BPM methodology, the application
can be deployed and transitioned to the user community. Once this
Transition phase occurs, issues usually arise that require the development of new
releases to correct problems or complete features that were
postponed.
A plan to support Business as Usual (BAU) activities. It identifies key
transition readiness
roles and responsibilities for maintaining a newly deployed application
plan
and provides necessary supporting documentation.
In Decision Management, treatment of predictors is a statistical term
treatment of predictors that indicates the way a property, used as a predictor variable, is
interpreted by a predictive model.
A tree grid layout allows you to view or edit values of a Page List or
Tree Grid layout report definition. The tree grid is created dynamically and can have as
many rows as needed to display the requested data.
A 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
Tree layout
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.
In Decision Management, trend detection is the ability to identify
patterns by comparing the performance of multiple models that are
triggered by the same proposition and configured with different
trend detection performance window sizes. The ability to calculate performance for a
number of cases during the specified timeframe using a combination of
strategy design patterns and compatible adaptive model rules with
different memory settings.
A 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
trend report
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.
A trigger is the event or method that starts the processing of a
trigger
specified action in response to another event or method.
 A trigger rule identifies an activity that runs automatically when an
object of a specific class is saved or deleted in the PegaRULES
trigger rule
database. This rule is an instance of the Rule-Declare-Trigger rule
type.
The UI Gallery is a collection of examples of effective and dynamic
forms and layouts that use many of Pega's design capabilities,
UI Gallery represent best practice implementations and comply with Pegasystems
guardrails. These examples can be copied into an application and
extended as needed.
In Designer Studio, the UI Inspector tool provides you an easy way to
locate rules in the user interface. The UI inspector can be configured to
UI Inspector (Rules
indicate UI rules, properties, declaratively set property values, and field
Inspector)
values. In versions of PRPC prior to 7.1, the UI Inspector was known
as the Rules Inspector.
The ultimate base class, identified by the symbol @baseclass, is the
topmost class in the class hierarchy. All other classes are derived from
ultimate base class 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 hotfixes are installed in your system and are active;
however, you can still remove them. You can use uncommitted hotfixes
uncommitted hotfix
to test your system with the changes in place before permanently
committing the changes.
A unit is the bottom level of the standard three-level organizational
hierarchy available in every Pega application. The organizational
unit structure affects management reports and statistics, and the ruleset
visible to users in that organization when they log in. See division and
organization.
A unit test is a form of testing performed on an individual rule during
unit test testing. Unit testing verifies that the rule works as intended, without
involving other rules in the testing.
In Decision Management, a univariate model is the result of a
univariate model
quantitative analysis of just one variable.
An unoptimized property is an aggregate property, a property within an
unoptimized property embedded page, or a Single Value property that is stored in a specially
formatted Storage Stream or BLOB column.
Update Controls is a feature that helps render your application user
Update Controls interface in the HTML5 document type. You can also use this feature to
upgrade deprecated controls in a section to improved alternatives.
Urgency is 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
urgency
important it is to address the open work, such as an assignment or
case. You can adjust urgency manually or with a service-level
agreement.
A usage daemon is a background Java thread that collects data
supporting the analysis of performance statistics, saving this data in an
instance of the Log-Usage class. The usage daemon adds one
usage daemon
instance to this class every hour for every requestor, including agents.
On a busy system, the associated PegaRULES database table
pr_perf_stats might grow to contain thousands of rows.
A usage report generates statistics about the usage and performance
of report definition reports in the current application. Several standard
usage report
usage reports are provided, or you can create your own usage reports.
You can run usage reports from the Report Usage landing page.
use case See specification.
 A duse case iagram describes what a system does from the standpoint
use case diagram of an external observer (with emphasis on what a system does rather
than how.)
User acceptance testing (UAT) is a type of software testing in which an
application is provided to end users who provide feedback on the
user acceptance testing
usability of the application. UAT is focused on using an application in
(UAT)
realistic scenarios to ensure that the application behaves in
accordance with its requirements.
A term used in Pega Express to describe flow actions that are
user action
associated with a case type or stage.
A user agent string is a text string that a user agent (such as a web
browser) uses to identify itself to the application it is connecting to
user agent string (such as a Pega application.) A Pega Mobile uses a browsers user
agent string to identify whether a user is on a mobile or desktop
platform.
A User Experience is a person's perceptions and responses that result
from the use or anticipated use of a product, system or service. User
User Experience (UX) experience (UX) includes all the users' emotions, beliefs, preferences,
perceptions, physical and psychological responses, behaviors and
accomplishments that occur before, during and after use.
The user interface category is a grouping of rule types that generate
user interface user-visible forms, through which end users interact with an
(category) application. The User Interface category includes control, flow action,
harness, paragraph, portal, section, and skin rules.
A user interface (UI )is the portion of an application responsible for the
user interface (UI) presentation of information and functionality to an end user, to facilitate
the effective control of the application by the end user.
A user page is a top-level clipboard page created by an activity. It
user page
appears under the User Pages section in the Clipboard tool.
A user reference is a type of field that you configure on a form. At run
user reference
time, it displays a list of existing users in your application.
A term used in Pega Express to describe access control in an
user role
application.
In PMF, a user story is a requirement that is expressed in brief non-
technical language with a set of acceptance criteria. A user story
user story should be small enough to be implemented by a team in one sprint.
Stories are groomed in a backlog and when ready, pulled into a team's
sprint. Once in the sprint, stories can be broken down into tasks.
A utility shape in a flow diagram calls an activity rule. The activity rule
utility (shape) specifies the automated processing to be performed which updates a
case, without any user interaction or input.
An utterance is text or speech that can be categorized to a topic for
utterance
conversation or training purposes.
Validate is a way to check property values against one or more
validate expected values, and return an error message if the property value
does not match the expected value.
A validate rule is used to restrict user inputs by comparing the entered
validate (rule)
properties with a set of conditions.
A Value Group property acts as a container for an unordered list of
Value Group
values of different types. It can contain an unlimited number of values.
A Value List property acts as a container for an ordered list of text
Value List
values. It can contain an unlimited number of values.
In PMF, velocity is a metric that predicts how much work, calibrated in
velocity
story points, a project team can successfully complete within a sprint.
A verbalization is a structured, English text description of an activity.
verbalization
The system can generate a verbalization file (in HTML format) for any
 activity. The file is a useful form of documentation for the activity.
A verification in a workflow is an independent review by one person of
some part of another's work (and of the system's work) before it
verification
becomes final. Verifications are common in financial workflows
involving large dollar amounts or sensitive legal commitments.
The Virtual rules table (VTable) cache is the default caching setting for
all Pega 7 Platform applications. It is a higher performance
replacement for Application-Based-Assembly (ABA) caching. VTable
Virtual rules table cache
caching is automatically primed during system startup with rules that
have been either statically assembled or built dynamically as they were
used in the system.
Visa Claims Resolution (VCR) is Visa's new disputes processing
process that significantly changes the requirements for issuers to file
and acquirers to respond to cardholder disputes and fraud claims. The
new program requires a real time interface between the issuer and the
Visa Claims Resolution
Visa Resolve Online (VROL) system, and between acquirers and the
VROL system, so that they can improve the efficiency of disputes
operations and provide faster resolution times for cardholders and
merchants.
The Visa Resolve Online (VROL) is a dispute processing solution that
can help improve user productivity and reduce labor and training costs
as well as errors associated with back-office exception processing. The
Visa Resolve Online VROL system includes an extensive transaction inquiry component
and a comprehensive exception management processing system, as
well as ancillary functions such as accounting and cardholder letter
generation.
The visible key of an instance is the text value of a reserved property
@baseclass.pxInsName. This property is defined in the ultimate base
visible key
class and is available for use in every class. The value of this property
is sometimes called the instance name, or informally, ""insname.""
The Visual Business Directory (VBD) is a Pegasystems product that
allows users to rapidly model, execute, and modify customer strategies
Visual Business
by analyzing the impact of strategy changes on key business goals
Director (VBD)
such as customer experience, productivity, revenue generation and
risk.
A web node is a server that hosts the Pega 7 Platform part of a
web node composite application. A web node has web as the value of the
nodetype entry in the prconfig.xml file or in Dynamic System Settings.
A Web service is a service that uses SOAP protocol to transmit XML-
Web service
formatted messages.
Web Services Description Language (WSDL) is an XML format defined
Web Services by the World Wide Web Consortium (W3C). Each WSDL file describes
Description Language network services as a set of endpoints operating on messages
(WSDL) containing either document-oriented or procedure-oriented information.
Pega uses WSDL files when integrating with web services.
A when condition rule defines a true-false test based on comparing one
when condition or more property values with constant values or with other property
values.
A when rule is a decision rule that defines a true-false test based on
comparing one or more property values with constant values or with
when (rule) other property values. For example, a when rule can test whether an
amount is greater than zero or a date is in the future. Also known as
when condition rule.
The Where-am-I? feature enables a user to view the current location of
Where-Am-I? inflight work within its case life cycle (stages and step) and current
process diagram.
 A white list is a list of pages or properties that you want to track for a
test case. When you run the test case, only differences in those pages
white list or properties cause the test case to fail. Differences in pages and
properties that are not on the white list are ignored. White list testing is
available for activity test cases.
A wireframe is a schematic or mockup of a user interface that specifies
wireframe
the key elements required in the final user interface.
A wizard include a series of prompts to help accomplish a task with
wizards
minimal effort.
The abstract parent class for any case type. Used as the starting point
Work- for the work-related classes in a class structure. Every application
requires at least one concrete class derived from the Work- base class.
The Work- base class is a superclass to all of the classes that define
Work- base class work items. A work item is the fundamental unit that records processed
work in an application.
A workbasket is a queue of open assignments. A workbasket is
sometimes referred to as a work queue. To view the workbaskets in
workbasket
your application, open the Designer Studio > Process & Rules > Work
Management > Workbaskets landing page.
A worker is a role that defines the behavior and responsibilities of an
individual or a group of individuals working together as a team. The
workers
responsibilities we assign to a worker include both performing a certain
set of activities as well as being the owner of a set of artifacts.
A workflow is a standard set of steps that resolve a case; a sequence
workflow
of activities that produces a result of observable value.
A work group identifies a user who is a supervisor and a set of workers
and workbaskets that report to that supervisor. A work group is an
work group instance of the Data-Admin-WorkGroup class. The Operator ID data
instance (Data-Admin-Operator-ID class) usually identifies the work
group that a user belongs to.
work item See case - work item
work item ID See case ID - work item ID.
A worklist displays open assignments, ordered by urgency, for a
worklist specific operator. You can use your worklist to view the ID, status, and
relevant instructions for each item.
A Work Manager is a traditional (compared to Composite) portal that is
WorkManager used by managers and supervisors who want to use the Monitor
Activity workspace.
A work party represents a person, business, or organization that is
involved in a case. A work party receives correspondence, such as
work party email, and can be an active or passive participant based on its role.
Work parties are added to a case as it is processed. You can list and
configure supported work parties in Case Designer.
A work pool is a set of allowed work items or cases that a user can
work on within an application. The parent Work- and Work-Cover-
work pool
classes for these work items and cases are specified in the user's
access group.
A work pool name is a short description for a class group that is a
work pool naem
collection of work types.
A work pool name is a short description for a class group that is a
work pool name
collection of work types.
A work queue is a list of work in your application that is shared by
work queue operators with the same user role. A work queue is sometimes referred
to as a workbasket.
Work status is a property value that defines whether the case is open
work status
or resolved and the primary indicator of the progress of the case
 towards resolution.
A workstream is a collection of specifications that describe a process
or subprocess, and the steps that comprise the process. During a DCO
session, DCO team members review the contents of the workstream,
workstream
iterating the specifications and requirements as needed and producing
draft flows and draft UI for review. Also referred to as a specification
set.
A work type is a concrete class derived from the Work- base class.
work type Work types derived from the Work-Cover- base class are referred to as
case types
A write-off is a cancellation from an account of a bad debt or worthless
asset. In the context of a dispute, an issuer may choose to assume the
loss amount on its own books. Small dollar transactions may be written
off instead of processing the dispute, because the cost of disputing
write-off
may be more expensive than the amount of the transaction loss.
Transactions may also be written off if the issuer assumes liability for
the dispute (for example, after arbitration) rather than passing the fee
or loss on to the cardholder.
In Decision Management, a Z-ratio is a measure of the reliability of
expected behavior (the predicted percentage versus actual behavior)
that takes into account errors by allowing for statistical significance.
Z-ratio
The Z-ratio is positive when expected behavior is above the average
behavior and negative when expected behavior is below the average
behavior.