What's new in Pega 7.1.

The PDN provides overview articles, best-practice solutions to common development

challenges, news of the latest product features, access to the latest version of the product help
documentation, and many more learning resources.

Learn from the experts. Pega Academycourses provide design and implementation best
practices that cover Pega 7 Platformapplication development as well as specialized topics.

Pega Academy courses provide the knowledge and hands-on experience that you need to
successfully design and deploy Pega 7 Platformsolutions.

These courses also prepare you to become a Pega Certified Professional.

User Dynamic containers and screen layouts have WAI-ARIA roles assigned by default.
interface WAI-ARIA roles provide information about the user interface to assistive
technologies.

Dynamic layouts can be assigned one of a variety of WAI-ARIA roles to support

accessibility.

Portal-level links allow users to skip non-essential content and tab directly to main
content, search, or navigation elements.

Case Add a user reference to a form to prompt caseworkers to search for an existing user
managemen as they process a case.
t
Integrate data with cases by referencing a data type on a form.

Reuse fields and forms in Form Builder to create forms that are easier to maintain.

The search field type in Form Builder is deprecated.

Pega 7 Switch from Designer Studio to express mode to quickly develop new applications in
Express the Pega 7 Express environment. Some limitations apply.

Create an express application for yourself or invite another user to explore Pega 7
Express.

Export your express applications to share with others or to migrate to a different

system.

Note: Trial versions of Pega 7 Express continue to be available on the cloud. To view the
documentation for both the cloud and on-premises environments, see Getting started
with Pega 7 Express.

Project You can now enable a historical specification count and implementation progress by
delivery complexity and business impact (Designer Studio > Application > Profile > Analysis).
You can view specification count filtered by complexity and business impact, as well
as counts, by business objective, of specifications that have been implemented and
those that have not.

Specifications can now be filtered by release and iteration (Designer Studio >
Application > Profile > Specifications).

Project stakeholders can now track an applications compliance score over time to
better understand and manage ongoing development adherence to Pega 7 Platform
guardrails. The compliance score history can be displayed on a line graph on the
Compliance Score tab of the Application Guardrails landing page (Designer Studio
> Application > Guardrails > Compliance Score).

The project sizing template used by the Application Sizing Wizard now includes a
column for business impact. Project owners can now incorporate this assessment into
their project sizing.

For more information, see:

Application Profile Analysis tab

 Application Specifications - Completing the Details tab

Enabling compliance score history

Decision Use the text analytics functionality for sentiment, classification, and entity extraction
managemen analysis. Create an instance of the Free Text Model rule and reference it in a data
t flow. Analyze text-based content, including news feeds, emails, and postings on
social media streams, such as Facebook, Twitter, and YouTube.

Process real-time events with the Event Strategy rule. Create an instance of the
Event Strategy rule and reference it in a data flow. Use event strategy to detect
meaningful events in a stream of real-time data and react to the detected events in a
timely manner.

Use the PMML upload wizard in the Predictive Model rule form to upload external
models in PMML format. Validate the models and receive immediate feedback when
they contain errors. Use the enhanced error messages and the Model XML preview in
the rule form to fix errors.

Set report definitions as primary and secondary sources in data flows.

When using a Database Table data set as the destination of the data flow, you can
specify whether to insert new records or insert new records and overwrite the
existing ones.

Run simulations and test strategies for single and multiple customers. Identify the
most popular propositions offered to customers, check the overall strategy
performance, and examine the performance of the individual components.

Mobility To integrate with device peripherals (Bluetooth devices, printers, scanners), you can
build Pega Mobile Client with custom modules by using the build server.

You can turn a Pega 7 Express app into a mobile app with a single click.

New Pega Mobile Client debugging options are available at both design and run time.
See Mobile settings reference and Troubleshooting Pega Mobile Client on the PDN for
more information.

Offline Upload PDF files to the Pega 7 Platform as binary files so that they can be viewed
mobility offline when added to the cache manifest. See also Ability to view a PDF file while
offline on the PDN.

Address map control displays a live Google map with location pins for a list of
addresses when online and defaults to a static map image when offline.

Create the JavaScript equivalent of pre- and post-processing on flow actions that will
run in a mobile app while offline.

