BAE Exercise Guide

Working with
Business
Architect
PMF Essentials
July 2, 2012
Exercise
Guide
07/23/13
PRPC V6.3 SP1
Copyright2013
PegasystemsInc.,Cambridge,MA
Allrightsreserved.
ThisdocumentdescribesproductsandservicesofPegasystemsInc.Itmaycontaintradesecretsandproprietary
information.Thedocumentandproductareprotectedbycopyrightanddistributedunderlicensesrestrictingtheir
use,copyingdistribution,ortransmittalinanyformwithoutpriorwrittenauthorizationofPegasystemsInc.
Thisdocumentiscurrentasofthedateofpublicationonly.Changesinthedocumentmaybemadefromtimeto
timeatthediscretionofPegasystems.ThisdocumentremainsthepropertyofPegasystemsandmustbereturned
toituponrequest.Thisdocumentdoesnotimplyanycommitmenttoofferordelivertheproductsorservices
described.
ThisdocumentmayincludereferencestoPegasystemsproductfeaturesthathavenotbeenlicensedbyyour
company.Ifyouhavequestionsaboutwhetheraparticularcapabilityisincludedinyourinstallation,pleaseconsult
yourPegasystemsserviceconsultant.
ForPegasystemstrademarksandregisteredtrademarks,allrightsreserved.Otherbrandorproductnamesare
trademarksoftheirrespectiveholders.
AlthoughPegasystemsInc.strivesforaccuracyinitspublications,anypublicationmaycontaininaccuraciesor
typographicalerrors.ThisdocumentorHelpSystemcouldcontaintechnicalinaccuraciesortypographicalerrors.
Changesareperiodicallyaddedtotheinformationherein.PegasystemsInc.maymakeimprovementsand/or
changesintheinformationdescribedhereinatanytime.
Thisdocumentisthepropertyof:
PegasystemsInc.
101MainStreet
Cambridge,MA021421590
Phone:(617)3749600
Fax:(617)3749620
www.pega.com
Document:BusinessArchitectEssentials
Updated:July23,2013
Table of Contents
Getting Started with BAE .................................................................................................................. 1
Explore the Business Analyst Portal .................................................................................................. 5
Explore the PurchaseFW Application ................................................................................................ 13
Read the LES Time Off Application Mandate .................................................................................... 23
Read the LES Time Off Application Document .................................................................................. 25
Review the Purchase FW Application Profile..................................................................................... 27
Create a New Application Profile ....................................................................................................... 29
Identify PTO Work Types ................................................................................................................... 33
Define the Work Types in the PTO Application Profile ...................................................................... 35
Create the Discovery Maps for the PTO Application ......................................................................... 37
Add Actors to the PTO AP ................................................................................................................. 41
Add Specifications to the PTO AP ..................................................................................................... 43
Generate the Application Profile Document ....................................................................................... 47
Import a Completed PTO Application Profile ..................................................................................... 49
Complete the PTO Application Profile ............................................................................................... 51
Run the Application Accelerator ......................................................................................................... 55
Create and Edit Rules ........................................................................................................................ 61
Generate a Baseline Application Document ...................................................................................... 65
Modify and Test Draft Flows .............................................................................................................. 67
Add a Decision Shape........................................................................................................................ 69
Working with Flow Actions ................................................................................................................. 73
Set Work Item Status ......................................................................................................................... 77
Route Work ........................................................................................................................................ 81
Create a Screen Flow ........................................................................................................................ 83
Reference a Screen Flow from Another Flow .................................................................................... 87
Add Specifications to Flow Shapes .................................................................................................... 89
Create a Section and Add Layouts .................................................................................................... 93
Add Labels to a Layout ...................................................................................................................... 99
Create a Flow Action .......................................................................................................................... 101
Add a Flow Action to a Flow Shape ................................................................................................... 103
Add a Control to a Field ..................................................................................................................... 105
Make a Field Required ....................................................................................................................... 109

Configure a Control ............................................................................................................................ 113
Reuse a Section ................................................................................................................................. 115
Nest a Section in a Section ................................................................................................................ 117
Create a Single Value Property ......................................................................................................... 119
Add a Single Value Property to a Field in a Section .......................................................................... 123
Create a Page Property ..................................................................................................................... 125
Add a Page Property to a Field in a Section ...................................................................................... 129
Use an Inherited Property .................................................................................................................. 131
Set Initial Property Value Using a Data Transform ............................................................................ 133
Create a When Rule........................................................................................................................... 135
Reference a When Rule on Decision Shape Connectors .................................................................. 137
Create a Declare Expression ............................................................................................................. 141
Create a Service Level for an Assignment......................................................................................... 145
Add Notifications to a Flow................................................................................................................. 147
Create a Correspondence Template.................................................................................................. 149
Modify a Standard Report Using the Report Browser ........................................................................ 153
Create a List Report using the Report Definition ............................................................................... 159
Document the Application Using the Document Application Wizard ................................................. 163
Exercise: Getting Started with BAE

