Tutorial: Building Your First Application
© Copyright 2011
Pegasystems Inc., Cambridge, MA All rights reserved.
This document describes products and services of Pegasystems Inc. It may contain trade secrets and proprietary infor-mation. The document and product are protected by copyright and distributed under licenses restricting their use, copying distribution, or transmittal in any form without prior written authorization of Pegasystems Inc.
This document is current as of the date of publication only. Changes in the document may be made from time to time at the discretion of Pegasystems. This document remains the property of Pegasystems and must be returned to it upon request. This document does not imply any commitment to offer or deliver the products or services described.
This document may include references to Pegasystems product features that have not been licensed by your company. If you have questions about whether a particular capability is included in your installation, please consult your Pegasystems service consultant.
For Pegasystems trademarks and registered trademarks, all rights reserved. Other brand or product names are trade-marks of their respective holders.
Although Pegasystems Inc. strives for accuracy in its publications, any publication may contain inaccuracies or typo-graphical errors. This document or Help System could contain technical inaccuracies or typotypo-graphical errors. Changes are periodically added to the information herein. Pegasystems Inc. may make improvements and/or changes in the infor-mation 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
About this tutorial 1 Audience 1 The scenario 2 Tutorial structure 2 Conventions 2 Navigation 3 Images 3 Application login 3
Errors and enhancements 3
Prerequisites 4
Importing the starter kit 4
About the starter kit 6
Business objectives, work type, use cases, and requirements 6
Globex's Onboarding project's business objectives 7
Equipment Request process and work type 7
Business process atomic use cases 7
Actors 8
Business requirements 8
Use case descriptions 8
Step 1: Create the application profile 11
Part A: Capture basic project details 11
Part B: Capture essential process steps using the Discovery Map 17
Part C: Complete capturing information in the Application Profiler 25
Review 27
Step 2: Generate the base application 28
Part A: Running the Application Accelerator 28
Step 3: Review the application structure 34
Part A: Update the OnboardingFW RuleSet 34
Part B: Review the class structure 37
Part C: Review the rules generated by the Application Accelerator 40
Part D: Use the standard heat map to review the number and types of rules in the application 41
Review 42
Step 4: Adjust the initial process 44
Part A: Run the process 45
Part B: Edit the flow 48
Part C: Review the updated process 59
Review 61
Step 5: Create a data model 62
Part A: Create a single value property 63
Part B: Create properties using the Property Wizard 68
Part C: Create embedded properties 72
Review 77
Step 6: Extend the default user interface 78
Part A: Customize the CoreSummary section 80
Part B: Create the sections for selecting hardware and software items 86
Part C: Create the Budgets Section 96
Part D: Create the ReviewSelections section 97
Part E: Add sections to harnesses and flow actions 99
Review 103
Step 7: Refine the process definition 104
Part A: Modify the user interface for the Review step 105
Part B: Edit the flow to refine the process 105
Step 8: Create a finished user interface 109
Part A: Customize the Header section 109
Part B: Add manager's note to the Header section 112
Review 114
Step 9: Create decision rules 115
Part A: Create when condition rules to control sections 116
Part B: Create rules to calculate budget amounts and totals 119
Review 124
Step 10: Document the application 126
Part A: Document the application 126
Introduction
The Building Your First Application tutorial walks you through the steps of building a Process Commander appli-cation. In the business scenario for this tutorial, you are an application developer working at a fictional software com-pany named Globex. Globex is growing by leaps and bounds, and is having a surge in hiring new employees for a number of its departments.
To increase the speed that the company can adapt to this surge, management is sponsoring development of an Onboarding application. They picture this application automating and managing all of the Globex processes involved in onboarding a new hire. Within this broad Onboarding framework, your task is to design and develop the piece that handles equipment setup for a new hire, while other teams at Globex work on the other onboarding-related proc-esses. Eventually, Globex wants to integrate all of the onboarding-related processes and applications. This tutorial is about the equipment setup process.
The application you build simplifies and automates an existing manual process currently used by Globex’s HR staff to ensure new hires have the necessary equipment on their first day.
You begin by reviewing Globex's requirements and creating an Application Profile. Using this profile, you create the basic structure of the application using the Application Accelerator. You continue by filling in this basic structure with the class structure, flow, and data models needed to meet these requirements. Later steps cover evolving and refin-ing the application to include decision and declarative rules to streamline the application's functionality.
Each step of this process is broken down into smaller tasks, with a review section at the end.
About this tutorial
Audience
This tutorial is intended for Process Commander users who wish to review the steps involved in creating a Process Commander application and improve their skills. The tutorial content assumes the reader has access to Process Commander V6.1 SP2, and is familiar with theDesigner Studio1and with creating rules, editing flows, and running processes in the Designer Studio.
1The Designer Studio is available to users who are associated with an access group that identifies the Developer rule as their current portal. It provides tools and resources organized into a development environment that speeds application planning, construction, testing, and updating.
The scenario
You are an application developer working at a fictional software company named Globex. Globex is growing by leaps and bounds, and is having a surge in hiring new employees for a number of its departments.
To increase the speed that the company can adapt to this surge, management is sponsoring development of an Onboarding application. They picture this application automating and managing all of the Globex processes involved in onboarding a new hire.
Within this broad Onboarding framework, you’ve been charged with developing the piece that handles equipment setup for a new hire.
The steps of the tutorial cover work that, in a large company, might be done by several colleagues rather than one developer. The header for each step indicates the role of the employee who would typically do the work in that step.
Tutorial structure
A diagram of the general flow of application development helps indicate where you are in the process. The high-lighted stage in the diagram indicates the focus of the current tutorial step. This is the image for the step on creating a data model:
Each step in the tutorial follows this pattern:
n The first screen of the step displays the relevant diagram, describes the situation within the scenario (where relevant), indicates the skills you will exercise, and provides information you may need to complete the step. n The step is broken down into parts. Each part provides text and images to help you accomplish the step’s
goals.
n At the end of the step, a review screen summarizes the work you did and provides links for learning more about the skills you used in the step.
Conventions
The tutorial follows a few display conventions:
n A value that appears within the application, such as the name of a property or a field, appears highlighted in the tutorial, such asGLBX-FW-OnboardingFW-WorkandName.
n A reference to a button you are to click appears as “Click Create”, or may show an image of the button: “Click ”.
n A small icon to the left of blue text ( ) indicates that more information is available. Click the icon to expand the area and see the additional information. Click to collapse the area again.
Navigation
At the bottom of the first screen of each step are links to the parts of the step. You can proceed using these links, or by using the Previous Topic / Next Topic links that appear below the step links.
The left panel of the tutorial window has four sections to help you understand and navigate through the tutorial: n TOC (table of contents) provides links to all the steps and parts of the tutorial. Click any closed book icon (
) to expand that entry and see the steps within it. Click any link to display the screen related to it. n Glossary defines key words and concepts found in the tutorial.
n In the Search feature, provide a word or phrase and click Search. The display shows a set of screen titles, with the screen most likely to satisfy your search at the top. Click any link to display that screen. Click the magnifying glass icon to the right of the Search button to add the current search term to your list of favorites (see next).
n The Favorites feature lists searches and topics that you have tagged as your favorites. To add a screen to the list of Favorite Topics, display it in the right panel and click the icon at the extreme left of the task bar.
Images
The tutorial includes many images to illustrate the text. Hover the mouse over any image to expand it to a larger size for easier viewing. Click away from the image to return it to its original size.
If images appear clipped on the left hand side of the content area, widen the content area (the right panel) of the tuto-rial window to avoid this behavior.
Application login
The initial import creates default administrator login credentials:
Name [email protected]
Password rules
You can create additional operator IDs within the GLBX.com structure if necessary.
Errors and enhancements
If you find errors in the tutorial, or have suggestions for making it more useful, feel free to write to [email protected].
Prerequisites
Before beginning the course in your Process Commander system, verify the following conditions:
Condition How to verify
You have access to a V6.1 SP2 system, and have an operator ID with which to access the sys-tem.
Your organization should provide you an operator ID and the URL to the system. After you log into the system using that operator ID, select the Help > About menu item to confirm the version of your system.
You have Microsoft Visio 2003 or higher installed on your client machine.
Open your Windows control panel and double-click Add/Remove Programs. See if Visio is listed.
Your operator ID references an access group con-taining thePegaRULES:SysAdm4role
When you are logged into your system, access the operator menu (the menu with your name) at the top of the Designer Studio window. Select Access Group from the menu.
The system does not contain RuleSets named GLBX, GLBXInt, OnboardingFW, Onboard-ingFWInt
On the left panel of the Designer Studio, select the Rules Explorer. Expand the SysAdmin cat-egory. Click the RuleSet branch to view a list of RuleSets in the right panel. If a list does not appear, select INSTANCES from the drop-down list at the left of the top toolbar.
The system does not contain an organization named GLBX.
On the left panel of the Designer Studio, select the Rules Explorer. Expand the Organization category. Click the Organization branch to view a list of organizations in the right panel. If a list does not appear, select INSTANCES from drop-down list at the left of the top toolbar.
Importing the starter kit
Before beginning Step 1 of the tutorial, you must import some Process Commander resources that set up the appro-priate organization and operators for the tutorial scenario, and provide some additional assets needed for the tutorial steps.
1. Download file Build_Your_App_Organization.zip from
http://pdn.pega.co- m/DevNet/eLearning/byfpca/Content/Resources/Zips/Build_Your_App_Organ-ization.zipand save it to a location on your network.
2. Log on to your V6.1 SP2 system using the operator ID that your organization has assigned to you for access-ing that system.
4. Click Browse, and select the downloaded file.
5. Click Upload File.
7. Click Import.
When the system indicates that all of the records have been copied, click Done. The resources are ready for you to begin Step 1 of the tutorial.
Because Step 1 of the tutorial starts by having you log in with a different operator ID, log out of the system before beginning Step 1.
About the starter kit
When you import the starter kit, the following assets are imported into your Process Commander system.
Assets Description
GLBX organization and the related rules and data instances
The GLBX organization and related rules and data instances provide the business context for the tutorial scenario. Items such as the GLBX organization, related oper-ator IDs, and related access groups are imported.
Two data tables named "Hardware Items" and "Software Items" and their supporting rules.
These data tables and their supporting rules provide sample data values used in the tutorial scenario.
Two activities named "getHardware" and "getSoftware".
These activities are used to retrieve the sample data values from the data tables and make the values available for display at runtime.
Business objectives, work type, use cases, and requirements
As described, the Globex organization wants an Onboarding application. Within this broad Onboarding framework, you’ve been charged with the piece that handles the process for requesting the equipment setup for a new hire. This section describes the needed background information about the application and the process. You will use this information in subsequent steps of the tutorial.
Note: The Globex scenario and the details describing Globex's process, the use cases,and requirements are inten-tionally simple to allow you to more quickly complete the tutorial steps while also illustrating the key concepts. In a real-world situation, an implementation is typically more complex than this tutorial scenario. In a real-world situation, the process, use cases, and requirements will involve more details than are provided for this scenario. Throughout this tutorial, assume that the Globex subject matter experts have provided this information.
Globex's Onboarding project's business objectives
Business objectives describe why the application is being developed. They are the project goals that, when reached, provide the sought-after business return or benefit.
The business objectives that Globex wants to achieve with the overall Onboarding application are: n Automate the approval process for employee onboarding requests
n Reduce turn-around time for new hire equipment setup
Equipment Request process and work type
You find out from the Globex business subject matter experts that their manual (paper-based) equipment request process today involves:
n Entering information about the new hire (name, department, hiring manager's name) n Specifying the hardware items to be purchased and set up for the new hire.
n Specifying the software items.
n Approving the equipment request or, alternatively, rejecting the equipment request. n Stamping the filled-out paper form as "Approved" (if approved) or "Rejected" (if rejected).
The template from which these forms are created is called the work type. For this application, the work type is Equipment Request. A specific created instance is called the work item.
Business process atomic use cases
To facilitate reuse, a business process is broken down into atomic use cases. Each atomic use case represents one action owned by a single actor. By using atomic use cases in the system, it is easy to trace where a use case is implemented in the application user interface, and assess whether the application is being built appropriately. The following table illustrates Globex's manual process steps broken down into atomic use cases and the actor involved in each use case.
Manual Business Process Step Associated Atomic Use Case Typical Actor Enter information about the new hire Enter New Hire Info HR Staff Member
Specify the hardware items Select Hardware HR Staff Member
Specify the software items Select Software HR Staff Member
Approve the equipment request Approve Hiring Manager
Reject the equipment request Reject Hiring Manager
Actors
An actor takes action on work at a specific business process point. The actors in this process are: n HR Staff Member: Begins the process and fills out the request for the new hire’s equipment setup n Hiring Manager: Approves equipment requests for the new hires in his or her department
n System: Updates status of the work
The system itself meets the definition of an actor for this application, because it takes action on work at specific process points. In this particular process, the Globex subject matter experts have identified points at which the sys-tem will update the status of the work isys-tem as it moves through the process: after the Approve step and after the Reject step.
Business requirements
Requirements describe the capabilities the application must fulfill, and typically provide additional details for an atomic use case. They can be viewed as the “success criteria” for the project: the stakeholders expect to see these items implemented to say the project was a success.
A Process Commander application enables you to capture requirements in the system itself, so that they can be associated to use cases and tracked as the application is developed. For this project, Globex's subject matter experts have provided a list of business requirements to enter into the system in Step 1 of the tutorial.
Note: The list below is not intended to represent the complete and exhaustive list of all business requirements a real-world equipment request process would typically have. In a real-real-world situation, an implementation is typically more complex that this tutorial scenario.
Requirement name Description
ER001_Create_ER System should enable an employee to create an equipment request.
ER002_Calculate_Cost System should calculate the cost of selected items during the process.
ER003_Calculate_Remainder System should calculate the remaining budget (where remaining budget is the department budget minus the equipment total cost). ER004_Add_Note System should enable a manager to add a note to the equipment
request.
Use case descriptions
Globex's subject matter experts have provided the descriptions for each atomic use case in their process. In a real-world situation, an implementation is typically more complex and would likely have more use cases and more com-plex descriptions.
Enter New Hire Info
First Name (entry field) Last Name (entry field) Department (drop-down list) Manager (entry field)
HR Staff Member specifies the information. Select Hardware
System displays a repeating structure with one row per item selected: Hardware (drop-down list)
Price (read-only field)
HR Staff Member makes selections from the Hardware list. Select Software
System displays a repeating structure with one row per item selected: Software (drop-down list)
Price (read-only field)
HR Staff Member makes selections from the Software list. Approve
System displays:
Department Budget (read-only field)
Hardware Total (read-only field; running total calculated from selections) Software Total (read-only field; running total calculated from selections)
Remaining Budget (read-only field; running total calculated from subtracting the total costs from the Department Budget)
Two lists for the selected Hardware and Software items: Hardware (read-only field)
Price (read-only field) Software (read-only field) Price (read-only field)
An Approve button to approve the request and an optional Note text box. Hiring Manager optionally enters a note and clicks the Approve button. Reject
Department Budget (read-only field)
Hardware Total (read-only field; running total calculated from selections) Software Total (read-only field; running total calculated from selections)
Remaining Budget (read-only field; running total calculated from subtracting the total costs from the Department Budget)
Two lists for the selected Hardware and Software items: Hardware (read-only field)
Price (read-only field) Software (read-only field) Price (read-only field)
A Reject button to reject the request and a Rejection Note text box to record the reason for the rejection. Hiring Manager enters a rejection note and clicks the Reject button.
Step 1: Create the application profile
Typically performed by In the previousstep
Purpose of this step
To... So that...
Business Analysts No previous step Capture descriptions of the use cases and appli-cation requirements
Later steps can relate specific parts of the application to individual use cases and requirements
In this step, you use the Application Profiler tool to capture the project's objectives, use cases, and requirements directly in the system. The input to this step is used in the next step to generate the base structure of the application.
Creating an application profile using the Application Profiler is the first step when creating an application. It answers the question “What will I build?” In going through the Application Profiler, important information about the project is captured such as its business objectives, the stakeholder requirements, and the business process. Typically, a busi-ness analyst runs the Application Profiler with subject matter experts and other team members to directly capture that information from them.
Within this tutorial's scenario, the project given to you is the Globex project described in theBusiness objectives, work type, use cases, and requirementstopic. The Globex organization wants an Onboarding application that can provide automation and efficiency for getting a new hire started in the company.
In this tutorial step, you run the Application Profiler and specify details about the project. The details you need to input are provided as you go through the exercise. Running the Application Profiler results in two items:
l An application profile object, which the system uses as the basis for generating the basic structure of the application. You build out this application in subsequent steps.
l An application profile document, which is typically used by the project sponsors to review the project, val-idate that it is proceeding in the expected direction, and size the effort.
Continue to the next topic to begin this step of the tutorial.
Part A: Capture basic project details
The first task in the Application Profiler is to capture basic project details. For the Globex scenario, use the following project details.
For this field Enter this value
Profile option New Application
Build New Framework And Implementation
Build on Framework None
Application Name Onboarding
Project Name Onboarding Version 1
Project Led By External Consultants
Organization Name Globex
Business Objectives Two objectives:
Automate the approval process for employee onboarding requests
Reduce turn-around time for new hire equipment setup Project Description Globex (GLBX) is a fast growing software company.
Mak-ing the onboardMak-ing process more efficient will increase the ability for the company to grow successfully.
1. Log on to the system [email protected]with the password rules to access theDesigner Stu-dio1. (That operator ID is the one provided in the zip file archive that needs to be installed before beginning the tutorial. SeePrerequisitesfor details.)
2. Start the Application Profiler by selectingNew Application > Application Profilefrom the Application menu.
3. In the Application Overview window that displays when the Application Profiler starts, specify the details as listed in the table above. You can copy text from the table and paste it into the fields.
1The Designer Studio is available to users who are associated with an access group that identifies the Developer rule as their current portal. It provides tools and resources organized into a development environment that speeds application planning, construction, testing, and updating.
To add the second business objective, click . A new line is displayed and you can paste in the text for the second business objective.
Confirm that the completed Application Overview window looks like the following image, then click OK to save the project details.
5. In the Actors window that opens, leave the Actors Background Information field blank. Specify the fol-lowing information for the actors that participate in Globex's current process for onboarding. Click twice to add two more rows.
Name Type Access
HR Staff Member Operator Browser
Hiring Manager Operator Browser
This information will be used in the use cases that are entered in the Application Profiler. 6. Click OK to save the information in the Actors window.
7. After closing the Actors window, the current step is the Processes step. This step is for entering details about the business processes that are part of this application.
Your assignment in Globex's Onboarding project is their Equipment Request process, as described in the
Business objectives, work type, use cases, and requirementstopic. Therefore, you first want to update the default values for the work type and the process name to reflect the Equipment Request process.
8. Select the drop-down menu next to the default Onboarding label to update the work type information.
Complexityfield is set toLow(the default value). Then click OK to save the updates.
Field Value
Name EquipmentRequest
Display Label Equipment Request
Complexity Low (the default value)
Prefix ER
Description Equipment request work item
10. To update the process name to reflect the fact that the process concerns an equipment request, select the drop-down menu next to the default label (StartOnboarding) and selectRename.
In the Edit Flow Name Details window, note that the system has supplied a default value based on the updated work type name (StartEquipmentRequest). Add spaces to the default value to set it toStart Equipment Request. Click OK.
At this point, the system refreshes the display for the Processes step and it should look like the following image.
Continue to the next tutorial topic.
Part B: Capture essential process steps using the
Dis-covery Map
The second task in the Application Profiler is to capture the essential process steps using theDiscovery Map1. The main area on the Processes step displays the Discovery Map. The Discovery Map is an inventory of the essential process steps that affect or alter the work item as it proceeds from its creation to its final resolution. Colored shapes represent these essential steps.
Note: The Globex scenario and the details describing Globex's process, the use cases,and requirements are inten-tionally simple to allow you to more quickly complete the tutorial steps while also illustrating the key concepts. In a real-world situation, an implementation is typically more complex. In this tutorial, assume that the Globex subject matter experts have provided this information.
Globex's subject matter experts have identified the following essential process steps that affect the Equipment Request work item:
l Select Hardware l Select Software l Approve
1A Discovery Map is a graphical design tool integrated into the Processes tab of the Application Profiler and Appli-cation Accelerator. A Discovery Map provides a high-level presentation of steps in the starting business flows in the application including the subflows and alternate paths.
l Update Status (system updates the work item status after approval) l Reject (alternate step to the Approve step)
l Update Status (system updates the work item status after rejection) Add the essential process steps to the Discovery Map using these steps:
1. In the Discovery Map, click theStep Namelabel on the default initial shape. TypeSelect Hardware. 2. Double-click the open shape space next to theSelect Hardwareshape to add a new green shape. Click
the shape's label and typeSelect Software.
3. Double-click the open shape space next to theSelect Softwareshape to add a new green shape. Click the shape's label and typeApprove.
4. Double-click the open shape space next to theApprove shape to add a new green shape. Click the shape's label and typeUpdate Status.
5. Right-click theUpdate Statusshape, and selectAdd New Alternate Stepto add theRejectstep, because Globex's subject matter experts have identified the Reject step as an alternate step in the process. A double red line appears in between theUpdate Statusshape and the new shape to indicate where the alternate steps begin. Click the new shape's label and typeReject.
6. Double-click the open shape space to the right of theRejectshape to add anUpdate Statusstep (in which the system updates the work item status after rejection). Click the new shape's label and typeUpdate Status. (You might have to widen the Designer Studio window to add this shape.)
At this point, the Discovery Map should look like the following image.
The following steps describe how to capture the details of Globex's atomic use cases and requirements in the sys-tem and associate them with the appropriate shapes. This table shows the relationship between the shapes and the atomic use cases and requirements, using the information provided by Globex's subject matter experts. Some requirements are associated with more than one use case. Because Globex's subject matter experts have not iden-tified a requirement associated with the "Update Status" use case, a requirement is not entered for that use case. The name of the use case is the same as the name of its associated shape.
Shape Actor Use Case Description Associated Requirements Select
Hardware
HR Staff Member
System displays a repeating struc-ture with one row per item selected: Hardware (drop-down list)
Price (read-only field)
HR Staff Member makes selections from the Hardware list.
Name: ER001_Create_ER Details:
System should enable an employee to create an equipment request.
Importance: 1 - Critical Select Software HR Staff Member
System displays a repeating struc-ture with one row per item selected: Software (drop-down list)
Price (read-only field)
HR Staff Member makes selections from the Software list.
Name: ER001_Create_ER Details:
System should enable an employee to create an equipment request.
Importance: 1 - Critical
Shape Actor Use Case Description Associated Requirements Approve Hiring
Manager
System displays a list for:
Department Budget (read-only field) Hardware Total (read-only field; run-ning total calculated from selections) Software Total (read-only field; run-ning total calculated from selections) Remaining Budget (read-only field; running total calculated from sub-tracting the total costs from the Department Budget)
System displays a repeating struc-ture listing the selected hardware and software items:
Hardware (read-only field) Price (read-only field) Software (read-only field) Price (read-only field)
System displays an Approve button to approve the request and an optional Note text box. Note (optional; entry note box) Hiring Manager optionally enters a note and clicks the Approve button.
Name: ER002_Calculate_Cost Details:
System should calculate the cost of selected items during the process. Importance:
2 - Very Important
Name: ER003_Calculate_Remainder Details:
System should calculate the remaining budget (where remaining budget is the department budget minus the equip-ment total cost).
Importance: 2 - Very Important
Name: ER004_Add_Note Details:
System should enable a manager to add a note to the equipment request.
Importance: 4 - Desirable
Shape Actor Use Case Description Associated Requirements Reject Hiring
Manager
System displays a list for:
Department Budget (read-only field) Hardware Total (read-only field; run-ning total calculated from selections) Software Total (read-only field; run-ning total calculated from selections) Remaining Budget (read-only field; running total calculated from sub-tracting the total costs from the Department Budget)
System displays a repeating struc-ture listing the selected hardware and software items:
Hardware (read-only field) Price (read-only field) Software (read-only field) Price (read-only field)
System displays a Reject button to reject the request and a Rejection Note text box to record the reason for the rejection.
Rejection Note (entry note box; required)
Hiring Manager enters a rejection note and clicks the Reject button.
Name: ER002_Calculate_Cost Details:
System should calculate the cost of selected items during the process. Importance:
2 - Very Important
Name: ER003_Calculate_Remainder Details:
System should calculate the remaining budget (where remaining budget is the department budget minus the equip-ment total cost).
Importance: 2 - Very Important
Name: ER004_Add_Note Details:
System should enable a manager to add a note to the equipment request.
Importance: 4 - Desirable
Update Status
System System automatically updates the status of an Equipment Request as required.
7. Perform the following steps on the first shape (Select Hardware) to capture the atomic use case, as well as the relevant requirement for that shape. After you complete these steps on the first shape, repeat the steps for the remaining shapes according to the preceding table.
Note: If your V6.1 SP2 system has had hotfix HFix-3278 installed, the window and fields in which you enter the use case and requirements information look slightly different from what is stated in the following steps and shown in the images. If your system has HFix-3278 installed, the window has more than two tabs. In that
case, enter the appropriate use case information on the Details tab and the use case descriptions on the Description tab (instead of on the Use Case tab as stated in the following steps).
a. Double-click the shape. After a few moments (depending on the speed of your network), the Details window opens.
b. Enter the relevant information on the Use Case and Requirements tabs using the following steps: i. On the Use Case tab:
l Confirm that the Shape field is set toHuman Based Step(the default value). In this step, the HR Staff Member selects the hardware items.
l Confirm that the Use Case field is set to the shape label (the default value). For the first shape, the value should beSelect Hardware.
The system uses the shape label as the default for the use case name. Globex's subject matter experts have agreed to use these default use case names.
l Confirm that the Status field is set toNew(the default value).
l In the Actors field, specifyHR Staff Member. To use the autocomplete feature, type the first letter (H) into the field and press your keyboard's down arrow key. The system displays the available choices. (The choices for actors are the ones you entered pre-viously. Click theHR Staff Memberchoice to select it from the displayed choices. l Confirm that the Use Existing Sub Process field is set toNone(the default value). l Confirm that the Trigger field is empty (no value) and the Complexity field is set to
Low. (The complexity values of the captured use cases are used in the Application Pro-filer to calculate project sizings for developing the project. This is not a concern in this tutorial scenario, so retain the default value.)
l In the Business Objective field, select theAutomate the approval process for employee onboarding requestschoice.
l In the Description field, enter the description of theSelect_Hardwareuse case: System displays a repeating structure with one row per item selected:
Hardware(drop-down list) Price(read-only field)
i. On the Requirements tab:
l In the Name field, enter the name for the requirement associated with this use case (ER001_Create_ER). Note that the autocomplete in the Name field does not display any choices because this requirement has not been previously entered into the system. Click the Expand icon ( ) to the left of the field to display the editor field. Enter the requirement's details in this field:
System should enable an employee to create an equipment request.
l Confirm that the Category field is set toBusiness Rule(the default value).
l For the Importance field, selectCritical(as indicated in the preceding table for this requirement).
l Confirm that the Status field is set toNew(the default value), and that the External Req ID field is empty (the default).
In the Discovery Map, the Select Hardware shape now has a document icon, which indicates a use case description is captured and associated with that step.
8. To save the work you have completed in the profile up to this point, selectActions > Save.
9. For each of the remaining shapes, repeat the previous steps to associate their use cases and requirements. You can copy text from the table and paste it into entry fields.
Note that once a requirement has been entered in the system for a previous use case, you do not re-enter its information to associate it with a use case. Use the autocomplete feature to select the previously entered requirement: type the first letter in the Name field (E) and press your keyboard's down arrow. The system dis-plays the previously entered requirements for you to select from. For example, when entering the requirement for the Select Software shape, after typingEinto the Name field and pressing the down arrow key, the sys-tem displaysER001_Create_ERas a choice. After clicking that choice, press your keyboard's Tab key to move your cursor to the next field. After a moment (depending on the speed of your network) the system auto-matically fills in the Importance and other fields with the previously entered information forER001_Create_ ER. (Depending on the speed of your network, this might take a few moments to display.)
Some use cases have more than one requirement associated with them. To add additional requirements in the Requirements tab, click to add a new row for entry.
For the two Update Status shapes, in the Shape field, selectAutomated Step(instead of the default Human Based Stepvalue).
After entering the use cases and requirements information, confirm that all of the shapes in the Discovery Map dis-play the document icon and that the two Update Status shapes are yellow. The Discovery Map should look like the following image.
Save the profile by selectingActions > Save. Continue to the next tutorial topic.
Part C: Complete capturing information in the
Appli-cation Profiler
The Globex subject matter experts inform you that they want the first use case that they identified captured as the use case for the starting screen of the process, because they want the system to display the fields to enter that infor-mation when the HR Staff Member begins the process.
1. Select the drop-down menu next to the Start Equipment Request label and selectAdd > Use case for start-ing screen.
2. In the window that opens, specify the following items in the fields on the Use Case tab:
Field Specified value
Use Case Enter New Hire Info
Status New
Actors HR Staff Member
Trigger Web Browser
(Use the SmartPrompt to select the value by putting your cursor in the field and pressing your keyboard's down arrow. The system displays the available choices. Double-click Web Browser to select it for the field.)
Complexity Low
Business Objective Automate the approval process for employee onboarding requests
Description When the HR Staff member selects to start the process, the system displays fields for entering the information about the new hire.
HR staff member enters the following information about the new hire: First Name (entry field)
Last Name (entry field) Department (drop-down list) Manager (entry field)
3. Click the Requirements tab. In the Name field, use the autocomplete to select theER001_Create_ER requirement and press your keyboard's Tab button to move to the next field. After a few moments, the sys-tem fills in the previously specified values for the remaining fields.
4. Click OK in the window to save the use case.
At this point, you have captured all of the details for the process-related requirements of the project. Each step of the Application Profiler is designed to capture details of the project related to a specific area. These steps are listed along the left side once you start the Application Profiler. For example, the Integration step is for capturing details of connections to external systems the application would have to make, the Reports step is for capturing details of the types of reports expected from the application, and the Project Roles step is for capturing estimates of the staffing resources needed for the project.
While larger-scale projects would likely require you to enter information for all of these areas of the project, it is not needed for this Globex scenario, and you can move directly to the Profile Review part. (Note that even though this project is for a simple process and the use cases and requirements have been kept intentionally simple, larger-scale projects would follow this same progression of steps.)
5. Click Profile Review in the Application Profiler's left side navigation.
The display shows the work type you specified in the Application Profiler, as well as supporting types typ-ically used in a Process Commander application. (The system includes these by default.) You can optionally expand theEquipmentRequestwork type and see the list of use cases you entered.
6. Click the Finish button to complete creation of the application profile.
The system works to generate the data it needs to create the application profile object. Once the system is done, the profile is completed and the completion window displays.
Optional: Create a Word document of the information in the created application profile that can be circulated to stake-holders by selectingActions > Document. In the Document window, click Create Document. If you have Microsoft Word on your local system, the program opens and displays the application profile document. You can save a copy to your local system, or close Word without saving. When you are done reviewing the document, close the Doc-ument window.
Typically the application is generated at this point. However, for this tutorial, move to Step 2 and complete Step 2 before generating the application. Click Close to close the Application Profiler and complete this step of the tutorial. Continue to the next tutorial topic.
Review
In this step, you created a profile for the Onboarding application by running the Application Profiler. You created a Discovery Map that inventories the steps of the business process that the application is to implement, and you entered information about the use cases and associated requirements.
To read more about the skills you used in this step, see: l Implementation and Methdology - Getting Started( ) l Business Analyst Resources overview( )
l About Direct Capture of Objectives [KB 26133]( ) l Creating an Application Profile [KB 26128]( )
In the next step of the tutorial, you generate a starting application structure based on this profile. Move to the next step in the tutorial.
Step 2: Generate the base application
Typically performed by In the previousstep, you
Purpose of this step
To... So that...
Business Analysts, with assistance from System Architects (SAs)
Built the application profile
Record your decisions about names and the pri-mary process
From the application profile, the Appli-cation Accelerator can automatically generate rules that provide a solid base starting point for later steps
This tutorial step generates the base application structure, using the information that you captured with the Appli-cation Profiler. In subsequent tutorial steps, from that base, you build out and customize the appliAppli-cation to the organ-ization's specific needs.
Generating a base application using the Application Accelerator is the second step in creating a Process Com-mander application. The Application Accelerator takes the profile created by the Application Profiler and turns it into a working application. It automates building a specific application by generating a base starting structure that you can extend with requirements for a specific implementation.
In this tutorial step, you run the Application Accelerator, customize some details for the specific implementation of an application for requesting new hire equipment, and generate the base application.
At the end of this tutorial step, a working application is created in the system. Continue to the next topic to begin this step of the tutorial.
Part A: Running the Application Accelerator
The Application Accelerator generates a basic application structure automatically from the application profile you created at the end ofStep 1.Cof this tutorial. The structure provides a starting point for later tutorial steps. The fol-lowing steps describe customizing some of the information from the profile to better align with the Globex team's expectations, and then generating the base application.
1. In the Designer Studio, start theApplication Accelerator1by selectingNew Application > Application Acceleratorfrom the Application menu.
2. In the Application Overview window that opens when the wizard starts, click the Select the Application Pro-file field and select the entry that starts withProfile for Onboarding. That entry is the application pro-file created inStep 1.Cof this tutorial.
The Application Overview window refreshes to display the default values from the profile. 3. In the New Implementation Name field, change the default value toEquipReq.
1The Application Accelerator is a wizard that integrates with an Application Profile to launch an automated, best-practice process that jump-starts the creation of new application and the extension of existing applications and frameworks.
4. Confirm the following values in the Application Overview window: l Framework Name isOnboardingFW
l Both Version fields display01.01.01
l Business Objectives displays the two business objectives you entered inStep 1.Aof this tutorial. 5. Click OK to save the changes.
6. By default, the Application Accelerator begins on the Base and RuleSets step. In this step, the system dis-plays default names based on the values from the application profile created inStep 1.Cand the GLBX organ-ization structure. For this tutorial, these default values should be used. Confirm the following settings:
l Parent Class isOnboardingFW l RuleSet Name isOnboardingFW
l Organization Name isGLBX.comand Organization Class is
GLBX-l Division Name isGLBXDiv, Division Class isGLBXDiv-, and Division RuleSet is GLBXGLBXDiv
l Application Class isEquipReqand Application RuleSet isGLBXEquipReq l Modify test operators checkbox is clear
Step 1.Bis displayed.
At this point, for a larger application, the business analyst would typically work with the subject matter experts to provide information to update the other areas of the Application Accelerator before generating the base application. In this tutorial scenario, the system provides default selections on the other steps based on the information from the profile that you created earlier and entered in the preceding steps. No further updates are needed before generating the base application structure.
8. Select the Review Objects step and confirm that the displayed use cases and requirements match the fol-lowing images. These are the use cases and requirements you entered into the Application Profiler inStep 1.Bof the tutorial. Expand theEquipmentRequestwork type to display the use cases.
Select the Requirements tab to see the requirements.
9. Select the Create Application step. In this step, the system displays a list of the rules that the system will generate for the starting structure.
10. Click Build the Application.
As the system creates the rules and classes for the application, progress is indicated in theStatuscolumn by the clockwise circling arrows ( ). When the Status column displays all check marks and the Finish button is available, click Finish.
11. Click the Switch to new application button that appears.
The system refreshes the Designer Studio window to display the newly generated OnboardingFW application.
As part of this process, the Application Accelerator updated [email protected] ID to set OnboardingFW as its default application. From now on, whenever you log into the system using
Continue to the next tutorial topic.
Review
In this step, you generated a starter structure for the Onboarding application by running the Application Accelerator, using information in the profile that you previously created.
To read more about the skills you used in this step, see:
l Introduction to the SmartBPM Implementation Methodology [KB 25665]( ) l Business Analyst Resources overview( )
l About the Direct Capture of Objectives [KB 26133]( ) l Using the Application Accelerator [KB 26129]( )
Because this is a starter application that you will extend to meet your stakeholders' needs, it's best to review the gen-erated items to gain an understanding of what was created. In the next step of the tutorial, you review the gengen-erated items.
Step 3: Review the application structure
Typically performed by In the previousstep, you
Purpose of this step
To... So that...
Lead System Architects (LSA)
Generated a base application structure
Build upon the RuleSets generated in the previous step and familiarize you-self with the generated base structure
You are familiar with assets gen-erated in the previous step and have the appropriate RuleSet prerequisites for creating and saving rules as you build out the process (screens, flow, logic) in the subsequent tutorial steps
This step builds upon the baseGLBX-FW-OnboardingFW-Workapplication structure that was generated in the pre-vious step. You explore the generated application structure, and set the prerequisites for the RuleSet into which new rules are saved as you create them in the application development process.
The Application Accelerator that you used in Step 2 created your application and populated it with a structure and assets that promote efficient development and reusability. For this tutorial, you also need to connect the RuleSet generated by the Application Accelerator with one that you imported before beginning the tutorial. That step would not be necessary in a real business setting.
In this step of the tutorial you:
l Update theOnboardingFWRuleSet to add the GLBX RuleSet as a prerequisite and turn off “in / check-out” of rules.
l Review the class structure created for your application by the Application Accelerator. l Review the rules the Application Explorer created for your application.
l Use the Heat Map to review your application’s assets. Continue to the next topic to begin this step of the tutorial.
Part A: Update the OnboardingFW RuleSet
The RuleSets generated by the Application Accelerator have rule check-out specified by default. This is the default setting because in a typical development effort involving more than one person, it is important to enforce rule
check-out. If Developer A has checked out a rule, Developer B cannot make changes to it until Developer A has checked it in again. Rule check-out helps prevent colleagues from accidentally overwriting each others’ work.
In this tutorial scenario, the work is done on your own. Turning off rule check-out for the RuleSets into which one saves rules reduces the number of steps involved each time one wants to create or update a rule. In this tutorial, rules are saved to theOnboardingFWRuleSet.
Rule check-out for the rules in a RuleSet is governed by a checkbox on the RuleSet form. The following steps describe turning off rule check-out in theOnboardingFWRuleSet:
1. In the Application Explorer under GLBX-FW-OnboardingFW-Work, expand the SysAdmin category and then expand the RuleSet category to see the list of RuleSets:
l GLBX l GLBXInt l OnboardingFW l OnboardingFWInt
2. Click OnboardingFW to open its rule form.
Even though there are four RuleSets in this application, check-out is turned off for only the OnboardingFW RuleSet. The reason is that this is the only RuleSet in which rules are saved in the course of performing the steps of this tutorial. Because the steps of the tutorial do not involve updating or saving rules into the other three RuleSets, their check-out settings can be left as they are.
3. Click theSecuritytab and clear theUse check-out?checkbox.
Before beginning Step 1 of the tutorial, you imported some Process Commander resources that set up the GLBX organization and operators for the tutorial scenario. One of those resources is the GLBX RuleSet. So that the rules that you save to the OnboardingFW RuleSet can use rules in the GLBX RuleSet, you must add the GLBX RuleSet as a prerequisite to the OnboardingFW RuleSet.
4. Click theVersionstab.
5. Click the Expand icon ( ) at the left of the01-01-01to view the Required RuleSets And Versions sec-tion.
6. Click that is within the Required RuleSets And Versions section to add a new row after the two exist-ing rows.
7. In the new row, use theSmartPrompt1to choose from the list of available RuleSets: a. Set your cursor in the entry field in the new row.
b. Press your keyboard's down arrow key. The system displays a list of appropriate choices.
c. Scroll down through the list until you see GLBX, then double-click GLBX to select it for the entry field. 8. Type a colon (:) and01-01-01after GLBX in that row. The new row should look like the following image.
1A SmartPrompt text box, used on many rule and data forms, makes a dynamic selection list available for fast user entry. Optionally, SmartPrompt processing can be added to fields on work object forms.
9. Click to save the updated OnboardingFW RuleSet.
10. Close the form for the OnboardingFW RuleSet by clicking the icon in its tab.
Continue to the next tutorial topic.
Part B: Review the class structure
Classes represent the applicability, or scope, of rules such as properties, sections, and flows. Your application is a hierarchy of classes, with more specific classes inheriting from more generic classes. In general, if there is a rule in a generic class in your application, and a rule of the same name in a more specific class that inherits from the first class, the rule in the more specific class is the one the application uses. Your application cannot use rules that are not part of the classes in its hierarchy.
Use the Application Explorer in the left panel of the Designer Studio to review your application’s class structure. Your application’s class hierarchy includes classes created by the Application Accelerator and standard classes pro-vided by Process Commander (as well as any standard classes from Frameworks your application uses). Most rules operate on ("apply to") objects of a specific class. However, rules that apply to a parent class are also available to child classes of that parent. In your application, objects in theEquipmentRequestchild class have access to the rules in its parent class.
Right-clickEquipmentRequestand selectStructurefrom the context menu to open the Class Structure Viewer and see the relationships among all the elements of your application.
Use the + and – icons in the Class Structure Viewer to explore the relationships. The full name of the Equip-mentRequestclass isGLBX-FW-OnboardingFW-Work-EquipmentRequest. This class is a direct child of GLBX-FW-OnboardingFW-Work-, which is a child ofGLBX-FW-OnboardingFW-, and so on. The top class in the hierarchy is named@baseclass.
Close the viewer. Right-clickEquipmentRequestagain, and selectInheritanceto open the Class Inheritance display and see the inheritance relationships among all the classes in your application.
Close the Class Inheritance display. Continue to the next tutorial topic.
Part C: Review the rules generated by the Application
Accelerator
Along with the application’s class structure and starter flows, the Application Accelerator creates RuleSets to hold the rules your application requires. In the Application Explorer, use the + and – controls to navigate the tree display and review the rules, RuleSets, and RuleSet versions that the Application Accelerator created.
During the following tutorial steps, you modify some of these generated rules and create others as you build out the application to match its requirements.
Continue to the next tutorial topic.
Part D: Use the standard heat map to review the number
and types of rules in the application
A heat map provides another way of visualizing your application’s assets. Select > Application > Inventory > Heat Mapto see the heat map.
(The arrangement of rectangles that you see might not precisely match the following image. Narrowing the Designer Studio window changes the display.)
Note: If you did not complete Steps 1 and 2, and instead imported the zip file at the start of this tutorial step, the number of rules is different than the one shown in this image.
Click the label of any rectangle to see a list of its contents.
Heat maps color the rectangles according to a stated criterion to provide additional information. You can choose a criterion in theShaded bydrop-down list. The heat map typically shows, by color gradation, the number of recently updated rules in each category rectangle.
Close the heat map (click in the Application-Inventory tab). Continue to the next tutorial topic.
Review
In this step you reviewed your application's structure and underlying items, and optionally simplified the devel-opment process by turning off rule check-in/check-out behavior.
To read more about the skills you used in this step, see: l How class inheritance works [KB 25169] ( )
l Video overview of the Enterprise Application Accelerator( )
l Application category - Inventory page - Inventory Reports, 6Rs, and Heat Map gadgets [Developer Help]( ) In the next step of the tutorial, you adjust the draft flow generated by the Application Accelerator.
Step 4: Adjust the initial process
Typically performed by In the previousstep, you
Purpose of this step
To... So that...
Business Analysts Specified appropriate settings for the default RuleSets gen-erated in Step 2 and explored the gen-erated application structure.
Revise and extend the process in the default flow
The process begins to look more like the business process desired by the stakeholders, and you can run it for them to get their feedback
This step builds upon the baseStart Equipment Requestprocess that was generated inStep 2. You customize some of the process defaults until it reaches a point where stakeholders can review it and provide useful feedback on its development.
After the Application Accelerator generates the application structure, the business analyst can run the process (as defined in the Discovery Map) immediately, and give stakeholders the opportunity to review the working process and user interface, without waiting for all of the pieces to be developed. Early reviews let stakeholders verify that the process satisfies the project's business requirements. The stakeholders can validate that the application is devel-oping as they expect, and the developer can quickly incorporate stakeholder feedback.
As you saw inStep 3, generating the application using the Application Accelerator creates a base structure for the application. The goal is to extend this generated base to deliver an application that meets the project’s requirements and objectives. One of the generated rules is a draftflow1. The Application Accelerator uses the process steps you created in the Discovery Map to create this rule. This tutorial step describes how to run the process, and then adjust the draft flow to have the process align more with the Globex team's expectations.
Continue to the next topic to begin this step of the tutorial.
1A flow defines a business process or part of a business process. A flow governs how work objects are created, progress through the system, and become resolved. A flow consists of a network of shapes and connectors (lines), each with associated parameters and values.
Part A: Run the process
The goal of running the process at this point in the project is to see what might need adjusting to better meet the expectations of the subject matter experts and stakeholders.
1. In the Designer Studio, select the Run ( ) menu from the toolbar, and select Run Process.
The words you entered in the Application Accelerator for the process -- Start Equipment Request -- appear as the first part of the label of the menu choice.
2. Select the menu choice that begins with the words Start Equipment Request to run the initial process that was generated by the Application Accelerator.
As you progress through the process, temporary messages ("nn system alerts") might appear. These mes-sages support performance tuning and you can ignore them.
The system presents the user interface screens that are in the base structure created by the Application Accelerator. A new tab is opened in the Designer Studio for the new work item. Click Create in the first screen and Submit in the subsequent screens to advance through the process. You do not have to enter any values in the fields.
3. As you progress from one screen to another by clicking Submit, observe the following items:
l The screens generated by default follow the steps you set in the Discovery Map, and use the names you entered on the shapes. By running the process at this point, you can quickly see whether the
process follows the steps provided by the Globex subject matter experts.
l Text in some of the screens indicates that certain items do not exist (such as "Flow Action does not yet exist."). The steps in the next tutorial topic address these items.
l The final screen of the process shows a confirmation message: "Thank you for your input". Notice that the work item's status is set to New. Because this is the primary path of the process and the work item is not being sent to another process, you want the work item's status set to Resolved at this point. That is, you would like the work item's status in the header to reflect that all of the required ele-ments of the work are complete ("resolved"). You would also like the work item's status to change from New to Pending-Approval as it moves to the Approve process step.
4. Close the tab for the work item by clicking the icon in the tab.
Part B: Edit the flow
The following steps describe editing the generated flow so that the items noted in the previous topic are addressed. 1. In the Application Explorer, expand EquipmentRequest to see the rule categories underneath it. Expand the
Process category and then expand the Flow category. Click StartEquipmentRequest.
2. Click theFlow Editor1icon ( ) to open the flow in the flow editor. The flow editor uses Microsoft Visio. You might be prompted to enable macros in Visio. If so, select to enable macros.
3. In the displayed flow diagram, observe the following items:
l The flow is in draft mode. You can tell when a flow is in draft mode by the yellow rectangle with the word Draft at the top of the flow diagram. Draft mode allows you to work with shapes in the flow with-out having to create all of the underlying rules for the shapes.
l The shapes from the Discovery Map that are specified as Human Based Steps (green shapes) are rep-resented as assignment shapes in the flow diagram.
l The Discovery Map shapes that are specified as System Steps (yellow shapes) are represented as utility shapes.
l The Discovery Map shapes that are specified as alternate steps (Reject and Update Status) appear in a separate branch.
4. Click to save the flow with the flow diagram. After the system completes saving the flow, a warning ( ) shape might appear in the diagram. This image marks where a shape's required values or underlying rules are incomplete. When a flow is saved, the system validates whether rules exist for each shape in the flow. Ignore any ( ) warnings that appear at this point, because the missing rules are created in the following steps of this topic.
5. Create flow action rules for the locations in the running process where the user interface is displaying "Flow Action does not yet exist" by following these steps:
a. Select the connector that runs between the SelectHardware shape and the SelectSoftware shape. The Connector Properties panel displays in the upper left corner.
b. In the Connector Properties panel, enterSelectHardwarein theFlow Actionfield. Do not use spaces in this field, because this value is the flow action rule name, which does not allow spaces.
c. Click next to the Flow Action field. In the New Rule dialog for the flow action, confirm the following values:
o Applies ToisGLBX-FW-OnboardingFW-Work-EquipmentRequest o Action NameisSelectHardware
o RuleSetisOnboardingFW o Versionis01-01-01
o Templateis blank (the default)
d. Click Create to create the flow action rule.
e. Click to save the SelectHardware flow action. Then click in its tab to close that tab.
f. In the Connector Properties panel in the flow editor, do not change any other values in the other fields in the panel. Click Apply in the Connector Properties panel. (Ignore the warning next to theFlow Actionfield. This warning clears the next time you click to save the rule and the system validates references to the new SelectHardware flow action rule.)
g. Repeat steps 5.a through 5.f for the connector that runs between the SelectSoftware shape and the Approve shape. EnterSelectSoftwarein theFlow Actionfield, and confirm the following values in the New Rule dialog for the flow action:
o Applies ToisGLBX-FW-OnboardingFW-Work-EquipmentRequest o Action NameisSelectSoftware
o RuleSetisOnboardingFW o Versionis01-01-01
o Templateis blank (the default)
Remember to save ( ) the new SelectSoftware flow action rule.
Connector Properties panel, use the SmartPrompt in theFlow Actionfield to see the list of available flow action rules. The first choices displayed by the SmartPrompt are the two flow actions just created, SelectHardware and SelectSoftware. Double-click theMorein the SmartPrompt list to see the list of standard flow action rules. Double-clickApproveto select it for theFlow Actionfield.
i. Click Apply.
6. When the process first creates the work item, the work item's status is set toNew. Adjust the flow to set the status of the work item toOpenas it enters the first assignment (Select Hardware) and toPending-Approval
as it enters the Approve step.
a. Select the Select Hardware assignment shape.
b. In the Assignment Properties panel, use the SmartPrompt in the StatusWorkfield to select the stand-ardOpenstatus value. (You might have to expand the Assignment Properties panel to see the field labels and locate theStatusWorkfield). Click Apply.