Use parameterized data pages to configure cascading drop-down lists on any screen
in a mobile app while offline.

Use a declarative property to get the current date and time on a mobile client while
offline.

Core engine You can now use cluster-based pulse processing, which immediately updates rule
changes across all nodes in a system after they are saved.

Multinode development environments now use real-time pulse processing, where rule
changes are immediately reflected on all the other nodes in the cluster.

Applications running in High Availability mode use database pulse by default, allowing
for persistent storage for passivation and providing control for the High Availability
landing page.

You can verify whether a Pega 7 Platform instance is up and running by entering this
URL:http://<<hostName:port/contextName>>/PRRestService/monitor/pingservice/p
ing
 Integration The name of Internet Application Composer (IAC) has changed to Pega Web Mashup.

When using SSH FTP (SFTP) in an FTP server record, you can securely transfer files
by using SSH keys. You can enable and configure SFTP on the Protocol section of
the Environment tab.

You are here: Deprecated features

Deprecated features
The following features are deprecated. Do not use them in new development. Adopt replacement features
where available.
Rule types
Deprecated Replacement
Rule-Admin-Product-Patch Products

Rule-Connect-BPEL SOAP

Rule-Declare-Collection Specifically, instances using

the original rule form implementation.

Rule-Declare-Constraint Constraints

Rule-Declare-Expression Declare Expressions

Rule-Define-Hierarchy Navigation

Rule-File-Form, Form Builder Harnesses and Sections

Rule-HTML-FixedList Properties

Rule-Obj-JSP Any other stream rule such

as HTML or XML

Rule-Parse-Infer @pxReplaceAllViaRegex function

Rule-Parse-Transform @pxReplaceAllViaRegex function

Rule-Parse-TransformCollection @pxReplaceAllViaRegex function

Rule-Report-*** Report Definitions

Rule-RDB-SQL Connect-SQL

Rule-Service-BPEL SOAP

Rule-Service-COM dotNet

Rule-Query-List Report Definitions

Rule-Query-Summary Report Definitions

 Rule-Service-CORBA Any other service type such
as SOAP, EJB, or HTTP

Note: Deprecated rule types and instances are excluded from specific Designer Studio features.

Data types
Deprecated Replacement
Data-Admin-ClassGenerator Connector and Metadata Accelerator output

Data-Admin-ConnectGenerator Connector and Metadata Accelerator output

Data-Customer Data-Party-COM or Data-Party-Person

Activity Methods
Deprecated Replacement
Apply-Model Apply-Data-Transform

Assign-Delete

Assign-EstablishContext

Index-Finish Declare Index

Link-List

Obj-List Obj-Browse and Obj-Filter

Obj-Set-Tickets The setTicket activity

Property-Set-Special Property-Set

Rule instruction The evaluateRule activity

Show-Applet Show-Page

Show-Applet-Data Show-Property

Wait-for-Connector Connect-Wait

Controls
Use the Update Control feature to automatically upgrade these deprecated controls found in sections and
harnesses. Buttons with custom settings must be manually converted to use the pxButton control.

Deprecated Replacement

TextArea TextAreaWithExpand pxTextArea

TextAreaSmall TextAreaInTable TextAreaExpandedOverflow
TextAreaWithExpandSmall TextAreaWithExpandExpanded
TextAreaExpanded
 Date-Calendar pxDateTime
DateTime-Short-i18n
DateTime-Calendar
Date
DateTime-
CalendarHarness Date-Full
DateCalendarForDataGrid Date-Long
Export_Date Date-Medium
Export_DateTime Date-Short
SecondsToHours Date-Full-i18n
SelectDate Date-Medium-i18n
SelectDateTime Date-Short-i18n
DateTime Time
DateTime-Default Time-Default
DateTime-Full Time-Medium Time-Short
DateTime-Long TimeElapsed-HMS
DateTime-Medium TimeZoneList
DateTime-Short Time-Full-i18n
DateTime-Full-i18n Time-Long-i18n
DateTime-Long-i18n
Time-Medium-i18n
DateTime-Medium-i18n
Time-Short-i18n

PromptSelect pxDropDown
DynamicSelect

RichTextEditor pxRichTextEditor

AutoComplete pxAutoComplete

URL pxLink

Checkbox pxCheckbox