Objectives
After completing this exercise, you will be able to
Be familiar with the structure of course exercises
Access the course exercise system
Log in to PRPC
View related content on the Pega Developer Network
Scenario
Exercises in this course give you hands-on practice with the skills learned in the lessons. Before
continuing with the course, you should make sure that the exercise environment is working correctly and
that you understand how to access the system as well as supplemental content to help you complete the
exercises.
Note: You must have downloaded and installed the PVS exercise system as explained in the previous
lesson before completing this exercise.
Role: Business Architect
User Name: becky@les.com
Password: rules
Tasks
1. Log in to PRPC
2. Bookmark PRPC
3. Log out of PRPC
4. View related content links for this lesson
How To Do It
1. Log in to PRPC
a. In Internet Explorer, go to PVS course page using URL http://prpc:8080.
b. Follow the link for the PRPC Process Commander (http://prpc:8080/prweb/PRServlet)
Note: this page contains the login information for the course; you may wish to bookmark
it for future reference.
c.
The PRPC login page displays. Bookmark this page in Internet Explorer; you will be
coming back here frequently throughout the course.
d. Enter user ID becky@les.com and password rules.
e. Confirm that the PRPC Business Analyst portal appears.
2. Log out of PRPC

a. Click the logout link in the upper right corner.
Note: If you stay logged in to PRPC and are inactive for 30 minutes, your session will
time out. You will need to log out and log back in to access any PRPC features.
3. View related content in the Pega Developer Network.
a. Follow the links to related content on the exercise page on Pega Academy.
Hints
1. The PRPC login URL is http://prpc:8080/prweb/PRServlet
2. The login ID and password are in the Scenario section of the exercises.
3. The Logout link in PRPC is on the upper right of the portal screen.
Exercise: Explore the Business Analyst Portal

Objectives
After completing this exercise, you will be able to:
Log in to the BA portal
Navigate the BA portal
Use context-sensitive and general help
Search for rules
Scenario
You are a business architect at LES. Before you can start working on Pega applications, you need to be
familiar with the PRPC Business Analyst Portal. A scavenger hunt for information in the portal will help
you learn how to find your way around.
You should be able to answer the questions below using tools that were shown or discussed during the
lesson. You may need to hunt around a bit, but if you need step by step instructions you can look at the
solution steps below.
Password: rules
Tasks
1. What tab is showing by default in the work space when Becky first logs in?
2. What is Beckys position title?
3. What is the first tab on the Application Document landing page?
4. What applications does Becky have access to?
5. Your application explorer disappeared when you started the Document wizard. How can you get
it back?
6. What is the first button in the Layout tab toolbar shown in the user interface section definition for
the billing address collection form?
7. What does that button do?
8. How many navigation controls are available in the PRPC help system, and what do they do?
9. Challenge question: what resources exist for new Business Architects? (Hint: Use the PDN)
How To Do It
1. What tab is showing by default in the work space when Becky first logs in?
a. In Internet Explorer, open PRPC by visiting http://prpc:8080/prweb/PRServlet.
Note: you must use Internet Explorer. Other browsers do not support the Business
Analyst Portal.
Hint: Bookmark this page; you will be returning here frequently in later exercises.
b. Enter username becky@les.com and password rules, and click Log In.
c.
Note the selected tab in the work space.
2. What is Beckys position title?

a. On the user menu (labeled Becky BA), select Profile.
b. Note the position field in Beckys profile.
3. What is the first tab on the Application Document landing page?

a. Click the Pega button and select Application Actions > Document Application.
b. Note the tab names.
4. What applications does Becky have access to?

a. Click on the application menu (labeled PurchaseFW), select Switch Application and note
the list of available applications.
5. Your application explorer disappeared when you started the Document wizard. How can you get
it back?
a. One of two ways:
Close the tab (by clicking the X)
Open the navigation pane by clicking the arrows in left margin of the workspace.
6. What is the first button in the Layout tab toolbar shown in the user interface section definition for
the billing address collection form?
a. Enter billing in the search bar and then click the search icon (or hit the Enter key).
b. Click to open the BillingAddress section.
c.
Note the first button on the Layout tab.
7. What does that button do?

a. First, hover your mouse over the button and note the tooltip description.
b. Get more information by clicking the help button for the work space tab.
c.
In the help window, select information on the Layout tab.
d. Open the topic Identifying controls on this tab
e. Read the paragraph that explains the Show Wireframes button.
8. How many navigation controls are available in the PRPC help system, and what do they do?
a. Open the online help system by clicking the help icon in the main toolbar.
b. Open the Using this help system topic in the table of contents.
c.
Locate the list of navigation controls.
d. Alternative: use the Search function instead of the table of contents.
9. Challenge question: what resources exist for new Business Architects? (Hint: Use the PDN)
a. Click the main menu help icon and select Pega Developer Network > PDN Home
b. If necessary, log in using your PDN/Pega Academy sign in.
c.
Enter businessarchitect in the search field and click the search icon.
10
d. Click Show Filters, and filter for Introduction Articles for your version of PRPC.
e. Select the first starred article
11
12
Exercise: Explore the PurchaseFW Application

Objectives
Be familiar with the user experience of the PurchaseFW application
Use the Case Worker and Case Manager portals to complete work item tasks
Use context-sensitive and general help
Scenario
You are a business architect working for the Lets Eat Something company (LES). Youll soon be starting
work on LESs second Pega application, to track employee time off. First, though, you want to familiarize
yourself with LESs existing application, the Purchasing Framework (PurchaseFW).
This exercise will also help you become familiar with the Case Worker and Case Manager portals.
Role: Request Originator
User Name: wally@les.com
Password: rules
Role: Manager
User Name: manuel@les.com
Password: rules
Role: Fulfillment Worker
User Name: frank@les.com
Password: rules
Role: Purchaser
User Name: polly@les.com
Password: rules
Tasks
1. Log in as the request originator. Create and submit a new purchase request containing several
items.
13
2. Log in as the manager. Approve the purchase request.

3. Log in as the fulfillment worker and select a fulfillment type for each line item. Make sure you
have at least one Inventory item and one Purchase Order item.
4. Complete the inventory request.
5. If necessary, log in as the Purchase manager and approve and complete any open purchase
orders.
6. Log back in as the request originator to review and confirm completion of the request.
How To Do It
1. As Wally the worker, create and submit a new purchase request containing several items.
a. Log in to the PRPC as user wally@les.com (password rules.)
Note: If you need a reminder of how to access PRPC, review the exercises in the
Using the Business Analyst Portal lesson.
b. The Case Worker portal displays. Click on the New menu in the upper right corner and
choose Purchase Request.
c.
A new tab appears for the new purchase request. Take note the work item ID on the tab:
PR-n.
d. Fill out the first screen for the shipping information. Fields noted with an asterisk (*) are
required, the others are optional.
14
e. Move to the next step either by clicking the Next>> button at the bottom of the screen, or
clicking on the Select Catalog Items tab.
f.
On the Select Catalog Items tab the list of selected items starts out empty. Add a new
item by clicking the Add a row button ( ).
g. In the Select from Catalog popup window, select a category and then a product from the
menus, and then enter a quantity of items to select.
h. Click the Add button to add current item to the list, and reset the popup to add a second
item.
i.
Repeat this step adding at least four items to the request. For at least one item, choose
a large number for the quantity (greater than 100); later in the process you will be able to
see how requests for more items than are in stock are handled.
j.
On the last item you select, click OK instead of Add to close the popup window.
k.
Confirm that your line item list now looks something like this:
15
Note: you can remove a line item by clicking the associated Delete this row button,
which looks like a garbage can ( ). You can change a line item but double-clicking the
row, changing the values in the popup, and clicking OK.
l.
When youve completed catalog item selection, move to the next step by clicking Next or
selecting the next tab in the sequence (Collect Billing Info.)
m. On the next screen, deselect Use shipping address and note that a form to enter a
billing address appears. Select it and note that the billing address form disappears.
n. Move to the next step to review the final request. If you want to make any changes to the
request, you can go to previous steps using the tabs or the Back>> button.
o. When you have confirmed that the request is correct, click the Finish button.
p. A confirm screen displays. Note that the next step in the process is the Review
Purchase Request, and that step is assigned to Wallys manager Manuel.
q. Wallys work on this work item is complete now. Close the work item tab by clicking the
red X.
r.
Log out of the Case Worker portal by clicking on Wallys user menu and selecting Log
off.
16
2. As Manuel the manager, approve the purchase request.

a. Log in to PRPC as user manuel@les.com (password rules).
b. The Case Manager portal displays. As the manager of the Sales team, Manuel can view
all the team members work lists, and the team work basket. Select Manuels work list.
c.
In the work pane on the right, the items on the selected work list are shown. Right now,
there is just one the Purchase Request that Wally just submitted. Double click on the
row to open the work item.
d. The work item displays in a new tab. Manuel has two actions he can take: approve or
reject the request. The default option is to approve, so the Approve action form is
currently displayed.
17
e. Optional: You can view Manuels other possible action: Choose Other Actions > Reject to
see the Reject action form. Then select Other Actions > Approve to return to the
Approve action form.
f.
Optional: Click the Where Am I link (

) button to see your current location in
the purchase request work flow. Close the window when you are done.
g. Approve the PR by clicking the Approve button at the button of the Approve action form.
h. Note the next step and the work basket the item is assigned to on the confirmation
screen.
i.
Manuels assignment on this work item is now complete. Close the work item tab and log
out of the Case Manager portal.
3. As Frank the fulfillment worker, select a fulfillment type for each line item in the PR
a. Log back in to PRPC as frank@les.com (password rules.)
b. The Case Worker portal displays. Frank has no items assigned to him at the moment, so
get the next item out of the Fulfillment workbasket by selecting Options > Get Next
Work (upper right corner of the portal).
c.
The work item created by Wally and approved by Manuel displays in a new tab. Each
line item has an option to indicate whether the item should be fulfilled from stock currently
in inventory, or should be fulfilled by submitting a purchase order to the supplier. The
default is Inventory for items that are available in stock in sufficient quantity, and
Purchase Order for other items. Make sure at least one item has Purchase Order
selected, and at least one item has Inventory.
d. Optional: Click the Audit link (

) near the top right of the work item tab to view a
history of actions taken on this work item. After reviewing the list, close the window by
clicking the Close button.
18
e. Click the Submit button.

f.
Take note of the confirmation screen. The current item (e.g. PR-11) is now assigned
back to Wally for final confirmation after all items have been delivered. Subcases have
also been added: a request to ship all the inventory items (e.g. IR-8) and a Purchase
Order for each item to be fulfilled by PO (e.g. PO-10).
4. As Frank, complete the Inventory Request

a. Note that one of the subcases the Inventory Request is assigned to the current user,
Frank. Click on New Inventory Request to complete the task.
b. The inventory request subcase opens in a new tab, showing a list of items to fulfill from
inventory. Franks job is to check of each item as he prepares it for shipping. But what if
he only prepares some of the items before his lunch break begins? Check one of the
items on the list, then click the Save link.
c.
Close the work item tabs and take a lunch break.
d. When you return from lunch, select Options > Get Next Work. The inventory request
item you were working on before re-opens where you left off.
e. Check off the remaining items on the list, then click Submit for Shipping.
19
f.
The inventory request subcase is now complete, but what about the rest of the purchase
request? You can see all the related cases by clicking the Purchase Request main case
at the top of the work tab.
g. There may be an open Purchase Order subcase. This is because some orders require
manager approval those over $1000, for instance and some get automatically
submitted to an external PO system. Take note of any open POs.
h. Franks work on this item is complete. Log out.

5. Optional challenge: if there are open Purchase Orders, log in as user polly@les.com and approve
all the items in the Purchase departments work basket. (Hint: use Options > Get Next Work)
6. Imagine time passes, and all items have been fulfilled. Wally needs to confirm fulfillment before
the purchase request can be resolved.
a. Log in to PRPC as Wally again.
b. Click on the My Worklist tab (
c.
).
Double click on the purchase request work item on the list.
d. Click on the calendar icon in the date field and choose a date from the calendar popup.
20
e. Click Confirm to complete the assignment.

f.
Close the work item tab.
g. Click the Refresh button (

request is no longer there.
) on your work list tab and note that the purchase
h. Optional: use the search field to find the resolved purchase request: enter the work item
id (e.g. PR11) in the search field and click the search icon. Or, if you dont remember the
work item, enter PR to get a filterable list of all purchase request items.
21
22
Exercise: Read the LES Time Off Application Mandate

Objectives
Understand the business objectives for the PTO (Personal Time Off) application
Be prepared to implement the PTO application in the exercises in the rest of the course
Scenario
work on LESs second Pega application, to track employee time off. The first step is to become familiar
with the business drivers and goals for the new application.
Tasks
1. Read the LES project documents provided in this exercise, including the project mandate and
high level requirements.
Note: Save these documents; youll refer to them later as you start to build the application.
23
24
Exercise: Read the LES Time Off Application Documents

Scenario
work on LESs second Pega application, which is to track employee time off.
LES has created a preliminary requirements document including a set of use cases. As a BA, you will be
responsible for translating these requirements and use cases into specifications in the application profile,
and then elaborating on them collaboratively as part of the DCO process.
The first step is to simply familiarize yourself with the preliminary requirements. In later exercises, youll
work with these directly in PRPC.
Tasks
1. Read the LES Time Off application requirements.
25
26
Exercise: Review the Purchase FW Application Profile

Objectives
After completing this exercise you will be able to
Open an existing Application Profile
Navigate through an existing Application Profile in the Application Profiler tool
Access the Application Profiler help
Scenario
work on LESs second Pega application, to track employee time off. First, though, you want to familiarize
yourself with LESs existing application, the Purchasing Framework (PurchaseFW).
Password: rules
Tasks
Log into the Business Analyst portal
View the list of application profiles in progress
Reopen the PurchaseFW application profile (dont modify it)
Briefly review the contents of each tab.
Use the context sensitive help button on each tab
How To Do It
1. Log into PRPC as user becky@les.com (password rules). You are now viewing the existing
PurchaseFW application in the Business Analyst portal.
2. Open the original AP that was created at the start of the PurchaseFW project.
a. Click the Pega Button and select Application Actions > Open Profile.
27

b. Select the completed Purchase AP.
c.
Because this AP is already complete, to view it, you need to reopen it. Click the Reopen
Profile button.
d. The first tab is the Create Processes tab that lets you see the discovery maps for each
work type. View the starting processes for each of the PurchaseFW work types by
selecting them:
e. Click the Instructions button

to see help for this tab. The Instructions button is
located in the upper-right corner of the BA Portal, near the Actions menu.
f.
Briefly review the contents of the other sections of the Application Profile by selecting the
associated tab Interfaces, Reporting and so on . On each tab, review the help for the
tab. After you have reviewed a tab it will be marked with a green checkmark.
3. When you are done, you can close the Application Profiler tool by clicking the X in the upper left
hand corner:
Reference Information:
https://pdn.pega.com/implementation-methodology-dco/dco-62-creating-application-profiles-anddiscovery-maps
28
Exercise: Create a New Application Profile

Objectives
After completing this exercise you will be able to
Create a new Application Profile
Complete an Application Profile overview with information provided by a system architect or lead
business architect
Scenario
Now that you are familiar with the existing project documents, you and your colleague Sam SA (the
projects system architect) are ready to begin work on the application profile for the LES Time Off
application (PTO). Sam has determined that the new application will be a framework because it will be
used as the basis for a number of specific implementations that vary by region and division within LES.
Password: rules
Tasks
Log into the Business Analyst portal
Create a new Application Profile
Complete the AP overview with the following characteristics determined by the projects system
architect:
o
A new framework, not built on any existing application or framework, called PTO
Part of existing organization LES.com
Built by internal resources
Complete the business objectives and description based on the project mandate
document
How To Do It
1. Log into PRPC as user becky@les.com (password rules). You are now viewing the existing
PurchaseFW application in the Business Analyst portal.
2. Click the Pega button and select Application Actions > Define Profile.
29
3. When the Application Profile Overview popup window appears, complete the dialog as follows:
a. Profile options: NewApplication
b. Build: NewFramework
c.
Built on Framework: none
d. Organization Name:LES.com(default value)

e. Application Name: PTO
f.
Project Name: PTOVersion1 (default value)
g. Project Led By: ClientSelfLed

h. Implementation Methodology: PegaBPM
i.
Business Objectives: Copy from project mandate
30
4. Click OK to create the AP.

5. Save the AP by opening the Actions menu and selecting Save. (You will continue work on this
AP in later exercises.)
31
32
Exercise: Identify PTO Work Types

Objectives
Identify an applications required work types based on the business requirements
Scenario
In a previous exercise, you created a new Application Profile for the LES PTO application. The first step
in completing the AP is to identify what work types the application requires.
Tasks
1. Based on the business requirements and use case specifications for PTO you reviewed earlier,
identify the work type(s) required by the PTO application. Give a brief description of each work
type. This is a pencil-and-paper exercise; note your findings below:
_________________________________________________________________________
_________________________________________________________________________
How to Do It
PTO requires one work type:
Time Off Request this captures the information about the employees request for time off
the type of time off, the dates, and so on. This is the primary work type. Most of the application
requirements relate to this work type, such as
o
Employee completes new time off request
Manager approves or rejects each time off request
Note: There are many different approaches that could be taken to designing a Pega application to meet
any given set of requirements; this solution reflects just one possible design. If you identified a different
set of work types for PTO, your answer is not necessarily wrong, just different. In this course we will use
this work type for consistency across exercises.
33
34
Exercise: Define the Work Types in the PTO Application Profile

Objectives
Add work type definitions to an Application Profile
Scenario
In the previous exercise, you identified the work types that are required in the PTO application. After
conferring with Sam SA, you both agree that these are suitable, so now you need to add these to the
PTO application profile.
Password: rules
Tasks
Log into the business analyst portal
Open the PTO application profile
Define the necessary work types
Use the context sensitive help as necessary
How To Do It
1. If you are logged out of PRPC, log back in as user becky@les.com (password rules).
Note: In future exercises, you will not be reminded to log into PRPC. This is a necessary first
step in all exercises.
2. If necessary, open the existing PTO application profile by selecting Pega Button > Application
Actions > Open Profile.
3. Make sure you are on the Create Processes tab in the AP wizard.
35
4. A default work type called PTO was created for you. You can re-use this by renaming it. Select
Options > Edit work type details.
5. Change the work type name to TimeOffRequest, the display label to TimeOffRequest and the
prefix to TR. Fill in a description based on known requirements.
6. Click OK.
7. Save the AP by opening the Actions menu and selecting Save.
36
Exercise: Create the Discovery Maps for the PTO Application

Objectives
Create a Discovery Map in an Application Profile to visually lay out the process requirements for
an application
Scenario
You previously created a new application profile for the PTO application, and defined the necessary work
type(s). Now you need to start working on mapping out the processes that works items of these types will
go through. Start with the starting process for the primary work type.
Password: rules
Tasks
Create a discovery map for the TimeOffRequest work type that meets the requirements laid out
the PTO Requirements document you reviewed previously
Add specification details to each step
There is no single correct map, as there are many valid approaches. The steps below guide
you toward one possible map (shown at the end of the solution steps), but feel free to experiment
with alternatives
Refer to the Create Processes tab help content for instructions on adding, moving, editing and
deleting steps in Discovery Map view
How To Do It
1. Go to the Create Processes tab in the PTO application profile.
2. Make sure the TimeOffRequest work type is selected.
3. By default, the name of the starting process is derived from the work type name. In this case, the
process name is StartTimeOffRequest. The automatically generated discovery map initially
contains a single shape with a generic name. Single click on the name of the shape to change
the name. Enter the new name EmployeeRequestsTimeOff. Click anywhere outside the name
field to confirm the change.
37
4. Double click the empty box to the right of the first step to add a new step. Following the same
process as above, change the name of the step to ManagerReview. The discovery map should
look like this:
5. Add a new step to the right of ManagerReview and change the name to ProcessPTORequest.
6. Add a new step below ProcessPTORequest. This changes the ProcessPTORequest step to a Sub
Process shape automatically. Name this step UpdatePTOBalance.
7. Double click the UpdatePTOBalance shape to see the details window. Most of these fields can be
left at their detail values for now. In a later lesson, you will use this screen to add step
specifications. For now, just set the Shape type to Integration, then click OK to confirm the
settings and close the details window.
8. Add one more step below UpdatePTOBalance, name it NotifyEmployee and change the shape
type to Automated Step. The discovery map should like this:
38
9. Right click on the ProcessPTORequest step and choose Add New Alternate Step.
10. Change the name of the new (alternate) step to HRReview.

11. If you are following our solution, the discovery map should look like this:
39
12. Save the AP.

Note: From now on, you will no longer be prompted to save your work in the Application Profiler
wizard. Remember to save frequently.
Reference Information: Creating Application Profiles and Discovery Maps

(https://pdn.pega.com/implementation-methodology-dco/dco-62-creating-application-profiles-anddiscovery-maps)
40
Exercise: Add Actors to the PTO AP

Objectives
Add Actors to an application profile
Scenario
In previous exercises, you created a new AP for the LES Paid Time Off application and defined the
required work types and processes. Now continue working on the AP by adding actors corresponding to
the various roles in the application.
Password: rules
Tasks
Review the PTO requirements document and identify the actors
Add definitions for the actors to the PTO AP
How To Do It
1. Open the PTO AP.
2. Select Actions > Actors.
3. Enter each type of actor identified in the requirements: employee, manager and HR Director. The
default values of Operator for type and Browser for access are correct.
4. Click OK to confirm the Actors list.
41
42
Exercise: Add Specifications to the PTO AP

Objectives
Use the Project Explorer tab in the Application Profiler wizard
View, add, edit and organize specifications in an Application Profile
Import and export specifications in an Excel spreadsheet
Scenario
Specifications are how the details of an applications requirements will be met. Although many
specifications will be created and added in the course of working on the Discovery Map and other areas
in the application profile, and more will be added during DCO Elaboration, some are known up front.
Some of the specifications for PTO were identified during the preliminary planning for the project and
collected in various documents. Enter this into the AP so that you no longer need to maintain numerous
documents.
Password: rules
Tasks
Review the PTO requirements document and select one of the use cases to enter as a PRPC
specification. For this exercise, we will use the Employee Request for Time Off use case
Add a specification to the correct work type in the Application Profiler project explorer tab for the
selected use case
Download the specification template spreadsheet and review
Import the completed spreadsheet provided for your convenience: PTOSpecificationsAndRequirements.xlsm.
How To Do It
1. Open the PTO AP.
2. Select the Project Explorer tab.
3. Select the TimeOffRequest work type.
4. Click Add Specification
43
5. In the Details tab, enter values as follows (other values can be left as default for now):
a. Specification: EmployeeRequestforTimeOff
b. Actors: Employee (the auto-complete icon means you can type in one or two characters
and use the down arrow to bring up a context-sensitive list of available options in this
case, the actors you added in the previous lesson)
c.
Business Objective: choose the most appropriate from the list of objectives you entered
when you created the AP
6. Select the Description tab, and copy in the description from the PTO Requirements document.
7. Click OK when done.

8. Confirm that the new specification now appears in the explorer under the correct work type.
44
9. Click Download Template and save the generated file. The default filename will be based on
the ID of the application profile and your computer name, e.g. pxAP2
SpecificationsAndRequirements.xlsm.
10. Open the downloaded file in MS Excel or a compatible spreadsheet program. Note that the file
contains the few specifications youve entered, and that several fields in the template, such as
work type, provide available options based on information youve already included in the AP. In
the real world, you would edit this file to add specifications for import. When you are done
reviewing, close the file.
11. To save you time in these exercises, youve been provided with a completed specification
spreadsheet to import: PTOSpecificationsAndRequirements.xlsm. Review the contents of the
spreadsheet. In the project explorer tab, click Import. Select the file and click Upload.
45
46
Exercise: Generate the Application Profile Document

Objectives
Generate an Application Profile document
Scenario
You have created an Application Profile for the PTO application and included a first pass at the
requirements, some initial specifications and a discovery map. Now you need to work with stakeholders
and team members to make sure all the requirements are correctly captured in the AP. Start by
generating a draft AP document for review.
Password: rules
Tasks
Generate a draft AP document.
How To Do It
1. Open the PTO Application Profile.
2. On the Actions menu, select Document.
3. All the settings can be left as their default values.
47
4. Click Generate Document.

5. Microsoft Word will load in a series of templates. Depending on your settings in MS Word, you
may be prompted for a conversion type for each imported template; confirm the default selection
by clicking OK.
6. When the document is complete, review it.

7. Close the document window.
48
Exercise: Import a Completed PTO Application Profile

Objectives
Withdraw an AP
Import an AP
Scenario
In the real world, completing an AP may take several days of dedicated effort. To save time in the
exercises, and to make sure the PTO Application Profile is complete and ready to use in later exercises to
generate the application foundation, withdraw the practice AP youve been working on and import a
final version of the AP.
Important Note: This exercise must be completed before continuing the exercises.
Password: rules
Tasks
1. Withdraw the AP youve been working on.
2. Import the final PTO AP zip file provided with the course materials.
3. Review the imported AP.
How To Do It
1. Withdraw the existing AP
a. Open the existing PTO AP if necessary.
b. Select Actions > Withdraw.
c.
Confirm that the status is now Resolved-Withdrawn.
2. Import the final version of the PTO AP
49
a. Click the Pega button and select Process & Rules > Distribution > Import to start the
Import Wizard.
b. Click Browse, then locate and select the PTO-AP-final.zip file.
c.
Click Next>> to upload the file to PRPC.
d. Confirm the correct file name is selected on the next screen and click Next>> to import
the uploaded file.
e. The import may take a few minutes. When it is complete, click Done.
f.
To open the newly imported AP, select the Pega button > Application Actions > Open
Profile. Open the final PTO AP.
3. Review each of the tabs in the AP to compare to your practice version.
50
Exercise: Complete the PTO Application Profile

Objectives
Add attachments to an AP
Incorporate review feedback during an AP review cycle
Close a completed AP
Scenario
As part of the iterative AP process for the PTO application, you have previously circulated a draft
Application Profile document and received feedback and additional information from other project
participants. For instance, there are missing correspondence requirements. Now you need to incorporate
the feedback and complete the AP.
Important Note: Be sure you have completed the previous exercise and imported the final version of
the PTO AP.
Password: rules
Tasks
1. Add correspondence requirements for PTO approvals and rejections.
2. For archival purposes, attach the project mandate and requirements documents to the AP.
3. Finish the AP.
How To Do It
1. Open the PTO AP.
2. Add correspondence requirements for time off request approval and rejection notices
a. Select the Correspondence tab.
b. Click the Add a Row (
c.
) button.
Add a correspondence name RequestApproval.
d. Enter a description.
51
e. Click Add to save this row and add a new one.

f.
Enter a name and description for Request Rejection.
g. Click OK to confirm.
3. Attach the initial project documents to the AP.
a. Click the paperclip button (
tool.
) in the upper right-hand corner of the Application Profiler
b.
Click Add and choose Attach a File.
c.
Enter a description, select Category: File, then use the Browse button to locate and
select the mandate document.
d. Click OK to upload the document and attach it to the AP.
52
e. Open the list of file attachments to confirm that the file attached correctly.
4. Optional: generate a new Application Profile Document for final review and sign-off.
5. Finish the AP.
a. Select the Project Explorer tab.
b. Click the Finish button. The AP is now complete.
c.
View the list of APs in progress by opening the Pega menu and selecting Application
Actions > Open Profile. Confirm that the PTO AP is no longer in the Application Profiles
in Progress list, and the status is set as Resolved-Completed in the Application Profiles I
Can Modify list.
53
54
Exercise: Run the Application Accelerator

Objectives
Understand the steps the SA takes in the Application Accelerator
Scenario
You have completed the PTO Application Profile, and are now ready to pass the AP to the system
architect, Sam. In the real world, Sam would run the Application Accelerator himself. For educational
purposes, youve been asked to run the Application Accelerator to learn how the Application Profile gets
translated to the application accelerator. You will not use the accelerator to build the application in this
exercise.
Password: rules
Tasks
Run the Application Accelerator but do not generate the application; review the steps in the AA
Import the generated application in the file PTOFWgenerated.zip
How To Do It
1. Run the Application Accelerator but do not generate the application for the PTO application
profile.
a. Click the Pega button and select Application Actions > Build Application.
b. In the Application Overview dialog, select the AP from the list for the first field.
55
c.
Selecting the AP fills in default for the other fields. Leave these as their default values.
Click OK to dismiss the dialog.
2. Review the steps of Application Accelerator wizard.

a. The first step is the Base and RuleSets step. System Architects can change the class
name, organization name and RuleSet name in this step. For a new application, the
wizard can also be used to create test operators. If the operators already exist, the
wizard can add the new application to those operators lists of available applications.
b. Select the Create Processes tab to see the Discovery Map created in the Application
Profile. SAs can add additional specifications, or change the Discovery Map if necessary.
c.
Select the Class Structure tab to see the classes that will be created. The class
structure of an application will be covered in a later lesson.
d. Select the Reporting tab. Note that the reports from the AP are here, but the SA can
add additional detail, such as a report category and a work type the report applies to.
Report categories and classes will be covered more later.
e. Select the Correspondence tab. Note that, similar to the Reporting tab, the AP
correspondence is here, but the SA can modify them, or add detail regarding the class
the correspondence applies to.
f.
Select the Roles tab. This allows the SA to define work parties for work items;
individuals who are involved with a work item in some capacity, such as the employee
who requested time off, and the manager who approved it. Work parties will be
discussed later in the lessons on Correspondence.
56
g. Select the Project Explorer tab. This works much as the same tab in the AP. It displays
the specifications defined for the application in the Application Profile. System Architects
can add additional specifications, requirements and supporting types if required.
h. The Review Application tab displays all the rules that the wizard will generate as part of
the application foundation.
DO NOT click the Build the Application button. SAs are responsible for making the
required changes in the Application Accelerator before generating the application.
i.
Because this Application Accelerator task was for educational purposes only, withdraw it
before continuing: select the Actions menu in the upper right and select Withdraw.
j.
Click Close.
3. Import the zip file containing the baseline application generated by the system architect.
a. From the Pega button select Process & Rules > Distribution > Import.
57
b. In the Import wizard, click Browse and select the PTOFWgenerated.zip file you
downloaded for this exercise on your local machine.
c.
Click Next to import the file.
d. You may get a warning screen that database changes are required by this import. Make
sure the Automatic option is selected, then click Next.
e. You may get a warning that some instances in the import are older than ones already in
the system. Make sure the Import Aged Updates option is selected, then click Next.
58
f.
Wait until the final step reaches 100%, then click Done to finish.
g. To access the new application, log out and back in (still as user Becky). The new
PTOFW application is now the default. You can switch between PurchaseFW and PTO
using the Application Menu (PTOFW) > Switch Application.
59
60
Exercise: Create and Edit Rules

Objectives
Understand the class tree and associated rules generated by the Application Accelerator
Use the Application Explorer to browse the class tree and locate applicable rules
Open, modify and save an existing rule
Create a new rule for a generated work class
Scenario
The application foundation for the PTO application has been generated and it is now time to start working
directly on the application as part of the elaboration process.
First, you should just familiarize yourself with the work types and work group classes, and the rules that
make up the initial application foundation.
Then start the elaboration process by editing the generated time off starter flow rule to use a more userfriendly description.
Youll also start working on a new flow action rule called SubmitRequest. Eventually this rule will connect
the starting flow to the user interface rule to display the Time Off Request form employees fill out. For
now, just create it as an empty rule, and youll continue working on it in later exercises.
Password: rules
Tasks
Switch to the new PTOFW application
View the class tree in the Application Explorer
Change the description setting of the RequestTimeOff starting flow
Create a new Flow Action rule called SubmitRequest. (Youll complete and use the rule later.)
61
How To Do It
1. Open the application menu (labeled with the current application, PurchaseFW) and select Switch
Application > PTOFW to switch to the newly created application.
2. Make sure that the navigation pane is showing the Application Explorer. If not, switch to the
Application Explorer view using the menu.
3. Most of your work will be done in the TimeOffRequest work type. Expand the work type in the
explorer to see the categories of rules generated by the AA.
4. One of the most important rules the AA created was the starting flow for the TimeOffRequest
work type. Find that rule in the explorer.
a. Open TimeOffRequest > Process > Flow to see the flows generated by the AA.
b. The green arrow indicates the starting process (flow) for the work type. The blue dots
indicate sub-processes.
62
5. Although this application contains only one work type so far, you can view rules that would be
shared between all work types by looking in the class group, also called the work pool: LES-FWPTOFW-Work. Review the rules in the work group.
6. Change the description setting of the RequestTimeOff starting flow
a. Open TimeOffRequest > Process > Flow. Click the StartTimeOffRequest flow to open
it in the work pane on the right.
b. Open the rule header by clicking the > button:
c.
Change the description to CreateaTimeOffRequest
d. Save the change by clicking save button:

was saved correctly.
. Look for the checkmark to confirm that it
This change is not reflected automatically in the Run menu. Changes to the Run menu do
not take effect until we either log out and log in, or press F5 to refresh the browser.
63
7. Create a new Flow Action rule called SubmitRequest

a. Right click the TimeOffRequest class in the Application Explorer and choose New > User
Interface > Flow Action.
b. Enter the name SubmitRequest. Confirm that the default values of the Applies to and
RuleSet fields are correct as show below. The other fields can be left as their default
values.
c.
Click Create to create the rule.
d. An unsaved Flow Action rule should display. You will complete the rule later. For now,
just save the rule.
e. Confirm the rules location in the application explorer:
64
Exercise: Generate a Baseline Application Document

Objectives
Use the Application Document Wizard to generate a baseline document
Scenario
Before starting elaboration on the PTO application in earnest, generate an Application Document that
documents the application as it is right after generating the application foundation. Save the settings so
that you can re-use them to generate later documents following the same format.
Password: rules
Tasks
Start the Application Document Wizard
Choose settings appropriate to a business audience
Save your settings
Generate the document
Review the document
How To Do It
1. Start the Application Document Wizard and select the option to print the full application
documentation.
a. Click the Pega button and select Application Actions > Document Application to start
the application document wizard.
65
b. Confirm that PTOFW is selected as the application to document, and Application

Document is selected as the template.
c.
In the options section, change the Detail Level to Full Application Documentation.
d. Scroll down to review other options. By default all options are selected. For each section
you can click the Make Selection button to see the available options, but for this exercise,
dont make any option changes.
2. Review the contents of the documentation.
a. In the Document Table of Contents (Preview) section, open the various sections to
explore will be included in the generated document. Note the work type section in
particular.
3. Save the settings so that you can generate the same document later.
a. Click the Save button.
b. Enter a document name such as PTOFWBaseline and click OK to save.
4. Generate the documentation and then review the generated document.
a. If necessary, close any documents you currently have open in Microsoft Word.
b. Click Document Now. This opens a new document in Word.
c.
You may be prompted to convert the template sections it imports. If so, click OK to select
the default (HTML) for each.
d. When the document generation is complete, review the document.

e. Save the file to your documents folder for later reference.
66
Exercise: Modify and Test Draft Flows

Objectives
Make changes in the flows created by the Application Accelerator
Verify the changes by running the flow in draft mode
Scenario
The Application Accelerator uses the Discovery Map to generate flow rules in draft mode. During
elaboration, business architects work with the system architects to refine these flows as appropriate. In
this exercise you will work with the TimeOffRequest draft flow generated by the AA.
Password: rules
Tasks
Run the TimeOffRequest starter flow in draft mode
Use the Where Am I link to locate the current step in the flow
In the StartTimeOffRequest flow, change the name of the first step to Create PTO Request
Re-run the flow in draft mode to verify that the change is reflected
How To Do It
1. Run the TimeOffRequest starter flow
a. In the Application Explorer, open TimeOffRequest > Process > Flow. Click the
StartTimeOffRequest flow to open it in the work pane on the right.
b. Click the Run button
c.
to run the flow.
Click the Create button in the screen to proceed to the next screen.
2. Click the Where Am I link to locate the current step.

a. Click the Where Am I link.
67
b. Close the window and the click the Submit button to move to the Manager Review step.
c.
Click the Where Am I link to see the current step and the previously completed step.
d. Close the window to return to the request, and then continue clicking the Submit button
until all steps are complete.
3. Return to the StartTimeOffRequest flow and change the name of the first step.
a. Click the StartTimeOffRequest tab.
b. Switch from Discovery Map view to Modeler view.
c.
Double-click the EmployeeRequestsTimeOff assignment to open the Properties panel.

Enter the name CreatePTORequest. Click OK to confirm the change.
d. Save the flow.

e. Run the flow and click Create to create the work item.
f.
Click the Where Am I link to see the updated flow.
68
Exercise: Add a Decision Shape

Objectives
Add a decision shape in a flow
Scenario
LES employees submit a time off request, which gets routed to their manager for approval.
If the manager approves the request and the employee is requesting time off that exceeds their available
days, or the reason specified is Other, then an approval from the HR director is required.
All approved requests should be processed. If either the manager or HR director rejects the request, the
process ends.
In this lesson, you do not need to provide the rule to make the decision; youll add that later. For now,
just add a decision shape to the flow to represent the logic of the scenario.
Password: rules
Tasks
Add a decision shape in the StartTimeOffRequest flow.
Add two connectors coming out of the decision shape: Yes and No
o
Connect the Yes to the HR Review step and
Connect the No to the Process PTO Request step.
How To Do It
1. Add a decision shape in the StartTimeOffRequest flow.
a. Open TimeOffRequest > Process > Flow. Click the StartTimeOffRequest flow to open
it.
b. From the toolbar, click the Add A Flow Shape menu item, then drag a Decision shape
onto the diagram.
69
c.
Click the Decision shape and change the name to RequiresHRReview?
d. Reposition the Manager Reviews connector to flow from the Manager Review
assignment shape to the Requires HR Review decision shape.
2. Connect the decision shape to the outcome steps.

a. Add a new connector from the decision shape to the HR Review assignment shape.
Double click the new connector to open the Properties. In the dialog enter Yes for Name
and change the likelihood to 20.
b. Click OK.
70
c.
Add another connector from the decision shape to the Process PTO Request subprocess shape.
d. Enter No for the connector name and change the likelihood to 80, and click OK.
e. Click the Display Likelihood icon
in the toolbar to enable the likelihoods to display.
3. Save your changes.

4. Run the flow to test the changes.
a. Click the Run icon to run the flow. Click Create, then Submit until you reach the
decision step.
b. Select the Yes connector and click Submit.

c.
The flow progresses to HR Review step.
71
d. Close the work item DO NOT click Submit.

NOTE: Since the HR Review assignment shape is not connected to a next step, if
you click Submit on the HR Review assignment step while running the flow, you will
receive an error. The goal of the exercise up to this point is simply to prove the logic
of the flow. We will address what happens after the HR Review step in the next
exercises.
e. Run the flow again and, when you get to the decision step, select No. Note that this
time the flow progresses to the Update PTO Balance step of the
ProcessPTORequest flow.
f.
Close the work item.
72
Exercise: Working with Flow Actions

Objectives
Identify flow actions for assignments.
Add labels to flow action connectors.
Scenario
When the employee submits their time off request, the request is submitted to their manager for approval.
The manager must be able to either approve or reject the request. If the manager approves the request,
the flow progresses according to the business rules. If the manager rejects the request, the process ends.
If the request requires HR Review, the HR director can either approve or reject the request. If the HR
director approves the request, the PTO Request is processed. If the HR director rejects the request, the
process ends.
Password: rules
Tasks
Add flow action connectors for the Manager Review and HR Review assignment shapes.
How To Do It
1. If necessary, open TimeOffRequest > Process > Flow. Click the StartTimeOffRequest flow to
open it.
2. Change the name of the flow action connector coming from the first step to Submit PTO Request.
a. Double click the connector and enter SubmitPTORequest as the name.
73
3. Add a new connector from the Manager Review assignment shape, which flows to an End shape.
a. Double-click the new connector to open the Connector Properties panel. Enter the name
as ManagerRejects and set the likelihood to 20.
b. Click OK to close the Connector Properties panel.

4. Edit the existing flow action for the Manager Approves action.
a. Double click the other connector, and then in the Connector Properties panel enter
ManagerApproves as the name and enter 80 for the likelihood.
b. ClickOKtoclosetheConnectorPropertieswindow.Your flow should look something like

the following:
74
5. Save your work.

6. Now that you have added connectors for the manager approval and rejection actions, test them
by running the flow.
a. Click the Run button
to run the flow.
b. Click the Create button, and then click Submit to progress to the Manager Review step.
c.
The assignment displays the Manager Approves action since it has a higher likelihood.
Select the Other Actions menu to see the Manager Rejects action.
d. Close the work item window; there is no need to progress the flow any further.
7. Make the same changes for the HR Review assignment by creating or modifying connectors to
represent the HR Approves and HR Rejects actions.
a. Connect the HRReview connector to the Process PTO Request sub-process shape.
b. Open the Properties panel for the connector, and enter HRApproves as the name, and 80
for the likelihood.
c.
Connect the HRRejects connector to the end shape used for the Manager Rejects
action.
75
d. Enter HRRejects as the name, and 20 for the likelihood. Your flow should look something
like the following:
76
Exercise: Set Work Item Status

Objectives
Set the work item status on a flow shape
Scenario
When an employee submits a time off request it must progress through a series of reviews before it is
either approved or rejected. When the time off request is moving between these different review and
processing stages, the work item status must reflect the current stage.
The status must be set to Pending-Approval when its assigned to the manager or HR director for review,
Pending-Fulfillment when it is approved and being processed, Resolved-Completed if the time off request
is approved and processed, and Resolved-Rejected if either the manager or the HR Director rejects the
time off request.
Password: rules
Tasks
Modify the Manager Review and HR Review assignment shapes to set the status of the work item
to PendingApproval
Modify the Process PTO Request sub-process to set the status of the work item to Pending
Fulfillment
Modify the end shapes to set the status of the work item to either ResolvedCompleted or Resolved
Rejected, depending on the outcome of the process.
How To Do It
open it.
2. Set status in the Manager Review step.
a. Double-click the Manager Review assignment shape.
b. On the Status tab, enter PendingApproval for the Work Status.
Remember, you can use the SmartPrompt to ensure you choose the correct work status.
Place your cursor in the Work Status field and press the down arrow on your keyboard to
open the select list.
77
c.
Click OK to close the Assignment Properties window.
d. Notice a status flag appears on the diagram.
3. Update the label and status of the end shapes to change the work status depending on the
outcome of the reviews.
a. Double click on the end shape that is connected by the Manager Rejects and HR Rejects
connectors.
b. Enter Rejected in the name field and enter ResolvedRejected in the Work status field.
c.
Click OK.
78
4. Modify the end shape connected from the Process PTO Request sub-process shape as follows:
Name: Approved; Work Status: ResolvedCompleted.
5. Set the status on the Process PTO Request sub-process shape to PendingFulfillment. When
finished, your diagram should look something like this:
6. Save the flow.

7. Run the process to test your changes.
a. Click Create to create the work item. Notice the Status is set to New.
b. Click Submit. The Status should read as Pending-Approval.
c.
Select the Other Actions option; the Manager Rejects action, then click Submit. The
Status should read as Resolved-Rejected.
79
d. Repeat this procedure to test the other flow paths.
80
Exercise: Route Work

Objectives
Route an assignment to a specific operator
Scenario
When an employee submits a time off request it must be assigned to their manager for review. If the
manger approves the request for time off and it requires HR Director review, the request must be
assigned to the HR Director.
Password: rules
Tasks
Modify the Manager Review assignment shape and change the routing to use the standard
ToOrgUnitManager router. Remember, ToOrgUnitManager automatically routes the work item to
the work list of the manager of the requestors unit or department.
Modify the HR Review assignment shape and change the routing to use the standard ToWorkList
router.
How To Do It
open it.
2. Modify the Manager Review assignment shape to route the time off request to the employees
manager.
a. Double-click the Manager Review assignment shape to open the Assignment Properties.
b. On the Routing tab, enter ToOrgUnitManager in the Router field. Remember, you can
use the SmartPrompt select list.
81
c.
Click OK to close the properties window.
3. Using the same procedure as in step 2, modify the routing information for the HR Review
assignment shape. Use To HR for the Router field entry.
NOTE: Since we dont have an operator ID for the HR Director creating an operator ID is not a
business architect responsibility we lack an operator to whom we can route the assignment.
Since our concern at this point is to identify the points where a work item should be routed, not to
configure the needed operator IDs, we can describe the routing we want and leave the
configuration to a system architect to implement later.
4. Save the flow.
82
Exercise: Create a Screen Flow

Objectives
Create a screen flow
Scenario
An employee completes a time off request form and reviews it before submitting it to their manager. The
employee should be able to go back and forth between the screens before submitting the request.
Password: rules
Tasks
Create a screen flow named CreateTimeOffRequest in the TimeoffRequest work type.
Add assignment shapes named EnterPTORequest and ReviewPTORequest.
How To Do It
1. Create a new screen flow named CreateTimeOffRequest in the TimeoffRequest work type.
a. In the Application Explorer, right click on the TimeOffRequest work type and then select
New > Process, then click Flow.
b. Enter CreateTimeOffRequest in the name field and select ScreenFlow in the Template
field.
83
c.
Click Create. Your diagram should look like this:
d. Save the rule.

2. Modify the flow so it contains two assignment shapes: EnterPTORequest and ReviewPTORequest.
a. Click the existing assignment shape and change the label so it reads EnterPTORequest.
b. Right click on the canvas and select Add, and then click Assignment. This is an alternate
method for adding shapes to the canvas.
c.
Change the label so it reads ReviewPTORequest.
84
d. Add connectors to the assignment shapes as needed. Your flow should look something
like this:
3. Save your work then run the screen flow. You should be able to move back and forth between the
two assignments.
85
86
Exercise: Reference a Screen Flow from Another Flow

Objectives
Reference a screen flow in another flow using a subprocess shape
Scenario
The StartTimeOffRequest starter flow is to be changed to call the CreateTimeOffRequest screen flow.
Password: rules
Tasks
In the StartTimeoffRequest flow, replace the Create PTO Request assignment shape with a
subprocess shape which references the CreateTimeoffRequest screen flow.
How To Do It
open it.
2. Modify the StartTimeOffRequest flow to reference the CreateTimeOffRequest screen flow as a
subprocess.
a. Select the Create PTO Request assignment shape and click the delete icon in the
toolbar. This deletes the assignment and its connector.
b. Right click on the canvass and select Add, then click Subprocess. This adds a
subprocess shape to the canvass.
87
.
c.
Add the necessary connectors to connect the subprocess shape in the process flow.
d. Double click the subprocess shape to open the Subprocess Properties window.
e. Enter CreateTimeOffRequest as the Name, select ScreenFlow in the Filter Flow Rule By
field and select CreateTimeOffRequest as the Flow Rule.
f.
Click OK.
3. Save the rule.

4. Test the new flow design.
a. Run the StartTimeOffRequest flow and verify the CreateTimeOffRequest screen flow is
presented.
88
Exercise: Add Specifications to Flow Shapes

Objectives
Add a specification to the entire flow
Add a specification to the assignment shape
Document the application during workflow elaboration
Reuse saved documentation settings
Scenario
Business Architects create specifications during the elaboration stage to capture business use cases.
These specifications are saved as part of the work type while creating the Application Profile. In the draft
flows, the business architects link these specifications to the flow shapes. This will help the developers to
quickly reference what functionality is required for that particular step.
Password: rules
Tasks
Open the CreateTimeOffRequest and add the specification for the entire flow.
Reference a specification rule on the connector named Manager Rejects in the

StartTimeOffRequest flow.
Document the application.
How To Do It
1. Add a specification rule to the entire flow.
a. Open TimeOffRequest > Process > Flow. Open the CreateTimeOffRequest flow.
b. Click the Specifications tab, then click the Edit button.
89
c.
Select the PTOFWapplication, then the TimeOffRequest work type, and then the
EmployeeRequestForTimeOff specification. Click Save & Close to save the changes.
2. Add a specification rule to a connector.

a. Open the StartTimeOffRequest flow.
b. Double-click the Manager Rejects connector shape.
c.
Select ManagerReview in the Specification field.
d. Click OK.
e. Save the rule.
3. Document the application.
a. Open the documentation wizard by clicking Pega > Application Actions > Document
Application.
b. Select UseSavedSettings.
90
c.
Select PTOFWBaseline or whatever name you entered in the Generate a Baseline

Application Document exercise to reuse your saved settings.
d. Review the completed document in MS Word. Note the content added since you
generated the baseline document.
e. Return to the Designer Studio browser window and click OK in the message window.
Saving the document is optional.
f.
Close the Document an Application tab.
91
92
Exercise: Create a Section and Add Layouts

Objectives
Create a section
Add layouts to a section
Add headers to a layout
Scenario
We use the specifications created in the Application Profile and elaborated on in the flow drafting effort to
make sure the UI meets our requirements. An initial design such as this was presented during a DCO
session:
93
In this exercise, youll create a section for this screen, and include the necessary layouts.
Password: rules
Tasks
Create a section named PTORequest with the necessary layouts used to collect the information for
an employee to request time off.
Add headers to the layouts which will represent the data the layouts contain
How To Do It
1. Create a Section named PTORequest in the TimeOffRequest work type.
New > User Interface, then click Section.
b. Enter PTORequest in the Purpose field, and then click Create.
c.
Save the section.
94
2. Click the Show Wireframes icon in the toolbar; this will make editing the layouts easier.
3. Add a total of four layouts to the section. The order of the four layouts should be single, triple,
double, triple.
a. When you create a section it contains a default double layout. We will keep this layout
and add three more.
b. Click the Layout menu item, and then click the Layout item.
c.
Drag the Layout item onto the canvas above the existing layout; the orange bar indicates
the position of the new layout.
d. Select Single in the Template field, and then click OK.
95
e. Add a triple layout between the single and double layouts using the same procedure.
f.
Your section should look like this.
g. Finally, add a triple layout below the double layout.

4. Your section should look like this:
96
5. Add headers to each of the layouts. The first layout header should read EmployeeInformation, the
second layout header should read CurrentPTOBalance, the third layout header should read PTO
RequestDetails and the last layout header should read NewPTOBalance.
a. Click the top SmartLayout(Single) to select it.
b. Click the Viewproperties icon to open the properties panel.
c.
Select Standard in the Format drop down list.
d. Enter EmployeeInformation in the Title field.
e. Click the X to close the properties panel.
97
6. Add headers to the remaining three layouts named, in order, CurrentPTOBalance, PTORequest
Details, NewPTOBalance using the same procedure.
8. Save your work.
98
Exercise: Add Labels to a Layout

Objectives
Add labels to a layout
Scenario
In the previous exercise, you created the core section required for the Time Off Request flows. It is now
time to add the labels to the layouts in the section, which will be used to identify the data collected in each
of the layouts.
Password: rules
Tasks
Add labels to each of the layouts in the PTORequest section
How To Do It
1. Add labels to the PTORequest section layouts according to the proposed UI design noted in the
exercise scenario.
a. Click in a label cell and enter the appropriate label. In this example, we click in the first
label cell in the Employee Information layout and enter RequestedFor: in the cell.
b. Click in the label cell in the second row and enter EmailAddress:
c.
Leave your cursor in the cell, and then click the Insert a Row After icon in the toolbar.
99
d. Click in the new label cell and enter Isthisarequestforunpaidleave?

e. Your section should look something like this:
2. Repeat this procedure to add labels for the remaining layouts. Refer to the proposed UI design
noted in the exercise scenario for the label text.
Note: If you need to delete a row, click in any cell in the row to select it, then click the Delete
Row button:
3. Save your work.

4. Your section should look something like this:
100
Exercise: Create a Flow Action

Objectives
Create a flow action
Add a section to a flow action
Scenario
Once we have completed the UI sections, it is time to consider how these sections will be used from our
flows. We need to add our new sections to our flows so that we can test and review them in context. We
do this by creating flow actions, which will connect the sections to the appropriate place in a flow.
Password: rules
Tasks
Create a flow action named EnterPTORequest which will be used to connect the PTORequest
section to the Enter PTO Request assignment in the CreateTimeOffRequest screen flow.
How To Do It
1. Create a new flow action named EnterPTORequest in the TimeOffRequest work type.
New > User Interface, then click FlowAction.
b. Enter EnterPTORequest in the Action Name field, and then click Create.
2. Add the PTORequest section to the flow action canvas.
a. Expand the TimeOffRequest work type, then UserInterface > Section.
101
b. Click the handle (the blue dot) of the PTORequest section and drag the section onto the
flow action canvas where the canvas reads < drag section here >. The orange bar will
indicate the section can be added to the flow action canvas.
c.
Save the rule.
3. Your flow action should look something like this:
102
Exercise: Add a Flow Action to a Flow Shape

Objectives
Add a flow action to an assignment shape in a screen flow
Scenario
When creating a draft UI, focus on validating and completing the user interface capabilities needed to
support each major aspect of the flows. At the same time, strive to gain stakeholders understanding and
acceptance of the proposed UI.
Now that you have completed the sections and flow actions, you need to test and review them in
context. Do this by associating the flow actions to the appropriate place in a flow.
Password: rules
Tasks
Add the EnterPTORequest flow action to the Enter PTO Request assignment shape in the
CreateTimeOffRequest screen flow.
How To Do It
1. Open the CreateTimeOffRequest screen flow in the TimeOffRequest work type.
2. Add the EnterPTORequest flow action to the Enter PTO Request assignment.
a. Double click the EnterPTORequest assignment shape to open the Assignment Properties
panel.
b. Enter EnterPTORequest in the Flow Action field. Remember, you can use the
SmartPrompt option by placing your cursor in the field and pressing the down arrow key.
103
c.
Click OK.
3. Save your work.

4. Run the Create Time Off Request process. The PTO Request section should appear as the first
screen.
104
Exercise: Add a Control to a Field

Objectives
Add a control to a field
Scenario
In this exercise, youll add controls to the fields in PTORequest section.
Password: rules
Tasks
Add controls to the fields in the PTORequest section to represent the type of data to be collected
or displayed.
How To Do It
1. Open the PTORequest section.
2. Add a Text Input to those fields where plain text would either be entered or displayed. In this
example, we add a TextInput control to the field for the Requested for: label.
a. Open the Basic control palette and select the Text Input control.
b. Drag the Text Input control into the first field cell of the Employee Information layout.
105
c.
Repeat this procedure to add a Text Input control to the Email address: field.
3. Add TextInput controls to the all of the fields in the Current PTO Balance and New PTO Balance
layouts.
4. Add a TextInput control to the Number of days requested: field in the PTO Request Details
layout.
6. Add a Check Box control to the Is this a request for unpaid leave? field in the Employee
Information layout.
7. Add a Calendar control to the From Date: and To Date: fields in the PTO Request Details layout.
8. Add a Select control to the Reason field in the PTO Request Details layout.
9. Finally, add a Text Area to the Note: field in the PTO Request Details layout.
106
11. Run the CreateTimeOffRequest screen flow to see the updated section.
107
108
Exercise: Make a Field Required

Objectives
Modify a field in a section so it is a required entry
Modify a label cell so it displays the required entry indicator
Scenario
In this exercise, youll modify fields in the PTORequestsection to make them required.
Password: rules
Tasks
Modify the necessary fields in the PTORequest section to make them required entries. Refer to the
proposed UI design to identify the required fields.
Modify the associated label cells to display the default required entry indicator a gold asterisk.
How To Do It
1. Make the Requested for field a required entry field.
a. Open the PTORequest section.
b. Place your cursor in the Requested for field and click the Viewproperties icon.
c.
Switch to the General tab, if necessary.
109
d. Select the Required check box, and then close the Cell Properties panel.
2. Modify the Requested for label to display the default required entry symbol (a gold asterisk).
NOTE: When implementing the user interface, PRPC allows us to associate label cells with the
properties they describe. This supports the use of screen-reading software to provide an
accessible application, and automatically displays the required indicator next to a label when we
mark the corresponding field for required entry. Since we are creating a draft UI and have not yet
implemented our data model, we must manually add the indicator to the label for each field.
a. Select the Requested for label cell, and then click the Viewproperties icon.
b. On the General tab, select the Required check box, and then close the Cell Properties
panel. The label cell will look like this:
110
3. Repeat this procedure for each label / field pair you want to make required. Your section should
look something like this:
111
112
Exercise: Configure a Control

Objectives
Configure a control
Scenario
In this exercise, youll configure a Calendar control so it does not allow text entries.
Password: rules
Tasks
Modify the From Date: and To Date: calendar controls so text entries are not allowed.
How To Do It
1. Select the From Date: field and click the View properties icon.
2. Click the Configure Control icon in the Cell Properties panel.
3. Select the No radio button for Allow Text Entry: option, and then click OK.
113
4. Close the Cell Properties panel.

5. Repeat this procedure for the To Date: Calendar control.
114
Exercise: Reuse a Section

Objectives
Reuse a section in different flow actions
Scenario
The information contained in the PTORequest section you created in the Sections and Layouts exercises
can be used for three other actions: 1) the employees review of their time off request prior to submitting
the request, 2) the Managers review of the time off request and 3) the HR Directors review (if required).
Given the information is the same, you can use the same section for each of these actions. Do this by
creating different flow actions, which reuse the PTORequest section.
Password: rules
Tasks
Create a flow action named ReviewPTORequest, which contains the PTORequest section.
Associate the ReviewPTORequest flow action to the ReviewPTORequest assignment shape in the
CreateTimeOffRequest screen flow.
Create a flow action named ApprovePTORequest, which contains the PTORequest section.
Associate the ApprovePTORequest flow action to the Manager Approves and HR Approves flow
actions in the StartTimeOffRequest process flow.
How To Do It
Note:RefertotheSectionsandLayoutsexercisesifyouneedareminderonhowtoaccomplishthese
keysteps.
1. Create a flow action named ReviewPTORequest in the TimeOffRequest work type.
2. Add the PTORequest section to the flow action.
3. Open the CreateTimeOffRequest screen flow in the TimeOffRequest work type.
4. Add the ReviewPTORequest flow action to the Review PTO Request assignment shape.
5. Create a flow action named ApprovePTORequest in the TimeOffRequest work type.
6. Add the PTORequest section to the flow action.
115
7. Open the StartTimeOffRequest process flow in the TimeOffRequest work type.

