Professional Documents
Culture Documents
bONITA SOFT
bONITA SOFT
Version 5.5
Introduction Tutorial
Introduction Tutorial
Change Notice
BOS 5.5 contains new functions and presents a new user interface in both Bonita Studio and Bonita
User Experience. This Introduction tutorial includes the updated interfaces and functions.
For an overview of where to find functionalities in Bonita Studio, Form Builder, and Bonita User
Experience, see the Bonita Open Solution QuickStart Guide 5.5
For more information about the new functions and for detailed information about Bonita Open
Solution functionality, see the Bonita Open Solution User and Reference Guide 5. 5
page 2
page 3
page 4
page 5
page 6
page 7
Bonita Studio
When you enter Bonita Studio, the Whiteboard is ready to begin with a pre-set Start1 and
Step 1. The Whiteboard is where you draw your processes.
Menu bar
Task bar
Use the Detail Panel to define and customize the entire Process,
individual Tasks, User Forms, Simulation, and more.
page 8
Use the Bonita Studio Form Builder to create Forms for End Users.
Use the Palette to select the widgets that allow you to format each field
Bonita User Experience Inbox allows the End Users to interact with and manage Process
Cases as they run.
There are 2 different views in Bonita User Experience: User View and Administration View.
page 9
change User
Preferences
change
UserXP
view
logged User
change
UserXP
view
the List of All Cases shows all Steps
page 10
Create a simple process in Bonita Studio and run it, then see the result in Bonita
User Experience (see Design and run a simple Process)
o
Draw Tasks and Transitions on the Whiteboard using the graphic tools in the
Bonita Studio Palette.
o Assign an Actor to each Task.
o Run the process, and complete the steps in Bonita User Experience.
Create a slightly more complex process and run it
(see Design a Process "Web Purchase")
o
o
o
o
o
o
o
o
o
On the Welcome screen, under the Design menu, click on New Process.
page 11
This opens a Process Diagram called MyProcessDiagram (1.0), which contains a Pool called
My Process.
Start1 and Step1 are already set up by default on the Whiteboard.
Figure 8. My Process
4.2
page 12
Drag and drop a new Human Task from the Design Palette on the left, and place it
next to Step 1 on the Whiteboard to the right.
page 13
page 14
Create an End event by clicking on Send a form to display its Context Palette.
Drag the blue circle End Event, out to the right of Send a form.
Drop the End Event into the required position at the end of the process.
A Transition is automatically created and Terminate End Event1 is added to the end of
the process.
Assign an Actor
Note: An Actor must be assigned to a human Task; an error icon will be displayed if the
Actor is missing. The error looks like this
and is displayed in the corner of Send a form.
Hover your curser over the icon to reveal the error message:
page 15
Click on Finish. The Actor Selector has been chosen, and the Process Initiator has
been assigned as the Actor for Send a form.
Enlarge the Whiteboard, zoom in and out, select elements to move, realign Tasks, add Text
Annotations and change Task colors.
None of these items will affect execution of the process.
4.4.1
Change the size of the Task Bar (Coolbar) to enlarge the Whiteboard.
page 17
Choose between 3 options: hidden, small and normal and see the Whiteboard
change size.
Restore all panels by selecting View -> Reset view from the Menu Bar.
4.4.2
Select a place on the Pool to zoom in on, and click to increase its size.
+ left click).
page 18
Click and hold down then drag out a selection over all the elements.
4.4.4
Use the Marquee tool for example, to select all the steps.
page 19
4.4.5
Click and drag the Text annotation icon to a place on your Pool close to the Task.
page 20
Click on General -> General and enter your text in the field.
4.4.6
page 21
Switch between a graphic zoomed out view and a tree view of the Process.
page 22
Click on the arrow to expand the default Tree view menu and display hidden
contents.
Click on Run
in the Menu bar at the top of the page. The process MyProcess will
be deployed and a Form will be created in the default Bonita web application.
A form is displayed. This form has no fields because no data was defined for this process.
page 23
The final screen presented below confirms the information has been submitted.
page 24
Click on the icon at the top right of the window to go to your Bonita User Experience
inbox.
Select New
to create a new Process. Bonita Studio will appear with a Start1 and a
first Step1 (Task).
6.3
page 25
Next add 3 Tasks, (Pay, Reject, More Info. All tasks will be connected to Sales
Review.
Sales Review should still be highlighted. The Context Palette to the right of the Task
should be highlighted too.
Click on the Task icon (circled) in the Context Palette and drag a new Task to the
right of Sales Review on the Whiteboard.
page 26
Notice that when you use the Context Palette (tools attached to a Task), a Transition is
added automatically.
page 27
Now add 2 more Tasks Reject and More info and connect them to Sales Review.
Priority is Normal.
Go to General -> General and in the Name field enter More Info.
Note: The red X appears to indicate that this Human Task has no Actor defined yet.
page 28
In the Description field, enter Simple item purchase from Web site
tutorial example.
page 29
Save the Diagram. The Whiteboard tab is now labeled Web Purchase Diagram (v2.0)
and the Pool is now labeled Web Purchase.
As the customer enters the details for Pay, he/she will choose whether the item is to be sent
by Express Delivery.
Click Pay and use the Context Palette to add a new Task.
page 30
Now that all the Tasks have been defined, add the remaining Transitions to connect
them.
As rejected requests will be archived, add a Transition between Reject and Archive.
End the Process highlight Archive and add a Terminate End event.
Drag the Event into place, and select the red Terminate End event to end the Process.
Click and drag the individual elements in your Process to re-arrange them if you
wish, or use the Marquee tool and right click + vertical / horizontal align.
page 31
The general sequence of the Process is nearly defined. Now add missing information to
complete it.
6.4
More Info has an input but no output. In this simple Process, the output will be returned to
the sales employee, so they can add information and complete the approval.
However, Sales Review will then have two inputs. A Gateway will define how these inputs
should be treated. Sales Review can proceed with either input, so an XOR Gateway is
needed.
Now, make room to add a Gateway between the Start and Sales Review.
To move a group of elements on the Whiteboard, click on the Horizontal Spacing
tool
page 32
in the Palette.
Now, select Gateway from the Palette and place it on the Whiteboard.
Note: If there is no XOR gateway to resolve multiple inputs, (just Transitions between Tasks)
Bonita Open Solution treats the Transitions as XOR by default. The Task will take the first to
arrive and proceed.
6.5
The next step to define this example Process is to add global and local variables.
Variables are used to define conditions on Transitions, and to capture and manipulate data
in end user Form fields (in this example, the form that the customer completes to begin the
process). Global data is accessible to all elements in the Process; while local data is available
only to the Task where it is defined and its output Transitions.
Add 4 global variables to this Process: 3 Text variables and one List of Options
variable.
page 33
Click on Add.
page 34
For the last variable, add a List of options, containing TV, Mobile phone and Laptop.
Click on Add.
Click on Ok.
Click on Add each time to add 2 more items to the same list of options, Mobile
phone and Laptop, with TV as the default value.
page 35
Click on Finish
The Web Purchase -> General -> Data now contains 4 global variables.
Now add local variables for the More Info and Pay.
The new text variable comment now shows up in the Data tab.
Figure 74. Newly created variable shows up in Data for this Task
page 36
Note that Sales Review has 3 outputs, and each implementation of the Process will follow
only one of them. One way to define how a Process will choose to follow which path is to
define Conditions for each Transition. Conditions can be defined using variables.
page 37
Click on Add to add the items Approve, Reject, and More info.
Click on Ok.
Click on Finish.
page 38
With this variable defined, you can associate each Transition output from Sales Review with
its associated decision Condition.
Select each Transition in turn and enter the details:
page 39
To change this label, select the Transition and go to Appearance -> Label.
page 40
Select the Transition between Pay and Express Delivery. Name the Transition if
yes.
Select the Transition between Pay and Archive. Name the Transition if no. In the
Conditions field, enter !chooseExpressDelivery. This Groovy expression
evaluates to chooseExpressDelivery=false.
Go to Appearance and change the labels on these two Transitions from Condition
Label to Name Label.
Note that you can also remove the labels on the Start, Gateway and End elements by
unchecking display name in the Appearance table of the Details Panel.
The Name of each Transition now shows on the Process.
page 41
To finish the definition of this example, define who will take action in the Human Tasks - the
Actor(s). In this section, you will add a static list of Actors, which is appropriate only for
trying out a Process design. (In a real-world scenario, the Actors of a Task would be selected
dynamically, usually from an external list which requires configuration of an Actor Selector).
Note: When the Process is Run, the Actors become the End Users.
The Process requires 2 types of Actors: the Process Initiator and Sales Employees. Define
these two Actor Selectors at the Process level, then go to each Task and assign them as
appropriate.
Note that Process Initiator is already defined, so add an Actor Selector for Sales Employees.
page 42
Click on Create, and when the wizard appears, select Bonita connectors and User List
Enter individuals manually.
Click on Next.
This will now show in the list of Actor Selectors available in this Process.
page 43
Figure 88. The newly created Actor Selector shows up in the Group list for the Process
You can now define the Actors in each of the Human Tasks in this Process.
Go to Sales Review -> General -> Actors. Initiator is already included by default. As
the Actor for this Task will be a Sales Employee, Select Initiator and Remove.
Note that removing Initiator from this Task does not remove it from the Process.
Figure 89. Sales Employees is now the only set of Actors for this Task
Select More Info and do the same to define the Actor Selector as Sales Employees.
For Pay, choose Initiator, as it is the initiator of the Process Case (the purchaser)
who will complete this Task.
page 44
After a few moments, Bonita Open Solution will present a series of status messages. The
deployment is successful.
Note that you are logged in as the User called admin.
The Process can now run Step by Step.
Recall that Tasks are called Steps in Bonita User Experience; Actors are End Users.
The forms are presented in the default Bonita Form and default Bonita Web Application,
which you have not customized (the fields are not presented in any specified order; they are
labeled with the variable name, and so on).
After you complete this Run a Process section, you can return to Bonita Studio and change
these forms (see Customize Forms).
Figure 90. Web Purchase Process Case initial Form (customer order form)
page 45
Figure 91. Fill in Web Purchase Process customer order Form to start a Case
The information entered by the customer is presented for approval in Sales Review. You
can now Approve, Reject, or request to enter More Information.
Note that the Step Actor candidates include the individuals you have identified as Sales
Employees, including the admin.
page 46
Figure 94. Fill in Form presented (again, after iteration) at Sales Review
As Customer, fill in Credit Card Number and Expiration Date, select Express
Delivery and click on Submit.
page 47
At this Step, the Form would be presented to the Initiator, but by default the admin has
access to activate it in this development activity.
Your inbox now contains a record of all the actions you have been involved in. You can look
at these actions at any time.
page 48
Figure 98. Bonita User Experience with completed Web Purchase Process test Case
Figure 99. A completed Step in the Web Purchase Process test Case
page 49
To run this Process again, return to the Inbox, go to Start a Case and select Web
Purchase. Click the Web Purchase under Start a case to run another Case.
Figure 100. Start another Case for the Web Purchase Process
The Process starts again with a new Case. This time, youll see the Forms presented inside
the User Experience.
Figure 101. Fill in web purchase process customer order Form to start a new case
page 50
The first Form presented in this process, Case Start: Web Purchase is the one that begins
this process.
Entry Pageflow allows you to define a series of Forms that allow data entry (i.e. interactive), and to
specify in what order the pages will be presented.
page 51
Select Add. A Form Wizard appears with all of the Data variables available for this
Form.
For this example, leave all choices checked and click Finish to continue.
A default version of the Form will appear, along with the Details panel for the Form.
page 52
To see the entire Form, close the Details and Overview Panels (click on the X in the
upper right corner of the Overview Panel, and on each tab in the Details Panel).
Figure 105. Close Details and Overview panels to see the entire Form
Each variable field in the Form is presented in a widget. You can customize the order and
presentation of each widget in the Form.
page 53
Add one to the top of the Form by clicking on the Insert a row symbol
top left:
at the
Now you can click and drag the customerName widget to the first row of the
Form.
page 54
Click and drag the other widgets into the order you want.
9.3
at the bottom
Click the widget and go to Details. You may need to restore the View to see the
Details panel again.
page 55
Figure 111. Indicate that the Customer Name field must be completed in the Form
page 56
page 57
For this Data variable, a drop-down list allows the user to select more than one item from a
Data list.
page 58
9.4
Save and close the Form and save it by clicking on the X on its tab.
Unlike the live Form presented to the Initiator to start this Process, the Form at Sales
Review primarily serves to carry data forward for review. There is only one live field for
the Sales Employee, the Decision choice.
Here is one way to create a Form here to do this.
Again select all Data available here to carry into the Form.
Add a new space to the Form, re-arrange the other widgets (see Figure below) and
delete the resulting empty widget.
page 59
To do this:
Here you can change its Field Type from TextBox (live) to Text (read only).
Figure 119. Change widget from Text field (live) to Text (read only)
page 60
Use the
Click and drag a Text widget from the Palette into the new space.
Click on the new widget, go to General and rename the widget and Label.
page 61
Last, go to the decision widget. In General, choose Radio buttons as the Field Type.
Radio buttons allows only one choice from a Data list. This is the only live field in
this Form.
Figure 123. Choose Radio buttons as the Field Type for decision
page 62
Customize the Form in More Info in the same way. Change the field for comment (Add
comment) as a live Text area.
The Form for Pay will be presented to the Initiator again (customer), so you can add a widget
to summarize the customers order.
page 63
When the Create a New Form wizard appears, select only chooseExpressDelivery,
creditCardNumber, and expirationDate.
Re-arrange the widgets as shown in the figure below. Add a new widget by clicking
and dragging the Message widget into the top spot.
page 64
For the new Message widget, go to General -> Data. For Initial value, select Edit
Expression. Create a Groovy expression to present a message in the Form.
Figure 128. Enter a Groovy expression to be evaluated and presented in the Message
page 65
Run it.
You should now see the Forms you have designed presented in the default Bonita Open
Solution Web Form.
Figure 130. Customized Form (fields) presented in Bonita Open Solution default web Form
page 66
page 67
page 68