RadioButtons pxRadioButton

Button pxButton

Note: More information is available in the PDN article Upgrading deprecated and outdated controls.

Local data
Data tables are replaced by local data storage.

Other
Deprecated Replacement
02 API 03-02 API

Application Accelerator tool New Application wizard

Application Document tool Application Document wizard

Application Profiler tool Application Profile landing page

Authentication Wizard Incorporated into the process of creating a

new integration

Business Events
Create Properties wizard Configuration Grid on the Definition tab of a
data type, viewed in the Data Designer.

Libraries named Default Use a descriptive name when creating a new

library

$mode-display in HTML code !mode-input

Monitor Activity workspace Standard reports based on report

definitions are available in the Report
Browser.

Override rulesets Production rulesets

Organization and division data instances that are Select an Application-based Access
defined by an Explicit RuleSet list. Group on the Access tab of these rule forms.

Organization Setup wizard New Application wizard

Amount property type Decimal property type

Search fields in Form Builder

Data references
User references

startOrStopTimer(String, boolean) PAL method

Status stage Stages and Steps

Six R's landing page

UI Inspector tool Live UI tool

UI Tree tool Live UI tool

Using this help system

This help system provides reference and guidance information for application developers. Suggestions and
comments are welcome. Submit feedback on the Global Customer Support web site (pdn.pega.com) by
clicking Support > My Support Portal.
Toolbar
Every help topic has a toolbar from which you can do the following:

- View the previous topic. Equivalent to the browser back action.

- Go to the next topic. Equivalent to the browser forward action.

- Print the current topic. For supported versions of Microsoft Internet Explorer, you must
click Options > Only the selected frame.

- Remove highlights from search results.

- Collapse or expand drop-down text.

Styles
Controls, such as field, button, and tab labels on rule forms, appear in bold.
References to specific standard rules and data instances appear in this format pyDefault.
HTML, JavaScript, and Java code snippets appear in this font, with a gray background.

Finding information in the help

Use the Contents, Index, or Glossary tabs to find a topic of interest.
When looking for specific content by using the Search field, it can be helpful to decide if you want to find
topics that contain any of the words that you enter or all of the words that you enter. The default behavior
is to return all the topics that contain any of your words.
To get a shorter, more focused list of potential topics in your search results, use AND between your search
words. Note: You can use + or & instead of AND.
For example: custom AND rule
To search for an exact phrase, enclose all of your words in quotation marks.
For example: "custom rule"

Contacting Pegasystems

On the web
On the Pegasystems (www.pega.com) home page, click Contact. Complete the Contact Us form to ensure
that your query reaches the person or team that can best respond to it.

By mail
Pegasystems
Attn: Product Management
One Rogers Street
Cambridge, MA 02142-1209
USA

By phone/fax
US: +1 (617) 374 9600 (voice)
US: +1 (617) 374 9620 (fax)
UK: +44(0) 118 9591150
AU: +61 2 9581 7000

Visit the PDN

The Pega Discovery Network (pdn.pega.com) (PDN) is a community that provides advice, tips, forums, and
how-to topics for anyone who develops Pega 7 Platform applications.

Contact Global Customer Support (GCS)

On the PDN, click Support > My Support Portal.

Provide documentation feedback

Documentation and help system suggestions and comments are welcome. Submit feedback through My
Support Portal.
Partner with us
Pegasystems has technology partners, solution partners, and services partners. To learn more, visit the
Partnerships web page at www.pega.com/services/partnerships.

Copyright and trademark notices

Copyright
Copyright 2015 Pegasystems Inc. All rights reserved.

Trademarks
For Pegasystems Inc. trademarks and registered trademarks, all rights reserved. Other brand or product
names are trademarks of their respective holders.
For information about the third-party software that is delivered with the product, refer to the third-party
license file on your installation media that is specific to your release.