8. Add the ApprovePTORequest flow action to the Manager Approves and HR Approves flow
action connectors.
9. Run the StartTimeOffRequest process.
10. Advance through each of the appropriate steps to verify the PTORequest section displays for the
Review PTO Request, Manager Approves and HR Approves actions.
116
Challenge Exercise: Nest a Section in a Section

Objectives
Nest a section in a section
Make a nested section read only
Scenario
Note: Completing this challenge exercise is optional. The techniques covered in this challenge exercise,
while discussed in concept in the lesson, were not demonstrated. However, these techniques are simply
a relatively simply advancement of what you have already learned and will help you create draft UIs
which can be implemented by your System Architects with even fewer modifications than would normally
be required.
In this scenario, we want to reuse the PTORequest section for the ReviewPTORequest and the
ApprovePTORequest flow actions, but have the section display as read only. Do this by creating an
outer section, which contains a layout with a cell marked as Read Only. Then, include (nest) the
PTORequest section in the read only cell.
Password: rules
Tasks
Create a section named ReviewPTORequest with a Free-Form layout, which contains a single cell
marked as Read Only, then nest the PTORequest section in the ReviewPTORequest section.
Modify the ReviewPTORequest flow action so it contains the new ReviewPTORequest section.
Create a section named ApprovePTORequest with a Free-Form layout, which contains a single
cell marked as Read Only, then nest the PTORequest section in the ApprovePTORequest section.
Modify the ApprovePTORequest flow action so it contains the new ApprovePTORequest section.
How To Do It
1. Create a section named ReviewPTORequest in the TimeOffRequest work type.
2. Add a FreeForm layout with 1 column and 1 row and then delete the default double smart layout.
3. Add the PTORequest section to the cell, then edit the Cell Properties and select ReadOnly from
the Edit Options list.
117
4. Delete the PTORequest section reference from the ReviewPTORequest flow action - use the trash
can icon then add the ReviewPTORequest section to this flow action.
5. Run the StartTimeOffRequest flow to verify the Review PTO Request step displays as read only.
6. Use this same procedure to create a section named ApprovePTORequest, which includes the
PTORequest section in a read only cell. Remember to modify the ApprovePTORequest flow action
so it references your new section.
118
Exercise: Create a Single Value Property

