1. Open the Project Authoring perspective (Authoring → Project Authoring).
2. In Project Explorer (Project Authoring → Project Explorer), navigate to the project where you want to create the Process definition (in the Project view, select the respective repository and project in the drop-down lists; in the Repository view, navigate to REPOSITORY/PROJECT/src/main/resources/ directory).

   Note

   It is recommended to create your resources, including your Process definitions, in a package of a Project to allow importing of resources and their referencing. To create a package, do the following:

   • In the Repository view of the Project Explorer, navigate to the REPOSITORY/PROJECT/src/main/resources/ directory.
   • Go to New Item → Package.
   • In the New resource dialog, define the package name and check the location of the package in the repository.
3. From the perspective menu, go to New Item → Business Process.
4. In the New Processes dialog box, enter the Process name and click OK. Wait until the Process Editor with the Process diagram appears.

1. In the Project Explorer, select a Project and the respective package to which you want to import the Process definition.
2. In the Process Designer toolbar, click the Import icon in the editor toolbar and pick the format of the imported Process definition.
3. From the Import window, locate the Process file and click Import.
   

   Figure 3.5. Import Window

Procedure 4.1. Creating a new color schema

1. Locate your project in the Project Explorer and switch to the Repository view.
2. Open the global directory and locate and open the themes.json file.
3. In the displayed Default Editor, add your theme definition at the end of the file and click the Save button.

1. Open the Process definition in the Process Designer:
2. On the canvas, select the Element.
3. Click the double arrow ( ) in the upper left corner of the Process Designer to display the Properties view.
4. In the displayed Properties view, click the property value fields to edit them. Note that where applicable, you can click the drop-down arrow and the relevant value editor appears in a new dialog box.
5. To save your changes, click the Save icon and select option Save.

1. Open your Process definition in the Process Designer.
2. In the editor toolbar, click the Form ( ) icon and then Edit Process Form.
3. Select the editor to use to edit the form. Note that this document deals only with the Graphical Modeler option.

1. Open your Process definition with the User Task in the Process Designer.
2. Select the Task on the canvas and click the Edit Process Form ( ) in the User Task menu.
3. In the displayed Form Editor, define the Task form.

1. In Business Central, go to Authoring → Project Authoring.
2. On the perspective menu, select New Item → Form.
3. In the Create New Form dialog that opens, fill out the name of your form in Resource Name and click OK.

1. In Form Modeler, select the Add fields by type tab and click the arrow button to the right of a field type. The field type is added to the canvas.
2. On the canvas, place the cursor on the field and click the edit icon.
3. In the Properties dialog that opens on the right, set the form field properties and click Save at the bottom of the dialog.

1. Create process variables to hold values entered into forms. Variables can be simple (e.g. 'string') or complex. You can define complex variables using Data Modeler, or create them in any Java integrated development environment (Java IDE) as regular plain Java objects.
2. Declare the process variables in the 'variables definition' property.
3. Determine which variables you want to set as input parameters for the task, which shall receive response from the form, and establish mappings by setting the 'DataInputSet', 'DataOutputSet', and 'Assignments' properties for any human task. To do so, use the Editor for Data Input, Editor for Data Output, and Editor for Data Assignment.

1. Open the Data Modeler: in the Project Authoring perspective, click Tools → Data Modeler on the perspective menu.
2. Create a data object:
   1. In the Objects panel, click the Create button and provide the data object details:
      • Identifier: name of the data object unique within the project.

        Warning

        This identifier name must be unique within the whole project, and not just the package.
      • Label: name of the data object to be displayed in the Objects panel
      • New package: a new package the object should be created in
      • Existing package: an existing package the object should be created in
      • Superclass: a data object to be used as the superclass for the data object (the data objects extends this class, that is, it inherits all its fields)
3. Create fields of the data object:
   1. Select the object in the Objects panel.
   2. In the Create new field part of the Fields panel, define the field properties:
      • Id: field ID unique within the data object
      • Label: label to be used in the Fields panel
      • Type: data type of the field
   3. Click Create.

