Glossary V62 SP2

 Copyright 2012
Pegasystems Inc., Cambridge, MA

All rights reserved.
This document describes products and services of Pegasystems Inc. It may contain trade
secrets and proprietary information. The document and product are protected by copyright and
distributed under licenses restricting their use, copying, distribution or transmittal in any form
without prior written authorization of Pegasystems Inc.
This document is current as of the date of publication only. Changes in the document may be
made from time to time at the discretion of Pegasystems. This document remains the property
of Pegasystems and must be returned to it upon request. This document does not imply any
commitment to offer or deliver the products or services provided.
This document may include references to Pegasystems product features that have not been
licensed by your company. If you have questions about whether a particular capability is
included in your installation, please consult your Pegasystems service consultant.
For Pegasystems trademarks and registered trademarks, all rights are reserved. Other brand
or product names are trademarks of their respective holders.
Although Pegasystems Inc. strives for accuracy in its publications, any publication may contain
inaccuracies or typographical errors. This document or Help System could contain technical
inaccuracies or typographical errors. Changes are periodically added to the information herein.
Pegasystems Inc. may make improvements and/or changes in the information described
herein at any time.
This document is the property of:

Pegasystems Inc.
101 Main Street
Cambridge, MA 02142-1590
Phone: (617) 374-9600

Fax: (617) 374-9620
www.pega.com
PRPC
Glossary of Terms
Updated: 10-Jul-12
ID: GLS62V2
Glossary of Terms
This document provides definitions for terms used in PRPC, Decision
Strategy Manager and Customer Relationship Management (CRM) in
courses and documents.
Glossary of Terms 2
A
@baseclass See ultimate baseclass.
abstract class A class that cannot be used to create any work items. It is used to collect
rules for re-use that can be shared by one or more work types and to
support the class hierarchy. Rules that apply to an abstract class are
inherited by its subclasses. Whether a new class is abstract or concrete
depends upon a selection on the Class rule form. Abstract class names
usually end with a hyphen (-), for example, Work-Cover-. Compare with
concrete class.
access group A group to which a user belongs that determines their available applications,
the layout of their home page and their assigned roles. System
administrators define access groups and associate them with users.
access role A user role assigned to an access group that enables us to limit the access
to rules based on what the access group members do for their jobs or on a
project implementation team.
account A representation of the relationship between a customer and an
organization.
account owner The customer that holds the agreement (account) with an organization such
as an individual or business unit.
action Also known as a flow action. A name for one of the available choices
presented to a user in the workflow (process) that are available to process
their assignment.
action section The area in a work item form where users select which action to take on the
current work item. This section can display its choices as a menu, or as a
series of links, emphasizing the most likely option or as a set of buttons.
activity A task that an individual is asked to perform. Also, an advanced rule that is
used to define a procedure consisting of a series of automated, logical steps
to manipulate data. An activity is called by another rule, such as a flow
action, a flow (by using the Utility shape) or a declare page.
Glossary of Terms 3
Adaptive Analytics The main process of the Adaptive Decision Manager, responsible for storing
Engine and analyzing adaptive statistics, and producing individual scoring models
that are used in PRPC to perform calculations used for predictions defined in
decision strategies. .
Adaptive Data The database scoring adaptive statistics and adaptive models.
Store
Adaptive Decision An integrated method that extends predictive analytics with an adaptive
Manager mechanism to establish customer preferences with customer responses in
real time. Due to its adaptive nature, no initial collection of data is necessary.
adaptive model Scoring models in Adaptive Decision Management (ADM) that use rules to
define the settings that influence the behavior of the adaptive models. They
output predictions in real time and adapt these after executing a strategy as
responses are captured (self-learning). They are typically used in the
absence of historical records to make predictions.
adaptive statistics The persistent information that results from running a strategy that contains
adaptive models.
agent A background process that monitors conditions and performs processing as

necessary. Agents run activities periodically at a set interval or time as an
internal thread on the server. Agents work according to the rules in an
application and also perform system tasks such as sending email or
generating updated indexes for the full-text search feature. PRPC includes
nine standard agents.
In a contact center, agents are representatives of an organization that serve
customers. Agents may interact with customers over several channels
including the telephone, e-mail and text chat.
aggregate A property that has a mode other than single value, such as Value List, Page
property List, Value Group, 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.
Glossary of Terms 4
AJAX Asynchronous JavaScript and XML – Coding technique used for creating
interactive web applications by exchanging small amounts of data behind the
scenes so that an entire web page does not reload each time users request
a change. PRPC uses this technology when processing server-side
validation rules and for calculated value expressions.
Application A PRPC wizard that uses information provided to it via an Application Profile
Accelerator (or directly into the Application Accelerator) to automatically create a working
baseline application foundation. This application includes organization and
class structure, draft processes and UI elements. This baseline application is
based on best practices for application design). Leveraging data captured in an
application A collection of rules and data developed in PRPC to support a specific
business function. A working baseline application that is created by running
the Application Accelerator.
Application A wizard that supports the generation of Microsoft Word documents that
Document wizard describe the application, including specifications, requirements and actors.
Because this documentation can be generated directly from the rules at any
time, it can be up-to-date and "in sync" with the actual implementation.
Application Navigation feature that is organized by class, category and rule type and
Explorer provides access to the rules in a selected work pool.
Application A tool used to quickly create and prototype your business processes, case
Express design and user interfaces in a working starter application designed for
experimentation, demonstration and learning. The class structure of this
application is not suitable for the reuse features that facilitate enterprise-
wide use.
application menu A menu in the Designer Studio that provides the ability to switch
applications, create a new application or switch work pools.
Application A wizard used to create a product rule or an archive containing all the
Packaging wizard classes, rules and data that make up an application that can be exported to
a ZIP file and imported or migrated to another PRPC system.
Glossary of Terms 5
Application Profile A work item which captures information about an application that is about to
be built, such as work types, specifications, etc. This work item is processed
by the Application Accelerator to create an application stub (baseline
application or application starting point), which can be modified by adding
rules to implement functionality and create a function, production application.
Application Profile speeds the creation of new applications and the
extension of existing applications.
Application Profile A high-level scoping document that is produced as a result of running the
Document Application Profile wizard. This document contains application-specific user
input that includes, but is not limited to, work types, specifications,
requirements, objectives, interfaces, reports and correspondence.
application rule Specifies an ordered set of multiple RuleSets and RuleSet versions that
together identify the components of a PRPC application and are available to
members of the access group. It includes objectives, actors, work types,
specifications, requirements. It also provides security and allows the
attachment of supporting documentation (screenshots, etc.).
Application A collection of RuleSets (not a collection of RuleSet versions) that represent
RuleSet our application. It determines which rules display in the Application Explorer,
Profile Explorer, Guardrails tool and Document wizard. A RuleSet that appears
on the General tab of the application rule referenced in the access group for a
requestor (when the current work pool is part of this application), (recursively)
on the General tab of a 'parent' application rule, if the Include Parent checkbox
on the General tab of a 'child' application is checked, or in the Local
Customization field on the Settings tab of the access group.
Applies To class See primary page.
Glossary of Terms 6
assignment A record that indicates that a work item that was progressing through an
executing flow is temporarily paused, waiting for a human user.
The user must display the work item, determine what action to do next, and
complete (“perform”) the assignment by entering his or her decisions and other
inputs.
Completing the assignment causes the record to be deleted. Note that one
piece of work – one work item – may have two or more assignments
outstanding at the same time.
Assignment shape A PRPC shape that represents a pause or potential pause of the work item
in a flow so that a person or system must act on that work item before the
flow can progress. An assignment shape creates an assignment either on
an operator's worklist or in a shared work basket.
association A rule type that predefines a JOIN-type relationship between instances of
two classes, such as operators and assignments or between work items 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 is building a report. PRPC provides more than
20 standard association rules that define commonly used relationships.
attachment Attachments are associated with work items and the attachment category
category identifies the business process or purpose of the attachment. Examples
include check photo copy, HR document or expense report. Developers can
restrict a user's ability to add, delete, view and edit attachments based on
privileges, when conditions or attachment types. One of three groupings used
on the Application Explorer and Rules by Type Explorer.
audit trail A feature that displays the history of a work item, including which operators
have worked on it and when, what automatic processes were performed by
the application, and other details. This information is added automatically at
runtime or added as a result of values selected for the Audit Note field of
flow shapes when editing the flow rule.
Glossary of Terms 7
authentication The process of determining the identity of a user or requestor of services. In