Objectives
Create single value properties
Scenario
During the draft UI elaboration effort, we identified the data elements necessary to transact a time off
request. These draft UIs will help with building the data model. Building the data model in PRPC is
typically a shared effort between Business Architects and System Architects.
You are tasked with creating single value properties for the time off request work type, which you will then
use in the PTORequest section you created in an earlier exercise. This exercise purposefully omits
creating properties for the Requested For and Email Address fields in the PTORequest section. You will
work with these in a later exercise.
Password: rules
Tasks
Create the following single value properties for the TimeOffRequest work type:
o
UnpaidLeave
NumberDaysRequested
FromDate
ToDate
Reason
How To Do It
NOTE:AllpropertiescreatedinthisexercisearecreatedintheTimeOffRequestworktype.
1. Create a single-value property named UnpaidLeave, of type TrueFalse.
a. Right-click the TimeOffRequest work type and select New > Data Model, and then click
Property.
119
b. Enter UnpaidLeave in the Property Name field.
c.
Select TrueFalse in the Type field in the Quick Create section.
d. Click Quick Create.
NOTE:QuickCreateisaquickandeasywaytocreateapropertywhenyouonlyneedto
specifythepropertynameandtype.
2. Expand TimeOffRequest > Data Model > Property in the application explorer to view the property.
3. Create a property named NumberDaysRequested, of type Integer, using the same quick create
method as above.
120
4. Create two properties named FromDate and ToDate, both of type Date, using the quick create
method.
5. Create a property named Reason, which uses a PromptSelect control to give the user a list of
valid reasons.
a. Create a new property named Reason, but this time click Create. DO NOT click Quick
Create, as you need to do more than just specify the property name and type.
b. Select PromptSelect in the Control field.