Notices
This publication describes and/or represents products and services of Pegasystems Inc. It may contain
trade secrets and proprietary information that are protected by various federal, state, and international
laws, and distributed under licenses restricting their use, copying, modification, distribution, or transmittal
in any form without prior written authorization of Pegasystems Inc.
This publication is current as of the date of publication only. Changes to the publication may be made from
time to time at the discretion of Pegasystems Inc. This publication remains the property of Pegasystems
Inc. and must be returned to it upon request. This publication does not imply any commitment to offer or
deliver the products or services described herein.
This publication may include references to Pegasystems Inc. product features that have not been licensed
by you or your company. If you have questions about whether a particular capability is included in your
installation, please consult your Pegasystems Inc. services consultant.
Although Pegasystems Inc. strives for accuracy in its publications, any publication may contain inaccuracies
or typographical errors, as well as technical inaccuracies. Pegasystems Inc. may make improvements
and/or changes to the publication at any time.
Any references in this publication to non-Pegasystems websites are provided for convenience only and do
not serve as an endorsement of these websites. The materials at these websites are not part of the material
for Pegasystems products, and use of those websites is at your own risk.
Information concerning non-Pegasystems products was obtained from the suppliers of those products, their
publications, or other publicly available sources. Address questions about non-Pegasystems products to the
suppliers of those products.
This publication may contain examples used in daily business operations that include the names of people,
companies, products, and other third-party publications. Such examples are fictitious and any similarity to
the names or other data used by an actual business enterprise or individual is coincidental.
This information is the property of:

Pegasystems Inc.
One Rogers St.
Cambridge, MA 02142-1209
USA
Phone: 617-374-9600
Fax: 617-374-9620
www.pega.com
Glossary
area chart business day
Tip: Click the Glossary tab as-of date processing business exception
to view all terms in a Assign- base class Business Intelligence
navigation pane. In this view, Exchange (BIX)
you can quickly search for a assignment
term or keep the full list of business process
assignment statistics
terms in focus as you read management (BPM)
the definition of an individual assignment status
Business Rules Engine
term. associated ruleset (BRE)

A association Business Value

Assessment (BVA)
Asynchronous
abstract class JavaScript and XML BVA
(AJAX)
access group
C
attachment
Access Manager
attachment category
access role Calculation Builder
attachment type
acknowledgment calendar
audit trail
action section case
authentication
active property Case Designer
autocomplete field
activity case instantiation
auto-generated HTML
activity list Case Management
Autonomic Event
activity type Services (AES) Case Manager portal

actor auto-populated case type

ad hoc case property Case Type Explorer

AES AV mode case-type

available rule dependency
age
available user Center of Excellence
agent
Certified System
aggregate property
B Architect (CSA)
AJAX Chart Editor
alert event back-to-back
check in
assignments
alert log check out
backward chaining
alternate path child case type
bar chart
application circumstance
base class
application bundle class
base rule
application document class group
best bets
Application Document class inheritance
wizard BIX
class name prefix
Application Explorer blocked rule
classification
application name BPM
clipboard
application profile branches and branch
rulesets Clipboard tool
application rule
BRE cluster
application ruleset
breadcrumbs control Code- base class
application scoping
control bubble chart collaboration flow

Application Validation build order collection rule

(AV) mode
bulk processing column chart
archives
business architect Column Populator
 combo chart database table express actions
DataGrid controls express application
committed hotfix
DataSource express mode
common name
DCO expression
compensating action
deadline extension point
compliance score
decision rule conflicts external assignment
component ruleset
decision shape external class
composite portal
decision table external operator
composition grid
decision tree external system
concrete class message
declarative rule
connection pooling extract marker file
delegated rule
connector
dependency network F
constraint
deployment
contact preference descriptor failover
container class Designer Studio family name
Content Security Direct Capture of favorite
Policy Objectives (DCO)
FCM
context-free Direct Feedback
expression feature FCMR

correspondence directed inheritance Federated Case

Management (FCM)
correspondence type Directed Web Access
(DWA) Federated Case
cover Management
credentials directive Repository (FCMR)

CSA division file attachment

current application draft mode filter

custom fields duplicate final rule

customer DWA final rule conflicts

customer satisfaction dynamic layout flow

cycle time Dynamic Select flow action

control
flow connector
D
E flow error

daemon flow marker

effort
dashboard flow model
eForm rule
Data- base class flow name
elasticsearch
Data Designer folder
Embed- base class
data instance follow
embedded page
data mapping form
enterprise application
data pages on the Form Builder
clipboard entry
forward chaining
data record entry point
fragment
data reference escalation
framework application
data table exceptions
management
framework class
data transform rule framework layer
expired page
data type free text rules
exposed property
 full description intent-driven local system
