BPMSandbox.com HandsOnExercise 2 BuildFromScratch BH V1

7/29/2019 BPMSandbox.com HandsOnExercise 2 BuildFromScratch BH V1

1/130

IBM Software

IBM BPM in Action! Using WebSphere Lombardi Edition Build-from-Scratch Exercise (http://BPMSandbox.com) Page 1

IBM BPM in Action using WebSphere Lombardi Edition

Build-from-Scratch Hands-on Exercise

This lab will guide you through a Build-from-Scratch process for WebSphere Lombardi Edition (LombardiEdition) using the Lombardi Authoring Environment. The intent is to let you experience the developmentprocess in Lombardi Edition. The process you will develop in this lab is an HR Request head count process.

Recommended Approach:

1) Goto http://BPMSandbox.comand Watch the YouTube Demo Videos for this exercise, or Download thefull-length video here: http://tinyurl.com/BPMSandboxVideosas seen below.

2) Come back here and do Sections 1.1-1.2 and as much of the rest as you would like.

The YouTube Demo Videos for the Extended Build-from-Scratch exercise are on http://BPMSandbox.comand look like the graphic below.

You can also download the full-length video here:http://tinyurl.com/BPMSandboxVideos


2/130

IBM Software

Page 2 IBM BPM in Action! Using WebSphere Lombardi Edition Build-from-Scratch Exercise (http://BPMSandbox.com)

TableofContents1.1 START THE ENVIRONMENT......................................................................................................... 31.2 CREATE THE FIRST EXECUTABLE VERSION OF THE PROCESS ....................................................... 4

1.2.1 CREATE THE PROCESS APPLICATION ............................................................................ 41.2.2 CREATE THE BUSINESS PROCESS DEFINITION................................................................ 51.2.3 RUN THE PROCESS .................................................................................................... 101.2.4 RUNNING THE PROCESS FROM THE LOMBARDI PROCESS PORTAL ................................ 141.2.5 TAKE A SNAPSHOT OF THE BASIC PROCESS ................................................................. 21

1.3 ADDMORE DETAILS TO BASE PROCESS .................................................................................. 231.3.1 ADD ADDITIONAL PROCESS LOGIC TO BASE PROCESS .................................................. 231.3.2 SET THE DEFAULT FLOW OF A DECISION GATEWAY....................................................... 371.3.3 TAKE A SNAPSHOT OF THE PROCESS CHANGES ........................................................... 40

1.4 DATA TYPES AND USER INTERFACES ....................................................................................... 411.4.1 ADDDATA TYPES ...................................................................................................... 411.4.2 CREATE USER INTERFACES USING THE ACTIVITY WIZARD ........................................... 461.4.3 USE THE COACH DESIGNER TO DESIGN A COACH (USER INTERFACE) ........................... 511.4.4 CREATE A SCREEN FLOW ........................................................................................... 631.4.5 ADD SYSTEM ACTIVITIES TO THE SCREEN FLOW........................................................... 781.4.6 ADD DROP-DOWNS AND MAKE FIELDS NOT-EDITABLE AND REQUIRED ............................ 841.4.7 TAKE A SNAPSHOT..................................................................................................... 91

1.5 MANUALLY CREATE A HUMAN SERVICE &CONFIGURE DECISION GATEWAY ................................. 911.5.1 CREATE A HUMAN SERVICE MANUALLY ....................................................................... 911.5.2 ASSOCIATE A HUMAN SERVICE TO AN ACTIVITY ......................................................... 1051.5.3 MODIFY A DATA TYPE AND SET OUTPUT MAPPING OF AN ACTIVITY.............................. 1071.5.4 CONFIGURE THE DECISION GATEWAY........................................................................ 1111.5.5 TAKE A SNAPSHOT................................................................................................... 120

1.6 SNAPSHOTS ......................................................................................................................... 1211.6.1 EXPLORE SNAPSHOTS ............................................................................................. 1211.6.2 SNAPSHOTS AT A LOWER-LEVEL ............................................................................... 126


3/130

IBM Software


1.1 Start the environment

In this section, you will start the Lombardi Authoring Environment, which is the authoring tool for BPM analystsand developers.

If you already started the Lombardi Authoring Environment, skip step #1.

__1. Start Lombardi Authoring Environment

__a. If you are using the POT VMWare, the Lombardi Authoring Environment should have beenstarted automatically. If you are not using the POT VMWare, then:

__i. Find the Lombardi Authoring Environment icon on the desktop and double-click it.Be aware depending on the hardware the image is running on it might take a fewminutes to start:

__b. Login with User Name oftw_admin and password oftw_admin, then click Login

If the Startup Assistant opens, selectBegin using WebSphere Lombardi Edition


4/130

IBM Software


Once the Lombardi Authoring Environment opens up, you will see a list of process applicationsdeployed in the Process Center.

1.2 Create the first executable version of the process

In this section, you will create the first executable model of a basic HR Request Headcount process. A

fundamental benefit of Lombardi is that the process is always executable. This means that at any time you canhit play to run the process allowing you to iteratively uncover requirements and validate the implementation.

The main point of this section is that you create an executing process very quickly. Subsequent sections, andfuture labs, reveal more and more details.

1.2.1 Create the process application

The first step will be to create a process application for the HR Request Head Count process. ProcessApplications are containers for the process models and supporting implementations that BPM analysts anddevelopers create in Lombardi Authoring Environment. In general, you will create a Process Application foreach business process to be automated using Lombardi Edition.

__2. Click Create New Process App


5/130

IBM Software


__3. In theCreate New Process App wizard, enter the following:

__a. Set Process App Name to HR Request Headcount

__b. Set Acronym to HRRHC

__c. ClickCreate

Process Acronyms

The acronym for a process application must be unique andis limited to seven characters (you are prevented fromentering invalid characters). Advanced process authors canuse the acronym as a unique identifier to distinguishreusable assets that share a common name.

__4. Open the HR Request Headcount process application:

__a. In the Process Center, find the process application and then clickOpen in Designer

1.2.2 Create the business process definit ion

In this section, you will create a basic HR Request head count process with a couple of activities. To model aprocess, you must first create a Business Process Definition (BPD). A BPD is a reusable model of a process,

defining what is common to all run-time instances of that process model.


6/130

IBM Software


__5. Create a BPD named Project Execution

__a. From the process library, hover overProcesses and select the plus ( ) icon

__b. In the Create New wizard, select Business Process Definition

__c. Set the Name to Request Headcount

__d. ClickFinish

__6. By default you get a process with two swim lanes and a Start Event and an End Event. There isnothing special about these two default components.


7/130

IBM Software


__7. Drag two activities from the palette onto the canvas

In Lombardi Edition, when you select a component on the diagram, the properties of that componentare displayed in the bottom portion of the screen. We will now rename the two activities to something

more meaningful.

__8. Set the properties of the first activity.

__a. Click on the first activity

__b. View (or click on) the Properties at the bottom

__c. View (or click on) the Step sub-tab

__d. UnderCommon, set the Name to Request Headcount


8/130

IBM Software


__9. Select the second activity, and follow similar steps to rename the second activity,Approve HCRequest

In Lombardi Edition, drawing lines is a bit different: instead of a click-drag-release to draw a line, yousimply click twice: click once to start the line and click a second time to end the line.

__10. Wire the components together

__a. Click the Sequence Flow icon in the palette on the right-hand side

__b. Click once on the Start component. Note: the closest blue dot to your click is used - you doNOT have to click directly on the blue dot.

__c. Move your mouse overRequest Headcount and click a second time.


9/130

IBM Software


Selection Tool

The Selection Tool enables you to select andmove components on the diagram.

Sequence Flow

The Sequence Flow enables you to connectprocess components to establish the order in which thesteps in the process occur.

__11. Now repeat similar steps to wire Request Headcount to Approve HC Request and Approve HCRequest to End.

Tip: Aligning components of a BPD

To nudge components so that the BPD lines up, click onthe component(s), and then use the arrow keys to nudgethe component(s).


10/130

IBM Software


1.2.3 Run the process

In Lombardi Edition, the diagram is the process. Therefore, right away we can already run this basic processwe have diagramed.

__12. Run the process by clicking Run Process

__13. Save the process. When you tried to run the process without saving the changes, Lombardi Editionwarns you that you have unsaved changes.

__a. At the Save Process? prompt, click Yes

__b. If you get a prompt to Switch Perspective?, click Yes. The reason for the prompt is that theprocess has reached a point where it needs some human interaction.


11/130

IBM Software


__14. The process Inspector provides a testing and debugging environment.

Section Description

1 Shows that you have one process instance running.2

Shows that associated with the process instance in #1, there is a taskassociated with it.

3 The diagram shows where you are in the process.


12/130

IBM Software


__15. Run the first task:

__a. Click the process instance in #1

__b. Click the task in #2 (highlighted)

__c. ClickRun

__16. Pick a user to run the task:

__a. At the Pick User From Role prompt, select tw_user(you can press t a couple times until youget to tw_user)

__b. ClickOK

__17. Enter the users password.

__a. At the Enter Password for tw_userprompt, enter their password, which is the same as theirusername: tw_user

__b. ClickOK


13/130

IBM Software


__18. Save the password so that you dont have to retype it later.

__a. At the Remember password prompt, check Remember decision

__b. ClickYes

__19. A browser will open up with a default screen even though we have not implement any business data,specific screens, etc. The default screen shows information about the instance and task.

__a. To complete this task, click Done.

__20. You will see a message that the service has finished.

__a. Close the browser. When users run the process from a portal, they do NOT have to manuallyclose the browser window (you will see this shortly).


14/130

IBM Software


__21. Back in the Inspector, click the Refresh icon (in the upper right above the list of tasks) to see whereyour process has advanced.

__22. You can see in the diagram view that the process has now moved on toApprove HC Request.

Takeaway from this section

J ust by drawing the picture, the process is executable, it runs and not just from this process Inspectorenvironment, but also from the Process Portal. You will see the process running from the Process Portal in thenext section.

1.2.4 Running the process from the Lombardi Process Portal

In this section, you will run the basic process you diagramed in the earlier section in the Lombardi ProcessPortal. The Lombardi Process Portal Provides an interface that enables process participants to performassigned tasks, view the history of tasks, and view the performance of their processes and teams. UsingLombardi Process Portal, process participants can connect to the Lombardi Process Center Server or a

Lombardi Process Server in any configured runtime environment, such as test or production environments.


15/130

IBM Software


__23. Double-click the Lombardi Edition program links on the desktop.

__24. Click Lombardi Process Portal


16/130

IBM Software


__25. Login to the Lombardi Process Portal as tw_user. At the Process Portal Login, enter:

__a. User Name oftw_user

__b. Password oftw_user

__c. ClickLogin


17/130

IBM Software


__26. Time Zone warning.

If you are using a VMWare you may notice this time zone message. J ust clickOK and continue withthe lab.

__27. Upon login, you will see a View of tw_users Inbox. At the bottom, find the Request Headcountinstance, and then click it to see its details.

Lombardi Process Portal

This is the out-of-the-box Process Portal. Many of ourcustomers use their existing Portal to display this work list

and then allow users to execute these work items.


18/130

IBM Software


__28. From the task details, select All Tasks so that you can see all tasks, not just the Open tasks.

__29. In the section highlighted in yellow, you can see that you have two tasks associated with this processinstance. One task was already completed: the one you completed from the Inspector and now there isa second open task.

__30. End users can see where they are in the Process Instance, by expanding the Process Diagramsection.


19/130

IBM Software


__31. The process diagram displays visually to end-users where we are in the process flow. If you hoverover the haloed activity, you will see some of the details of the task: Due date, who it isAssigned to,and the Time left to complete the task.

__32. Execute the work item by clicking Run on the open task.

__33. At task assignment prompt, click OK.


20/130

IBM Software


__34. The default screen will open up in a browser. ClickDone to complete the task.

__35. Right-click on the browser to Reload the page.


21/130

IBM Software


__36. The process is now in the Completed state (yellow high-light).

__37. Log Off from the Lombardi Process Portal and close the browser.


The main point for showing the Lombardi Process Portal is to validate that the process runs from the verybeginning. Everything we do now in the Lombardi Authoring Environment will be to add more to the processuntil it does the right thing. This is the fundamental difference in Lombardi Edition as to how customersapproach projects. The process runs from the beginning and it becomes much more of a business decisionwhen does the process do enough of the right things to be valuable.

1.2.5 Take a snapshot of the basic process

In this section, you will take a snapshot of the basic process you have implemented. Snapshots allow you tocapture and save the items in a process application at a specific point in time. Usually snapshots represent amilestone or are used for playbacks or for installation.


22/130

IBM Software


__38. Switch back to the Designer perspective

__a. ClickDesigner

__39. ClickSnapshot

__40. Name the snapshot:

__a. For snapshot name, enterv1.0 Base Process

__b. ClickOK

__41. Notice the snapshot in the lower left of the Authoring Environment, underRevision History.


23/130

IBM Software


1.3 Add More Details to Base Process

In this section, we will make this process a bit more realistic.

1.3.1 Add addi tional process logic to base process

__1. Add another lane to the process

__a. Drag a Lane above the Participant lane, to the top-left most point


24/130

IBM Software


__2. Move the new lane,Untitled1, below the Participant lane.

__a. Click onUntitled1 to select the lane

__b. Position it below the Participant lane

__3. The updated BPD should look like this:


25/130

IBM Software


__4. Rename the Participant lane.

__a. Click onParticipant to select the Participant lane



__d. UnderCommon, set the Name to Requestor


26/130

IBM Software


__5. Follow similar steps to rename Untitled1 lane asApprover.

__6. Move Approve HC Request to the Approver lane.

__a. Click on Approve HC Request, then drag to Approver lane.


27/130

IBM Software


__7. To model the process based on the Approvers decision, add a decision gateway to the process.

__a. Drag a Decision Gateway to the Approver lane.

__8. Drag another activity into the System lane.


28/130

IBM Software


__9. Move the line going into End to the decision gateway. To move a line, click on the end-point and thenmove it to the new location.

__10. Use the Sequence Flow to wire the rest of the diagram.

__11. Add a flow line from the decision gateway to the activity in the System lane.


29/130

IBM Software


__12. Use the Selection Tool to move End to the System lane.

__13. Finish the rest of the diagram.

__a. Draw a flow line from the decision gateway to the Request Headcount.

__b. Draw a flow line fromUntitled1 to End .


30/130

IBM Software


__14. Rename Untitled1 to Update Sys & Notify Recruiter.

__a. Click onUntitled1



__d. UnderCommon, set the Name to Update Sys & Notify Recruiter


31/130

IBM Software


__15. Rename the decision gateway.

__a. Click on the decision gateway



__d. UnderCommon, set the Name to Status


32/130

IBM Software


__16. Rename the flow lines coming out of the decision gateway so that the process will be moreinformative.

__a. Click on the flow line fromStatus to Update Sys & Notif y Recru iter


__c. View (or click on) the Line sub-tab

__d. UnderCommon, set the Name toApproved

__e. CheckName Visible


33/130

IBM Software


__17. Rename similar steps to rename flow line from Status to Request Headcount asRejected.

__18. Here is the revised process model. Click Run to run the process.

__19. Save the process at the Save Process? prompt.

__20. Switch to the Inspector perspective, if you were not automatically switched there.


34/130

IBM Software


__21. Run the first task as tw_user.

__22. At the default screen, click Done.

__23. Close the browser after you see the message that the service has finished.


35/130

IBM Software


__24. Back in the Inspector, click Refresh to see where your process has advanced.

__25. Run the Approve HC Request task as tw_user.





36/130

IBM Software


__29. Because we have not specified any logic for the decision gateway, the process will move back to theflow that was defaulted as the Default flow for the decision gateway.

__30. Run the Request Headcount task as tw_user.





37/130

IBM Software


__34. The current process is at Approve HC Request step and if we do not make process changes, theprocess will continue going back to Request Headcount from the decision gateway.

1.3.2 Set the default flow of a decision gateway

In this section, you are going to change the process model and then continue this in-flight process instance.

__35. Switch back to the Designer perspective by clicking Designer.


38/130

IBM Software


__36. Set the default flow out of the decision gateway, Status.

__a. Click on Status


__c. View (or click on) the Implementation sub-tab

__d. Click the up-arrow next toApproved (Update Sys & Not ify Recru iter) to move this up.

Empty conditions

An empty condition of a decision gateway is alwaysconsidered true.

Decisions are evaluated top-to-bottom and the first one evaluated to true is the path that is followed. This iswhy even though the Default Line was on Approved, the first condition that was evaluated was an emptycondition (true), and therefore the rejected path was followed. The Default Line for Approved was neverevaluated.


39/130

IBM Software


__37. Save your changes by clicking Save

__38. Switch back to the Inspector perspective by clicking Inspector.

__39. Select the in-flight instance, and run theApprove HC Request task as tw_user.





40/130

IBM Software


__43. The process Inspector shows the process instance has now completed. It executed another activity,Approved (Update Sys & Not ify Recrui ter ), automatically because it is in the System lane.


What you just observed is that in-flight instances, in this environment, the development environment, areaffected by changes to this process model.

1.3.3 Take a snapshot of the process changes

In this section, you will take a snapshot of the more realistic process you just developed.


__a. ClickDesigner


41/130

IBM Software


__45. Take a snapshot and name itv1.1 - Process Changes.

1.4 Data types and User Interfaces

In previous sections, you have modeled the process. Now, you will model some of this business data that isflowing through our process.

1.4.1 Add Data types

__46. From Request Headcount, click Variables to switch so that you can add variables to the process.

__47. ClickAdd Pr ivate to add a private variable to this process.


42/130

IBM Software


__48. Set the details of the private variable.

__a. Click on the new private variable

__b. UnderDetails, set the Name to request

__c. For Variable Type, click New

__49. Give the new variable type a name. At the New Variable Type prompt,

__a. Enter Name as HeadcountRequest

__b. ClickFinish

This step has just created a new Data Type / Variable Type in Lombardi.


43/130

IBM Software


__50. Add some parameters to this new variable type.

__a. UnderParameters, clickAdd

__51. Name the first parameter id.

__a. UnderParameters, click on the new parameter, Untitled1

__b. UnderParameter Properties, set the Name to id


44/130

IBM Software


__52. Repeat the previous two steps to add three more parameters of type String: project, requestor, andjust if ication .

__53. Add a new parameter named budget of type Decimal.

__a. Use the same steps to create the parameter and name itbudget

__b. For Variable Type, click Select


45/130

IBM Software


__54. Use type-ahead to narrow down your search list.

__a. Start typing De and you should see the variable type list narrowed down by what you typed.

__b. Select Decimal.

__55. Add another parameter nameddesiredStartDate of type Date.

__56. Review HeadcountRequest parameters and their types. When you are satisfied, click Save.

__57. Close HeadcountRequest by clicking Close.


46/130

IBM Software


__58. Set request to have a Default value. Setting a default value for the variable initializes our object.

__a. UnderDefault Value, check Has Default.

1.4.2 Create User Interfaces using the Act ivity Wizard

Instead of using the default screens, you are going to create some screens (user interfaces) that areimplementation specific to this process and data types you defined. For the first activity, you will use theActivity Wizard to create its user interface.

__59. Switch back to Diagram


47/130

IBM Software


__60. Right-clickRequest Headcount and selectAc tivi ty Wizard

__61. At theAc tivi ty Wizard Setup Acti vi ty prompt:

__a. Keep the default for Service Type, Human Service

__b. Keep the default for Service Selection, Create a New Service

__c. ClickNext >.


48/130

IBM Software


__62. At theActiv ity Wizard Parameters prompt:

__a. Keep the default to use request as an Input and Output parameter

__b. ClickFinish.

By running the Activity Wizard with these selections, it has created a reusable implementation. Note,that the first time you run the Activity Wizard in an environment, it may take some time. Subsequent

uses are much faster.


49/130

IBM Software


__63. Double-clickRequest Headcount.

__64. Note that the generated implementation opened up in the Coach designer, which is used to designscreens for human interaction.

__65. Double-click the Coach.


50/130

IBM Software


__66. The activity wizard went ahead and put the data elements onto the screen. Earlier you saw that wecould run the process from the higher-level process (BPD), but you are not limited to always running

from the higher-level process. In fact, go ahead and run this implementation by clicking Run .

__67. A browser window opens with the data elements that were defined for the screen. Note thatBudgetand Desired Start Date have appropriate control types, Budget, which was a Decimal has a numericcontrol, and Desired Start Date has a date control.



51/130

IBM Software


1.4.3 Use the Coach Designer to design a Coach (user interface)

In this section, you will setup multi-column screens, input boxes with multiple rows, use a flow line to act as aRefresh button, and set some currency formatting.

__69. Select Request by clicking on Request title in blue. You have selected the right section, if you see theblue outline bolded around all its parameters.


52/130

IBM Software


__70. Set the number of Request columns to two.

__a. View (or click on) the Properties at the bottom

__b. View (or click on) the Section sub-tab

__c. UnderBehavior, set # of Columns to 2.


53/130

IBM Software


__71. DragProject to the second column.

__72. Repeat similar steps to dragBudget and Desired Start Date also to the second column.


54/130

IBM Software


__73. Move Justification to its own section. Drag it and move it until you see a shadow under Request andover the button section.


55/130

IBM Software


__74. Set the number of rows for J ustification to four rows. Similar to designing in the BPD, when you selectan element above you get properties for it below.

__a. Select Justification


__c. View (or click on) the Presentation sub-tab

__d. UnderPresentation, set # of Rows to 4.

__75. Look at your changes by clickingRun .



56/130

IBM Software


__77. If you notice the columns are not proportionate.

__a. Leave the browser open while you switch back to the Coach designer to set the column widths


57/130

IBM Software


__78. Set the column widths of Request.

__a. Select Request



__d. UnderColumns, click Column:0

__e. UnderColumn Properties, set Column Width to 50%. By default, the other column will also be50%.


58/130

IBM Software


__79. To reiterate that the picture is the process, you will change the flow line out of the Coach to work as aRefresh button.

__80. Switch back to Diagram

__81. Take the end-point of the flow line out of the Coach and move it from End to loop-back to the Coach.

__82. Click Save to save your changes.


59/130

IBM Software


__83. Go back to the browser, and then clickOk.

Wherever the flow line out of the Coach goes, will be the next step. In this example, it should act as arefresh and reload the Coach. If you accidentally closed the browser, run the coach.

__84. The screen should have refreshed and the columns should be 50% each.


60/130

IBM Software


__85. Set a value for the Budget, then click Ok. In the next step, you will add some formatting to this field.

__86. Leave the browser open.

__87. Double-click on theCoach


61/130

IBM Software


__88. Set Budget to use a currency formatting.

__a. Click onBudget



__d. UnderWidget Style, click Select to set the Format


62/130

IBM Software


__89. Select dollar currency format

__90. Verify your format.

You can use existing formats, or define your own formats.

__91. Click Save to save your changes. Or, use Ctrl-S to save your changes.


63/130

IBM Software


__92. Go back to the browser, and then clickOk. If you accidentally closed the browser, run the coach.

__93. Verify the Budget now appears formatted for dollar currency.

__94. Close the browser.


The idea that the picture is the process does not only apply to the higher-level process, but also toimplementations and screens.

1.4.4 Create a screen flow

In this section, you will modify this implementation from a single screen to a screen flow.


64/130

IBM Software


__95. Add anotherCoach to Request Headcounts diagram.

__a. Move End further to the right of its current position.

__b. Move Coach further to the right of its current position.

__c. Drag a Coach onto the diagram


65/130

IBM Software


__96. Rename the new coach as Introduction.

__a. Click onUntitled1



__d. UnderCommon, set Name to Introduction.


66/130

IBM Software


__97. Connect Start to Introduction and re-align Introduction

__a. Click the end-point of the flow line fromStart and connect it to Introduction

__b. Move up and/or nudge Introduction so that it is parallel to Start

__98. Open Introduction by double-clicking on it

__99. Delete the default Section so that you can build a coach from scratch.


67/130

IBM Software


__100. UnderSections, drag over a One-Column with Title.

__101. UnderControls, drag over a Button Group into the Section Title, deselect the Button Group whenyou see the shaded area inside the Section Title.


68/130

IBM Software


__102. Rename Section Title to Introduction.

__a. Click onSection Title


__c. View (or click on) the Section sub-tab

__d. UnderCommon, set Title to Introduction.


69/130

IBM Software


__103. Drag a Custom HTML control into Introduction.

__a. UnderControls, use the arrow-down button to scroll-down until you seeCustom HTML.

__b. DragCustom HTML into the Introduction above the button group.


70/130

IBM Software


__104. Customize the HTML in Custom HTML.

__a. ClickCustom HTML



__d. UnderCustom HTML, set HTML to Welcome. You are about to enter a headcount request.


71/130

IBM Software


__105. Change the label of the Button on the Introduction coach.

__a. ClickButton



__d. UnderButtons, click Button.

__e. UnderButton Details, set Label to Next >>.

__106. ClickDiagram


72/130

IBM Software


__107. Use the Sequence Flow, to wire Introduction to Coach.

__108. OpenCoach by double-clicking it.


73/130

IBM Software


__109. Change the label of OK on Coach.

__a. ClickOk



__d. UnderButtons, click Ok.

__e. UnderButton Details, set Label to


74/130

IBM Software


__110. Add another button by clickingAdd, which is under Buttons.,

__111. Similarly rename this buttonFinish.

__112. ClickDiagram

__113. Use the Sequence Flow, to wire Coach back to Introduction.


75/130

IBM Software


__114. Add a flow line fromCoach to End .

__115. If the elements of the diagram are close to grid, use Tidy Layout to snap them to grid.

__a. Right-click on the canvas

__b. Select Tidy Layout

__116. Verify your diagram.


This is not about just creating a single screen; it is about creating a wizard or a coach flow to guide the userthrough what they need to do in the process.


76/130

IBM Software


__117. Go ahead and run this screen flow.

__118. At the Save Service? prompt, click Yes.

__119. ClickNext >>.

__120. Click


77/130

IBM Software



__122. ClickFinish.



With the screen flow, we saw again: What you design, is what you get.


78/130

IBM Software


1.4.5 Add system activ it ies to the screen flow

While the screen flow you developed in the previous section only involved human interactions (coaches), thesehuman interactions could be interspersed with services and non-human activities. In this section, you willmodify the screen flow to add some non-human steps, which are a bit more technical than what you have doneso far.

__124. Drag a Server Script onto the diagram and set its name.

__a. Drag a Server Script onto the diagram



__d. UnderCommon, set Name to Set Requestor.


79/130

IBM Software


__125. Move the flow, which connects Introduction to Coach, to instead connectIntroduction to SetRequestor.

__126. Use the Sequence Flow to connect Set Requestor to Coach.


80/130

IBM Software


__127. Set the script implementation of Set Requestor.

__a. Click onSet Requestor



__d. UnderScript, type tw .

__e. This should have triggered code-completion, and then double-clicklocal.


81/130

IBM Software


__f. Type.

__g. This should triggered code-completion, and then double-clickrequest.

__h. Type .

__i. This should triggered code-completion, and then double-clickrequestor.


82/130

IBM Software


__128. Set the rest of the script.

__a. Type = , including the spaces before and after =.

__b. Type tw.system.u

__c. Double-clickuser_loginName

__d. Add a semi-colon at the end of the line.

__129. Verify your script.

__130. Go ahead and run this revised screen flow with non-human steps by clicking Run.

__131. At the Save Service? prompt, click Yes.



83/130

IBM Software


__133. Note that Requestor is now pre-populated with the user, tw_admin , which ran the screen flow.

__134. Leave the browser open.


84/130

IBM Software


1.4.6 Add drop-downs and make fields not-editable and required

In this section, you will add some drop-downs to the screen and make fields not editable or required.

__135. Make the Requestor non-editable.

__a. ClickRequestor


__c. View (or click on) the Visibility sub-tab

__d. UnderVisibility, check Override Parent Visibility.

__e. Set Default Visibility to Disabled (read only access)for everyone. This makes the field noteditable.


85/130

IBM Software


__136. Set Project so that it has a drop-down with a list of projects.

__a. ClickProject


__c. View (or click on) the Input Text sub-tab

__d. UnderBehavior, select Control Type as Single Select.


86/130

IBM Software


__137. Verify your configuration for Project.

__138. The data that populates a single select control can either be manual or dynamic. Dynamic data couldbe retrieved for example from a database or an Ajax Service. For simplicity, in this example, you willuse manual values.

__a. UnderManual Data, clickAdd.


87/130

IBM Software


__b. Similarly, add two more rows.

__139. Set the first row.

__a. For Value, delete Click to edit.

__b. For Display Text, enterSelect


88/130

IBM Software


__140. Similarly, set the two other rows to Project 1 and Project 2, respectively.

__141. To make sure users select a project, we need to make the field a required field.

__a. ClickVisibility

__b. UnderVisibility, check Override Parent Visibility.

__c. Set Default Visibility to Required (full access)for everyone. This makes the field required.



89/130

IBM Software


__143. Switch to the open browser. If you closed the browser, run the screen flow again.

__a. Click.

__145. Notice that Requestor is no longer editable. Notice that Project is now in red and has an asterisk,which shows this is a required field. Click Finish.


90/130

IBM Software


__146. Because Project is a Required field, the validation kicked in and you see an ERROR message at thebottom.

__147. Complete the form. Use the drop-down to select a project, and then clickFinish.



91/130

IBM Software


1.4.7 Take a snapshot

In this section, you will take a snapshot of the first activity you just implemented.


__150. Take a snapshot and name itv1.2 First Activ ity.

__151. Close Request Headcount.


This section just showed some basic validation that is available as you design screens.

1.5 Manually create a human service & conf igure decision gateway

In this section, instead of using the Activity Wizard to create our User Interface, you will create theimplementation of the second activity by hand. You will also associate the human service you created manuallyto the second activity of the process. Next, you will set the input data mapping for the Approve HC Request.

Previously you have created and edited data types from the Variables tab of the higher-level process or lowerlevel implementations. In this section, you will modify the variable from the Library. While it is not shown in thislab, you could also create data types from the Library.

After making the data type changes, the process has a variable to capture the result of the approval, you willuse that variable to configure the decision gateway to let the value of the variable decide with flow line will befollowed.

1.5.1 Create a Human Service manually

Instead of using the Activity Wizard, this time we are going to implement an activity from scratch. This will showyou a little bit of what the Activity Wizard did for you in previous sections.


92/130

IBM Software


__152. Create a Human Service.

__a. From the process library, hover user User Interface and select the plus ( ) sign

__b. In the Create New wizard, selectHuman Service

__153. Name the new human service. At theNew Human Service wizard:

__a. Set Name toApprove Headcount Request .

__b. ClickFinish.

__154. By creating a new Human Service, you get a blank canvas, where you can manually create your owncoach.


93/130

IBM Software


__155. Create a very simple coach from scratch.

__a. Drag a Coach onto the diagram.

__156. Name the coach Approve Request.

__a. Select Untitled1



__d. UnderCommon, set Name toApprove Request.

__157. ClickVariables.

Because a higher-level process will use this component, we should define Input and Output variables. An Inputvariable allows you to define the data the component will receive when someone reuses this component. Forthis example, the input variable will be a request of type HeadcountRequest.


94/130

IBM Software


__158. Add an Input variable to the human service by clickingAdd Input.

__159. Name the input variable request and set its type to HeadcountRequest.

__a. Click the new input variable.

__b. UnderDetails, set the Name to request.

__c. For Variable Type, click Select

__d. Type Re, and then select HeadcountRequest.


95/130

IBM Software


__160. Verify the configuration of the input variable, request. Also, set it to have a Default Value.


96/130

IBM Software


__161. The next step is to define an Output Variable for the component. A typical pattern would be to use thesame output as the input. For this example, the data we want to obtain from this step is the approvaloutcome. Therefore, create an output variable named result of type Boolean.

__a. ClickAdd Output .

__b. Click the new output variable.

__c. UnderDetails, set the Name to result.

__d. For Variable Type, click Select

__e. Type Bo , and then select Boolean.


97/130

IBM Software


__162. ClickDiagram so that you can start designing the coach.

__163. Double-clickApprove Request to open the coach.

__164. Select Section Title, then right-click and select Delete.


98/130

IBM Software


__165. UnderSections, drag a One-Column with Title onto the coach.

__166. UnderVariables, drag the request variable into Section Title.


99/130

IBM Software


__167. Set the J ustification to four rows.

__a. Select Justification



__d. UnderWidget Style, set # of Rows to 4.


100/130

IBM Software


__168. The Approver should not have the ability to modify the Request, therefore, make the entire Requestdisabled.

__a. ClickRequest


__c. View (or click on) the Visibility sub-tab

__d. UnderVisibility, check Override Parent Visibility.

__e. Set Default Visibility to Disabled (read only access)for everyone. This makes the field noteditable.


101/130

IBM Software


__169. UnderVariables, drag the result variable into Section Title below Request.

__170. Change the label of Result to something more descriptive.

__a. ClickResult


__c. View (or click on) the Boolean sub-tab

__d. UnderCommon, set Label to Check here to approve:.


102/130

IBM Software


__171. Add a Button Group to the coach.

__a. UnderControls, drag a Button Group to the bottom of Section Title.

__172. Change the label of the button to Complete.

__a. ClickButton



__d. UnderButtons, click on the button

__e. UnderButton Details, set Label to Complete.


103/130

IBM Software


__173. ClickDiagram to wire the flow.

__174. Wire the components of the Diagram.

__a. Use the Sequence Flow to connectStart toApprove Request .

__b. ConnectApprove Request to End .




104/130

IBM Software


__177. Notice that the entire Request object is not editable and there is a place for the approver to approvethe request. Click Complete.


__179. CloseApprove Headcount Request .


You created from scratch the Approve Headcount Request activity implementation of type Human Service.


105/130

IBM Software


1.5.2 Associate a Human Service to an activi ty

In this section, you will associate the human service you created manually in the previous section, ApproveHeadcount Request, to the second activity of the process, Approve HC Request. You will also set the inputdata mapping for the Approve HC Request.

__180. Associate Approve Headcount Request human service to Approve HC Request activity.

__a. ClickApprove HC Request



__d. Under Implementation , click Select


106/130

IBM Software


__181. TypeAp , then selectApprove Headcount Request

__182. Verify the Implementation configuration forApprove HC Request.

__183. ClickData Mapping. Notice that the service expects an Input and an Output mapping.

Data Mapping is the second most technical topic so far, after the definitions of variables. If you recall when youcreated Approve Headcount Request, you specified what input data you expected to receive from a higher-level process, request data.


107/130

IBM Software


__184. Set the Input Mapping for the activity as request.

__a. Click to select request from the variables list.

__185. Verify your Input Mapping.

If you recall, you did not define a parameter within HeadcountRequest data type to store the approvaldecision. In the next section, you will modifyHeadcountRequest to add this parameter.

1.5.3 Modify a data type and set Output Mapping of an activity

Previously you have created and edited data types from the Variables tab of the higher-level process or lowerlevel implementations. In this section, you will modify the variable from the Library. While it is not shown in thislab, you could also create data types from the Library.


108/130

IBM Software


__186. Modify HeadcountRequest to add a parameter for the approval result.

__a. Select Data, and then selectHeadcountRequest.

__187. Add a parameter named approved of type Boolean.

__a. ClickAdd.


109/130

IBM Software


__b. Set the name to approved with a variable type ofBoolean.


__189. Close HeadcountRequest.

__190. Now that the request has a parameter for approved, add this output mapping to the activity.

__a. ClickDiagram.


110/130

IBM Software


__191. Set the Output Mapping of Approve HC Request.

__a. ClickApprove HC Request.


__c. Click the Data Mapping sub-tab

__a. Click to select approved parameter of the result variable.


111/130

IBM Software


__192. Verify the Output Mapping.


1.5.4 Configure the decision gateway

Now that the process has a variable to capture the result of the approval, you can use that variable to configurethe decision gateway to let the value of the variable decide with flow line will be followed.

__194. Configure the decision gateway to use approved parameter. If approved is true, the process shouldfollowed the approval path.

__a. ClickStatus.


__c. Click Implementation


112/130

IBM Software


__a. Click to select approved parameter of the request variable.

__b. Set the criteria to ==

__c. Enter true as the value we want to compare to the approved value.



__197. Switch to the Inspector perspective, if you were not automatically switched there.


113/130

IBM Software


__198. Run the first task as tw_user.


__200. Fill out the form and submit it.

__a. For Project, selectProject 1

__b. For Budget, set it to 56

__c. Use the calendar control to set the date to 09-23-2010.

__d. For J ustification, enterwe need another person.

__e. ClickFinish.



114/130

IBM Software



__a. Run Approve HC Request as tw_user.


115/130

IBM Software


__203. Lets not approve the first time around, so just clickComplete.



116/130

IBM Software


__205. Back in the Inspector, click Refresh to see where your process has advanced. Because you leftCheck here to approve un-checked, the process should have returned back toRequest Headcount.

__a. Run Request Headcount as tw_user.



117/130

IBM Software


__207. ClickFinish.



118/130

IBM Software



__a. Run Approve HC Request as tw_user.


119/130

IBM Software


__210. At the approval screen, approve the request.

__a. CheckCheck here to approve:.

__b. ClickComplete.



120/130

IBM Software


__212. Back in the Inspector, click Refresh to see where your process has advanced. Because youchecked Check here to approve, the process completed when it followed the approval flow.

1.5.5 Take a snapshot

In this section, you will take a snapshot of the complete process.


121/130

IBM Software



__214. Take a snapshot and name itv1.3 - Complete.

1.6 Snapshots

Lombardi has kept track of the revisions you make to the process, and you have labeled some of theserevisions after reaching some milestone. In this section, you will see how you can switch from one snapshot toanother and furthermore, these snapshots are not just pictures, they are runnable!

__215. Review the snapshots you have taken as you have developed this process.

1.6.1 Explore Snapshots

In this section, you will move back in time and mainly look at snapshots from the high-level (BPD level).


122/130

IBM Software


__216. UnderRevision History, click v1.0 - Base Process.

At any point, you can switch back and understand what did the process look like at the very beginning.When you clicked v1.0 - Base Process, it reverted the diagram to that point in time. It is not just thesingle component that you are looking at, it reverted all the components in the library.

__217. Under Revision History, click v1.1 Process Changes. If you recall, at this point in time you just hadthe process level diagram with no implementations for the activities, therefore when you ran thatversion of the process all screens were default screens.


123/130

IBM Software


__218. Run the process by clicking Run.


124/130

IBM Software


__219. The diagram is not just a version control model; it is runnable!

__a. Run the first task as tw_user.


125/130

IBM Software


__220. You can verify that this first activity was back to the default screen, the way that screen existed whenyou took that snapshot.

__a. ClickDone.



The benefit of snapshots is that Lombardi is tracking these versions for you and it makes it easy for you to goback in time. In the real world, when you have multiple versions of the same process running at the same timeyou need it to be as easy as you just saw to switch back to previous versions of the process. Not just theprocess, but also the lower level of implementation to understand what did it look like at the beginning, whatdid it look like further back and so on.


126/130

IBM Software


1.6.2 Snapshots at a lower-level

In this section, you will verify that snapshots not only track high-level changes, but low-level implementationdetails.

__222. ClickDesigner

__223. Close v1.1 Process Changes snapshot.

__224. Under Revision History, click v1.3 - Complete.


127/130

IBM Software


__225. Double-clickRequest Headcount.


128/130

IBM Software


__226. Verify that this is the latest version of the Request Headcount activity.

__227. Under Revision History, click v1.2 First Activi ty.


129/130

IBM Software


__228. Again that was the state of the first activity.

__229. Under Revision History, click v1.1 Process Changes.

__230. Note thatRequest Headcount is flagged as Missing from this snapshot because it did not exist whenyou took that snapshot, at that point in time.


130/130

IBM Software

__231. Close the snapshot to get back to the current version.

__232. Close Request Headcount.

Attention!

There is MUCH MORE to see in the extended Videoshi h b d h h j d i hi h d i

Documents

BPMSandbox.com HandsOnExercise 2 BuildFromScratch BH V1