PRPC, authentication is accomplished by matching the submitted user name
and password to those stored in the user’s Operator ID instance. A
requestor or user who is not authenticated is known as a guest.
auto-complete A field on a form that supports user selection of one text value from a large
field list of candidate values. After the user types one or a few characters, a
filtered list of qualifying text values appears below the input field. Users can
then select a value from the drop-down list.
auto-generated When a rule form is saved, PRPC translates some types of rules (such as
rules control, section, flow action and harness rules) to HTML, JSP tags and
JavaScript. These autogenerated rules eliminate hand-coding and usually
provide better performance, security, browser independence and more
consistent branding and styles than hand-crafted rules.
Automatic Call The equipment (or software) used to direct incoming calls to service
Distributor (ACD) representatives in a call or contact center.
Autonomic Event An optional product that automatically monitors, retrieves organizes and
Services (AES) displays PRPC system statistics and warning conditions at the enterprise,
cluster and node levels. A dashboard displays real-time, critical performance-
related data including the number of requestors and agents running,
percentage of memory used, CPU usage and so on, so that an operator can
quickly remediate and resolve issues. AES also provides reports, charts and
diagnostic information about the events that triggered the alerts.
availability The status of a rule, which determines if the rule can be used when called
during rule resolution. PRPC provides five possible values: Yes, No/Draft
Mode, Blocked, Final and Withdrawn.
B
background Automatic processing that occurs without user intervention.
processing
Glossary of Terms 8
backward chaining The status of a rule, which determines if the rule can be used when called
during rule resolution. PRPC provides five possible values: Yes, No/Draft
Mode, Blocked, Final and Withdrawn.
An advanced technique that allows eviction of a declarative expression to
advance even when the value of an input or parameter property is not
available. PRPC also uses the internal dependency network of property
relationships to develop inferences about how to obtain the missing property
value.
These computations are sometimes called goal-seeking, since the system
reaches a final goal (finding a value for property X) by completing other
goals (finding a value for properties that allow X to be computed).
base class One of PRPC’s standard abstract classes that are immediately below the top
class in the class hierarchy. All instances of classes inherit either directly or
through pattern inheritance from base classes The top class, known as the
ultimate base class, is the highest level class available in the class structure
hierarchy and is identified by the symbol @baseclass. The four base classes
of greatest interest to application developers are Data-, Assign-, Rule- and
Work-.
base rule A rule that supports a circumstance-qualified rule or time-qualified rule is the
fallback rule that is selected by rule resolution when the circumstances or
time-period is not met. A base rule must exist for every qualified rule.
behavioral profile A representation of a univariate model that is based upon a single behavior
variable, like usage or loyalty.
best bet Indicates a subset of options which are likely to have the choice you are
seeking. In the Application Explorer, a Best Bet is one of the classes in your
application. The Application Explorer display shows the tree of rules for only
one of these classes. An Auto Complete rule form can be configured so that
the top of the drop-down list (under the heading BestBets) displays the
results that application users select most often.
Glossary of Terms 9
BLOB (Binary A database field that stores all of the data for a case or work item in a
Large Object) proprietary, compressed format that is highly optimized for performance and
flexibility. A BLOB field can hold any amount of digitized information, and
supports text, images, audio or video. Also known simply as a "large object".
A rule instance is blocked if its Availability value is set to Blocked. When rule
blocked
resolution selects a rule that is blocked, that rule and all others (same name or
key, any RuleSet) are not executable.
BPM See Business Process Management.
BPMN A specification promoted by the Business Process Management Initiative of
the Object Management Group, that provides a graphical notation for
expressing business processes in a business process diagram. The BPMN
specification also defines the relationships between the graphical elements
and process execution languages such as BPEL.
branch RuleSet A RuleSet that is s based off of or "branched from" another RuleSet and
contains rules that are in active development in the associated branch. By
using branches, rule development can take place within an isolated space
(the branch) without affecting functionality in the source rules.
BRE See Business Rules Engine.
build order This specifies the sequence in which rules and data instances are created
when earlier phases are complete. The build order may differ in separate
iterations of the implementation.
bulk processing Allows users of the manager portal to repeatedly perform one action, such
as accept or reject numerous purchase orders, on multiple assignments in
an application.
Business Architect A business user or business analyst who defines and maintains business
rules, service levels and flows (processes).
Business Architect A portal that is an alternative to the full Designer Studio ad that provides
portal access to those PRPC facilities most useful to Business Architects.
Glossary of Terms 10
Business An optional add-on product that provides the extract functions of an ETL
Intelligence (Extract, Transform and Load) utility and can provide some portion of the
Exchange (BIX) transformation functions from a PRPC database into formats suitable for
export to a consolidated data warehouse.
Business Process The organizational activity that defines how we get work done and
Management coordinates the presentation of our UI, the application of our logic and the
(BPM) accessing of data. It incorporates management practices with information
technology to plan, design, build, operate, control, monitor, analyze and
maintain an organization’s business.
Business Rules The PegaRULES component of PRPC provides a powerful Java-based rules
Engine (BRE) engine that separates business logic from the mission-critical applications
and enables the enterprise to capture, manage and execute business
policies and practices as business rules. The Business Rules Engine or BRE
uses advanced software techniques to compute and record the
consequences and results of rules in a non-procedural, non-programming
form. PRPC supports declarative rules, multithreaded execution and a large
number of industry interfacing and standards.
Business Use A type of use case (specification) that describes a business process from
Case beginning to end without regard to process ownership. It can involve many
different actors and has a very low likelihood of being reused within an
enterprise.
Business Value A stage of the project implementation methodology that defines the success
Assessment factors and expected return on investment of the project. A business
architect has a major role in this stage.
C
cache The collection of data automatically maintained by the PRPC engine in
memory, disk or database, enabling faster access to rules or data stored in
PegaRULES database, especially during rule resolution searches. Multiple
types of cache, representing various types of data, exist in PRPC.
Calculation A display used to select from a number of an existing SQL function as the
Builder basis for the SQL function. The form displays further fields where you select
the data the function is to use.
call center An office or location used by an organization to receive large volumes of
calls from its constituents.
camel case Two words that both start with a capital letter and that have no space
between them, and that form a single word, such as RuleSet, SmartLayout
or PromptSelect. Popular with software developers.
case A collection of tasks or assignments and subcases and the relationships
between them that are completed to resolve an exception. A work class that
inherits from Work–Cover– and contains a case type rule that can cover or
be covered by other case types.
In CPM, a case is a “work item” or “service request”. In decision
management, a case can be any person, company or event that exhibits
some defined behavior. For example, good and bad outcomes.
Case Designer A landing page used to view and modify the case type relationships and
processes comprising a case management application. It displays a
hierarchical tree of case type nodes, indicating the parent /child
(covering/covered) case type relationships and their starting processes for
all case types in the work pools defined in the user's access group. It
populates a tab with information relevant to that case type when a node in
the tree is selected.
case management A structure that involves managing multi-level parent-child relationships so
that a cover work item can nest within other cover work items in a parent-
child hierarchy to centralize flow processing and monitoring among multiple
work types in large applications.
Case management differs from classic BPM work items because it allows
less rigid structure, more flexibility in the order of tasks or which tasks are
needed, and interrelationships with other work.
Case Manager A portal that provides case managers with a standard user interface for
portal creating, viewing, and working on cases; displaying unresolved cases, their
subcases, and the case’s open assignments; displaying associated content,
users, roles, and subjects; monitoring work group status, goals, and deadlines;
and generating work management reports.
case type A rule used to create multi-level, parent-child relationships among work
types that enables nesting of cover objects within other cover objects and
When a case type work item (case) is created, the case is said to be
instantiated.
case type A relationship that controls automatic case instantiation or the completion of
dependency a workbasket assignments (also referred to as a "mid-flow dependency" or
"assignment dependency"). A dependency relationship exists when a
dependent case type automatically instantiates only when one or more other
case type instances (under the same top-level case type and at sibling or
cousin-levels) are created, completed or reach a specified work status.
case worker See operator.
Case Worker A portal that provides case workers with a standard interface for creating,
portal viewing, and working on their own cases and assignments. The user cannot
monitor and manage work among other operators or workbaskets, or view
work statistics.
category Used to group and organize rule types and data forms in the Application
Explorer, My Rules, Rules Explorer, attachments and reports to enhance
navigation.
channel Often refers to a communication channel or mode of interaction – for
example, telephone, email, letters, text chat and in-person interaction at a
branch or office.
check in/check out A rule management process for a RuleSet which allows a rule to be checked
out and edited by only one developer at a time, so that multiple users cannot
overwrite each other’s changes. Other users can access the rule in a read-
only mode. When the rule is checked back in, it is available to be checked
out again.
circumstance A way to create multiple versions or variants of a rule based on a specific