processing local variable
function rule interactive chart
locale
funnel chart interest page
locatable page
interested party
G lock
internal class
Log- base class
gauge chart internal key
lookup list cache
geolocation internal rule
LSA
global resource iteration
setting M
goal J

grid controls major version

Java date pattern
grid layout map
Java identifier
Group Builder map value
Java object property
guardrails mode
master agents

guided tour Java Property mode

mathematical
operators
H K method
method status
handle key part minor version
harness keyring file mixin
headless application keystore mobile portals
heat map
L mobile preview
hierarchy
modal dialog
hierarchy rule node landing page Modal Dialog
historical processing landing page gadget Templates
History- base class language pack modal flow
history type language-specific Model-View-Controller
ruleset pattern
hotfix catalog
layout groups multitenant system
I My Rules
Lead System
Architect (LSA)
identifier N
library
implementation class
License Compliance named user
implementation layer
lightweight list navigation panel
implementation
methodology likelihood New Application
Link- base class wizard
index
linked property Node ID
Index- base class
list view Not a Number (NaN)
indirect page
listener note attachment
instance
load-balancing notify activity
instruction
integration services local customization
O
ruleset
integrator shape
local data storage
intelligent routing occasional user
local flow action
one-and-done
 OOTB Pega Mobile Project Worklist
Pega Mobility property
open assignment
Pega Pulse property message
open authoring
Pega Web Mashup property mode
open instance
PegaAccel- base class property name prefix
open work item
PegaCALL Property Optimizer
operator
PegaDISTRIBUTION property page modes
operator menu Manager (PDM)
property qualifier
operator profile PegaIMAGE Manager
display property reference
PegaRULES database
optimized property property stream
PegaRULES Log
organization Analyzer (PLA)
property validation

organization unit pending status

property value modes

organizational ruleset PublicAPI

perform
out of the box rule Performance tool
pulse
(OOTB) pyramid chart
persistent object
overlay
Personal Edition Q
override
personal ruleset
owner of work items
pinned class Queue Manager

P PLA Quick create

platform
R
package
PMF
page
policy override Record
Page group
poolID record editor
Page list
portal redirected rule
page message
prconfig setting refactoring
page name prefix
prconfig.xml file reference property
page validation status
precondition Referencing Rules
panel set
preference regular expression
paragraph
prefix regular user
parallel processing
primary page reject
parameter
primary path remote logging
parent flow
privilege remote system
passivation
prlogging.xml file reopen
password hashing
problem assignment Report Browser
patch version
Process API report category
pattern inheritance
process architect report definition rule
PDM
Process category Report Editor
Pega 7 Express
Process Outline View Report List
Pega Cloud
process page report shortcut
Pega composite
production level Report Usage landing
application
page
Pega composite
production ruleset
Report Viewer
application gadget Project Management
Framework (PMF) reporting
Pega log
 reports database screen shot Storage Stream
attachment straight-through
requestor section processing
requestor ID security auditing stream processing
requestor page security role subprocess
requestor scheme server node subreport
requestor type service subscription
required field service activity summary view rule
requirements service invocation Survey Builder
resolution service package suspended work
resolution quality items
ServiceExport
Resource Kit directory SWIFTNet

responsive behavior service-level swimlane

agreement
results page symbolic date
shared ruleset
reusable rules system administrator
Short Description
rollback hotfix system architect
shortcut rule
root cause System- base class
sibling
router activity system ID
single value
rule System Management
skill application (SMA)
rule attachment
skim
Rule- base class T
skin rule
rule cache
SMA table
rule form
smart layout tag
rule- message
instance SmartInfo target property

rule resolution SmartPrompt technical category

rule status space template rules

rule type spark chart temporary files

special property directory
rule version prefix
specification temporary work item
rules assembly
spinoff tenant
Rules Assembly cache
split button Test ID property
ruleset list
Split For Each shape Test Management
ruleset name Framework (TMF)
ruleset version Split Join shape
text direction
ruleset version prefix SQL function alias
thread
stage
S
threshold
stage step
throughput
standard rules
sample application ticket
starter flow rule
sampling timeliness
static assembler
scheduled task time-qualified rule
static content
schema TMF
status
scratchpad toolbar
step
screen flow top-level case
step page
screen layout
 top-level class W

