Process designer elements
Standard BPMN elements
The following table describes some of the standard BPMN elements that BMC uses:
Element category | Element name | Symbol | Description |
|---|---|---|---|
Events | | Indicates where a process or subprocess starts. | |
| Indicates the end of a process or sub-process. | ||
| Interrupts a wait step and lets the process make a decision about how to proceed after the wait step times out. | ||
| Captures errors and exceptions within a process and identifies the path that should be executed after the business error or exception is captured. | ||
| Displays the business errors that occur in a process. | ||
| Calls another process. It is for application integration and component reuse. | ||
| Integrates an application with third-party systems. | ||
| Represents the user performing a task. The task is represented by a record. The task is considered complete if the completion criteria are satisfied. | ||
| Represents a wait step in the process that waits for the arrival of a message. | ||
| Describes a detailed sequence. | ||
| Models a Service Task, which invokes a Java service method that is exposed as an Action Type through @Action annotation. | ||
| Integrates an application with a RESTful web service in a codeless way. | ||
| Models concurrency in a process. It forks into multiple paths of execution or joins multiple incoming paths of execution. | ||
| Models a decision in the process and the conditions on exit paths. | ||
| Connects two elements in a process flow. | ||
| Provides additional information for the reader of the process diagram. |
Service task elements
The following table describes the service task elements that BMC provides:
Element category | Element name | Symbol | Description |
|---|---|---|---|
| Automates the task assignment by using machine learning. | ||
| Automates the manual task of data categorization by using machine learning. | ||
| Verifies whether the PIN value provided by a user matches the PIN value set for that user. | ||
| Creates a record instance for a specified record definition. | ||
| Deletes a record instance for a specified record definition. | ||
| Retrieves a record instance for a specified record definition. | ||
| Retrieves a set of record instances based on a specified query. | ||
| Retrieves a security label for a specified record definition. | ||
| Deletes a security label for a specified record definition. To identify whether the security label is updated, see Identifying updates to the security label. | ||
| Updates a record instance for a specified record definition. | ||
| Restricts access of a user, group, or a role to a record. To identify whether the security label is updated, see Identifying updates to the security label. | ||
| Sends a notification about the status of a particular activity. | ||
| Sends notifications based on the existing templates. | ||
| Displays an error, warning, or note. | ||
| Associates a child record instance with its parent record instance. | ||
| Associates two record instances with the relevant IDs. | ||
| Removes the association between the two records. | ||
| Removes the association between all the records. | ||
Document |
| Accesses individual attributes within the document schema | |
| Calculates a value in the workflow by performing an arithmetic operation. | ||
Data Streaming |
| Stores the application event data that is used to derive usage metrics for the application. | |
Platform Actions |
| Enables you to create a list of attachment or text data types from a process. | |
| Enables you to create an attachment from a base64 encoded string. Important: Use this element to handle web API responses. | ||
| Enables you to get a base64 encoded string from an attachment. Important: Use this element to handle web API responses. | ||
| Enables you to rename an attachment. For example, you can rename an attachment that you have downloaded from a web API or that is stored in a record definition. | ||
| Enables you to analyze the tone of a written document such as an email or a chat conversation. | ||
| Represents an array of objects that can store multiple inputs from processes and connectors in the array. |
Example of using a Process designer element
Consider a purchase process that involves a manager review to initiate a procurement process. If the item is available, it is shipped to the customer, and a notification is sent to the customer. If the item is not available, the order is canceled, and the customer is informed about the cancelation.
The following image shows a purchase process:
The purchase process can be designed in Process designer using elements available in the palette of the Process designer UI.
The following image illustrates the purchase process designed using Process designer:
The following table describes the various elements used in the purchase process:
No. | Element Type | Description |
|---|---|---|
1 | Start Event | This element denotes the start of a process. |
2 | User Task | Manager review requires human intervention. So a User Task element is used here. |
3 | Sub-Process | After the manager review is complete and the completion criteria is fulfilled, a procurement process is triggered. Because procurement is a larger process itself, a Sub-Process element is used here. |
4 | Exclusive Gateway | Depending on the availability of the item, the process progresses further. An Exclusive Gateway element creates a decision point, which further directs the process to the appropriate activity. |
5 | Parallel Gateway | If the item is available, the Parallel Gateway triggers the shipment and notifies the customer about the shipment. These activities happen concurrently. |
5a | User Message | The customer is notified about the shipment date; a User Message service task is used. |
5b | User Task | Shipping an item needs human intervention, so a User Task element is used. |
6 | Parallel Gateway | To logically close the procurement request, the end result of shipping an item and informing the customer should converge, and the Parallel Gateway element is used to join the two paths of execution. |
7 | User Message | If the item is not available, the user message element triggers a notification to the customer about the non-availability. |
8 | Update Record | If the item is not available, the Update Record element cancels the order by setting the Status field of the record to Cancel. |
9 | Delete Record | After the order has been canceled, the Delete Record element deletes the order. |
10 | End Event | This element denotes the completion of a process. |