Definition

10/2/2020 Take Lesson TL-36945031
Pega Academy Glossary
Term Deﬁnition
An abstract class supports the de nition of rules,

including other classes. Rules with a class as a key
part (including properties, activities, ows, and data
abstract class 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 de nes what the
Acceptance Criteria
product owner expects and what the team needs to
accomplish when implementing the user story or
epic.
Acceptance testing is a level of software testing
where a system is tested for acceptability. The
Acceptance Testing purpose of this test is to evaluate the system's
compliance with the business requirements and
assess whether it is acceptable for delivery.
An access group restricts access to functionality
within your application. You can create multiple
access group
access groups for the same application to achieve
di erent levels of access control.
Access Manager is a landing page that you can use
Access Manager to view and authorize operator access to case types,
data, and tools in your applications.
An access role de nes the classes that a user can
access role view, update, and delete through the Access of Role
to Object and Access Deny rule types.
An acknowledgment is a letter, email, or other
acknowledgment correspondence that is sent to the originator of a
work item and identi es the work item ID.
An acquirer is a nancial institution that represents
the merchants in the transaction. An acquirer
acquirer receives a nancial 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
action section the action is 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
activity more steps. Each step can call a 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 to run. Each user has the
activity list
following activity lists: activity (default), work ow,
and current.
https://pegaacademyapp.pega.com/prweb/PegaSSO/WmhSmvRrQ7qWntq73M7R4oiuqIskpuJu*/!STANDARD?pyActivity=%40baseclass.pzTra… 1/90
10/2/2020 Take Lesson TL-36945031
activity loop An activity loop is a step in an activity that can run

repeatedly, such as 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 activities that you can
activity type
reference directly in ows. The Activity Type eld 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
speci cations. You can view and de ne actors for
actor
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 Engine is
responsible for storing and analyzing adaptive
Adaptive Analytics Engine
statistics and producing individual scoring models.
The scoring models are then used in Pega to
perform calculations used for predictions de ned in
decision strategies.
In Decision Management, this is the database that
Adaptive Data Store
stores the adaptive statistics and adaptive models.
In Decision Management, this is an integrated
technology that extends predictive analytics with an
adaptive mechanism to establish customer
Adaptive Decision 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 and adapt
adaptive model 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
adaptive statistics to the persistent 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
ad hoc case in the case that you are currently processing.
Because ad hoc cases are not instances of a case
type, they are not part of your case-type hierarchy.
A role-based authoring environment focused on
Admin Studio system operations such as agents and queues and
APIs. Targeted for experienced system admins.
An agent is an internal background process
operating on the server that runs activities on a
agent
periodic basis. In a multinode cluster, an agent can
run on multiple nodes.
aggregate property (PRPC 6.x) An aggregate property stores more than a
10/2/2020 Take Lesson TL-36945031
single value, such as a Value List, Page List, Value

Group or Page Group, or a page 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-
Agile Workbench time feedback about your application and tracks
feature development.
An alert event is an entry in the alert log. Alert
alert event events use the naming format PegaRULES-Alert-
YYYY-MMM-DD.log.
The alert log contains a sequence of text les
(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 might take from the primary path.
alternate 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 ows in your organization. Multiple, unrelated
application applications can be hosted in the 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 Pro le (or directly in the Application
Accelerator) to speed the creation of new
applications or the extension of existing
Application Accelerator (AA) applications. The AA automatically creates a case,
and a baseline application that includes organization
and class structure, draft processes and UI
elements. This baseline application can be modi ed
to implement functionality and create a functioning,
production application.
The Application-Based Assembly (ABA) cache
identi es rules for which rules assembly on the
current node is complete. Each rule that generates
Java and executes is a candidate for the ABA cache.
Application-Based Assembly cache
Note: 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.
Application document An application document contains a high-level
business overview, including information on case
types, ows, user interface, speci cations, and
10/2/2020 Take Lesson TL-36945031
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 Express to access tools and
application-editing mode
information. To enable application-editing 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
Application Explorer applications that are available to 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
Application Express minimum of technical expertise. You can then add
ows, user interfaces, and other rules to complete
the application.
An application menu in Designer Studio, that is
identi ed by the name of the current application.
application menu
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.
application name You specify an application name as a 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 archive that contains all of the
classes, rules and data that make up an application.
Application Packaging wizard
The result of the wizard can be exported to a ZIP le
and then imported or migrated to another Pega
system.
An application pro le 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
application pro le
supports the Direct Capture of Objectives (DCO) and
includes the processes, case types, reports,
requirements, speci cations, participants,
collaborators, and actors for a project.
A high-level scoping document that can be produced
from content in an Application Pro le. This
document contains application-speci c user input
that includes, but is not limited to, case types,
Application Pro le document
speci cations, requirements, objectives, interfaces,
reports and correspondence associated with the
selected application. The user can control which
rules and sections appear in the document.
Application Pro ler The Application Pro ler is a wizard that allows users
to enter information about the application or
framework that is being built or extended. The
Application Pro ler creates an Application Pro le
and can also produce a printable project document.
The Application Pro le generated by this wizard can
10/2/2020 Take Lesson TL-36945031
be imported by the Application Accelerator to create

or extend an application or framework.
An application rule de nes a set of ruleset versions
added as a unit to a user's ruleset list. An application
application (rule)
rule is an instance of the Rule-Application rule type,
which is part of the Application De nition category.
An application ruleset is a collection of rules that
identify the components of an application. You must
be a member of a speci ed access group to work
with an application ruleset The set of application
application rulesets
rulesets determines which rules are re ected in
various tools in Designer Studio, such as the
Application Explorer, the Pro le Explorer, and the
Guardrails tool.
The application scoping control is a reusable gadget
that lters by application layer, class name, and
speci ed search term. The combination of lters
application scoping control used depends on how the control has been
con gured. 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 determine which rules are valid to
reference at design time without having to use
Application Validation mode
ruleset prerequisites. Using AV mode o ers
performance advantages over the alternative
Ruleset Validation (RV) mode.
An application bundle is a .zip archive le that
contains an XML document known as the manifest.
applicaton bundle During import of an application bundle, the manifest
controls the order in which rulesets, rules, or other
items in the bundle are imported.
application development targeted for use by
App Studio
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 to
arbitration
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 lled space
rather than points, curves, or lines. You can specify
area chart
the chart type and subtype for a report de nition
report by using the Chart Editor
An artifact is an element of the application
artifact development process, such as a design document,
requirement, speci cation, or UI mock-up.
Assign- A collection of rulesets that represents an
application, including the Application rulesets
de ned for the Application rule, the Application
10/2/2020 Take Lesson TL-36945031
rulesets de ned for any built-on application and the

local customization ruleset.
The Assign- base class is an abstract class above
Assign- base class
other classes containing assignments.
An assignment is a task that must be completed
before an open case can continue through an
assignment executing ow. You con gure assignments in a ow
by using Case Designer or Process Modeler. Either a
user or external system can act on an assignment.
An assignment (shape) identi es a task that must be
completed by a user or external system before an
open case may continue through an executing ow.
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 classes. Associated rulesets help to
associated ruleset
identify which data instances to include in an
application package or when you export rulesets.
An association is a rule type that de nes a one-
directional relationship between two classes, used
often in reporting to include properties from
another class in a report. The rule prede nes a JOIN-
type relationship between instances of two classes,
association 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 in interactive web applications to
exchange small amounts of data as needed, so that
Asynchronous JavaScript and XML (AJAX) the entire web page does not reload each time users
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 le
attachment
added to a case to provide additional information.
An attachment category controls the security of
attachments in your application. It restricts user
operations on an attachment, based on privileges,
attachment category (rule)
when conditions, or attachment types. You can
create attachment categories for your cases in Case
Designer.
attachment type An attachment type de nes the media and format of
items that users attach to work in your application.
An attachment type is implemented in your
application as a class that inherits from Data-
WorkAttach-. The following standard attachment
10/2/2020 Take Lesson TL-36945031
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 includes
audit trail
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 authentication is accomplished by 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
Autocomplete values. As the user types in the eld, a ltered list of
qualifying text values appears below the input eld.
Users can then select a value from this list.
An autocomplete eld 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
ltered list of qualifying text values displays below
Autocomplete eld
the input eld. On an input eld, the icon indicates
that autocomplete is available for the eld. You can
con gure 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 con guring UI rules (sections and
controls). When a rule form is saved, Pega translates
auto-generated
some types of rules (such as control, section, ow
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
Automatic Call Distributor (ACD) (or software) used to direct incoming calls to service
representatives in a call or contact center.
The Automation Server in DevOps pipeline is used
for application package generation, artifact
Automation Server
management, and package promotion to di erent
stages in the work ow to fully automate the CI/CD .
Autonomic Event Services (AES) is an optional
product that monitors, retrieves, organizes and
Autonomic Event Services (AES) displays Pega 7 Platform system statistics and
warning conditions at the enterprise, cluster, and
node levels.
auto-populatied property An auto-populated property is a Page or Page List
property that automatically obtains its data directly
from a speci ed data page. The values can be an
entire object from the PegaRULES database, or
10/2/2020 Take Lesson TL-36945031
copies of pages developed by a Data Page rule. To

enable auto-population for a Page mode or Page List
property, con gure the Data Access elds on the
General tab of the Property form.
A page or page list property that automatically
obtains its data directly from a speci ed data page.
auto-populating property The auto populate can be in the form of a 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 con gured with a set of when
Auto-processing
rules and corresponding ow actions. At run-time,
Pega evaluates the when rules in top-down order
and performs the ow action that corresponds to
the rst 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 is
availability determined by a developer. PRPC provides ve
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 processing. For an available rule, the
available rule
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 or no user intervention. Examples
background process
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. In PMF,
backlog
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 completes an assignment for
a speci c work item and then works on a second
back-to-back assignments
assignment for the same work item. The second
assignment can be from the same ow execution or
an unrelated ow 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
backward chaining
and the Property-Seek-Value method working
together, and can be seen in standard ow actions
including VerifyProperty and
VerifyPropertyWithListing.
bar chart A bar chart displays property values as horizontal
bars. You can specify the chart type and subtype for
10/2/2020 Take Lesson TL-36945031
a report de nition report by using the Chart Editor.

A base class is one of twelve standard abstract
classes that are immediately below the top class in
base class
the hierarchy. This top class, known as the ultimate
base class, is identi ed by the symbol @baseclass
The ultimate (topmost) parent class in the class
hierarchy for any Pega application. All other classes
@baseclass (ultimate baseclass) are derived from this class. The standard 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 circumstanced or time-quali ed. A base rule
base rule
must exist for every circumstance or time-quali ed
rule.
In Decision Management, a behavioral pro les is a
behavioral pro le representation of a 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 you are looking for. Best Bets are
best bet
classes in your application that are the Applies To
key part of one or more rules.
A binary le is a rule type in Pega that identi es
static content les that contain information in a non-
text format, such as images and PDF documents.
Binary le rules store data in a Base64 format to
binary le (rule)
support endian-independent, character-set
independent processing. When extracted or
downloaded, the le 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, images,
Binary Large Object (BLOB) audio or video. PRPC uses BLOB elds to store all of
the data for a case in a proprietary, compressed
format that is highly optimized for performance and
exibility. Also known simply as a "large object".
A blocked rule has an availability status that
indicates to the rule resolution algorithm that the
blocked
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
branch
are undergoing rapid change and development.
A branch ruleset is based o another ruleset and
branch ruleset contains rules that are in active development in the
associated branch.
The breadcrumbs control shows each task, or entry
point, in a ow execution. Application users can click
breadcrumbs control a task based on settings in the ow. The ow can
allow users to jump to any task in a ow, or just to
the completed tasks.
bubble chart 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
10/2/2020 Take Lesson TL-36945031
the other is a category. The horizontal and vertical

axes represent two of the three dimensions, as in
other charts. The size of the colored circle, or
bubble, for each data point represents the third
dimension. You can specify the chart type and
subtype for a report de nition report by using the
Chart Editor.
Build for Change is Pegasystems' corporate slogan
and application development philosophy, that
Build for Change acknowledges the continuous evolution of business
processes through methodologies and tools that
embrace exible procedures.
The Build Order is part of the Construction phase of
the Pegasystems Professional Services project
methodology, and speci es the sequence in which
build order
rules and data instances are created when earlier
phases are complete. The build order might di er 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
bulk processing application. For example, a user could bulk 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-axis
Burndown Chart
shows time starting and ending based on the dates
of your release, project team or sprint. The vertical
Y-axis shows e ort in story points or hours.
Business analysis de nes needs and identi es
business analysis
solutions that add value 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
Business Analyst portal
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 de nes and maintains
business rules, service-level agreements, and
processes ( ows). Business architects include
Business Architect (BA)
subject matter 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
business data
a given task for a given participant.
business day Business days, also known as work days, are
https://pegaacademyapp.pega.com/prweb/PegaSSO/WmhSmvRrQ7qWntq73M7R4oiuqIskpuJu*/!STANDARD?pyActivity=%40baseclass.pzTr… 10/90
10/2/2020 Take Lesson TL-36945031
scheduled work days for users. Business days are

not identi ed as holidays or other days with no work
on a calendar data instance. If your application
includes multiple calendar data instances, a non-
business day for some users might be a business
day for others.
A business exception is an unusual condition within
a business process that warrants investigation or
external review. A business exception might indicate
business exception
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, which supports the Rule-
Business Intelligence Exchange (BIX) Admin-Extract rule type. Data is extracted and
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
business metrics processed or how many orders are canceled.
Business metrics represent the data that you have
de ned when you create properties.
A business objective is an expected business
Business objective
outcome or goal for an application.
Business process management (BPM) is the
organizational activity of developing and managing
processes that are responsive to change and
improve business performance outcomes. When an
Business Process Management (BPM)
organization 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
speci cation that provides a graphical notation for
expressing business processes in a diagram. The
Business Process Modeling Notation (BPMN)
BPMN speci cation also de nes the relationships
between the graphical elements and process
execution languages such as BPEL.
A business rule is a requirement that de nes,
business rule requirement
constrains, and enables organizational operations.
Business Rules Engine (BRE) A business rules engine (BRE) is a Java-based rules
engine that separates business logic from
applications and enables the enterprise to capture,
manage, and execute business policies and practices
as business rules. The business rules engine
supports declarative rules, multithreaded execution,
10/2/2020 Take Lesson TL-36945031
and a large number of industry interfacing

standards.
A Business Use Case is a type of use case
(speci cation) that describes a business process
from beginning to end without regard to process
Business Use Case
ownership. It can involve many di erent actors and
has a very low likelihood of being reused within an
enterprise.
Business Value Assessment (BVA) is a phase of the
implementation methodology during which
Business Value Assessment (BVA) stakeholders de ne 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
cache
of data, 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
Calculation Builder guided interface to help you de ne SQL expressions
for use in report de nition 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,
calendar
workbasket, and Operator ID data instances, and
service-level agreements. The calendar allows due
dates and similar calculations to be based on
business days rather than calendar days.
A call center is an o ce or location used by an
call center organization to receive 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
speci c brand. The Visa and Mastercard associations
do not issue credit or debit cards directly. They each
collectively comprise thousands of banks worldwide.
card association These 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 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 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
10/2/2020 Take Lesson TL-36945031
your application. To access Case Designer, open the

Case Type Explorer and click any case type name.
A case ID is a permanent, external identi er of a
case. A case ID is the value of property pyID. The
case ID (work item ID)
value is unique system-wide and contains an
optional pre x, a number, and an optional su x.
Case instantiation is the way that a case is created in
your application. You can manually create a case or
case instantiation automate this process based on the 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
case management
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 management capabilities and
represent best practice implementations that
Case Management Gallery
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
case manager and update delegated business rules, in addition to
performing work.
The Case Manager portal supports users who
manage cases and their related sub-cases and tasks
Case Manager portal 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
Cases Explorer allows users to view and modify case type
relationships in an application.
Case status is the primary indicator of the progress
case status of a case towards resolution. Case status is the value
of the standard property Work-.pyStatusWork.
A case (step type) is a setting for a case step that
case (step type) con gures the step to generate another case of a
speci ed 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 examples
Cases Type Explorer
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.
case type A case type represents work in your application that
follows a life cycle, or path, to completion. Each case
10/2/2020 Take Lesson TL-36945031
type has a hierarchical structure and 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
case type backlog types and 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 is instantiated or an
case type dependency
assignment is automatically completed. Each
condition de nes a case and a status.
A case type (rule) establishes how to create a case,
case type (rule) including the relationship between the case and any
parent or child case.
A case worker is an individual responsible for
case worker (operator)
creating, processing, and/or resolving a case.
The Case Worker portal provides case workers with
a standard interface for creating, viewing, and
Case Worker portal working on their own cases and 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
case (work item) can 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
category Application Explorer, My Rules, Records Explorer,
Rules Explorer (in versions of Pega prior to 7.1),
attachments and reports to enhance navigation.
A category (rule) de nes an organizational
framework for reports displayed in the Report
Browser. Each category consists of a label and an
category (rule)
owner type, which exposes the category to a speci c
audience, either an individual user, a group of users,
or all users.
A certi cate set gathers in one place all keys and
certi cate set certi cates needed to properly con gure, build, and
run an Android or an iOS mobile app.
Certi ed System Architect A Certi ed System Architect (CSA) is a Pega 7
Platform application developer or technical sta
member who has passed an exam that
10/2/2020 Take Lesson TL-36945031
acknowledges the acquisition of foundation-level

knowledge of the Pega 7 Platform.
A change control requirement documents a
modi cation to a Pega application. You can
change control requirement
implement modi cations before or after the release
of an application.
A channel is a mode of communication or
channel
interaction, such as 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
chargeback charge because the products or 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,
de ne 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 De nition 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 con icts arising when more than
one developer simultaneously try to edit the rule.
Upon check out, a copy of the rule is added to a
check in/check out
ruleset reserved 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 private
checkin process 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
child case type type. Child case types can be instantiated manually
or automatically. You can view your child case types
in the Case Type Explorer.
circumstance A circumstance is an optional quali cation available
for supported rule types. Commonly referred to as a
""circumstanced"" or ""specialized"" version, a
circumstance is based upon an unquali ed rule
known as the base rule. Using circumstances in your
10/2/2020 Take Lesson TL-36945031
application allows you to easily support a variety of

use cases.
Circumstancing is the practice of creating additional
variants of a rule based on speci c 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 quali ed circumstanced version of the base rule.
A class is a collection of rules or other objects. Each
class de nes 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
class diagram application by showing its classes and the
relationships among them.
Class Explorer is a navigation feature in the Designer
Studio that displays portions of the class hierarchy
Class Explorer di erentiating between abstract 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 pre x of the
names of its member classes.
The class hierarchy is a hierarchical structure that
supports the sharing of rules and data. The ultimate
class hierarchy base class (@baseclass) is the topmost class in the
class hierarchy. All other classes are derived from
this class.
A classi cation is a text value in the prcon g settings
or Dynamic System Settings that is used to group
classi cation
nodes that share speci c setting values in a
multinode or clustered system.
Class inheritance is the method by which a child
class can use all of the rules de ned for a parent
class. The Pega Platform supports two types of class
inheritance: directed inheritance and pattern
class inheritance
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 pre x is used during pattern
inheritance when the Pega 7 Platform searches the
class name pre x class structure to nd a rule using a sequence of
pre xes of the class name. The hyphen delimits
segments of the name.
10/2/2020 Take Lesson TL-36945031
Client Event Editor The Client Event Editor is a tool you use to de ne the
runtime behavior of a control when an OnChange,
OnBlur or OnClick event occurs for non-auto-
generated controls, or for auto-generated controls
con gured 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 browser-based users
clipboard 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 system and associated with a
clipboard message
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 a
Clipboard tool 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
coaching tips practices. Users with the appropriate privilege can
create coaching tips for any screen that is available
in a customer interaction.
The Code- base class contains all the classes that
de ne the objects used by the Pega 7 Platform's
own implementation. Application developers can
code- base class
work with properties and clipboard pages
associated with classes derived from the Code- base
class.
In Decision Management, a coe cient is a weight
used for each predictor in the logistic regression
formula. The coe cient indicates the importance of
coe cient a predictor. Negative coe cients imply the presence
of predictors with a very similar behavioral pro le,
and their presence may lead to over tting and
unreliable models.
Coe cient of Concordance (CoC) In Decision Management, the Coe cient of
Concordance (CoC) is a non-parametric coe cient
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 coe cients are sensitive to the complete
range of score bands regardless of their distribution.
The 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
10/2/2020 Take Lesson TL-36945031
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 ow supports discussion among co-
workers. The system saves each participant's inputs
collaboration ow
as note attachments, similar to a discussion forum
thread.
A collection de nes an ordered sequence of rules to
run. On each step you can de ne a precondition that
collection
is evaluated prior to execution, and a response
action that runs after the step completes.
A column chart displays values as vertical bars. You
column chart can specify the chart type and subtype for a report
de nition 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 newly exposed property,
Column Population utility
exposing values that are previously stored only in
the Storage Stream BLOB column. Optionally, it can
also rebuild database indexes and Index- instances
de ned 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 can
populate values for a new column corresponding to
Column Populator
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 de ned 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 (vertical), or two y-axes. The
combo chart
two data sets share the same x axis (horizontal). You
can specify the chart type and subtype for a report
Committed hot xes are permanent parts of the
committed hot x
system. You cannot roll back a committed hot x.
A compensating action allows a custom activity to
update the Pega 7 Platform application data to
compensating action negate the e ects of a connector failure. This type of
action is an optional feature of Connect SOAP and
Connect dotNet rules.
compliance 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
10/2/2020 Take Lesson TL-36945031
compliance case may be initiated by the acquirer. A

compliance case can be led when; a member or its
a liate has violated one or more of the MasterCard
or Visa bylaws and rules or the ling member
documents a nancial loss as a result of the
violation.
A compliance score is a weighted score for each
application that measures overall compliance with
compliance score
the Pega Platform best practices. This score is
available on the Guardrails landing page.
A component ruleset contains rules that are
designed to de ne reusable applications or
functionality that executes embedded within an
component ruleset
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 de ned by a
collection of harnesses that each references a
composite portal
screen layout. Each harness de nes an entire portal
window.
The composition grid in the Data Designer lets you
review and manage the selected data type's
composition grid
properties. The composition grid appears on the
De nition 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
Computer Telephony Integration (CTI) and place calls. In call centers, CTI software allows
applications to monitor 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
concrete class bottom of the list. There are several types of
concrete classes: internal classes, external classes,
rule types, and work types.
The Condition Builder is an editing tool used to
Condition Builder de ne conditions and 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
connection pooling
opening, closing, or 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.
connector The term connector is used in the following two
ways: on a ow diagram, a connector is a line that
connects two shapes. Typically, connectors leaving
10/2/2020 Take Lesson TL-36945031
an assignment shape represent ow actions. Other

connectors might link to a When condition rule. A
connector is also a programmatic component that
de nes 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 ow action completes the current
assignment and advances the ow to the next shape
connector ow action in the sequence. Connector ow actions are
con gured on the line shapes, or connectors, in a
ow that exit assignment shapes.
The Connector and Metadata wizard imports
information about an external application or system
and con gures direct table access without the need
for SQL connector rules. This wizard generates
connector rules or data mapping rules and creates a
Connector & Metadata wizard data class for each table in the database we want to
work with, creates properties in 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
connector (rule) allows an application, acting as a client, to interact
with an external system or database.
A constraint is a comparative relationship between
property values (or between a property value and a
constraint
constant or expression) that is expected to be true
at all times.
A rule used to de ne 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 property when a speci c
constraints
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 con gured, integrated into
the application, and thoroughly tested. The outcome
of this phase is a user-ready product running on the
Construction phase
adequate platforms, with user manuals and a
description of the current release. A large project
may have parallel construction activities to
accelerate deployment.
contact In Customer Service, a contact is the person with
10/2/2020 Take Lesson TL-36945031
whom the user is interacting. A contact can be a

customer, prospect or other interested third party.
In Customer Services, a contact center is an o ce or
location used by an organization to serve customers
contact center
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 correspondence as email, by
contact preference
fax, by phone, or through the mail. The contact
preference is always email for users identi ed 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
container form, marked by a colorful border. 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
uni es a set of classes in the PegaRULES database. It
container class has a name that corresponds 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
Content Security Policy informing the browser of locations that it can use to
obtain content. Each directive governs a speci c
resource type.
Continuous behavior is a range of values which is
continuous behavior usually ordered, for example, the purchase amount,
or length of a relationship.
Continuous delivery (CD) is the ability to deploy
changes of all types, including new functionality,
con guration changes, bug xes, and prototypes
into production, in a quick, reliable, consistent, and
repeatable way. Continous delivery is a software
Continuous delivery
release process that uses automated testing to
validate if changes to an application or system of
applications are correct and stable and ready for
immediate autonomous deployment to a production
environment.
Ready to deploy. Continuously deploying or
shipping. Continuous deployment or continuous
delivery (CD) is a software release process that uses
Continuous deployment automated testing to validate if changes to an
application or system of applications are correct and
stable and ready for immediate autonomous
deployment to a production environment.
Ready to integrate. Continuously integrating into a
shared repository multiple times per day. Continous
Integration (CI) is a development practice where
Continuous integration developers integrate code into a shared repository
frequently, preferably several times a day. Each
integration can then be veri ed by an automated
build and automated test..
10/2/2020 Take Lesson TL-36945031
control A control rule used to dictates how properties

appear on user forms, correspondence and other
HTML forms, for both display and accepting 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 sta in the
development and testing of your Pega application.
Customer resources are trained on Pega technology,
co-production
then 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 is produced by the system and its
users. Correspondence is typically associated with
correspondence 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 COS can convert
Correspondence Output Server (COS) correspondence into an attractive formatted print
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
correspondence template referenced in a ow to provide a template to specify
the format, content and type of correspondence.
The correspondence type de nes whether a
correspondence type correspondence is a 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 de ne 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
CPM Data Source data from external systems. 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
Create Case command the topic returned from the Natural Language
Processing and a case in your Pega application.
credentials 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
10/2/2020 Take Lesson TL-36945031
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 Wide Web Consortium
CSS 3
(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 behalf of a customer. In many
customer
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
Customer Composite account owner. Information in the customer
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 Service and is a
Customer Process Manager (CPM) Pegasystems agship application, used to 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
customer satisfaction organization 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 organization to serve its customers.
Customer Service Representative (CSR) CSRs may interact with customers using several
channels including the telephone, e-mail, letters and
text chat.
A custom eld is an instance of the Index-
CustomFields class that has two parts, a name and a
value. Associating custom elds with rules provides
custom elds a exible way to supplement your application with
metadata, such as a change order number or log le
attachment. Custom elds are not available for
Data- objects.
A customization ruleset is an application ruleset
customization ruleset used as the default ruleset when copying an existing
rule or creating a new rule.
daemon 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
de ned by a Rule-Agent-Queue rule type, are not full
requestors, and operate continuously and
10/2/2020 Take Lesson TL-36945031
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
de nes and contains static data and cumulative
data. Pega 7 Platform applications often retain
database class
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
database table column contains a di erent attribute, such as 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
data class Pega application. Each 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 application. When you select a data
Data Designer
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 associated data pages, and
Data Explorer
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
DataGrid control
existing DataGrid to a Grid control.
A data instance is an instance of a concrete data
class, a concrete class derived from the Data- base
data instance
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 elds received from or sent to an external
data mapping application with properties or other sources or
destinations in Pega Platform. Data mapping is
de ned in service and connector rule forms.
A data model is a collection of entities and attributes
data model that describes the 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
data model (category) information about a case. The Data Model category
includes property, data page, data transform, eld
value, and edit validate rules.
data page (declare page) A data page is used to cache data on demand to a
clipboard page for use by one or more applications.
A data page rule de nes the source, scope, refresh
strategy, editability, and structure of the cached
10/2/2020 Take Lesson TL-36945031
data. Data pages were previously known as

declarative pages.
Data propagation is the act of itializing a case or
data propagation
other item of work 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 speci c 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 eld that you con gure
data reference on a form. At run 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 connector, report
data source
de nition, or lookup. Data sources are referenced in
data pages.
Data tables are superseded by the local data storage
feature. Click Convert for each data table displayed
data table
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
Data Table wizard classes that have a simple 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 Page List property to another, and iterate over
data transform (model)
pages in a Page List property to map data on each
page. These rules de ne 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 de ne and hold data for your application.
For example, a Customer data type might be used to
manage customer contact information. It might
data type
include the customer's name, email, phone number,
and so on. Data types are managed using the Data
Explorer.
Data views Data views de ne the data associated with a data
type and contain the data type's connection
10/2/2020 Take Lesson TL-36945031
con guration to a system of record, separating your

application from the integration with the system of
record. 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 capture and tie business and
DCO (Direct Capture of Objectives)
project goals, objectives, processes, speci cations
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
DCO session
elaborate on a set of high-level application
speci cations to identify and catalog the details
necessary to implement a ow, user interface, or
other application speci cation.
A deadline is an interval of time that is de ned in a
deadline service-level 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
decision running a strategy 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 identi es the most
decision (category)
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 de ntion class is where the set of
decision properties is de ned. You can add these
decision data de nition class
properties to be displayed on 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 o ered to customers.
Successful Decision Management results in
increased customer loyalty and the ability to address
Decision Management (DM) multiple issues in the decision making process.
Decision Management functionality includes
proposition management, strategy development,
using strategy, scorecard and predictive model rules
to drive process ows, capturing interaction results
using Interaction Services (IS), visualization and
monitoring, and advanced adaptive analytics using
Adaptive Decision Manager (ADM).
10/2/2020 Take Lesson TL-36945031
decision (shape) A decision shape within a ow diagram that calls a

decision rule such 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 rules to drive
process ows and strategy development.�It also
Decision Strategy 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 de nes
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 de nes
comparisons by using a tree structure. A decision
decision tree tree contains nested if... then... else 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 de nes the relationship between properties
whose value is automatically (declaratively)
calculated based on changes to other property
declarative network
values. Complex relationships can be con gured and
visualized by using the declarative network display,
which depicts the target property and all potential
input that might a ect its nal 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
declarative rule records: 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 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
declare page
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 speci c need.
Use these rules for high-throughput, distributed
Dedicated queue processor
processes critical to an application or for delayed
queuing.
De ne Properties wizard The De ne Properties wizard allows you to create
10/2/2020 Take Lesson TL-36945031
multiple properties for the same class in a single

form.
A delegated rule is visible to a speci c user or group
of users with a speci c access group. Rule
delegation facilitates rule management outside of
the development environment. A delegated rule can
delegated rule
be a 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
dependency requires (or relies on) 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 among properties can be established
dependency network
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.
De ne the package of software components that
Deployment make up an application in a particular environment,
for example, development or production.
With Deployment Manager, you can fully automate
your CI/CD work ows, including branch merging,
Deployment Manager application package generation, artifact
management, and package promotion to di erent
stages in the work ow.
A descendent class is derived from another class.
Descendent classes can use rules and/or data
descendent class
objects de ned for a parent class by means of either
directed inheritance or pattern inheritance.
Designer Studio is a web-based integrated
development environment that you use to build
Designer Studio
applications. Designer Studio provides access to
tools, wizards, reports, and other features.
DevOps is a collaboration between Development,
Quality Assurance, and Operations sta to integrate
the processes between software development and
DevOps
IT operations teams to deliver high-quality
applications to end users in as automated and agile
a way possible.
advanced functionality such as system settings,
Dev Studio
complex rules or security. Targeted for experienced
app developers, account and security admins.
diagnostic process In Customer Service, a diagnostic process is a service
process which leads customer service
representatives through a series of questions in
order to provide a suggested result. For example,
10/2/2020 Take Lesson TL-36945031
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) to users which are
dialog script 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 development tools and best practices
Direct Capture of Objectives (DCO) that are used to de ne business and project
objectives, processes, speci cations, and
requirements, and link them to implementations
Directed inheritance is the method by which a class
inherits characteristics directly from a speci ed
parent class, regardless of any de ned 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 working with your
Direct Feedback feature
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
directive performance and 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 speci cations and requirements for each case
Discovery Map
type. The Discovery Map captures the primary path
in the ow 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 which a customer questions
dispute
the validity of a transaction that was registered to
the account.
division A division is the middle level of the three-level
organization hierarchy and is available for use in
every application. Divisions are below the
organization level and above the organization unit
10/2/2020 Take Lesson TL-36945031
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, application
Document Application tool
pro le, and speci cation documents that you can
share with stakeholders. This tool was previously
called the Application Document wizard.
The Documentation wizard supports the generation
of Microsoft Word documents that describe the
application, including speci cations, requirements
Document wizard (Application Document wizard) and actors. Because this documentation can be
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-value
dot notation
properties and complex properties. For example,
.CurrentSalary and .Customer.FirstName are both
valid user inputs in a eld that supports expressions.
In Process Modeler, draft mode is a ow-editor
setting that enables users to create or update ows
that reference elements, such as rules and ow
actions, that are not yet de ned or complete. When
draft mode
you run a ow in draft mode, links are displayed on
forms with missing elements. You can use these
links to create the missing elements without exiting
the ow.
A duplicate case is an open instance of your case
type that matches a set of conditions. In business
duplicate case processes, identifying and eliminating 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 exible display of content. Dynamic layouts
separate content and presentation. You add
content, such as properties, controls, dynamic
Dynamic Layout
containers, and other sections, to a dynamic layout
within a section. You set the presentation of that
content by using dynamic layout formats speci ed in
the skin.
A control that displays a drop-down list of text value
choices for an input eld - returned from an activity,
Dynamic Select
a list view, report de nition, or clipboard page -
instead of a static list of values.
Dynamic Select control The Dynamic Select control is an optional feature
you can add to user forms (through HTML rules,
harnesses, or sections) and other HTML forms to
speed user input. The Dynamic Select control is
deprecated, but supported. Use the Dropdown
control (pxDropdown) instead. As a best practice,
10/2/2020 Take Lesson TL-36945031
upgrade Dynamic Select controls to Dropdown

controls.
As a best practice, set system con guration settings
by using dynamic system settings data instances.
For example, you can use dynamic system settings
Dynamic System Settings to con gure which elds are available in full-text
search. Dynamic system settings are stored in the
Pega Platform database and are used by all nodes
that share that database
An Enterprise Application Archive (.ear) is a
compressed le format used by Java EE for
packaging one or more modules into a single archive
for the deployment of the various modules onto an
.ear enterprise application server. The .ear contains one
or more entries representing the modules of the
application and a metadata directory called META-
INF that contains one or more deployment
descriptors.
An edit validate rule de nes a Java routine to test
edit validate the validity of an input value and/or format data;
listed in the Data Model rule category.
An eForm le contains a PDF le that is used as a
template for generating new PDF documents. The
corresponding eForm map speci es the relationship
eForm le between the form elds in the PDF form and
properties in your application. The eForm le 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
su ciently mitigated, to predictably determine the
Elaboration phase
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 de nition, a class
Embed- 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.
embed- base class The Embed- base class is a parent to other classes
10/2/2020 Take Lesson TL-36945031
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-
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
embedded page
child of another page.
An enterprise application is a full-scale application
that is generated by the New Application wizard. It
enterprise application provides all the capabilities in the Pega Platform and
can be developed in Designer Studio or express
mode.
An Enterprise Application Archive (.ear) is a
Enterprise Application Archive (.ear) enterprise application server. The .ear contains one
descriptors.
An Enterprise Application ARchive (EAR) is a
Enterprise Application Archive (EAR) enterprise application server. The .ear contains one
descriptors.
The Enterprise Class Structure, or ECS, is an out-of-
box class structure that provides a foundation for
reuse. There are four layers (Enterprise or
Enterprise Class Structure (ECS)
Organizational, Divisional, Implementation) and
each layer is designed to hold rules that are
specialized for that layer.
An enterprise standard requirement documents
enterprise standard requirement industry or enterprise standards that your
application must include.
An entity is a piece of extractable text or data that
entity
occurs within an utterance.
In a ow, entry points control to which places in the
ow users can move. Assignments and
entry point subprocesses are commonly marked as entry
points, because these are places in a business
process that require human input.
An environment is another system or instance that
PMF integrates with or that PMF is managing work
environment
for. This could be a Pega 7 instance or a 3rd party
application.
10/2/2020 Take Lesson TL-36945031
Epic 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 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 speci ed service-level agreement. For
escalation example, you can send correspondence to
interested parties when a case is 5 days overdue.
Use the Service-level agreement form to con gure
escalation behavior in your application.
An exception path is the least-likely path a process
exception path may take to complete a unit of work. Also called an
alternate scenario.
The Explorers are part of the navigation menu that
Explorers allows access to 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 identi es the rules to be
exported. Rules to be exported are copied to a
Export gadget
speci c ruleset and version. You can copy all rules in
a ruleset, or all rules and data instances de ned in a
speci c 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 enhance record
exposed property
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 subset of the
express application
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 to track important information that
Express History
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, Java
expression operators, standard functions, and properties. On
many forms, you can start the Expression Builder to
provide prompting and guidance while entering an
expression.
Expression Builder The Expression Builder is an interface used to
construct sound Java expressions by guiding the
user's selection, locating functions, completing
10/2/2020 Take Lesson TL-36945031
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
express mode you log in to an express application, express mode is
the default mode. For enterprise applications, you
can switch to express mode from Designer Studio.
An extension point is an activity (or other rule) that
is designed to be overridden to meet application
extension point 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 an
external assignment
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. You can
external class 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 application and appears in the Data
external data entity
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 with an externally mapped
external data source
Applies to class, or a report de nition with an
externally mapped Applies to class.
An external operator is an operator who can process
external assignments. The Directed Web Access
external operator
facility supports sending external assignments to
such operators.
The extract marker le records the date and time of
the initial startup of a node that triggers initialization
processes, such as function library extraction and
extract marker le
compilation. This text le is named
PegaRULES_Extract_Marker.txt and is created during
installation in the temporary les 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-
Family name MyCo-Mortgage.Reopen and Work-MyCo-.Reopen
both have REOPEN as the family name. Or, when a
binary le rule has three key parts de ned as
webwb, pegalogo, and gif, the family name is
WEBWBPEGALOGOGIF.
10/2/2020 Take Lesson TL-36945031
favorite A favorite is a link to a rule or data instance. Use a

favorite to quickly nd items while working in
Designer Studio or the Case Manager portal. You
can create favorites that are visible to your operator
exclusively, another operator, or all operators within
a speci ed 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 de ning features that are linked to
Feature rules and work items, you can 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
Federated Case Management (FCM) display cases and assignments from other
applications in the federation. Each 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 centralized repository for cases and work
Federated Case Management Repository performed by users in a federation. The FCMR
consolidates work items and makes them 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 stakeholders.
feedback
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 ne-tuning of localized
applications, by allowing updates to eld value rules
through a pop-up window that contains translations
while viewing the application. Displays visual
eld value inspector
indicators that link text elements on a form to the
associated eld value rules and identi es missing
eld 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 eld 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
nal rule ruleset to which the rst 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 nal.
10/2/2020 Take Lesson TL-36945031
ow A ow models a business process in your application

by using graphical shapes and connectors to de ne
a sequence of events. You can edit a ow in Case
Designer or Process Modeler.
A ow action displays a task or a choice, such as
Approve or Reject, to users when they run ows. The
ow action two types of ow actions are connector ow actions
and local ow actions. You can edit ow actions in
the Process Modeler or Case Designer.
Flow data is Information needed by an application to
ow data determine what action to perform and who should
perform it.
Flow drafting is the process of iteratively testing and
re ning a ow rule before creating the UI, data
ow drafting
model and decision rules. Flow drafting is an integral
part of the DCO process.
Flow errors are error conditions that prevent a ow
execution from continuing. An example of a ow
error is if the ow references a rule that is not found
ow error
at run time. Click Designer Studio > Processes and
Rules > Processes > Flow Errors to view the ow
errors in your current application.
A ow marker rule is a rule of type Rule-AutoTest-
Case.RunRecursiveTestSuites that supports the
testing of ows. If an operator has the
ow marker AutomatedTesting privilege, that operator can
create and use these ow 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,
ow (rule) processed, and ultimately resolved. A ow rule
consists of a network of shapes and connectors or
lines, each with associated parameters and values.
A ow shape represents a task that is accomplished
as part of a business process. Shapes are
ow shape di erentiated by color, symbol, and name. You add
standard, advanced, and smart shapes to a ow 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
folder collection of one or more cases, including covers
and other folders, to provide access for analysis and
reporting.
A foreground process is any command or task you
run directly and wait for it to complete. Some
foreground processes show a user interface that
Foreground processing
supports ongoing user interaction, whereas others
execute a task and "freeze" the computer while it
completes that task.
fork A fork is an optional con guration for a decision
shape, in which decision logic is con gured using
when rules associated with the connectors
emanating from the decision shape, rather than a
10/2/2020 Take Lesson TL-36945031
decision table, decision tree, or map value rule

con gured 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, update, and resolve cases in
form
your application. Use Case Designer to de ne 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. This
forward chaining
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
fragment to incorporate the fragment rule into other HTML or
correspondence rules as they are processed. A
fragment is an instance of the Rule-HTML-Fragment
rule type or the Rule-Corr-Fragment rule type.
A framework application is an application that you
can extend and modify to create implementation
framework application
applications for a speci c organization, division, or
organization unit.
A framework class de nes a common work-
processing foundation that you extend and modify
framework class as implementation applications for an organization,
division, or organization unit. Framework classes
belong to the framework layer of an application.
A framework layer contains reusable application
framework layer elements and provides an application that you can
use as the basis for many production applications
A fraudulent application (sometimes called FRAP) is
a speci c type of fraud where someone applies for
credit with someone else's social security number,
fraudulent application
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 processing model. The F-score is
F-score
determined by leveraging a test set of training data
to validate and evaluate the models for accuracy.
A Fully Quali ed Name (FQN) is an unambiguous
reference that includes the name of the item being
referenced and any contextual information
necessary to di erentiate the item from another
Fully Quali ed Name (FQN) item with the same name. Fully quali ed names are
most commonly used with 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.
10/2/2020 Take Lesson TL-36945031
function A function de nes a Java function and makes the

function callable from 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, designed to help non-developers
function alias
when creating or updating a decision table or when
rule, or when creating a report.
A functional requirement describes a capability that
functional requirement the application must have to meet your business
needs.
A funnel chart displays the progressive reduction of
data as it passes from one phase to another. You
Funnel chart
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
gadget 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 di erent 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 determine
Gauge chart
whether the value is within a targeted range. You
In Decisioning, a geofence is a rule type used to
de ne the latitude and longitude of a location and a
geofence radius surrounding the location, known as 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 a case type,
geolocation 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
gesture
interaction with an application on a mobile device
A global resource setting is a property value on a
data page that is referenced through speci c syntax
on a connector rule, or by a data instance that
supports a connector. A global resource setting can
reference any property of the appropriate type on a
Global resource setting
data page. The use of global resources settings for
references to external systems, rather than xed
text values in rule forms, allows greater exibility for
changing values such as port numbers, addresses,
and URLs.
goal A goal is an interval of time that is de ned in a
service-level agreement. It is the suggested
10/2/2020 Take Lesson TL-36945031
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 Good faith can be initiated by either an issuer 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
governance
projects to a successful completion.
Grid controls allow you to display the relationships
between large quantities of data and provide a
convenient interface for editing or adding to that
grid controls
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 de nition in a spreadsheet format.
When a grid is bound to a data page or report
de nition that accepts parameters, and the
grid layout
parameter value uses a 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.
The Grooming/Elaboration process is a sequence of
Grooming/Elaboration process ancillary activities used to prepare for, run, and close
a Grooming/Elaboration session.
A Grooming/Elaboration session is a tightly
moderated meeting (never more than 4 hours) with
Grooming/Elaboration session a xed and clearly de ned set of resources whose
sole purpose is the gathering and capturing of detail
related to a xed set of speci cations.
Guardrails are guidelines that help developers
guardrail achieve project success, optimal performance,
reuse, and maintainability for applications.
A guest is an unauthenticated user. See
guest
authentication.
A guided tour is a sequence of tour stops that
provides information, tips, and instructions about
Guided tour the key features in your application. Use the Guided
Tour form to de ne the content that is displayed in
each tour stop.
A handle is a permanent, unique identi er for a class
that includes certain key parts, and the creation date
and time of a single instance for rules and some
handle classes. A handle is sometimes known as an internal
key. The pzInsKey property holds the handle value
for an object. The pzInsKey property is unde ned
until you save the object.
Hardware sizing Estimation of required hardware based on a
complex series of models that are constantly
reviewed, updated, and enhanced leveraging global
10/2/2020 Take Lesson TL-36945031
production eld information, in-house metrics, and

periodic performance benchmarks.
A harness de nes a run-time form and is an
instance of the Rule-HTML-Harness rule type. Each
harness de nes the appearance and behavior of a
harness
form. Harnesses are de ned on the Harness rule
form that at run time produces a user form, rule
form, or composite portal
A headless application uses ows 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 colors. From
heat map
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
Health Insurance Portability and Accountability Act.
The act consists of ve titles. Title I of HIPAA protects
health insurance coverage for workers and their
families when they change or lose their jobs. Title II
of HIPAA, known as the Administrative Simpli cation
(AS) provisions, requires the establishment of
HIPAA national standards for electronic health care
transactions and national identi ers for providers,
health insurance plans, and employers. Title III sets
guidelines for pre-tax medical spending accounts,
Title IV sets guidelines for group health plans, and
Title V governs company-owned life insurance
policies.
Historical processing is a feature that enables an
application (for the current requestor) to operate
based on how rules were de ned on a speci c date.
Historical processing
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
History-
rules. See History- classes.
The History- base class is an abstract class that is
parent to numerous other classes that de ne
cumulative tracking data about the objects in your
History- base class 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
History- classes as a byproduct of the creation of other classes, to
track changes to rules.
History type The history type of a history instance for a case
identi es the event that corresponds to the
10/2/2020 Take Lesson TL-36945031
instance. The history type is recorded as a single

letter value in the pyHistoryType property.
A hot x catalog is a repository of information about
all Pegasystems Inc. hot xes. The catalog describes
the changes in each hot x and is used for
Hot x catalog
dependence checking. Either upload a catalog .zip
le, 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 Web Consortium (W3C), which
HTML 5
includes standards to enforce cross-browser
compatibility.
An HTML fragment is a rule that de nes reusable
HTML not associated with a speci c class, often used
HTML fragment for frequently used HTML text, JavaScript or CSS
text. HTML fragment rules are listed in the Technical
rule category.
An application developed for a speci c business
audience or need, and not intended to be reused for
Implementation application
other audiences or needs. See also framework
application.
An implementation class de nes the extension,
reuse, and specialization of assets in a framework
class layer to meet the business requirements of an
implementation class
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 speci c business
audience or purpose. The contents of the
implementation layer
implementation layer extend the elements of the
framework to create a composite application that
targets a speci c organization or division.
An implementation methodology is a software
development methodology that focuses on project
management, return on investment, conformance to
implementation methodology best practices and compliance 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 speci cation model,
Inception phase project plan, initial risk assessment and 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 de nition and cost/schedule estimates.
index An index is a value that identi es one element (or
member) of an aggregate data structure. These
indexes are sometimes called subscripts. In addition,
10/2/2020 Take Lesson TL-36945031
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 de ne
indexes, sometimes called secondary or alternate
keys, that are stored in the PegaRULES database.
Index- base class These alternate keys are used by the system to
speed searches and provide sorted lists to help
users nd 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 nds by
searching the clipboard at run time. The page
reference to an indirect page starts with the
indirect page
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 rules de ned for a parent class.
inheritance
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 corresponds to a
instance 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
instantiate
through operation of a case type rule or manually.
An instruction initiates an action for a row on an
instruction activity form. The 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 systems in
Integration Designer
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
Integration services systems. Integration services include both connector
and service capabilities. Integration services are
supported by the Pega-IntSvcs ruleset.
The category of rules used to support service
Integration Services category
interfaces between Pega and external systems.
integrator shape 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 ow
diagram might run an activity that automatically
queries an external database to obtain current
prices or current inventory levels. Flows edited with
10/2/2020 Take Lesson TL-36945031
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
intelligent routing
supervisor who thoughtfully distributes work to her
team, intelligent routing in your application can
signi cantly a ect 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
intent-driven processing elements and actions to developers and users. With
intent-driven processing, a Decision shape in a ow
might be named “Require Additional Authorization”,
rather than the more general “AuthCheck”.
Contact, either in real-time or o ine, between the
individual or organization responsible for processing
interaction a case and one or more parties 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 di erent
categories of Service Processes that users can
choose from (such as Account, General, Contact).
In Customer Service, an Interaction Goal re ects an
organization's business rules and can be based on
prior customer interactions, customer pro le or
Interaction Goal
other information. Customer Service may use this
goal to present di erent 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.
Interaction Result Recorded in the IS database tables and 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
Interaction Thumbnail information for the current interaction (such as
Customer Name, Duration Timer, Interaction Goal,
and Call Back Number.)
10/2/2020 Take Lesson TL-36945031
Interaction Timer In Customer Service, an Interaction Timer is a gadget

on each Interaction that indicates how the
interaction is proceeding in relation to a de ned
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 increasing and decreasing the level
interactive chart
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. Customers often
Interactive Voice Response (IVR)
interact with an IVR before being transferred to a
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
in uence the outcome of the work. For example, the
interested party
spouse of a cardholder can be an interested party in
a credit card dispute. By default, you can associate
more than one interested party with a case type in
your application.
An interest page is the primary page that a ow runs
interest page against. An 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, rather than in an
internal class
external database. The properties
@baseclass.pzInsKey and @baseclass.pxObjClass
are de ned for every internal class.
The internal key of an instance is the text value of a
reserved property @baseclass.pzInsKey. This
property is de ned in the ultimate base class and is
available in every class. This value is also known as
internal key the handle. For rule instances, the date and time
that the rule was rst saved becomes a portion of
the internal key. As a result, the pzInsKey property is
unde ned until the new rule instance is saved and
committed.
The Internet Application Composer is a tool that
enables a Pega application to be accessed from the
Internet Application Composer (IAC)
pages of a Web application located on your intranet,
extranet, or internet site.
In Decision Management, an interval is a mechanism
typically used to group the values of numeric
interval
predictors. Each interval provides a useful building
block for understanding behavior.
An issuer is a nancial institution that issues the
issuer
credit or debit card to the cardholder.
iteration Iteration is the process of repeating the same set of
10/2/2020 Take Lesson TL-36945031
actions on any given list. The Split For Each shape in

a ow and the ForEach JSP tag in a stream rule both
support iteration.
A Java Archive (JAR) is a le format that aggregates
Java Archive (JAR)
many les into one ZIP compressed- le.
A Java identi er is an identi er that must start with a
letter, and contain only letters, numbers, and
hyphens. Java identi ers in Pega Platform are similar
Java Identi er
to those de ned in the Java language speci cations,
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 object. The Java
java Object mode 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 enables applications to interact
Java Property mode
with external Java objects as though they were
pages and properties on the clipboard.
Java Virtual Machine (JVM) is an abstract machine. It
is a speci cation that provides runtime environment
Java Virtual Machine (JVM) in which java bytecode can be executed. These are
available for many hardware and software platforms
(JVM is platform dependent).
A background process that schedules recurring
Job Scheduler
tasks.
A methodology that focuses project e orts and
Journey Centric Delivery
application delivery on 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
rst reference of a keyed data page occurs, all the
keyed data page data stores on the data page according to the data
source con guration. 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 elds that you specify on
the Create form for every rule instance and data
instance. Which properties form the key part for
key part objects of a speci c 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) identi es,
monitors and measures the organizational
key performance indicator (KPI)
performance of a business operation that is
considered important by management.
keyring le A keyring le is an encrypted le that contains the
user name and password needed to access the
PegaRULES database. The keyring le is usually
10/2/2020 Take Lesson TL-36945031
named pegarules.keyring. If your application server

supports Java Cryptography Extensions (JCE), you
can identify an encryption algorithm in the crypto
elements of the prcon g.xml le to create the
keyring le.
A keystore is a le that contains security certi cates.
To support Web Services Security and outbound
keystore email security, you can attach a keystore le to a
data instance of the class Data-Admin-Security-
Keystore.
In Customer Service, Knowledge Topics allow agents
Knowledge Topics to create, 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 provides
landing page
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-speci c
rulesets that support localization of applications. A
language pack
language pack provides eld value rules that localize
buttons, prompts, and labels.
A layout is a portion of a section rule, used to
organize the labels, elds, and other controls that
layout 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. A layout
layout group
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 provides technical leadership in
Lead System Architect (LSA)
design and project management tasks 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 instead process each
legacy agent 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 speci cation is a high-level speci cation
created during the Inception phase. Level-1
speci cations contain su cient information to
Level-1 speci cation facilitate project sizing, but may be missing key
implementation details. These application
speci cation rules are later iterated upon in DCO
sessions and become level-2 speci cations.
Level-2 speci cation A level-2 specifricatiaon is more-detailed
speci cation (when compared to a level-1
10/2/2020 Take Lesson TL-36945031
speci cation) that is the result of a DCO session. In

DOC sessions, the level-1 speci cations are iterated
upon to identify and address gaps in the content of
the speci cation. The result of this iteration is a
more-detailed level-2 speci cation. Llevel-2
speci cations contain enough information for
business and system architects to create the process
and/or UI described by the speci cation, and for QA
to create test scripts to test the implementation.
A library (rule) is a container for a set of related
library (rule)
function rules.
License Compliance is a tracking and reporting
system. This feature can provide evidence that
operations of the system comply with provisions of
License Compliance 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 e cient than the default format but
lightweight list does not support certain kinds of processing. You
can specify that results display in a lightweight list
for Obj-Browse methods and lookup lists. Report
de nitions automatically use lightweight lists.
A likelihood is a value between 1 and 100,
interpreted as an assumed or known probability
associated with a ow action. For example, a
likelihood of 66 on a ow action labeled Accept
likelihood means that users completing an assignment linked
to that ow action are expected to choose the
Accept ow action two out of three times. When
editing a ow in Process Modeler, click the percent
sign icon to display likelihood values.
The Link- base class is an abstract class that is an
Link- base class ancestor class to other classes and identi es 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 con gurations, linked properties can
improve performance and eliminate the need to
linked property
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
listener TCP/IP port, mailbox, messaging facility or directory
for arriving messages or les.
list view rule A list view rule de nes a list view report that displays
unsummarized or detailed data. The list view rule is
deprecated. Re-create the custom list view reports
that you need as report de nitions. The last version
10/2/2020 Take Lesson TL-36945031
of Internet Explorer that list view rules support is

Internet Explorer 11.
A live interaction occurs over a synchronous
live interaction channel, such as a telephone call, chat session, or in-
person visit.
Load-balancing is a technique or facility that
load-balancing attempts to provide an even backlog of demand
across multiple processors or production facilities.
A load test is a type of software testing which is
conducted to understand the behavior of the
Load test application under a speci c expected load. Load
testing is performed to determine a system's
behavior under both normal and at peak conditions.
Local data storage is a feature that lets you store
data records for a data type without having to
manually create or maintain database tables. In the
local data storage
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 variant su x.
locale Every user session has a locale setting that can
a ect the language presented by the Pega 7
Platform user interface when displaying or entering
dates, times, and monetary values.
A local ow action leaves the current assignment
open and does not advance the ow. In other words,
you can update the assignment but not complete it.
local ow action If a service-level agreement is associated with the
assignment, the goal or deadline intervals continue
to run. Local ow actions are con gured 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
Localization wizard
language packs for French, German, Japanese,
Spanish, Traditional Chinese and Simpli ed Chinese.
It can also import translations into the language-
speci c ruleset.
Local variables are text strings stored in a Java
StringBu er object rather than in a page structure.
local variable They require less memory and can be 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 activity with
locatable page
type Locate to nd and add the correct page to the
clipboard. Locatable pages can be used with
Constraints rules and Declare Expression.
lock A lock secures an object or a ruleset version to
prevent them from being changed. You can lock
10/2/2020 Take Lesson TL-36945031
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
Lock and Roll and optionally update the 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 that it
locking 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
Log- base class concrete classes) their instances through the
Application Explorer. For concrete classes derived
from the Log- base class, the property
@baseclass.pxCreateDateTime is usually the nal (or
only) key part.
Logging is the process of keeping records of server
activity, called logs or log les, for the use of system
logging administrators. Pega automatically maintains
several log les 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
lookup list cache
saved automatically. Although rarely necessary, you
can cause your system to clear the LLC at startup by
deleting the extract marker le, or at any time by
using the System Management Application.
A major version is the rst two digits of a ruleset
major version 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 speci c maps and the properties of speci c
classes.
A map value is a rule that converts one or two input
values, such as latitude and longitude numbers, into
map value a calculated result value, such as a city name. The
rule uses ranges for the input values and a matrix to
look up the result.
MasterCom MasterCom is Mastercard s online disputes system,
10/2/2020 Take Lesson TL-36945031
for issuers to le chargebacks on behalf of their

cardholders, and for acquirers to 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 Indicators (KPIs). In the
measurement 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
method performed by one step of an activity (Rule-Obj-
Activity rule type), or by a Parse Structured rule
(Rule-Parse-Structured rule type).
A methodology is a set or system of methods,
methodology
principles, and rules for accomplishing a goal.
A microjourney represents the series of interactions
between one type of customer and an organization
Microjourney�
through a speci c delivery channelthat occur as the
customer pursues a speci c goal.
Microservices, also known as the microservice
architecture, is an architectural style that structures
an application as a collection of services. It enables
Microservices
the rapid, frequent, and reliable delivery of large,
complex applications. It also enables an organization
to evolve its technology stack.
Minimum Lovable Product (MLP) is the initial release
of an application built on the Pega Platform that
identi es the rst product release scope and the
Minimal Lovable Product (MLP)
microjourneys that are going to provide the biggest
bene t and delight your customers and internal
users.
MLP is the minimum functionality you need to
Minimum Lovable Product (MLP)
achieve real business bene t.
A minor version is the middle two digits of a ruleset
minor version version number. For ruleset version 01-02-03, the
minor version would be 02.
A mixin is a reusable style pattern de ned in the
mixin skin. Mixins can de ne a combination of reusable
text, border, or background styles.
Mobile compliance indcates that harnesses, controls
and behaviors support the usage of an application
mobile compliance on a mobile device. A mobile-compliant application
does not require any user interface enhancements
to be enabled for mobile users.
mobile preview Mobile preview is a set of interactive icons that
allows you to emulate the appearance of your
application on di erent devices and orientations.
Use it to understand how your user interface
displays on a full screen, laptop browser, tablet, or
phone. To enable mobile preview, select Mobile
10/2/2020 Take Lesson TL-36945031
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
mobile ruleset appended. For 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 specialization mobile 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.
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
modal dialog
until submitting the form or dismissing the modal
dialog box. A ow action provides the sections that
contain the elds that the user must complete.
In Decision Management, model attributes are the
various descriptions and settings created during
model attributes
model development that can be made available to
the decision making system at decision time.
Modeling is the process of generating a conceptual
modeling representation of 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 customer communicated with the
multi-channel
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 multi-step form must be routed 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 ow rule.
Multi Step Process When previewing a Multi Step Process in the Process
Outline, the system displays the ow diagram for the
process.
Multitenancy A Pega Multitenant system is a single system that is
10/2/2020 Take Lesson TL-36945031
logically partitioned into multiple heterogeneous

business processing environments, such that each
environment operates as if on a dedicated,
standalone system. In Pega’s Multitenancy, a tenant
is a exible 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 upgrades,
Multitenant Administrator
apply patches, or perform any function that requires
or 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 enabled during a Pega Platform
Multitenant system
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 to everyone sharing an
My Rules
access group. Each delegated rule is identi ed by a
shortcut link (a favorite).
A named user is a classi cation of an Operator ID
used in the License Compliance facility. Typically, an
named user
Operator ID instance identi es a named user if the
License Type eld on that tab is set to Name.
Natural Language Processing (NLP) is the process of
Natural Language Processing (NLP) deriving understanding and determining an intent
from piece of raw text or 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
navigation panel bars used by managers to switch from one
workspace to another workspace. For the Designer
Studio, the navigation panel contains the Explorer
tools and is called the Explorer area.
A net promoter score is a measure of customer
loyalty and whether they would be willing to
recommend a company, product, or service to
others. Also referred to as a Net Promoter System,
Net Promoter Score or Net Promoter System (NPS)
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
New Application wizard objectives, case types, and data types. You can
create enterprise or express applications by using
this wizard.
In Decision Management, the Next Best Actions
(NBA) is a strategy that allows applications to make
Next Best Action (NBA)
the best decision in a multidimensional context
(retention, recruitment, risk, recommendation, etc.)
A node ID is a unique 32-character identi er for each
node ID
node of the Pega 7 Platform system.
10/2/2020 Take Lesson TL-36945031
non-functional requirement A non-functional requirement places constraints on

how the system operates. Non-functional
requirements specify criteria that may be used to
judge the operation of the system.
Non-functional testing is de ned as a type of
software testing to check non-functional aspects
(such as performance, usability, and reliability) of a
Non-functional testing software application. It is designed to test the
readiness of a system as per nonfunctional
parameters which are never addressed by functional
testing.
An non-live interaction that occurs over an
non-live interaction
asynchronous channel, such as email, fax, or mail.
A class of activity referenced that sends
correspondence, such as an email message, when a
ow execution creates an assignment. Typically, the
notify
system addresses correspondence to a work party
who is identi ed 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 identi ed in the
work item, and reports progress to that party. For
notify activity
example, when referenced in a ow, a notify activity
sends correspondence when an assignment is
created.
An occasional user is a classi cation of usage for an
Operator ID instance for a time period, such as a
calendar month, by the License Compliance facility.
occasional user
This facility can classify an Operator ID as an
occasional user during one period, but count the
operator in another classi cation in other periods.
In Decision Management, the Omega XML Language
(OXL) is the XML le format generated by Predictive
Omega XML Language (OXL)
Analytics Director (PAD) when exporting a predictive
model.
On-premise refers to systems and software that are
On-premise installed and operate on customer sites, instead of
in Pega Cloud.
An on-us item is a check or draft that is presented to
the bank where the check writer has the funds on
on-us deposit. The check can be cashed or deposited into
another account. The drawing account must have a
su cient balance to pay the check.
An open assignment is one that has not yet been
open assignment processed by a user. Open assignments are
associated with a worklist or work queue.
The open authoring feature allows you to specify an
open authoring editor for viewing or editing Java, HTML, or XML rule
form source code.
An open instance is an instance copied from the
database to a clipboard page. Usually, an open
open instance
instance is locked so that only one requestor can
update it at a time.
operator An operator stores the user name, password, and
10/2/2020 Take Lesson TL-36945031
other identifying information for an application user.

Each operator has a role, such as caseworker or
customer service representative, that determines
which 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.
De nes an operator’s username, password, access
operator ID group organizational setting, calendar and other
values.
An operator menu provides access to your operator
pro le and a number of features, depending on
where you access the menu and your application
operator menu con guration. 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 pro le 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
operator pro le
your pro le in the Designer Studio or from the Case
Manager, CaseWorker, WorkManager, or Manager
portals, select Pro le from the operator menu. The
system assembles this information as you log in.
Optical Character Recognition (OCR) is the process
of turning image based text (both printed and
Optical Character Recognition (OCR)
handwritten) into a format that can be 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 enhance
optimized property
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
a ects the management reports, statistics, and rules
Organization
that are available to users in that organization. One
system can support multiple organizations. An
organization is an instance of the Data-Admin-
Organization class.
An organization (category) is a grouping of data
organization (category) classes in used to describe operators, organizational
structure, work groups and workbaskets.
organization hierarchy 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 hierarchy also a ects work item
routing. The organization hierarchy consists of three
10/2/2020 Take Lesson TL-36945031
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 a ects
Organization (record)
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
organization ruleset optional ruleset in the Default Ruleset eld 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 hierarchy and is available for use
organization unit
in every application. An organization unit is an
instance of the Data-Admin-OrgUnit class.
In Decision Management, over tting is a statistical
term describing the fact that a predictive model is
over tting
more accurate in tting 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 area, or
overlay
through an explicit Display > Close action con gured
in the local action. Use an overlay to display simple
forms or ows.
During rule resolution, override is the ability to mask
other available rule instances with the same name
override
but di erent rulesets or the same ruleset but
di erent version numbers.
An Owner is the party who directly caused a case to
Owner exist. Tan Owner can be a customer, an employee, a
vendor representative or another party.
Ownership is a condition that de nes 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
ownership
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 le that contains code or a code
library that you can import in a library rule or
package 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 pages are de ned in
page
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.
10/2/2020 Take Lesson TL-36945031
Page Group An embedded unordered array of pages. See also

property mode.
A Page Group property consists of an unordered set
of pages, each identi ed by a string subscript value.
Use a Page Group property for large lists when you
Page Group property
need to frequently look up speci c pages by a
unique identi er and the order of the pages does
not need to be maintained.
A property mode that allows an embedded ordered
Page List
array of pages. See also property mode.
A Page List property consists of an ordered list of
pages, each identi ed by an integer index (starting
Page List property 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
page message
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 pages are de ned in
Page (property mode)
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 con guration of panels (areas) in a
harness that support a composite portal. Panel sets
panel set are deprecated; although, 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 page parameter names and 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 inheritance. The
parent class 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 ow contains a shape, such as the
Subprocess shape, in the ow diagram that calls
parent ow another ow. You can view the parent ow 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 document or text
parse XML
message into clipboard property values. The
message may be a request for a service or a reply
from a connector.
party See work party.
patch version The patch version is the nal two digits in the ruleset
version number. For ruleset version 01-02-03, the
10/2/2020 Take Lesson TL-36945031
patch version would be 03.

Pattern inheritance is an optional method where a
class inherits characteristics from other classes and
a ects the rst steps in the rule resolution
pattern inheritance 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 and
PDN
partners. The PDN provides short articles, identi ed
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 Application Express and other wizards.
PegaAccel- base class
Generally, you do not work with these classes,
except indirectly by using the tools.
The Pega API consists of Public API, Engine APIs,
Process API consists of the rules for standard
activities, ows, and ow actions that you can use to
start and advance ows without using user forms.
Pega API
These rules can support Pega Platform business
processing through Service Oriented Architecture
(SOA) facilities, including agents and service
activities.
A Pega Certi ed Business Architect (PCBA) possess
the fundamental, essential skills needed for
Pega Certi ed Business Architect (PCBA) analyzing, designing, and creating business
requirements and speci cations in the Pega
application.
A Pega Certi ed System Architect (PCSA) is a Pega
Platform application developer or technical sta
Pega Certi ed System Architect member who has passed an exam that
acknowledges the acquisition of foundation-level
knowledge of the Pega Platform.
Pega Cloud provides services for customers to
augment their IT sta . It supplies the infrastructure,
operational support, and life cycle management to
Pega Cloud support Pega applications as a cloud-delivered
solution. Customers contract and are provided
speci c 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 portal rule. Pega
composite applications do not support all
Pega composite application
operations 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 Customer Service Pega Customer Service is the premier customer
service application that predicts and manages
today's customer journey on a global scale. Part of
10/2/2020 Take Lesson TL-36945031
Pega's CRM Suite, Pega Customer Service can help

you and your employees: anticipate what is right for
customers.
Pega Express is an accelerated environment that
exposes key elements and features of the Pega 7
Pega Express Platform. You access this environment when you
switch from Designer Studio to express mode, or
when you log in to an express application
A Pega support organization dedicated to keeping
Pega Global Customer Support (GCS)
customer applications up and running e ectively.
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
Pega log was most recently started. The Pega log uses the
naming format PegaRULES-YYYY-MMM-DD.log,
where the date portion of the name indicates the
date the application server was recently started (on
the current node).
Pega mentors are Pega employees or Pega Partners
Pega mentors who are experienced Lead System Architects (LSA)
or Business Architects (BA).
Pega Mobile is an optional product that enables
Pega Mobile users on 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, DevOps,
Pega Platform
mobility, security, robotic automation, workforce
intelligence, intelligent virtual assistant, Java, and
activities.
A rich social platform built into Pega that supports
Pega Pulse collaboration, discussion, and sharing documents in
Pega applications.
The PegaRULES database is a relational database
that holds the rules, data instances, work items,
PegaRULES database history, and other concrete objects from the internal
classes of the Pega 7 Platform system. External
classes are not part of the PegaRULES database.
The PegaRULES Log Analyzer (PLA) is a Java program
that can parse, consolidate, and summarize logs
PegaRULES Log Analyzer from the Pega log, the alert log, and JVM. Use PLA
results to identify, diagnose, and resolve issues that
might a ect performance, stability, or scalability.
Pega Sales Automation is the rst seller-centric SFA
to put a digital brain on the desktop of every seller.
It delivers proactive insights to sales representatives
Pega Sales Automation
and managers, showing them the best leads and
opportunities, and the most useful next-best-o ers
and actions that score revenue.
Pega Social Engagement Pega Social Engagement is shipped with Pega
Customer Service but is licensed separately as an
add-on. Pega Social Engagement enables your global
services teams to work together to deliver relevant,
10/2/2020 Take Lesson TL-36945031
fast 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 while a continuous integration
PegaUnit
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 as a gadget on
Pega Web Machup
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 a gadget on
Pega Web Mashup
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
pending status status does not alter the goal times or deadline
times for the assignment. Your ows 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 tool provides server demand
statistics for the current user since login, or since the
last time you reset the Performance tool statistics to
zero. These statistics include detailed trace of
Perfomance Analyzer
performance 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.
The Performance Analyzer (PAL) is a collection of
Performance Analyzer counters and timer 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
Performance tool trace of performance 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
Perform (harness) interface rule used to display an assignment for
processing by an end user.
10/2/2020 Take Lesson TL-36945031
persisent object 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 the database after the requestor session ends.
Generally, pages can become persistent when they
belong to a concrete class, have a non-blank key
de ned, 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 small
Personal Edition 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 are used with the check out and
personal ruleset
check in features. A personal ruleset is sometimes
called a private ruleset.
A pinned class allows you to access objects across
inheritance hierarchies without explicitly switching
contexts. Pinned classes are stored by access group
pinned class
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
playback session counters and timer 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 behavior is to be
population
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
portal and mobile portals. Information in the user's 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
(' xed') 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
portal gadget gadget. Gadgets are de ned 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.
prcon g setting A prcon g setting is a name-value pair that a ects
the operation of a Pega 7 Platform system. Many
10/2/2020 Take Lesson TL-36945031
prcon g settings have a default value. If no other

value is explicitly assigned, the default value is used.
The prcon g.xml le de nes installation and
prcon g.xml le
operating parameters for a 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 speci c to
prediction a form of behavior that is expected at a given point
in time.
de ning AI models and assets such as predictive,
Prediction Studio
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 de ne predictive model
rules, which can then be used directly in ows, or
Predictive Analytics Director (PAD)
combined with other components in a strategy.
These models provide a way to di erentiate
between cases based on likely future behavior,
insights into opportunities and risks, and the
foundation for personalized strategies.
The Predictive Diagnostic Cloud (PDC) is a secure
Software as a Service (SaaS) o ering of Autonomic
Event Services (AES). PDC runs on Pega Cloud and
actively gathers, monitors, and analyzes real-time
performance and health indicators from all active
Predictive Diagnostic Cloud (PDC)
Pega Platform applications. PDC also predicts
potential system performance and business logic
issues and noti es business stakeholders and IT
administrators with remediation suggestions before
they impact the business.
The Predictive Diagnostic Cloud (PDC) is a secure
Software as a Service (SaaS) o ering of Autonomic
Event Services (AES). PDC runs on Pega Cloud and
actively gathers, monitors, and analyzes real-time
performance and health indicators from all active
Predictive Diagnostic Cloud (PDC)
Pega Platform applications. PDC also predicts
potential system performance and business logic
issues and noti es business stakeholders and IT
administrators with remediation suggestions before
they impact the business.
predictive model In Decision Management, a predictive model is an
algorithm that delivers predicted behavior and
values for one or more segments, given the input of
the required data about a case. Predictive models
10/2/2020 Take Lesson TL-36945031
are developed in the Predictive Analytics Director

(PAD).
Predictive Model Markup Language (PMML) is an
XML-based language that provides compatibility
Predictive Model Markup Language (PMML) methods to de ne statistical and data mining
models, and further, shares these models between
PMML-compliant applications.
In Decision Management, a predictive performance
is one measure of the scores or segments generated
predictive performance 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 those
predictive power with a negative outcome using behavior de ned 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
predictor predict. Examples include: 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
predictor grouping collection of 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 customize
preference 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
Pre-inception include pre-sales activities and are 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,
Prepare phase
holding a kicko meeting, re ning the backlog with
Direct Capture of Objectives (DCO) sessions while
you nalize development standards for the
development team and initiate project governance.
preview A preview is the run-time view of a rule, used to unit-
10/2/2020 Take Lesson TL-36945031
test the appearance or execution of the rule. Using

the Preview function for a harness, section, ow
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),
primary page designated when the activity is called. This 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
primary path a process follows to complete a unit of work. Also
called the normal course of events.
A privilege is an application-speci c access control
element associated with a class and access role.
privilege Using privilege rules in an application is optional, but
they can o er ner control over access than access
roles alone.
The prlogging.xml le is a control le for the Pega 7
Platform logging facility that is located on each node
prlogging.xml
and controls the contents of the server console
output and Pega log les.
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 that is no longer
available. When either of these conditions is
detected, the assignment status (the
problem assignment 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
process
completed (resolved.)
A process analyst also known as a business analyst
process analyst who focuses on the data needed for reporting,
metrics, and analysis.
The Process API consists of the rules for standard
activities, ows, and ow actions that you can use to
start and advance ows without using user forms.
Process API 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 ( ows), business
Process Architect objectives, service-level agreements, reporting
requirements, and business policies. A process
architect might also be referred to as a business
architect
process (category) A process (category) is the grouping of rule types. It
includes rule types that support business processes
10/2/2020 Take Lesson TL-36945031
such as collection, correspondence, service level and

ows.
Process metrics or statistics are tracked by Pega and
include how long it takes to complete an
process metrics
assignment, the percentage of ow down a given
pathway or how often SLAs are violated.
Process Modeler is a tool that supports the
development of business processes in your
Process Modeler
application. You use it on the Flow form to add,
connect, and con gure shapes in a ow.
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.
process page
The contents of the process page are identical for
every requestor on a node. This page has a class of
Code-Pega-Process. Use the Clipboard tool to view
this page.
The process participant has a task level view of the
process participant data in the 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 external application.
process step
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,
product de ned by its 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 restrictive) and 5 (most
production level
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 after the application is
production ruleset 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 backlog,
product owner answering questions when they arise, providing
feedback, and signing o 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 tool that lists the Task Groups
Project Explorer
(Scrum Stories) containing tasks and bug xes
assigned to the Operator ID.
Project Management Framework (PMF) The Project Management Framework (PMF) is an
application that implements best practices for the
10/2/2020 Take Lesson TL-36945031
management and tracking of Scrum projects across

multiple development and QA environments.
A project worklist shows the open assignments for a
project worklist
user, including user stories, tasks, bugs, and issues.
In Decision Management, the propensity is the
propensity
probability of positive behavior or membership.
A property de nes 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
property
Value or Page List, de nes the structure that is used
to store the property value. The property type, such
as Text or Date, de nes the format and allowable
characters in the property value.
A property message is a text clipboard value that is
property message
property. A property message can convey error
conditions, progress, or exceptions to a user.
A property mode de nes either a single value or a
collection of related values. Each property has one
property mode (mode)
property mode, as speci ed 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
BLOB. Optimizing a property improves the e ciency
Property Optimizer
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 e ciently from the PegaRULES
database so that it can be used in reporting.
Normally property values are stored as part of a
Property Optimizer tool BLOB in a 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 quali er
determines the appearance and allowable values of
property quali er a portion of the property value. A property quali er
rule is an instance of the Rule-Obj-Property-Quali er
rule type.
A property reference is a notation for a run-time
reference to the name or value of a property that
property reference 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
property type be stored by a value-mode property, such as text,
encrypted text, integer, date, or true/false.
10/2/2020 Take Lesson TL-36945031
proposition In Decision Management, a propostion is an o er

extended to a customer, often to resolve a case. The
o er can be either tangible, such as a handset or a
subscription, or intangible o er, such as bene ts,
compensation or services.
In Decision Management, proposition bundling is a
method of combining and presenting a number of
proposition bundling propositions as a coherent and justi able 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
PublicAPI the rules engine. As such, the PublicAPI is
sometimes referred to as the Engine API.
Pulse is a gadget that adds social activity streams to
your application. When embedded in your
Pulse application, this gadget allows users in the same
work group to create posts that share instant
messages, les, and URLs.
A Personal Virtual Server (PVS) is a virtual machine
(VM) that lets system and business architects learn
PVS Pega without the hassles of software installation and
con guration. 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 its
pyramid chart
width, is signi cant. You can specify the chart type
and subtype for a report de nition report by using
the Chart Editor.
The pyWorkPage is the name of the clipboard page
that represents the current case being processed.
pyWorkPage
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-
Queue Manager for-Agent method. Agents with a Queue Method
value of Standard (on the Schedule tab of the Agents
rule form) use the Queue Manager.
An internal background process that identi es and
Queue Processor
queues tasks.
The Quick Create option for certain rule types allows
you to create rules directly in the Create dialog
Quick Create without having to open the rule form. Rule types
with this option include properties, eld values,
when conditions, ows, 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 menu, the
Quick Launch
Clipboard tool, Tracer tool, Help menu, Designer
Studio, Search, My Recent Rules and Checked Out
Rules.
quiesce Quiesce is to temporarily disable or remove an
application server from service, usually for the
purpose of system maintenance. It allows a system
10/2/2020 Take Lesson TL-36945031
administrator to gracefully transfer activity to other

servers in the cluster without any impact to users.
Delivery that begins with small-scoped customer
Rapid delivery journeys to develop an application using an iterative
process.
Rational Uni ed Process (RUP) is an iterative
software development process created by the
Rational Software Corporation (now a division of
Rational Uni ed Process (RUP)
IBM). RUP is an adaptable process framework,
tailored by development organizations and software
project teams according to their needs.
A record is a collective term that describes a rule
instance or a data instance. You use the Records
record
Explorer to access records available to you based on
your RuleSet list.
The record editor lets you add, edit, and delete data
record editor type records. It is 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 objects; displays all
Records Explorer (Rules Explorer)
rules regardless of application. In versions of PRPC
prior to 7.1, the Records Explorer is referred to as
the Rules Explorer.
Refactoring refers to changing the Applies To key
refactoring
part of a rule, the 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 maintain what
reference property 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.
For learning about and debugging applications, the
Referencing Rules tool displays where a rule is
referenced. For several rule types, the Referencing
referencing rules 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.
Regression testing is a type of software testing to
Regression testing con rm that a recent program or code change has
not adversely a ected existing features.
A regular user is a classi cation of usage for an
Operator ID instance for a time period by the
regular user
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
Related Rules toolbar used to access a list of other rules that are
alternatives or otherwise related to this rule.
A set of user stories and bug xes that are released
release
together as a product. Releases are versioned.
remote logging Remote logging is a feature available in the System
Management Application that streams the contents
10/2/2020 Take Lesson TL-36945031
of a log le to your workstation. While running a

service, you can watch the log for an entire node, or
lter to view the log for a listener or service
requestor, rather than opening the log le
repeatedly.
A remote system is any system in a Federated Case
remote system Management (FCM) network that provides cases and
work for other systems in the federation.
The term rendezvous describes the time when
rendezvous multiple ows must 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 de nition, or a
repeating layout
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 Browser. Application
report category 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 of formats. Report
report de nition
de nitions can be used to de ne sets of data used
by other Pega components, such as data transforms,
data pages, and UI layouts.
A report de nition rule de nes a report de nition
report. This rule generates an SQL query that
retrieves and sorts information from the PegaRULES
report de nition rule database, an external database, or an Elasticsearch
index, and displays the results in a variety of
formats. The two types of report de nition reports
are summarized reports and list reports.
The Report Editor is a tool that displays a report and
Report Editor
provides options for editing it.
Reporting is the process of using an SQL (Structured
Query Language) query to retrieve and sort
information from the PegaRULES database, an
reporting external database, or the Elasticsearch index. This
process generates HTML that displays the query
results in a variety of formats. A report de nition
rule generates the SQL query.
Report list The Report list is a tool in Pega Express that
provides access to all of the reports that are
10/2/2020 Take Lesson TL-36945031
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
reports database performance impact of report 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 an e cient way to retrieve
report shortcut
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 performance of
Report Usage landing page report de nition reports in the current application.
Open 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
Report Viewer results. Options for working with the results might
include formatting, ltering, 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 process allows merchants
representment
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 data associated
requestor
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
requestor page page that contains information about your access
roles, RuleSet list, and HTTP protocol parameters.
The requestor scheme is the pxReqScheme property
requestor scheme on the requestor page. It indicates the protocol used
by the browser that connects to the Pega Platform.
Requestor type data instances de ne the types of
requestors that can access the Pega 7 Platform, such
requestor type
as a browser session, an external application, or an
internal background process.
A required eld is an input eld on a form that must
have a non-blank value to be valid. Many ow action
forms mark a required eld with an orange asterisk.
required eld
(This image is only a label to notify users that the
eld is required, and does not a ect input editing or
processing.)
requirements A requirement is an event, condition, or function
that must be satis ed and tracked by an application.
10/2/2020 Take Lesson TL-36945031
A requirement can be functional (a capability) or

non-functional (a quality or constraint). One or more
requirements de ne the criteria for the successful
implementation of a speci cation.
A requestor ID is a system-generated hash identi er
rerquestor ID that uniquely identi es 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 ow, information stored in its
resolution
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
Response command topic returned from the Natural Language
Processing and a Response in your channel.
Responsive behaviors enable a layout to adjust
responsive behavior according to screen size, providing an optimal user
experience on a desktop, tablet, and phone.
Results pages are a clipboard pages that store the
results of running the Obj-List-View, Obj-Browse,
results page
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
reusability application beyond its original usage. Pega o ers
multiple facilities to promote reusability, such as
class inheritance and library of standard rules.
In Decision Management, robustness is a statistical
term that measures consistency and reliability for a
robustness
predictive model based on many data samples. It is
used for model comparison.
A role is a concise description of a party and their
role
part in a process.
A router activity evaluates assignment criteria, such
as required skill sets and user availability, to
determine whether an assignment moves to a
router activity worklist or work queue for processing. Router
activities have the Usage eld 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 de nes the
behavior of part of an application, and a single
persistent instance of a class derived from the Rule-
rule
base class. Rules are saved in the PegaRULES
database, and the name acts as a unique key for
storage and access.
rule availability Rule availability is a setting that governs the usability
of a rule at runtime. There are ve options for rule
availability. Rules with an availability of Yes or Final
are available for use during processing, 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
10/2/2020 Take Lesson TL-36945031
resolution algorithm when determining which rule

to use at runtime.
The Rule- base class is the abstract class that
contains all rule classes. Rules de ne how an
Rule- base class
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 used to improve the performance
rule cache
of Pega Platform, especially during rule resolution
searches.
Use the Compare Rules tool to compare two
di erent rules or two versions of the same rule to
Rule Compare Utility
nd additions, changes, or deletions from one
version to another.
A rule form displays the elds and values that
comprise a rule or data instance in your application.
rule form
Rule form types include form-based, harness-based,
and custom.
Rule Form Search Utility can search for content
within some rule forms. Search for content within a
Rule Form Search Utility
rule form by clicking the Actions menu, clicking
Search rule, and entering text to search.
A rule instance is a unique occurrence of a rule type,
rule instance which may be di erentiated by scope (class),
version, or circumstance.
Rule resolution is the search algorithm used by Pega
Platform to nd 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 the rule resolution process. Pega
rule resolution cache
maintains a speci c rule resolution cache for each
user.
Rules assembly is the process of generating and
rules assembly
compiling Java code to execute a rule.
A ruleset identi es, stores, and manages the set of
rules that de ne an application or a major portion of
an application. A ruleset contains rule instances,
ruleset which are divided into ruleset versions to support
version management. A ruleset is identi ed 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
ruleset hierarchy basic functions are at the bottom, rulesets speci c to
your application are in the middle and rulesets
customized for your organization are at the top.
ruleset list 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, the system
10/2/2020 Take Lesson TL-36945031
assembles this list from several sources. The list

in uences a phase of rule resolution processing.
A ruleset prerequisite is a ruleset that is required by
ruleset prerequisite
another ruleset 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 format NN-
ruleset version NN-NN, de nes the major version ( rst 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
rule type instance of, and 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 and reliable, the
sample
sample must include su cient 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 elements without creating new rules.
sample application
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 running reports on a scheduled
scheduled task
basis. A scheduled task belongs to the Pega-
ScheduledTask class, and the work ID pre x is px-ST.
A schema is the structure and layout for a database.
schema
See PegaRULES database schema.
In Decision Management, the score is a value
score calculated by a model. Score intervals are
aggregated under a score band.
In Decision Management, a score band is aa set of
score band
score intervals.
In Decision Management, a scorecard is a decision
rule that combines a number of properties to
scorecard
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 ow is a type of ow with actions that are
con gured on shapes instead of connectors in the
ow diagram. Screen ows are typically used to
screen ow
present a series of assignments to a single user, and
allow the user to go back and change or review the
input on each screen.
screen layout A screen layout determines the overall structure of
10/2/2020 Take Lesson TL-36945031
your screen and de nes the structure of a harness

in a composite portal. Screen layouts are available
only to user interfaces rendered in HTML5
document type (standards mode). Screen layouts
replace the deprecated panel set.
The Scrum methodology takes an agile approach to
Scrum development that accomplishes iterations in short
cycles called sprints.
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 associated
Scrum Board
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,
section behavior, and contents of a section are de ned by a
section rule (Rule-HTML-Section rule type). Sections
can contain other sections.
A rule that de nes the content and behavior of a
user interface, including property references,
section (rule)
controls, and layout types, referred to by ow action
rules and harness rules.
Security auditing is an optional feature that you can
use to add information to the default details
security auditing
captured in the History Details of a data instance or
rule.
A security role is used by application servers to
control access to servlets. For example, the
security role
PegaDiagnosticUser security role provides access to
the System Management Application.
In Decision Management, a segment is a group of
customers de ned by predicted behavior, score and
characteristics. Segmentation components in a
segment
strategy drive the decision ow by placing a
customer in a given segment for which actions
and/or results are de ned.
A Senior System Architect (SSA) is someone who has
taken additional training, and understands
Senior System Architect (SSA)
advanced technical concepts such as class structure,
inheritance, and rule resolution.
A sequence diagram is an interaction diagram that is
organized according to the time and details of how
sequence diagram
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
servcie package service rule types, a service package corresponds to
a package of Java classes. Service packages are
instances of the Data-Admin-ServicePackage class,
and comprise the rst key part of most service rules.
service A service is a programmatic component that de nes
and implements an interface between an external
10/2/2020 Take Lesson TL-36945031
application acting as a client and a 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
Service Accelerator SOAP, JSR94, .Net, JMS, 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
service activity BATCH requestor type to perform background
processing, and returns the results to the client or
calling external system.
The ServiceExport directory is a subdirectory of the
ServiceExport directory
temporary les directory on the server.
A service invocation is a call from an external system
service invocation to run a Rule-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
de ne 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 de ned as
part of the case. A service level for an assignment is
de ned with a service level rule.
A service-level agreement de nes intervals of time,
such as a goal and deadline, that are used to
Service Level Agreement (SLA) standardize how you resolve work in your
application. You can apply a service-level agreement
to cases, stages, steps, ows, and assignments.
A service level rule is used to de ne the time interval
required to complete an assignment. It includes one
or two time intervals, known as goals and deadlines,
service level (rule)
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 package service rule types, a service package corresponds to
a package of Java classes. Service packages are
instances of the Data-Admin-ServicePackage class,
and comprise the rst key part of most service rules.
In Customer Service, a service process is a work ow
that starts within an interaction, creates a case, and
then guides the user through a process to address
service process 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 Accelerator In Customer Service, a Service Process Accelerator is
a wizard that automates the creation of service
10/2/2020 Take Lesson TL-36945031
processes.
In Customer Service, a service request is a case or
request to perform a task, usually on behalf of a
service request
customer. A service request is processed using a
service process.
The Setup wizard prepares the environment for
application development by con guring the
prerequisite elements for logging on to Pega and
Setup wizard 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
shared ruleset that each operate on a common, top-level page of a
single class (or of subclasses of that class).
A shortcut rule de nes report shortcuts, which are
an e cient way to view, run, and share reports
based on report categories. Report shortcuts are
shortcut (rule)
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 key. Two rule instances are siblings
sibling rule
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 to exchange information in a
Simple Object Access Protocol (SOAP)
decentralized, distributed environment. See SOAP
Services.
A simulation is the representation of the behavior or
characteristics of a system, through use of another
system. Simulation allows an application developer
simulation
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 ow rule that
contains a single assignment. When previewing a
Single Step Assignment
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
single value lower-level elements such as an integer, decimal or
true/false.
A Single Value property, or scalar property, contains
a single text string. Text, numbers, dates, Boolean
single value property
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
situational layer cake the right time. Each layer specializes on a di erent
dynamic variable, such as customer attributes;
country or region; product or line of business.
Sizing tool The Sizing tool is an Excel spreadsheet used to
10/2/2020 Take Lesson TL-36945031
estimate the duration 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
skill pro ciency value for a speci c 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 rules. The
skimming 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 de nes the responsive behavior and
formatting, such as colors, fonts, images, and layout,
skin 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 speci c elements in a report or
SmartInfo 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, styles, and
Smart Layout 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
SmartPrompt selections, providing faster and more accurate data
entry. SmartPrompts are identi ed by a small blue
triangle in the lower right corner of the eld.
A Smart Shape is a standard ow shape pre-
Smart Shape con gured to perform a speci c task, such as
sending an email.
A smoke test is a type of software testing in which
an application is tested to ensure a minimum level
smoke test
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
SnapStart without a user log-in process. SnapStart sends a
user ID and password within the URL and uses
Pega's authentication.
Social Intercept No longer being used. See Social Engagement
solution framework A solution framework is an industry-speci c starter
application that provides a head start to application
development for speci c industries or lines of
business. The applications are limited in scope, built
on top of Pega, and designed for use in the
10/2/2020 Take Lesson TL-36945031
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 small, you can
spark chart 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 de nition report
by using the Chart Editor.
A speci cation represents a unit of processing that is
performed by one or more actors for a given case
type within an application. In other words, a
speci cation
speci cation de nes what an application does. One
or more requirements de ne the criteria for the
successful implementation of a speci cation.
A high-level scoping document that can be produced
for an application, using the Document wizard. A
Speci cation document consists of a set of related
Speci cation document
speci cations - sometimes referred to as a
speci cation set - produced in advance of a DCO
session for review by an implementation team.
A spin-o ow is a process that runs in parallel with
the calling process, or parent ow. Spin-o ows can
Spin-o work on the same case as the parent ow or they
can work on a di erent case, based on the context
that you provide.
A Split for Each shape in a ow diagram enabling
synchronous operations use to send a case through
another ow based on information in the pages of a
Split for Each Page List or Page Group property. When these
sub ows complete, the original ow continues. In
some programming environments, this is called
enumeration or iteration.
A Split Join shape in a ow diagram causes
processing of a case to split into two or more
independent subprocesses to rejoin and be
Split Join
completed before the current ow continues
execution. This allows subprocesses to execute
asynchronously, in parallel.
Split schema is a database con guration in which
Split-Schema
rules are in a separate schema from work and data.
A sprint is a time boxed period in which the project
team implements and delivers a set of stories and
sprint
bug xes. 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
SQL function alias reference an SQL function alias rule in a report
de nition rule to de ne SQL expressions for
querying a database for reporting.
A tool that provides a guided interface to help users
SQL Function Builder construct SQL functions for use in Report De nition
rules.
Stage A stage is the rst level of organizing work in your
10/2/2020 Take Lesson TL-36945031
case type. It contains the work ows, 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
in uences the development of an application.
stakeholder Project stakeholders provide the funds or resources
for the project. Business stakeholders determine
and evaluate the functionality of the solutions.
standard queue processor Pega Platform default queue processor rules.
Standard rules are those rules provided with the
Pega Platform. You can use standard rules as-is, or
standard rules
you can copy them into your application and modify
them.
A starter ow is a ow that supports the creation of
starter ow a case. Starter ows are also called starting
processes.
In Customer Service, a starting work ow activity
Starting work ow activity
used by you application to start a service process.
The static assembler is a utility that you use to
static assembler
preassemble and cache the rules of an application.
Static content is information that is extracted once
from a rule to an HTTP server or web server and is
static content
una ected by user input, such as the use of an
application or the contents of user clipboards.
In Decision Management, statistical signi cance is
statistical signi cance the degree to which 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
step be represented as numbered rows on a 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 activity could
step page
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
Storage Stream compressed format. Most tables in the database
contain a Storage Stream column, identi ed as the
pzPVStream column.
Straight-through processing is automatic processing
that occurs without operator intervention. Straight-
straight-through processing (STP)
through processing is implemented by using a ow
rule that does not contain any assignments.
strategy In Decision Management, a strategy is the reasoning
built up by a set of components that enables
business strategy de nition and provides the
decision support to manage an interaction in the
context of a decision hierarchy. A strategy can
import data and propositions and reference other
decision rules (scorecards, predictive models,
10/2/2020 Take Lesson TL-36945031
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 nal form that
stream processing 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 development and enhance productivity.
studios
Studios include, App Studio, Dev Studio, Admin
Studio and Prediction Studio.
A sub-feature de nes a capability that extends
another capability. For example, dynamic UI is a sub-
Sub-feature
feature of user interface because dynamic UI is a
capability of the user interface feature.
A subprocess, also called a sub ow, is a ow that is
called by another ow. Subprocesses are
represented by the Subprocess, Split Join, or Split
Sub ow (subprocess)
For Each shape in a ow diagram. Use Case Designer
or Process Modeler to con gure a subprocess in a
ow.
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
sub-report
have its own subreports. You can designate
subreports within report de nition 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,
subscription or an event. Noti cations are sent to subscribers by
using an RSS feed, an email, or a notice on a
dashboard.
A summary view rule de nes 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-create the
summary view rule
custom summary view reports that you need as
report de nitions. 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 surveys. Access the Survey Builder from
Survey Builder
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
suspended case detected. All of the ow executions in process for
the suspended case are stopped, and the value for
the property Work-.pxSuspended changes to true.
Swimlane (shape) A swimlane is a shape that organizes and graphically
10/2/2020 Take Lesson TL-36945031
identi es a related group of shapes that are

performed within a speci c work context, typically a
work group.
A symbolic date is a system-derived date value that
is used in the selection criteria of reports to choose
symbolic date 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
System- concrete classes that hold real-time status
information about the server software as it runs.
A system administrator is responsible for system
System Administrator installation and setup, security and access, and
other operational functions.
A system architect is an application developer who
contributes object-oriented design and technical
System Architect (SA)
implementation skills to an application development
project.
A System- base class is a standard, top-level abstract
class that contains concrete subclasses that hold
System- base class
real-time status information about the server
software as it runs.
The system ID, or system name, identi es your Pega
7 Platform system, which includes all instances
system ID (nodes) that share a single database and the same
system name. The system ID is stored in a System
data instance record (Data-Admin-System class).
The System Management Application (SMA) is a web
application distributed with the Pega 7 Platform that
System Management Application enables system administrators and developers to
monitor and manage the resources and processes
of Pega 7 Platform applications.
The system of record (SOR) de nes the original
source of data, ideally the only source of the truth.
System of record (SOR)
The system of record de nes the logical and physical
database tables that your application requires.
Used by a queue processor or job schedular to
System Runtime Context gure out the privileges and permissions available
when processing a queued or scheduled task.
A tag is a text value that case workers and case
managers can associate with one or more cases.
tag They can select from a list of available tags or create
new tags. Case managers can search, access, and
report on tagged cases.
talk o Talk o 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 ling the claim or dispute. For example,
a customer says, ""I don't recognize this transaction;
it must be fraud."" 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 ectively talked o the
10/2/2020 Take Lesson TL-36945031
dispute, so the dispute is resolved-talk o , and no

other action is required.
A target property is a property for which a value is to
target property be set, by either 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 ow diagram. Tasks are
typically created for a story during or after sprint
task
planning. 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
Technical (category) including familiarity with Java, HTML, XML, 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. You can use
temporary case temporary cases in screen ows and regular ows.
To create a temporary case, select the Creates
temporary object? check box on the ow that
creates the object.
A tenant is a secure region of a Pega 7 Platform
multitenant system. A tenant shares a single
database, rulesets, and code that support the Pega 7
tenant Platform operations of the other tenants in the
system. Tenant-speci c 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,
Tenant Administrator primarily the creation and maintenance of 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 deployments on
behalf of the tenant, or more generally, performs
Tenant Proxy Administrator
any function that requires or involves elevated
privileges and tenant-quali ed 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 Platform applications. To generate
Test ID
Test IDs, con gure the Test ID eld on the General
tab of the Dynamic Layout property panel.
The Test Management Framework (TMF) is an
optional application that implements best practices
Test Management Framework
for the testing and deployment of new applications
and incremental changes to existing applications.
text le (rule) A text le rule stores static HTML, XML, Cascading
10/2/2020 Take Lesson TL-36945031
Style Sheet, DHTML and JavaScript script les used in

an application, to provide the security, inheritance
versioning and deployment bene ts of rule
resolution for a le.
Themes allow users to change the appearance of
their Customer Service display on PRPC 6 systems.
Theme Several standard themes are 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
thread a requestor to 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
threshold manage threshold settings and specify whether
alerts display by updating the prcon g.xml le, or by
using Dynamic System Settings.
Throughput is a measure of work accomplished or
throughput
completed during a calendar interval.
A ticket is a named location that you add to a ow
diagram by using Process Modeler. Tickets identify
ticket processing, such as a transaction rollback, that
occurs when the normal ow progression is
interrupted for a case.
A time-quali ed rule is a circumstance that is only
rule resolved during a speci ed range of time. This
time-quali ed rule
type of rule is commonly referred to as a date range
circumstance or temporary rule.
To enable or disable "risky" functionality that is still
under development during continuous integration.
Toggles Toggles use conditional when rules that can be used
to control access to a feature that is not fully
developed.
A topic is an abstraction of the intent or subject that
topic
is returned from 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
top-level case type parent. 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
top-level class
of the ultimate base class, @baseclass.
A top-level page is a clipboard page that is usually
created through the Page-New method. Applications
create many top-level pages during the course of
top-level page
operations, and activities can create top-level pages.
Most top-level pages are named, and have an
associated class.
Tracer tool The Tracer tool is a feature that you can use to
debug ows, data transforms, activities, services,
10/2/2020 Take Lesson TL-36945031
parse rules, and declarative rules. The Tracer tool

provides full debugging facilities, including step-by-
step execution, breakpoints, and watch variables.
Traditional portals have a xed layout and are built
from HTML rules with Data-Gadget as the Applies To
key part. Traditional portals are referred to as
traditional portal ""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
transfer workbasket by a user or 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 PegaRULES database, the values are
transient property
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-
transition Obj-When rule 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 identi es key roles and responsibilities for
transition readiness plan
maintaining a newly deployed application and
provides necessary supporting documentation.
In Decision Management, treatment of predictors is
a statistical term that indicates the way a property,
treatment of predictors
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 report de nition. The tree grid is
Tree Grid layout
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
Tree layout
branch of the tree corresponds to a single
embedded page or property. The tree is created
dynamically and can have as many branches as
needed to display the requested data.
trend detection In Decision Management, trend detection is the
ability to identify patterns by comparing the
10/2/2020 Take Lesson TL-36945031
performance of multiple models that are triggered

by the same proposition and con gured with
di erent performance window sizes. The ability to
calculate performance for a number of cases during
the speci ed timeframe using a combination of
strategy design patterns and compatible adaptive
model rules with di erent 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,
trend report
or quarters in a year, or some other meaningful
increment. One column of the data that supports
the trend report displays one or more single value
properties of a DateTime type.
A trigger is the event or method that starts the
trigger processing of a speci ed action in response to
another event or method.
A trigger rule identi es an activity that runs
automatically when an object of a speci c class is
trigger rule saved or deleted in the PegaRULES database. This
rule is an instance of the Rule-Declare-Trigger rule
type.
The UI Gallery is a collection of examples of e ective
and dynamic forms and layouts that use many of
Pega's design capabilities, represent best practice
UI Gallery
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 con gured to indicate UI
UI Inspector (Rules Inspector)
rules, properties, declaratively set property values,
and eld values. In versions of PRPC prior to 7.1, the
UI Inspector was known as the Rules Inspector.
The ultimate base class, identi ed by the symbol
@baseclass, is the topmost class in the class
hierarchy. All other classes are derived from this
ultimate base class 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 hot xes are installed in your system
and are active; however, you can still remove them.
uncommitted hot x You can use uncommitted hot xes 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 structure a ects
unit
management reports and statistics, and the ruleset
visible to users in that organization when they log in.
See division and organization.
unit test A unit test is a form of testing performed on an
10/2/2020 Take Lesson TL-36945031
individual rule during testing. Unit testing veri es

that the rule works as intended, without involving
other rules in the testing.
In Decision Management, a univariate model is the
univariate model
result of a quantitative analysis of just one variable.
An unoptimized property is an aggregate property, a
property within an embedded page, or a Single
unoptimized property
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 interface in the HTML5 document
Update Controls 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
urgency and case details. The higher the urgency, the more
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 instance
usage daemon
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 de nition reports in the
current application. Several standard usage reports
usage report
are provided, or you can create your own usage
reports. You can run usage reports from the Report
Usage landing page.
use case See speci cation.
A duse case iagram describes what a system does
use case diagram from the standpoint 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 usability of the
user acceptance testing (UAT)
application. UAT is focused on using an application
in realistic scenarios to ensure that the application
behaves in accordance with its requirements.
A term used in Pega Express to describe ow actions
user action
that are 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 (such as a Pega
user agent string
application.) A Pega Mobile uses a browsers user
agent string to identify whether a user is on a mobile
or desktop platform.
User Experience (UX) A User Experience is a person's perceptions and
10/2/2020 Take Lesson TL-36945031
responses that result from the use or anticipated

use of a product, system or service. User 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-visible forms, through
user interface (category) which end users interact with an application. The
User Interface category includes control, ow action,
harness, paragraph, portal, section, and skin rules.
A user interface (UI )is the portion of an application
responsible for the presentation of information and
user interface (UI)
functionality to an end user, to facilitate the e ective
control of the application by the end user.
A user page is a top-level clipboard page created by
user page an activity. It appears under the User Pages section
in the Clipboard tool.
A user reference is a type of eld that you con gure
user reference on a form. At run time, it displays a list of existing
users in your application.
A term used in Pega Express to describe access
user role
control in an 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 should be small
user story 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 ow diagram calls an activity rule.
The activity rule speci es the automated processing
utility (shape)
to be performed which updates a case, without any
user interaction or input.
An utterance is text or speech that can be
utterance categorized to a topic for conversation or training
purposes.
Validate is a way to check property values against
one or more expected values, and return an error
validate
message if the property value does not match the
expected value.
A validate rule is used to restrict user inputs by
validate (rule) comparing the entered properties with a set of
conditions.
A Value Group property acts as a container for an
Value Group unordered list of values of di erent types. It can
contain an unlimited number of values.
A Value List property acts as a container for an
Value List ordered list of text values. It can contain an
unlimited number of values.
In PMF, velocity is a metric that predicts how much
velocity work, calibrated in story points, a project team can
successfully complete within a sprint.
verbalization A verbalization is a structured, English text
10/2/2020 Take Lesson TL-36945031
description of an activity. The system can generate a

verbalization le (in HTML format) for any activity.
The le is a useful form of documentation for the
activity.
A veri cation in a work ow is an independent review
by one person of some part of another's work (and
of the system's work) before it becomes nal.
veri cation
Veri cations are common in nancial work ows
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 signi cantly changes the
requirements for issuers to le and acquirers to
respond to cardholder disputes and fraud claims.
The new program requires a real time interface
Visa Claims Resolution
between the issuer and the Visa Resolve Online
(VROL) system, and between acquirers and the VROL
system, so that they can improve the e ciency 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-o ce exception
Visa Resolve Online processing. The 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 de ned in the ultimate base class and is
visible key
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 by
Visual Business Director (VBD)
analyzing the impact of strategy changes on key
business goals such as customer experience,
productivity, revenue generation and risk.
.war A Web Application ARchive (.war) le is a
compressed le format used to distribute a
collection of JAR- les, JavaServer Pages, Java Servlets,
Java classes, XML les, tag libraries, static web pages
10/2/2020 Take Lesson TL-36945031
(HTML and related les) and other resources that

together constitute a web application.
A web node is a server that hosts the Pega 7
Platform part of a composite application. A web
web node
node has web as the value of the nodetype entry in
the prcon g.xml le or in Dynamic System Settings.
A Web service is a service that uses SOAP protocol to
Web service
transmit XML-formatted messages.
Web Services Description Language (WSDL) is an
XML format de ned by the World Wide Web
Consortium (W3C). Each WSDL le describes
Web Services Description Language (WSDL) network services as a set of endpoints operating on
messages containing either document-oriented or
procedure-oriented information. Pega uses WSDL
les when integrating with web services.
A when condition rule de nes a true-false test based
when condition on comparing one or more property values with
constant values or with other property values.
A when rule is a decision rule that de nes a true-
false test based on comparing one or more property
values with constant values or with other property
when (rule)
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
Where-Am-I? current location of in ight 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 di erences in those pages or properties
white list
cause the test case to fail. Di erences 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
wireframe interface that speci es the key elements required in
the nal user interface.
A wizard include a series of prompts to help
wizards
accomplish a task with minimal e ort.
The abstract parent class for any case type. Used as
the starting point for the work-related classes in a
Work- 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 de ne work items. A work item is the
Work- base class
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
workbasket queue. To view the workbaskets in your application,
open the Designer Studio > Process & Rules > Work
Management > Workbaskets landing page.
workers A worker is a role that de nes the behavior and
responsibilities of an individual or a group of
10/2/2020 Take Lesson TL-36945031
individuals working together as a team. The

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 work ow is a standard set of steps that resolve a
work ow case; a sequence of activities that produces a result
of observable value.
A work group identi es a user who is a supervisor
and a set of workers and workbaskets that report to
that supervisor. A work group is an instance of the
work group
Data-Admin-WorkGroup class. The Operator ID data
instance (Data-Admin-Operator-ID class) usually
identi es 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 speci c operator. You can use your
worklist
worklist to view the ID, status, and relevant
instructions for each item.
A Work Manager is a traditional (compared to
Composite) portal that is used by managers and
WorkManager
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 email, and can be
work party an active or passive participant based on its role.
Work parties are added to a case as it is processed.
You can list and con gure 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
work pool parent Work- and Work-Cover- classes for these
work items and cases are speci ed in the user's
access group.
A work pool name is a short description for a class
work pool naem
group that is a collection of work types.
A work pool name is a short description for a class
work pool name
group that is a collection of work types.
A work queue is a list of work in your application
that is shared by operators with the same user role.
work queue
A work queue is sometimes referred to as a
workbasket.
Work status is a property value that de nes whether
the case is open or resolved and the primary
work status
indicator of the progress of the case towards
resolution.
workstream A workstream is a collection of speci cations 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, iterating the speci cations and
requirements as needed and producing draft ows
10/2/2020 Take Lesson TL-36945031
and draft UI for review. Also referred to as a

speci cation set.
A work type is a concrete class derived from the
work type Work- base class. Work types derived from the
Work-Cover- base class are referred to as case types
A write-o 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 o instead of processing the dispute,
write-o because the cost of disputing may be more
expensive than the amount of the transaction loss.
Transactions may also be written o 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
Z-ratio account errors by allowing for statistical signi cance.
The Z-ratio is positive when expected behavior is
above the average behavior and negative when
expected behavior is below the average behavior.

Definition

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Definition

Uploaded by

Copyright:

Available Formats

10/2/2020 Take Lesson TL-36945031

Pega Academy Glossary

An abstract class supports the de nition of rules,

activity loop An activity loop is a step in an activity that can run

single value, such as a Value List, Page List, Value

requirements. You can create an application

be imported by the Application Accelerator to create

rulesets de ned for any built-on application and the

types are supported: File, Note, Screenshot, Scanned

copies of pages developed by a Data Page rule. To

a report de nition report by using the Chart Editor.

the other is a category. The horizontal and vertical

scheduled work days for users. Business days are

and a large number of industry interfacing

your application. To access Case Designer, open the

type has a hierarchical structure and can include

acknowledges the acquisition of foundation-level

application allows you to easily support a variety of

reverse if a set of scores orders negative cases

compliance case may be initiated by the acquirer. A

an assignment shape represent ow actions. Other

whom the user is interacting. A contact can be a

control A control rule used to dictates how properties

password. The user name is the key to an Operator

automatically. The Pega Platform includes the

data. Data pages were previously known as

con guration to a system of record, separating your

decision (shape) A decision shape within a ow diagram that calls a

multiple properties for the same class in a single

diagnostic processes may be used to suggest the

level. Divisions are referenced in Organization Units

upgrade Dynamic Select controls to Dropdown

that, by design, are never to be used as top-level

Epic An epic is a large user story that can be broken

parameters to functions in a natural language

favorite A favorite is a link to a rule or data instance. Use a

ow A ow models a business process in your application

decision table, decision tree, or map value rule

function A function de nes a Java function and makes the

resolution time for an item, such as a case or stage.

production eld information, in-house metrics, and

instance. The history type is recorded as a single

an index is a PegaRULES database feature that

the Process Modeler use the integrator shape. The

Interaction Timer In Customer Service, an Interaction Timer is a gadget

actions on any given list. The Split For Each shape in

named pegarules.keyring. If your application server

speci cation) that is the result of a DCO session. In

of Internet Explorer that list view rules support is

ruleset versions, an instance of a concrete class, and

for issuers to le chargebacks on behalf of their

preview from the operator menu in the Case

logically partitioned into multiple heterogeneous

non-functional requirement A non-functional requirement places constraints on

other identifying information for an application user.

levels with organizations at the top level, divisions at

Page Group An embedded unordered array of pages. See also

patch version would be 03.

Pega's CRM Suite, Pega Customer Service can help

fast customer eperiences via social channels such as

persisent object A persistent object is an object instance that was

prcon g settings have a default value. If no other

are developed in the Predictive Analytics Director

test the appearance or execution of the rule. Using