circumstance and automatically executing the correct version of the rule –
either the base rule or overriding the base rule with a qualified version of the
base rule when the circumstance criteria is met.
class A class represents the applicability - or scope - of a rule. A rule defined for a
class can be used by any rule defined for that class or any inherited class.
class diagram A diagram that provides an overview of a system by showing its classes and
the relationships among them.
Class Explorer A navigation feature in the Designer Studio that displays portions of the
class hierarchy differentiating between abstract and concrete classes.
class group Used to store instances of similar or related Work- concrete classes and sub
classes together in a relational database table. Analogous to what users
think of as an application.
Client Event Editor Used to identify a field that dynamically submits elements within a work item
or flow action form and re-renders the display when a user interface event is
performed.
clipboard A temporary, secure, hierarchical memory structure that is allocated on the
server as the user logs in. The clipboard consists of pages that can contain
information about the server, requestors and in-memory processes that are
specific to each user or requestor. A page provides a temporary copy of the
instances from which item they are copied. Each page represents an
individual or aggregated object, and consists of a set of tag-data (or name-
value) pairs. Do not confuse with the Windows operating system clipboard,
which holds only one value.
Clipboard tool A tool that allows developers to examine a static snapshot copy of the
structure and contents (pages and properties) of their own clipboard. They
can troubleshoot issues by viewing and directly updating parts of their
clipboard.
The left panel displays the pages organized as a tree structure. The right
panel lists the properties and values set on one selected page, sorted by
property name.
coaching tips In CPM, coaching tips help improve employee performance and reinforce
best practices. Users with the appropriate privilege can create coaching tips
for any screen that is available in a customer interaction.
coefficient A weight used in CPM for each predictor in the logistic regression formula
that indicates the importance of a predictor. Negative coefficients imply the
presence of predictors with very similar behavioral profile that can lead to
over fitting and unreliable models.
A mathematical term that represents the weight of a variable in an
expression. In the following example “ ”, the coefficient is “ ”.
Coefficient of A non-parametric coefficient that measures how well the scores generated
Concordance by the model separate positive from negative outcome cases using the
(CoC) statistic known as coefficient of concordance. They are sensitive to the
complete range of score bands irrespective 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 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.
Column An advanced utility for database and schema maintenance that uses a
Population utility command-line script to update rows of PegaRULES database tables after
the database schema changes. It can populate values for a new column
corresponding to a newly exposed property, exposing values that are
previously stored only in the Storage Stream (BLOB) column. Optionally, it
can also rebuild database indexes and Index- instances defined by Declare
Index rules as part of the same operation.
Composite portal A user portal defined by a collection of harness rules that each references a
panel set. Each harness rule defines a space — an entire portal window.
concrete class A class that is used to create (instantiate) and can have work items
(instances). Also referred to as work type or work class since it represents a
type of work and creates work items. Compare with abstract class.
Condition Builder An editing tool used to define conditions and ensure that expressions are
valid.
connector An arrow between two shapes in a flow diagram.
Connector rule A rule that allows an application, acting as a client, to interact with an
external system or database.
connector action A flow action that corresponds to steps within a flow, controlling how users
interact with user forms to complete assignments, allowing the flow
execution to progress along a connector arrow to another shape on the
diagram. It also contains sections.
Connector & A tool that imports information about an external application or system and
Metadata wizard configures direct table access without the need for SQL connector rules.
This wizard generates connector rules or data mapping rules and creates a
data class for 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 (i.e. create, read, update, delete).
constraint A rule used to define and enforce a 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 specific condition is met, providing an automatic form of
property validation every time a property value is touched.
If a value entered by a user does deviate from the intended range, a
message is added to the page the property belongs to, invalidating the page.
the process stops and is not allowed to proceed until the user corrects the
entry.
Construction The phase when all remaining components and application features are
Phase developed and integrated into the product and all features are thoroughly
tested. The outcome of this phase is a user-ready product running on the
adequate platforms, with user manuals and a description of the current
release. A large project may have parallel construction activities to
accelerate deployment.
contact The person with whom you are interacting. Contacts can be customers,
prospects, or other interested third parties.
contact center An office or location used by an organization to serve customers over
multiple channels such as telephone, email and text chat.
container A structural element of a work item form that may correspond to a visually
distinct rectangle on the form, marked by a colorful border. Harnesses are
made up of containers, which contain sections. Not every work item form
includes a container.
continuous A typically ordered range of values, for example, the purchase amount,
behavior length of a relationship.
control A rule used to control how properties appear on user forms, correspondence
and other HTML forms, for both display and for accepting user input. Auto-
generated controls are available and are preferred in new development.
correspondence A rule used to define an outgoing e-mail message, printed letter, SMS text or
FAX produced by a PRPC application and its users to notify the work item
originator and. other interested parties about the progress of a work item, to
request needed information or obtain a signature from a person that may or
may not be a PRPC user. Once correspondence is sent, it is permanently
linked to the work item and cannot be deleted once it is saved.
Correspondence A Pegasystems component that supports printing and faxing of
Output Server correspondence external to PRPC.
(COS)
correspondence A rule that is referenced in a flow that provides a template which specifies
template the format, content and type of correspondence.
cover A work item that is also a parent to one or more related work items –
including other cover objects and their children. Typically one work party –
such as the customer party – is present in the cover work item and also
present in all the covered work items associated with it. The covered work
items are the children in a parent-child relationship. A cover may also be a
parent of other cover objects (and their children).
Customer A CPM UI area consisting of individual tabs or sections that display
Composite information about the account, contact and account owner (whether the
owner is a business unit or individual). Information in the customer
composite areas may come from the CPM database or from other third-party
applications and databases within an organization.
CPM Customer Relationship Management. Pegasystems’flagship CRM solution,
built on PRPC’s core BPM capabilities to enable multi-channel, intent-driven
processes for customer service. The processes within an organization that
are used to create, build and manage relationships with prospects, clients or
customers.
Customer Service A person employed by an organization to serve its customers. CSRs may
Representative interact with customers using several channels including the telephone, e-
(CSR) mail, letters and text chat.
Computer A technology that enables applications to interact with telephony systems –
Telephony for example, a desktop application may use CTI to control a user’s telephone
Integration (CTI) and place calls. In call centers, CTI software allows applications to monitor
and act upon calls (e.g. transfer a call).. Using PegaCALL, CPM supports
CTI capabilities such as screen pops and desktop telephony control.
D
Data Explorer A feature that provides a quick way to find a property or calculation with
which to populate a column in the report. It can display the properties that
are most likely to be used in a report organized in a tree structure. It also
allows a user to select an SQL function and identify one or more properties
for it to work with; the result of the calculation can populate a column in the
report.
data instance A concrete class that the system uses internally while it operates. During
installation, instances of classes derived from Data- are created. As the
system is used, other instances are created automatically. For a list of Data-
classes, see Data classes by class name in Developer Help.
data source Data about customers and their previous behavior that can be used for
modeling and strategy design. A source should contain one record per
customer with the same structure for each record.
data table A simple structure typically used to store data from a concrete class in a row
within a separate data table, outside of the application so that the
information can be updated periodically without modifying the application. It
contains only scalar (Single Value) properties and informally, represents an
internal "flat file" that contains no repeating groups.
Data Table wizard A wizard that accelerates the creation of properties in a concrete data class
by generating the class and supporting rules that make the data table an
interactive data entry tool. This enables business users to use the Data
Table Editor.to interactively enter, update and delete database table items
for classes that have a simple structure without added privileges or
programming support. 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. It also optionally
creates a dedicated table in the PegaRULES database and a corresponding
database table data instance.
data transform A rule that is typically used to set default values for properties on a clipboard
page, to copy one clipboard page to another, to map properties from one
page to another, to append properties from one Page List property to
another or to iterate over pages in a Page List property to map data on each
page.
database table A set of related data in a database, organized into rows and columns. Each
column contains a different type of attribute, such as a property, and each
row corresponds to a single record, such as a work item.
DCO See Directly Capture Objectives.
deadline The maximum time interval allowed for resolving a case, configured in a
service level agreement (SLA). When a service level rule is associated with
an assignment, a work item or other instance, the system determines the
start time for a deadline (for that work item) and then adds the deadline
interval to calculate a specific deadline time and date. See goal.
decision The result of running a strategy in the interaction context. Several decisions
can be involved in a single interaction.
decision category One of the groupings under the rule types and data classes category in the
Application Explorer that organizes the four types of decision rules: Decision
Table, Decision Tree, Map Value and When.
decision rule A rule that defines the application of business rules and statements of policy
to PRPC applications and processes in business-friendly, easy-to-use forms
that can be delegated to business managers allowing them to directly
maintain and update their business rules. Performs computations and
comparisons that may cause processing of a flow to continue along one path
or another.
Decision shape A shape within a flow diagram used to call a decision rule such as a decision
tree, decision table or map value.
decision table A decision rule that automates decisions by defining business rules in a
table format, similar to a spreadsheet. A decision table allows a series of
conditions tests or on property values to be evaluated and returns the result
for each outcome.
decision tree A decision rule that automate our business decisions and processes using in
a tree structure format that contains use nested if-then-else logic to define
conditions that we want to evaluate and their return results. The tree’s logic
provides a user-friendly format based on rows of property values,
computations and comparison.
declarative An interactive display of the relationships among properties that are
network computed by Declare Expression rules in the selected application that
depend on forward chaining or backward chaining. See forward chaining and
backward chaining.
declarative A rule that allows developers to model relationships between properties so

expression rule PRPC can process property values automatically or perform an action when
one or more input values are used to determine the value of another
property. Declare rules can be used to determine a property value as the
sum of other property values, or restrict the allowed value of a property
based on the value of another property. PRPC provides six declarative rule
types: Constraints, Declare Expressions, Declare OnChange, Declare
Trigger, Declare Index and Declare Pages. Declare rules do not need to be
called explicitly or run in a sequential fashion.
declare page A rule that creates a page on the clipboard that is available in read-only
mode to multiple requestors in an application. Typically used to store data
that changes infrequently and is needed by more than one user. For
example, a page may contain daily prices for a set of commodities or
currencies, an organization chart or inventory quantity data extracted hourly
(rather than in real time on-demand) from an external system. These pages
can be "globally" available to all requestors on a node.
Define Properties A tool to create one or more property rules with a common Applies To class by
wizard completing a single form. When you need to create several properties, using
the wizard is faster than completing the Property form for each property.
delegated rule A rule that appears for a specific user or access group so those users can
manage these rules outside of the development environment so he or she
can update the leftmost tab of existing rules that may change frequently.
Where the delegated rules appear depends on the portal type used.
dependencies A relationship that exists when one object requires/relies on the functionality
of another object; depicted as dotted arrows between two objects within a
diagram.
dependency An internal data structure that supports forward chaining or automatic

network recalculation of certain property values based on changes to other property
values; a set of rules that share properties.
You can establish required relationships among properties using a Declare
Expression, Constraints or Declare Index rule. Such rules are sometimes
known as declarations.
dependent See case type dependency.
assignment
descendent class Classes that support work items and their attachments, work items that
belong to a folder, links between a top case and descendent sub-cases or
tasks, the association of an application requirement rule with a flow rule or
other rule, the association of a specification rule with an activity, flow or
other rules that support the specification's implementation.
Designer Studio PRPC’s web-based integrated development environment or IDE, used to
build BPM, CRM, decision management and case management applications.
Provides a user interface to users who create rules.
Dialog Script CPM’s agent scripting capability that dynamically displays scripts (dialog) to
users that are personalized for the customer within the context of the
interaction. Displayed in the Interaction Thumbnail area.
Dimensions A hierarchical context for the facts and responses associated with an
interaction. Currently, the following dimensions are implemented: customer,
application, proposition, channel, behavior, response context and time.
directed An inheritance method that causes a class to inherit characteristics directly

inheritance from a specified parent class, regardless of any defined pattern inheritance,
i.e. it is mandatory and takes precedence over pattern inheritance. The
system always looks for the rule it needs in the class initially provided. If the
rule does not exist in this class and if pattern inheritance is enabled, the
system next looks for the rule in the pattern class. If the pattern search
finishes without finding the rule, the system goes back to the original class
and uses directed inheritance to locate the rule. Directed inheritance allows
a parent class name to be unrelated to the name of the class. Directed
inheritance paths are displayed by the Inheritance Viewer with a solid line.
Directly Capture A term that describes the process of using PRPC as an integrated solution
Objectives (DCO) to capture objectives, requirements, draft flows, draft UI and specifications,
and enables reuse of these individual components throughout the delivery
methodology.
Discovery Map A graphical design tool used to provide a high-level presentation of the steps
in an application's starting business processes, including the subprocesses
and alternate paths and the sequence of the specifications and requirements
for each work type. A Process Discovery Map captures the primary path –
the sequence of steps that users will most likely perform to resolve a piece
of work - the top row.
This tool is integrated into the Application Profiler and Application
Accelerator, the Processes tab of the Case Designer landing page and the
Diagram tab of the Flow rule form. The Application Accelerator uses the end
result as the basis for creating the draft starting flow diagrams in the
application.
division The middle level of the standard three-level organization hierarchy. The
organizational structure affects management reports and statistics and the
RuleSets visible to users in that organization when they log in. See
organization and unit.
Document button A button in the Application Profiler that when clicked produces a Microsoft
Word document listing all the rules associated with the selected application.
You control what rules and which sections appear in the document.
draft mode A setting in Visio, Process Modeler and the Discovery Map that allows users
to create and model flows with shapes that contain rules and flow actions
that are not yet defined or complete.
DynamicSelect An optional control added to user forms (through HTML rules, harness rules,
or section rules) and other HTML forms to speed user input. It displays a
drop-down list that contains values returned from an activity, instead of the
normal (static) HTML SELECT element control.
E
edit validate rule Defines a Java routine that tests the validity of an input value and/or formats
data; listed in the Property rule category.
Elaboration Phase In this Phase you analyze the problem domain, establish a sound
architectural foundation, develop the project plan and eliminate the highest
risk elements of the project. At the end of this Phase, the hard “engineering”
is considered complete and the project undergoes its most important day of
reckoning: the decision on whether or not to commit to the Construction and
Transition Phases. The Elaboration Phase activities ensure that the
architecture, requirements and plans are stable enough and the risks are
sufficiently mitigated, so you can predictably determine the cost and
schedule for the completion of the development.
The output from this Phase includes a use-case model (80% complete),
software architectural description, executable prototype, a development plan
and a revised risk list and business case.
Embed- base The parent to other classes. By definition, any class derived from the
class Embed- base class is used only as an embedded class; they’re never for
top-level structures, clipboard pages or saved objects. Accordingly, no
saved instances of concrete Embed- classes ever exist.
embedded page A clipboard page that has the value of a property of mode Page. Any page
on the clipboard that is not a top-level page is an embedded page.
escalation Refers to any processing within a PRPC application that causes high-priority
work items to become visible to users and managers based on service level
rules and to be processed sooner rather than later.
exception path The less likely paths a process may take to complete a unit of work. Also
called alternate scenarios.
Export gadget A form in the Application Packaging wizard on a source PRPC system that
contains the rules to be extracted. Rules to be exported are copied to a
specific RuleSet and version, all rules in a full RuleSet, or all rules and data
instances defined in a product rule or patch rule.
exposed property A Single Value property that is visible as a column in a database table,
enhancing record selection operations in reporting. Aggregate properties,
properties within an embedded page, and properties that are not exposed
are contained in a specially formatted Storage Stream or BLOB column.
express action Buttons placed in the repeating row of a Tree, Tree Grid or Grid to provide
quick access to actions on the work item represented by that row.
Clicking the button may initiate an action, like “Open”, “Approve", Speed
Approve" or "Flag for Review", that does not require further user input; or it
may cause a modal dialog to appear with a form based on a flow action the
user specifies.
Expression Builder A guided interface used to construct sound Java expressions by guiding the
user's selection, locating functions, completing parameters to functions in a
natural language format and validating the format of an expression.
F
field value A tool supports testing, evaluation and fine-tuning of localized applications,
inspector by allowing updates to field value rules through a pop-up window that
contains translations while viewing the application. Displays visual indicators
that link text elements on a form to the associated field value rules and
identifies missing field value rules, for text labels, error messages, Tool Tips
and so on
final rule A rule that has the Available field set to Final - and displays a green stopped
arrow on a rule form - meaning that no one can create a second rule with the
same visible key in any RuleSet other than the RuleSet to which the first rule
belongs to; but this rule can be overridden through a higher version in the
same RuleSet. Most standard rules that are necessary to ensure the
integrity and security of the system are set to final.
flow See workflow.
flow action A rule that controls how users interact with user forms to complete
assignments. Flow actions correspond to steps within a flow, contain
sections and determine which data values are displayed in the Take Action
area of a work item form. These choices are available as interim or final
dispositions of the assignment they are processing. There are two types of
flow actions: connector flow actions and local flow actions.
flow rule The fundamental rule that represents a business process or part of a
business process, governing how work items are created, who works on a
work item and in what sequence, what decisions and processing occur
automatically, how work items are resolved and more. A flow rule consists of
a network of shapes and connectors (lines), each with associated
parameters and values. There are three diagram modes in which to edit the
flow: Process Modeler, Microsoft Visio and Discovery Map.
folder A folder is a type of work item that loosely packages many related work
items, covers and other folders together.
fork A feature available through the Decision shape to evaluate When
connectors, where the flow chooses one of multiple paths of processing
based on the conditions on the object.
forward chaining An internal mechanism that provides the automatic propagation of changes
in one property value to changes in other property values or to indexes.
In a Declare Expression rule, constraints rule or Declare Index rule, you can
establish required relationships among properties. When an activity step
changes the value of a property that is defined in such rules, the system
automatically consults an internal dependency network to see if other values
are affected and performs property value computations, indexing and other
processing as determined by the network. Similarly, Declare OnChange and
Declare Trigger rules implement automatic processing when certain
database or property value conditions are met.
FQN Fully Qualified Name.
framework class A class that belongs to a RuleSet that is not one of your application
RuleSets. If the Application Accelerator created an application with
framework classes, the second segment of the class name is FW.
framework layer or The classes associated with the framework business application — started
application through the Application Accelerator and defined through an application rule
and one or more RuleSets — that provides an almost complete solution for a
business.
function rule An instance of the Rule-Utility-Function rule type. Each function rule defines a
Java function and makes it callable from activities and expressions.
G
gadget An HTML rule that defines the label and function of a link on the portal, such
as the worklist display. A gadget provides information or tools that assist a
system architect or system administrator in building and maintaining
applications.
Gadgets determine the appearance, labeling and location of sections on the
home page (portal) and which parts of the portal are visible to different
groups of users.
geolocation The detection of the physical location of an Internet-connected computing
device. More generally, a set of services related to mapping and directions on
a mobile device.
gesture A movement or touch-based user interaction with an application on a mobile

