ft61v1 student guide%282%29

Fast Track to

PegaRULES Process Commander® V6.1 – Student Guide

© Copyright 2010 Pegasystems Inc., Cambridge, MA

All rights reserved.

This document describes products and services of Pegasystems Inc. It may contain trade secrets and proprietary information. The document and product are protected by copyright and distributed under licenses restricting their use, copying, distribution, or transmittal in any form without prior written authorization of Pegasystems Inc.

This document is current as of the date of publication only. Changes in the document may be made from time to time at the discretion of Pegasystems. This document remains the property of Pegasystems and must be returned to it upon request. This document does not imply any commitment to offer or deliver the products or services provided.

This document may include references to Pegasystems product features that have not been licensed by your company. If you have questions about whether a particular capability is included in your installation, please consult your Pegasystems service consultant.

For Pegasystems trademarks and registered trademarks, all rights are reserved. Other brand or product names are trademarks of their respective holders.

Although Pegasystems Inc. strives for accuracy in its publications, any publication may contain inaccuracies or typographical errors. This document or Help System could contain technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Pegasystems Inc. may make improvements and/or changes in the information described herein at any time. This document is the property of: Pegasystems Inc. 101 Main Street Cambridge, MA 02142-1590 Phone: (617) 374-9600 Fax: (617) 374-9620 www.pega.com Course Name: Fast Track to PegaRULES Process Commander® V6.1 SP1-- Student Guide Updated: 16-Jul-10 Course ID: FT61V1

Contents Introduction: Fast Track and this Student Guide ........................................................................................................... 1

Audience .................................................................................................................................................................... 1 Course Prerequisites ................................................................................................................................................ 1 Course Objectives ..................................................................................................................................................... 1 How to Use This Student Guide............................................................................................................................... 1 User IDs and Passwords .......................................................................................................................................... 3

Module 1: Introduction to PRPC ............................................................................................................................... 1-1

Module 2: Introduction to User Portals ................................................................................................................... 2-1 Exercise 2-1: Create a Purchase Request ..................................................................................................... 2-13 Exercise 2-2: Process a Purchase Request .................................................................................................. 2-20

Module 3: Introduction to Designer Studio ............................................................................................................. 3-1

Module 4: Introduction to Fields and Data Elements ............................................................................................. 4-1 Exercise 4-1: Create a New Property ............................................................................................................... 4-5

Module 5: Introduction to UI and Form Design ...................................................................................................... 5-1 Exercise 5-1: Add a Property to a Section ...................................................................................................... 5-6

Module 6: Introduction to Process Definition ......................................................................................................... 6-1 Exercise 6-1: Add Existing Decision Table to a Process ............................................................................. 6-11

Module 7: Introduction to Business Rules .............................................................................................................. 7-1 Exercise 7-1: Edit a Decision Table .................................................................................................................. 7-7

Module 8: Introduction to the PDN and Developer Help ........................................................................................ 8-1 Exercise 8-1: Open Process Commander Developer Help ............................................................................ 8-7

Module 9: Direct Capture of Objectives................................................................................................................... 9-1 Exercise 9-1: Run the Application Profile Wizard ......................................................................................... 9-13 Exercise 9-2: Create an Application Using the Application Accelerator .................................................... 9-26 Exercise 9-3: View the Application Overview ............................................................................................... 9-34 Exercise 9-4: Run a Process Created by the Application Accelerator ....................................................... 9-36

Module 10: Class Structure and RuleSets .............................................................................................................. 10-1 Exercise 10-1: Review the Class Structure Generated by the Application Accelerator ............................. 10-9 Exercise 10-2: Review Inheritance in an Application ................................................................................... 10-13 Exercise 10-3: Review the Rules Created by the Application Accelerator ................................................ 10-16 Exercise 10-4: Create Classes ........................................................................................................................ 10-21

ii Fast Track Exercise Guide

Module 11: Creating a Data Model ........................................................................................................................... 11-1

Exercise 11-1: Create a Property Using the New Rule Dialog ....................................................................... 11-5 Exercise 11-2: Change the Appearance of a Property ................................................................................... 11-6 Exercise 11-3: Create Properties Using the Define Property Wizard ......................................................... 11-15 Exercise 11-4: Create Embedded Properties ................................................................................................ 11-17 Exercise 11-5: Create a Data Table ................................................................................................................ 11-25 Exercise 11-6: Set Initial Values Using a Model Rule ................................................................................... 11-32 Exercise 11-7: Disable Check-in/Check-out Functionality ........................................................................... 11-35

Module 12: Process Definition ................................................................................................................................. 12-1 Exercise 12-1: Create a Subflow ..................................................................................................................... 12-11 Exercise 12-2: Create a Tabbed Screen Flow ............................................................................................... 12-14 Exercise 12-3: Call a Subflow from a Starter Flow ....................................................................................... 12-19

Module 13: User Interface ......................................................................................................................................... 13-1 Exercise 13-1: Create a Section ...................................................................................................................... 13-13 Exercise 13-2: Create a Section Containing Multiple Layouts .................................................................... 13-16 Exercise 13-3: Adding a Section to a Flow Action ....................................................................................... 13-21 Exercise 13-4: Create a Repeating Grid Layout ............................................................................................ 13-26 Exercise 13-5: Use the HTML Rules Inspector to Review your UI .............................................................. 13-30

Module 14: Clipboard ................................................................................................................................................ 14-1 Exercise 14-1: Review a Process Using the Clipboard .................................................................................. 14-5

Module 15: Decision Rules ....................................................................................................................................... 15-1 Exercise 15-1: Create a Decision Table to Route Work Items ....................................................................... 15-6 Exercise 15-2: Create a Decision Table to Automatically Approve or Reject Work Items ....................... 15-12 Exercise 15-3: Use a Decision Tree to Determine a Property Value ........................................................... 15-19 Exercise 15-4: Create a When Rule to Control Display of a Layout ........................................................... 15-28 Exercise 15-5: Direct a Process Using a When Rule .................................................................................... 15-30

Module 16: Activities ................................................................................................................................................. 16-1 Exercise 16-1: Add a Utility to a Process to Execute an Activity .................................................................. 16-4 Exercise 16-2: Create an Activity to Set a Property ..................................................................................... 16-14 Exercise 16-3: Create a Parameterized Activity ............................................................................................ 16-17 Exercise 16-4: Create an Activity to call another Rule Type ....................................................................... 16-20

Module 17: RuleSets and Rule Resolution .............................................................................................................. 17-1 Exercise 17-1: View Operator Profile ............................................................................................................. 17-11

Module 18: Validation ................................................................................................................................................ 18-1 Exercise 18-1: Validation ................................................................................................................................... 18-4

Contents iii

Exercise 18-2: Validate Credit Scores .............................................................................................................. 18-9 Exercise 18-3: Validate Assets and Liabilities .............................................................................................. 18-14

Module 19: Declarative Rules ................................................................................................................................... 19-1 Exercise 19-1: Calculate a Value Using a Declare Expression...................................................................... 19-7 Exercise 19-2: Create a Declare Expression to Sum Items in a List ........................................................... 19-10 Exercise 19-3: Use a Declare Expression to Evaluate a Decision Tree ...................................................... 19-13 Exercise 19-4: Create a Constraint to Enforce Valid Data Entry ................................................................. 19-16

Module 20: Advanced UI ........................................................................................................................................... 20-1 Exercise 20-1: Conditionally Display a Layout Using a When Rule ............................................................. 20-5 Exercise 20-2: Conditionally Display Property Fields .................................................................................... 20-7 Exercise 20-3: Create a Smart Label .............................................................................................................. 20-16 Exercise 20-4: Create a Dynamic Select Control .......................................................................................... 20-19

Module 21: Advanced Activities ............................................................................................................................... 21-1 Exercise 21-1: Create an Activity with a Precondition and a Transition ...................................................... 21-4 Exercise 21-2: Create an Activity to Populate a Dynamic Select ................................................................ 21-14 Exercise 21-3: Create an Activity to Write to a Data Table .......................................................................... 21-17

Module 22: Routing and SLA .................................................................................................................................... 22-1 Exercise 22-1: Create a Work Basket for Loan Approvals ........................................................................... 22-10 Exercise 22-2: Route Loan applications to a Workbasket ........................................................................... 22-12 Exercise 22-3: Create a Service Level to Enforce Deadline on Approvals ................................................ 22-16

Module 23: Development Performance Tools ......................................................................................................... 23-1 Exercise 23-1: Run Preflight and View Warnings ........................................................................................... 23-5

Module 24: Documenting the Application ............................................................................................................... 24-1 Exercise 24-1: Run the Application Documentation Wizard .......................................................................... 24-5 Exercise 24-2: Export an Application ............................................................................................................... 24-9

Module 25: Wrap Up .................................................................................................................................................. 25-1

Appendix A: Exercise Solutions ................................................................................................................................... A-1 Exercise 11-4: Create Embedded Properties .................................................................................................... A-1 Exercise 11-5: Create a Data Table .................................................................................................................... A-5 Exercise 15-2: Create a Decision Table to Automatically Approve or Reject Work .................................... A-12 Exercise 15-3: Use Decision Trees to Define Variables Used in Calculations ............................................ A-17 Exercise 18-3: Validate Assets and Liabilities ................................................................................................ A-23 Exercise 20-2: Conditionally Display Property Fields .................................................................................... A-25

iv Fast Track Exercise Guide

Appendix B: Optional Exercises ................................................................................................................................... B-1

Exercise B-1: Index Embedded Properties ...................................................................................................... B-1 Exercise B-2: Add a Spinoff to a Flow .............................................................................................................. B-2 Exercise B-3: Audit Changes to a Field............................................................................................................ B-3 Exercise B-4: Circumstance a Decision Table ................................................................................................ B-4 Exercise B-5: Customize the Appearance of an Application with the Branding Wizard ............................. B-6 Exercise B-6: Create a Cascading Dynamic Select Control ........................................................................... B-7 Exercise B-7: Create a Declare Page to Cache External Data........................................................................ B-8 Exercise B-8: Create an SLA for a Flow ......................................................................................................... B-10

Appendix C Auto Loan Application ............................................................................................................................. C-1 Exercise C-1: Create Properties and Set the Model Rule ............................................................................... C-1 Exercise C-2: Create the Auto Loan Flows ...................................................................................................... C-3 Exercise C-3: Create User Interface Rules ....................................................................................................... C-7 Exercise C-4: Create Decision Rules ................................................................................................................ C-8 Exercise C-5: Create a Constraint to Enforce Valid Data Entry ................................................................... C-11 Exercise C-6: Create a Declare Page to Cache External Data...................................................................... C-13 Exercise C-7: Use a Declare Page to Populate an Auto complete Control ................................................. C-15

Introduction: Fast Track and this Student Guide

Audience The Fast Track to PegaRULES Process Commander course is designed for Architects and Designers who: Need to develop multi-process applications with PegaRULES Process Commander (PRPC) Are interested in reusability

Course Prerequisites None; however, helpful experience includes: Application development Knowledge of your company’s business practices and policies Familiarity with one or more project methodologies

Course Objectives Capture executable business requirements by defining:

o Use Cases o Business rules o The user interface o Business processes

Capture initial requirements using the Application Profile wizard, create an Application Profile, and capture additional requirements directly in the system

Change the application (user interface, business rules, processes, and define simple properties)

How to Use This Student Guide The modules in this guide have been developed for you to use during your training and then later as a reference guide. Each module contains information on a particular feature of PRPC. Some modules include exercises to reinforce the concepts taught in the module. Exercises are structured to include the following sections:

Always

Scenario — describes the business problem, task, or situation the exercise addresses.

Requirements — describes the objective of the exercise and specifies the business tasks that must be performed to complete the exercise.

How to Do It — describes a series of steps or instructions that are designed to help you understand how to complete these required exercise. In the beginning of the course, and when performing the task for the first time, detailed instructions will be provided. As the course progresses, or when a task has been covered in detail earlier, only brief, high-level instructions will be provided. You should reference earlier modules or cited PDN articles as needed.

Pegasystems Inc. Fast Track to PRPC 1


Exercise Summary — provides a review of what you completed during the exercises, why it was required, and how it fits into the overall solution or scenario.

As Needed

Solution Tip — is an optional section that provides suggestions or hints to help you implement your solution according to best practice or using the most efficient approach.

Reference Material — provides information, such as a Developer Help topic or module covered previously, which may be useful when developing a solution for a particular task.

Best Practices — states the best practice the developer should follow when developing solutions.

Taking It Further (Optional Exercises) — are optional exercises that may be included in a module, after the required exercise(s). These exercises do not include step-by-step instructions. They intentionally provide only high-level guidance because in order to complete these exercises you must use various resources. The resources you will need to reference include information on the Pega Developer Network (PDN). Copies of the referenced PDN articles have been provided in the Fast Track Files folder, located on the desktop of the training image.

Appendices

Appendix A: Exercise Solutions — describes or shows the correct outcome of the required exercise. In cases where detailed exercise instructions are provided, an exercise solution may not be provided, since it would be redundant. When an exercise provides only high-level instructions, an exercise solution for the exercise will be included in Appendix A.

Appendix B: Taking It Further — are exercises designed to extend the functionality of the two processes that you will create during the class, home equity and mortgage processes (note that the two processes will work properly even if you do not complete these optional exercises). Note that in some cases, you may have to reach a specific point in the development of your home equity or mortgage processes before you begin the Taking It Further exercise. Solutions for these exercises appear in the Appendix B.

Appendix C: Auto Loan Application — are optional exercises that may be included in a module, after the required exercise(s). The purpose of these exercises is to provide additional practice opportunities as you create and modify a third work type, auto loan. This exercise may be completed after you have successfully completed the required exercises and Taking It Further exercises for that module. Solutions for these exercises appear in the Appendix C.

2 Fast Track to PRPC Pegasystems Inc.


Pegasystems Inc. Fast Track to PRPC 3

User IDs and Passwords To complete the exercises you often play different roles. To do this, you log onto the system as a number of different users so that you can perform the tasks associated with each role. Below is the list of roles, user IDs, and passwords.

Role Operator ID Password

User (Purchase Request) User password

Manager (Purchase Request) Manager password

Designer (Purchase Request) Designer password

Architect (Loan Application) [email protected] password

Pegasystems Inc. Fast Track to PRPC 1-1

Module 1: Introduction to PRPC


1-2 Fast Track to PRPC Pegasystems Inc.


Student Notes:



Module 2: Introduction to User Portals



Exercise 2-1: Create a Purchase Request

Scenario: Your company has a purchase request application that employees use to create a purchase request for job-related hardware, such as laptops, monitors, and printers. Employees enter the items they wish to order, select vendor information, and provide billing and/or shipping information. The employee then submits this request to a manager who reviews it for approval. You’ve been experiencing problems with your laptop. The IT department has instructed you to order a new one using the purchase request application.

Requirements: As part of this process, you: • Log in to Process Commander using the User operator ID. • Create a purchase request for a new laptop. • Close the Vendor Information form. • Open the purchase request from your worklist, complete the

Vendor Information and Shipping/Billing Information forms. • Submit the completed purchase request to your manager.

How To Do It:

1. Open Internet Explorer and log in to Process Commander as the user User, using the password password.

2. Create a new Purchase Request.

Step Description

2.1 Click on the New drop-down list and select Purchase Request.

This opens the Purchase Request work form.



2.2 Enter your name in the Requested For field. This will identify you as the user who created the purchase request.

2.3 Select any option in the Bill To Department pull-down list and in the GL Account pull-down list.

2.4 Change the Order Date and Needed by Date from the default by clicking the Calendar icon to open a calendar. Select your desired dates.

2.5 Select an item from the Item Name pull-down list and enter a quantity.



2.6 Optionally, enter a note for this purchase request.

3. Click Create. This creates the purchase request and opens the Add Vendor Information form. The system automatically assigns a work item identifier (ID number) to your purchase request. The ID appears in the header of the form.

4. Click the Close icon to close the form. The purchase request (work item) appears in a worklist of items assigned to you.

5. Edit the Add Vendor Information form.

Step Description

5.1 Click anywhere on the purchase request in your worklist to open the Add Vendor Information form.

5.2 In the Vendor Category field, select either US Vendors or Non-US Vendors.



5.3 In the Vendor Name field, select a vendor. The system automatically fills in the address fields.

5.4 Click Submit. The Enter Shipping/Billing Information form appears. By default, this form is populated with a shipping address. The billing address defaults to the specified shipping address. Users can clear the Same as Shipping Address checkbox if they want to supply a different billing address.



5.5 On the Enter Shipping/Billing Information form, click Submit. This opens the Confirm Request form.



6. Determine the current status of your work item.

Step Description

6.1 On the Confirm Request form, click the Where Am I? icon to display the process diagram in a new window.

6.2 The gold arrow indicates where the work item currently is in the process. When you have finished reviewing the process diagram, close this window.

7. Notice that the Take Action pull-down box defaults to Confirm Request. Click Submit. A confirmation form appears.



8. Click the History icon to review the details of every step taken by the Purchase Request application to process the purchase request.

Note: This application is configured to update the History report, or audit trail, when the Order Total and Include in Forecast fields are updated – note the third and fourth entries in the list shown above.

9. Click the Close icon to return to your worklist. Your purchase request has been assigned to a manager and routed to their worklist, so it is no longer on your worklist.

10. Click the Log Off link in the top right corner of the portal to log out of Process Commander.



Exercise 2-2: Process a Purchase Request

Scenario: As a manager, it is your responsibility to review and then approve or reject the purchase requests that have been submitted by users.

Requirements: As part of this process, you: Log in to the Process Commander using the Manager operator ID. Open the purchase request that appears in your worklist. Click Approve on the purchase request work form.

How To Do It:

1. Log in to Process Commander as the user Manager, using the password password. The Manager portal appears.

2. Click the Process Work bar in the Navigation panel to display your worklist. The purchase request you entered in Exercise 2-1, acting as a User, appears as a work item in the worklist on the right side of your portal.

3. Click the purchase request once to open it.



4. Click the Where Am I? icon to locate where the purchase request is in the process.

5. Click Approve to resolve this work item. A confirmation message, similar to the following example, appears and the work item is removed from your worklist. You can confirm this by clicking the Process Work bar in the navigation panel.

6. Log out of Process Commander.

Do not proceed until the instructor is ready to review the exercise solution(s).


Exercise Summary:

This exercise demonstrates that Process Commander presents a different portal for different set of users.

In Exercise 2-1, you logged in to a Process Commander User portal, learned how to create a new work item, and process the work item as a user. Specifically, you created a new purchase request, providing information about yourself (the requestor), the desired item name and the item quantity. You saw the system assign a unique ID number to your newly created work item. You verified that the purchase request item that you just created was in your worklist with a status of Open. You provided the necessary information in the Add Vendor Information and the Enter Shipping/Billing Information forms and then submitted these forms. You selected the Where Am I? icon to view where your work item currently is in the process. You clicked Submit on the Confirm Request form to confirm the request, and then used the View History icon to view the details of each step the work item has taken to this point.

In Exercise 2-2, you logged in to a Process Commander Manager portal and clicked Approve to process the purchase request created in the previous exercise.



Student Notes:



Module 3: Introduction to Designer Studio


Student Notes:



Module 4: Introduction to Fields and Data Elements



Exercise 4-1: Create a New Property

Scenario: A new policy dictates that any purchase request that is made on behalf of an external customer project must be identified. Your manager has asked you to create a new property, named CustomerCode, to store this information.

Requirements: As part of this process, you: • Create a new property

How To Do It:

1. Create a property named Customer Code.

Step Description

1.1 Log in to Process Commander as the user Designer, using the password password.

1.2 In the Application Explorer, under OrderEntry, expand Data Model.

1.3 Right-click Property and select New.



1.4 In the New Rule dialog, create a new text property named Customer Code and click Quick Create.

1.5 Confirm that the new property (CustomerCode) appears in the Application Explorer.

1.6 In the Application Explorer, click the CustomerCode property name to review the property rule form.



Note: Rule names in Process Commander cannot contain spaces. If you attempt to create a name with a space, Process Commander removes the space from the rule name, but retains the space in the short description. It is always a good practice to create a property with spaces so that the short description looks meaningful. It is also a best practice to click the History tab and enter Full Description and Usage to provide more details on the property and its usage.




Exercise Summary:

In exercise 4-1, you created a new property, named CustomerCode, which will be used to identify any purchase requests that are made for a customer project. You will add this property to a field on the Purchase Request work item form in the next exercise.


Student Notes:



Module 5: Introduction to UI and Form Design



Exercise 5-1: Add a Property to a Section

Scenario: Allow users who are creating a new purchase request item to associate a customer project with the purchase request.

Requirements: As part of this process, you: • Add the customer code property you created in the previous

exercise to a field on the Enter a Purchase Request form. When a user completes this form they can specify the customer’s code in this field to associate the customer project with the purchase request.

How To Do It:

1. Open the GeneralInfo section and add the CustomerCode property.

Step Description

1.1 From the Application Explorer, under OrderEntry, expand User Interface.

1.2 Expand Section. Click the GeneralInfo section.



1.3 The GeneralInfo section form appears in the workspace.

1.4 Add a new row to the section by clicking anywhere in the bottom row of the grid. Click the Insert Row After icon. A new row is appended to the bottom of the grid.

1.5 Find the CustomerCode property in the Application Explorer.

1.6 Click the blue dot next to the CustomerCode property name and drag the property into the second column (field column) of the newly inserted row. Notice that the property name is added to the label column to the left of the actual field.



1.7 Save the section rule.

1.8 Select the Run button in the Quick Launch toolbar. Select Run Process > Purchase Request. This will display the Enter a Purchase Request form. Notice the updated user interface in the Enter a Purchase Request form.

Note: When dragging a property into a field cell, the property’s Short Description is applied to the Label field.




Exercise Summary:

In Exercise 5-1, you took a new property, CustomerCode, and added it as a field on a work item form, in this case the Enter a Purchase Request form. When a user completes this form at runtime, they can specify the customer’s code in order to associate the customer’s ID code with a purchase request, making it easier to track and bill items to the correct customer project.


Student Notes:



Module 6: Introduction to Process Definition



Exercise 6-1: Add Existing Decision Table to a Process

Scenario: A decision table, IsApprovalRequired, has been created to streamline the approval process. Purchase requests meeting certain criteria will no longer require manager approval:

• Bill to Department = Customer • Order Total < 300 • Bill to Department = Finance and Order Total < 2000

Requirements: As part of this process, you will: • Use drag and drop to add an existing decision table to the

process

How To Do It:

1. Navigate to the StartOrderEntry flow using the Process landing page.

Step Description

1.1 Click the Pega button.

1.2 Go to Process & Rules > Processes > Process Explorer. The Process Explorer gadget displays.



1.3 Click on Purchase Request. The StartOrderEntry flow form opens.

1.4 On the StartOrderEntry form, click the Flow Editor icon to edit the flow.

2. Add the IsApprovalRequired decision table into the StartOrderEntry flow.

Step Description

2.1 Expand the Application Explorer window.

2.2 Under the Order Entry work type, open the Decision category. Then open the Decision Table rule.

2.3 Click on the blue dot next to the IsApprovalRequired rule and drag it into the StartOrderEntry form.



2.4 Connect the OrderConfirmed connector to the top of the IsApprovalRequired decision shape. Click in the Flow Editor workspace; the Yes and No connectors will display attached to the IsApprovalRequired decision shape.



2.5 Connect the Yes connector to the Manager Approval assignment shape and the No connector to the UpdateStatus:Resolved-Completed utility shape.

2.6 Click Save and click the Return icon to close the Flow Editor.

2.7 In the Application Explorer, expand Order Entry, Decision and Decision Table. Click the IsApprovalRequired decision table to open and review it.

