Professional Documents
Culture Documents
Pega Fast Start Guide PDF
Pega Fast Start Guide PDF
Copyright 2013
Pegasystems Inc., Cambridge, MA
All rights reserved.
This document describes products and services of Pegasystems Inc. It may contain trade
secrets and proprietary information. The document and product are protected by copyright
and distributed under licenses restricting their use, copying distribution, or transmittal in
any form without prior written authorization of Pegasystems Inc.
This document is current as of the date of publication only. Changes in the document may
be made from time to time at the discretion of Pegasystems. This document remains the
property of Pegasystems and must be returned to it upon request. This document does not
imply any commitment to offer or deliver the products or services described.
This document may include references to Pegasystems product features that have not been
licensed by your company. If you have questions about whether a particular capability is
included in your installation, please consult your Pegasystems service consultant.
For Pegasystems trademarks and registered trademarks, all rights reserved. Other brand or
product names are trademarks of their respective holders.
Although Pegasystems Inc. strives for accuracy in its publications, any publication may
contain inaccuracies or typographical errors. This document or Help System could contain
technical inaccuracies or typographical errors. Changes are periodically added to the
information herein. Pegasystems Inc. may make improvements and/or changes in the
information described herein at any time.
This document is the property of:
Pegasystems Inc.
One Rogers Street
Cambridge, MA 02142-1590
Phone: (617) 374-9600
Fax: (617) 374-9620
www.pega.com
PegaRULES Process Commander
Document: Fast Start Guide
Software Version: 6.2 SP2
Updated: January 23, 2013
Contents
Chapter 1: Overview .................................................................................... 6
Business Process Management ................................................................................................. 6
Structure of This Document ...................................................................................................... 7
Knowledgebase and Community .............................................................................................. 8
Prerequisites ................................................................................................................................. 8
Decisions ...................................................................................................................................... 91
Tables....................................................................................................................................... 91
VPApproveOrder ............................................................................................................... 91
Trees ........................................................................................................................................ 92
Manager Review................................................................................................................ 92
Map Values.............................................................................................................................. 92
Whens ...................................................................................................................................... 92
ItemPrice ............................................................................................................................ 92
Security ............................................................................................................................................ 92
SLAs ................................................................................................................................................ 93
Activities ........................................................................................................................................... 93
Properties ......................................................................................................................................... 93
Declaratives ................................................................................................................................ 94
Expressions ............................................................................................................................. 94
.LineItemTotal ................................................................................................................... 94
.OrderTotal ......................................................................................................................... 94
Triggers ................................................................................................................................... 95
OnChange ............................................................................................................................... 95
Constraints.............................................................................................................................. 95
Specifications Matrix............................................................................................................................ 95
Chapter 1: Overview
Welcome to the Fast Start Guide. This book introduces PegaRULES Process
Commander (PRPC) and provides hands-on instructions for modifying an application
built on PRPC. It also introduces terms and skills for application developers.
The hands-on tasks involve working with a small application called ASupply. The
application allows employees of ASupply to submit purchase order requests using their
Web browser and it automates the process of entering, routing, and approving
purchase orders.
The ASupply application is intentionally incomplete and simplified. Your assignment is
to make changes and enhancements to it. The tasks presented in this book show you
how to extend the application by adding and modifying rules to meet the needs of
ASupply. By following these exercises, you will learn to:
Create rules that enhance the application user interface and behavior.
Produce a Microsoft Word document that describes the application and lists its files,
functions, and features.
You make the modifications on your PRPC system in a RuleSet designated for
development. This book takes you step-by-step through each modification.
Receiving Accepting and capturing the essential data describing work from multiple
sources, including keyboards, scanners, and external systems, in a wide range of
media and formats.
Routing Using characteristics of the work together with knowledge about the
workforce to make intelligent matches and assignments.
PRPC is the only BPM solution that automates both the business rules and the business
processes that drive work to completion.
Additionally, PRPC employs a sophisticated common object model to deliver the power
of process and practice integration. This integration is achieved without the expense
and resources associated with maintaining separate business process and rules
databases, user interfaces, test environments, and production environments.
Chapter 3 describes how to improve the application by changing the purchase order
request process.
Appendix B provides a description of the icons and buttons found on the Designer
Studio toolbar and tab bar.
Appendix C provides additional information that might be useful when setting up your
workstation.
Tip: Print Appendix B and have it available as you go through this book to help you learn about
the toolbar and tab bar buttons.
Prerequisites
To follow the steps in the hands-on exercises in this book, you need:
Access to a PRPC Version 6.2 SP2 system. This specific software version is required
to accommodate the ASupply application that is used in the hands-on exercises. The
installed Pega-ProcessCommander RuleSet version should not be lower than
06-02-20.
Typically, the system administrator for your organization provides access to the
organizations installed PRPC system. The process for obtaining access is determined
by your organization. Contact your system administrator to obtain the appropriate
access and for assistance in verifying the version of the installed PRPC RuleSet.
The URL for logging into PRPC. The URL is usually obtained from your organizations
system administrator. It is typically in the format:
http://<hostname>:<port>/prweb/PRServlet, where <hostname> is the
system on which PRPC is installed and <port> is the assigned port. The URL is case
sensitive.
The ASupply application. To install the application, follow the steps in Appendix D. If
your organization has policies on who can install applications in PRPC, contact your
organizations system administrator for assistance.
Intel-based dual-core processor with at least 4GB of free RAM running a 32-bit or 64bit version of Microsoft Windows 7 or Vista.
Chap
pter 2: Using
g the Applic
A
cation
This chapter shows you how to use the app
plication and
d experiencce it from the worker
and man
nager points
s of view by:
Cre
eating a purchase order requ
uest.
Ap
pproving the pu
urchase order request.
r
In Chaptters 3 and 4,
4 you assum
me the role of a designe
er and you cchange the business
process, appearance
e, and functtions supporrted by the application.
Creating a Pu
urchase
e Order
1. Open
n your brows
ser to the URL
U
for loggiing into PRP
PC. The PRP
PC login scre
een
appears (Figure 2-1).
The UR
RL is usually obtained from your
y
organizations system ad
dministrator. It is typically in
n the
formatt: http://<ho
ostname>:<p
port>/prweb/
/PRServlet, w
where <hostna me> is the sys
stem on
which PRPC is installled and <port>
> is the assigne
ed port. The U RL is case sensitive.
If pro
ompted with
h a Windows
s Security warning,
w
clicck Install. ((Figure 2-2 shows an
exam
mple.) This might
m
occur a few more
e times as W
Windows dow
wnloads eac
ch needed
ActiveX control.
Click the
My Worklist ta
ab to view a list of outsstanding (no
ot complete)
assig
gnments rea
ady and waitting for the user to perfform (orderred by urgen
ncy). In
this example,
e
the worklist is
s empty, dis
splaying the
e message No items.
Fiigure 2-3. My
y Worklist
4. Selec
ct Purchase
e Order from the New selection bo
ox (Figure 2
2-4). A form
m labeled
Purch
hase Order appears
a
in the
t
portal header.
Fiigure 2- 4. Ne
ew Selection Box Purcha
ase Order
10
5. In the Purchase Order form, select IT from the Department Name selection box.
In the Department Number field, type a number. Optionally, type a note in the
Note field (Figure 2-5).
6. Click Create at the bottom of the form. This action transmits your input to the
PRPC server and creates a work item according to the purchase order process
defined in this application. The system assigns a sequential identifier called the
work item ID to the work item. This ID is visible in the top bar of the user form
(circled in Figure 2-6). In this application, the work item IDs begin with the prefix
P- to identify purchase orders.
11
in the wo
ork item tab
b to close it. The
My Worklist
W
tab
b, click Refr
resh
My
y Worklist
The worklist
w
refrreshes and an
a assignme
ent row for this work ite
em appears
s on your
work
klist. Because additionall steps are needed
n
befo
ore your tassks with the work item
can be
b complete
ed, a row forr this assign
nment for ap
ppears in yo
our worklist. Figure 27 sho
ows a worklist containin
ng one assig
gnment row
w for the purrchase orderr.
12
2. In the Item Name column, select an item from the drop-down list. When an item
is selected, its price appears in the Price column.
3. Click in the Quantity field, enter a number for the quantity to be purchased, and
then press the Tab key. The total charge (price multiplied by quantity) appears for
that line item.
Note: Use the Tab key to advance from field to field. Do not use the Enter key, as pressing Enter
submits the form.
13
Note
e: If you make
e a mistake an
nd want to dele
ete an items ro
ow, click the ga
arbage can ico
on at the
right end of the row
w.
5. Click Submit to move to the next step in the purcchase order process (if necessary,
use the
t
right-hand scroll bar to bring th
he Submit button into view).
6. Afterr clicking Su
ubmit, the Confirm
C
Or
rder section
n appears in the form (n
note the
Confiirm Order la
abel circled in Figure 2-10).
14
To se
ee where this point occu
urs within th
he overall p
process, click
k the Wherre Am I
at the top
icon
p of the tab. The You Are
A Here w indow opens and displa
ays the
proce
at the work
ess diagram
m (Figure 2-1
11). This is the path tha
k item follow
ws. The
shapes in this diagram are types
t
of building blockss in the PRP
PC representtation of
the business
b
pro
ocess. Comm
mon shapes are explain
ned in Chaptter 3.
Check marks appear next to
o those proc
cess steps t hat the worrk item has passed
throu
ugh and are complete. Following
F
th
he diagram ffrom the top downward
d, the work
urrent Operrator, Work User.
item was created
d, and then was assigned to the Cu
The first
f
Assignm
ment shape (green recttangle), labe
eled Enter I
Item Inforrmation,
corre
esponds to the
t
form where a user must
m
select items and tthe quantitie
es before
the work
w
item ca
an continue through the
e process. W
When you cllicked the S
Submit
butto
on, the work
k item move
ed to the next Assignme
ent shape, llabeled Con
nfirm
Orde
er. The arrow shape ind
dicates the current
c
step
p of the flow
w. The P-1 w
work item
is at the Confirm
m Order Assiignment.
15
An
n Assignmen
nt shape (grreen rectang
gle) corresp
ponds to a h
human-base
ed step in
the flow. Assignments arre points in the
t
processs that are to be handled
d by a
pe
erson (to pro
ovide input or take other actions). Here, the C
Confirm Ord
der
As
ssignment shape is whe
ere a user co
onfirms the order and a
adds shippin
ng details
to the purchase order req
quest.
7. Click
16
8. Select the Add Shipping Information check box. The Shipping Information
fields appear in the form (Figure 2-12).
9. Type the shipping information for your purchase order. Use the Tab key to
advance from field to field. Do not use the Enter key, as that submits the
form.
17
10. Click Submit. The Confirrmation secttion appearss (Figure 2--13). The Sttatus is
Pe
ending-App
proval. The
e form indica
ates that th e work item
m has gone tto a
manager for approval.
a
An
n assignmen
nt for the ap
pproval requ
uest is place
ed on the
managers wo
orklist.
Figure 2-14
4. Logoff
18
2. In the ACORP Work Group, click Manager. The managers worklist appears in the
work space on the right (Figure 2-16).
19
The ASupply application displays a confirmation form (Figure 2-19). The resolved
status indicates that the business process is complete.
20
Note
e: In this flow, after a manag
ger Approves (or Rejects) the
e purchase ord
der request, the
e work item
becom
mes resolved with
w
a status off Resolved-Com
mpleted (or Re
esolved-Rejecte
ed).
Fiigure 2-20. Lo
ogoff
21
Bill Customer
Order Total
IT
>$1,000
HR
>$500
Finance
No
Finance
Yes
>$200
Legal
Yes
Legal
No
>$200
>$200
IT
No
>$2,000
Then
And
The Bill Customer check box is unchecked
(clear)
However If
The Department Name is set to Finance
22
When you complete the changes to the application to implement this policy, the
revised process diagram will look like Figure 3-2, with the added shapes shown within
the purple box.
23
The Designer Studio opens (Figure 3-4). If the Application Explorer does not
display, click the arrow to select it from the list of Explorers.
The Application Explorer in the left panel provides quick access to this applications
rules. It presents a multi-level tree structure to browse for and perform operations
on rules. Rules are organized into PRPC rule categories.
For example, the ASupply application contains the PurchaseOrder class which
contains rules that belong to various rule type categories such as Process,
Decision, and User Interface (Figure 3-5).
24
2. Open
n the PurchaseOrder flow
f
rule (Figure 3-6):
a. Click
C
the + ic
con to expand the Purc
chaseOrde r class and see the cate
egories it
co
ontains.
b. Click
C
the + ic
con to expand the
co
ontains.
Process
P
cate
egory to see
e the rule ty
ypes it
c. Click
C
the + ic
con to expand the Flow
w rule type. In the Application Explorer, a
preceding a name indicate
green arrow icon
es a starter flow rule, w
which
su
upports the creation of a new work
k item.
d. Click
C
Purch
haseOrder to open the
e flow rule.
Figure
F
3-6. Pu
urchaseOrder
r Flow Rule in
n Application Explorer
Fast Start Guide
25
26
will
w save a co
opy of this flow
f
rule into a RuleSett named ASupply with a higher
RuleSet
R
Vers
sion of 01-0
01-02. Then
n you make updates to the new copy.
3. Click Save As
to save a copy of the
e flow rule into the
ASup
pply:01-01-0
02 RuleSet Version.
V
A SaveAs
S
dialo
og opens (F
Figure 3-8).
e keys of th
4. The Applies
A
To and Flow Name
N
fields
s identify the
he flow rule.. Do not
alter the values in these fiellds. The new
w flow rule sshould use tthe same ke
eys as the
origin
nal you are copying. Co
onfirm that ASupply
A
di splays in th
he RuleSet drop-down
list and the Vers
sion is 01-0
01-02, and then click S
Save As.
The new
n
flow rule appears. Select the arrow
a
to collapse the de
etails.
The next
n
steps change
c
the PurchaseOrd
P
der flow to iinclude a De
ecision shap
pe that
deterrmines whetther the VP must appro
ove a purcha
ase order re
equest.
A Decision shape
e, representted in the prrocess diagrram by an o
orange diam
mond,
identtifies an automatic step
p where proc
cessing may
y advance along any on
ne of two
or mo
ore outcome
es. In this case,
c
the De
ecision shap e has two o
outcomes:
VP
P approval is re
equired (True)
VP
P approval is no
ot required (Fa
alse)
p
diag
gram display
ys.
The process
27
6. Using
g the mouse
e wheel, scrroll towards you to redu
uce the size of the proc
cess
diagrram, so thatt you can view the entirre process.
7. In the toolbar, make
m
sure th
hat the Pan
n icon
iss selected. L
Left-click a b
blank area
of the
e canvas an
nd drag to move
m
the dia
agram as a w
whole. You can use the
e mouse
whee
el to re-size the diagram
m again, if desired.
d
You
u can also pa
an the diagrram using
the mini-map
m
in the lower right.
d
aboutt using the Process Mod
deler, click tthe
Help
p icon in the
e toolbar,
For details
selec
ct Develope
er Help, and
d go to the Flow Rules Process M
Modeler Bas
sics topic.
Fiigure 3-9. De
eveloper Help
Pan and
a
Select
modes are mutually exclusive. When Selecct mode is o
on, you can
left-c
click a blank
k area of the
e canvas and
d drag to fo
orm a selecttion boundary. When
you release
r
the mouse button, the sele
ected shapess are highlig
ghted and y
you can
take action; for example, move
m
or dele
ete, on all th
he highlighte
ed shapes
simultaneously. You will work with Sele
ect mode latter.
8. In the toolbar, verify
v
that Draft
D
On
is sselected. W
While the flow
w rule is in
draft mode, it is known as a flow mode
el, and you ccan referencce other rule
es and
flow actions thatt you have not
n yet defin
ned.
28
The green circle at the top of the process diagram identifies the start of the
business process in which a new purchase order request is created. Processing
of each purchase order proceeds along the connectors from shape to shape.
The three green rectangles with clocks on them mark Assignment shapes
(Enter Item Information, Confirm Order, and Manager Approve Order).
Assignments are the steps in the process that require a human actor (here, a
user or manager) to enter information or record their decisions. The orange
diamond shape labeled Manager Review identifies an automated Decision. In
this process, the automated Decision has two outcomes: Review or No Review.
29
30
e flow are h
12. When
n you releas
se the mous
se, selected areas of the
highlighted iin blue.
Hove
er the mouse
e pointer ov
ver the highlighted area
a until it cha
anges to a c
cross
and then
t
click an
nd drag the selected arrea down.
31
The bounding
g box shown
n in Figure 3-14
3
indicattes the new location.
Figure
e 3-14. Bound
ding Box Indic
cates New Lo
ocation
m the Shapes
s palette, drrag a Decision shape
onto th
he process d
diagram,
13. From
positioning it bellow the Man
nager Appro
ove Order Asssignment sshape (Figurre 3-15).
This indicates that the busin
ness process
s requires a decision affter a purchase order
reque
est is approved by the manager.
14. Hove
er the mouse
e pointer ov
ver the Decision shape until it chan
nges to a cro
oss
,
and then
t
double-click the Decision shap
pe to display
y the Decisiion Properties panel.
32
Figure 3-1
17. Decision Properties
P
Diialog
33
Do
o not change th
he Applies To field
ould be ASupp
ply; if not, chan
nge it
The RuleSet sho
Figure
F
3-19. Decision
D
Table
e Rule Form
34
Definin
ng a New
w Decision
n Table Rule
R
1. In the Decision Table
T
rule fo
orm, click th
he Results tab to bring
g it to the frront.
Comp
plete two ro
ows of the Allowed
A
Results array to identify the allowed
d results
for th
his decision table. In this case, the
e allowed ressults are:
Whe
en completin
ng arrays, click:
to ad
dd a new row
w at the botttom of the array
to insert a new row between existing rrows
elete a row
to de
2. On th
he Results tab, type True in the first
f
row, clicck
then type False in the second row.
to ad
dd a new row
w, and
Note: No
o changes are needed
n
to the Set Propertie
es?, Options, or Preset Pro
operty Values
s areas.
35
3. Click the Table tab to bring it to the front. In this tab, you record the decision
table logic as presented previously in Figure 3-1:
Dept Name
Bill Customer
Order Total
IT
>$1,000
HR
>$500
Finance
No
Finance
Yes
Legal
Yes
>$200
>$200
Legal
No
>$200
IT
No
>$2,000
4. The decision table in this example has three inputs that are identified by property
rules: DepartmentName, BillCustomer, and OrderTotal. Each column in the decision
table (except the Return column) corresponds to a property. Use these steps to
complete the Table tab:
a. Click the column heading cell (the cell just below the Conditions column
title) to label the column in the matrix. A Property Chooser pop-up dialog
displays (Figure 3-22).
36
c. Click Sav
ve to save th
he property to the deci sion table m
matrix.
5. The starting
s
tablle contains a single input condition
ns column. Y
You need to add two
colum
mns; one for the BillCus
stomer prop
perty and on
ne for the O
OrderTotal property.
To ad
dd a column
n to the righ
ht of the starting colum n:
a. Click the cell under Department
D
Name to se
elect that co
olumn (Figure 3-24).
Figure 3-24.
3
Decision Table Rule Select A Co
olumn
37
t
BillCusto
omer and OrderTotal
O
prroperties (F
Figure 3-26) to the columns using
6. Add the
the Property
P
Cho
ooser (Figurre 3-22).
Figure 3-27.
3
Decision Table Rule First Row C
Completed
38
8. Add additional
a
ro
ows by click
king the Ins
sert Row Affter icon
show
wn in Figure 3-28.
Figure
F
3-28. Decision
D
Table
e Rule Emp
pty Rows Add
ded
9. Using
g Figure 3-1
1 as your gu
uide, comple
ete the table
e so it lookss like Figure 3-29. In
the Bill
B Custom
mer column, enter =Fallse for No a nd =True ffor Yes. In tthe
othe
erwise (fina
al) row, set the
t
return action
a
to Fa lse.
39
40
12. To de
elete this row, click in any
a
cell in th
he row to se
elect the row
w, and then select the
Dele
ete Row icon
. Click Show Confflicts again
n to confirm that no logic errors
rema
ain. A messa
age displays
s: The Decision Table iis consistent.
13. Save the revised
d decision ta
able and close the rule form by cliccking the X.
41
2. Click and drag the connection point from the Update Status Completed Utility
shape to the top connector of the VP Approve Order Decision shape. A connector
must make a valid connection to a shape. Valid connections display with a green
connector line and a green outline around the target shape (Figure 3-33).
42
3. Select and drag an Assignment shape below the VP Approve Order Decision
shape, so that purchase order requests can be routed to the Vice President (Figure
3-34).
43
4. Hove
er the mouse
e pointer ov
ver the Assig
gnment sha
ape until it cchanges to a cross
and then
t
double-click the Assignment
A
t shape and complete the Assignment
Prope
erties. On th
he Assignm
ment tab, co
omplete the
e following (Figure 3-35
5):
a. Name: Ty
ype VP App
proval.
b. Harness Name:
N
Use the SmartPrompt to se
elect Perforrm. (A harne
ess rule
provides the basis off a form for work item p
processing.))
c. Instructio
ons: Type VP
V Approval Pending (do not include punctua
ation).
This text will appear in the Conffirm user forrm.
d. Confirmation Note: Type
T
VP Ap
pproval is rrequired (do not includ
de
punctuatiion).
Figu
ure 3-35. Ass
signment Prop
perties
5. In the Status ta
ab, use the SmartPromp
S
pt to select Pending-A
Approval as
s the Work
Statu
us.
44
8. Doub
ble-click the connector to
t open the Connector Properties a
and configure this
connector as sho
own in Figurre 3-39. Sett the Likelih ood to 50. A likelihood
d is a value
between 1 and 100.
uman
1
It reflec
cts an assum
med or know
wn probabillity of the hu
actorr taking thatt action.
45
9. This configuratio
on means th
hat when the
e decision ta
able rule retturns a valu
ue of False,
the Vice
V
Presiden
nts approva
al is not required. The ffollowing ev
vents occur
autom
matically: The requests
s status is updated
u
to R
Resolved-Co
ompleted an
nd the
purch
hase order request
r
is re
esolved, as shown in Fi gure 3-40.
10. When
n the decisio
on table rule
e returns a value of Tru
ue, the Vice Presidents
s approval
is req
quired. Add a connector from the VP
V Approve
e Order De
ecision shape
e to the
VP Approval
A
As
ssignment shape
s
as folllows:
11. From
m the VP Ap
pproval Assignment sha
ape, add a cconnector to
o the Updatte Status
Reje
ected Utility
y shape.
46
12. Doub
ble-click the connector to
t open the Connector Properties d
dialog. In th
he Flow
Action field, pres
ss the down
n arrow, dou
uble-click Mo
ore, and then double-c
click to
selec
ct Reject.
47
15. Click
48
Test Yo
our Proce
ess Chan
nges
Test your process ch
hanges usin
ng the Run menu.
m
on
in the
e Quick Laun
nch bar, sel ect Run Prrocess, and then
1. Click the Run ico
selec
ct Purchase
e Order. You do not ne
eed to log ou
ut, but can a
act as the w
work user,
mana
ager, and VP.
2. Creatte a new pu
urchase orde
er request, using
u
data v
values simila
ar to those entered in
the example
e
in Chapter
C
2.
3. Enterr line items and quantitties that pro
oduce a tota
al amount th
hat meets one of the
criterria for requiring VP app
proval as sho
own in Figurre 3-1. For example, if the
Depa
artment is IT
T, any orderr over $1000 requires tthe VPs rev
view.
4. Click Submit to confirm the
e purchase order
o
reque st.
5. Click the Approv
ve Order link displayed
d at the botttom of the confirmation note
that indicates the purchase order is ass
signed to th e manager (Figure 3-4
47). As a
mana
ager, approv
ve the request.
Figu
ure 3-47. App
prove Order Link
L
6. Verify
y that after the manage
er approves
s the purcha
ase order request, the rrequest is
route
ed to the Vic
ce Presidentt for approval.
49
Chap
pter 4: Upda
ating the
t
Us
ser Intterface
e
Currently
y, the Vice President
P
se
ees the same user interrface as the manager w
when
approvin
ng or rejecting a purcha
ase order request. Howe
ever, ASupp
plys business policy
requires the VP to enter
e
an app
proval code. The busine
ess policy alsso gives the
e VP the
option to
o enter a no
ote about the
e approval.
In this ch
hapter you will
w enhance
e the user in
nterface to e
enable the V
VP to enter these
details.
Buildiing a Ne
ew Flow
w Action rule
Recall fro
om Chapterr 2 that assig
gnments are points in tthe process that are to be
handled by a person
n (to provide
e input or ta
ake other acctions). Rule
es known as
s flow
actions determine
d
which
w
inputs are requested from th e user in the work item
m form as
the user completes the assignm
ment.
To provid
de the VP th
he opportun
nity to enterr input durin
ng the VPApproval assig
gnment, a
new flow
w action rule
e is needed to
t implemen
nt those dettails.
1. Log in as Design
ner with the
e password password,, as in Chap
pter 3.
2. From
m the Applica
ation Explorrer tree in th
he left pane l, click the + icon to ex
xpand the
Purc
chaseOrder
r class.
3. Click the + icon to expand the
t
User
r Interface
e category, rright-click F
Flow
Actio
on, and sele
ect New fro
om the conte
ext menu (F
Figure 4-1).
4. The New
N
flow ac
ction rule dia
alog opens (Figure
(
4-2)). Specify th
he following:
a. Keep the Applies To
o value as itt is.
b. For the Action
A
Nam
me, type VPA
Approve.
c. For the RuleSet,
R
select ASupplly.
d. For the Version,
V
select 01-01-02.
Fast Start Guide
50
Figure
e 4-2. New Flo
ow Action Dia
alog
5. Click
C
Create to create th
he new VPA
Approve flow
w action and
d display the
e rule
fo
orm. In the Short Descrription field,, insert a sp
pace betwee
en VP and A
Approve.
This label, VP
P Approve, will
w display in the flow a
action sectio
on.
Figure
e 4-3. VPAppr
rove Flow Acttion Rule Form
m
6. Click
C
Save
. At this point
p
the new VPApprov
ve flow actio
on rule does
s not
display user interface ite
ems for the VP to enterr information
n. Section rrules are
used to imple
ement user interface fe
eatures for a flow action
n. Next, you
u will
crreate a secttion rule.
51
Buildiing a Se
ection ru
ule
1. From
m the Applica
ation Explorrer tree in th
he left pane l, click the + icon to ex
xpand the
Purc
chaseOrder
r class.
2. Click the + icon to expand the
t
User
r Interface
e category, rright-click S
Section,
and select
s
New from the co
ontext menu
u (Figure 4-4
4).
Figure
F
4-4. Se
ection Contex
xt Menu
3. The New
N
section
n rule dialog opens (Figu
ure 4-5). Sp
pecify the fo
ollowing:
a. Keep the Applies To
o value as itt is.
b. For the Purpose,
P
en
nter VPAppr
roval.
c. For the RuleSet,
R
select ASupplly.
d. For the Version,
V
select 01-01-02.
52
to save the VP
PApproval section rule.
Figure
F
4-6. VPApproval
V
Se
ection Rule Fo
orm
6. Add
d a field in which
w
the VP
P is required
d to enter a n approval code. To do
o this, click
the
e Basic icon
in the
e toolbar, se
elect the Te
ext Input C
Control and d
drag it to
the
e Field colum
mn cell in th
he top row, as shown in
n Figure 4-7
7.
Figure
F
4-7. Te
ext Input Con
ntrol
7. In the
t
Field column, click the magnify
ying glass iccon
in th
he first row to open
the
e Cell Properrties panel. In the Property field, ty
ype .Appro
ovalCode (u
using the
exa
act case and
d being sure
e to include a leading pe
eriod).
8. Click
C
the Ope
en icon
next
n
to the Property
P
fie
eld (Figure 4
4-8). This o
opens a
New
N
property
y rule dialog
g (Figure 4-9).
53
Figure
e 4-9. New Pro
roperty Dialog
g
9. Make
M
sure th
hat ASupply
y is selected
d in the Rul eSet field a
and that 01--01-02 is
se
elected in th
he Version field. Click Quick Crea
ate to creatte the new p
property
ru
ule (Figure 4-9).
4
10. In
n the Cell Prroperties pa
anel, select the
t
Genera
al tab, and tthen select tthe
Required
R
ch
heck box. Th
his ensures that a value
e is entered in the userr form
before it is su
ubmitted. Otherwise,
O
an error messsage appea
ars and reminds the
user to enterr a value. Cllose the Cell Properties panel.
Figure
e 4-10. Selectt the Required
d Check Box
11. In
n the Label column, clic
ck the magn
nifying glasss icon
nex
xt to Text Input to
open the Cell Properties panel. In th
he Cell Prop
perties pane
el, change th
he Value
frrom Text Input to Appr
roval Code, as shown in Figure 4--11. On the General
ta
ab, notice th
hat the Requ
uired check box is seleccted. A requ
uired icon (
) will
54
Figure
e 4-11. Chang
ge the Value
to
Figure
e 4-12. Insertt Row After
Figure
e 4-13. New Rows
R
Added to
t the Layout
13. A property ru
ule named PaymentDat
P
te already ex
xists. You ccan drag and
d drop it
frrom the App
plication Exp
plorer into the new row
w below Apprroval Code. In the
Application
A
Explorer,
E
clic
ck the + ico
on to expand
d the Purch
haseOrder class, and
th
hen click the
e + icon to expand the
Property rule
e type.
14. Click
C
the + ic
con to expand the Prop
perty rule ttype (Figure
e 4-14). Eac
ch blue dot
identifies a simple property rule,, one that h olds only a single value
e such as a
55
date or amou
unt. Other ic
cons in this tree, such a
as
, identtify aggrega
ate
properties, which
w
are sim
milar to arra
ays and stru
uctures.
Select the
blue dot to the left of the
t
Paymen
ntDate link. (Do not clic
ck the
PaymentDate
e link.)
w contains th
he .PaymentDate prope
erty. Notice the calenda
ar icon in
This row now
th
he Field colu
umn. This in
ndicates that the .Paym
mentDate pro
operty is a
pxDateTime Control. PRPC supports
s a wide varriety of inpu
ut and outpu
ut formats
fo
or dates and
d times.
56
15. In
n the Label column, clic
ck the magn
nifying glasss icon
ne
ext to Paym
mentDate
to
o open the Cell
C Properties panel. Change
C
the V
Value to Pay
yment Datte (insert a
sp
pace), and then
t
close the Cell Prop
perties pane
el.
Figure
e 4-17. .Paym
mentDate pxD
DateTime Con
ntrol
Figure
e 4-18. Add th
he Text Area Field
F
17. In
n the Label column, clic
ck the magn
nifying glasss icon
ne
ext to the Te
ext Area
ce
ell to open the
t
Cell Prop
perties pane
el. Change tthe Value to
o Note and then close
th
he Cell Prop
perties panel.
Figure
e 4-19. Chang
ge the Text Ar
rea Label
18. In
n the toolba
ar, click Sav
ve
to sav
ve the updatted VPAppro
oval section
n rule form.
57
19. Click
C
the Pre
eview butto
on
in the
e toolbar to v
view the efffect of your changes
in
n the bottom
m half of the
e portal (Figure 4-20).
Figure
e 4-20. Previe
ew
20. Click
C
the x on the VPAp
pproval tab to close the
e section rule form.
58
Return to the VPApprove flow action rule form by clicking its tab in the Designer
Studio (Figure 4-21).
2.
In the Application Explorer, expand the Section rule type to locate the newly
created VPApproval section. Select the blue dot to the left of the VPApproval
section in the Application Explorer. Each blue dot identifies a single rule. The blue
dot turns yellow, indicating that it is selected. Drag it into the VPApprove flow
action rule form, dropping it onto the <drag section here> area (Figure 4-22).
3. When you release the mouse button, the VPApprove flow action rule form displays
a section reference to the VPApproval section (Figure 4-23).
59
5. Click the x on th
he VPAppro
ove tab to close
c
the VPA
Approve flow action rulle form.
Editin
ng the Flow
At this point, the ne
ew flow actio
on VPApprov
ve is comple
ete, but nott referenced by any
shape in the flow rule. In this section you will
w update tthe PurchasseOrder flow
w rule so
that the new VPApprove flow ac
ction runs when
w
the VP
P approves a purchase o
order
request.
3.
In th
he Connecto
or Properties panel, typ
pe VP Appro
ove in the N
Name field, use the
Sma
artPrompt to
o replace Ma
anagerApp
prove with V
VPApprove
e, and then click OK
(Figure 4-25).
60
Fiigure 4-25. VP
V Approve Co
onnector Prop
perties
The connector
c
in
n the proces
ss diagram is labeled VP
P Approve.
Fiigure 4-26. VP
V Approve Co
onnector
in the Quic
ck Launch ba
ar and selecct Run Proc
cess >
61
The VP is now required to enter an approval code and may also enter an
optional note (Figure 4-28).
62
Figure 4-30.
4
Declara
ative Expressiion for .Order
rTotal
Figure 4-31.
4
Declara
ative Expressiion for .LineI
ItemTotal
Like form
mulas in a Microsoft
M
Exc
cel spreadsh
heet, properrties controllled by decla
arative
rules are
e computed automatically wheneve
er a value ch
hanges thatt affects the
e
computa
ation. For ex
xample, the target prop
perty LineIte
emTotal is ccomputed whenever
the Price
e or Quantity
y changes. Similarly, yo
ou dont nee
ed to create
e an explicitt program
to recalc
culate the OrderTotal affter you inpu
ut a quantitty.
Using the
t
Decla
arative Rules
R
Insp
pector
You can use the Dec
clarative Rules Inspecto
or to see wh
hich propertties in the w
work item
form are
e dependentt upon these
e rules, and to graphica
ally illustrate
e those dependencies.
1. To en
nable the De
eclarative Rules
R
Inspector, click th e Run ico
on in the Qu
uick
Launch bar and select Rules Inspecto
or > Declarrative Rules (Figure 4--32).
Figu
ure 4-32. Dec
clarative Rule
es Inspector
Fast Start Guide
63
2. Creatte a new pu
urchase orde
er request by
b selecting > Run P
Process > P
Purchase
Orde
er. On the work
w
item fo
orm, a D liink appears next to eacch property that is
calcu
ulated by a declarative
d
rule.
r
For example,
e
ass
sume that you
y
select th
he Laptop ittem and typ
pe 2 as the q
quantity.
Notic
ce that a D appears
a
nex
xt to the LineItemTotal property (F
Figure 4-33)). Click the
D link to inspe
ect how thatt property va
alue is calcu
ulated.
Figu
ure 4-33. Rev
viewing Decla
arative Rules
Figu
ure 4-34. Dep
pendency Nettwork Viewer
r
The symbols
s
sho
own are des
scribed below
w:
A function
f
symbo
ol (
) referen
nces a declarattive rule.
PRPC
C supports complex dec
clarative rule
es and enab
bles you to ttest and deb
bug
decla
arative comp
putations interactively.
To disable the Declarative Rules
R
Inspec
ctor feature,, click
Declarative Rules.
>R
Rules Inspector >
64
A decision table rule, VPApproveOrder, controls which purchase order requests are
routed to the VP for review.
A property rule, ApprovalCode, holds an input value entered by the Vice President.
A flow action, VPApprove, prompts the VP with two new fields after the VP approves a
purchase order request.
A section, VPApproval, provides the user interface for the VPApprove flow action.
These new rules supplement the original set of rules in the ASupply RuleSet, which
defined the application before you changed it. As you will see in Chapter 6,
Documenting Your Application, and from the application document in Appendix A, the
ASupply RuleSet contains about 125 rules.
The Application Explorer provides designers and developers with quick access to rules
in the ASupply RuleSet. These rules, in turn, build on hundreds of built-in, out-of-thebox standard rules that are present in every PRPC system and which form the
foundation building blocks of applications.
Rules and other data are stored in a relational database supported by any of several
popular database products from Oracle, Microsoft, or IBM.
Computations, such as declarative rules and decision table rules, are transformed into
efficient Java programs.
65
Autogenerated Controls simplify design and maintenance, eliminating the need for
hand-coding, improving performance, and ensuring browser independence and
compatibility.
Grid layouts enable users to view and edit values of a Page List or Value List property
or a Report Definition in a spreadsheet format. Grids are created dynamically and
have as many rows as needed to display the requested data.
Through hardware clustering, one PRPC system can support thousands of users in
multiple locations who enter, work on, and resolve millions of work items.
Developers can use the Run menu in the Quick Launch bar to quickly switch from a
development task to a testing task and back to a development task, as you did.
PRPC applications can interface with other systems using a wide variety of industrystandard technologies (such as SOAP / Web services, e-mail, relational databases,
J2EE facilities including Enterprise JavaBeans, and JavaServer Pages).
66
Chap
pter 6: Docu
umentting Yo
our Ap
pplicattion
PRPC inc
cludes tools that enable
e you to easily documen
nt what you have built. This
chapter describes
d
ho
ow to use th
hose tools.
Note: Miccrosoft Word 20
002 or later is needed to pro
oduce the Appliication docume
ent.
Docum
menting
g the AS
Supply Applicat
A
tion
1. In the Designer Studio, sele
ect the Pega
a button
Tools > Docum
ment (Figure
e 6-1).
and then
n select App
plication >
Figu
ure 6-1. Docu
ument Menu Item
I
67
2. In the Application Document wizard, select the ASupply application, the ASupply
application template, and specify the Detail Level, for example, Full Application
Documentation.
For more information about the Application Document wizard, click the Help button
in the upper right of the wizard.
3. Click the Order chevron at the top of the screen to proceed to the next page.
68
4. Selec
ct the items that you want to includ
de in the do
ocument and
d then click the
chevron to proce
eed through
h the Define and Capturre screens.
Fiigure 6-5. Do
ocument Now Button
PRPC
C generates a Word doc
cument that lists all of tthe rules in the applicattion. The
generation proce
ess may tak
ke a minute or two. A m
message disp
plays when the
nt created b
by PRPC for
documentation is complete. Appendix A contains t he documen
the ASupply
A
app
plication.
6. Click the Logoutt link in the upper rightt corner of tthe Designe
er Studio.
This is th
he conclusio
on of the Fas
st Start Guid
de. More infformation on the ASupply
application and appe
endices describing the Designer Sttudio toolbar, tab bar, a
and the
w
setup
s
can be found in the
t
following
g pages.
typical workstation
69
70
71
Copyright 2013
Pegasystems Inc., Cambridge, MA
All rights reserved.
This document describes products and services of Pegasystems Inc. It may contain
trade secrets and proprietary information. The document and product are protected by
copyright and distributed under licenses restricting their use, copying distribution, or
transmittal in any form without prior written authorization of Pegasystems Inc.
This document is current as of the date of publication only. Changes in the document
may be made from time to time at the discretion of Pegasystems. This document
remains the property of Pegasystems and must be returned to it upon request. This
document does not imply any commitment to offer or deliver the products or services
described.
This document may include references to Pegasystems product features that have not
been licensed by your company. If you have questions about whether a particular
capability is included in your installation, please consult your Pegasystems service
consultant.
For Pegasystems trademarks and registered trademarks, all rights reserved. Other
brand or product names are trademarks of their respective holders.
Although Pegasystems Inc. strives for accuracy in its publications, any publication may
contain inaccuracies or typographical errors. This document or Help System could
contain technical inaccuracies or typographical errors. Changes are periodically added
to the information herein. Pegasystems Inc. may make improvements and/or changes
in the information described herein at any time.
72
Contents
Application Overview ................................................................................. 75
Description .................................................................................................................................. 75
Business Objectives ................................................................................................................... 75
Actors ........................................................................................................................................... 75
Case Type Definitions ............................................................................................................... 75
Work Types ................................................................................................................................. 75
Supporting Types ....................................................................................................................... 75
RuleSets ....................................................................................................................................... 75
Requirements.............................................................................................................................. 76
PurchaseOrder ............................................................................................. 76
Purchase Order - Flow .............................................................................................................. 76
Primary Path ........................................................................................................................... 77
Alternate Path 1 ..................................................................................................................... 83
Alternate Path 2 ..................................................................................................................... 84
Alternate Path 3 ..................................................................................................................... 85
Other Specifications referenced in the application (outside of a Process) .................... 86
ApproveOrder - Specification .............................................................................................. 86
ConfirmOrder - Specification .............................................................................................. 86
EnterDeptInformation - Specification ............................................................................... 86
EnterItemInformation - Specification ............................................................................... 87
PurchaseOrder - Specification ............................................................................................ 87
RejectOrder - Specification ................................................................................................. 87
Entity Relationship Diagram .................................................................................................... 88
Properties Referenced ............................................................................................................... 88
Common .......................................................................................................... 89
Security ........................................................................................................... 89
Navigation ...................................................................................................... 89
DataManagement ........................................................................................ 89
SysAdmin ........................................................................................................ 89
Requirements Matrix .............................................................................................. 90
Reports ............................................................................................................ 90
List Views ..................................................................................................................................... 90
Fast Start Guide
73
Correspondence .................................................................................................... 90
Acknowledgement............................................................................................................................... 90
Integration .................................................................................................... 91
Services........................................................................................................................................ 91
Connectors .................................................................................................................................. 91
Decisions ........................................................................................................ 91
Tables ........................................................................................................................................... 91
VPApproveOrder .................................................................................................................... 91
Trees ............................................................................................................................................. 92
Manager Review .................................................................................................................... 92
Map Values .................................................................................................................................. 92
Whens........................................................................................................................................... 92
ItemPrice ................................................................................................................................. 92
Security ................................................................................................................ 92
SLAs 93
Activities .............................................................................................................. 93
Properties ............................................................................................................. 93
Declaratives................................................................................................... 94
Expressions ................................................................................................................................. 94
.LineItemTotal ........................................................................................................................ 94
.OrderTotal.............................................................................................................................. 94
Triggers ........................................................................................................................................ 95
OnChange .................................................................................................................................... 95
Constraints .................................................................................................................................. 95
74
Application Overview
Description
Initial implementation of a system that will centralize and automate the purchasing function for corporate employees.
Business Objectives
Actors
Actor
Type
Count
Access Method
Employee
Operator
Browser
Manager
Operator
Browser
Prefix
Starting Process
C-
ASupply (ASupply)
Purchase Order (Purchase Order)
C-
No Processes Defined.
P-
PurchaseOrder
Work Types
Name
Implementation Class
PurchaseOrder ACORP-FW-ASupply-Work-PurchaseOrder
Supporting Types
Name
Description
Common
Security
Navigation
Specifications specific to getting between work types and general application processing
DataManagement Specifications specific to managing lists of products, reference data tables, broadcast messages
SysAdmin
RuleSets
RuleSet
ASupply
Version
Description
Prerequisites
Pega-ProcessCommander:06-02-20
ASupplyInt:01-01-01
Pega-ProcessCommander:06-02-20
75
Description:
RuleSet
Version
Description
Prerequisites
ACORP:01-01-01
ACORP
Pega-ProcessCommander:06-02-20
Pega-ProcessCommander:06-02-20
Requirements
ID
Name
Category
Status
Description
Complete Pruchase requests are routed to managers based on total dollar values as
described in the corporate accounting manual
New
New
PurchaseOrder
Implementation:
ACORP-FW-ASupply-Work-PurchaseOrder
Edit this Description
PurchaseOrder
ACORP-FW-ASupply-Work-PurchaseOrder
ASupply : 01-01-02
76
Flow Diagram
Primary Path
Start
Implementation:
Referenced By:
Rule Name:
Applies to Class:
RuleSet:
New
Purchase Order - Flow (Page 76)
New
ACORP-FW-ASupply-Work
ASupply : 01-01-01
77
RuleSet:
Pega-ProCom : 06-02-01
Initial Urgency: 0
Assignment is ready for work:
Goal
Deadline
Late
Repeating interval from Deadline
5
0:0:0
::
Yes
No
Escalation Activity
Enter Item Information - Assignment (Page 78) in Purchase Order - Flow (Page 76)
Perform
ACORP-FW-ASupply-Work
ASupply : 01-01-01
78
EnterItemInformation
Purchase Order - Flow (Page 76)
EnterItemInformation
ACORP-FW-ASupply-Work-PurchaseOrder
ASupply : 01-01-01
Confirm Order - Assignment (Page 77) in Purchase Order - Flow (Page 76)
Confirm Order - Assignment (Page 78) in Purchase Order - Flow (Page 76)
79
ConfirmOrder
Purchase Order - Flow (Page 76)
ConfirmOrder
ACORP-FW-ASupply-Work-PurchaseOrder
ASupply : 01-01-01
ManagerReview
Purchase Order - Flow (Page 76)
ManagerReview
ACORP-FW-ASupply-Work-PurchaseOrder
ASupply : 01-01-01
80
Manager Approve Order - Assignment (Page 77) in Purchase Order - Flow (Page 76)
Manager Approve Order - Assignment (Page 78) in Purchase Order - Flow (Page 76)
ManagerApprove
Purchase Order - Flow (Page 76)
ManagerApprove
ACORP-FW-ASupply-Work-PurchaseOrder
ASupply : 01-01-01
VPApproveOrder
Purchase Order - Flow (Page 76)
VPApproveOrder
ACORP-FW-ASupply-Work-PurchaseOrder
ASupply : 01-01-02
81
Conditions
Actions
Return
if
IT
>1000
True
else if
HR
>500
True
else if
Finance
=False
else if
Finance
=True
>200
True
else if
Legal
=True
>500
True
else if
Legal
=False
>200
True
True
Otherwise
False
82
Alternate Path 1
VP Approval - Assignment
Implementation:
WorkList
Parameters:
DoNotPerform = false
ConfirmationNote = VP Review is required
Instructions = VP Approval Pending
HarnessPurpose = Perform
VP Approve - Transition
Implementation:
Referenced By:
Rule Name:
Applies to Class:
RuleSet:
VPApprove
Purchase Order - Flow (Page 76)
VPApprove
ACORP-FW-ASupply-Work-PurchaseOrder
ASupply : 01-01-02
83
Alternate Path 2
Reject - Transition
Implementation:
Reject
Referenced By:
Purchase Order - Flow (Page 76)
Rule Name:
Reject
Applies to Class: WorkLong Description: This flow action is for rejecting the work object.
Usage:
Used by the StandardEvaluate flow. Approval flows should use the Disapprove flow action, not Reject.
RuleSet:
Pega-EndUserUI : 06-02-01
84
Usage:
Alternate Path 3
Reject - Transition
Implementation:
Referenced By:
Reject
Purchase Order - Flow (Page 76)
85
Details
Actors:
Manager
Triggers:
Web Browser
Complexity:
Medium
Description
Manager must approve order totaling more than $100
ConfirmOrder - Specification
Rule Name:
RuleSet:
Details
Actors:
Employee
Triggers:
Web Browser
Complexity:
Low
Description
Not Yet Defined
EnterDeptInformation - Specification
Rule Name:
RuleSet:
Details
Actors:
employee
Triggers:
Web Browser
Complexity:
Low
Description
Fast Start Guide
86
Department information is defaulted into the purchase request form but the employee can overwrite it if not correct.
EnterItemInformation - Specification
Rule Name:
RuleSet:
Details
Actors:
Employee
Triggers:
Web Browser
Complexity:
Medium
Description
Enter the items to purchase.
PurchaseOrder - Specification
Rule Name:
RuleSet:
Details
Actors:
Any
Triggers:
Web Browser
Complexity:
Low
Description
Enter department information
RejectOrder - Specification
Rule Name:
RuleSet:
Details
Actors:
Manager
Triggers:
Web Browser
Complexity:
Low
Description
Not Yet Defined
87
Properties Referenced
Rule Name
Label
Mode
Type
RuleSet
AddShipping
AddShipping
ASupply
ApprovalCode
ApprovalCode
ASupply
BillCustomer
BillCustomer
ASupply
ContactInformation
ContactInformation
Page
ASupply
DepartmentName
DepartmentName
ASupply
DepartmentNumber
DepartmentNumber
ASupply
Order
Order
PageList
OrderDate
OrderDate
ASupply
OrderTotal
OrderTotal
ASupply
PaymentDate
PaymentDate
ASupply
py ActionPrompt
Action
Pega-WB
py AttachmentType
Attachment Type
Pega-ProCom
py Caption
Window Caption
Pega-RULES
py ConfirmationNote
Confirmation Note
Pega-ProCom
py Description
Description
Pega-RULES
py ElapsedStatusNew
Pega-ProCom
py ElapsedStatus Open
Pega-ProCom
py ElapsedStatusPending
Pega-ProCom
py ID
Work ID
Pega-ProCom
py IncludeSubCases
pyIncludeSubCases
Pega-EndUserUI
py Instructions
Instructions
Pega-ProCom
Data-Party
ACORP-Data-Order ASupply
88
Description:
Description:
Rule Name
Label
Mode
Type
py Label
Label
Pega-ProCom
py Note
Routing/Transfer note
Pega-ProCom
py OrigUserID
Originating User ID
Pega-ProCom
py ProblemReason
Problem Reason
Pega-ProCom
py RootCause
Root Cause
Pega-ProCom
py Selected
Selection Flag
Pega-ProCom
py SLADeadline
SLA Deadline
Pega-ProCom
py SLAGoal
SLA Goal
Pega-ProCom
Pega-UIEngine
Pega-ProCom
py Status Work
Work Status
Pega-ProCom
py TemplateInputBox
InputboxTemplate
Pega-UIDesign
py WorkIDPrefix
Work ID Prefix
Pega-ProCom
py WorkParty
Parties
PageGroup
Pega-ProCom
Urgency Assign
Urgency of Assignment
Data-Party
ASupply
Common
Specifications shared by multiple work types
Security
Specifications dealing with authentication, authorization
Navigation
Description:
Specifications specific to getting between work types and general application processing
Description:
Specifications specific to managing lists of products, reference data tables, broadcast messages
Description:
RuleSet
DataManagement
SysAdmin
Specifications specific to managing operator profiles, calendars, skills, rule migration/promotion
89
Requirements Matrix
Requirement
Category
External
ID
Status
Description
Linked To
ASupply 01.01.01 (
Application)
Purchase
Items
Business
Rule
New
ASupply 01.01.01 (
Application)
RejectReason Business
Rule
New
ASupply 01.01.01 (
Application)
Reports
List Views
Applies To
Name
ACORP-Data-Line Item
Details
DataTableClass Editor
Description
Added by wizard
RuleSet
ASupply
Summary Views
None found
Report Definitions
None found
Correspondence
Acknowledgement
Rule Name:
Applies to Class:
RuleSet:
Acknowledgement Email
ACORP-FW-ASupply-Work
ASupply : 01-01-01
90
Integration
Services
None found
Connectors
None found
Decisions
Tables
VPApproveOrder
Rule Name:
Applies to Class:
RuleSet:
VPApproveOrder
ACORP-FW-ASupply-Work-PurchaseOrder
ASupply : 01-01-02
Conditions
Actions
91
Conditions
Actions
Return
if
IT
>1000
True
else if
HR
>500
True
else if
Finance
=False
else if
Finance
=True
>200
True
else if
Legal
=True
>500
True
else if
Legal
=False
>200
True
True
Otherwise
False
Trees
Manager Review
Rule Name:
Applies to Class:
RuleSet:
ManagerReview
ACORP-FW-ASupply-Work-PurchaseOrder
ASupply : 01-01-01
Map Values
None found
Whens
ItemPrice
Rule Name:
Applies to Class:
RuleSet:
Logic:
ItemPrice
ACORP-Data-LineItemDetails
ASupply : 01-01-01
A0
Security
Access Group
ACORPApp:Administrators
Role Name
PegaRULES:SysAdm4
Pega-Feedback:PegaDeveloper
ACORPApp:BusinessAnalysts
PegaRULES:SysArch4
Pega-Feedback:PegaDeveloper
92
Access Group
Role Name
ACORPApp:Managers
PegaRULES:WorkMgr4
ACORPApp:SystemArchitects
PegaRULES:SysArch4
ACORPApp:Users
PegaRULES:User4
ASupply:Administrators
PegaRULES:SysAdm4
PegaRULES:User4
PegaRULES:WorkMgr4
SLAs
None found
Activities
Applies To
Name
Description
RuleSet
Version
ACORP-Data-Order
Copy UnitPrice
Copy UnitPrice
ASupply
01-01-01
Purchase Order
ToVP
ASupply
01-01-01
ASupply
getItemDetails
getItemDetails
ASupply
01-01-01
Properties
Applies To
Name
Description
Mode
RuleSet
Version
ACORP-Data-Line Item
Details
ItemName
Item Name
String
ASupply
01-01-01
ACORP-Data-Line Item
Details
Price
Price
String
ASupply
01-01-01
ACORP-Data-Order
ItemName
ItemName
String
ASupply
01-01-01
ACORP-Data-Order
LineItemTotal
LineItemTotal
String
ASupply
01-01-01
ACORP-Data-Order
Quantity
Quantity
String
ASupply
01-01-01
ACORP-Data-Order
UnitPrice
UnitPrice
String
ASupply
01-01-01
ACORP-FW-ASupplyWork-PurchaseOrder
AddShipping
AddShipping
String
ASupply
01-01-01
ACORP-FW-ASupplyWork-PurchaseOrder
ApprovalCode
ApprovalCode
String
ASupply
01-01-02
ACORP-FW-ASupplyWork-PurchaseOrder
ContactInformation
ContactInformation
Page
ASupply
01-01-01
93
Applies To
Name
Description
Mode
RuleSet
Version
ACORP-FW-ASupplyWork-PurchaseOrder
PaymentDate
PaymentDate
String
ASupply
01-01-01
ACORP-FW-ASupplyWork-PurchaseOrder
Urgency Assign
Urgency of Assignment
String
ASupply
01-01-01
ACORP-FW-ASupplyWork
BillCustomer
BillCustomer
String
ASupply
01-01-01
ACORP-FW-ASupplyWork
DepartmentName
DepartmentName
String
ASupply
01-01-01
ACORP-FW-ASupplyWork
DepartmentNumber
DepartmentNumber
String
ASupply
01-01-01
ACORP-FW-ASupplyWork
ItemDetails
ItemDetails
PageList
ASupply
01-01-01
ACORP-FW-ASupplyWork
Order
Order
PageList
ASupply
01-01-01
ACORP-FW-ASupplyWork
OrderDate
OrderDate
String
ASupply
01-01-01
ACORP-FW-ASupplyWork
OrderTotal
OrderTotal
String
ASupply
01-01-01
Declaratives
Expressions
.LineItemTotal
Rule Name:
Applies to Class:
RuleSet:
.LineItemTotal .Order()
ACORP-FW-ASupply-Work
ASupply : 01-01-01
Execute this expression: Only when the top-level page is of the Applies To class
Calculate value: Whenever inputs change
Set .LineItemTotal = Value of .Quantity*.UnitPrice
.OrderTotal
Rule Name:
Applies to Class:
RuleSet:
.OrderTotal
ACORP-FW-ASupply-Work
ASupply : 01-01-01
Execute this expression: Only when the top-level page is of the Applies To class
Calculate value: Whenever inputs change
94
Set .OrderTotal =
Triggers
None found
OnChange
None found
Constraints
None found
Specifications Matrix
Application
Work Type
Specification
ASupply
PurchaseOrder ApproveOrder
ASupply
PurchaseOrder ConfirmOrder
ASupply
PurchaseOrder EnterDeptInformation
ASupply
PurchaseOrder EnterItemInformation
ASupply
PurchaseOrder PurchaseOrder
ASupply
PurchaseOrder RejectOrder
95
Appe
endix B: The
e Designer S
Studio
o Toolb
bar
and Tab Bar
In the De
esigner Stud
dio, use the
e buttons on
n the toolbarr and tab ba
ar to work w
with rules
and data
a instances in
i your PRPC
C system.
Toolb
bar Butto
ons and
d Functio
ons
The spec
cific tools an
nd selection boxes that appear on tthe toolbar vary depending on
your role
e, the type of
o workspac
ce, and the contents
c
of the form an
nd list area. The
toolbar contains
c
only buttons both relevantt to the ope
en object an
nd available to you. If
a button does not appear or is unavailable (gray), the
e correspond
ding function
n is not
available
e to you in the current context.
c
Figure B-1 describes
s all of the buttons
b
thatt might appe
ear.
Name
Availabilitty
Buttton
Fu
unction
Op
pens the Availability dialog to change the av
vailability of th
he
rule. Select Yes, No/Draft Mode
e, Final, Blocke
ed, or Withdraw
wn to
sett the availabilitty of the rule.
Check In
erator ID settin
ngs allow you tto
Your Ope
check ou
ut rules
The rule
e is not currenttly checked outt to
you.
Creates a copy of
o the rule in yo
our private RulleSet and mark
ks
e original rule as checked ou t (locked). No one else can c
check
the
out a rule while it
i is checked ou
ut.
Delete
96
Name
Buttton
Fu
unction
Delete Ch
heck-
out
Draft On//Off
Favorites
Clic
ck to save a lin
nk to a rule to your My Favorrites menu, or to
dellegate a rule to
o another userr or group of ussers.
Help
Op
pens the help system at the h
help topic for th
he currently
dis
splayed rule or data form.
Launch
Mo
oves the curren
nt rule or data form into a separate, floating
bro
owser window with a copy off its own toolba
ar. This action lets
you
u compare two
o forms, or worrk with some in
nformation or
vallues in the maiin portal windo
ow and paste them into anoth
her
porrtal window.
New
Cre
eates a new ru
ule or data insta
ance of the sa me type as the
e
currrently open ru
ule or data insttance. To creatte a new rule o
or
datta instance of a different type
e, click the arrrow to display a
me
enu to select an
nother rule typ
pe.
Preview
Private Check
Forr a privately ch
hecked-out rule
e in your perso
onal RuleSet,
In
cop
pies the modified instance ov
ver the originall instance in th
he
public RuleSet. After
A
you have performed a p
private check out,
ars if the condiitions that allow
w the rule to b
be
this button appea
ecked in to its base RuleSet a
and version arre present.
che
Private Check
Cre
eates a copy off a rule in yourr personal Rule
eSet. This disp
plays
Out
wh
hen you have th
he pxAllowPriv
vateCheckout p
privilege, the A
Allow
rule check out? checkbox
c
in you
ur operator ID form is selected,
e rule is not av
vailable for regu
ular checkout, and the rule
the
bellongs to a Rule
eSet that has tthe rule manag
gement facility
ena
abled.
Priv
vate check outt is not possibl e for a few rule
e types, such a
as
class rules. Also, you cannot prrivately check o
out a rule that
erride RuleSet..
bellongs to an ove
Reattach
Recover
Related Rules
R
Restore
97
Name
Buttton
Fu
unction
Shows the XML document
d
that makes up the form displayin
ng
Rule Data
a
Run
con
ntext.
Save
Sav
ves the instanc
ce to the Pega RULES databasse.
Save As
Sav
ves the instanc
ce under a diffferent name, R
RuleSet, or vers
sion.
Show Jav
va
Figure B-1
1. Workspace
e Toolbar Butttons
Tab Bar
B Butto
on and Functio
ons
The tab bar identifie
es currently open rule or
o data insta
ances, the Instances lis
st, and
other dis
at the leftt and the Cu
splays. Tabs
s appear bettween the Home
H
icon
urrently
Open
, Refresh , and Close
e
icons. Click a tab to make it tthe front tab
b. For a
tab that represents a rule, hold the mouse pointer ove
er the tab to
o see the ty
ype, full
rule key,, RuleSet, and version information
i
of that rule
e.
Buttton
Home
Func
ction
Click to return to th
he Whats Happ
pening display and your home
view of the portal
Currently
y Open
Refresh
Close
Figure B-2
2. Tab Bar Bu
uttons
98
99
them for you, by signing on and using PRPC briefly. (You do not need Power User or
Administrator privileges to run the ActiveX controls.)
From the Windows Control Panel, double-click Internet Options, or from Internet
Explorer, select Tools > Internet Options. On the Security tab, select the Local
intranet zone to confirm that you can download signed ActiveX controls. You can set
security for the Local intranet zone to Low, or you can select Custom level and enable
the download settings (Figure C-1 and Figure C-2):
Cookies PRPC uses cookies. Confirm that your browsers settings allow cookies.
Pop-up windows Certain portal operations use pop-up windows. Pop-up blockers
(such as the Google toolbar) may interfere with correct operation of these windows.
Scripting PRPC uses JavaScript. Applications based on PRPC may use VBScript or
JScript in addition to JavaScript. Users must have the ability to execute scripts in the
Local Zone. This is available under the Low setting for the Local intranet zone or as a
custom setting:
100
Performance
e Tips an
nd Keyb
board Sh
hortcuts
s
Designerrs, develope
ers and userrs are most productive if they reme
ember these
e tips:
Do
o not use the browsers Back button or Back
k keyboard sho
ortcut. Do not use the
bro
owsers History
y capabilities to
o return to an earlier page. T
The older page
es may
contain stale info
ormation, and the
t
browsers Back and Histo
ory features may interfere
chronization.
witth session sync
on the
t
Designer S
Studio tab bar, not the Intern
net Explorer
or the F5 ke
ey, to refresh tthe current display.
Pre
ess CTRL+F to
o search for tex
xt on a page.
Pre
ess CTRL+P to
o print the currrent page.
ome display.
Ho
101
1
Appe
endix D: Ins
stalling the ASupp
ply
Appllicatio
on
This App
pendix descrribes how to
o install the ASupply ap
pplication. Yo
ou can download the
the Fast_
_Start_62SP
P2.zip and import the ASupply
A
app
plication into
o PRPC.
The Fastt_Start_62SP2.zip file contains
c
two
o files:
AS
Supply_V62SP2.jar the application a
archive to imp
port into PRPC
C
Fa
ast_Start_Guide_62SP2.pd
df this guid
de to working with PRPC a
and the
AS
Supply applica
ation
Installiing the AS
Supply Ap
pplication
The follo
owing proced
dure describ
bes how to import
i
the A
ASupply app
plication into
o your
PRPC sys
stem.
Dependin
ng upon the
e state of yo
our database
e, PRPC win
ndows may a
appear diffe
erently. To
install th
he ASupply application,
a
browse to the
t
location of the ASupply_V62SP
P2.jar file,
and then
n click Nextt throughoutt the Importt wizard to a
accept the d
defaults.
1. Open the Fast_Start_62SP2.zip and
d save the file
es to your loccal directory.
2. Log into yo
our PRPC sy
ystem using an
a operator ID
D and passwo
ord that has tthe
appropriatte privileges to
t import rules (for examp le, privileges similar to tho
ose given
by the Peg
gaRULES:Sy
ysAdm4 acces
ss role). The Designer Stu
udio opens.
3. In the Des
signer Studio,, select the Pega button (
Import & Export > Imp
port (Figure D-1).
D
) and th
hen click App
plication >
Figu
ure D-1. Desiigner Studio Import
I
102
2
4. Brows
se to the ASupply_V62SP2
2.jar file and then click Ne
ext (Figure D--2).
103
3
6. Click Next
N
to updatte the databa
ase schema ( Figure D-4).
Figure D-4
4. Update dattabase schem
ma
Figure D-5
5. Import to database
d
104
4
8. Data is
s saved to the database. This
T
may take
e a few mom
ments. When tthis is
complete, click Nex
xt (Figure D-6
6).
9. Log-ou
ut of PRPC. The
T ASupply application iss ready to usse in the hand
ds-on
exercise, beginning
g in Chapter 2 of this guid e.
105
5
Education services
Documentation feedback
For more information about our company and products, visit our Web site at
www.pega.com.
Education Services
Pegasystems University of Pega offers a wide range of courses for our customers. For
course descriptions and contact information, go to
http://pega.com/services/university-of-pega/pega-education-services. University of
Pega offers both live classes and e-Learning courses. Courses can be presented at
customer sites also.
Documentation Feedback
Pegasystems strives to product high-quality documentation. If you have comments or
suggestions about this guide or about the sample ASupply application, send us an
email with the following information:
Document name, version number, and date it was updated (located at the bottom of
the copyright page)
Page number
106