device, such as tapping or swiping the screen, or shaking or tipping the
device. This contrasts with traditional desktop interactions based on keyboard
and mouse.
goal The amount of time a user is expected to take to resolve a case or to
complete an assignment. It is the smallest time interval, configured in a
service level agreement (SLA). See deadline.
governance The processes that need to exist and be enforced to help guide projects to a
successful completion. All departments associated with a project should
participate in project governance for it to be successful.
grid control A control available in harness, section and flow action forms that displays
the relationship between large quantities of data and provides a convenient
interface for editing or adding to that data.
guardrails A landing page that presents information about the rules with warnings in the
current application and its built-on application, the severity of the warnings,
and how many are justified warnings. Warning messages suggest that the
rule is at variance with guardrails, good design, implementation and other
best practices.
H
harness rule A rule that sequences section rules, defining the layout of the workspace.
History- classes These classes are created automatically as a byproduct of the creation of
other classes, to track changes to instances of other classes.
HTML fragment Defines reusable HTML not tied to a specific class and holds frequently
needed HTML text, JavaScript or style (CSS) text; listed as part of the
Technical rule category.
I
implementation A class that belongs to a RuleSet that is one of your application RuleSets.
class When you create an application with the Application Accelerator, the second
segment of an implementation class is a division name.
implementation An application that is built upon, and that extends and modifies, a framework
layer or application for a specific organization or division.
application
implementation A type of software development methodology that focuses on project
methodology management, return on investment, conformance to best practices and
compliance requirements, communication with stakeholders and the creation
of physical artifacts that help ensure project success.
Inception Phase The phase when the business case and success factors (expected revenue,
market recognition, etc.) are identified. To complement the business case, a
basic specification model, 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 definition and cost/schedule
estimates.
 Requirements understanding as evidenced by the primary
specifications.
 Credibility of the cost/schedule estimates, priorities, risks and
development process.
 Depth and breadth of any architectural prototype that was
developed.
 Actual expenditures versus planned expenditures.