2.8 Test the revised flow by creating purchase requests that meet the criteria for bypassing manager approval.




Exercise Summary

In Exercise 6-1, you added the pre-defined IsApprovalRequired decision table from the Application Explorer to the StartOrderEntry flow and tested the Purchase Request application to ensure that you had eliminated the need for manager approval when certain criteria have been met.


Student Notes:



Module 7: Introduction to Business Rules



Exercise 7-1: Edit a Decision Table

Scenario: You want application users to enter customer codes more easily and accurately by selecting a code from a drop-down list. In addition, any purchase request that specifies customer codes 001, 002, or 003 will no longer require manager approval, speeding the overall process.

Requirements: Modify the CustomerCode property so that it displays a list of allowed customer codes. Modify the process by updating the IsApprovalRequired decision table, so that any purchase request that specifies the customer code 001, 002, or 003 does not require manager approval. Test the rule to ensure that the table is consistent and returns the proper results.

How To Do It:

1. Modify the CustomerCode property so that it contains a list of customer codes, ranging from 001 to 005, plus one blank row.

Step Description

1.1 From the Application Explorer, click the CustomerCode property to open the property rule. The Property form appears.

1.2 On the General tab of the Property form, in the Table Type drop-down list, select Local List.

Note: Note that a triangle on the lower right corner of a text box identifies a SmartPrompt. A SmartPrompt may be used on rule and data forms, to provide a user with a dynamic selection list for fast data entry. To complete a SmartPrompt box, place the insertion point inside the box and press the Down Arrow key. Double-click to select one choice from the list.



1.3 In the HTML Property field, use the SmartPrompt to select PromptSelect.

1.4 In the Table Values array, select the Add a row icon and enter five code values (001 through 005). Leave the first row blank; this ensures that no default value appears in the Customer Code field on the Enter a Purchase Request form.

1.5 Save the property rule.

2. Modify the IsApprovalRequired decision table by adding a new condition using the CustomerCode property.

Step Description

2.1 From the Application Explorer, expand the Decision category and the Decision Table. Open the IsApprovalRequired decision table.



2.2 Under the Order Total column, click in any body cell (not a heading cell). Then click the Insert Column Before icon .

2.3 Click the header row in the new column. This opens the Decision Table Property Chooser dialog.

2.4 On the Settings tab, in the Property field, use the SmartPrompt to select CustomerCode. Be sure to include a single dot (a period) before the property name, for example, .CustomerCode.

2.5 Check the Use Range check box. Accept the default options.

2.6 Click Save. The decision table should look this:



2.7 Under the >= and <= columns, for the Customer row, use SmartPrompt to select 001 and 003 respectively. Purchase requests for the customer Bill To Department with customer codes 001 through 003 will not require manager approval.

2.8 Save the decision table.

3. Click Show Conflicts on the rule form to test the decision table rule for consistency. A dialog appears stating “The Decision Table is consistent.”

4. Create three new purchase requests. Based on the customer code selected, check to see whether it is sent for manager approval.

Field Name Purchase Request 1 Purchase Request 2 Purchase Request 3 Bill To Department Customer Customer Documentation

Customer Code 002 004

Item Dell Laptop Toshiba Laptop Xerox Printer

5. Click Logout.




Exercise Summary:

In Exercise 7-1, you made two enhancements to the purchase request application. The first enhancement involved creating a drop-down list of customer codes. Allowing users to select a code from a pre-defined list instead of typing in this code will make this process easier and more accurate. This change will reduce the time required to process a purchase request, especially those that were delayed due to invalid customer codes entered by users. The second enhancement will also speed the purchase request process, in this case, by removing the need for manager approval for specific customer codes 001, 002, or 003 when the Bill To Department is Customer.

You modified the customer code property to include all of the customer codes that will appear in the drop-down list.

You also modified the IsApprovalRequired decision table so that any purchase requests for customer projects that specify a customer code of 001, 002, or 003 will not require manager approval. Lastly, you tested the decision table’s consistency to ensure that it return the proper results.


Student Notes:



Module 8: Introduction to the PDN and Developer Help



Exercise 8-1: Open Process Commander Developer Help

Scenario: Become familiar with some of Process Commander‘s Developer Help features.

Requirements: Process Commander provides extensive help for developers. In this exercise, open the Developer Help and learn how to use it by navigating to the section on Using this Help System. Also, search for a specific topic.

How To Do It:

1. Click the Help menu icon in the Quick Launch menu at the top of your portal, and select Developer Help. The Process Commander V6 help window opens.

2. On the Contents tab, click on the Using this Help System link. This page contains information about how to find various topics in the help system. You can also access context-sensitive help from the toolbar help icon that appears in many tools and wizards.

3. In the Search tab, enter Decision Table, and read the first result that is returned.




Exercise Summary:

In Exercise 8-1, you opened Developer Help and learned the basics of how to use it. You reviewed the section on Using this Help System, navigated around to become familiar with the organization of the help system and searched for a specific topic. As you become more familiar with Process Commander, you will find the Developer Help a useful resource for learning about the various components, terms and concepts and instructions for how to create a specific rule.


Student Notes:



Module 9: Direct Capture of Objectives



Exercise 9-1: Run the Application Profile Wizard

Scenario: The Application Profile defines the components that comprise the Loan Request application. The Application Profile wizard guides you through a series of input steps to collect high level requirements and produce a professional looking, work-based proposal for your project. The profile also provides the basis for automated input into the Application Accelerator wizard, which is described in Exercise 9-2. You have been provided a completed Application Profile which is used to generate your application.

Requirements: Review the completed Application Profile (AP-97), which has been provided to you.

How To Do It:

1. Log on to the system as the user [email protected], using the password password.

2. Open the Application Profile (AP-97) for the Loan Request application.

Step Description

2.1 From the Application menu, select New Application > Profiles in Progress.

2.2 Open the Application Profile AP-97. The Application Profile wizard opens on the Processes step for the Auto Loan process.



3. Click Actions and select Overview to review the Application Overview.

4. Review the Application Overview. When you finish, Click OK to exit the Application Overview and return to the Discovery Map.



5. Switch to the Mortgage tab and double-click the Review Conditional Offer shape in the mortgage flow to review the associated use case.

Note: The document icon in the upper right corner of the Review Conditional Offer shape indicates that a use case is attached.

6. Review the use case, including the description, the actors, and the associated business objective.

7. Click the Requirements tab to review the requirements associated with the use case. When you finish, click OK to close the dialog to return to the Processes tab.



8. Proceed to the next step in the wizard by clicking Integration. Double-click the listed integration point (AutoMakeModel) and review the information provided. When you finish, close the dialog and return to the wizard.

9. Proceed through the remainder of the steps in the wizard, until you reach the Profile Review step.

10. Expand the AutoLoan, HomeEquityLoan, and Mortgage work type entries, and the Common supporting type. Notice the use cases which appear.

Note: Most of the listed use cases correspond to steps in the application process that you will build over the remaining modules.



11. Click the Requirements tab to review all the requirements associated with the listed use cases.

12. Click Finish at the bottom of the page to complete the Application Profile wizard.

13. Do not click Generate this Application at this time, as the next exercise begins at this point.

14. Generate the Application Profile document.

Step Description

13.1 From the Actions menu, click Document.

13.2 Check the Attach to profile checkbox.

13.3 Click Create Document. A Microsoft Word window appears, and the Application Profile document is generated.

15. Review the generated document. When you finish, close Word.



16. Verify that the Application Profile document has been attached to the Application Profile.

Step Description

15.1 Click the Attachment icon next to the Actions menu.

15.2 Expand the Attachments area and verify that the document was attached to the Application Profile.




Exercise 9-2: Create an Application Using the Application Accelerator

Scenario: The Application Accelerator wizard guides you through a series of input steps and prompts you for information about the key design elements that are used to create the base application structures and rules. The Application Accelerator is best used in conjunction with an Application Profile. When you provide an Application Profile, the information it contains is transferred to various forms in the Application Accelerator wizard. This avoids the need to re-enter information, and ensures that project requirements are captured when the application is generated. In this exercise, use the Application Accelerator to create your base application from the information provided in the Application Profile.

Requirements: Create the starting point for your application, by: • Launching the Application Accelerator • Using your Application Profile to provide information • Providing the remaining required information • Generating the classes, RuleSets, and initial rules for the

application

How To Do It:

1. Click Generate this Application to launch the Application Accelerator. The Application Accelerator opens and presents the Application Overview dialog.

Tip:

When you launch the Application Accelerator from the Application Profile wizard, the Application Accelerator uses the open Application Profile as its information source. If you launch the Application Accelerator from the Application menu, you must specify an Application Profile from which to import information.



2. In the Application Overview dialog, enter the following information:

Field Name Value To Enter Framework Name LendFW

New Implementation Name Loans

3. Click OK to accept your edits and advance to the Base and RuleSets step of the Application Accelerator. The Parent Class and RuleSet Name are already defined for the Framework application, but you must provide information for the Implementation application. Enter the following information, and check the Modify Test Operators checkbox.

Field Name Value To Enter Organization Name iLend.com

Division Name Lending



4. Advance to the Processes step of the Application Accelerator, and review the Discovery Maps that are displayed.

5. Advance to the Class Structure step, and add a new class, named Home, to the class structure as a parent of the HomeEquityLoan and Mortgage classes.

Step Description

5.1 Click Add Layer.

5.2 Enter Home as the name of the class to add to the class structure.

5.3 Select HomeEquityLoan and Mortgage as children of the Home class.

5.4 Click OK.



Note:

The Home layer added in the class structure lets you save rules in a class common to both mortgage and home equity loans, without sharing them with auto loans. This provides an additional level of reusable rules.

6. Proceed through the remaining steps in the Application Accelerator, until you reach the Review Objects step. Review the rules that will be generated by the Application Accelerator and added to your initial application.



7. Click Create to generate your application structure. When the Application Accelerator finishes, click Finish, and then click Switch to new application.

Tip:

Clicking Switch to new application refreshes your browser and updates the Application Explorer for you. If you do not click Switch to new application, you will need to log out and log back in to see your new application.




Exercise 9-3: View the Application Overview

Scenario: Running the Application Accelerator has provided you with a functional starting application, from which you will build out the Loan Request application. Before you begin development, you should review the project objectives and overview in the Application Profile. Doing so provides you with information such as the business objectives, business need, work types, use cases, actors, work types, etc.

Requirements: View the information contained in the Application Profile on the Application Overview landing page.

How to Do It:

1. From the Pega button click Application > Overview. This opens the Application - Overview landing page in a tabbed layout.



2. Review the information on the Basic Information tab.

3. Click the Work Types & Use Cases and Actors tabs to review the information that was provided from the Application Profile.



Exercise 9-4: Run a Process Created by the Application Accelerator

Scenario: By running the Application Accelerator, you created an application and some basic rules – including starting flows. These starting flows represent the processes you attempted to capture in the Application Profile. As you build out your application, you will modify these rules – and create new ones – to add functionality to your application.

Requirements: Run the Mortgage Main Flow process and review the steps that were added to the flow by the Application Accelerator.

How to Do It:

1. Run the Mortgage Main Flow process.

Step Description

1.1 From the Quick Launch toolbar, click the Run icon.

1.2 From the Run menu, click Run Process > Mortgage Main Flow.

2. Click Create in the New Work Object form. This creates a Mortgage Request work item.

3. You should see a form similar to the following:



Note: Do not click Click to Create; you will add steps to the loan processes and create the user interface in a later module.

4. Step through the remainder of the process, clicking Submit to advance to the next form. Stop when you reach the last form (Underwrite Loan). At each step of the process, you should see a form similar to the previous example.

5. Click Submit to submit the last form and complete the process.

Reference Material:

Refer to the following PDN articles for more information on these related topics

• PRKB26128 Creating an Application Profile • PRKB26129 Using the Application Accelerator • PRKB25665– Introduction to the SmartBPM Methodology • Webinar Archive – The PegaScrum Agile Methodology • PRKB25401– About the Project Management Framework • PRKB25397 – About the Test Management Framework




Exercise Summary:

In Exercise 9-1, you used the Application Profile wizard to review the existing application profile for the Loan Request application. The Application Profile wizard documents the processes, use cases, and requirements that dictate how you should build your application.

In Exercise 9-2, you used the Application Accelerator to convert the data from your application profile into a working application. Because you ran the Application Accelerator, Process Commander provided you with a base set of rules that can be used as a starting point when developing your application. You will edit some of these rules in later modules.

In Exercise 9-3, you viewed the Application Overview which lists the business objectives, the use cases for each work types, and actors of the application. This is useful in relating the user interface and other business rules built in the application that meet one of the use cases or the requirements.

In Exercise 9-4, you ran one of the processes created by the Application Accelerator. Even without creating or updating any rules, you already have a functioning application, which you will extend as you progress through the upcoming modules.


Student Notes:


Pegasystems Inc. Fast Track 10-1

Module 10: Class Structure and RuleSets


10-2 Fast Track Pegasystems Inc.



Exercise 10-1: Review the Class Structure Generated by the Application Accelerator

Scenario: Now that you have run the Application Accelerator, you are ready to begin developing your application. Before you begin, however, you should review the class structure created by the Application Accelerator.

Requirements: Review the class structure to understand what rules were created by the Application Accelerator. This will help you understand inheritance in your application, which in turn, will help you to reuse rules when possible.

How to Do It:

1. Open the Class Structure Viewer.

Step Description

1.1 Right-click ILend-FW-LendFW-Work.

1.2 Click Structure.



2. Expand the work classes for your application.

Step Description

2.1 Locate the Work entry in the ILend- section. This is the ILend-FW-LendFW-Work class.



2.2 Click Work to expose its child classes, AutoLoan and Home.

2.3 Click Home to expose its child classes, HomeEquityLoan and Mortgage.

3. Expand the Work- class to expose its child classes.



4. Click each of the following classes, and note its directed parent.

ILend-FW-LendFW-Work

ILend-FW-LendFW-Work-AutoLoan

ILend-FW-LendFW-Work-Home

ILend-FW-LendFW-Work-Home-HomeEquityLoan

ILend-FW-LendFW-Work-Home-Mortgage



Exercise 10-2: Review Inheritance in an Application

Scenario: Become familiar with the rule inheritance of all classes, their pattern and parent classes, and the class inheritance path for your application.

Requirements: Review the class hierarchy and find the directed and pattern parent classes of all generated classes.

How To Do It:

1. Open the Class Inheritance Diagram for the ILend-FW-LendFW-Work class.

Step Description

1.1 Right-click ILend-FW-LendFW-Work.

1.2 Click Inheritance.



2. Beginning with the ILend-FW-LendFW-Work class and ending with @baseclass, list the class inheritance:

ILend-FW-LendFW-Work

@baseclass

3. Open the Class Inheritance Diagram for the ILend-FW-LendFW-Work-Home-Mortgage class.



4. Beginning with the ILend-FW-LendFW-Work-Home-Mortgage class and ending with @baseclass, list the class inheritance:

ILend-FW-LendFW-Work-Home-Mortgage

@baseclass

5. Open the ILend-FW-LendFW-Work-Home-Mortgage class rule. What class is listed as the directed parent? Does this class appear on the Class Inheritance Diagram?

Taking It Further:

Review the inheritance for the ILend-FW-LendFW-Work-AutoLoan class as well. Observe how it is different from the Mortgage class rule.



Exercise 10-3: Review the Rules Created by the Application Accelerator

Scenario: The Application Accelerator creates the class structure, RuleSets, starter flows, and some other basic rules. At this stage you can review all the rules that were created by the Application Accelerator.

Requirements: To review all the rules created by the Application Accelerator.

How to Do It:

1. Return to the Application Explorer and review the rules created in the ILend-FW-LendFW-Work class and all of its child classes. Expand the rule categories and rule types to view the individual rules created.

Step Description

1.1 Expand ILend-FW-LendFW-Work. Expand all the subcategories listed in each and view the rules created by Application Accelerator.

1.2 Continue expanding the tree for ILend-FW-LendFW-Work-Home and also for ILend-FW-LendFW-Work-AutoLoan to see the rules created by the Application Accelerator.




Exercise 10-4: Create Classes

Scenario: Data classes are used to store data model properties and rules specific to a data class. They are typically used to store embedded properties which can be referenced in the application. Data classes can also include section rules and other business rules in order to enforce reusability. For example, the loan application has embedded pages (data classes), like Borrower Information, that can be used for all of the company’s loan types.

Requirements: Create some of the data classes that are needed to build the Loan Request application. Specify the directed parent for these data classes. You must also create embedded pages for the loan applicant’s (Borrower’s) assets, liabilities, and spouse information. Review the Inheritance Diagram. Change the parent class of a class to allow its sub-classes to use the properties and other rules defined in that class.

How to Do It:

1. Create the ILend-FW-LendFW-Data-Borrower class.

Step Description

1.1 Click the Class Selector , located to the right of the ILend-FW-LendFW-Work class name in the Application Explorer.

1.2 Select the ILend-FW-LendFW-Data- class.

1.3 Right-click ILend-FW-LendFW-Data- and select New > SysAdmin > Class.

1.4 In the New Rule dialog, enter ILend-FW-LendFW-Data-Borrower as the class name. Confirm that LendFW is the RuleSet. Click Create.



2. Configure the class using the following properties, and verify the inheritance of the class.

Field Name Value To Enter Select Concrete

Created in Version 01-01-01

This class Does not belong to a class group

Step Description

2.1 In the Select field, select Concrete.

2.2 In the Created in Version field, use the SmartPrompt to select the 01-01-01 RuleSet Version.

2.3 In the This class field, select does not belong to a class group.

2.4 On the History tab, complete the Full Description and Usage fields, and save the Class rule.

2.5 Click the Related Rules button and select Inheritance to review the inheritance diagram for the ILend-FW-LendFW-Data-Borrower class.

When you finish, close the Class Inheritance Diagram dialog.



3. Update this class to use the Data-Party class as a directed parent.

Step Description

3.1 On the class rule, change the Parent Class to point to the Data-Party class, so you can use the properties defined in that class. Save the class rule.

3.2 Return to the inheritance diagram and notice the change. This allows the ILend-FW-LendFW-Data-Borrower class (and any subclasses inheriting from it) to use the properties and other rules defined in Data-Party.

4. Using the steps described above, create the following classes listed in the table below and have them use the specified directed inheritance class. (Make sure all the classes have “does not belong to a class group” selected).

Class Name Directed Inheritance ILend-FW-LendFW-Data-Borrower-Assets ILend-FW-LendFW-Data-Borrower

ILend-FW-LendFW-Data-Borrower-Liabilities ILend-FW-LendFW-Data-Borrower

ILend-FW-LendFW-Data-Borrower-Spouse ILend-FW-LendFW-Data-Borrower

ILend-FW-LendFW-Data-Property Data-Party

ILend-FW-LendFW-Data-Loan ILend-FW-LendFW-Data-

Note: Since these data classes will not be instantiated, they should not belong to a class group.

5. Return to the ILend-FW-LendFW-Data class, and open the Class Structure Viewer to review your changes.

Reference Material:

Refer to the following PDN articles for more information on class inheritance and RuleSets:

• PRKB25169 – How Class inheritance works • PRKB25269 – About RuleSet Versions • PRKB24257 – How to Use RuleSet Prerequisites



Exercise Summary:

In Exercise 10-1, you learned that when designing a PRPC application, it is essential that you understand the class structure, including the pattern and directed parents of your work classes. To promote your understanding of the class structure, you reviewed the class structure of both work classes generated by the Application Accelerator. You should now have a better understanding of the various classes and the layer (such as organization level, framework level, PRPC level and work layer) in which each class exists.

In Exercise 10-2, you reviewed the inheritance of the work classes for your application. You followed the path used by the rule resolution process for each of these classes. The Class Inheritance diagram provides another way to view the class structure, showing both the pattern and directed inheritance path. The numbers noted in the structure indicate the path taken by the rule resolution process to find the rules defined. Understanding this path helps you reuse rules across multiple layers and allows you to create specialized rules if needed.

In Exercise 10-3, you reviewed all the other rules created by the Application Accelerator. Application Accelerator is a tool which is used to quickly build the rules based on information derived from the Application Profile. Application Accelerator creates work classes, all RuleSets and RuleSet Versions, base classes for data classes, interface classes, model rules, and work parties if they are included in Application Profile. The Application Accelerator also enforces the class structure while it builds the starting point application, allowing developers to build PRPC applications right on top of the base PRPC classes it provides. This helps promote the reuse of the standard PRPC business rules and also standardizes how a PRPC application is constructed.

In Exercise 10-4, you created new class rules for all of the data classes that will be used in the Data Model module. The data classes contain all of the data model properties. Creating a data model and positioning it at the appropriate place is critical when building an enterprise application. You must identify which data classes need to be shared across the organization, across the division, across the product line, and so on. Naming the data classes and defining them in the appropriate position in your class structure helps all developers achieve rule reuse.

Some of the data classes inherit from Data-Party, which allows you to use the properties that exist in that class; for example, information related to a party or person, such as first name, last name, email, phone, and address. These properties can be reused for loan applicants (borrowers) instead of defining new properties in the Borrower class.


Student Notes:



Module 11: Creating a Data Model



Exercise 11-1: Create a Property Using the New Rule Dialog

Scenario: When completing a Mortgage or Home Equity loan request application, Loan Agents must specify the terms of the loan – the duration of the loan, and whether the rate is fixed or adjustable.

Requirements: Create a property named Terms in both the ILend-FW-LendFW-Work-Home-Mortgage and ILend-FW-LendFW-Work-Home-HomeEquity class. These properties will be used in an upcoming exercise to capture the terms of the loan sought by the applicant.

How to Do It:

1. Right-click the ILend-FW-LendFW-Work-Home-Mortgage class.

2. From the menu, click New > Data Model > Property.

3. In the New Rule dialog, enter Terms in the Property Name field.

4. Use the default values in ruleset name, ruleset version and type fields.

5. Click Quick Create to create the text property.

6. In the ILend-FW-LendFW-Work-Home-HomeEquityLoan class, repeat steps 2 – 5 to create a text property named Terms.



Exercise 11-2: Change the Appearance of a Property

Scenario: Loan Agents would prefer to select home equity loan terms from a list of values, rather than entering them manually. In addition to entering data more quickly, this will allow Loan Agents to enter data with fewer inaccuracies, which will reduce the number of applications that are rejected with incorrect entries.

Requirements: Modify the HTML Property of the Terms property in the ILend-FW-LendFW-Work-Home-HomeEquityLoan class to include a pre-defined list of acceptable values as part of the property definition, and configure the property so that it will display these values in a drop-down list when you add it to the user interface.

How to Do It:

1. In the ILend-FW-LendFW-Work-Home-HomeEquityLoan class, open the Terms property definition.

2. Modify the property to display as a drop-down list containing the following values:

Table Values 5 years, fixed rate

10 years, fixed rate

15 years, fixed rate

Step Description

2.1 Click the Check Out icon to check out the rule for editing.

2.1 In the General tab of the property rule, select the PromptSelect in the HTML Property field.



2.2 In the General tab of the property rule, select LocalList in the Table Type field.

2.3 Add the specified values to the Table Values list. To create a new table entry, click the Append Row icon.

2.4 Save the rule.

2.5 Click the Check In icon to check the rule back in to the system. While checking in add a comment for the check-in.

Note: By default, check-in functionality is enabled in any ruleset created by the Application Accelerator. Once you finish editing a rule, you should check in the rule, so others can view your changes.

Tip: Defining a local list and presenting it as a drop-down list is a form of input validation, because you are preventing the user from entering data incorrectly. You will learn about other methods of input validation in Module 18: Validation.



