This documentation supports the 22.1 version of BMC Helix Innovation Studio.

To view an earlier version, select the version from the Product version menu.

Process designer elements

Process designer uses a combination of the default Business Process Model and Notation (BPMN) elements and BMC extended elements. For example, the Process designer uses Service Task element in BPMN to create Record, User Message, Expression, and Association elements. These elements are available in the palette of the Process designer UI. You can drag the desired element on the canvas to design your process.


Application business analysts can customize the objects developed in their own applications and that are marked customizable by the administrator, but cannot customize the objects developed in com.bmc.arsys in Best Practice Customization mode. For example, objects in core BMC applications like Foundation, Approval, and Assignment cannot be customized in Best Practice Customization mode.

Standard BPMN elements

The following table describes some of the standard BPMN elements that BMC uses:

Element CategoryElement NameSymbolDescription


Indicates where a process or sub-process starts.

Indicates the end of a process or sub-process.


Interrupts a wait step and let the process make a decision about how to proceed after the wait step times out.
Error Boundary

Captures errors and exceptions within a process and identifies the path that should be executed after the Business error or exception is captured. 
Error End

Displays the business errors that occurs in a process.

Call ActivityCalls another process. It is for application integration and component reuse.

Integrates an application with third party systems.
User Task

Represents user performing a task. The Task is represented by a record. The task is considered as complete if the completion criteria is satisfied.
Receive Task

Represents a wait step in the process that waits for the arrival of a message.

Describes a detailed sequence.

Service Task

Models a Service Task, which invokes a Java service method that is exposed as an Action Type through @Action annotation.
Web Request

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 an execution.



Models a decision in the process, and the conditions on exit paths.
Sequence FlowSequence Flow

Sequence element connects two elements in a process flow.
AnnotationsText Annotation


 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 CategoryElement NameSymbolDescription
AssignmentSuggest Assignee

Automates the task assignment by using machine learning.
CognitiveSuggest Category

Automates the manual task of data categorization by using machine learning.
PINVerify Pin

Verifies if the PIN value provided by a user matches the PIN value set for that user.


Create Record

Creates a record instance for a specified record definition.
Delete Record

Deletes a record instance for a specified record definition.
Get Record

Retrieves a record instance for a specified record definition.
Get Records by Query

Retrieves a set of record instances based on a specified query.
 Get Security Label

Retrieves a security label for a specified record definition.

Remove Security Label

Deletes a security label for a specified record definition.

To identify if the security label is updated, see Identifying updates to the security label.

Update Record

Updates a record instance for a specified record definition.
Set Security Label

Restricts access of a user, group, or a role to a record.

To identify if the security label is updated, see Identifying updates to the security label.

User Message

Send Message

Sends a notification about the status of a particular activity.
Send Message by Template

You can use the existing templates to send notifications.
Show Alert

Used to display an error, warning, note.

Associate Child Records

Used to associate a child record instance with its parent record instance.
Associate Records

 Used to associate the two record instances with the relevant ids.
Disassociate Records

Removes the association between the two records.
Disassociate All Records

Removes the association between all the records.
DocumentCreate Document

Accesses individual attributes within the document schema
ExpressionsCompute Value

Used in the workflow to calculate a value by performing an arithmetic operation.
Data StreamingPublish Event

Stores the application event data that is used to derive usage metrics for the application.

Platform Actions

Create List

Enables you to create a list of attachment or text data types from a process.

Create Attachment

Enables you to create an attachment from a base64 encoded string.

Note: Use this element to handle web API responses.

Encode Attachment

Enables you to get a base64 encoded string from an attachment.

Note: Use this element to handle web API responses.

Rename Attachment

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.

Analyze User Engagement Tone

Enables you to analyze the tone of a written document such as an email or a chat conversation.
Add Array Element To Document

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 as an example. The purchase process 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 cancellation.

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 TypeDescription
1Start EventDenotes the starting of a process
2User TaskManager review requires a human intervention. Hence, a user task element is used here.
3Sub ProcessAfter the manager review is complete, and the completion criteria is fulfilled, a procurement process is triggered. Since procurement is a larger process in itself, a Call Activity element is used here.
4Exclusive GatewayDepending on the availability of the item, the process progresses further. For a decision to be taken and further direct the process to an appropriate activity, an exclusive gateway is used.
5Parallel GatewayIf the item is available, the shipment activity has to be triggered and also the customer has to be informed about the shipment. Both these activities must happen concurrently, so a parallel gateway is used.
5aUser MessageThe customer has to be notified about the shipment date, a User Message Service Task is used.
5bUser TaskShipping an item needs human intervention. Hence, a user task element is used.
6Parallel GatewayThe end result of shipping an item and informing the customer should converge for the process to end. The parallel gateway is used is join the two paths of execution.
7User MessageIf the item is not available the customer has to be informed about non availability. A user message element is used to trigger this notification.
8Update RecordIf the item is not available the order has to be canceled. Update record element is used process the cancellation activity by setting the Status field of the record to Cancel.
9Delete RecordAfter the order has been canceled, it must be deleted. A delete record element is used to delete the order.
10End EventDenotes the completion of a process.

Related topic

Defining the application business logic through processes

Was this page helpful? Yes No Submitting... Thank you


  1. Patrik Stanz

    Can you please let me know if I use the "Delete Record" or "Update Record" for a Remedy Form (e.g. HPD:Help Desk) will this be done via SQL directly in the database or will if be done via the Remedy-API so that Remedy "recognizes" this actions as "DELETE" or "MODIFY"?

    Oct 05, 2023 08:56

      Hi Patrik,

      In this case, the actions run via Remedy API and not directly via SQL on the database. Hope this helps.

      Regards, Minal

      Mar 27, 2024 01:18