Remember: Use the built-in select list to ensure you select a valid Control. Do this by
entering the first few characters of the control you wish to use in the Control: field, and
then press the down arrow on your keyboard to invoke the select list. Double-click the
PromptSelect control to select it.
In these next few steps, you are going to create a list of local values from which the employee
can select as the reason for their PTO request. Adding a list of local values is an easy way to
enhance the elaboration of a draft UI as actual values or their source may not be
available at this stage of the project development.
c.
Select Local List in the Table Type drop-down list.
121
d. Place your cursor in the first row and enter Bereavement.
e. Click the Add a row icon 4 times to add four more rows.
f.
Enter Parental, Sick, Vacation and Other in each of the rows.
g. Save your work.
122
Exercise: Add a Single Value Property to a Field in a Section

Objectives
Add single value properties to fields in a section
Scenario
Now that the data model is complete it is time to turn your attention to associating the properties to the
fields in the PTORequest section.
Password: rules
Tasks
Associate the time off request properties with the appropriate fields in the PTORequest section.
How To Do It
Remember:YouareskippingtheRequestedForandEmailAddressfieldsfornow.Youwilldealwith
thesetwofieldsinalaterlessonandexercise.
1. Associate the UnpaidLeave property with the appropriate field in the PTORequest section.
a. Expand TimeOffRequest > User Interface > Section in the application explorer, and then
open the PTORequest section.
b. Expand TimeOffRequest > Data Model > Property in the application explorer.
c.
Drag the UnpaidLeave property click on the blue dot next to the property name in the
application explorer - to the appropriate field in the PTORequest section.
123
2. Add the NumberOfDaysRequested, FromDate, ToDate and Reason properties to the appropriate
field using the same procedure as above.
3. Save your work.
4. Run the StartTimeOffRequest process to test the updated PTORequest section.
a. If necessary, open the StartTimeOffRequest process flow in the TimeOffRequest work
type, and then click the Run button.
b. Enter sample data in the PTO Request Details area. Remember, this is the only part of
the section where you associated properties to the fields.
c.
Click Next.
d. The sample data you entered should appear in read-only mode in the next screen.
124
Exercise: Create a Page Property