Exercise 11-3: Create Properties Using the Define Property Wizard

Scenario: As a system architect, you need to create properties to collect data during the loan application processes: properties to support both the home equity loan and mortgage request processes.

Requirements: Create the remaining properties needed for HomeEquityLoan and Mortgage work types, including properties that may be common to multiple work types.

How to Do It:

1. In the Application Explorer, right-click the ILend-FW-LendFW-Work-Home class, and click Define Properties.

2. Use the Define Properties wizard to create the following property.

Description Type Loan Purpose Text

Home In Mind TrueFalse

Tip: The Define Properties wizard automatically generates the property name from the contents of the Description field, removing any spaces. The contents of the Description field are used to populate the Short Description field on the property rule form.

3. Click Next to advance to the Define Property Display step of the wizard, and enter the Display As and Details information for the following properties.

Name Display As Details LoanPurpose DropDown Purchase

Refinance

HomeInMind TextBox Default



4. Click Finish. Using the Application Explorer, verify that the properties were created in the ILend-FW-LendFW-Work-Home class.

5. Use the Define Properties wizard to create the following properties in the ILend-FW-LendFW-Work class. Click Finish on the first page of the wizard, as the Display As fields do not need to be updated.

Description Type Loan Rate Adjustment Decimal

Needs PMI TrueFalse

Base Rate Decimal

Risk Rate Adjustment Decimal

Note: In this exercise, you created properties that will be used to collect data in the user interface and act upon it. In the next exercise, you will create a data model – a data structure better suited to collecting information for storage.



Exercise 11-4: Create Embedded Properties

Scenario: The data classes (Data Model) are designed in a way that the properties can be used across different loan products. You need to define properties for the loan applicant, or borrower, such as their first name, last name, and spouse details which can then be referenced in each loan process. You also need to define properties that are common to all loans (like loan purpose, loan terms, loan rate, and property details) that are specific to both home equity loan and mortgage process.

Requirements: Create all the page and pagelist properties for HomeEquityLoan and Mortgage classes that will be used in the loan request application. The properties are to be defined in ILend-FW-LendFW-Data-Borrower and accessed by the BorrowerInfo embedded property defined in the ILend-FW-LendFW-Work class. You will add more properties to child classes of Borrower, such as ILend-FW-LendFW-Data-Borrower-Assets, ILend-FW-LendFW-Data-Borrower-Liabilities, and ILend-FW-LendFW-Data-Borrower-Spouse. You must also create a new embedded property for all loans, pointing to ILend-FW-LendFW-Data-Loan.



How to Do It:

1. Create a Page property named BorrowerInfo in the ILend-FW-LendFW-Work class, to collect borrower information.

Step Description

1.1 In the Application Explorer, under the ILend-FW-LendFW-Work class, expand the Data Model category.

1.2 Right-click Property and click New.

1.3 In the New Rule dialog, in the Property Name field, enter BorrowerInfo.

1.4 Click Create.

1.5 In the Property Mode drop-down list, select Page.

1.6 In the Page Class field, select the ILend-FW-LendFW-Data-Borrower class.

1.7 Save the property.

2. Repeat step 1 to create the following page properties:

Name Property Class Property Mode

Page Class

Loan Info ILend-FW-LendFW-Work Page ILend-FW-LendFW-Data-Loan

Property Info ILend-FW-LendFW-Work-Home Page ILend-FW-LendFW-Data-Property

3. Switch the Application Explorer to the ILend-FW-LendFW-Data- class.



4. Using the Define Properties wizard, in the ILend-FW-LendFW-Data-Borrower class, create the following page properties.

Description Mode Type Assets Page List ILend-FW-LendFW-Data-Borrower-Assets

Liabilities Page List ILend-FW-LendFW-Data-Borrower-Liabilities

Spouse Page ILend-FW-LendFW-Data-Borrower-Spouse

5. Use the Define Properties wizard to create the following properties in the specified classes. Click Next at the first step to enter the Display As and Details information.

Description Type Display As Details Class Name: ILend- FW-LendFW-Data- Borrower Asset Total Decimal TextBox CurrencyAmount

Credit Score Integer TextBox Default

Date Of Birth Date TextBox Date

Income Decimal TextBox CurrencyAmount

Liability Total Decimal TextBox CurrencyAmount

Marital Status Text DropDown Single Married Domestic Partnership Divorced

Class Name: ILend- FW-LendFW-Data- Borrower-Assets Asset Type Text DropDown Checking account

Savings account Investment account

Asset Value Decimal TextBox CurrencyAmount



Class Name: ILend- FW-LendFW-Data- Borrower-Liabilities Liability Type Text DropDown Credit card

Home equity loan Mortgage

Liability Value Decimal TextBox CurrencyAmount

Class Name: ILend- FW-LendFW-Data- Loan Amount Decimal TextBox CurrencyAmount

Asking Price Decimal TextBox CurrencyAmount

Down Payment Decimal TextBox CurrencyAmount

Loan Purpose Text TextBox Default

Loan Type Text DropDown Auto Loan Home Equity Loan Mortgage

Property Type Text DropDown Single Family Detached Townhouse Condominium Multi-family Dwelling

PMI Premium Decimal TextBox Currency Amount

Rate Decimal TextBox Default

Terms Text TextBox Default



Note: The Spouse and PropertyInfo pages should display no single-value properties. All of the single-value properties used by these pages are inherited from a parent class.




Exercise 11-5: Create a Data Table

Scenario: Unlike home equity loans, which allow all possible combinations of loan purpose and terms, certain combinations of mortgage purpose and terms are not allowed. As a result, Loan Agents would like the Loan Request application to include a set of drop-down lists that would eliminate the possibility of incorrect combinations. Also the choices listed in the drop-down lists must be updated periodically. All the loan applicants who are approved by the underwriter must be recorded in the system as customers for future retrieval.

Requirements: Create two data tables: one containing information about mortgage products, and one to record customer data:

• The mortgage products table should include the allowed combination of mortgage purposes and terms.

• The table of customer data should contain the following columns: First Name, Last Name, Address, Address Line 2, City, State, ZIP, Phone and Email.

How to Do It:

1. Using the Data Table wizard, create a data table of mortgage products.

Step Description

1.1 From the Pega button, click Data Model> Data Tables to access the Data Tables landing page.

1.2 Click Add a new Data Table to create a new data table.



1.3 In the Data Table Wizard, for Class Name, enter

ILend-FW-LendFW-Data-HomeLoans.

1.4 In the Description field, enter Listing of home loan products.

1.5 In the Derives From field, select ILend-FW-LendFW-Data-.

1.6 In the Name field of the first row, enter ID. The ID property is the key value for the data table.

1.7 Click the Add a Row icon to create one more row.

1.8 In the empty row, in the Name field, enter LoanTerms. In the Label field, enter Loan Terms. In the Type field, select Text.

1.9 Click Generate.



2. Populate the data table with the following mortgage loan products.

ID Label Loan Terms 1 Purchase 30 years, 3/1 adjustable

2 Purchase 30 years, 5/1 adjustable

3 Purchase 15 years, fixed rate


5 Refinance 10 years, fixed rate


Step Description

2.1 Click the List Editor link.

2.2 Click the Add a Row icon to create an empty row.

2.3 In the ID field, enter 1.

2.4 In the Label field, enter Purchase.

2.5 In the Loan Terms field, enter 30 years, 3/1 adjustable.



2.6 Click the Add a Row icon to create additional rows, and enter the remaining values in the preceding table.

2.7 When you finish, close the window and return to the Data Tables Landing Page. Verify that the table now contains 6 rows.

3. Create a second data table. In the Class Name field, enter ILend-FW-LendFW-Data-Customers. In the Description field, enter Customer Data. In the Derived from field, select ILend-FW-LendFW-Data-.

4. Specify ID as the Key property for the data table.



5. Add the following properties to the table, and click Generate.

Name Type FirstName Text

LastName Text

AddressLine1 Text

AddressLine2 Text

City Text

State Text

PostalCode Text

Phone Text

Email Text

SSN Text

6. Close the Data Table wizard and return to the Data Tables Landing Page. You should see two data tables listed.

Note: The Customers table should contain no rows of data. You will populate this data table in a future exercise.



7. In the ILend-FW-LendFW-Work class, create a new Page List property named Customer. For Page Class, select ILend-FW-LendFW-Data-Customers.




Exercise 11-6: Set Initial Values Using a Model Rule

Scenario: Certain information should be set by default in your loan application, such as a base interest rate – used as a starting point for calculating each borrower’s interest rate – and the asset and liability details.

Requirements: Create a model in the ILend-FW-LendFW-Work class to define default values for properties common to multiple loan types.

How to Do It:

1. In the ILend-FW-LendFW-Work-Home-HomeEquityLoan class, add the following properties and values to the pyDefault model rule. You need to check out the rule to make these changes. After making the changes, check in the rule to make the changes into effect.

Property Value .LoanPurpose Refinance

.LoanInfo.LoanType Home Equity Loan

2. In the ILend-FW-LendFW-Work-Home-Mortgage class, add the following properties and values to the pyDefault model rule.

Property Value .LoanInfo.LoanType Mortgage



3. Create a model rule named pyDefault in the ILend-FW-LendFW-Work class.

Step Description

3.1 In the Application Explorer, expand the ILend-FW-LendFW-Work class.

3.2 Right-click the Technical category and click New > Model.

3.3 In the New Rule dialog, for Model Name, enter pyDefault, and click Create.

4. Add the following properties and values to the model:

Property Value .BaseRate .0325

.NeedsPMI false

.BorrowerInfo.Assets(1).AssetType Checking account

.BorrowerInfo.Liabilities(1).LiabilityType Credit card

Note: The (1) in the preceding property names represents the index value. When referencing a Page List property, such as Assets, you must include the index of the specific list entry to read from or write to.



Taking It Further: If you have time, try the following exercise to create a Declare Index for an Embedded Property: Exercise B1: Index Embedded Properties Refer to the PDN article PRKB25278 How to create declarative indexes for embedded properties for instructions on how to use the wizard to create declarative indexes.



Exercise 11-7: Disable Check-in/Check-out Functionality

Scenario: You have reviewed the rules created by running the Application Accelerator, created data classes needed to build the application, and are now ready to begin application development. Since you are the only developer working on this project, you would like to disable the check-in and check-out functionality so that you will not need to check out each rule every time you need to modify it.

Requirements: Disable check-in and check-out for all framework RuleSets since they are the only RuleSets that you will be working with in this class.

How to Do It:

1. From the Pega button, click Application> Structure > RuleSet Stack.

2. Under the RuleSet bar, click the open icon next to the LendFW RuleSet.

3. Click the Security tab.

4. Clear the Use check-out? Checkbox.

5. Save the LendFW RuleSet rule.

6. Repeat steps 2 – 5 to disable rule check-out for the LendFWInt RuleSet.




Exercise Summary:

In Exercise 11-1, you created properties using the New Rule dialog. Properties are data elements used by an application. Some of the properties will be used to display choices when you create the user interface for your application. Other properties will be used to store information to be acted upon while processing work. And some properties will be used to execute calculations.

In Exercise 11-2, you specified a list of default values for one property, and configured this property to display these values as the contents of a drop-down list. By defining this list, users will be restricted to a small set of possible choices, eliminating any variations in the values users enter, especially those due to typographical errors.

In Exercise 11-3, you created properties by using the Define Properties wizard. The Define Properties wizard allows you to create multiple properties within one class at the same time. In addition, you can specify the HTML Property and any Local List values in the wizard, eliminating the need to open the property rules afterward to add this information

In Exercise 11-4, you defined embedded properties using the Property wizard. You also used HTML Properties which define how the data elements (properties) get displayed in the UI such as textbox, radio button, select box or checkbox. HTML property is also used to specify the required formatting, like displaying the decimal value as a currency amount, or including a calendar control for date fields.

In Exercise 11-5, you created two data tables. One data table stores information about the mortgage loan products offered by iLend; the other data table will be used to store data about customers whose loans are approved and underwritten. Data tables store their contents in a separate database table, so they can be used to store data outside of an application, where it can be updated without needing to update the application.

In Exercise 11-6, you used model rules to assign default values to properties. The model rules in your application are chained, combining the properties they define to take advantage of reuse.

In Exercise 11-7, you disabled rule check-out in your application. Rule check-out is an essential tool in a multi-developer environment, because it prevents multiple users from simultaneously editing a rule and inadvertently overwriting each other’s changes. Disabling the check-out feature is not advised for multi-user development environments. However, since you are using a single-developer environment during this course, rule check-out functionality can be disabled for your convenience.


Student Notes:



Module 12: Process Definition



Exercise 12-1: Create a Subflow

Scenario: Once a Loan Agent completes a loan application on behalf of the loan applicant (borrower) and a conditional offer is accepted, the Loan Request must be sent to a Junior Loan Officer for the underwriting process. As part of this process, the Junior Loan Officer will request a copy of the loan applicant’s credit report, verify the financial information provided during the application process, and enter the loan applicant’s credit score. The Loan Request application uses this credit score to calculate an updated interest rate for the loan. The Junior Loan Officer will then decide whether to extend an official loan offer to the loan applicant.

Requirements: Create an underwriting flow in the ILend-FW-LendFW-work class. Because this process is common to all of the loan types offered by iLend, you can implement it in a class inherited by each of your work types, and call it from each starting flow.

How To Do It:

1. In the ILend-FW-LendFW-Work class, create the UnderwriteLoan flow.

Step Description

1.1 In the Application Explorer, right-click the ILend-FW-LendFW-Work class, and select New > Process > Flow.

1.2 In the New Rule dialog, for Flow Type enter UnderwriteLoan, and click Create.

2. Open the flow in the Flow Editor by clicking the Flow Editor icon .



3. Add an Assignment shape named Approve Application to the flow, and connect it to the Start shape.

Step Description

3.1 Drag an Assignment shape from the Shapes palette onto to the Flow Editor workspace. Position the Assignment shape over the connector emanating from the Start shape, and release the mouse button.

3.2 In the Assignment Properties panel, in the Name field, enter Approve Application.

3.3 In the StatusWork field, select Pending-Approval. Click Apply to accept your changes.

4. Add a flow action named Approve to the assignment, to approve the loan request and specify a Likelihood of 85. Associate the flow action with the IssueFinalOffer use case.

Step Description

4.1 Drag a connector from the Shapes palette onto the Flow Editor workspace.

4.2 In the Properties panel, in the Flow Action field, select Approve.

4.3 In the Work Type field, select Common.

4.4 In the Use Case field, select IssueFinalOffer.

4.5 In the Likelihood field, enter 85.



5. Add a second flow action, named Reject, to the assignment. Specify a Likelihood of 15, and associate the flow action with the RescindConditionalOffer use case defined in the Common Work Type.

6. Add an End shape and connect the flow actions to it.

7. Save the flow and exit the Flow Editor.



Exercise 12-2: Create a Tabbed Screen Flow

Scenario: In order to process the requests for loans, iLend must collect certain basic information from the loan applicant. This information falls into four basic categories:

• Personal identification and qualification information (such as name, address, and income)

• Information about the loan being requested (such as the type of loan and amount of the loan)

• Information about how the loan will be used (the property to be purchased)

• The approximate net worth of the loan applicant. Loan Agents must be able to navigate each form and readily understand (and communicate to the loan applicant) the information being requested. Loan Agents must also be able to navigate between forms, because choices made early in the application process affect the information that is collected later, and they may need to return to a particular form to alter entries.

Requirements: Create a tabbed screen flow for both mortgage and home equity loan work types to collect the information needed to process the Loan Request application. Each screen flow should consist of four steps:

• Collecting loan applicant/borrower information • Collecting loan information • Collecting property information • Collecting asset and liability information

How To Do It:

1. In the ILend-FW-LendFW-Work-Home-Mortgage class, create the CollectInfoMortgage screen flow.

Step Description

1.1 In the Application Explorer, right-click Mortgage, and select New > Process > Flow.



1.2 In the New Rule dialog, in the Flow Type field, enter CollectInfoMortgage. In the (Template) Name field, select ScreenFlowStandardTabbed.

1.3 Click Create to create the flow rule.

2. Open the flow in the Flow Editor.

3. Change the existing Assignment shape in the flow to collect information about the loan applicant. Use the following information to update the assignment:

Field Name Value to Enter Name Collect Borrower Information

Flow Action CollectBorrowerInfo

Work Type Common

Use Case CollectBorrowerInformation

Step Description

3.1 Select the Perform Task assignment on the Flow Editor workspace.



3.2 On the Properties panel, specify the information provided in the preceding table.

4. Drag three assignment shapes on to the Flow Editor workspace to create the remaining assignments in the flow. Use the following information to create each shape.

To collect information about the loan:

Field Name Value to Enter Name Collect Loan Information

Flow Action CollectLoanInfo

Work Type Mortgage

Use Case CollectMortgageInformation

To collect information about the property:

Field Name Value to Enter Name Collect Property Information

Flow Action CollectHomeInfo

Work Type Common

Use Case CollectPropertyInformation

To collect asset and liability information about the loan applicant:

Field Name Value to Enter Name Collect Assets and Liabilities

Flow Action CollectAssetsandLiabilities

Work Type Common

Use Case CollectAssetAndLiabilityInformation



5. Use connectors to connect the flow shapes in the following order:

6. Click the Draft icon in the toolbar to turn on Draft mode.

Tip: Turning on Draft mode allows you to save and run the flow even though you have not created the flow actions (which will display the user interface at run time).


8. Expand the collapse icon in the flow rule to update the Short Description on the flow rule to Collect Mortgage Information, and save the flow rule.



9. Save a copy of the flow by changing the class in the Applies To field to ILend-FW-LendFW-Work-Home-HomeEquityLoan and entering CollectInfoHomeEquity in the Flow Type field. Enter Collect Home Equity Loan Information in the Short Description, and update the Collect Loan Information assignment, using the following information:

Field Name Value to Enter Name Collect Loan Information


Work Type HomeEquityLoan

Use Case CollectHomeEquityLoanInformation

Tip: You can update the Properties panel for a flow shape without opening the flow in the Flow Editor, by right-clicking the flow shape and clicking the Edit tab.



Exercise 12-3: Call a Subflow from a Starter Flow

Scenario: iLend wants the Home Equity Loan and Mortgage processes to collect basic information, such as personal information, loan requested for, how the loan is intended to be used, and the net worth of the borrower. iLend also wants the Home Equity Loan and Mortgage processes to use the underwriting process, a process where a Loan Officer uses the borrower’s credit report when deciding whether to approve the loan.

Requirements: Modify each starting flow to call the appropriate screen flow and the UnderwriteLoan flow you created in the previous two exercises.

How to Do It:

1. In the Application Explorer, in the ILend-FW-LendFW-Work-Home-Mortgage class, open the Mortgage flow. Update the Short Description to New Mortgage Request. Save the flow and open it in the Flow Editor.

2. Delete the Collect Information and Underwrite Loan assignments.

Note: These assignments were added to the Discovery Map as placeholders for the flow shapes that you will add in this exercise.

3. From the Application Explorer, drag the CollectInfoMortgage flow rule onto the Flow Editor, onto the connector emanating from the Start shape.



4. On the Properties panel for the flow shape, in the Flow type drop-down list, select Screen Flow.

5. Make sure that the tail of the connector leading to the Add PMI Premium utility is attached the CollectInfoMortgage flow shape. In the Properties panel, change the connector type to Always.

Note: This is necessary since the connector was previously attached to an Assignment. Connector types can vary, depending on the shape they emanate from. Not all connector types are compatible with every shape.

6. Drag a flow shape, in the ILend-FW-LendFW-Work class, onto the Flow Editor workspace, in the space formerly occupied by the Underwrite Loan assignment. Change the flow rule to UnderwriteLoan. Change the connector type emanating from the flow shape to Always.



7. Click the connector emanating from the Review Conditional Offer assignment, and update the Properties panel with the following information:

Field Name Value To Enter Flow Action Approve

Likelihood 80

WorkType Common

UseCase AcceptConditionalOffer

8. Add a second flow action, named Withdraw, to the Review Conditional Offer assignment. Specify a Likelihood of 20, and associate the flow action with the WithdrawApplication use case defined in the Common Work Type. Connect this connector to an end shape.


10. Repeat steps 1-9 to add the CollectInfoHomeEquity and UnderwriteLoan flows to the HomeEquityLoan flow. Update the Short Description of this flow to New Home Equity Loan Request. (Make sure the connectors for both the flow shapes are modified to Always from Action).



Reference Material:

Refer to the following PDN articles for more information on Process Definition:

• PRKB25463 – Introduction to process definition and flow rules.

Taking It Further: If you have time, try the following exercise: Exercise B2: Add a Spinoff to a Flow, to start a parallel flow and the current flow continues processing. Refer to the Developer Help System for information about spinoff shapes.




Exercise Summary:

In Exercise 12-1, you created a new flow rule to capture the loan underwriting process. You created this loan in the work class because this process is common to all of your work types. Because this flow is defined in the parent class for the work type classes, it can be inherited by the work type classes. You also added two standard flow actions, Approve and Reject, to this process, taking advantage of rules provided by Process Commander to begin creating your user interface.

In Exercise 12-2, you created screen flows to capture information as part of the loan application process. A screen flow is a special type of flow that presents its constituent flow actions as a series of tabs in one window. Users can easily switch between the different flow actions, moving backward and forward in the process. Unlike a regular flow, in which the work item is submitted and resubmitted to the database every time you advance to the next flow action, a screen flow does not submit the work item until you exit the flow.

In Exercise 12-3, you added these flows to the home and mortgage main flows as subflows. You were able to break up your processes into component flows, and were able to tailor each flow to address a particular set of needs. For the screen flows, the requirement is to allow Loan Agents to switch between different forms during the application process; for the UnderwriteLoan flow, the requirement is to have an underwriting procedure that is common to all loan types.


Student Notes:



Module 13: User Interface



Exercise 13-1: Create a Section

Scenario: Loan Agents must collect the information about the loan, specifically, the purpose, term, and the type. The loan terms differ with each loan type.

Requirements: Create a section rule and add the following properties: Loan Type, Loan Purpose, Loan Terms, and Loan Amount.

How to Do It:

1. In the Application Explorer, right-click ILend-FW-LendFW-Home-Mortgage, and select New > User Interface> Section. In the Purpose field, enter CollectLoanInfo. Click Create.

2. From the Application Explorer, drag the following properties from the ILend-FW-LendFW-Work class into the first row of the two-column Smart Layout.

• .LoanInfo.LoanType

• .LoanInfo.Amount

In the Pick/Add Page And Class dialog, enter .LoanInfo in the Page Name field and click OK.



3. Add the following two properties to the second row of the layout.

Property Class .LoanPurpose ILend-FW-LendFW-Work-Home

.Terms ILend-FW-LendFW-Work-Home-Mortgage

4. On the Properties panel for the LoanType property, check the Read only checkbox, so the user can not modify the value.

5. Add the title Loan Information to identify the section at run-time.

Step Description

5.1 Click the Show Wireframes icon .

5.2 Open the Properties panel of the Smart Layout, by clicking the layout label and clicking the View Properties icon .

5.3 In the Format drop-down list, select Standard (Sub). In the Title field, enter Loan Information. In the Header Type drop-down list, select Bar.

5.4 Click OK.



6. Click the Preview icon in the rule form to preview the section rule. The Loan Purpose and Terms fields should be empty. In a later exercise, you will populate these fields with values from a data table.

7. Click the Save As icon to create a version of the CollectLoanInfo section in the ILend-FW-LendFW-Work-Home-HomeEquityLoan class.

8. Preview the section. The Loan Purpose and Terms fields should contain values.

9. Repeat step 1 to create the following two section rules.