If the project does not pass the criteria above, it can either be cancelled or
this phase can be repeated after the project is redesigned to better meet the
criteria.
inheritance Inheritance is not related to Java inheritance; rather it is the result of PRPC
rule resolution algorithm in order to promote the reuse of rules. When a
class inherits from another class, the inheriting class (referred to as a child
class) automatically gains use of all the rules applied to the inherited class
(referred to as a parent class). Application-specific data elements (or
properties) and other rules can be added to classes so that an inherited rule
will be overridden by a rule of the same type and name in the child class.
PRPC uses two ways to inherit rules: pattern inheritance and directed
inheritance.
instance A single, durable, potentially permanent representation of a concrete class,
created using the New operation (instead of the Java term constructor or
instantiation).
Each instance is stored as a row or record in the PegaRULES database. A
page in the clipboard corresponds to a locked open instance. An instance
consists of property values, some of which form a unique key to the
instance.
instantiate The creation of a new work item, whether automatically through operation of
a case type rule, or manually.
Integration Rule types and data classes organized into this category as a learning and
Services category navigation aid. The thirteen rule types in the Integration Services category
create service rules and data objects and support service interfaces between
PRPC and external systems for nine service types, for example, SOAP.
JMS, EJB and .NET.
intent-driven In PRPC, the use of familiar terms from the application domain for names,
processing labels, selection of available flow actions and the Instruction field in
assignments, for example, Submit PO for approval.
In CPM, the ability to dynamically drive processes based on the intent of the
user while presenting the right data at the right time to simplify the overall
user experience.
Interaction The communication between a contact and an organization, in real time or
offline. See Live Interaction and Non-live Interaction.
Interaction Driver A Customer Process Manager UI component that dynamically presents the
user with a variety of service process options, based on rules that are
constantly evaluating customer context. It consists of Suggested Tasks, a
“To Do” list (queued Service Processes for the user) and different categories
of Service Processes that the user can choose from (such as Account,
General, Contact).
Interaction Goal In CPM, reflects an organization’s business rules and can be based on prior
customer interactions, customer profile or other information. CPM may use
this goal to present different dialog scripts to the user or may use it to
present suggested processes. The Interaction Goal displays in the
Thumbnail area of the CPM UI.
Interaction Result The reaction of a customer to a proposition that is recorded in the IS
database tables and propagated to ADM and VBD.
Interaction An area of the CPM user interface that provides users with pertinent
Thumbnail customer information (such as customer name, Duration Timer, Interaction
Goal, and Call Back Number).
Interaction Timer A timer gadget on each Interaction in CPM that indicates how the interaction
is proceeding in relation to defined service levels (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.
Interactive Voice The equipment (or software) used to provide automated service to
Response (IVR) customers over the telephone. Customers often interact with an IVR before
being transferred to a service representative in a call or contact center. Also
known as Voice Response Unit (VRU).
interested party An organization or person who may receive information about a work item,
but who is not an active participant with no responsibilities or influence. The
parties and the role of each, such as originator, customer, merchant bank,
paying bank, broker, and so on, identified for a work item.
internal key The text value of a reserved property @baseclass.pzInsKey, defined in the
ultimate base class and available in every class. This value is also known
as the handle. For rule instances, the date and time that the rule was first
saved is a portion of the internal key. When a database administrator
creates a new table in the PegaRULES database, it is important to include a
database constraint that identifies the pzInsKey column as the primary key
of the table
Internet A tool that enables a PRPC application to be embedded as a gadget on the
Application pages of a Web application located on your intranet, extranet, or internet site.
Composer (IAC)
interval Typically used to group the values of numeric predictors. Each
interval provides a useful building block for understanding behavior.
inventory button Produces an interactive HTML report that lists all the rules associated with
the application sorted by the Applies To class.
iteration A complete development loop resulting in a release (internal or external) of
an executable product or a subset of the final product under development,
which grows incrementally from iteration to iteration to become the final
system.
J
Java EE Java Enterprise Edition.
JAR Java ARchive, a file format that aggregates many files into one ZIP
compressed-file.
K
key performance Business activity focused on identifying, monitoring and measuring
indicator (KPI) organizational performance of a business operation that is considered
important by management.
The KPIs gadget on the Business Analyst portal's home page and the
dashboard display of the Work Manager portal can present real-time KPI
results for an application, using gauge charts or other interactive charts.
Knowledge Topics A CPM capability for creating, maintaining and enabling agents to leverage
relevant knowledge content during processing of work. Knowledge Topics
can be configured to automatically be associated with specific steps
(screens) during a process flow.
L
landing page A set of one or more displays or tools (also known as gadgets) in the
Designer Studio that is reached from the Pega button menu. Each page
presents one or more gadgets.
library rule A container for a set of related function rules that holds custom functions for an
application, and which can supplant and extend standard functions.
Lift A measure (multiplied by 100) of the improvement in behavior exhibited by
cases in one interval or segment over the average of all cases.
likelihood A value between 1 and 100, interpreted as an assumed or known probability

associated with a flow action. Likelihood values determine the order of
presentation of connector flow action choices on the Perform form — the
highest likelihood choice appears first.
linked properties A Single Value text property that has a value that is expected to exactly match
the key of an instance of a concrete class.
listener A background Java thread that monitors a TCP/IP port, a mailbox, a

messaging facility or a directory for arriving messages or files.
live interaction A telephone inquiry, chat session or a branch walk-in visit from a customer.
CPM creates an interaction log to record all activities and service items that
result from live customer interactions.
local A RuleSet that is always included in your set of application RuleSets and is
customization often the default RuleSet when Save As is used to copy an existing.
RuleSet
local flow actions A mechanism that enables users to update, but not complete, an
assignment. They are referenced inside an assignment shape in a flow
diagram.
local variable Text strings stored in a Java StringBuffer object (rather than a page
structure) to manipulate local variables. Within an activity, use the Local
keyword followed by a period and the variable name to read or set the value
of a local variable.
Localization Assists developers and translators with the localization of an application to
wizard multiple languages. It provides the ability to extend and build on
Pegasystems-provided language packs for French, German, Japanese,
Spanish, Traditional Chinese and Simplified Chinese. It can also Import
translations into the language-specific RuleSet.
locking A way to prevent any changes to the rules associated with that RuleSet or
RuleSet version. When a rule belongs to a locked RuleSet version, a lock
icon appears at the upper left of the form. A password may be required to
unlock a locked RuleSet or RuleSet version.
PRPC also allows work item locking, where a requestor may acquire
temporary exclusive access to an open work item, preventing other
requestors from updating or deleting it.
Lock and Roll The ability to review and lock a RuleSet version, advance it to new, higher
version and optionally update the application with a new RuleSet version or
create a new version of the application.
logging Each node on a PRPC system produces several logs: The two most important
are Pega Log and Alert Log. Pega Log — also known as the console log or
system log — which contains messages created since the server was most
recently started and the Alert Log, which contains only alerts and supports
performance-related monitoring.
logistic regression A statistical term that represents a type of regression analysis used for
predicting an outcome.
M
major version The number of a RuleSet version, consisting of the first two digits of the
complete version number, for example, 01-02-04. The Skim operation can
create a new major version. Rules in versions below the major version are not
visible to rule resolution.
map value rule A rule that uses a table of numbers, text or date ranges that converts one or
two input values to a calculated result value. At runtime, PRPC evaluates
the rows starting at the top and then evaluates columns from left to right.
Part of the Decision rule category.
Measurement The primary storage of numeric information associated with
interactions, which can be used for Key Performance Indicators
(KPI). There are two types of measurements. In the context of the simulation
process these two types can be defined as strategy-driven and customer data-
driven. Decision Management supports up to 20 measurements.
method The rules that define the methods that can be used in steps of activities and
Parse Structured rules. About seventy standard methods are available for your
use.
minor version The number of a RuleSet version, consisting of the middle two digits of the
complete version number, for example, 01-02-05.
mobile compliance Applications that use only layouts, harnesses, controls and behaviors
supported by Pega Mobile are considered “mobile compliant”. A mobile
compliant application does not require any user interface enhancements to be
enabled for mobile users.
mobile RuleSet A special RuleSet that is included automatically in the RuleSet stack for users
connecting through a mobile device. The name of a mobile RuleSet matches a
base RuleSet with “_mobile” appended. For 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 A specialized version of a rule that is resolved only for users on mobile
specialization devices. Rules may be specialized using circumstancing, or by including them
in a Mobile RuleSet. Mobile specialization is typically used when a user
interface element such as a harness or section does not work well for mobile
users, but is optimal for desktop users. See also mobile compliance.
modal dialog A pop-up dialog box combined with a flow action that displays in front of all
other forms. The flow action provides the section or sections containing the
form fields the user is to complete. The user cannot continue with other work
until he has submitted the form or dismissed the modal dialog.
When the user submits the form, the system updates the work item and the
modal dialog closes. The user can then continue working with the main
screen display.
mode See property mode.
model attributes Various descriptions and settings created during model development that
can be made available to the decision making system at decision time.
modeling The process of generating a model as a conceptual representation to identify
patterns in behavior.
multi-channel The ability to access and use a process over multiple channels or modes of
communication. For example, a CPM service process may be used regardless
of whether the customer communicated with the organization using a phone
call, letter, email or a text chat request.
My Rules The list of rules delegated to a user personally or delegated to everyone
sharing an access group. Each delegated rule is identified by a shortcut link (a
favorite).
N
Net Promoter® A framework of practices designed to measure and improve customer loyalty
System (NPS) and build lasting relationships. A net promoter score is a measure of the
loyalty of an organization’s customers and whether they would be willing to
recommend the company to others. Net Promoter Score, Net Promoter and
NPS are registered trademarks of Bain & Company, Satmetrix Systems and
Fred Reichheld who developed the system.
Next Best Action A strategy that allows applications to make the best decision in a
(NBA) multidimensional context (retention, recruitment, risk, recommendation, etc.).
non-live An e-mail, fax or mail inquiry from a customer. CPM creates an interaction
interaction log to record all activities and service items that result from non-live
customer interactions.
notify An activity referenced in a flow that sends correspondence, such as an email
message, when a flow execution creates an assignment. Typically, the
system addresses correspondence to a work party who is identified in the
work item and reports progress to that party.
O
operator profile The profile of a requestor session is a collection of facts and values about the
operator and the requestor. Many are derived from the Operator ID instance
and other data instances.
operator ID Defines an operator’s username, password, access group organizational
setting, calendar and other values.
organization The top level of the standard three-level hierarchy available in every PRPC
application. The organizational structure affects management reports and
statistics and the RuleSets visible to users in that organization when they log
in. See division and unit.
organization unit See unit. The bottom level of the standard three-level organizational
hierarchy available in every PRPC application.
originator The party who directly caused the work item to exist. This may be a
customer, an employee, a vendor representative or another party.
outcome The field representing the behavior to be predicted.
overfitting A statistical term describing the fact that a predictive model is more accurate in
fitting known data (hindsight), but less accurate in predicting new data
(foresight).
override During rule resolution, to mask others rule instances available that are siblings,
that is, that have the same names (for all key parts) but different RuleSets or
the same RuleSet but different version numbers.
ownership Work items are owned by organizational entities, not by people. Usually, the
initial owner of a work item is the organizational unit of the user who entered
the work item. Processing of a work item can update its ownership with new
values for its owner and organization properties. Ownership does not
constrain who can work on assignments from the work item.
Omega XML The XML file format of predictive models as published using Predictive
Language (OXL) Analytics Director.
P
page A memory instance on the clipboard that holds name-value pairs. See
clipboard.
page group A property mode that allows an embedded unordered array of pages. See
property mode.
page list A property mode that allows an embedded ordered array of pages. See
property mode.
parameter page The location where parameter names and values are stored when an activity
is called.
parent flow The flow rule that contains the call, branch, spinoff or shape that started the
current flow execution (a subprocess). This is not a permanent or static
relationship.
parse XML rule A rule that contains parsing instructions to interpret the XML. Used with
services and connectors to map data from an incoming XML document or
text message into clipboard property values. The message may be a request
for a service or a reply from a connector.
party A person or entity involved in a case; for example, a customer, a bank or an
internal department.
patch version The final two digits in the RuleSet version number, for example, 01-02-04.
pattern inheritance An optional type of inheritance that causes a class to inherit characteristics
from other classes by parsing class names and inheriting from classes it
resembles in name, while moving up the visible class hierarchy. If enabled,
rule resolution searches through additional classes when looking for a rule
with a specific name,
The dash or hyphen is used as the delimiter for pattern matching. To
determine the parent of a particular class, the characters to the left of the
right-most hyphen is the class from which this class inherits rules. For
example, for a class named ABC-DEF-GHI, pattern inheritance searches
exactly the following classes in the following order, stopping when it finds
what it seeks:
ABC-DEF-GHI
ABC-DEF-
ABC-DEF
ABC-
ABC
Consequently, it would never find classes named AB, AB-, ABC-D or ABD-
DE.
Pega button A button in Designer Studio that provides a menu of landing pages.
Pega Cloud A Pegasystems product offering, this is a form of "cloud computing" where
multiple, separate PRPC systems are hosted by one server, implementing a
shared compute and database resources.
Pega Mobile: An optional product that enables users on mobile devices such as smart
phones and tablets to access a PRPC application.
PDN World Wide Web-accessible knowledge base of the latest information and
examples about a wizard or other facility. The PDN provides short articles,
identified by a knowledge base number, such as 26404, longer documents
that are distributed as HTML documents and also Acrobat PDF files that you
can download and other resources available to Pegasystems customers and
partners. Books are available as single chapters or complete PDF documents.
perform A description of what users usually do as they work on assignments (as

opposed to the automatic processing done by the system). When users
perform an assignment, they update information in the work item and generally
eliminate (complete) the assignment. Standard harness rules support users as
they perform assignments, by including an action section.
PegaRULES The relational database that houses PRPC data.
database
Performance tool A PRPC tool used to identify and record resource usage and inefficiencies in
(PAL) a PRPC application such as resource bottlenecks; the number of times an
event occurs and how long each event took to complete.
Personal Edition A limited-distribution, limited-capacity edition of PRPC that is distributed for
training and experimental use. It contains a small application that can be
tested and enhanced. All features are present, but performance is typically
constrained by the laptop or workstation's memory and disk capabilities.
personal RuleSet A RuleSet created automatically for those users who have the Allow Rule
Check Out? checkbox (on their Operator ID instance) selected. It provides a
place where copies of rule instances can be held when an application
developer checks out a rule (using either the standard check out or private
check out). This RuleSet is always topmost in a user's RuleSet list and is
named the same as their Operator ID.
population The group of cases with known behavior which is consistent with the
group of cases whose behavior is to be predicted. In predictive analytics,
samples are extracted for modeling and validation from the population.
prconfig A name-value pair that affects the operation of your system. Some prconfig
settings have a narrow purpose and outcome, while others have broad,
system-wide impact. The Configuration Settings Reference Guide on the PDN
describes the names of various settings (for both current and older releases)
and the results obtained from each value.
precondition A true-false test associated with one step of an activity. During activity
execution, the system evaluates the precondition to determine whether to
execute or skip the method referenced in the step.
prediction The outcome to be predicted, which is specific to a form of behavior at a
given point in time.
Predictive A desktop application used to develop and create predictive models. These
Analytics Director models are used to create and define predictive model rules, which can then
(PAD) be used directly in flows, or combined with other components in a strategy,
providing the means to differentiate between cases on the basis of likely
future behavior, insights that enable opportunities and risks to be evaluated,
constituting the foundation of personalized strategies.
predictive model 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 are developed in the Predictive Analytics Director.
predictive Some measure of the scores or segments generated by models.
performance Performance can be measured in terms of predictive power, value or rate
achieved under selected conditions.
predictive power For scoring models, the measure of the ability of a model to separate cases
with a positive outcome from those with a negative outcome using behavior
defined in terms of two opposite types of outcome, either a symbol to
indicate which type of behavior or the probability of being one of the types.
Pre-inception Processes that are associated with a project that occur prior to the Inception
phase. These usually include pre-sales activities and are primarily
performed by Sales Executives, Sales Consultants and/or Practice Leaders.
predictor grouping The grouping of predictors whose relationship with behavior is correlated
at, or above, a selected level of correlation.
predictors Properties considered to have a predictive relationship with the outcome.

Predictors contain information available about the cases whose values may
potentially show some association with the behavior you are trying to
predict. Examples include:
 Demographic
For example, age, gender and marital status.
 Geo-demographic
For example, home address and employment address.
 Financial
For example, income and expenditure.
 Activity or transaction information
For example, the amount of a loan taken out of the price of the product.
preview Splits the workspace to present a partial preview of the runtime appearance
of a rule in the bottom half of the workspace. Using the Preview function for
a harness, section, flow action, activity or HTML rule creates a clipboard
page and initializes properties on that page.
primary page Used at runtime to access a location in memory (clipboard page) to display
or manipulate data. The clipboard page that the currently executing rule is
most likely to use as a source of property values and target for changed
property values.
primary path The most likely course of action a process follows to complete a unit of work.
Also called the normal course of events.
privilege An access control element associated with a class and an access role.
Privileges offer finer tuning of access control than access roles alone. To
have access to a privilege, a user must have at least one of the access roles
that grant access to the privilege in an access role list.
prlogging.xml A configuration file for the PRPC logging facility that specifies what severity
of messages will be output and where the messages should go (into a file,
the console, another program, etc.); a modified version of the Apache log4j
facility.
Process Architect See Business Architect.

process category One of the groupings under the rule types and data classes category that
includes rule types that support business processes such as collection,
correspondence, service level and flows.
Process Engine Business process management applications can use an external portal or
API external system to call PRPC services through Service Oriented Architecture
(SOA) facilities. The SOA facilities, in turn, call this API, which includes a
collection of standard activities, flows and flow actions that are used to
create work items, advance the work items through a flow, perform
assignments and so on, without using user forms.
Process Explorer A graphical display of the starter flow rules (represented by a green
rectangle) and the subprocesses they call, to aid identification of the
caller/calling relationships among the flow rules for the currently selected
application and work pool.
Process Modeler The default PRPC editor used to create and edit process flow diagrams.
production A RuleSet that has the Type field set to Standard (on the Category tab of
RuleSet the RuleSet form) and that typically has at least one open (not secured)
RuleSet Version.
Profile Explorer A metric-related display used by business analysts and others to monitor the
application's business-related assets, profile-related elements and enter
specifications over time to ensure its design and behavior meet the
specifications and requirements.
Project Explorer A tool that is enabled by the Project Management interface.
Project A PRPC application that links application development work to project
Management assignments and implements best practices for the management, tracking
Framework (PMF) and real-time reporting on projects across multiple development and QA
environments.
propensity The probability of positive behavior or membership.
property A data element that acts as a container for data from a PRPC application. It
defines and labels a value that can be associated with a class. Applications
capture, store, process and display data that is saved as properties.
Properties can capture a single value or aggregate other properties and their
values. Each field used to collect new data or display existing data
references a property and a property can have a type to identify the type of
data this property holds.
Properties have controls that allow users to format how the property is seen,
for example, defining a calendar control for the property displays a calendar
next to the property.
property mode A property has 1 of 11 modes that are variations of either single, array or list
and group. See Application Developer Help for more information.
Property Optimizer A tool that is accessed by right-clicking the Optimize For Filtering option for
tool a property in Designer Studio. Running 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.
proposition A tangible product offer, such as a handset, or a subscription, or a less
tangible offer, such as benefits, compensation or services.
proposition A method of combining and presenting a number of propositions as a coherent
bundling and justifiable set in terms of cross-product eligibility, propensity and likelihood
of interest linked to the call reason.
PRPC Pega Rules Process Commander Where PegaRULES is the business rule
engine (Pega RULES) and Process Commander is the business process
management suite.
The world's leading business application development platform for developing,
deploying and evolving business processes, business rules, integration, case
management, and user interactions.
pyWorkPage Many standard flow processing activities and rules use specific page names
by convention; when a single (non-cover) work item is opened onto the
clipboard, the page is named pyWorkPage.
Q
Quick Create A button that speeds development work by creating a simple property, field
value and when condition rule types directly in the New dialog by completing
one or more key fields.
Quick Launch A toolbar
R
ranking Part of the rule resolution algorithm PRPC uses to find and rate the best or
most appropriate rule instance to apply.
Rational Unified An iterative software development process framework created by the
Process (RUP) Rational Software Corporation (now a division of IBM). RUP is an adaptable
process framework, tailored by development organizations and software
project teams according to their needs.
rendezvous Occurs when multiple flows must come together at the end of the process.
refactoring A tool to move rules with a specific Applies To class from one RuleSet into
another RuleSet or another Applies To class, removing them from the
current RuleSet.
referencing rules A facility available for several rule types where the left column lists other
rules that reference the current rule, while the right column lists rules that
the current rule references. This can be a valuable aid in learning and
debugging applications.
Related Rules A button on the Designer Studio toolbar used to access a list of other rules
that are alternatives or otherwise related to this rule.
Repeating layout A way of presenting information from items from sources such as a Page List
or Page Group property, a report definition or declarative page. There are six
repeating layouts that are available: Row Repeat, Column Repeat, Tabbed
Repeat, Grid, TreeGrid, and Tree.
Report Browser Ability for a user of the Manager portal to browse and search for existing
available reports, re-organize reports within report categories, run reports,
create new reports and share them.
report category Category rules define categories that can help users organize reports in the
rule Report Browser.
report definition A rule that defines a shared or personal version of a report. This rule
rule generates HTML that displays selected data in a wide variety of formats and
allows a wide variety of user interactions with the displayed results.
Report Editor A tool that displays the selected report or the newly-created report, and
provides an array of tools and resources for editing. The Report Editor displays
simulated data only. To see actual data in the report, save the report, exit the
Editor, and view the report in the Report Viewer.
report shortcut A named link in the Report Browser that allows managers to retrieve and run
rule the report. They also allow managers to organize their reports based on the
report category’s name.
Report Viewer A separate window that displays the results from running a PRPC v6 report
using the Report Browser. Provides many options for manipulating the
displayed report, including formatting, filtering, saving, printing and exporting
the report to Excel.
requestor The process and data associated with a user (guest or authenticated) of
PRPC, or the processing and data associated with a request into a system
started by an external system.
requirement An inventory of events, conditions or functions that need to be satisfied and

tracked by an application.
resolution The act of closing a work item, identifying in the properties that work is
complete, through user input and automatic processing. After a work item
becomes resolved, it generally cannot be worked on (modified) until it is
reopened, although some changes are possible.
reusable A characteristic of a software component that supports a general-purpose

function or process. PRPC offers multiple facilities to promote reusability, such
as class inheritance, a library of standard rules, subprocesses and
organizational hierarchy.
robustness A statistical term that measures the consistency and reliability of a predictive
model over many data samples, used for model comparison.
role A concise description of the party and their part in the process.
router activity An activity that determines which worklist or workbasket is the recipient of an
assignment.
rule A rule is a data construct that defines user interface, business logic or data
behavior within PRPC. Rules are constructed using rule forms, stored in XML
format in a PegaRULES database and some rules are some rules are
converted to Java at runtime and stored in the PRPC database.
A collection of rule instances of the same type and purpose stored in the same
RuleSet.
rule availability A technique that improves system performance and involves generating and
compiling Java code corresponding to a rule at the moment it is first needed
to execute, rather than in advance. This technique avoids the cost of
creating and compiling code that is never used and produces more efficient
Java code than the "generation at Save" approach.
A second use of the rule (by the same requestor or another requestor with the
same RuleSet list and on the same node) executes the precompiled Java code
for the rule. PRPC generates rules-assembly Java for activities, stream rules,
most decision and declarative rule types, parse rule types and others.
rule instance The collection of all instances that exist in a RuleSet version. When PRPC
processes work, it uses a process called rule resolution to determine the rule
instance to use when a rule is called..
rule cache An internal cache of compiled rules where the Java classes compiled during
rules assembly reside. The rule cache is specific to a given user. Also called
the instance cache.
rule form An HTML form that represents a rule instance. Users enter information on a
rule form. PRPC uses this information to generate and compile executable
Java code during rules assembly.
rule resolution PRPC’s search algorithm used to find the best or most appropriate rule
instance to apply in a situation. Rule resolution applies to most, but not all,
classes derived from the Rule- base class.
Rule resolution uses as input values:
 The name of the rule needed (one or more key parts)
 A starting location in the class hierarchy, often determined by context
 Your RuleSet list
 The current date and time, which may cause time-based rules to
take precedence
 Circumstance property and value
 The value of the as-of date property
 When to use either directed inheritance or pattern inheritance
rule resolution An internal cache that maintains sufficient information regarding rules and
cache their versions to determine the applicable rule to be compiled during rules
assembly. It is specific to a given user.
rules assembly The process of generating and compiling Java code to execute a rule.
Rules Explorer A navigation feature that allows users to quickly access rules and data
objects; displays all rules regardless of application.
Rules Inspector A tool that provides an easy way to locate rules present in the user interface.
RuleSet A group of related object classes, workflows and business rules.
RuleSet hierarchy The ordered list of RuleSets in PRPC applications. The most general
RuleSets that provide basic functions are at the bottom, RuleSets specific to
your application are in the middle and RuleSets customized for your
organization are at the top.
RuleSet list An internal data structure, assembled automatically from several sources when
users log in, to determine which rule instances a requestor can execute (rule
resolution processing).
RuleSet A RuleSet that is required by one of the RuleSets that comprise your
prerequisite application.
RuleSet version Defines a three-level version number for a RuleSet name. Every instance of
every rule type references a RuleSet version.
rule type The class to which a rule belongs or is an instance of. The concrete class
derived from the Rule- base class.
S
sample A sub-set of historical data extracted by applying a selection and/or sampling
method on the data source. To be meaningful and reliable, it is essential that
the sample uses sufficient records and that the distribution of values and
patterns of behavior are representative of those in the population.
schema The structure and layout for the database. At initial installation, the
PegaRULES database includes about 70 tables in a single database instance.
Each table stores the persistent objects from one or more concrete classes.
Columns for the table correspond to Single Value properties in the object.
Some aggregate property values are stored in a single special column named
pzPVStream, known as the Storage Stream.
score The value calculated by a model. Score intervals are aggregated under a
score band.
score band A set of score intervals.

scorecard A decision rule that combines a number of properties to calculate segments.
The resulting segmentation is translated into a score.
scoring model The score positions a case on a numerical scale. High scores are associated
with good performance and low scores are associated with bad
performance. Typically, the range of scores is broken in 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
that fall into each interval.
screen flow An input procedure that presents a user with a series of forms and that
allows users to change or review previous input.
section A rule that defines the content and behavior of a rectangular area on a work
item form, called by flow action rules and harness rules.
segment A group of customers defined by predicted behavior, score and
characteristics. Segmentation components in a strategy drive the decision
flow by placing a customer in a given segment for which actions/results are
defined.
sequence diagram An interaction diagram that is organized according to time and details how
operations are carried out, including what messages are sent and when.
service A programmatic component that defines and implements an interface
between an external application, acting as a client and a PRPC system,
acting as a server. Implemented through an appropriate Rule-Service rule,
and in some cases, appropriate code in the initiating application or system.
See connector.
Service The Service accelerator creates service rules and data objects for services
Accelerator for nine service types: SOAP, JSR94, .Net, JMS, HTTP, MQ, EJB, File and
Java. The Service Accelerator is also known as the Service wizard.
service level rule A rule that defines the time interval required to complete a request. It
includes one or two time intervals, known as goals and deadlines, which
indicate the expected or targeted turnaround time for the assignment or time
to resolve for the case. See deadline and goal.
service process In CPM, a service process is a work flow that starts within an Interaction,
creates a work item or case, and guides the user through a process to
address the work item. The work item can be completed during the
Interaction or can continue processing after the Interaction is completed.
Also known as an Intent Task.
Service Process A CPM wizard that automates the creation of Service Processes.
Accelerator
service request A request to perform a task, usually on behalf of a customer. In CPM, a
service request or case is processed using a service process..
Setup wizard Formerly called the Initial Setup wizard and the External Setup wizard; this
wizard prepares the environment for application development by configuring
the prerequisite elements for logging on to PRPC and building applications.
This tool creates a starter set of operators, access groups and rules.
sibling rule A rule instance that has the same name and the Applies To class (visible key)
as another rule instance.
Simple Object An XML-based protocol used to exchange information in a decentralized,

Access Protocol distributed environment.
(SOAP)
single value A property mode that has built-in data types for lower-level elements such as
an integer, decimal or true/false.
Six Rs (6 Rs) Process Commander applications provide business process management and
automation through six functional capabilities, informally known as the Six R's:
 Receiving — Accepting and capturing the essential data describing work from
multiple sources in multiple media and formats, from keyboards, scanners, and
external systems.
 Routing — Using characteristics of the work and knowledge about the
workforce to make intelligent matches and assignments.
 Reporting — Providing real-time visibility of work in progress, work completed,
productivity, bottlenecks, and quality.
 Responding — Communicating status, requests for information, and progress
to the work originator and to other people involved in the work, by email, fax,
written mail, and other means.
 Researching — Accessing external systems and databases through
connectors to support analysis and decision-making.
 Resolving — Through automated processing and automated support of users,
completing the work and updating downstream systems promptly.
Sizing tool An Excel spreadsheet, produced by the Application Profiler, that can be used
to estimate the duration and size of an implementation project.
skin rule A rule that is referenced in the portal rule that defines four Cascading Style
Sheet (CSS) files that together determine the colors, fonts, images and
layout of portal, work item, rule forms and report displays.
SLA Service level agreement. See service level.
SmartInfo A feature that presents a pop-up window when users hold the mouse pointer
over specific elements in a report or form. The contents of the pop-up
display are determined by a section rule, presented in read-only mode.
SmartInfo uses Asynchronous Java and XML (AJAX) technology.
Smart Layout A grid (corresponding to an HTML <TABLE> element) of paired cells on a

harness, section or flow action form that has columns of uniform width,
uniform styles and uniform characteristics. Each pair of cells holds one label
and one property value or other form control. Used instead of a "freeform"
table layout.
SmartPrompt A text box with a blue triangle in the lower right corner used on many forms
that dynamically creates a list of valid selections for fast user data entry.
Shapes that can be displayed on the Visio template. Each shape has
SmartShape
parameters, behaviors and types of tasks.
SnapStart A data import facility used to generate and pre-populate PRPC work items
from an external application, without a user log-in process. SnapStart sends
a user ID and password within the URL and uses PRPC authentication.
SOAP (Simple A collection of functions that applications can call using the SOAP protocol.
Object Access
Protocol) services
Social Intercept A Social CRM application bundle that is installed as an extension to
Customer Process Manager to enable monitoring of conversations occurring
in social communities and provides the ability to proactively engage in those
conversations.
solution Starter applications for specific industries or lines of business that are built
framework on top of PRPC.
specification Defines a small but meaningful processing unit performed by actors for a
given work type that details the steps taken in each part of the interaction
with a system. involves processing by only one owner and corresponds to a
flow action, flow, screen flow, harness or activity. It includes a description of
the interaction, actors, triggers, data outputs or updates, work items and
assignments.
spin-off A feature used to execute another flow asynchronously and independently

when one flow execution starts. The first flow does not pause or wait for
results from the second flow. The second flow may operate on the same
work item, or a different work item. This support for parallel operation of
work processing at the workflow level can improve end-to-end resolution
times.
Split for Each A shape in Visio or in Process Modeler in a flow used to send a work item or
objects through another flow based on information in the pages of a Page
List or Page Group property. When the subprocesses complete, the original
flow continues. In some programming environments, this is called
enumeration or iteration.
split join A shape in a flow diagram that causes processing of a work item to split into
two or more independent subprocesses to rejoin and be completed before the
current flow continues execution. This allows subprocesses to execute
asynchronously, in parallel.
solution Industry-specific applications that provide a head start to application

framework development of selected business process applications in banking, insurance,
investment, health care and other industries. The applications are limited and
designed to facilitate further development and customization.
spin-off task Causes a second flow to start that executes asynchronously and
independently from the current flow execution; it may operate on the same
or a different work item from the first flow. It is represented by a shape on
the Diagram tab of a flow rule.
standard rule Rules that are initially installed with your PRPC system and are available for
use as-is or (in many cases) they may be copied into an application and
modified. Standard rules are also sometimes called out-of-the-box or
"OOTB" rules.
state chart A diagram that depicts the possible states of the object and the transitions
diagram that causes a change in its state.
statistical The degree to which a value is greater or smaller than it would be expected
significance to be by chance.
status connector In a flow, this is the element that appears on a Visio diagram as an arrow
that connects two tasks.
stencil A Visio file that defines a set of shapes, their associated properties and their
behaviors and that provide a diagrammatic representation of the business flow
that is easy for users and management to understand.
step The primary processing unit of an activity or business process.
step page Identifies the page on which the step is to act.
straight-through Automatic processing that occurs without operator intervention.
processing (STP)
strategy The reasoning built up by a set of components that enables business
strategy definition and provides the decision support to manage the
interaction in the context of the decision hierarchy. A strategy can import
data and propositions and reference other decision rules (scorecards,
predictive models, decision tables, decision trees, adaptive models and
strategies).
sub-process See subflow.
subflow A flow rule that performs a common set of steps either for reuse or to reduce
flow complexity. Once these steps or tasks have completed control returns
to the calling flow rule where the subflow is referenced. A subflow can only
be called from another flow, either a starter flow or another subflow. Also
called a sub-process.
sub-report A report that calls another report to provide data. A sub-report cannot have
its own sub-report.
support type A collection of specifications that are not instantiated as a work type. Can
include functions such as correspondence or security.
swim lane On a Visio flow diagram, this shape is shown either vertically or horizontally,
and graphically identifies responsibilities for sub-processes of a related
group of task shapes that are performed within a specific work context
(typically a work group).
System- One of thirteen reserved, standard top-level abstract classes, it contains
concrete classes that hold real-time status information about the server
software as it runs. For example: System-Status-Nodes instances identify
other nodes participating in your system.
System Person responsible for system installation, setup, security and other
Administrator operational functions.
System Architect An application developer who creates the class structure for your work with
supporting automation capabilities and implements interfaces with external
systems.
T
target property The address of a property name-value pair on the clipboard, in the context of
a change to the value. The dot notation syntax is used throughout PPPC to
identify references to target properties.
task A term with multiple uses:
Informally, the work that a user does to "perform" or complete an
assignment. In addition, sometimes it refers to any shape in a flow diagram.
Standard properties that record user behavior and performance of
assignments have "task" in the property name; for example
pyPerformTaskTime.
Scheduled tasks are those that can execute on a regular schedule. These
scheduled tasks are created by users through the use of report definition
rules.
Technical A group that organizes fourteen rule types, one data class, and one System-
category class. Design and development of most of these types require Information
Technology skills, including Java, HTML, XML, and JavaScript.
test case rule A rule used with the Run Rule option to enable the unit testing of a rule by itself
before testing it within the context of an entire application. It requires that the
operator ID have the AutomatedTesting privilege through an access role. The
unit testing data used for certain rule types as test case rules can be saved so
that the next time that rule is tested, the test case can run without entering the
test data again.
text file rule Used to hold and identify static HTML, XML, Cascading Style Sheet, DHTML
and JavaScript script files used in an application and provide the security,
inheritance versioning and deployment benefits of rule resolution to the file.
Use the file JSP tag within a static JSP tag to identify a single text file rule to
be included in the current stream.
Theme Allows the user to change the appearance of their CPM display. Several
standard themes are provided in CPM, or a user can create/save their own.
Themes are selected and saved in the user’s CPM Desktop Preferences.
ticket Shape used to mark the starting point for business exceptions that may arise
at any point in the flow.
Test Management An optional add-on PRPC application that implements best practices for the
Framework (TMF) testing and deployment of new applications and incremental changes to
existing applications.
thread The named context of clipboard pages. The pxThread page is a named top-
level clipboard page sometimes referred to as the thread page. Most
processing for a requestor is single-threaded. A PRPC thread does not
correspond to a UNIX or Windows operating system thread.
Tracer tool A tool that provides full debugging facilities including step-by-step execution,
breakpoints and watch variables. Use to debug flaws, activities, services,
parse rules and declarative rules.
transition A when condition or an expression that evaluates to True or False, that is
evaluated during activity execution. The resulting value (True or False) can
cause the activity execution to continue, end or continue at a higher-
numbered step.
Transition Phase In this phase, the software product is mature enough to be deployed and is
transitioned to the user community. Once this occurs, issues usually arise
that require the development of new releases to correct problems or
complete features that were postponed.
treatment of A statistical term that indicates the way a property, used as a predictor
predictors variable, is interpreted by a predictive model
Tree Grid layout Also called a Repeating Grid layout. Typically used when large amounts of
data need to be displayed. It allows users to view and possibly edit, data in a
spreadsheet format with multiple columns and rows, containing values of a
Page List or Value List property. The developer specifies which page
property to display in each column and each row corresponds to a single
embedded page.
Tree layout Allows users to view the embedded pages of a Page List or the entries in a
Value List property, as a tree. Users can click branches to display or hide
the tree’s leaves. The developer specifies which page property to display as
the name of each branch; each branch corresponds to a single embedded
page or property.
trend detection The ability to identify patterns by comparing the performance of multiple
models that are triggered by the same proposition and configured with different
performance window sizes. Determining the timeframe in number of cases
over which the performance is calculated. Implementing trend detection
requires a combination of strategy design patterns, and using compatible
adaptive model rules with different memory settings.
trend report A report that presents counts of events, objects or actors at a series of points
along a continuum on the X-axis, normally a time line representing weeks,
months, or quarters in a year, or some other meaningful increment. One
column of the data displays one or more Single Value properties of a DateTime
type.
U
UI Gallery A collection of examples of effective and dynamic forms and layouts that use
many of PRPC's design capabilities, represent best practice implementations
and comply with Pega are guardrails. These examples can be copied into an
application and extended as needed.
ultimate baseclass The topmost class in the class hierarchy. All other classes are derived from
this class; if a specific class is not chosen for directed inheritance,
@baseclass should be used.
The abstract classes Assign-, Rule-, Work- and others that are direct
subclasses of the ultimate base class are known as base classes. This class
is similar to the root class in Java.
unit The bottom level of the standard three-level hierarchy. The organizational
structure affects management reports and statistics and the RuleSet visible
to users in that organization when they log in. See division and organization.
univariate model The result of a quantitative analysis of just one variable.
urgency A numeric value between 0 and 100 that defines the importance and timing
to complete and resolve an assignment. Urgency defines the order in which
cases appear on a user’s worklist. Higher values correspond to greater
importance. Urgency can be changed by users, managers or the system
based on service levels, currency amounts and special treatment for special
customers, backlog or other conditions.
use case See specification.
use case diagram A diagram that describes what a system does from the standpoint of an
external observer (with emphasis on what a system does rather than how).
user agent string 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 PRPC application). Pega Mobile
uses a browser’s user agent string to identify whether a user is on a mobile or
desktop platform.
Utility shape A shape in a flow diagram that calls an activity rule. It specifies the
automated processing to be performed that updates a work item, without any
user interaction or input.
utility task References an activity that updates a work item but does not require user
interaction or input. PRPC comes with standard activities for utility tasks that
can be used or additional ones can be created.
V
validate rule A rule that tests property values, typically immediately after they are
submitted on a browser form. Calls edit validate rules.
value group A single property that has an unordered set of values of any Type. The
system does not limit the number of entries in a group.
value list A single property that has an ordered list of text values. The system does
not limit the number of entries in a list.
verification A task performed by a person who is double-checking prior work to catch
possible mistakes or variances from the policy before the work becomes
final. Verification is common in financial processes involving large sums,
sensitive legal commitments or correspondence.
version See RuleSet version.
Visual Business A Pegasystems product that allows users to perform historical analysis.
Director (VBD) Provides 3D graphical views of the different business decision results,
dimensions and measurements (proposition, channel, customer, accept and
conversion rate, average price, volume, number accepted, number of
processed responses, etc.).
W
Web server A server responsible for accepting HTTP requests from clients, which are
known as Web browsers and serving them HTTP responses along with
optional data contents, which usually are Web pages such as HTML
documents and linked objects.
Web service A service using the SOAP protocol to transmit XML-formatted messages.
What’s Happening A display that enables developers working on an application to monitor each
other's work and progress in near-real-time through a streaming display -
even if they are physically distributed. It displays two types of event
messages: Rule actions (deleted, checked in or checked out) and comments
posted by developers. Messages pertaining to the current application are
visible to other developers working on the same application.
when rule A rule that defines a true-false test based on comparing one or more property
values with constant values or with other property values. For example, a
when rule can test whether an amount is greater than zero or a date is in the
future. Also known as when condition rule.
Where-Am-I? An icon on a worklist or a button on a work item form that when clicked
displays the Visio diagram of the current flow rule in a separate window, with
a larger arrow marking the current assignment.
wireframe A button on a flow action form that, when clicked, displays the SmartFrames
wireframe preview which uses blue rectangles to help developers
understand the structure of the section, names of rules referenced in this
rule and the size and other relationships of elements in the section.
wizards A series of prompts to help you accomplish a task with minimal effort. See
Application Developer Help for information about available PRPC wizards.
Work- Work- classes define the data structures for processing work. Used as the
starting point for the work-related classes in the class structure. Every
application requires at least one concrete class derived from the Work- base
class.
work group Identifies a user who is a supervisor, together with a set of workers (users)
and workbaskets that report to that supervisor. An operator ID data instance
(Data-Admin-Operator-ID) usually identifies a work group to which the user
belongs.
work item The primary collection of data that a flow operates on and the primary unit of
work completion in an application. Workers using an application create,
update and eventually resolve and close work items. Sometimes referred to
as a work object. Every work item has a unique ID (property pyID) an
urgency value and a status (property pyStatusWork).
work item ID An ID associated with a work item that uniquely and permanently identifies
the work item within the work pool. When you create your application, you
define the optional prefix and suffix and the numbering format, which
together represents the unique key.
worklist A list of open (incomplete) assignments ready for a user to perform once an
Assignment shape in a flow creates the assignment. At any point in time,
one work item may have two or more open assignments. These assignments
may all appear on one user's worklist, or on the worklist of various users.
WorkManager A traditional portal used by managers and supervisors who can use the
Monitor Activity workspace.
work party A person, organization or other actor identified in a work item that needs to
be notified about the progress or status of work and can be the recipient of
e-mail or other forms of correspondence. The work party role associated
with each work party identifies why a party is present and may determine
which properties are defined for that party. Each work party is configured by
role to define who can participate in the work item.
work pool A collection of work items of related types that control how work is presented
to users who enter and select work items for processing from one or more
designated work pools.
work type A concrete class derived from the Work- base class. In the Application
Profile, the work type is also used to collect specifications.
workbasket A centralized, queue or pool of work assignments, that more than one
person has access to, and from which users from the same workgroup can
select work.
workers A role that defines the behavior and responsibilities of an individual or a