1. Create an implementation of the UserGroupInfoProducer interface and provide your own custom callback (see Section 4.15.3.1, “Connecting to LDAP”) and user info implementations according to the needs from the producer.
   This implementation must be annotated with the @Selectable qualifier for it to be found by Business Central. The listing below shows an example LDAP implementation:

   import javax.enterprise.context.ApplicationScoped;
   import javax.enterprise.inject.Alternative;
   import javax.enterprise.inject.Produces;
   
   import org.jbpm.services.task.identity.LDAPUserGroupCallbackImpl;
   import org.jbpm.services.task.identity.LDAPUserInfoImpl;
   import org.jbpm.shared.services.cdi.Selectable;
   import org.kie.api.task.UserGroupCallback;
   import org.kie.internal.task.api.UserInfo;
   
   @ApplicationScoped
   @Alternative
   @Selectable
   public class LDAPUserGroupInfoProducer implements UserGroupInfoProducer {
   
     private UserGroupCallback callback = new LDAPUserGroupCallbackImpl(true);
     private UserInfo userInfo = new LDAPUserInfoImpl(true);
     
     @Override
     @Produces
     public UserGroupCallback produceCallback() {
       return callback;
     }
   
     @Override
     @Produces
     public UserInfo produceUserInfo() {
       return userInfo;
     }
   
   }

2. Package your custom implementations (the LDAPUserGroupInfoProducer, the LDAPUserGroupCallbackImpl and the LDAPUserInfoImpl classes from the example above) into a bean archive (jar with META-INF/beans.xml so it can be found by CDI container). Add this jar file to business-central.war/WEB-INF/lib.
3. Modify business-central.war/WEB-INF/beans.xml and add the implementation (LDAPUserGroupInfoProducer from the example above) as an alternative to be used by Business Central.

   <beans xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://docs.jboss.org/cdi/beans_1_0.xsd">
   
       <alternatives>
           <class>com.test.services.producer.LDAPUserGroupInfoProducer</class>
       </alternatives>
       <interceptors>
           <class>org.uberfire.security.server.authz.cdi.RolesInterceptor</class>
           <class>org.uberfire.security.server.authz.cdi.TraitInterceptor</class>
       </interceptors>
   </beans>
   

4. Restart your server and your custom callback implementation should now be used by Business Central.

1. Create a Runtime Manager in your Execution Server.

   • Singleton: allows sequential execution of multiple instances in the one session
   • PerProcessInstance: allows you to create multiple process instances; every instance is created within its own session.
   • PerRequestSession: every external interaction with a process instances causes that the process session finishes and the process instance is re-created in a new session.
2. Get a runtime context and create a session in it.
3. Start a Process from the underlying Knowledge Base.
4. Close the Runtime Manager.

1. In the stencil set of the Process Designer, locate the workflow pattern that resembles most to and that will use as base for your workflow pattern.
2. Open the $JBOSS_HOME/standalone/deployments/business-central.war/org.kie.workbench.KIEWebapp/defaults /patterns.json file in a text editor.
3. Locate the JSON object with the description property set to the base workflow pattern name (for example, "description" : "Sequence Pattern").
4. Copy the JSON object and modify its elements as needed. Note that all the JSON objects are nested in a pair of square brackets and are comma separated.

1. Open the Process in the Process Designer and make sure you have defined the simulation parameters for individual Elements.
   

   Figure 6.2. Simulation Properties

2. Click the Process Simulation ( ) icon in the toolbar and then click the Run Simulation entry.
3. In the Run Process Simulation dialog window, define the simulation session details:
   

   Figure 6.3. Run Process Simulation properties dialog window

   • Number of instance: number of Process instances to be created and triggered
   • Interval: interval between individual Process instantiations
   • Interval units: time of unit the Interval is defined in
4. Click Run Simulation.

1. Display the Process Definitions view: on the top menu, click Process Management → Process Definitions.
2. Look up the Process Definition and in the respective row, click the Instantiate icon .
3. In the displayed dialog view, enter the properties and input paramaters for the Process instance.

1. On the top menu of the Business Central, go to Process Management → Process Instances.
2. In the list on the Process Instances tab, locate the required running Process instance and click the Details button in the instance row.

1. On the top menu of the Management Console, go to Process Management → Process Instances.
2. In the list on the Process Instances tab, locate the required Process instance and click the Abort button in the instance row.

1. Open the Tasks drop down menu (Tasks → Tasks List).
2. On the Tasks List tab, click New Task and define the task parameters:
   • Task Name: the task display name
   • Advanced
   • Due Date
   • User: user name of the person to execute the task
   • Priority: priority level
3. A Task cannot be created without a User or a Group. To add more users, select the Add User button.
4. To add more groups, select the Add Group button.
5. Click the Create button when you are satisfied with the information provided.

1. Make sure the data source is up and running and that the application server has access to the data source. (Check the driver, the login credentials, etc. In Red Hat JBoss EAP 6, you can do so in the Management Console under Subsystems → Connector → Datasources)
2. In Dashboard Builder, on the Tree Menu (by default located on the of the Showcase perspective), go to Administration → External connections.
3. On the displayed External Connection panel, click the New DataSource button.
4. Select the data source type (JNDI or Custom DataSource) and provide the respective data source parameters below.