Section Class CollectPropertyInfo ILend-FW-LendFW-Work-Home

CollectAssetsandLiabilites ILend-FW-LendFW-Work

You will update these section rules in later exercises.



Exercise 13-2: Create a Section Containing Multiple Layouts

Scenario: Loan Agents must be able to collect basic information about the loan applicant and their spouse. This information is specific to the loan applicant and does not differ with the loan type. iLend wants to collect the details of the loan applicant such as first name, last name, Social Security Number (SSN), date of birth, contact details such as address, phone number and email address. iLend also wants to collect the annual income and the marital status of the loan applicant.

Requirements: Create a section in ILend-FW-LendFW-Work and add the properties defined in the previous module to the section rule. Also, add the same properties for spouse.

How to Do It:

1. In ILend-FW-LendFW-Work, create a new section named CollectBorrowerInfo.

2. Add the loan applicant/borrower properties to this section rule.

Step Description

2.1 From the Basic palette, drag an input box and drop it on the Smart Layout’s first Field cell (the Field cell on the left).

2.2 Click the magnifying glass icon to open the Cell Properties panel. For Property, select .BorrowerInfo.pyFirstName, and clear the contents of the Display As field. When you finish, click OK.



Note: When you enter a value in the Display As field, you override the HTML Property setting on the property rule.

2.3 Click the Label cell and in the Cell Properties panel, in the Value field, replace Input Box with First Name. Click OK.

2.4 In the same row, drag another input box into the Field cell.

In the Field cell, select .BorrowerInfo.pyLastName. In the Label cell, enter Last Name.

2.5 In the second row, add input box and enter .BorrowerInfo.pySSN in the left Field cell and enter SSN in the Label cell. In the right Field cell, add input box and enter .BorrowerInfo.DateOfBirth and clear the Display As field in the Cell Properties panel. In the Label field, enter Date of Birth.

2.6 In the new row, add input boxes and in the left Field cell, enter .BorrowerInfo.pyHomePhone and in the Label cell, enter Home Phone. In the right Field cell, enter .BorrowerInfo.pyEmai1 and in the Label cell, enter Email Address.

2.7 In the new row, drag .BorrowerInfo.Income and .BorrowerInfo.MaritalStatus from the Application Explorer.

2.8 Save the section.

3. Preview the section rule. Note that the Marital Status drop-down list includes all of the values specified on the property rule.



4. Enter Borrower Information in the section header and save the section. Select Standard (Sub) for the header format.

5. From the Layout palette drag a layout and drop it below the Smart Layout. Click OK in the Set Layout Type dialog to accept the default selection – a Smart Layout using the Double template.

6. In the new layout, add the following properties from the Spouse page property.

Label Property First Name .BorrowerInfo.Spouse.pyFirstName

Last Name .BorrowerInfo.Spouse.pyLastName

SSN .BorrowerInfo.Spouse.pySSN

Date Of Birth .BorrowerInfo.Spouse.DateOfBirth

Annual Income .BorrowerInfo.Spouse.Income

7. Apply the label Spouse Information to the layout you just created.



8. Add a new layout named Address Information, and add the following properties in the Smart Layout.

Label Property Address .BorrowerInfo.pyHomeAddress1

Address Line 2 .BorrowerInfo.pyHomeAddress2

City .BorrowerInfo.pyHomeCity

State .BorrowerInfo.pyHomeState

Postal Code .BorrowerInfo.pyHomePostalCode



9. Save the completed section rule.

Best Practice(s):

Label fields include a reference the property name. This reference (Label for) is an optional field; however, defining the property name provides three benefits:

• During runtime, when a user clicks the label, the focus moves to the cell containing the property.

• Screen reader software, such as JAWS for Windows®, can identify the cell containing the property.

• If the Required checkbox is checked for a property, it displays an asterisk next to the label.

You used the properties defined in the Data-Party class, such as .pyFirstName and .pyLastName. This is a good example of reusing properties defined in the parent classes, rather than creating additional properties. You modified the parent class of the data classes in the previous module in order to be able to reuse these properties.



Exercise 13-3: Adding a Section to a Flow Action

Scenario: Loan Agents must be able to collect the loan applicant information, spouse information, and the information on the loan specifically the purpose, term and the type.

Requirements: Create new flow actions and include the sections that are created in the previous exercises.

How to Do It:

1. Launch a New Mortgage Request process.

2. Click Create to advance to the Collect Borrower Information step.

3. Create a flow action named CollectBorrowerInfo, in the ILend-FW-LendFW-Work class.

Step Description

3.1 Click the Click to create link on the Collect Borrower Information step. The New Rule dialog appears.



3.2 Click Create.

4. Add the CollectBorrowerInfo section to the flow action.

Step Description

4.1 Return to the Developer portal. The CollectBorrowerInfo flow action should be the active tab.

4.2 From the Application Explorer, drag the CollectBorrowerInfo section onto the Layout tab of the CollectBorrowerInfo flow action.

4.3 Save the flow action.

5. Return to the New Mortgage Process, and click Submit to advance to the next step, Collect Loan Information.



6. Repeat steps 3 – 6 to create the following flow actions.

Flow Action Class Section Reference CollectLoanInfo ILend-FW-LendFW-Work-Home-

Mortgage CollectLoanInfo

CollectPropertyInfo ILend-FW-LendFW-Work-Home CollectPropertyInfo

CollectAssetsAndLiabilites ILend-FW-LendFW-Work CollectAssetsAndLiabilites

7. Complete the New Mortgage Request process. Do not create any more flow actions.

8. Copy the CollectLoanInfo flow action into the ILend-FW-LendFW-Work-Home-HomeEquityLoan class.

Step Description

8.1 Open the CollectLoanInfo action in the ILend-FW-LendFW-Work-Home-Mortgage class.

8.2 Click the Save As icon .

8.3 In the New Rule dialog, select ILend-FW-LendFW-Work-Home-HomeEquityLoan in the Applies to field. Click Create.

8.4 Turn on Wireframes, and verify that the flow action references the copy of the CollectHomeInfo section in the ILend-FW-LendFW-Work-Home-HomeEquityLoan class.


9. Launch a New Home Equity Loan Request process to view the flow actions you just created.

Best Practice(s):

Always use the same names for both a flow action and the section it references.




Exercise 13-4: Create a Repeating Grid Layout

Scenario: iLend wants the Loan Agents to collect the information on the borrower’s assets and liabilities.

Requirements: Create a repeating grid that will be used to enter the assets and liabilities information.

How to Do It:

1. Open the CollectAssetsAndLiabilites section defined in the ILend-FW-LendFW-Work class.

2. Add a Grid Repeat layout containing the AssetType and AssetValue properties.

Step Description

2.1 From the Layout palette drag a new layout and place it on top of the Smart Layout. In the Set Layout Type dialog, click Repeating and choose Grid in the dropdown. Click OK.

2.2 Click the Show Wireframes icon.

2.3 In the Grid Layout, open the Properties panel for the Repeat Grid element. Enter .BorrowerInfo.Assets in the List/Group field. In the Edit Mode drop-down list, select Read/Write. Click OK.



2.4 In the Application Explorer, expand Data Model under ILend-FW-LendFW-Work and expand BorrowerInfo, and then expand Assets.

2.5 Drag the Asset Type property to the property cell in Repeat Grid as shown.

2.6 Widen the Asset Type cell to a width of 140.

2.7 Drag the Asset Value property to the second property cell.

2.8 Delete the empty cells by selecting the cell and clicking the Delete Column icon .

3. Repeat step 2 to add another repeating grid for liabilities in the same section and add the properties LiabilityType and LiabilityValue.



4. Remove the empty Smart Layout.

Step Description

4.1 Select the Smart Layout.

4.2 Click the Delete Row icon .

5. Save the rule and preview the section.

6. Run a New Mortgage Request process and add and delete assets and liabilities from their respective lists.


Taking It Further: If you have time, try the following exercise: Exercise B3: Audit Changes to a Field, to track changes made in any field in the audit trail. Refer to: PDN article PRKB26135: How to track changed values of work object properties using the Field Level Auditing gadget.



Exercise 13-5: Use the HTML Rules Inspector to Review your UI

Scenario: When you run a process, you may need to know which section rule is displayed in the screen in order to modify the elements or the format. In this situation, you can use the HTML Rules Inspector tool to identify all the user interface rules – harness, flow action and section – that are used to render the screen.

Requirements: Turn on the HTML rules inspector in the Designer Studio to see the associated user interface rules.

How to Do It:

1. From the Run menu, select Rules Inspector -> HTML Rules to enable the HTML Rules Inspector.

2. Launch a New Mortgage Request process. Notice the HTML Rule icon that now appears on the form.



3. Position the cursor over the HTML Rule icon located above the text Summary and click on the tooltip that appears. This tooltip identifies the rule that produces that portion of the form.

4. Continue running the process and click the various HTML rule icons to open the specific rules for review. When you finish, close the process window, and then select the Rules Inspector-> HTML Rules in the Run menu again to turn off the Rules Inspector.




Exercise Summary:

In Exercise 13-1 and 13-2, you created sections using Smart Layouts. Also, you became familiar with labels and fields as well as the layout and basic controls that are used to build a section. There are three sets of controls in the rule form: Layout, to add sections/layouts, Basic, to add the input box, select and other basic controls, Advanced, to add Smart Labels, auto complete, etc. We will use some of the advanced controls in the future exercises.

In Exercise 13-3, you added sections to the flow actions so they will be displayed while running the process. In the flow, the user interface screens are displayed only when there is an assignment shape. Every assignment shape contains one or more flow actions and each flow action corresponds to a section. Depending on the likelihood, the flow action with the highest likelihood displays the corresponding section.

In Exercise 13-4, you created a repeated grid layout for a page list. There are other types of repeating layouts (like row, column, tabs, trees and tree grids) which can be used in other scenarios.

In Exercise 13-5, you learned how to use the HTML rules inspector tool, which is very useful to identify the user interface rules while running the process. This tool is also very useful in projects where there are multiple developers, and when there are many screens.



Student Notes:


Module 14: Clipboard



Exercise 14-1: Review a Process Using the Clipboard

Scenario: As you build out your application, you may need to review information, such as property values. Sometimes, this information is not presented in the user interface. In this situation, you can use the Clipboard to review all the properties – including those for system information – that are collected and set by your processes.

Requirements: Run the Mortgage Request process and review the information set by your application at each step.

How To Do It:

1. Click the Run button in the Quick Launch toolbar and select Run Process > New Mortgage Request.

2. Click the Create button to create a new a Mortgage Request item. The Collect Borrower Information form is displayed.

3. Click the Clipboard Tool in the Quick Launch toolbar.

4. Notice that values have already been set for the .LoanType, .Asset(1).AssetType, and .BaseRate properties. Where did these values come from?

5. Advance through the remainder of the New Mortgage Request process.

Step Description

5.1 On the Collect Borrower Information form, do not specify any values, simply click Next.

5.2 Do the same for the Collect Loan Information form, and the Collect Home



Information form.

5.3 Stop when you reach the Collect Assets and Liabilities form. Click the Finish button.

6. In the left panel of the clipboard, expand the UserPages node and click the pyWorkPage entry. View all the single value properties for the page, and their values.

Tip: In addition to viewing information, you can also use the clipboard to set information. To set a property value using the clipboard, open the corresponding page and enter the value you wish to set in the corresponding property field, and click Submit.

7. In the left panel, under pyWorkPage, expand BorrowerInfo and notice the values in the right panel.

8. Close the Clipboard tool. In the Collect Assets and Liabilities form, select Finish. On the next form, click Submit, then close the Confirm Work Object window.




Exercise Summary:

In Exercise 14-1, you used the Clipboard tool to examine the property values set during the New Mortgage Request process. You viewed the hierarchical page structure of the clipboard, and reviewed the properties set on each page. You saw that values were set for certain properties, even before you created a work item. These values came from data model rules. Property values also changed as a result of user input on forms.



Student Notes:


Module 15: Decision Rules



Exercise 15-1: Create a Decision Table to Route Work Items

Scenario: A Loan Agent collects information from the individual requesting a loan and submits the loan request to a Junior Loan Officer. A Junior Loan Officer has limited capability to approve and formalize conditional offers. In cases where they cannot provide final approval, the request must be routed to a Loan Officer. Loan requests must be routed to the Loan Officer for approval in the following situations:

• Home equity loans for more than $30,000. • Mortgages for more than $417,000 on single-family dwellings. • Mortgages on multi-family dwellings, condominiums, and

townhouses. Loan requests which do not satisfy these criteria can be approved by the Junior Loan Officer and resolved without the need for further action.

Requirements: Create a decision table to route loan requests to the Loan Officer in the following situations:

• A home equity loan in excess of $30,000. • A mortgage in excess of $417,000 for a single-family home. • A mortgage for a multi-family dwelling, condominium, or

townhouse.

How To Do It:

1. Create a decision table named RequiresLoanOfficer.

Step Description

1.1 In the Application Explorer, right-click ILend-FW-LendFW-Work, and select New > Decision > Decision Table.

1.2 In the Purpose field, enter RequiresLoanOfficer and click Create.



2. Create two outcomes for the table.

Step Description

2.1 Click the Results tab.

2.2 Under Allowed Results, in the first row, enter Yes.

2.3 Click the Add a Row icon to create a new row, for a second allowed result, enter No.

3. Edit the existing table column to test the type of loan requested.

Step Description

3.1 Click the Table tab.

3.2 Click the empty header column under Conditions of the table.

3.3 In the Property field, using the SmartPrompt, select .LoanInfo.LoanType.

3.4 From the Use Operator drop-down list, select “=”. Click Save.

4. Create a column to test whether the loan amount is less than or equal to the maximum that the Junior Loan Officer can process.

Step Description

4.1 Next to if, click on the cell under the newly created property.

4.2 Click the Insert Column After icon to create an additional column.



4.3 Click the empty header column next to LoanType in the Conditions.

4.4 Select .LoanInfo.Amount as the property to test.

4.5 Select <= as the operator for the test. Click Save.

5. Repeat step 4 to create a column in the conditions and select .LoanInfo.PropertyType as the property to test. Select = as the operator for the test. Click Save.

6. Create a condition to test home equity loans.

Step Description

6.1 Next to the if, under the conditions, click one of the table cells.

6.2 In the cell under LoanType column, select HomeEquityLoan.

6.3 Under the Amount column, enter 30000 in the cell.

6.4 In the cell under Return column, enter No.

6.5 Click the Insert Row After icon to create an additional row.

7. Populate a second row to return No in the Return column if the loan type is for a Mortgage of not more than $417,000, on a single-family detached residence.

8. In the Otherwise row, in the Return column, select Yes.

9. Save the table.



10. Test the logic of the table for Home Equity Loan.

Step Description

10.1 Click the Run button in the rule form of the decision table to test the table.

10.2 In the Test page, for LoanType, select HomeEquityLoan. Click Run Again.

10.3 For the Amount column, enter 50000. Click Run Again.

10.4 Click the Result Decision Path link to review which row evaluated as true.

11. Continue testing the decision table for these additional scenarios and check the resulting decision path used to reach them.

Property Value To Enter LoanType Home Equity Loan

Amount 20000

Property Value To Enter LoanType Mortgage

Amount 300000

PropertyType Single Family Detached


Amount 500000

PropertyType Single Family Detached


Amount 200000

PropertyType Condominium



12. Add the decision table to the flow.

Step Description

12.1 Open the UnderwriteLoan flow in the Flow Editor.

12.2 Disconnect the Approve flow action connector from the End shape.

12.3 Drag the RequiresLoanOfficer decision table rule onto the Flow Editor workspace, on top of the Approve connector extending from the Approve Application assignment.

12.4 Add an assignment named Loan Officer Approval to the flow.

12.5 Connect the Yes connector extending from the decision shape to the Loan Officer Approval assignment.

12.6 Connect the No connector coming from the decision shape to the End shape.

12.7 Add a connector emanating from the Loan Officer Approval assignment. Connect the connector to the End shape.

12.8 Turn on Draft mode for the flow.

12.9 Save the flow and exit the Flow Editor.



13. Run both the New Mortgage Request and New Home Equity Loan Request processes to test the decision table logic.

Taking It Further: If you have time, try the following exercise to create a circumstanced decision table: Exercise B4: Circumstance a Decision Table Refer to PDN article PRKB25272: How multivariate circumstancing works for instructions on how to create a circumstanced decision table.



Exercise 15-2: Create a Decision Table to Automatically Approve or Reject Work Items

Scenario: iLend wants to evaluate the risk of the loan based on certain factors, to determine if they want to underwrite the loan or not. A loan application is considered too risky in the following situations:

• Home Equity loan where the loan amount is 1.3 times more than the total income of the applicant and spouse.

• Mortgages where the loan amount is three times more than the total income of the applicant and spouse.

• Total value of listed assets is less than the total value of listed liabilities.

Loan requests which are considered too risky should not be approved.

Requirements: Create a decision table for evaluating the risk of the applicant in the following situations:

• Home equity loan more than 1.3 times of the total income of the applicant and spouse.

• A mortgage loan three times more than the total income of the applicant and spouse.

• Total listed liabilities in excess of total listed assets

How to Do It:

1. Create a decision table named IsTooRisky, in the ILend-FW-LendFW-Work class.

2. Create two outcomes for the table: TooRisky and NotTooRisky.



3. Populate the table to return TooRisky in the following situations:

• If the total value of the listed assets(AssetTotal) is less than the total value of the listed liabilities(LiabilityTotal)

• If the loan is a Home Equity loan and the loan amount is greater than 1.3 times the total income (borrower and spouse).

• If the loan is Mortgage and the loan amount is greater than 3 times the total income (borrower and spouse).

Otherwise, return NotTooRisky.

Tip: Use the Expression Builder to enter calculations in the Amount > column. In the Expression Builder, you can type a “.” Select properties using a SmartPrompt, and syntax-check your expression by clicking Validate. To use the Expression Builder, position the cursor in the expression field and click the magnifying glass icon.

4. Save the decision table.

5. Test the logic of the decision table, using the following scenarios:

Loan Type Amount Borrower Income

Spouse Income

Asset Total

Liability Total

Result

Home Equity Loan 40000 40000 60000 50000 10000 NotTooRisky


Home Equity Loan 50000 30000 3000 10000 5000 TooRisky

10000 50000 TooRisky

Mortgage 300000 40000 60000 10000 5000 NotTooRisky

Mortgage 300000 60000 20000 10000 5000 TooRisky

Note: Although you were able to unit test the loan applicant’s assets and liabilities, this will not always be so. In a later exercise, you will set the



values of these properties declaratively, using the result of a calculation. When you determine a property value declaratively, you cannot unit test any condition that depends on it. You can only test these conditions by running the flow.

6. Add the decision table to the Mortgage flow.

Step Description

6.1 Open the flow rule and open the Flow Editor.

6.2 Disconnect the connector emanating from the CollectInfoMortgage flow shape from the Add PMI Premium utility.

6.3 Drag the IsTooRisky decision table onto the connector emanating from the CollectInfoMortgage flow shape.

6.4 Connect the TooRisky connector to the End shape.

6.5 Connect the NotTooRisky connector to the Add PMI Premium utility.



7. Repeat step 6 to add the decision table to HomeEquityLoan flow, connecting the NotTooRisky connector to the Review Conditional Offer assignment.

8. Run both Mortgage and Home Equity loan process to test the decision tables.




Exercise 15-3: Use a Decision Tree to Determine a Property Value

Scenario: iLend needs to adjust the loan rates it offers to borrowers based upon several factors: the type of the loan, the loan duration, and the credit risk represented by the borrower. In addition, if a borrower does not provide a minimum down payment of 20% of the property’s purchase price, iLend must calculate a Private Mortgage Insurance (PMI) premium, which will be added to the monthly loan payment.

Requirements: Create a decision tree to evaluate the loan rate adjustment for the home and mortgage loans for the different loan terms and purposes. Create a decision tree to determine a rate adjustment based upon the applicant’s credit score. Create a decision tree to calculate the premium for the mortgage loan using the loan terms.

How to Do It:

1. Create a decision tree named LoanRateAdjustment in the ILend-FW-LendFW-Work class.

Step Description 1.1 In the Application Explorer, right-click the ILend-FW-LendFW-Work class and select

New > Decision > Decision Tree.

1.2 In the Decision Tree field, enter LoanRateAdjustment, and click Create.

2. Create a decision tree branch to calculate loan rate adjustments for Home Equity loans.

Term Rate Adjustment 5 years, fixed rate 0.0575

10 years, fixed rate 0.0600

15 years, fixed rate 0.0650



Step Description 2.1 In the first line, click ["first value" = "second value"].

2.2 In the first field, select .LoanInfo.LoanType.

2.3 In the second field, enter “Home Equity Loan”.

2.4 Click return and select continue from the drop-down list.

2.5 In the sub-condition that appears, click ["first value" = "second value"].

2.6 In the first field, select .LoanInfo.Terms.

2.7 In the second field, enter "5 years, fixed rate".

2.8 Click result, and enter .0575 in the field.

2.9 Click the Add Row After button to create a new sub-condition, and set this sub-condition to return .0600 for a "10 years, fixed rate" loan.

2.10 Click the return and select otherwise, in the result enter 0.0650.

3. Create another branch of the tree to return rate adjustments for the following mortgages.

Purpose Term Rate Adjustment Purchase 15 years, fixed rate 0.01125

Purchase 30 years, fixed rate 0.0150

Refinance 10 years, fixed rate 0.0125



Refinance 20 years, fixed rate 0.01625

4. Make the last condition an Otherwise, returning 0.0250.

5. Save the decision tree. Unit test the tree by supplying various values to test conditions.

6. Create a decision tree named RiskRateAdjustment in the ILend-FW-LendFW-Work class, to calculate the rate adjustment based upon the borrower’s credit score, using the following values:

Borrower’s Credit Score Rate Adjustment 0 0

751 and above 0.0025

701 – 750 0.0050

651 – 700 0.0075

551 – 650 0.0100



550 and below 0.0250

Tip: If your decision tree evaluates only one property, you can create a simplified form of the decision tree by using the Input tab to specify the property. The Input tab becomes available after you click Advanced on the Results tab.

Step Description 6.1 Click the Results tab.

6.2 In the options, enable Allowed to Evaluate Properties, and click the Advanced button.

6.3 Click the Input tab.

6.4 Select .BorrowerInfo.CreditScore in the property field.

6.5 Click the Decision tab.

6.6 Click [expression]. Enter 0 in the value is field, and enter 0 in the [result] field.

6.7 Click the Add new decision after this one icon to add another condition.

6.8 Enter >750 in the [expression] and enter .0025 as the result.

6.9 Repeat to add other values listed in the above table.



7. Why does the tree include the condition when the borrower’s credit score is zero? Why would this situation be different from one in which the credit score is 550 or lower?

8. Create another decision tree named PMIPremium in the ILend-FW-LendFW-Work-Home-Mortgage class. Build this tree to return values for the following conditions, and set the final Otherwise condition to return 0.

Down Payment/Asking Price

Loan Terms Result

<10% 15 years, fixed rate 0.0079*.LoanInfo.Amount/12




Tip: When creating a decision tree, you can use an otherwise to combine conditions that will return the same result. In this example, the 30 years, 3/1 adjustable and 30 years, 5/1 adjustable mortgages return the same result, and can be combined using an otherwise.



Note: In this exercise, you created a decision tree to determine a result based upon the value of certain properties. In order to assign this result to a property, you need to use a Declare Expressions rule, which you will learn about in Module 19: Introduction to Declarative Rules.



Exercise 15-4: Create a When Rule to Control Display of a Layout

Scenario: When collecting information about the loan applicant, Loan Agents do not want the Spouse Information fields to be displayed unless the applicant is married or in a domestic partnership.