group of individuals working together as a team. The responsibilities we
assign to a worker include both to perform a certain set of activities as well
as being the owner of a set of artifacts.
workflow A standard set of steps that resolves a case; a sequence of activities that
produces a result of observable value.
worklist A list of items assigned to a specific user, ordered by urgency. Essentially, it
is a work inbox of a specific user.
work item status A property value that defines whether the work item is open or resolved and
is a primary indicator of the progress of the item towards resolution.
Web Services An XML format defined by the World Wide Web Consortium (W3C). Each
Description WSDL file describes network services as a set of endpoints operating on
Language (WSDL) messages containing either document-oriented or procedure-oriented
information.
Z
Z-ratio A measure of the reliability of expected behavior (the predicted percentage
versus actual behavior) that takes into account error by allowing for
statistical significance. The Z-ratio is positive when expected behavior is
above the average behavior and negative when below.
The Developer Toolbar 63
The Developer Toolbar

A toolbar appears at the top of the Designer Studio. The buttons that appear
on the toolbar depend on the class or instance selected.
Toolbar Buttons and Functions

The tools and selection boxes on the toolbar vary depending on the contents
of the form and list area. If a button does not appear or is unavailable (grey),
the corresponding function is not available to you in the current context.
The table below describes all the buttons that may appear.
Name Button Function

