Red Hat Summit Red Hat SummitSupportKonsoleEntwicklerDemo startenKontakt

Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.

Chapter 3. Process instance filtering

For process instances in Menu Manage Process Instances, you can use the Filters and Advanced Filters panels to sort process instances as needed.

Figure 3.1. Filtering Process Instances - Default View

Filtering Process Instances - Default View
View larger image
Filtering Process Instances - Default View

You can filter process instances by the following attributes in the Filters panel:

Id

Filter by process instance ID.

Input: Numeric

Initiator

Filter by the user ID of the process instance initiator.

The user ID is a unique value, and depends on the ID management system.

Input: String

Correlation key

Filter by correlation key.

Input: String

Description

Filter by process instance description.

Input: String

State

Filter by different states. You can select more than one status to display results that meet any of the selected states. Removing the status filter displays all processes, regardless of status.

The following filter states are available:

  • Active
  • Aborted
  • Completed
  • Pending
  • Suspended
Errors
Filter by process instances with or without errors.
Name
Filter by project name.
Date and time filtering
Start Date
When the process was started.
Last Update
When the process was updated or modified.

Each of these filters have the following quick filter options:

  • Last Hour
  • Today
  • Last 24 Hours
  • Last 7 Days
  • Last 30 Days

  • Custom

    Selecting Custom date and time filtering opens a calendar tool for selecting a date and time range.

    Figure 3.2. Process Instances Search by Date Range

    Search by Date Range
    View larger image
    Search by Date Range

3.1. Filtering process instances based on business data
Link kopieren

You can add process variables as columns in the process instance list in order to enable flexible filtering of process instances based on business data.

Procedure

  1. In Business Central, go to Menu Manage Process Instances.
  2. In the Manage Process Instances page, click the advanced filters icon on the left to open the list of process instance Advanced Filters options.
  3. In the Advanced Filters panel, enter the name and description of the filter, and click Add New.
  4. From the list of filter values, select processId and equalsTo.

  5. Provide a valid processId value and click Ok.

    A new filter is created and immediately applied to the process instances list. The filter is also saved in the Saved Filters list. You can access saved filters by clicking the star icon on the left side of the Manage Process Instances page.

3.2. Creating a custom process instance list
Link kopieren

You can view the list of all the running process instances in Menu Manage Process Instances in Business Central. From this page, you can manage the instances during run time and monitor their execution. You can customize which columns are displayed, the number of rows displayed per page, and filter the results. You can also create a custom process instance list.

Prerequisites

  • A project with a process definition has been deployed in Business Central.

Procedure

  1. In Business Central, go to Menu Manage Process Instances.
  2. In the Manage Process Instances page, click the advanced filters icon on the left to open the list of process instance Advanced Filters options.
  3. In the Advanced Filters panel, enter the name and description of the filter that you want to use for your custom process instance list, and click Add New.

  4. From the list of filter values, select the parameters and values to configure the custom process instance list, and click Ok.

    A new filter is created and immediately applied to the process instances list. The filter is also saved in the Saved Filters list. You can access saved filters by clicking the star icon on the left side of the Manage Process Instances page.

3.3. Aborting a process instance using Business Central
Link kopieren

If a process instance becomes obsolete, you can abort the process instance in Business Central.

Procedure

  1. In Business Central, go to Menu Manage Process Instances to view the list of available process instances.
  2. Select the process instance you want to abort from the list.
  3. In the process details page, click the Abort button in the upper-right corner.

3.4. Signaling process instances from Business Central
Link kopieren

You can signal a process instance from Business Central.

Prerequisite

  • A project with a process definition has been deployed in Business Central.

Procedure

  1. In Business Central, go to Menu Manage Process Instances.
  2. Locate the required process instance, click the Actions button and select Signal from the drop-down menu.

  3. Fill the following fields:

    • Signal Name: Corresponds to the SignalRef or MessageRef attributes of the signal. This field is required.

      Note

      You can also send a Message event to the process by adding the Message- prefix in front of the MessageRef value.

    • Signal Data: Corresponds to data accompanying the signal. This field is optional.
Note

When using the Business Central user interface, you can only signal Signal intermediate catch events.

3.5. Asynchronous signal events
Link kopieren

When several process instances from different process definitions are waiting for the same signal, they are executed sequentially in the same thread. But, if one of those process instances throws a runtime exception, all the other process instances are affected and usually result in a rolled back transaction. To avoid this situation, Red Hat Process Automation Manager supports using asynchronous signals events for:

  • Throwing intermediate signal events
  • End events

3.5.1. Configuring asynchronous signals for intermediate events
Link kopieren

Intermediate events drive the flow of a business process. Intermediate events are used to either catch or throw an event during the execution of the business process. An intermediate event handles a particular situation that occurs during process execution. A throwing signal intermediate event produces a signal object based on the defined properties.

You can configure an asynchronous signal for intermediate events in Business Central.

Prerequisites

  • You have created a project in Business Central and it contains at least one business process asset.
  • A project with a process definition has been deployed in Business Central.

Procedure

  1. Open a business process asset.
  2. In the process designer canvas, drag and drop the Intermediate Signal from the left toolbar.
  3. Click the Properties icon on the upper-right side of the screen to open the Properties panel.
  4. Expand the Data Assignments section.
  5. Click the box under the Assignments sub-section. The Task Data I/O dialog box opens.
  6. Click Add next to Data Inputs and Assignments.
  7. Enter a name of the throw event as async in the Name field.
  8. Leave the Data Type and Source fields blank.
  9. Click OK.

It will automatically set the executor service on each session. This ensures that each process instance is signaled in a different transaction.

3.5.2. Configuring asynchronous signals for end events
Link kopieren

End events indicate the completion of a business process. All end events, with the exception of the none and terminate end events, are throw events. A throwing signal end event is used to finish a process or subprocess flow. When the execution flow enters the element, the execution flow finishes and produces a signal identified by its SignalRef property.

You can configure an asynchronous signal for end events in Business Central.

Prerequisites

  • You have created a project in Business Central and it contains at least one business process asset.
  • A project with a process definition has been deployed in Business Central.

Procedure

  1. Open a business process asset.
  2. In the process designer canvas, drag and drop the End Signal from the left toolbar.
  3. Click the Properties icon on the upper-right side of the screen to open the Properties panel.
  4. Expand the Data Assignments section.
  5. Click the box under the Assignments sub-section. The Task Data I/O dialog box opens.
  6. Click Add next to Data Inputs and Assignments.
  7. Enter a name of the throw event as async in the Name field.
  8. Leave the Data Type and Source fields blank.
  9. Click OK.

It will automatically set the executor service on each session. This ensures that each process instance is signaled in a different transaction.

Nach oben
Red Hat logoGithubredditYoutubeTwitter

Lernen

Testen, kaufen und verkaufen

Communitys

Über Red Hat Dokumentation

Wir helfen Red Hat Benutzern, mit unseren Produkten und Diensten innovativ zu sein und ihre Ziele zu erreichen – mit Inhalten, denen sie vertrauen können. Entdecken Sie unsere neuesten Updates.

Mehr Inklusion in Open Source

Red Hat hat sich verpflichtet, problematische Sprache in unserem Code, unserer Dokumentation und unseren Web-Eigenschaften zu ersetzen. Weitere Einzelheiten finden Sie in Red Hat Blog.

Über Red Hat

Wir liefern gehärtete Lösungen, die es Unternehmen leichter machen, plattform- und umgebungsübergreifend zu arbeiten, vom zentralen Rechenzentrum bis zum Netzwerkrand.

Theme

© 2025 Red Hat