Requirements: Create a When rule to test if either Married or Domestic Partnership has been selected in the Marital Status field in the Borrower Information layout.

How To Do It:

1. In the ILend-FW-LendFW-Work class, create a When rule named MaritalStatus.

Step Description

1.1 In the Application Explorer, right-click ILend-FW-LendFW-Work and select New > Decision > When.

1.2 In the Purpose field, enter MaritalStatus and click Create.

2. Configure the When rule to test if the applicant is either married, or in a domestic partnership.

Step Description

2.1 In the first line, click the ["first value" = "second value"] link.

2.2 In the first field, select .BorrowerInfo.MaritalStatus.

2.3 In the second field, enter "Married".

2.4 Click the Append Condition icon to add a new row.

2.5 Select Or in the condition dropdown.



2.5 Click the ["first value" = "second value"] link.

2.6 In the first field, select .BorrowerInfo.MaritalStatus.

2.7 In the second field, enter "Domestic Partnership".

Note: You will learn how to use the When rule to control the display of a user interface element in Module 20: Advanced UI.



Exercise 15-5: Direct a Process Using a When Rule

Scenario: If a borrower does not provide a down payment of at least 20% of the asking price of a property, iLend requires that the borrower pay for PMI. The Loan Officer wants the PMI premium to be calculated automatically, if necessary, as part of the mortgage application process.

Requirements: Create a when rule to evaluate whether a PMI premium needs to be calculated, and add the when rule to the mortgage loan process.

How To Do It:

1. Quick Create the NeedsPMI when rule in the ILend-FW-LendFW-Work-Home-Mortgage class.

Step Description

1.1 In the Condition field , enter .LoanInfo.DownPayment/.LoanInfo.AskingPrice < .2

1.2 Click Quick Create.



2. Add a Fork shape named Requires PMI? to the Mortgage flow.

Step Description

2.1 Drag the Fork shape onto the Flow Editor workspace.

2.2 Name the fork Requires PMI?.

2.3 Add two connectors to the fork.

2.4 Select one connector, and in the Properties panel:

• Select When as the condition

• Select the NeedsPMI when rule

• Change the Likelihood to 30%

2.5 Select the other connector and change the condition to Else.

3. Connect the Requires PMI? fork in the flow.

Step Description

3.1 Connect the NotTooRisky flow action connector to the fork shape.

3.2 Connect the Else connector to the Review Conditional Offer assignment shape.

3.3 Connect the NeedsPMI connector to the Add PMI Premium utility shape.



Note: In the next module, you will learn how to create an activity to calculate the PMI premium, using the decision tree you created in Exercise 15-3, and add this activity to the Mortgage flow.

4. Click Save.




Exercise Summary:

In Exercise 15-1, you created a decision table to route a loan request to the Loan Officer under certain conditions. You added this decision table to the UnderwriteLoan flow using a Decision shape, using the result of the table to route the loan request to the Loan Officer if necessary.

In Exercise 15-2, you created a decision table to evaluate the risk represented by the applicant. You added some basic tests to the table: comparing the applicant’s income to the amount of their loan request, and comparing the value of their assets to their liabilities. You then added this table to a flow using a decision shape, using the results of the table to determine whether an application is conditionally approved or rejected.

In Exercise 15-3, you created three decision trees:

• To calculate a loan rate adjustment, dependent upon the loan purpose and terms. • To calculate a risk rate adjustment, dependent upon the applicant’s credit score. • To calculate a PMI premium, dependent upon the loan terms and ratio of the down

payment to the loan amount.

A decision tree is a free-form format for evaluating conditions. You can create a variable number of conditions to test, and nest one test within another. This provides more flexibility over when to evaluate a particular condition – unlike a decision table, where each condition must be evaluated for each row.

In Module 19: Introduction to Declarative Rules, you will learn how to invoke the rate adjustment decision trees in a calculation.

In Exercise 15-4, you created a when rule to determine if the applicant’s marital status is married or domestic partnership. If the applicant is married or in a domestic partnership, the when rule will return a result of true. You can use a When rule to perform a yes/no or true/false test, rather than a decision table or decision tree. In Module 20, you will learn how to use this when rule to display or hide the Spouse Information layout on the CollectBorrowerInfo section.

In Exercise 15-5, you created a when rule to determine if a PMI premium is required for the loan. You called this when rule from the Mortgage flow, using a Fork shape. A Fork shape is similar to a Decision shape, but is used to invoke when rules, rather than a decision table or decision tree.


Student Notes:


Pegasystems Inc. Fast Tack to PRPC 16-1

Module 16: Activities


16-2 Fast Tack to PRPC Pegasystems Inc.



Exercise 16-1: Add a Utility to a Process to Execute an Activity

Scenario: As each loan request is processed, its work status should be updated to reflect its current status. The Loan Officer would like the status set on all loan requests that have been resolved, to distinguish them from loan requests awaiting action by a Junior Loan Officer. This status can also be used to create reports to monitor the productivity of Loan Agents and Junior Loan Officers.

Requirements: Add utilities to each main flow to set the status for the following: • Resolved-Rejected – when the request is rejected as too risky • Resolved-Withdrawn – when the request is accepted, but the

applicant declines the offer Add utilities to the UnderwriteLoan flow to set the following statuses:

• Resolved-Completed – when the offer has been formally approved by either the Loan Officer or the Junior Loan Officer

• Resolved-Rejected – when the conditional offer has been rescinded by either the Loan Officer or the Junior Loan Officer

How To Do It:

1. Open the UnderwriteLoan flow in the Flow Editor.

2. Drag a utility shape onto the Flow Editor workspace.

3. Configure the utility to call the standard UpdateStatus activity and set the work status of the work item to Resolved-Rejected.

Step Description

3.1 In the Properties panel for the utility shape, in the Name field, enter Resolved-Rejected.

3.2 In the Rule field, select UpdateStatus.

3.3 Click Apply.



3.4 The Status field appears. Select Resolved-Rejected.

4. Connect the Reject flow action connector to this utility, and connect the utility to the End shape.

5. Add another utility to the flow. Configure this utility to set the work status to Resolved-Completed.

6. Connect the utility into the flow. When you finish, save the flow and exit the Flow Editor.



7. Add a utility to the Mortgage flow to set the work status to Resolved-Rejected. Connect the TooRisky result from the IsTooRisky? decision shape to the utility, and connect the utility to the End shape.

8. Add a utility to the Mortgage flow to set the work status to Resolved-Withdrawn. Connect the Withdraw flow action connector emanating from the Review Conditional Offer assignment to the utility, and connect the utility to the End shape.

9. Run several New Mortgage Request processes to completion, and verify that the work status changes accordingly.

10. Repeat steps 7 and 8 to add utilities to the HomeEquityLoan Flow.




Exercise 16-2: Create an Activity to Set a Property

Scenario: When a loan applicant requests a mortgage to refinance an existing home, or requests a home equity loan, the answer to the question “Do you have a home in mind?” is automatically yes. In these situations, the question should be answered automatically, and the Loan Agent should be able to collect information about the home when they reach the Collect Home Information form. (This information is optional if the loan applicant is requesting a mortgage to purchase a property, as the applicant may not yet know the property they intend to purchase.)

Requirements Create an activity to set the value of the .PropertyInfo.HomeinMind property to true when the value of the .LoanInfo.LoanPurpose property is Refinance. This occurs when:

• The process being run is the Home Equity Loan process • The process being run is the Mortgage process, and the

.LoanPurpose property has been set to Refinance Use a precondition to test the value of the .LoanInfo.LoanPurpose property, and exit the activity if the value is not Refinance. Execute this activity automatically when the Loan Agent reaches the CollectHomeInfo flow action. The .HomeInMind property will be used as a flag in a later exercise, to determine whether to hide or show fields on the Collect Home Information form.

How To Do It:

1. In the Application Explorer, right-click the ILend-FW-LendFW-Work-Home class. In the resulting menu, click New > Technical > Activity. Complete the New Rule dialog, specifying IsRefinance as the name of the activity.

2. In the first step of the activity, in the Method field, select Property-Set.



3. Click the Expand Method Step icon to expose the parameters for the Property-Set method, and enter the following values:

PropertiesName PropertiesValue .HomeInMind true

4. Create a precondition so that this step only executes if the LoanType property is set to Refinance.

Step Description

4.1 Click the Expand Precondition Step icon .

4.2 In the When field, enter .LoanInfo.LoanPurpose==”Refinance”.

4.3 In the if False drop-down list, select Exit Activity. This prevents the activity step from executing if the Loan Agent selects Purchase as the Loan Type.

4.4 Click the Enabled? checkbox to enable the precondition.

5. Save the activity.

6. Configure the CollectPropertyInfo flow action to execute the activity when the Loan Agent reaches the Collect Property Information form.

Step Description

6.1 In the ILend-FW-LendFW-Work-Home class, open the CollectPropertyInfo flow action.

6.2 Click the Action tab.



6.3 In the BEFORE THIS ACTION section, select IsRefinance in the Run Activity field.


Tip: The .HomeInMind property is used as a flag, to determine whether the Loan Agent needs to collect the address of the property. By setting the value of the property .LoanInfo.LoanPurpose to Refinance in the model for the HomeEquityLoan work type in a previous exercise (Module 11: Data Model), you were able to simplify the activity you wrote to automatically display these fields, by testing one condition (the purpose), rather than two (the type of loan and the purpose).



Exercise 16-3: Create a Parameterized Activity

Scenario: When a Loan Agent enters the loan purpose and terms chosen by the loan applicant, they select values from lists of values that are defined specifically for each loan type. However, in order to process the application, this information must be copied to non-loan-specific properties.

Requirements: Create an activity to copy the values of the LoanPurpose and Terms properties, which are specific to each loan type, to corresponding properties on the .LoanInfo page (which is not loan-specific). To do so:

• Define two parameters, Loan Purpose and Terms, to collect the values for the loan-specific properties.

• Call the activity from the CollectLoanInfo flow action defined for each work type, and specify the .LoanPurpose and .Terms properties as values for the parameters.

How To Do It:

1. In the ILend-FW-LendFW-Work class, create a new activity named CopyLoanInfo.

2. Create two input parameters of type string on the activity. Name these parameters LoanPurpose and Terms.

Step Description

2.1 Click the Parameters tab.

2.2 On the first line, in the Name field, enter LoanPurpose. From the Data Type drop-down list, select String. From the In/Out drop-down list, select In.

2.3 Click the Add a Row icon to add a second parameter.

2.4 On the second line, in the Name field, enter Terms. From the Data Type drop-down list, select String. From the In/Out drop-down list, select In.



3. Create an activity step to copy data from the parameters to properties as follows:

Parameter Property to Set LoanPurpose .LoanInfo.LoanPurpose

Terms .LoanInfo.Terms

Step Description

3.1 Click the Steps tab.

3.2 For step 1, in the Method field, select Property-Set.

3.3 Click the Expand Method Step icon.

3.4 In the PropertiesName field, enter .LoanInfo.LoanPurpose.

3.5 In the PropertiesValue field, enter Param.LoanPurpose.

3.6 Click the Add a Row icon to add a second parameter row.

3.7 In the second parameter row, in the PropertiesName field enter .LoanInfo.Terms, and in the PropertiesValue field enter Param.Terms.

4. Configure the activity to run when the Loan Agent leaves the Collect Loan Information form. Specify .LoanPurpose and .Terms as the parameters for the activity.

Step Description

4.1 In the ILend-FW-LendFW-Work-Home-Mortgage class, open the CollectLoanInfo flow action.



4.2 Under the Action tab, in the AFTER THIS ACTION section, select CopyLoanInfo in the Run Activity field.

4.3 Click Params.

4.4 Enter .LoanPurpose in the LoanPurpose field, and .Terms in the Terms field.


5. Test the activity by running the Mortgage loan request process until you reach the Collect Loan Information form, and verify that values are not copied to the LoanPurpose and Terms properties on the LoanInfo page until you submit the form and advance to the next step in the process.

Note: You need to open the clipboard to check if these values are properly set.

6. Repeat step 4 to add the activity to the CollectLoanInfo flow action in the ILend-FW-LendFW-Work-Home-HomeEquityLoan Class.



Exercise 16-4: Create an Activity to call another Rule Type

Scenario: For applications that require assessment of a PMI premium, the PMI premium should be calculated and disclosed.

Requirements: Create an activity, called CalculatePMI, which sets the .NeedsPMI property to true, and executes the PMIPremium decision tree to determine the PMI premium. Call this activity from the MortgageMainFlow flow by using a Utility shape.

How To Do It:

1. In the ILend-FW-LendFW-Work-Home-Mortgage class, create an activity called CalculatePMI.

2. In the first step of the activity, set the value of the property .NeedsPMI to true.

3. Add a second step to the activity, to call the decision tree PMIPremium and calculate the PMI premium for the mortgage.

Step Description

3.1 Click the Add a Row icon to add a second step to the activity.

3.2 In the Method field, select Property-Map-DecisionTree.

3.3 Click the Expand Method Step icon to expose the parameters for the method.



3.4 In the Property Name field, select .LoanInfo.PMIPremium. In the Decision Tree field, select PMIPremium.

3.5 On the Security tab, in the Activity Type drop-down list, select Utility.

3.6 Save the activity.

4. Configure the Add PMI Premium utility in the Mortgage flow to call the CalculatePMI activity.

Step Description

4.1 Open the Mortgage flow in the Flow Editor.

4.2 Select the Add PMI Premium utility shape on the Flow Editor workspace.

4.3 In the Properties panel, select CalculatePMI in the Rule field.

4.4 Save the flow and exit the Flow Editor.



5. Run a New Mortgage Request process, and specify the following values. You need to set the values for Asking Price and Down Payment in the clipboard after you exit the screen flow. When you reach the Review Conditional Offer form, open the clipboard and verify that a value has been calculated for the PMIPremium property.

Field Name Value To Enter Income 80000

Loan Purpose Purchase

Asking Price 200000

Down Payment 20000

Loan Terms 15 years, fixed rate

Loan Amount 180000

Tip: Although this method works, it is usually not the best approach to calculating a value. You will learn the preferred method to calculating values in Module 19: Declaratives.




Exercise Summary:

In Exercise 16-1, you used a utility shape to call the standard activity UpdateStatus. The process executed the activity, which set the status of the work item, without the need for user input. Activities are typically used in scenarios to implement system actions, such as modifying the status of a work item when the process proceeds along a particular path.

In Exercise 16-2, you used an activity to set a property as a flag. In addition, you added a precondition to the activity, so that it only executes under specific circumstances. In this case, if the applicant is requesting either a mortgage to refinance an existing home, or a home equity loan, then you set a property called HomeinMind, which will be used in a later exercise to hide or show fields on the Collect Home Information form (this will occur in Module 20: Advanced UI). This allows you to create one flow action for this step of the process, rather than two or three.

In Exercise 16-3, you created an activity that accepted input parameters. Activities that accept input parameters – or supply output parameters – are more reusable than activities that do not; rather than hard-coding a specific variable in the activity, you can specify the variable when you call the activity. (In this exercise, you specified the parameter on a flow action rule form.) By defining two parameters for the activity and specifying values for them on the flow action form, you were able to create one activity that works for all loan types. Had you referenced the properties explicitly in the activity, you would have needed to create an activity for each loan type.

In Exercise 16-4, you used a fork shape to call an activity when needed. You also learned how to call another rule – in this case, a decision tree – from an activity. Although you were able to perform this calculation using an activity, this is not always the preferred method to do so. You will learn the best practice for calculating values in an upcoming module – Module 19: Declaratives.


Student Notes:



Module 17: RuleSets and Rule Resolution



Exercise 17-1: View Operator Profile

Scenario: The System Administrator has created Operator IDs and access groups that allow iLend users to access the Loan Request application. Each Operator ID is controlled by membership in various access groups. View your Operator Profile to understand how your access is controlled through access to specific RuleSets and RuleSet Versions.

Requirements: Review your Operator ID, [email protected], to see its associated RuleSets.

How To Do It:

1. Open the Operator menu by clicking the white arrowhead next to the operator name.

2. Review the RuleSets you can access. Note that there is an additional RuleSet, [email protected], associated with the operator name. The system creates a default RuleSet used for check-in /check-out for each operator who has access to the developer role.



3. The operator profile also lists the default access group and the application rule in the profile.

Reference Material:

To understand how these RuleSets are assembled in an operator profile, refer to the PDN article PRKB-25161- How Process Commander assembles a RuleSet list in a user profile.

For more information on rule resolution, refer to the PDN article PRKB-25168– Overview of Rule Resolution.

To learn more about specialization and how to build reusable applications, refer to the eLearning module Reusability and Specialization on the PDN.



Exercise Summary:

In Exercise 17-1, you reviewed your Operator Profile to gain a better understand of how your Operator ID’s access to Process Commander is controlled through association with personal, production and application RuleSets.


Student Notes:



Module 18: Validation



Exercise 18-1: Validation

Scenario: ILend wants to address inefficiency in the existing Loan Request process: Loan Request applications that do not contain complete or accurate information still make their way through the flow and are then rejected. They want the Loan Request process to indicate what information the user needs to provide. They have identified certain fields in the Loan Request application that should be required so that incomplete applications will no longer be processed.

Requirements: Make the following fields on the Collect Borrower Information form required so that users must enter values for these fields:

• SSN (Social Security Number) • Phone Number • Annual Income

Users will not be able to proceed to other screens in the loan application process unless they provide values for these required properties.

How To Do It:

1. Open the CollectBorrowerInfo section and configure the SSN, Phone Number, and Annual Income fields to be required.

Step Description

1.1 In the Application Explorer, in the ILend-FW-LendFW-Work class, expand the plus sign next to User Interface.

1.2 Expand Section. Select CollectBorrowerInfo.

1.3 Under the Borrower Information layout, click the Wireframes icon to enable it.

1.4 To the right of the SSN label, click in the blank field to open the Cell Properties panel.

1.5 In the General tab, select the Required checkbox.



1.6 Repeat steps 1.5 and 1.6 for Phone Number and Annual Income fields.

1.7 Save this section.

1.8 Run the New Mortgage Request process, verify that the user cannot exit from the Collect Borrower Information tab if the SSN, Phone Number, or Annual Income fields are blank.




Exercise 18-2: Validate Credit Scores

Scenario: ILend wants to reduce the number of errors in applications submitted by loan agents. They want the application to automatically validate the credit score value that each loan agent enters to ensure it falls within a specified range.

Requirements: Create a new flow action and section for offer confirmation and add the credit score and the first name and last name of the borrower. Create a validate rule that ensures that the loan applicant’s credit score is greater than or equal to 300 and less than or equal to 850.

How To Do It:

1. Create a flow action named ConfirmOffer in the ILend-FW-LendFW-Work class, and add two sections to it.

Step Description

1.1 In ILend-FW-LendFW-Work, create a new section named ConfirmOffer.

1.2 Open the section rule and in the first row of the layout, add the .BorrowerInfo.pyFirstName property in the Field cell.

1.3 Add the .BorrowerInfo.pyLastName property to the layout in the second Field cell in the top row.

1.4 Drag the .CreditScore property into the left Field cell in the second row.

1.5 In the layout title, enter Borrower Summary.



1.6 Drag the existing CoreSummary section below the section you just created and save your changes. When you are finished, your section should look like this:

1.7 In the same class, create a flow action named Approve. Add the section you just created to this flow action.

2. Create a Validate rule named ValidateCreditScore, in the ILend-FW-LendFW-Work class.

Step Description

2.1 In the Application Explorer, under ILend-FW-LendFW-Work, right-click Process and select New > Validate. In the Validate Name field, enter ValidateCreditScore.

2.2 Under Validate Entries, click [Property], and select .BorrowerInfo.CreditScore.

2.3 Click [expression]. In the If value is field, for the condition, enter > 850.

2.4 Click the Add new condition after this one icon to add a second condition below this one. For the second condition enter < 300.



2.5 Click the AND, and then change it to OR. This will cause the validation to fail if the number entered for credit score does not fall between 300 and 850, inclusive.

3. Create a message to display when validation fails.

Step Description

3.1 Click [Message]. In the message field, enter, Enter a credit score value greater than or equal to 300 or less than or equal to 850.

3.2 Save the rule.

4. Return to the Approve flow action and update it to use this Validate rule.

Step Description

4.1 Open the Approve flow action.

4.2 Click the Action tab. In the Validate section, in the Validation Rule field, select ValidateCreditScore.




5. Open the Underwrite Loan flow in the Flow Editor and add the Approve flow action to the connector emanating from the Loan Officer Approval Assignment. Click the draft icon to turn off the draft status.



6. Run a New Mortgage Request process to check that the flow action displays correctly and, test the validate rule.



Exercise 18-3: Validate Assets and Liabilities

Scenario: To ensure the accuracy of decisions involving the assets and liabilities of the loan applicant, loan agents should be prompted to collect values for all assets and liabilities specified by the loan applicant.

Requirements: Create a Validate rule to ensure that loan agents populate a value for each listed asset and for each liability they include in their loan application.

How To Do It:

1. Create a Validate rule named PopulatedAssetsandLiabilities in the ILend-FW-LendFW-Work class.

2. Create a validation entry to check that all listed Asset Value fields contain a value.

Step Description

2.1 Click Validate. In the drop-down list, select Validate Each.

2.2 Click [Property] and select .BorrowerInfo().Assets().AssetValue.

2.3 Check the Required? checkbox and clear the Conditions? checkbox.

2.4 Click the Add new Validate after this one icon to create a second validation entry.

2.5 Repeat steps 2.2 and 2.3 to create a validation entry for .BorrowerInfo.Liabilities().LiabilityValue.



3. Add the Validate rule to the CollectAssetsandLiabilities flow action rule.





Exercise Summary:

In Exercise 18-1, you marked as required certain fields on a section. As a result, Loan Agents now have to provide the SSN, phone number, and annual income information; they will be unable to proceed in the application until they have done this.

These changes improve process efficiency, by preventing rejection of loan requests due to incomplete information.

In Exercise 18-2, you added the ValidateCreditScore validate rule to automatically validate the credit score value entered by the Loan Agent. You replaced the existing Approve flow action in the UnderwriteLoan with the ConfirmOffer flow action, which uses this validate rule. Now, only values between 300 and 850 (inclusive) are accepted by the UnderwriteLoan flow. This change reduces the number of data entry errors made by Junior Loan Officers.

In Exercise 18-3, you required Loan Agents to specify a value for each listed asset and liability.


Student Notes:



Module 19: Declarative Rules



Exercise 19-1: Calculate a Value Using a Declare Expression

Scenario: For a mortgage application, the Loan Agent must know the ratio of the down payment being provided to the asking price of the property. If the ratio is less than 20%, the Loan Agent must inform the loan applicant that a PMI premium is required, in addition to the monthly loan payment.

Requirements: Create a Declare Expressions rule to calculate the ratio of .DownPayment to .AskingPrice.

How To Do It:

1. Quick create a single-value decimal property named PMIRatio, in ILend-FW-LendFW-Data-Loan.

2. Create a declare expression for this property in the work class.

Step Description

2.1 In the Application Explorer, in ILend-FW-LendFW-Work, right-click the PMIRatio property under LoanInfo, and select Define Expression.

2.2 Click Create. Notice the page context is automatically set while saving the rule.

2.3 Click the expression and enter .DownPayment/.AskingPrice.

3. Save the expression and test the rule by running a mortgage loan request process; note the error that occurs. Why does this happen?



4. Add a condition in the expression to avoid the divide by zero error.

Step Description

4.1 Click the Insert a Condition icon to insert a condition to evaluate before calculating the expression.

4.2 Click on the [“first value”= “second value”] field.

