Activities performed within the context of a business process may have to execute application logic. This application logic is defined by a concept called application. For more details on applications, refer to Applications. Applications in the Stardust Documentation.
The following application types are supported in the Web-based modeler:
Chapter Using imported Plain Java Applications gives details on how to use imported Plain Java Applications, which are not supported for editing in the Browser modeler, but can be imported to be used for modeling.
This section helps you to work with applications in the Business Process Modeling perspective.
You can create following application types:
To create any of these applications, perform the following steps:
Figure: Create Application
Under the Application node, right-click the application name and select Rename .
Figure: Rename Application
Rename can be performed in the My Process Models panel, property panel of the element, and by double-clicking element in the Process Diagram canvas.
Under the Application node, right-click the application and select Delete.
Figure: Delete Application
To view and edit the properties of any application, select the application under the Applications node in the My Process Models panel.
Figure: Select Application
The properties of the selected application get displayed.
The Service Wrapper Process Wizard allows creating a process definition with SOAP and/or REST interface based on a service application, without the need to model it manually. It supports service definition with one IN and OUT access points on a structured data type only. The Request Data (any Structured Data Type in the same model) and Response Data (any Structured Data Type in the same model) are used as IN and OUT formal parameter of the process interfaces created. A Service Wrapper Process can be transient and/or persistent (default).
Figure: Create Service Wrapper Process Wizard
If the Create Test Wrapper Process check box is selected, another test process is created. This process can be used as manual test process to invoke the original process from within the process portal and not via SOAP and/or REST.
Figure: Service Wrapper Process Wizard
Under the model node, following elements get created:
Figure: Service Wrapper Process
Figure: Test Process - Service Wrapper Process as a Subprocess
In case you want to create a test process after the wrapper process is created, right-click the wrapper process and select the option Create Interface Test Process. The test process gets created.
Figure: Create Interface Test Process
This creates a test process to test your original process.
Figure: Interface Test Process
Specify following details:
The created wrapper process becomes Auxiliary process, by default.
If the Public Visibility check box is selected of the application, then it can be referenced in the consumer model. To reference the application, drag and drop the application from the provider model to the consumer model.
Figure: Drag and Drop the Application to Consumer Model
Based on the application type, it gets converted to appropriate task types.
Figure: Referenced Application converted to Script Task
For more information, please refer to the section Dragging and Dropping of Elements of the chapter Swim Lanes Usage.