Availability Changes the availability of the rule. Select Yes, No/Draft Mode, Final or
Blocked from the dialog box that opens.
Check In This button appears only for rules in RuleSets subject to rule
management. After checking out a rule to a private RuleSet, use Check In
to copy the modified rule over the original in the public RuleSet.
Check Out This button appears only for rules in RuleSets subject to rule
management. Creates a copy of a rule in your private RuleSet and marks
the original rule as checked out. No one else can check out a rule while it
is checked out.
Delete Deletes a rule or data instance.
Delete Check-out Delete a checked-out rule from your personal RuleSet.
Favorites Adds to a user’s Favorites in Internet Explorer or allows a user to delegate

a rule using the My Rules feature.
Help Opens the Help window for the currently displayed rule or data form.

Preview Splits the workspace to present a partial preview of the runtime
appearance of a rule in the bottom half.
Private Check In For a privately checked out rule in your personal RuleSet, opens the
Check In Rule dialog so you can copy the modified instance to a specified
unlocked destination.
Private Check
Creates a copy of a rule in your personal RuleSet.
Out
Recover Recovers the most recent version of a deleted rule, if the RuleSet and
version are unlocked.
Refresh Refreshes the browser display with the latest data in the PRPC server.
Any inputs you have entered but not sent are lost.
Related Rules Lists rules related to the current rule. Clicking displays a menu that lists
lower-numbered versions of the currently open rule, circumstance and
circumstance-date, editions and additional menu items.
Restore Replaces the current checked-in copy of a rule with the last checked-in
copy of that rule.
Rule Data Shows the XML document that makes up the form displaying this instance.
This is primarily a debugging tool.
Run Starts execution or testing of the current rule, in the current context.
Save Saves the instance to the PegaRULES database.
Save As Saves the instance under a different name, RuleSet or version.
Show Java After a rule is saved, approximation of the generated Java to be created by
this rule instance appears in a new window. (You cannot alter this Java
code.) This button is visible only to developers who hold the privilege
@baseclass.ToolbarFull. Available for activities, When rules and stream
rules, among others.