4.3 Enter .AskingPrice in the first value and select > in the operator field and enter 0 in the second value.

4.4 Click on the form to update the expression; this changes the last line to an otherwise statement.

4.5 Copy the expression .DownPayment/.AskingPrice from the Otherwise step to the Set step.

4.6 Click ["expression"] and enter 0 as the value to use.

5. Save the rule and unit test the expression. Enter the following values and verify that PMIRatio is calculated properly.

Down Payment Asking Price PMI Ratio 50000 250000 0.2

0 150000 0.0

100000 600000 0.17

Step Description

5.1 Click the Run button to test the expression.

5.2 In the Test page click on the Asking Price label, it refreshes and displays a text box to enter the value for the .AskingPrice property. Enter 250000, and click Update.



5.3 Enter 50000 by clicking the Down Payment Label and click Update.

5.4 Check if the PMI ratio is displayed correctly, and repeat the steps to test other values displayed in the table.

6. What are some other ways you could have calculated these expressions? What is the advantage of using a Declare Expression?



Exercise 19-2: Create a Declare Expression to Sum Items in a List

Scenario: As part of the loan request application process, the loan agents must provide a listing of assets and liabilities for the loan applicant, including the approximate value for each one. To determine whether the applicant represents a high risk of default – and automatically reject their application – the Loan Request application must sum the listed asset and liability values.

Requirements: Define both the .AssetTotal and .LiabilityTotal properties as the result of a corresponding Declare Expression:

• .AssetTotal: sum the values of the .AssetValue property for each entry in the Assets page list.

• .LiabilityTotal: sum the values of the .LiabilityValue property for each entry in the Liabilities page list.

Add a layout to the AssetsLiabilities section to display the result of each calculation.

How To Do It:

1. Under BorrowerInfo, right-click the AssetTotal property and select Define Expression.

2. In the expression, click on Value of and select Sum of in the dropdown.

3. Select .Assets().AssetValue in the value. Save the rule.

4. Repeat steps 1 – 3 to define an expression that sets the value of LiabilityTotal as the sum of all the LiabilityValue properties on the Liabilities page list.



5. Add a layout to the CollectAssetsandLiabilities section to display each total field as read-only.

Step Description

5.1 Open the CollectAssetsAndLiabilities section.

5.2 Drag a layout onto the Layout tab. Specify a Smart Layout using the double template.

5.3 Drag the AssetTotal and LiabilityTotal properties onto the 2 column Smart Layout. Place these properties in the same row.

5.4 Open the Properties panel for each field, and check the Read Only checkbox.


6. Set the AssetTotal and LiabilityTotal properties to calculate automatically.

Step Description

6.1 Open the AssetTotal and LiabilityTotal property rules.

6.2 Click the Param button located next to the HTML Property field.

6.3 Click the CalculatedValue checkbox, click OK and save the property rules.

6.4 Open the CollectAssetsAndLiabilities flow action.

6.5 On the HTML tab, enable the client-side expression calculation by checking the Enable Expression Calculation? checkbox. Save the flow action.



7. Run a New Mortgage Request process and advance to the Collect Assets and Liabilities step. Create lists of assets and liabilities, and verify that the totals change accordingly.



Exercise 19-3: Use a Declare Expression to Evaluate a Decision Tree

Scenario: The interest rate for each loan is determined by adding together three values: the base rate, an adjustment for the credit risk represented by the loan applicant, and an adjustment for the type of loan being sought. This calculation should be performed and updated dynamically, as the application is completed by the Loan Agent and processed by the Junior Loan Officer.

Requirements: Create a Declare Expression for each of the following properties: • .LoanRateAdjustment: the result of the LoanRateAdjustment

decision tree. • .RiskRateAdjustment: the result of the RiskRateAdjustment

decision tree. • .LoanInfo.Rate: the sum of the properties .BaseRate,

.LoanRateAdjustment, and .RiskRateAdjustment.

How To Do It:

1. Create a declare expression for the LoanRateAdjustment property.

2. Set the value of the property LoanRateAdjustment to be the result returned by the LoanRateAdjustment decision tree.

Step Description

2.1 Click Value of ["expression"] and select Result of Decision Tree.

2.2 Select the LoanRateAdjustment rule.

3. Repeat steps 1 and 2 to create a declare expression that sets the value of the RiskRateAdjustment property to the result of the RiskRateAdjustment decision tree.



4. Create a Declare Expression rule to calculate the interest rate.

Step Description

4.1 Under ILend-FW-LendFW-Work, under the LoanInfo embedded page, right-click the Rate property and click Define Expression.

4.2 Click ["expression"] and enter a formula to add the following three properties: .BaseRate, .RiskRateAdjustment and .LoanRateAdjustment. Refer to them as Parent.BaseRate, Parent.RiskRateAdjustment, and Parent.LoanRateAdjustment because the declare expression uses LoanInfo for the page context and these properties are saved in the top level class.

5. Modify the CoreSummary section to display all the loan properties as read-only and display the calculated rate as a percentage.

Step Description

5.1 Open the CoreSummary section defined in ILend-FW-LendFW-Work class.

5.2 Select the layout and click Delete Row, a new Smart Layout appears.

5.3 Drag the following properties to the layout: .LoanInfo.LoanType, .LoanInfo.Terms,.LoanInfo,Amount, and .LoanInfo.Rate. Set each property to display as read-only.

5.4 In the Properties panel for .LoanInfo.Rate select Percentage in the Display As field.




Exercise 19-4: Create a Constraint to Enforce Valid Data Entry

Scenario: Large mortgages have become riskier within the past few months, and the Loan Officer wants to modify the Loan Request application to limiting mortgage loans to no more than $1 million dollars.

Requirements: Create a constraint rule to restrict mortgage loans to $1 million dollars. Display a message to the loan applicant if they request a loan for a larger amount.

How To Do It:

1. In the Application Explorer, right click ILend-FW-LendFW-Work, and select New > Decision> Constraints. In the purpose field, enter ConstrainLoanAmount. Click Create.

2. Set the constraint to restrict the loan amount.

Step Description

2.1 In the first row, use the expression selector to select [property reference] has a value.

2.2 Using SmartPrompt, select the .LoanInfo.Amount property.

2.3 Next to RequireThat, click on the [“first value” = “second value”].

2.4 In the first value enter .LoanInfo.Amount.

2.5 Set the < in the Operator.

2.6 In the second value enter 1000000.



2.7 Click [Message] and enter The loan amount you have requested exceeds our allowed limit. Select .LoanInfo.Amount in the empty field. Save the rule.

3. Test the constraint by running the new mortgage request process and enter an amount exceeding a million.



Exercise Summary:

In Exercise 19-1, you created a declare expression to calculate the PMI ratio for mortgages, to determine whether the loan applicant will be responsible for paying a PMI premium, in addition to their monthly loan payment. To avoid a divide by zero error – which occurs because the asking price is $0 until the applicant provides one – you added a condition to verify that the asking price is greater than $0 before calculating the PMI ratio.

In Exercise 19-2, you created a declare expression to automatically sum up all of the asset values given for provided by the loan applicant. You also created a declare expression to sum each liability value. The loan request application automatically refreshes the display for these totals whenever the Loan Agent updates an existing asset or liability value, or adds a new entry to either list.

In Exercise 19-3, you used a declare expression to and set a property value to the result returned by a decision tree. You calculated the interest rate formula as a sum of the properties .BaseRate, .RiskRateAdjustment, and .LoanRateAdjustment. In Exercise 19-4, you created a constraints rule to restrict all mortgage requests to one million dollars or less. A Loan Agent attempting to submit a loan request for a greater amount will be informed of this limit and not be allowed to continue the loan request process unless the loan amount is reduced.



Student Notes:


Module 20: Advanced UI



Exercise 20-1: Conditionally Display a Layout Using a When Rule

Scenario: In order to process – and grant – requests for loans, iLend must collect certain basic information from the loan applicant. If the loan applicant is married or has domestic partner then information about this spouse/partner must be collected to properly calculate the risk.

Requirements: Apply a When rule to the Spouse Information layout, to display the layout only if the borrower is married or in a domestic partnership.

How To Do It:

1. Update the Spouse Information layout to display only when the MaritalStatus When rule evaluates to true.

Step Description

1.1 In the CollectBorrowerInfo section, open the Properties panel for the Spouse Information layout.

1.2 In the Smart Layout window, in the Visible When field, enter MaritalStatus.

1.3 Click OK and save the section.



2. Update the Marital Status field to refresh the BorrowerInfo section upon user selection.

Step Description 2.1 Open the Properties panel for the MaritalStatus property.

2.2 Click the magnifying glass next to the Behavior field to open the Client Event Editor.

2.3 Select the On Change event.

2.4 For Action, select Refresh this Section.

2.5 Click Save. Click OK to dismiss the Properties panel and save the section.

3. Preview the section and test that the Spouse Information layout appears when the user selects either Married or Domestic Partnership as their marital status.



Exercise 20-2: Conditionally Display Property Fields

Scenario: If the loan applicant knows the specific property they want to finance, iLend wants to collect specific details about this property. Add fields that will display only when the loan applicant has a property in mind.

Requirements: Add properties to the CollectHomeSection that will conditionally display property detail fields when the borrower knows the property they plan to finance.

How To Do It:

1. In the ILend-FW-LendFW-Work-Home class, quick create a single-value property of type TrueFalse, named CopyAddress.

2. Open the section rule CollectPropertyInfo, defined in the ILend-FW-LendFW-Work-Home class.

3. Create three Smart Layouts, titled Property Basics, Property Details, and Purchase Information.

4. Add the following properties to the corresponding layout:

Layout 1: Property Basics

Property Label Property Name Display As Do you have home in mind? .HomeInMind DisplayYesNo

Property Type .LoanInfo.PropertyType

Use current address? .CopyAddress DisplayYesNo



Layout 2: Property Details

Property Label Property Name Address .PropertyInfo.pyHomeAddress1

Address Line 2 .PropertyInfo.pyHomeAddress2

City .PropertyInfo.pyHomeCity

State .PropertyInfo.pyHomeState

Postal Code .PropertyInfo.pyHomePostalCode

Layout 3: Purchase Information

Property Label Property Name Down Payment .LoanInfo.DownPayment

Amount .LoanInfo.Amount

Asking Price .LoanInfo.AskingPrice



5. Preview the section rule to view your changes.

6. Update the section to display the Property Details layout when the value of HomeInMind is true.

Tip: When applying an event to a field containing a radio button or checkbox, use the On Click event, rather than On Change.

7. Update the section to display the Purchase Information layout when Purchase is selected from the Loan Purpose drop-down list.

8. Run the New Home Equity Loan Request or New Mortgage Request process to view the changes.




Exercise 20-3: Create a Smart Label

Scenario: When a loan applicant purchases a property, they are assessed closing costs – fees for services required by a lender to verify that the property can be legally sold. Since these fees vary, depending upon the circumstances of the sale, they are not always known until the property is officially sold. As a result, iLend’s policy is to add closing costs to the mortgage automatically, and Loan Agents must inform the loan applicants of this policy during the loan application process.

Requirements: Use a Smart Label to add a note to the .LoanAmount property field on the CollectLoanInfo section. This note should state that closing costs should not be included in the loan amount requested by the loan applicant, but rather that they will be automatically added to the loan amount at the time of sale.

How To Do It:

1. Open the CollectLoanInfo section in the ILend-FW-LendFW-Work-Home-Mortgage class.

2. Drag a Smart Label control from the Advanced Control palette onto the Amount label.

3. Specify the parameters of the Smart Label.

Step Description

3.1 Open the Properties panel for the Smart Label.

3.2 Next to the Display As field, click the Display Formats magnifying glass.

3.3 For Label, enter Loan Amount.

3.4 For SectionName, enter LoanAmountPopup.



3.5 For HeaderText, enter Loan Amount and Closing Costs.

4. Create the content of the Smart Label.

Step Description

4.1 Create a new section named LoanAmountPopup in ILend-FW-LendFW-Work-Home-Mortgage

4.2 Replace the smart label layout with a free form layout of 1 columns x 2 row.

4.3 In the top cell, enter The requested loan amount should not include an estimate for closing costs.

4.4 In the bottom cell, enter Closing costs will be determined separately, prior to the closing date.



5. Save both sections and preview the CollectLoanInfo section. In the preview, hover over the label to see the entered text.



Exercise 20-4: Create a Dynamic Select Control

Scenario: For mortgages, the terms that can be offered depend upon the purpose of the loan; for example, adjustable-rate loans can only be offered for mortgages to purchase a property. When Loan Agents select a purpose for the applicant’s mortgage, the options available for loan terms should be restricted to only the appropriate choices.

Requirements: Configure the .LoanPurpose property field on the CollectLoanInfo section for the Mortgage work type as a Dynamic Select, populated by the HomeLoans data table you created earlier.

How To Do It:

1. Open the CollectLoanInfo section in the ILend-FW-LendFW-Work-Home-Mortgage class.

2. Open the Properties panel for the LoanPurpose cell. In the Display As field, select DynamicSelect.

3. Configure the Dynamic Select control to populate using the HomeLoans data table.

Step Description

3.1 Click the Display Formats magnifying glass next to Dynamic Select.

3.2 Select List View as the method for generating the dynamic select.

3.3 In the Applies To field, select ILend-FW-LendFW-Data-HomeLoans.

3.4 In the View Purpose field, select DataTableClassEditor.

3.5 Enter Is this a purchase or refinance? as the Default Caption.



3.6 For Property for Option Display and Property for Option Value, select pyLabel.

3.7 Click OK to close the Param Window.

4. Save the CollectLoanInfo section. Preview the section to see the choices.

5. Run the mortgage loan request process on the Collect Loan Information form. Verify that the drop-down display defaults to “Is this a purchase or refinance?”, and that the Purchase and Refinance options are available.



Note: The options listed in the Dynamic Select control you created in this exercise are read directly from the data table. To create the list of loan terms, you must create an activity to filter data from a data table. You will learn how to write such an activity in Module 21: Advanced Activities.

Taking It Further: If you have time, try the following exercises: Exercise B5: Customize the Appearance of an Application with the Branding Wizard Refer to PDN article PRKB25641: How to use the Application skin wizard to create a new skin.




Exercise Summary:

In Exercises 20-1 and 20-2, you used Visible When conditions to control the display of both layouts and individual cells. In a section, Visible When conditions can be applied to the whole section, to a specific layout, or to an individual cell. This allows you to hide content that is not needed – such as information about a spouse/partner for single applicants – or delay the presentation of content until a specific condition is met. You also controlled the collection of information according to the loan type and loan purpose, eliminating the need for additional sections and validation rules.

In Exercises 20-3, you created a Smart Label to inform applicants not to add closing costs into the loan amount. By using a Smart Label, Loan Agents will have this additional information available for display when needed, without cluttering the UI with additional fields.

In Exercise 20-4, you used a Dynamic Select to display content that changes over time. In previous exercises, you used a PromptSelect to read values from the property definition and display them in a drop-down list. When the options in a list change, you may want to dynamically generate the list at runtime. In this example, the drop-down list options are generated when the section is displayed, by querying a data table and reading its current values.


Student Notes:



Module 21: Advanced Activities



Exercise 21-1: Create an Activity with a Precondition and a Transition

Scenario: When applying for a home equity loan or mortgage, Loan Agents must collect the address of the property if the applicant knows this information. For home equity loan applications and mortgage refinance applications, this address is generally the same as the loan applicant’s current address. Rather than re-enter this information manually, Loan Agents have requested functionality to automatically copy this information from the Borrower Information form.

Requirements: • Create an activity called CopyAddressData, top copy the values of the following properties from the .BorrowerInfo property page to the .PropertyInfo property page:

• .pyHomeAddress1 • .pyHomeAddress2 • .pyHomeCity • .pyHomeState • .pyHomePostalCode • Use a precondition to test whether the Loan Agent as checked

the checkbox for the .CopyAddress property. Use a transition to direct activity processing to a second step to clear the address fields if the Loan Agent clears the checkbox.

How To Do It:

1. Create an activity called CopyAddressData in the ILend-FW-LendFW-Work-Home class.

2. In the first step, select Property-Set as the method.



3. Expand the method, and enter the following properties.

PropertiesName PropertiesValue .PropertyInfo.pyHomeAddress1 .BorrowerInfo.pyHomeAddress1

.PropertyInfo.pyHomeAddress2 .BorrowerInfo.pyHomeAddress2

.PropertyInfo.pyHomeCity .BorrowerInfo.pyHomeCity

.PropertyInfo.pyHomeState .BorrowerInfo.pyHomeState

.PropertyInfo.pyHomePostalCode .BorrowerInfo.pyHomePostalCode

4. Create a precondition to jump to the second step if the borrower decides not to copy their current address.

Step Description

4.1 Expand the precondition for the first step.

4.2 Click the Enabled? checkbox to activate the precondition.

4.3 In the When field, enter .CopyAddress.

4.4 In the if True column, select Continue Whens.

4.5 In the if False column, select Jump to Later Step.

4.6 In the False Param column, enter Undo.

5. Create a transition step to exit the activity if the borrower has copied their address.

Step Description

5.1 Expand the transition for the first step.

5.2 Click the Enabled? checkbox to activate the transition.

5.3 In the When field, enter .CopyAddress.

5.4 In the if True column, select Exit Activity.

5.5 In the if False column, select Continue Whens.



6. Add a second step to the activity, to perform a Property-Set to clear the address fields. Label the step Undo.

Step Description

6.1 Click the Add a Row icon to add a second row to the activity.

6.2 In the Label field, enter Undo.

6.3 In the Method field, select Property-Set.

7. Expand the method and set all the properties listed in step 3 to null (enter “” in the PropertiesValue field).

8. Call the activity from the CopyAddress property displayed in the CollectPropertyInfo section.

Step Description

8.1 Open the CollectPropertyInfo section defined in ILend-FW-LendFW-Work-Home.

8.2 In the Properties panel for CopyAddress, click the magnifying glass icon next to the Behavior field.

8.3 From the Event drop-down list, select On Click. From the Action field, select Refresh this section. In the Activity field, select CopyAddressData

8.4 Click Save, then click OK to dismiss the Properties panel. Save the section.

9 Test the activity by running a new mortgage request process.




Exercise 21-2: Create an Activity to Populate a Dynamic Select

Scenario: Unlike a home equity loan, the terms offered for a mortgage depend on whether the mortgage is intended to purchase a home, or to refinance an existing mortgage. As a result, the options presented to the Loan Agent must be filtered, to prevent the submission of incorrect applications.

Requirements: • Create a dynamic select control listing the allowed loan terms for purchase and refinance mortgage requests. Create an activity to filter the contents of the data table to populate the results of this dynamic select, and refresh the section whenever the LoanPurpose selection changes to ensure that the dynamic select options are consistent with the selected purpose.

How To Do It:

1. In ILend-FW-LendFW-Work-Home-Mortgage class, create an activity named GetTerms.

2. Create a step to find the list view associated with the HomeLoans data table.

Step Description

2.1 On the Steps tab, in the first step select Obj-List-View as the method,

2.2 Expand the method step and, for the obj class, enter ILend-FW-LendFW-Data-HomeLoans.

2.3 For ListView, select DataTableClassEditor and for the owner, enter ALL.

3. Filter the result set.

Step Description

3.1 In the second step, for the method step, select Obj-Filter.

3.2 Expand method step, for ListPage, enter pyListViewContentPage.



3.3 For ResultClass, select ILend-FW-LendFW-Data-HomeLoans and for the When rule enter IsPurposeMatched.

4. Create a When rule to filter loan products that match the specified purpose.

Step Description

4.1 Click the When rule section and click the open icon located in the Method Obj-Filter step to create a new when rule named IsPurposeMatched.

4.2 Click the Pages & Classes tab.

In Page Name, enter pyWorkPage to add a page name. In the Class field, select in ILend-FW-LendFW-Work-Home.

4.3 In the Conditions tab, enter the condition .pyLabel = pyWorkPage.LoanPurpose.

4.4 Save the when rule.

5. Show the filtered results.

Step Description

5.1 Go back to the activity and in the third step, for Method, select Show-Page.

5.2 For the third step, for Step Page, enter pyListViewContentPage.

5.3 Click on the Security tab and check the May start? checkbox.

6. Save the rule.

7. Configure the LoanPurpose field to refresh the section when you change the selection.

Step Description

7.1 Open the CollectLoanInfo Section defined in ILend-FW-LendFW-Work-Home-Mortgage and select the LoanPurpose Dynamic Select.

7.2 Click the magnifying class next to Behavior.

7.3 In the Client Event Editor, for Event, select OnChange and for Action, select Refresh this Section. Also, enable the Activate Input Formatting checkbox to activate client-side validation.



7.4 Click Save to close the Client Event Editor and return to the Properties panel.

8. Configure the Terms as a Dynamic Select.

Step Description

8.1 Click the Terms field to open the Properties panel.

8.2 Set the Display As field to DynamicSelect and open the Param Window.

8.3 For Method for Generating the Dynamic Select, select Activity.

8.4 For Activity Information, select the following:

Applies To: ILend-FW-LendFW-Work-Home-Mortgage

Activity Name: GetTerms

Class of Returned Results: ILend-FW-LendFW-Data-HomeLoans

8.5 In the Common Dynamic Select Information, enter the following:

Select ID: LoanTerms

Default Caption: Select Loan Terms ...

Property for Option Display: LoanTerms

Property for Option Value: LoanTerms

8.6 Clear the Enable Caching checkbox. Click OK in both the Properties panel and in Parameter Dialog window.

9. Save the section.

10. Run the mortgage process. Verify that the choices presented in the Terms dynamic select correspond to the allowed terms for the specified Loan Purpose.

Taking It Further: If you have time, try the following exercises: Exercise B6: Create a Cascading Dynamic Select Control, which restricts the choices in a dynamic select control based on the selection made in another dynamic select control. Refer to PDN article PRKB25898: How to configure Cascading Dynamic Selects for instructions on how to create a cascading dynamic select.



Exercise 21-3: Create an Activity to Write to a Data Table

Scenario: Once an applicant has been approved for a loan, their contact information – name, address, phone number, and email address – should be copied to a separate customer data record, separate from their loan application. This allows other applications – such as a payment-management system – to access this information.

Requirements: Create an activity to copy the values of the following properties to the Customers data table.

• .BorrowerInfo.pyFirstName • .BorrowerInfo.pyLastName • .BorrowerInfo.pyHomeAddress1 • .BorrowerInfo.pyHomeAddress2 • .BorrowerInfo.pyHomeCity • .BorrowerInfo.pyHomeState • .BorrowerInfo.pyHomePostalCode • .BorrowerInfo.pyHomePhone • .BorrowerInfo.pyEmail1 • .BorrowerInfo.pySSN

How To Do It:

1. Create an activity named CreateCustomer in ILend-FW-LendFW-Work class.

2. On the Pages & Classes tab, create a page named CustomerList, for Class select Code-Pega-List.



3. On the Steps tab, create a step to query the current customer list and return a list of the current records.

Step Description

3.1 In the first step, select Obj-Browse as the method.

3.2 Expand the Method step and for PageName - the page to write to the clipboard - enter CustomerList.

3.3 For ObjClass, select ILend-FW-LendFW-Data-Customers (this is the class to browse).

3.4 Select .ID as the field, for Condition, select Value Only, and enable the Select checkbox.

4. In the second step, enter Page-New of class newCustomer. Define newCustomer of type ILend-FW-LendFW-Data-Customers in the Pages and Classes tab.

5. Use the length of the results list to determine the ID for the new record.

Step Description

5.1 In the third step, use the Property-Set method. In the Step Page, type newCustomer.

5.2 Enter .ID as the Property Name and enter CustomerList.pxResultCount+1 as the Property Value.