Objectives
Create a Page property
Scenario
One of the roles of a system architect is to create a reusable and robust data model. This includes
creating data classes to be used as templates for adding Page and Page List properties to work types.
The PTO system architect has created a reusable data class called PTOBalance, which reflects a users
current available time off in each time off category: Vacation, Sick, Paternity, Bereavement and Other.
Your task is to review the LES-FW-PTOFW-Data-PTOBalance data class so you are familiar with the
properties associated with this data class, and then add a Page property based on the PTOBalance data
class to the work type.
Password: rules
Tasks
Review the LES-FW-PTOFW-Data-PTOBalance data class
Create a Page property named AvailablePTO for the TimeOffRequest work type
How To Do It
1. Review the LES-FW-PTOFW-Data-PTOBalance data class
a. Click on LES-FW-PTOFW-Work class, and then click on LES-FW-PTOFW-DataPTOBalance.
b. Expand Data Model > Property.
125
c.
Review the single value properties in the data class.
2. Switch the application explorer back to the LES-FW-PTOFW-Work class group using the same
procedure as above.
3. Create a new property named AvailablePTO in the TimeOffRequest work type.
a. Right click on TimeOffRequest and select New > Data Model and then click Property.
b. Enter AvailablePTO in the Property Name field, and then click Create.
NOTE: Make sure you click Create and not Quick Create
c.
Select Page as the Property Mode
d. Select LES-FW-PTOFW-Data-PTOBalance as the Page Class.