Visio Tools Display or hide, Visio toolbars during Visio editing.
Zoom In (Visio) Zoom in on the Visio diagram, to make the diagram larger.
Zoom Out (Visio) Zoom out from the Visio diagram, to make the diagram smaller.
Workspace Toolbar Buttons

Glossary V62 SP2

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Glossary V62 SP2

Загружено:

Авторское право:

Доступные форматы

 Copyright 2012

Pegasystems Inc., Cambridge, MA

This document is the property of:

Phone: (617) 374-9600

agent A background process that monitors conditions and performs processing as

authentication The process of determining the identity of a user or requestor of services. In

circumstance A way to create multiple versions or variants of a rule based on a specific

declarative A rule that allows developers to model relationships between properties so

dependency An internal data structure that supports forward chaining or automatic

directed An inheritance method that causes a class to inherit characteristics directly

gesture A movement or touch-based user interaction with an application on a mobile

likelihood A value between 1 and 100, interpreted as an assumed or known probability

listener A background Java thread that monitors a TCP/IP port, a mailbox, a

perform A description of what users usually do as they work on assignments (as

predictors Properties considered to have a predictive relationship with the outcome.

Process Architect See Business Architect.

requirement An inventory of events, conditions or functions that need to be satisfied and

reusable A characteristic of a software component that supports a general-purpose

score band A set of score intervals.

Simple Object An XML-based protocol used to exchange information in a decentralized,

Smart Layout A grid (corresponding to an HTML <TABLE> element) of paired cells on a

spin-off A feature used to execute another flow asynchronously and independently

solution Industry-specific applications that provide a head start to application

workers A role that defines the behavior and responsibilities of an individual or a

The Developer Toolbar

Toolbar Buttons and Functions

Name Button Function

Delete Deletes a rule or data instance.

Delete Check-out Delete a checked-out rule from your personal RuleSet.

Favorites Adds to a user’s Favorites in Internet Explorer or allows a user to delegate

Name Button Function

Save Saves the instance to the PegaRULES database.

Save As Saves the instance under a different name, RuleSet or version.

Name Button Function

Workspace Toolbar Buttons

Вам также может понравиться