Popup dialogs are used throughout the editor to prompt for additional configuration information or command confirmation. This section describes some the more “interesting” of these dialogs.
As described in the section on Graphical Editing, you do have the option of closing the Property Viewer and using popup dialogs to configure the elements. In this case, the property tabs are laid out horizontally in a popup dialog, instead of vertically (as in the Property View). Also, the Description tab is omitted to save space.
Like the Property View, the content of the Property Dialog varies, depending on which element is being edited. Here is an example of the Property Dialog showing the settings for a Manual Task:
Figure 44: BPMN2 Element Property Dialogs
Data Types (a.k.a. “Item Definitions”) use the following configuration dialog:
Figure 45: Data Type (“Item Definition”) Editing Dialog
· Item Kind – indicates whether the item is Physical or Informational
· Is Collection – if checked, the item represents a collection of data
· Structure – a reference to the actual structure of the data. By default, this is an XSD type, but may also be other language data types (e.g. Java) depending on the Type System defined for the Process.
Variables (a.k.a. “Properties”) are configured with the following dialog:
Figure 46: Variable ("Property") Editing Dialog
· Name – the variable name
· Data State – an application-defined state such as “initialized” or “staging”. See also Data Elements.
· Data Type – the type and structure of the variable (see above)
Messages are configured with the following dialog:
Figure 47: Message Editing Dialog
· Name – the name of the Message
· Data Type – the type and structure of the Message payload
Errors are configured with the following dialog:
Figure 48: Error Editing Dialog
· Name – the name of the Error
· Error Code – an application-specific value that can be used by Activities in, e.g. condition expressions to test for specific error types
· Data Type – the type and structure of the Error payload (if any)
Signals are configured with the following dialog:
Figure 49: Signal Editing Dialog
· Name – the name of the Signal
· Data Type – the type and structure of the Signal payload (if any)
Escalations are configured with the following dialog:
Figure 50: Escalation Editing Dialog
· Name – the name of the Escalation
· Error Code – an application-specific value that can be used by Activities in, e.g. condition expressions to test for specific escalation types
· Data Type – the type and structure of the Escalation payload (if any)
Data Stores are configured with the following dialog:
Figure 51: Data Store Editing Dialog
· Name – the name of the Data Store. This is typically a database table or file name, depending on the underlying technology used to persist the data.
· Capacity – an application-specific value that represents the maximum capacity of the Data Store
· Is Unlimited – if checked, indicates the Data Store capacity is unlimited. This overrides the Capacity value.
· Data Type – the type and structure of the Data Store
· Data State – an application-specific state of the data, e.g. “committed”, “archived”, etc. See also Data Elements.
Imports are used whenever data definitions required by the Process are maintained in an external file or some online resource (e.g. a web server.) The File Import dialog allows you to select and preview these resources before importing:
Figure 52: File Import Dialog
· Import Type – selects the type of file to import, one of the following:
o XML Schema (XSD) - for data type definitions
o Web Service Definition (WSDL) – for Web Service Interface definitions
o BPMN 2.0 Diagram (BPMN2) – for BPMN2 Process definitions
· Import Source – the location to search for the import file:
o Workspace – the Eclipse Workspace
o File System – the local host file system
o URL – on online web server
o WSIL – using the WSIL directory. See WSIL Browser for more information.
· Resource Selection Pane – this section displays the available files in the selected Import Source
· Preview Pane – this section displays the parsed contents of a selected file.
Clicking the OK button adds the selected file to the list of Imports and creates additional BPMN2 elements as appropriate:
· XSD – creates Data Type definitions for each of the element definitions contained in the XSD file.
· WSDL – creates Interfaces, Operations, Message types, Error types and Data Types from the WSDL file.
· BPMN2 – creates Interface references and Process references defined in the BPMN2 file. These are then available for use by Activities in the Process (e.g., Service Tasks, Call Activities, etc.)
· Java – imported Java files create the following BPMN2 elements:
o Classes – create Interfaces
o Class methods – create Operations for these Interfaces
o Method Parameters – create Messages and Data Types for each of the parameters
o Method return values – create Messages and Data Types
o Method “throw” declarations create Errors and Data Types for the Java Exception
Editing an imported file from the Imports List in the Process Definitions property tab displays the following dialog:
Figure 53: Import Editing Dialog
Note that only the Prefix can be edited, all other fields are read-only. Clicking the button displays this dialog which allows you to select a namespace prefix:
Figure 54: Namespace Editing Dialog
The editor will check to ensure that the new prefix is not already in use.
Resources are configured with the following dialog:
Figure 55: Edit Resource Dialog
A Resource may require one or more Resource Parameters; these are configured with the following dialog:
Figure 56: Edit Resource Parameter Dialog
Resource Roles are configured with the following dialog:
Figure 57: Edit Resource Role Dialog
This dialog is invoked from the Drawing Canvas context menu. It is used to save the currently selected diagram as an image file. The image can be saved in several different formats and sizes.
Figure 58: Export Diagram Dialog