top-level page
Wait shape
Tracer tool
warning
traditional portal
web node
transfer
When condition rule
transient property
Where-am-I?
transition
white list testing
tree grid layout
withdrawn rule
tree layout
Work- base class
trend report
work group
trigger
work item
trigger rule
work item ID
type
work item ID prefix
U work item status
work manager
ultimate base class
work party
uncommitted hotfix
work party role
unoptimized property
work pool
Update Controls
work pool name
urgency
work queue
urgent work
work type
URL obfuscation
workbasket
usage daemon
worklist
usage report
workspace
user action
user interface events
user page
user reference
user role
Utility shape

validate rule
Value Group
Value List
verbalization

verify
version
vertical cluster
view
Virtual File Interface
visible key
Case Manager portal Using My Cases

The My Cases page in the Case Manager portal initially displays, in the top-level nodes of a tree grid, all
cases where the following are true:
The case is in one of the operator's work pools, is not resolved, and is not covered by another case.
The current operator is a party to that case. The node does not appear if the current operator is a
party to only a child case but not to the top-level case.

Expanding a node shows the child cases.

Cases on this page refer to work instances belonging to case types defined on the Case Type Explorer, and
use the same case-type icons. You can change the default icons using the Appearanceoption on
the Detailstab in the Case Designer landing page.
To ensure that an operator's cases appear in this tab, name the operator in a work party rule referenced in
the Work Parties Rule field on the top-level case type rule's Processes tab. Use theDetails tab for a case
type in the Case Designer landing page to edit this work party rule.
The case information, collected in the new case work harness, is displayed under the following fields:

Heading Description
Name
Name of the case type as it appears in the Case Type Explorer. If available, appends
the customer name (.pyCustomerName) to the case name. If the item is ad hoc work,
the name is New ad hoc work for: <case type name>.
Two or more child cases of the same type with the same parent are nested beneath
the child case name.

Item ID
The unique identifier assigned by the application to this case. A prefix or suffix portion
of this identifier can help users remember the application or work type. By default, ad
hoc instances use the prefix "C-". See Understanding work item IDs.

My Roles
The work item owner. See Ownership.

Creation
The date and time the case was created by the user or by the system.
Date

Urgency
Indicates the case's urgency value. By default, a value of 10 is considered of normal
priority. A red urgency clock in the row header indicates that the item has an urgency
value equal to or greater than 60. A yellow urgency clock indicates an urgency value
from 30 to 60. The rest are indicated by a green urgency clock.

Deadline
For this case, the time remaining from the current time to the overall deadline time, or
the time elapsed from the deadline to the current time. The deadline time is specified
this case type's service-level agreement (.pyCaseTypeDefault), used by the
.OverallSLA flow.
You can set goals and deadlines on the Service-level agreement form or in the Case
Designer. The time appears in yellow if the case has exceeded its goal but not its
deadline; in red if the deadline is exceeded. A blank value in this field indicates that
the Goals and Deadlines option has not been initialized, or that the service level rule is
not present in this case type class.
See Using the Case Type Explorer.

Status
This item's work status (property Work-.pyStatusWork).

The case-level and expanded child case lists use the Work-pyMyCasesReport and the Work-
.pyLoadMyCasesNested report definitions, respectively. By default, the lists show a maximum of 500 items.
You can modify this value by copying the rules and updating the Maximum Number of Rows To
Retrieve field in the Data Access tab.
The user can do the following in the grid:
Double-click an item to open its review user form in a separate tab on the portal.
Select an item to display the user form's work summary section in an embedded pane beneath the
grid.
Click a breadcrumb link in summary section's child case header to open a parent case.

Quick Create
The Quick Create feature lets users create ad hoc cases to track work that is not instantiated from the
current application's case type structure. See Working with ad hoc cases.
Case list actions
The user can perform the following actions by right-clicking an item and opening a context menu.

Selection Description

Open
Open review user form .