6. Copy the borrower's information to the new customer record.

Step Description

6.1 In the fourth step, use the Property-Set method. In the Step Page, type newCustomer.

6.2 Expand Method Step and enter

Properties Name : Properties Value .FirstName: Primary.BorrowerInfo.pyFirstName

.LastName: Primary.BorrowerInfo.pyLastName

.AddressLine1: Primary.BorrowerInfo.pyHomeAddress1



.AddressLine2: Primary.BorrowerInfo..pyHomeAddress2

.City: Primary.BorrowerInfo.pyHomeCity

.State: Primary.BorrowerInfo.pyHomeState

.PostalCode: Primary.BorrowerInfo.pyHomePostalCode

.Phone: Primary.BorrowerInfo.pyHomePhone

.Email: Primary.BorrowerInfo.pyEmail1

.SSN: Primary.BorrowerInfo.pySSN

7. In the next step use Obj-Save as the Method Name, enter newCustomer as the Step Page name and expand Method Step, click the checkbox Write Now. This method writes the data to the data table.

8. Delete the temporary pages you created in the activity.

Step Description

8.1 Use the Page-Remove method.

8.2 Expand the Method Step and, in the Page field, enter CustomerList. Also, add another row and enter newCustomer. Save the activity.

9. Add the activity as a utility in the UnderWriteLoan flow and add the utility shape after the Resolved-Completed utility shape.

10. Why doesn’t the activity name appear in the drop-down list in the flow rule?

11 Run the New Mortgage Request process and set values to get an approved quote and see if the customer record gets added to the Customers data table.




Taking It Further: If you have time, try the following exercise: Exercise B7: Create a Declare Page to Cache External Data Refer to the PDN article PRKB25039 How to create a declare pages rule for instructions on how to create and populate a Declare Page.



Exercise Summary:

In Exercise 21-1, you created an activity with both a precondition and a transition. You used these to execute different steps, depending on when the activity was called.

In Exercise 21-2, you created an activity to populate options in a Dynamic Select control. This activity filters the results returned from the data table, and displays a list containing only allowed options. You can also use activities to read from an external database, rather than a data table.

In Exercise 21-3, you learned how to write data to a data table. This activity introduced the commonly used methods Obj-Browse and Obj-Save, which eliminate the need to write SQL queries to save or read data from the data tables. The last step used the Page-Remove method to delete all the temporary pages created as part of the activity. Doing so frees up memory, as these pages are not used outside the context of this activity.


Student Notes:



Module 22: Routing and SLA



Exercise 22-1: Create a Work Basket for Loan Approvals

Scenario: Create a Workbasket to store the work items that need Underwriter approval. The work items in this Workbasket will then be routed to a Junior Loan Officer for approval.

Requirements: Create a workbasket and a work group for the iLend Underwriter work group.

How to Do It:

1. Create the LoanUnderwriting work group.

Step Description

1.1 In the Application Explorer, right-click ILend-FW-LendFW-Work and New-> Organization-> Work Group.

1.2 In the Work Group Name, enter LoanUnderwriting, and click Create.

2. Map the work group to a Workbasket.

Step Description

2.1 On the Work Group tab, for Manager, select [email protected].

2.2 For Default Workbasket, select LoansWB and click the Open icon to create the Workbasket.

2.3 Click Create.

3. Configure LoansWB Workbasket.

Step Description

3.1 For Name, select iLend.com.

3.2 For Division, select Lending.



3.3 For Unit, select Underwriting.

3.4 For Work Group, select Default.

3.5 Save the workbasket rule.

3.6 Go back to the work group rule and save the Workgroup rule.

3.7 Go back to the work basket and change Work Group to use LoanUnderwriting.

3.8 Save the Workbasket rule again.



Exercise 22-2: Route Loan applications to a Workbasket

Scenario: Use a Workbasket to route work assignments. Route the loan request applications to the Underwriter workbasket so that the loan officers who work in Underwriting work group can view and process the work items.

Requirements: Add the router to the UnderwriteLoan flow to route the loan application assignments to the LoansWB workbasket.

How to Do It:

1. Route loan applications to the LoansWB workbasket.

Step Description

1.1 Open the UnderwriteLoan flow. Drag a router shape onto the Flow Editor workspace.

1.2 Connect the router to the Approve Application assignment.

1.3 In the Router Shape Properties panel, for Rule select ToWorkBasket, and click Apply.

1.4 For Workbasket name, select LoansWB.

1.5 Edit the Approve Application assignment properties and change the rule to use a WorkBasket, instead of a WorkList, to route work. Click Apply.

2. Add a router shape to the Loan Officer Approval Assignment. Select ToWorkGroupManager as the rule in the router properties.

3. Run Mortgage Loan request process with the following data and verify that the loan request is correctly routed for approval. (Enter AssetTotal greater than LiabilityTotal).

Property Value Income 220000

Loan Amount 550000



Property Type Single Family Detached




Exercise 22-3: Create a Service Level to Enforce Deadline on Approvals

Scenario: ILend wants to improve the Loan Agents’ response time for processing a loan application and responding to loan applicants. You must set service levels to ensure that the loan officers work on the loan application within the specified timelines.

Requirements: Add a Service Level (SLA) to the Underwriter assignment and set Goal and Deadline timelines.

How to Do It:

1. Add a service level named ApproveApplication to enforce a deadline on Approvals.

Step Description

1.1 Open the UnderwriteLoan Process in the flow editor.

1.2 In the Approve Application assignment, in the Service Level Field, enter ApproveAssignment.

1.3 Click the Open icon to create the ApproveApplication Service Level.

2. Specify the terms of the Service Level.

Step Description

2.1 Set the Initial Urgency to 10.



2.2 For Goal, enter 1 for minutes (MM), for Urgency, enter 20. Also check Business Days.

2.3 For Deadline, enter 2 for minutes, for Urgency enter 50; also check Business Days.

2.4 For Passed Deadline, enter 3 for minutes, also check the Business Days.

2.5 Save the Service Level and the flow.

3. Run Mortgage Loan request process, and verify that the urgency increments as specified in the Service Level.

4. Return to the service level rule and select ActionTransferToManager as the Escalation Activity in the Passed Deadline portion of the rule form. Save the rule.

5. Run Mortgage Loan request process. Verify that the application is routed to the work group manager ([email protected]) after the specified interval (3 minutes).



Taking It Further: If you have time, try the following exercises: Exercise B8: Create an SLA for a flow, which routes the pending assignment to a workbasket and then use an SLA to reassign to an operator for processing the application.




Exercise Summary:

In Exercise 22-1, you created a work group and a workbasket to enable routing decisions for a manager and their team. This feature is useful when different team members can handle the same assignment, based on criteria such as geographical region, skill level, language, etc. In cases like this, each work group can have its own workbasket. The work items are then routed to appropriate workbasket using the specified criteria.

In Exercise 22-2, you added a Router shape to route work items to a workbasket. A router can also use a decision tree, a decision table or other rule to decide which workbasket to select.

In Exercise 22-3, you created a service level rule used to assign goal, deadline and passed deadline timelines. Escalation rules can be defined at each interval. Urgency is displayed in the worklist, with higher urgency work items appearing at the top of the worklist. In some situations urgency can play a significant role in deciding which work item in the workbasket will be assigned first.


Student Notes:



Module 23: Development Performance Tools



Exercise 23-1: Run Preflight and View Warnings

Scenario: To ensure that the home equity and mortgage loan processes are designed following all the best practice guidelines and the guardrails, architects and designers working in the project must periodically test for warnings using the Preflight tool.

Requirements: The Preflight tool identifies all the performance warnings, browser warnings, rule warnings and accessibility warnings if applicable on the rules written in the application. Run the Preflight tool, take a closer look at all of the warnings and consider how they can be addressed.

How to Do It:

1. Click the Pega button and select Application > Tools > Preflight to access the Preflight tool.

2. The Preflight tool checks all the rules and provides a report on all the warnings that exist.



3. Click each link to review the warnings returned by the Preflight tool.

Step Description

3.1 Download High Priority warnings- It lets you to view all the rules marked as high priority warnings. It gives you the option of viewing it in browser or download to the local file system. The download option pulls the list into an excel sheet.

3.2 All Warnings by Rule Type - Provides a drilldown list of all the rules that have warnings, grouped by rule type. You can drill down further by clicking on the rule type to see the name of the rule, you can also modify the criteria to add or remove the RuleSets. The rules can also be exported to Excel.

3.3 Performance Warnings by Rule Type – Provides a drilldown list of rules that have performance warnings, grouped by Rule Type.



3.4 Percent of Warnings by Rule Type – Provides a drilldown list of rules that have warnings, grouped by Rule Type. It also includes the percentage of rules that have warnings in that rule type, for example, 9% of class rules have warnings and 100% of listview rules have warnings.

3.5 Pie chart of Warnings by severity – Provides a pie chart of all the warnings classified into the severity levels (Severity 1 to Severity 4). You can drill down further by clicking on the severity level to see the list of rules.

3.6 Browser Compatibility Report - Provides the list of rules that are not compatible with all browsers.

3.7 Accessibility Report – Provides information for applications that have the accessibility feature turned on.

4. Review the Warnings closely.

Step Description

4.1 Click the All Warnings by Rule Type link.



4.2 In the report click on Class. This opens a new page listing all the class rules with warnings.

4.3 The warning displays “Saves to pr_other”. What does this message mean? How can you fix this warning?

4.4 Then click on Listview to see the warning message. What does this message mean? How can you fix the problem that is generating this warning? Why is this warning performance-related?



Exercise Summary:

In Exercise 23-1, you used the Preflight tool, and viewed the different reports generated by this tool. You learned how to drill down to the rules that have warnings. You must run the Preflight tool periodically during your PRPC projects in order to discover the performance warnings, best practice violations, and all the guardrails you should follow.


Student Notes:



Module 24: Documenting the Application



Exercise 24-1: Run the Application Documentation Wizard

Scenario: iLend’s Internal Audit department requires a MS Word document that thoroughly documents the Loan Request application that you’ve developed. This hand-off document will be used by others on the implementation team and by future developers, so it must list all of the work types, use cases, and rules associated with your application. For an actual implementation project, you would have carefully entered detailed information on the History tab of each rule that you created and these comments would be included when the Application Documentation wizard is run.

Requirements: Run the Application Documentation wizard to generate a document using the standard templates.

How To Do It:

1. Click the Pega (button) > Application > Tools > Document to launch the Application Documentation wizard.

2. Complete the wizard to create the document.

Step Description

2.1 Accept defaults in the first step (use ApplicationDocument as the template) and click Next. Note that there is also another standard template called Project Document.

2.2 Leave all RuleSets checked and click Next.

2.3 Leave all work types checked and click Next.



2.4 Select Full Application Documentation from the drop-down list in the detail level.

2.5 Continue clicking Next in the next three screens without modifying any values.

2.6 In the last step, click the Word Create Document icon.

2.7 This launches a new window and opens a Word document; wait until the entire document finishes loading all of the content. Once the document is generated it can be modified and resaved to the local file system.




Exercise 24-2: Export an Application

Scenario: In order to deploy the Loan Request application to iLend’s QA and production environments, you must create a product rule which will allow the Loan Request application to be exported.

Requirements: Review the existing product rule to understand how it is used to export the application’s associated rules.

How to Do It:

1. Search for the LendingApp product rule.

2. Open the rule.



3. Under the Applications to Include section, the product rule lists both the framework and the specialized application. The Document wizard will zip all of the RuleSets included in the application RuleSets.

Step Description

3.1 Under the RuleSets to Include section is an optional list that of specific RuleSet instances that need to be moved.

3.2 Under the Class Instances to Include section is a list of all the data class instances to include in the zip file. In our case, this must include all the instances from the Home Loans data table.

3.3 Under the Individual Instances to Include section are all the specific data instances that belong to a class. To add entries, you can select a class like “Data-Admin-WorkGroup” and then click Query.

3.4 This opens a new window and lists all the data instances applicable for that data class. You can then select the instances that are applicable for our application, in our example, LOANUNDERWRITING, and then click OK.

3.5 Another way to do this is to include Data-Admin-WorkGroup in the Class Instances to Include, and then create a when rule that includes a filter for this specific instance.



4. Click Create Zip File, located in the end of the rule form.

5. Enter LendingApp as the name of the product zip file and click OK.

6. Click on the hyperlink to save the file locally.




Exercise Summary:

In Exercise 24-1, you created the application document. The documentation feature is very useful and the document can be generated at any stage of the project (Elaboration, Construction, Transition, etc.). The document uses the Short Description field in each rule, which is why it’s strongly recommended that you provide meaningful short descriptions in every implementation project. Note that although you used a standard document template when creating your application document, you can create a customized template simply by creating a new template rule.

In Exercise 24-2, you ran the product rule and created a zip file of your application’s RuleSets. You saw that the product rule allows you to include applications instead of specifying each associated RuleSets one-by-one. All four groups in the product rule are optional, so a product rule can be created with whatever RuleSets are needed. If you need to move a specific RuleSet, then you can use the RuleSets to Include option.



Student Notes:


Module 25: Wrap Up

Appendix A: Exercise Solutions

Pegasystems Inc. Fast Track to PRPC A-1


Exercise 11-4: Create Embedded Properties

How to Do It:

1. Create a Page property named BorrowerInfo in the ILend-FW-LendFW-Work class, to collect borrower information.

Step Description

1.1 In the Application Explorer, under the ILend-FW-LendFW-Work class, expand the Data Model category.

1.2 Right-click Property and click New.

1.3 In the New Rule dialog, in the Property Name field, enter BorrowerInfo.

1.4 Click Create.


1.6 In the Page Class field, select the ILend-FW-LendFW-Data-Borrower class.


2. Repeat step 1 to create the following page properties:

Name Property Class Property Mode Page Class Loan Info ILend-FW-LendFW-Work Page ILend-FW-LendFW-Data-Loan

Property Info ILend-FW-LendFW-Home Page ILend-FW-LendFW-Data-Home

Step Description

2.1 In the Application Explorer, under the ILend-FW-LendFW-Work class, right-click the


A-2 Fast Track to PRPC Pegasystems Inc.

Data Model rule category and click New > Property.

2.2 In the New Rule dialog, in the Property Name field, enter LoanInfo.

2.3 Click Create.


2.5 In the Page Class field, select the ILend-FW-LendFW-Data-Loan class.


2.7 In the Application Explorer, expand the ILend-FW-LendFW-Work-Home class, right-click the Data Model rule category, and click New > Property.

2.8 In the New Rule dialog, in the Property Name field, enter PropertyInfo.

2.9 Click Create.


2.11 In the Page Class field, select the ILend-FW-LendFW-Data-Home class.


3. Switch the Application Explorer to the ILend-FW-LendFW-Data- class.

Step Description

3.1 In the Application Explorer, using the Class Selector, switch the class to the ILend-FW-LendFW-Data- class.



4. Using the Define Properties wizard, in the ILend-FW-LendFW-Data-Borrower class, create the following page properties. Click Finish at the first step to complete the wizard.

Description Mode Type Assets Page List ILend-FW-LendFW-Data-Borrower-Assets

Liabilities Page List ILend-FW-LendFW-Data-Borrower-Liabilities

Spouse Page ILend-FW-LendFW-Data-Borrower-Spouse

5. Using the Define Properties wizard, create the following properties in the appropriate classes as listed. Click Next at the first step to enter the Display As and Details information.

Description Type Display As Details

Class Name: ILend- FW-LendFW-Data- Borrower Asset Total Decimal TextBox CurrencyAmount

Credit Score Integer TextBox Default

Date Of Birth Date TextBox Date

Income Decimal TextBox CurrencyAmount

Liability Total Decimal TextBox CurrencyAmount

Marital Status Text DropDown Single Married Domestic Partnership Divorced

Class Name: ILend- FW-LendFW-Data- Borrower-Assets Asset Type Text DropDown Checking account

Savings account Investment account Stocks Bonds Retirement account Property

Asset Value Decimal TextBox CurrencyAmount

Class Name: ILend- FW-LendFW-Data- Borrower-Liabilities



Liability Type Text DropDown Credit card Home equity loan Mortgage Personal loan Vehicle loan

Liability Value Decimal TextBox CurrencyAmount

Class Name: ILend- FW-LendFW-Data- Home Appraised Date Date TextBox Date-Calendar

Appraised Value Decimal TextBox CurrencyAmount

Home In Mind TrueFalse

Class Name: ILend- FW-LendFW-Data- Loan Amount Decimal TextBox CurrencyAmount

Down Payment Decimal TextBox CurrencyAmount

Loan Purpose Text TextArea Default

Loan Type Text DropDown Auto Loan Home Equity Loan Mortgage

Property Type Text DropDown Single Family Detached Townhouse Condominium Multi-family Dwelling

PMI Premium Decimal TextBox Currency Amount

Rate Decimal TextBox Default

Terms Text TextArea Default



Exercise 11-5: Create a Data Table

How to Do It:

1. Using the Data Table wizard, create a data table of mortgage products.

Step Description




ILend-FW-LendFW-Data-HomeLoans.

1.4 In the Description field, enter Listing of home loan products.




1.8 In the empty row, in the Name field, enter LoanTerms. In the Label field, enter



Loan Terms. In the Type field, select Text.

1.9 Click Generate.

2. Populate the data table with the following mortgage loan products.

ID Label Loan Terms 1 Purchase 30 years, 3/1 adjustable

2 Purchase 30 years, 5/1 adjustable







Step Description

2.1 Click the List Editor link.

2.2 Click the Add a Row icon to create an empty row.

2.3 In the ID field, enter 1.

2.4 In the Label field, enter Purchase.

2.5 In the Loan Terms field, enter 30 years, 3/1 adjustable.



2.6 Click the Add a Row icon to create additional rows, and enter the remaining values in the preceding table.

2.7 When you finish, close the window and return to the Data Tables Landing Page. Verify that the table now contains 6 rows.

3. Create a second data table. In the Class Name field, enter ILend-FW-LendFW-Data-Customers. In the Description field, enter Customer Data. In the Derived from field, select ILend-FW-LendFW-Data-.

Step Description




ILend-FW-LendFW-Data-Customer.

3.4 In the Description field, enter Customer Data.




4. Specify ID as the Key property for the data table.

Step Description


5. Add the following properties to the table, and click Generate.

Name Type FirstName Text

LastName Text

AddressLine1 Text

AddressLine2 Text

City Text

State Text

PostalCode Text

Phone Text

Email Text

SSN Text

Step Description


5.2 In the empty row, in the Name field, enter FirstName. In the Label field, enter First Name. In the Type field, select Text.

5.3 Continue Click the Add a Row icon to create additional rows and enter the fields as shown in the table above.



6. Close the Data Table wizard and return to the Data Tables Landing Page. You should see two data tables listed.

Note: The Customers table should contain no rows of data. You will populate this data table in a future exercise.

7. In the ILend-FW-LendFW-Work class, create a new Page List property named Customer. For Page Class, select ILend-FW-LendFW-Data-Customers.

Step Description

7.1 In the Application Explorer, under the ILend-FW-LendFW-Work class, expand the Data Model category. Right-click Property and click New.

7.2 In the New Rule dialog, in the Property Name field, enter Customer. Click Create.


7.4 In the Page Class field, select the ILend-FW-LendFW-Data-Customers class.




Exercise 15-2: Create a Decision Table to Automatically Approve or Reject Work

How to Do It:

1. Create a decision table named IsTooRisky, in the ILend-FW-LendFW-Work class.

Step Description

1.1 In the Application Explorer, right-click ILend-FW-LendFW-Work, and select New > Decision > Decision Table.

1.2 In the Purpose field, enter IsTooRisky and click Create.

2. Create two outcomes for the table: TooRisky and NotTooRisky.

Step Description

2.1 Click the Results tab.

2.2 In the first row under Allowed Results enter TooRisky

2.3 Click the Add a Row icon to create a new row, and enter NotTooRisky as a second allowed result.

3. Populate the table with the conditions

Step Description

3.1 Click the Table tab.

3.2 Click the empty header column under Conditions of the table.



3.3 In the Property field, using the SmartPrompt, select .LoanInfo.LoanType

3.4 From the Use Operator drop-down list, select “=”

3.5 Click on the cell under the newly created property, next to if.

3.6 Click the Insert Column After icon to create an additional column.

3.7 Click the empty header column next to LoanType in the Conditions.

3.8 Select .LoanInfo.Amount as the property to test against.

3.9 Select > as the operator for the test

3.10 Repeat 3.3 to 3.9 to add another property .BorrowerInfo.AssetTotal and Select < as the operator for the test

3.11 Click one of the table cells under the conditions next to the if.

3.12 In the first row, under AssetTotal column, enter .BorrowerInfo.LiabilityTotal. Enter TooRisky in the cell under actions column.

3.13 In the second row, select HomeEquityLoan in the cell under LoanType Column, enter (.BorrowerInfo.Income+.BorrowerInfo.SpouseInfo.Income)*1.3 in the cell under Amount column. Enter TooRisky in the cell under actions column.

3.14 In the third row, select Mortgage in the cell under LoanType Column, enter (.BorrowerInfo.Income+.BorrowerInfo.SpouseInfo.Income)*3 in the cell under Amount column. Enter TooRisky in the cell under actions column.

3.15 In the otherwise row, enter NotTooRisky in the cell under actions column.



4. Save the decision table.

5. Test the logic of the decision table, using the following scenarios:

Loan Type Amount Borrower Income

Spouse Income

Asset Total

Liability Total

Result



Home Equity Loan 50000 30000 3000 10000 5000 TooRisky

10000 50000 TooRisky

Mortgage 300000 40000 60000 10000 5000 NotTooRisky

Mortgage 300000 60000 20000 10000 5000 TooRisky

6. Add the decision table to the MortgageMainFlow rule.

Step Description

6.1. Disconnect the Connector emanating from the CollectInfoMortgage flow shape from the Review Conditional Offer assignment

6.2. Drag the IsTooRisky decision table onto the Connector emanating from the CollectInfoMortgage flow shape.

6.3. Connect the TooRisky Connector to the End shape.

6.4. Connect the NotTooRisky Connector to the Review Conditional Offer flow shape



‘



7. Repeat step 6 to add the decision table to HomeEquityLoan flow, connecting the NotTooRisky connector to the Review Conditional Offer assignment.

8. Run both Mortgage and Home Equity loan process to test the decision tables.



Exercise 15-3: Use Decision Trees to Define Variables Used in Calculations

How To Do It:

1. Create a decision tree named LoanRateAdjustment in the ILend-FW-LendFW-Work class.

Step Description 1.1 In the Application Explorer, right-click the ILend-FW-LendFW-Work class and select

New > Decision > Decision Tree.

1.2 In the Purpose field, enter LoanRateAdjustment, and click Create.

2. Create a decision tree branch to calculate loan rate adjustments for Home Equity loans.

Step Description 2.1 In the first line, click the ["first value" = "second value"] link.

2.2 In the first field, select .LoanInfo.LoanType

2.3 In the second field, select Home Equity Loan.

2.4 Click return and select continue from the drop-down list

2.5 In the sub-condition that appears, click the ["first value" = "second value"] link

2.6 In the first field, select .LoanInfo.Terms

2.7 In the second field, enter "5-year, fixed rate"

2.8 Click result, and enter .0575 in the field

2.9 Click the Add Row After icon to create a new sub-condition, and set this sub-condition to return .06 for a "10-year, fixed rate" loan.

2.10 Add a third row for the remaining loan term. Change the return to otherwise, and return .0650.



3. Create a third branch in the tree to return the rate adjustments for mortgages:

Step Description

3.1. Click on otherwise row, it highlights the whole row.

3.2. Click the Add Row Before icon to create a new branch, to add conditions

