A simple process that let the user book a meeting room.
The user can then view his bookings and remove or add new ones, it also ensure that there can't be two booking in the same meeting room at the same time.
This example use advanced groovy script, customized form and custom connectors to persist data.
Data are serialized using xstream and stored in a file called MRB_db in order to allow running this example without any database configuration.
This process demonstrates the use of dynamic subprocesses in a loop.
Given the mode ('rent now' or 'book') chosen by the user, a different sub-process is called in the loop task.
It also shows how to manipulate a list of business objects (Bike) using getters and setters. With this feature, you can use a single business object in one or several forms instead of having to create a variable for each form field.
In the step "choose dates" you can also see how to update a data field (using HTML attributes) when the value of another data field changes.
Apache ActiveMQ is the most popular and powerful open source messaging and Integration Patterns provider.
Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4.
Please refer to http://activemq.apache.org/ for more information about ActiveMQ.
This connector is built to publish a message to an ActiveMQ server. Server URL , topic name, topic control Name are needed.
This connector allows you to log data in the default Bonita engine's log file (i.e, within the studio: help>Show Engine log).
Data can be either variables or groovy expressions.
- Source: the source of the log, e.g., the name of the step that generates the log.
* column1: the name of the variable / expression to log.
* column2: the value of the variable / expression to log.
This process demonstrates the use of the following concepts:
- Email connectors + mail attachment
- Form customization
This process shows 2 levels of verification of a document before its publication, i.e., before it is sent out by email.
The Writer submits a version of the document for review.
The Reviewer can make comments and ask the Writer to make some fixes.
Multiple iterations can be done. Once the Reviewer allows it, the Writer can submit the document to a Validator for a final validation.
The Validator can make comments or accept the document as it is.
1.You should login in the UserXP with "admin" then start a case about it.
2.You should login in the UserXP with "jack", "jack" role is a team leader , you can "approve" or "reject" this case. if you approved .then go to third step. if not go to first step.
3.You should login in the UserXP with "james", "james" role is a deptment manager, you can "approve" or "reject" this case. if you approved then send to a message to sub process that sub process start to with four step. if not go to first step.
This connector will get the next tasks actors and provide a Set of unique user names in return.
It will only look for the next human tasks linked to the current task (at a distance of 1 transition, not more).
this process let you select users by group.
First you could select group and it list the users of that group,and you can select users you want.
At the end,the process return an list of user names.
You can call this as sub process.
The process helps you organize your tasks following the Getting Things Done method.
An highly customized look'n feel is included.
The process is based on a Java business object and leverage the power of using setters of java objects using the setVar connector or using the output action of forms.
This example demonstrate the use of the overview forms and customized dynamic labels
This process has an instantiation (initial) Generic Request Form to be completed by a User. When the User logs in to make a request, the Process takes the User’s information (first name, last name, and email address) from the User Profile in UserXP.
At the Step "Approve or Reject," the manager of the requestor is approves or rejects the User’s request. On completion, an email Connector sends a message to the requestor.
You can use the provided test Users John, Jack, and James.