Complete Item
Resolve this case. Status becomes Resolved-Completed.
The user cannot manually add a child case to a
completed case.
If this case has child cases, the Would you like to
mark all the child cases as Complete? field appears.
The user selects the Yes radio button (default) to
resolve them (includes direct and nested child cases). To
resolve only the selected case, the user selects No.
If one or more of the child cases must be resolved
before the parent, and the user selects Yes, the system
displays an error message indicating which child case(s)
must be resolved. The system does not resolve any of
the child cases.

Withdraw Item
Reject and withdraw this case. Status becomes
Resolved-Withdrawn. The user cannot manually add a
child case to a withdrawn case.
The user can resolve all child cases as described in
the Complete Item above.

Configure for reuse

This option is available only for ad hoc cases, and
appears only if the operator's access group references
the standard pyPega-ProcessEngine:CaseDesigner role,
which contains the privilege .pyCaseInstitutionalize. The
option enables an operator to convert ad hoc case to a
case types in the current application's case type
structure.
See Working with ad hoc cases.

Actions
Enables the user to start local or connector flow actions
defined in the flow. The menu also provides an Add Work
submenu, so that user can add child cases to the current
case , or start processes that support this case.
See Working with ad hoc cases.
Create Ad Hoc Case
Create an ad hoc child case under the parent case or
another ad hoc case. See

After performing an action on this tab, the user can click Refresh to refresh the current page.
The sections in the My Cases tab can be localized to suit your requirements.

Portals in applications

portals, case, assignment, flow

About the Case Manager portal

About Portal rules
Portals for application users
Using the Case Type Explorer

, :
,
.
. ,
, .

.
, ,
Case Type Explorer, .
,
.

, ,
,
.

To ensure that an operator's cases appear in this tab, name the operator in a work party rule referenced in
the Work Parties Rule field on the top-level case type rule's Processes tab.
Case Designer,
.
Use theDetails tab for a case type in the Case Designer landing page to edit this work party rule.
, ,
:

Heading Description
Name
Name of the case type as it appears in the Case Type Explorer. If available, appends
the customer name (.pyCustomerName) to the case name. If the item is ad hoc work,
the name is New ad hoc work for: <case type name>.
Two or more child cases of the same type with the same parent are nested beneath
the child case name.
 Item ID
The unique identifier assigned by the application to this case. A prefix or suffix portion
of this identifier can help users remember the application or work type. By default, ad
hoc instances use the prefix "C-". See Understanding work item IDs.

My Roles
The work item owner. See Ownership.

Creation
The date and time the case was created by the user or by the system.
Date

Urgency
Indicates the case's urgency value. By default, a value of 10 is considered of normal
priority. A red urgency clock in the row header indicates that the item has an urgency
value equal to or greater than 60. A yellow urgency clock indicates an urgency value
from 30 to 60. The rest are indicated by a green urgency clock.

Deadline
For this case, the time remaining from the current time to the overall deadline time, or
the time elapsed from the deadline to the current time. The deadline time is specified
this case type's service-level agreement (.pyCaseTypeDefault), used by the
.OverallSLA flow.
You can set goals and deadlines on the Service-level agreement form or in the Case
Designer. The time appears in yellow if the case has exceeded its goal but not its
deadline; in red if the deadline is exceeded. A blank value in this field indicates that
the Goals and Deadlines option has not been initialized, or that the service level rule is
not present in this case type class.
See Using the Case Type Explorer.

Status
This item's work status (property Work-.pyStatusWork).

The case-level and expanded child case lists use the Work-pyMyCasesReport and the Work-
.pyLoadMyCasesNested report definitions, respectively. By default, the lists show a maximum of 500 items.
You can modify this value by copying the rules and updating the Maximum Number of Rows To
Retrieve field in the Data Access tab.
The user can do the following in the grid:

Double-click an item to open its review user form in a separate tab on the portal.

Select an item to display the user form's work summary section in an embedded pane beneath the
grid.
Click a breadcrumb link in summary section's child case header to open a parent case.

Quick Create
The Quick Create feature lets users create ad hoc cases to track work that is not instantiated from the
current application's case type structure. See Working with ad hoc cases.
Case list actions
The user can perform the following actions by right-clicking an item and opening a context menu.

Selection Description

Open
Open review user form .