3.3. Click the ["first value" = "second value"] link. In the first field, select .LoanInfo.LoanType.

3.4. In the second field, select Mortgage.

3.5. Click return and select continue from the drop-down list

3.6. Repeat steps 3.2 to 3.4, to enter a new condition, .LoanInfo.Purpose=”Purchase”.

3.7. Click return and select continue from the drop-down list

3.8. Repeat steps 3.2 to 3.4, to enter a new condition, .LoanInfo.Terms="15 years, fixed rate".

3.9. Click result after the return and enter 0.01125.

3.10. Click the Add Row After icon to create a new sub-condition, and enter a new condition to return .0150 for a "30 years, fixed rate" loan.

3.11. Click on if label displayed before the .LoanInfo.LoanPurpose=”Purchase” and click the Add Row After icon.

3.12. In the new branch, enter a new condition, .LoanInfo.Purpose= "Refinance”

3.13. Click return and select continue from the drop-down list.

3.14. Repeat steps 3.2 to 3.4, to enter a new condition, .LoanInfo.Terms = "10



years, fixed rate". Click result after the return and enter 0.0125.

3.15. Repeat steps 3.2 to 3.4, to enter a new condition, .LoanInfo.Terms = "20 years, fixed rate". Click result after the return and enter 0.01625.

3.16. Click the Add Row After icon to create a new sub-condition, Click return and select otherwise from the drop-down list and enter 0.0250 in the result.

4. Save the decision tree. Unit test the tree by supplying various values to test conditions.

5. Create a decision tree named RiskRateAdjustment in the ILend-FW-LendFW-Work class, to calculate the rate adjustment based upon the borrower’s credit score, using the following values:

Borrower’s Credit Score Rate Adjustment 0 0

751 and above 0.0025



701 – 750 0.0050

651 – 700 0.0075

551 – 650 0.0100

550 and below 0.0250

Tip: If your decision tree evaluates only one property, you can create a simplified form of the decision tree by using the Input tab to specify the property. The Input tab becomes available after you click Advanced on the Results tab.

Step Description 6.1 Click the Results tab.

6.2 In the options, enable Allowed to Evaluate Properties, and click the Advanced button.

6.3 Click the Input tab.

6.4 Select .BorrowerInfo.CreditScore in the property field.

6.5 Click the Decision tab.

6.6 Click [expression]. Enter 0 in the value is field, and enter 0 in the [result] field.

6.7 Click the Add new decision after this one icon to add another condition.

6.8 Enter >750 in the [expression] and enter .0025 as the result.

6.9 Repeat to add other values listed in the above table.



6. Test the decision tree for conflicts and completeness, and unit test the tree.

7. Why does the tree include the condition when the borrower’s credit score is zero? Why would this situation be different from one in which the credit score is 550 or lower?

8. Create another decision tree named PMIPremium in the ILend-FW-LendFW-Work-Home-Mortgage class. Build this tree to return values for the following conditions, and set the Otherwise condition to return 0.



Step Description

8.1. In the first field enter .LoanInfo.DownPayment/.LoanInfo.AskingPrice and < as the condition to test and in the second field enter 0.10 , Select continue from the drop-down list.

8.2. Click the ["first value" = "second value"] link, in the first field, select .LoanInfo.Terms and in the second field, enter "15 years, fixed rate”, in the Return enter .0079*.LoanInfo.Amount/12

8.3. In the first field enter .LoanInfo.LoanTerms and = as the condition to test and in the second field enter “30 years, fixed rate”, in the Return enter .0090*.LoanInfo.Amount/12

8.4. Click return and select otherwise from the drop-down list and in the Return enter .0097*.LoanInfo.Amount/12

8.5. In the first field enter .LoanInfo.DownPayment/.LoanInfo.AskingPrice and < as the condition to test and in the second field enter 0.20, Select continue from the drop-down list.



8.8. Click return and select otherwise from the drop-down list and in the Return enter .0092*.LoanInfo.Amount/12

8.9. Enter 0 in the return of the otherwise



Exercise 18-3: Validate Assets and Liabilities

How To Do It:

1. In the Application Explorer, under ILend-FW-LendFW-Work, right-click Process and select New > Validate. In the Validate Name field, enter PopulatedAssetsandLiabilities

2. Create a validation entry to check that all listed Asset Value fields contain a value.

Step Description

2.1 Click Validate. In the drop-down list, select Validate Each.

2.2 Click [Property] and select .BorrowerInfo().Assets().AssetValue.

2.3 Check the Required? checkbox and clear the Conditions? checkbox.

2.4 Click the Add new Validate after this one icon to create a second validation entry.

2.5 Repeat steps 2.2 and 2.3 to create a validation entry for .BorrowerInfo.Liabilities().LiabilityValue.


3. Add the Validate rule to the CollectAssetsandLiabilities flow action rule.

Step Description

3.1 Open the CollectAssetsandLiabilities flow action.

3.2 Click the Action tab. In the Validate section, in the Validation Rule field, select PopulateAssetsandLiabilities.






Exercise 20-2: Conditionally Display Property Fields

How To Do It:

1. In the ILend-FW-LendFW-Work-Home class, quick create a single-value property of type TrueFalse, named CopyAddress.

2. Open the section rule CollectPropertyInfo, defined in the ILend-FW-LendFW-Work-Home class.

3. Create three Smart Layouts, titled Property Basics, Property Details, and Purchase Information.

Step Description

3.1. In the Layout tab, click the Show Wireframes icon.

3.2. Select the Smart Layout(Double -1) and open the properties panel.

3.3. In the Format Field select Standard (sub) under sub header, and enter Property Basics in the Title field. Click OK.

3.4. From the basic palette, drag a layout and place it under the Smart Layout(Double-1).

3.5. Repeat steps 3.2 and 3.3 and enter Property Details in the title field to create another layout.

3.6. Repeat steps 3.2 and 3.3 and enter Purchase Information in the title field to create another layout.



4. Add the following properties to the corresponding layout:

Step Description

4.1. From the basic palette, drag an input box and drop the input box to the first field cell in the smart layout(Double-1) from the left side

4.2. Click the cell properties panel and enter .PropertyInfo.HomeInMind as the Property and click ok

4.3. Click the label cell and in the cell properties panel replace input box with Do you have home in mind? in the value field. Click Ok.

4.4. Drag another input box in the field cell on the same row. Enter .LoanInfo.PropertyType in the Field cell and enter Property Type in the label Field.

4.5. Add .CopyAddress in the first cell from the left side in the second row. In the Label Field enter Do you have a current address?

4.6. Repeat Steps 4.1 to 4.5 to add the following properties in their respective layouts.



Layout 2: Property Details

Property Label Property Name Address .PropertyInfo.pyHomeAddress1

Address Line 2 .PropertyInfo.pyHomeAddress2

City .PropertyInfo.pyHomeCity

State .PropertyInfo.pyHomeState

Postal Code .PropertyInfo.pyHomePostalCode

Layout 3: Purchase Information

Property Label Property Name Down Payment .LoanInfo.DownPayment

Amount .LoanInfo.Amount

Asking Price .LoanInfo.AskingPrice



5. Preview the section rule to view your changes.

6. Update the section to display the Property Details layout when the value of HomeInMind is true.

Step Description

6.1. Open the layout properties of the property details layout by clicking on the layout.

6.2. In the visible when field, enter .PropertyInfo.HomeInMind = true

6.3. Enable the Run on Client Field.



7. Update the section to display the Purchase Information layout when Purchase is selected from the Loan Purpose drop-down list.

Step Description

7.1 Open the layout properties of the appraisal information layout by clicking on the layout.

7.2 In the visible when field, enter . LoanPurpose==’Purpose’

7.3 Enable the Run on Client Field.

8. Run the New Home Equity Loan Request or New Mortgage Request process to view the changes.

Pegasystems Inc. Fast Track to PRPC B-1

Appendix B: Optional Exercises

Exercise B-1: Index Embedded Properties

Scenario: Managers would like to create reports that include information about specific loans, such as the loan type and the loan purpose.

Requirements: Index the .LoanType and .LoanPurpose embedded properties. These properties will then be available to report rules by using a declarative index join. Refer to: PDN article PRKB25278: How to create declarative indexes for embedded properties.

After you index each property, you will see a dialog similar to the following:


B-2 Fast Track to PRPC Pegasystems Inc.

Exercise B-2: Add a Spinoff to a Flow

Scenario: ILend wants to follow up with Applicants who withdraw their mortgage requests after reviewing their conditional offer.

Requirements: Add a spinoff shape to the Mortgage flow that routes the work item to a new flow. In the new flow, create an assignment. Connect the Assignment to End Shape, use Assign in the Flow action rule. This assignment currently is assigned to the loan agent. After you complete Module 22, you can modify the flow to route to a work basket. Refer to: Developer Help.

After you add the Spinoff shape, your flow should look like the following:



Exercise B-3: Audit Changes to a Field

Scenario: Using the audit trail, debug the Loan Request application to verify that .Terms and .LoanRateAdjustment are set properly.

Requirements: Use the Field Level Auditing gadget to record changes to the Terms and LoanRateAdjustment properties. You can test changes to .Terms by entering a value in the screen flow. .LoanRateAdjustment is set declaratively using the result of a decision table, and cannot be fully tested until you complete Module 19. Refer to: PDN article PRKB26135: How to track changed values of work object properties using the Field Level Auditing gadget.

After you complete this exercise, the History for the loan request work item should contain two entries: one that records any change to .LoanRateAdjustment as 0, and one that records the value you entered in the Terms field. Click Finish to exit the screen flow to view history.



Exercise B-4: Circumstance a Decision Table

Scenario: Due to weakness in the housing markets in California, New York, and Massachusetts, the Loan Officer must verify that applicants meet a special income threshold for mortgage requests greater than or equal to $200,000 and home equity loan requests greater than or equal to $30,000.

Requirements: Use multivariate circumstancing to ensure that loan requests for applicants in the following situations are routed to a loan officer for either mortgage requests greater than or equal to $200,000 or home equity loan requests greater than or equal to $30,000.

• State= CA, Income= < $80,000 • State= MA, Income= < $60,000 • State= NY, Income= < $70,000

Refer to: PDN article PRKB 25272: How multivariate circumstancing works.

After you complete this exercise, you will have two RequiresLoanOfficer decision tables. Look for the Circumstance icon ( ) in the Application Explorer and on the rule form to indicate the circumstanced decision table.

The circumstance template is:



The circumstance definition should look like the following:

The circumstanced decision table should look like the following:



Exercise B-5: Customize the Appearance of an Application with the Branding Wizard

Scenario: The Loan Request application uses a default skin. Use the Branding Wizard to create a new skin to customize the display of tabs and title bars on the forms used by the Loan Request application.

Requirements: Run the Branding wizard from the Pega menu: User Interface > Tools > Branding Wizard. Refer to: PDN article PRKB25641: How to use the Application Skin wizard to create a new skin.

After you complete this exercise, the work item form for the Loan Request process should modify the colors of the tabs and the bars depending on the color scheme chosen by you



Exercise B-6: Create a Cascading Dynamic Select Control

Scenario: On the CollectLoanInfo section, the current implementation of dynamic select controls may lead to degradation in performance. Re-implement this form to use a cascading dynamic select.

Requirements: Update the GetTerms activity to comment out the Obj-Filter step and reconfigure the Terms DynamicSelect as a Cascading DynamicSelect control. Refer to: PDN article PRKB25898: How to configure cascading dynamic select controls.

After you complete this exercise, the parameters for the Terms DynamicSelect control should be similar to the following:



Exercise B-7: Create a Declare Page to Cache External Data

Scenario: To avoid data entry mistakes by Loan Agents, the loan terms for mortgages is provided in a data table. Because this information changes infrequently — only when a new loan product is added — the IT department has suggested caching this information, rather than querying the database during each mortgage request process.

Requirements: Create a Declare Pages rule to cache the contents of the ILend-FW-LendFW-Data-HomeLoans data table. Create an activity in ILend-FW-LendFW-Data-HomeLoans to populate the declare page with data from the data table. (Refer to the activity listed in the next page) Refer to: PDN article PRKB25039: How to create a declare pages rule.

After you complete this exercise, the declare page rule should look like the following:



The activity you create should look like the following

When creating the activity, remember to select the LoadDeclarativePage activity type on the Security tab.



Exercise B-8: Create an SLA for a Flow

Scenario: Used to describe the exercise in business terms, rather than developer terms.

Requirements: Edit the Reinitiate contact flow and modify the assignment to route to a new workbasket called PendingApplications. Create another work basket for ProcessPendingApps. Create a new SLA rule with a goal and deadline task. For the goal task, create an escalation activity which reroutes to ProcessPendingApps workbasket. For the deadline task, use Actiontransfertomanager so that the work item is routed to manager if it lingers in the workbasket. Refer to: Module 22 for steps in creating a workbasket and an SLA rule, and Developer Help.

Note: You can also use a Work Parties rule in transferring the workbasket between multiple operators. For help in using a Work Parties rule, see Developer Help.

Pegasystems Inc. Fast Track to PRPC C-1

Appendix C Auto Loan Application

Exercise C-1: Create Properties and Set the Model Rule

Estimated Duration

Scenario: As a system architect, you need to create properties to collect data during the loan application processes to support the automobile loan request processes

Requirements: Build properties specific to Automobile loan process to be used in the tabbed screen flow for Automobile Loans.

How to Do It:

1. Use the Define Properties wizard to create the following properties in ILend-FW-LendFW-Work-AutoLoan. Enter the DisplayAs and Details information on the second page of the wizard, and click Finish.

Description Type Display As Details Current Model Year Integer TextBox

Loan Purpose Text DropDown New Vehicle Used Vehicle

Make Text TextBox

Model Decimal TextBox

Model Year Integer TextBox

Terms Text DropDown 3 years,fixed rate4 years,fixed rate5 years,fixed rate6 years,fixed rate

Appendix C: Auto Loan Application

C-2 Fast Track to PRPC Pegasystems Inc.

2. Add the following properties and values to the pyDefault model rule in the ILend-FW-LendFW-Work-AutoLoan class:

Property Value .CurrentModelYear 2010

.LoanInfo.LoanType “Auto Loan”



Exercise C-2: Create the Auto Loan Flows

Scenario: ILend wants to expand the Loan Request application to offer Automobile Loans in addition to Mortgage and Home Equity Loans. Loan Agents must be able to navigate between each form similar to the other loans.

• Personal identification and qualification information (such as name, address, and income).

• Information about the loan being requested (such as the type of loan and amount of the loan).

• Information about how the loan will be used (the vehicle to be purchased).

• The approximate net worth of the borrower. Loan Agents must be able to navigate each form and readily understand (and communicate to the Loan Applicant) the information being requested. Also, ILend wants to use the same UnderwriteLoan process built for the other loans.

Requirements: Build AutoLoanMainFlow and CollectInfoAuto flows in the ILend-FW-LendFW-Work-AutoLoan class. Add the UnderwriteLoan flow to the AutoLoanMainFlow. Include all utility shapes needed to set the work status.

How to Do It:

1. Open CollectInfoHomeEquity and save a copy of the flow into the ILend-FW-LendFW-Work-AutoLoan class by changing it in the Applies To field, and enter CollectInfoAuto in the Flow Type field. Enter Collect Automobile Loan Information in the Short Description, and update the Collect Loan Information assignment, using the following information:



Field Name Value to Enter Name Collect Auto Loan Information


Work Type AutoLoan

Use Case CollectAutoLoanInformation

2. Edit the Assignment shape to collect the vehicle information.

3. Update the Short Description of the AutoLoan flow to New Automobile Loan Request. Save the flow and open it in the Flow Editor.

4. Delete the Collect Information and Underwrite Loan assignments.

5. Drag the CollectInfoAuto flow onto the Flow Editor, onto the connector emanating from the Start shape.



6. On the Properties panel for the flow shape, select Screen Flow in the Flow type drop-down list.

7. Open the HomeEquityLoan flow rule. Keep it open as a reference while completing the AutoLoan flow rule.

8. Add the decision shape and refer the same decision table, make sure the connectors are connected to the same shapes.

9. Add all the utility shapes that exist in HomeEquityLoan in the AutoLoan.



10. Add the UnderwriteLoan subflow and delete the UnderWriteLoan Assignment.



Exercise C-3: Create User Interface Rules

Scenario: Loan Agents must be able to collect Automobile loan specific information in the loan information and vehicle information tabs.

Requirements: Build user interface rules to build the loan information and the vehicle information user interfaces.

How to Do It:

1. Open the section rule named CollectLoanInfo defined in ILend-FW-LendFW-Work-Home-HomeEquityLoan and click Save as to create the rule in ILend-FW-LendFW-Work-AutoLoan. (Do not change the name of the rule).

2. Click the Preview icon to see the choices in Terms, Loan type, and Loan Purpose are referring to the values defined in the AutoLoan class.

3. Open the flow action rule named CollectLoanInfo defined in ILend-FW-LendFW-Work-Home-HomeEquityLoan and click Save as to create the rule in ILend-FW-LendFW-Work-AutoLoan. (Do not change the name of the rule).

4. Create a flow action CollectVehicleInfo in ILend-FW-LendFW-Work-AutoLoan.

5. Create a new section rule named CollectVehicleInfo, and reference this section from the flow action rule.

6. Drag the Make, Model and ModelYear properties to the layout.

7. Save the rule.

8. Mark the ModelYear property as Required.



Exercise C-4: Create Decision Rules

Scenario: ILend wants to evaluate the risk of the loan based on certain factors, to determine if they want to underwrite the loan or not. A loan request application is considered too risky in the following situation for an automobile loan:

• Loan amount is more than the total income of the applicant and spouse.

Requirements: Modify the IsTooRisky decision table to add the condition for automobile loans.

How to Do It:

1. Open the decision table rule named IsTooRisky.

2. In the decision table click on any row and click Insert Row After icon to add a condition.

3. Add the following condition: if the request is for an Auto Loan, and the loan amount is greater than the total income of the borrower and spouse, then return TooRisky.

Note: Alternately, you can click Edit in Excel and enter these values in the Excel and then click Save in Excel to see how the decision table is viewed in Excel.



4. Unit test the logic of the decision table using the following scenarios.

Loan Type Amount Borrower Income Spouse’s Income Auto 30000 4000 10000

Auto 20000 20000 10000

5. Open the decision table rule named RequiresLoanOfficer.

6. Add a new condition in the table for auto loans and return No.

7. Run the Auto Loan process and test the decision table logic.

8. Open the LoanRateAdjustment decision tree rule defined in ILend-FW-LendFW-Work class.

9. Create a new decision tree branch to calculate loan rate adjustments for Auto Loans.

Purpose Term Rate Adjustment New Vehicle 6 years, fixed rate 0.0075

New Vehicle All other terms 0.0045

Used Vehicle 6 years, fixed rate 0.0115

Used Vehicle All other terms 0.0095



Exercise C-5: Create a Constraint to Enforce Valid Data Entry

Scenario: ILend wants to restrict the loan terms when the applicant is requesting an automobile loan for vehicles older than three years. ILend did an extensive analysis and have estimated that they cannot offer loans for more than 3 years for these vehicles.

Requirements: A when rule has to be created to add conditions to qualify a vehicle which is older than 3 years. A constraint rule has to be created to restrict the loan term.

How to Do It:

1. Create a when rule named IsOldVehicle in ILend-FW-LendFW-Work-AutoLoan class to determine if the vehicle chosen satisfies the condition.

Step Description

1.1 In the when rule, add the condition .LoanPurpose != “New Vehicle”

1.2 Add another condition, .Terms != “3 years, fixed rate”

1.3 Add another condition, select [property reference] has a value. Enter .ModelYear in the property field.

1.4 Save the rule.



2. Create a constraint named ConstraintModelYear in the ILend-FW-LendFW-Work-AutoLoan class.

Step Description

2.1 Select Rule [when Record] evaluates to true. Select IsOldVehicle as the when rule.

2.2 Enter .ModelYear >.CurrentModelYear-4 as the condition.

2.3 Enter .ModelYear. as the property.

2.4 Add the following text in the message. “The loan you have requested cannot be made on a vehicle more than four years old.”



Exercise C-6: Create a Declare Page to Cache External Data

Scenario: Loan Agents are required to collect the make and model of a vehicle when completing a loan application. To avoid mistakes in data entry, ILend’s IT department has created a database of automobile makes and models, and would like to incorporate this database into the Loan Request application. Furthermore, because this information changes infrequently – once per model year – they would like to cache this information, rather than necessitate a database query during each automobile loan request process, to improve performance.

Requirements: Create two declare pages; one containing a listing of automobile makes, and one containing a listing of automobile makes and models.

How To Do It:

1. Create a Declare Page named Declare_AutoMakes.

Step Description

1.1 Select Node in the Page Scope drop-down list, and enter ILend-FW-LendFW-Int- in the Page Class field.

1.2 Select Page in the Page Structure drop-down list.

1.3 Select LendFW:SystemArchitects as the access group.

2. Create an activity named QueryMakeInfo to populate this page with a listing of automobile makes.

Parameter Value RequestType getMakeInfo

Access MSSQL

ClassName ILend-FW-LendFW-Int-



Step Description

2.1 Enter QueryMakeInfo in the Load Activity field. Create a new activity rule.

2.2 In the first step, enter Declare_AutoMakes as the step page, and select RDB-List as the method.

2.3 Expand the method step and enter the parameter values listed above.

2.4 Click the security tab and select Load Declarative Page in the Activity Type drop-down list.

3. Save the activity and the declare page rule.

4. Create a second declare page, named Declare_AutoModels, using the same parameters as the first page. Use QueryModelInfo as the activity name.

5. Create an activity to populate this page with a listing of vehicle makes and models. In the activity, use the RDB-List method and specify getModelInfo as the RequestType.

Note: getMakeInfo and getModelInfo are Connect-SQL rules provided to you for this exercise. Connect-SQL is one of the standard Integration-Connectors rules available in Process Commander. You will learn more about Integration-Connector rules in PegaRules Process Commander Bootcamp course.



Exercise C-7: Use a Declare Page to Populate an Auto complete Control

Scenario: Loan Agents would like to be able to enter automobile make and model information without needing to select this information from a long list. They would prefer to be able to enter one or two letters of the make or model, and be presented with a much shorter list of possible choices.

Requirements: Add AutoComplete controls on the Collect Vehicle Information form to allow Loan Agents to select automobile makes and models by typing two letters.

How To Do It:

1. Use the Declare Page you created in the previous exercise to populate an Auto-Complete control for vehicle makes.

Step Description

1.1 Open the CollectVehicleInfo section

1.2 Edit the properties panel of Makes Property and select AutoComplete in the Display As field

2. Configure the AutoComplete control

Step Description

2.1 Click the magnifying glass next to Autocomplete.

2.2 Select ClipboardPage as the DataSourceType, and specify the Declare_AutoMakes page in the ClipboardPage Name field

2.3 Enter Make as the DisplayField and specify 2 as the Minimum Search Characters

2.4 Enable the Highlight, Only match the start of string, and Client Cache options

2.5 Click OK to close the Param window. Save the section.



3. Preview the CollectVehicleInfo section, and verify that the AutoComplete control prompts you with a list of vehicle makes matching the string you have entered into the field. Select a make from the list to verify that the field populates properly.

4. Add another AutoComplete control for Model.

5. Notice you could select any model for any make and they do not constrain based on the make selection. This can be done by using cascading dynamic select for both or use an activity to populate the clipboard page for the second autocomplete control.

ft61v1 student guide%282%29

Documents

pegasystems trademarks

property of pegasystems

services of pegasystems

discretion of pegasystems

pegasystems product

pegasystems service

student guide copyright

fast track