REMEMBER: You can use the SelectPrompt feature. Do this by entering the first few
characters of the class you are searching for in our example, LES - in the Page Class
126
field, and then press the down arrow on your keyboard to invoke the SelectPrompt list
filtered on the characters you entered.
e. Save your work.

4. View the page mode property in the Application Explorer.
127
128
Exercise: Add a Page Property to a Field in a Section

Objectives
Add page properties to fields in a section
Scenario
Systems Architects create the data model and typically add the necessary properties to the class group,
including Page mode properties. Your goal is to provide a more complete draft UI to the business user,
which includes proving as much of the data flow as possible. To accomplish this goal, you have already
created a page-mode property in the class group and now you will associate the page-level properties to
the appropriate fields in the PTORequest section.
Password: rules
Tasks
Associate the AvailablePTO page properties to the appropriate fields in the PTORequest section.
How To Do It
1. Associate the AvailablePTO properties to the appropriate fields in the PTORequest section.
a. Open the PTORequest section
b. Select the Maternity/Paternity field, and then click the View properties icon to open the
Cell Properties panel.
c.
Enter .AvailablePTO.Parental in the Property field.
129
d. Close the Cell Properties panel.

2. Associate the .AvailablePTO.Bereavement property to the field associated with the Bereavement
label using the same procedure as above.
3. Save your work.
4. Run the StartTimeOffRequest process, and then enter values in the Maternity/Paternity and
Bereavement fields to verify the values are visible in the next screen.
NOTE: These property values would typically be automatically populated later in the process,
during the Integration step of the process development roadmap. This effort is a system architect
responsibility and is beyond the scope of this exercise.
130
Exercise: Use an Inherited Property

Objectives
Add an inherited property to a field in a section
Scenario
Your goal is to provide a more complete draft UI to the business user, which includes proving as much of
the data flow as possible. The Note field in the PTORequest section is missing a property reference. You
will take advantage of inherited properties to complete this missing property reference.
Password: rules
Tasks
Add the .pyNote property to the Note field in the PTORequest section
How To Do It
1. Add the PRPC provided property .pyNote to the Note field.
a. Select the Note field, and then click the View properties icon to open the Cell Properties
panel.
b. Enter .pyn in the Property field, and then press the down arrow on your keyboard to open
the property select list.
c.
Double click More.
131
d. Double click pyNote to select it.
e. Save your work.

2. Run the StartTimeOffRequest process, and then enter values in the PTO Request Layout
making sure to enter a value for Note - to verify the values are visible in the next screen.
132
Exercise: Set Initial Property Value Using a Data Transform

Objectives
Edit an existing data transform to set an initial property value
Scenario
The list of values for the .Reason property are defined alphabetically in the property rule. This makes
Bereavement seem to appear as the default reason for a time off request. You have a requirement from
the business users to ensure the default reason is set to Vacation when an employee starts a time off
request.
Password: rules
Tasks
Set the .Reason property to an initial value of Vacation using the pyDefault data transform
How To Do It
1. Edit the pyDefault data transform to set the initial value of .Reason to Vacation.
a. Open the pyDefault data transform located in TimeOffRequest > Data Model > Data
Transform
133
b. Click the Add a row icon.
c.
Enter a . (dot), and then select the Reason property from the select list in the Target
column field.
d. Enter the word Vacation in the Source column field.

NOTE: It is important that you enter this value exactly as specified, including the double
quote characters and capitalizing the word.
e. Save your work.

2. Run the StartTimeOffRequest flow to verify Vacation presents as the default reason.
134
Exercise: Create a When Rule

Objectives
Create a When rule
Scenario
As you continue the elaboration of the PTO requirements, it is time to turn your attention to the rules that
control the flow of the time off request process. Your goal is to define the business rules that determine
when the HR Directors approval is required. According to LES policy, any time off request for a reason
of Other (that is, a request that is not for vacation, sick time, parental or bereavement leave) must be
approved by the HR Director.
The first step is in automating this policy is to define a decision rule. In this case, you need to decide
between two different outcomes: yes (requires HR approval) and no (does not require approval).
Therefore, the most appropriate decision rule type is a When rule.
Password: rules
Tasks
Create a When rule that defines when HR Director approval is required: when the Reason
property of the request is specified as Other.
How To Do It
1. Create a When rule named RequiresHRApproval in the TimeOffRequest work type.
a. Right-click on the TimeOffRequest work type and then select New > Decision, then click
When.
b. Enter RequiresHRApproval in the name field, and then click Create.
NOTE: For When rules with one simple condition, we can enter the condition in the New
Rule dialog and click Quick Create, as we did for properties. In this exercise, click Create
c.
Double-click the statement [Double click to add a condition].
d. Select .Reason in the left field and Other in the right field, and then click OK.
NOTE: Since we defined Reason as a local list with a table of default options, we can
select from a list of those options in the right field of Condition dialog. When using PRPC,
select values from a list, rather than type them, to avoid typos that may lead to errors.
135
e. Click OK.
136
Exercise: Reference a When Rule on Decision Shape Connectors

Objectives
Use a When rule in a flow
Scenario
In the last exercise you defined a RequiresHRApproval When rule to determine if a request for time off
requires the approval of the HR director.
In a previous exercise you added a decision shape to the flow, but did not specify the associated decision
rule.
In this exercise, you need to connect the new RequiresHRApprovalrule to your existing decision shape and
its connectors.
Password: rules
Tasks
Change the type of the decision shape named Requires HR Approval to a Fork in the
StartTimeOffRequest flow
Reference the When rule in the Yes connector emanating from the Requires HR Approval
decision shape
Set the No connector emanating from the Requires HR Approval decision shape to Else
How To Do It
1. Open the StartTimeOffRequest flow in the TimeOffRequst work type.
2. Set the Type of the decision shape named Requires HR Review to Fork.
a. Double-click the Requires HR Approval decision shape to open the Decision Properties
panel.
b.
Select Fork in the Type field, and then click OK.
137
3. Modify the Yes connector emanating from the decision shape so it references the
RequiresHRApproval When rule.
a. Double-click the Yes connector emanating from the decision shape to open the Connector
Properties panel.
b. Select When in the Condition Type field.
c.
Enter RequiresHRApproval in the When field.
138
d. Enter Yes in the Name field, and 20 in the Likelihood field, and then click OK.
4. Modify the No connector emanating from the Requires HR Approval decision shape and set the
Condition Type to Else.
a. Double-click the No connector emanating from the Requires HR Approval decision shape
to open the Connector Properties panel.
b. Select Else in the Condition Type field and enter No in the Name field.
5. Save your work.

6. Run the StartTimeOffRequest process and select Other as the Reason and submit the PTO
request. When you get to the Manager review step, approve the request. The process should
progress to the HR Review step.
139
140
Exercise: Create a Declare Expression

Objectives
Create a Declare Expression to automatically calculate a property value
Scenario
You will create a new property named TotalPTO, whose value is automatically calculated using a declare
expression.
Password: rules
Tasks
Create new property named TotalPTO in the TimeOffRequest work type
Define a Declare Expression on TotalPTO, which is calculated from the total of the Bereavement,
Other, Parental, Sick and Vacation properties
Test the Declare Expression using the Declarative Network display
How To Do It
1. Create a property named TotalPTO of type Integer in the TimeOffRequest work type. Refer to the
Working with Properties Exercises in the Modeling the Data module if you need help.
2. Define a Declare Expression on .TotalPTO which adds the values of .Bereavament, .Other,
.Parental, .Sick and .Vacation
a. Right-click the TotalPTO property and select DefineExpression from the submenu.
b. Click Create in the Declare Expression: New window.
c.
Click Value of [expression] to access the expression builder.
141
d. Click the Search icon to open the Expression Builder window.
e. Enter .AvailablePTO.Bereavement+.AvailablePTO.Other+.AvailablePTO.Parental+
.AvailablePTO.Sick+.AvailablePTO.Vacation in the Expression Builder text area.
f.
Click Save to close the Expression Builder window.
g. Save your work.

3. Test the declare expression using the Declarative Network display.
a. Click the Run icon in the toolbar.
142
b. Click a property name; in this example, Bereavement.
c.
Enter a numeric value in the property field, and then click Update.
d. The TotalPTO property value should update.
e. Add numeric values to the remaining properties, clicking Update after each addition.
143
144
Exercise: Create a Service Level for an Assignment

Objectives
Create a service level rule
Associate a service level rule with an assignment in a flow
Scenario
One of the requirements for PTO is to ensure timely response by managers to time off requests. Ideally,
managers and HR directors should respond to requests within one day, but they must respond within
three days.
Password: rules
Tasks
Create a service level rule which defines a goal of 1 business day and a deadline of 3 business
days. Increase the urgency of the assignment by 10 at goal and by 20 at deadline.
Add the service level rule to the Manager Review and HR review assignments in the flow
Create a new work item to test the service level
How To Do It
1. Create a service level rule named ReviewPTORequest in the TimeOffRequest work type.
a. Right click on the TimeOffRequest work type and then select New > Process, then click
Service Level.
b. Enter ReviewPTORequest in the Service Level field, and then click Create.
2. Set the Goal to 1 day and 10 urgency. Set Deadline to 3 days and 20 urgency. For both values,
check Business Days.
3. Save your work.
145
4. Open the StartTimeOffRequest flow