Complete Item
Resolve this case. Status becomes Resolved-Completed.
The user cannot manually add a child case to a
completed case.
If this case has child cases, the Would you like to
mark all the child cases as Complete? field appears.
The user selects the Yes radio button (default) to
 resolve them (includes direct and nested child cases). To
resolve only the selected case, the user selects No.
If one or more of the child cases must be resolved
before the parent, and the user selects Yes, the system
displays an error message indicating which child case(s)
must be resolved. The system does not resolve any of
the child cases.

Withdraw Item
Reject and withdraw this case. Status becomes
Resolved-Withdrawn. The user cannot manually add a
child case to a withdrawn case.
The user can resolve all child cases as described in
the Complete Item above.

Configure for reuse

This option is available only for ad hoc cases, and
appears only if the operator's access group references
the standard pyPega-ProcessEngine:CaseDesigner role,
which contains the privilege .pyCaseInstitutionalize. The
option enables an operator to convert ad hoc case to a
case types in the current application's case type
structure.
See Working with ad hoc cases.

Actions
Enables the user to start local or connector flow actions
defined in the flow. The menu also provides an Add Work
submenu, so that user can add child cases to the current
case , or start processes that support this case.
See Working with ad hoc cases.

Create Ad Hoc Case

Create an ad hoc child case under the parent case or
another ad hoc case. See

After performing an action on this tab, the user can click Refresh to refresh the current page.
The sections in the My Cases tab can be localized to suit your requirements.

Portals in applications

portals, case, assignment, flow

About the Case Manager portal

About Portal rules
Portals for application users
Using the Case Type Explorer

case, case. ,
(.pyCustomerName) . , :
: < >.

.
Item ID
, .
.
C-. .
.

. . .

.

. 10 .
,
, 60. 30
60. .

, , ,
.
(.pyCaseTypeDefault), .OverallSLA.

. , , ; ,
. ,
case.
. .

( Work-.pyStatusWork).
case-level Work-
pyMyCasesReport Work-.pyLoadMyCasesNested, .
500 . ,
.
:
,
.
,
.
breadcrumb ,
.

Quick Create
, case . .
.

,
.

.

 . -.
.
, ?
. ( )
( ). ,
No.
,
, , , ()
. .

. - .
.
, .

,
pyPega-ProcessEngine: CaseDesigner,
.

Configuring cases for reuse

The Configure for Reuse feature is useful where the operator repeatedly uses ad hoc cases to process
specific exceptions. If these exceptions become routine, the operator may decide to copy the ad hoc case
structure (top-level or child) to the application's case type structure without the assistance of an application
developer. When invoked, the system automatically creates the case type and its default case type, starter
flow, work parties, and activity rules.
This feature is available only if the operator's access group references the standard pyPega-
ProcessEngine:CaseDesigner role, which contains the privilege .pyCaseInstitutionalize.
Verify that the current application contains an unlocked RuleSet version.
The operator can access the feature by:

Clicking the Configure for Reuse icon on the Ad Hoc Case Dashboard assignment.
Selecting a case on the My Cases list and using the Configure for Reuse right-click menu.
Clicking the Configure for Reuse button on a user form header.

When the user selects this option, the Configure for Reuse dialog appears.
If the ad hoc case is a top-level case or has no children, the system converts the ad hoc case to a
top-level case type. The name of the new case type can be edited in the text field.
If the ad hoc case is a parent, the dialog lists the ad hoc child cases. Select the Include check box
to convert the child cases to child case types in the case management structure. The names of the
new case types can be edited in the text fields.
If the ad hoc case is a child of a standard case (case type instance), the dialog displays radio
buttons that let you choose to convert the case to a top-level case or a child case of the current
parent. Edit the name of the new case type in the text field.

When the user clicks OK, the new case type appears in the Case Type Explorer.

Portals in applications

portals, case, assignment, flow

 About the Case Manager portal
About Portal rules
Portals for application users
Using the Case Type Explorer

Configure for Reuse ,
. ,
( )
.
case , , .
, pyPega-
ProcessEngine: CaseDesigner, .pyCaseInstitutionalize.

, RuleSet.
:

Case.

.
.
,
.
ad hoc ,
ad hoc . .
ad hoc , ad hoc child.
,
. .
ad hoc ( case),
,
. case
.
, case .

, , ,
Case Manager


Case