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