5. Add the ReviewPTORequest service level to the Manager Review assignment shape.
a. Double click the Manager Review assignment shape to open the Assignment Properties
panel.
b. Enter ReviewPTORequest in the Service Level field.
c.
Click OK to close the properties panel.
6. Add the ReviewPTORequest service level to the HR Review assignment shape using the same
procedure as above.
7. Save your work.
8. Run the flow and submit a new time off request. After submitting to the manager review step,
confirm that the deadline is the one specified in the service level by clicking on the Review link:
A note on testing: to properly test this Service Level, you need to submit a new time off request, and
then view its urgency value right after submission; after 24 hours; and after 3 days. If you wish to test
in a shorter time frame, consider temporarily setting the goal and deadline to 5 and 10 minutes
respectively.
146
Exercise: Add Notifications to a Flow

Objectives
Add a notification to an assignment shape in a flow
Send a notification using a utility shape
Scenario
Most business processes depend on correspondence with application users to establish an
understanding of pending transactions and assignments. Your task in this scenario is to add notification
correspondence to the time off request flow.
Managers and HR Directors may not work continuously in the PTO Request application, so they need to
be notified when a time off request is ready for their review.
The application requirements also include notifying employees if their request is rejected.
Your task is to add these notifications to the flow. In a later exercise, you will add the templates for the
correspondence to be sent and test.
Password: rules
Tasks
Add a notification to the Manager Review and HR Review assignment shapes in the
StartTimeOffRequest flow
Add a utility shape named NotifyEmployeeofRejection to the StartTimeOffRequest flow, which

serves as a placeholder for notifying the employee if the manager rejects their time off request
How To Do It
1. Add a notification to the Manager Review assignment shapes.
a. Open the StartTimeOffRequest flow in the TimeOffRequest work type.
b. Double-click the Manager Review assignment to open the Assignment Properties panel.
c.
On the Notification tab, enter NotifyManager in the Notify field.
147
d. Click OK.
NOTE: Since the flow is in draft mode, we dont need to enter a valid notification activity
at this time. By entering Notify Manager, we can identify the assignment as one from
which a notification should be sent, and we or a system architect can select the best
option to implement the notification at a later time.
2. Modify the HR Review assignment shape using the same procedure as above. However, enter
NotifyHRDirector in the Notify field.
3. Add a utility shape named NotifyEmployeeofRejection to the StartTimeOffRequest flow.
a. Add a Utility shape to the flow and place it between the Manger Rejects flow action and
the End shape.
b. Double click the utility shape to open the Utility Properties panel
c.
Enter NotifyEmployeeofRejection in the Name field.
d. Click OK. Your flow should appear similar to the following:
148
Exercise: Create a Correspondence Template

Objectives
Create an email correspondence template
Add a correspondence template to an assignment shape
Scenario
In the previous exercises, you identified the steps in the time off request process that require a notification
of a pending assignment. Now you need to create the email correspondence template that will be used to
send the notification to the assignee and add that correspondence to the assignment.
Password: rules
Tasks
Create an email type correspondence template that includes the name of the employee
requesting time off, and notifies the manager and HR director that the request awaits their review
Add the new template to the Manager Review and HR Review assignment shapes
Test the notification by viewing the audit trail and attachments
How To Do It
1. Create an email correspondence template named PTOReview in the TimeOffRequest work type.
a. Right-click on the TimeOffRequest work type and then select New > Process, then click
Correspondence.
b. Enter PTOReview in the Correspondence Name field, enter Email as the Correspondence
Type, and then click Create.
149
c.
In the text field, enter APTOrequestfromispendingyourreview. Leave three spaces

between the words from and is.
d. Place your cursor between the words from and is, and then select the Addaproperty icon
in the toolbar.
e. Enter .pxCreateOperator in the Name field, and then click Save.
f.
Save your work.
2. Add the PTOReview email correspondence to the Manager Review assignment shape as a
notification.
a. Open the StartTimeOffRequest flow.
150
b. Double-click the ManagerReview assignment shape to open the Assignment Properties

panel.
c.
Click the Notification tab.
d. Enter NotifyAssignee in the Notify field.

e. Enter PTOReview in the CorrName field.
f.
Enter PTOrequestforyourreview in the Subject field.
g. Click OK.
h. Save your work.
3. Test the notification
a. Run the StartTimeOffRequest process and progress to the Manager Review step.
b. Click the Audit link to view the audit trail.
c.
Confirm that the correspondence has been added to the audit trail:
151
d. Expand the Attachments layout to view the email.
4. Add and test the email correspondence to the HR Review assignment using the same procedure
as above.
152
Exercise: Modify a Standard Report Using the Report Browser

Objectives
Create a report category for organizing reports in the report browser
Modify a standard report using the report browser
Scenario
The HR Director wants to be able to view a report of all time off requests submitted, regardless of status.
You can modify the List of processes entered by operator standard report so it shows a list of processes
entered by all operators.
Password: rules
Tasks
Create a personal report category named PTO Requests to organize your customized report
Modify the List of processes entered by operator standard report to remove the Create
Operator filter and add the Create Operator Name as a column
Summarize the report by Create Operator Name and Status
How To Do It
1. Create a new personal report category named PTO Requests using the Report Browser
a. Click the Pega button, and then select Reporting > Report Access and then click Report
Browser.
153
b. Click the New Category link.
c.
Enter PTORequests in the Category Name field, PTO Requests in the Category
Description field, select Personal from the Category Type list, and then click OK.
2. Customize the List of processes entered by operator report by removing the Create Operator
filter and adding the Create Operator Name field as a column in the report.
a. Click the List of processes entered by operator report to open it in the report browser.
b. Click the Edit Report icon in the toolbar.
154
c.
Remove the Create Operator = becky@les.com filter.
d. Click and drag the Create Operator Name property from the left panel onto the report.
3. Sort the custom report by Create Operator Name and Status.

a. Right-click on the Create Operator Name column and select Summarize this column
from the sub-menu.
b. Select the Status check box, and then click OK.
155
4. Change the report title to PTO requests grouped by employee.

a. Click the Edit Report icon in the tool bar.
b. Change the report title to PTO requests grouped by employee, and then click OK.
5. Save the customized report.

a. Click the Exit and Run Report icon in the toolbar.
b. Click the Save As icon in the toolbar.
156
c.
Enter PTORequests in the Report Name field, select PTO Requests in the Report
Category list, and then click OK.
6. Close the report viewer. Your report is now available in the PTO Requests personal reports
category.
157
158
Exercise: Create a List Report using the Report Definition

Objectives
Use a Report Definition rule to create a list-type report
Scenario
The HR Director wants to be able to view a report of all time off requests submitted within the last 7 days.
The report should list all PTO requests submitted in the last seven days by employee and include the
PTO request reason and date the request was entered.
Password: rules
Tasks
Create a list-type report that lists all PTO requests submitted within the last seven days using a
Report Definition rule. Include the employees name, the PTO request reason and the date the
request was submitted.
Note: This report requires us to specify an unoptimized property Reason as a source of data for one
of the columns. Since unoptimized properties are not available in the Report Editor, we need to create
this report by using the report definition rule form, rather than the Report Editor. Optimizing properties that
comprise the data model of an application is a system architect responsibility.
How To Do It
1. Create a new report definition named PTORequestsLastSevenDays in the TimeOffRequest
work type.
a. Right click on the TimeOffRequest work type and select New > Reports, and then click
ReportDefinition.
b. Enter PTORequestsLastSevenDays in the Report name field.
c.
Click Create.
2. Add .pxCreateOperator, .pxCreateDateTime and .Reason as columns

a. Enter .pxCreateOperator in the first Column Name field and change the Column Heading
to read SubmittedBy.
159
b. Click the Add a column icon and enter .pxCreateDateTime in the Column Name field, and
then change the Column Heading to read SubmittedOn.
c.
Add another column and enter .Reason in the Column Name field.
3. Filter the report by including only those PTO requests submitted in the last 7 days.
a. Enter .pxCreateDateTime in the Column field in the Rows to Include section.
b. Click the SelectValues icon and select Last 7 Days from the list, and then click OK.
4. Save your work.
160
5. Run the report to see a list of all PTO requests submitted within the last 7 days.
6. Add a Sort Order of Highest to Lowest on the .pxCreateDateTime columns.
7. Save your work and run the report again.

Note: Normally, we would add a report to the Report Browser once we complete its definition. Doing so
allows other users to run the report, and use it as a starting point for their own reports. Since this report
uses an unexposed property Reason this would allow users to run a report that can negatively impact
system performance, and create their own copies of the report. When adding a report to the Report
Browser, first verify that all of the properties especially those used in filter conditions are optimized.
161
162
Exercise: Document the Application Using the Document

Application Wizard
Objectives
Use the Application Document Wizard to document a completed application
Scenario
The Documentation of an application is critical throughout the development life cycle, but especially so at
the end of the project.
Password: rules
Tasks
Use the Document Application wizard to produce a final Application Document
Review the final Application Document
How To Do It
1. Create a final Application Document
a. Click the Pega button, select Application Actions, and then click DocumentApplication.
b. Select FullApplicationDocumentation in the Detail Level field in the Options section.
c.
Click DocumentNow.
d. When the document is completed, click File > Save As in Microsoft Word to save the
document to your local system. Use a meaningful name such as PTOApplication.
e. Close Microsoft Word.
f.
In Internet Explorer, click OK in the message dialog box.
163
g. Click Save.
h. Enter the same meaningful name such as PTOApplication in the Name field and then
click OK in the Save Document Wizard dialog box.
i.
Close the Document Application wizard.
164

BAE Exercise Guide

Загружено:

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

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

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

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

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

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

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

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

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

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

BAE Exercise Guide

Загружено:

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

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

Working with

Make a Field Required ....................................................................................................................... 109

Exercise: Getting Started with BAE

Be familiar with the structure of course exercises

Access the course exercise system

View related content on the Pega Developer Network

Role: Business Architect

User Name: becky@les.com

d. Enter user ID becky@les.com and password rules.

e. Confirm that the PRPC Business Analyst portal appears.

2. Log out of PRPC

Exercise: Explore the Business Analyst Portal

Log in to the BA portal

Navigate the BA portal

Use context-sensitive and general help

Search for rules

Role: Business Architect

User Name: becky@les.com

Note the selected tab in the work space.

2. What is Beckys position title?

b. Note the position field in Beckys profile.

3. What is the first tab on the Application Document landing page?

b. Note the tab names.

4. What applications does Becky have access to?

b. Click to open the BillingAddress section.

Note the first button on the Layout tab.

7. What does that button do?

In the help window, select information on the Layout tab.

d. Open the topic Identifying controls on this tab

e. Read the paragraph that explains the Show Wireframes button.

Locate the list of navigation controls.

d. Alternative: use the Search function instead of the table of contents.

b. If necessary, log in using your PDN/Pega Academy sign in.

e. Select the first starred article

Exercise: Explore the PurchaseFW Application

Be familiar with the user experience of the PurchaseFW application

Use context-sensitive and general help

Role: Request Originator

User Name: wally@les.com

User Name: manuel@les.com

Role: Fulfillment Worker

User Name: frank@les.com

User Name: polly@les.com

2. Log in as the manager. Approve the purchase request.

2. As Manuel the manager, approve the purchase request.

Optional: Click the Where Am I link (

d. Optional: Click the Audit link (

e. Click the Submit button.

4. As Frank, complete the Inventory Request

Close the work item tabs and take a lunch break.

h. Franks work on this item is complete. Log out.

Double click on the purchase request work item on the list.

e. Click Confirm to complete the assignment.

Close the work item tab.

g. Click the Refresh button (

) on your work list tab and note that the purchase

Exercise: Read the LES Time Off Application Mandate

Exercise: Read the LES Time Off Application Documents

Exercise: Review the Purchase FW Application Profile

Open an existing Application Profile

Navigate through an existing Application Profile in the Application Profiler tool

Access the Application Profiler help

Role: Business Architect

User Name: becky@les.com