Managing business processes

Overview

Business processes in the Data Queries type of Business Activity Monitoring (BAM) are created and managed from the tree view or the Actions dropdown on the BAM homepage. This article covers the lifecycle operations available for individual business processes in the Data Queries type: creating, editing, deleting, importing, exporting, enabling and disabling monitoring, and interpreting the health indicator.

For managing the groups that contain business processes, see Managing business process groups.

Business value

Managing business processes in Turbo360 keeps your Data Queries tracking configuration aligned with your Azure monitoring workflows. Import and export let you migrate or back up process definitions across environments; the resource remapping step during import ensures each transaction stage is connected to the correct data source in the target environment. Health indicators provide at-a-glance status derived from live incident data.

Prerequisites

• A BAM environment deployed with the Data Queries type
• Contributor role or higher

Required permissions

How it works

Each business process is identified by a tracking name (used for runtime data correlation) and a friendly name (displayed in the tree view). Processes are organized into business process groups in the tree view. Configuration is accessible from the Context menu ( ⋮ ) on each process.

In the Data Queries type, monitoring can be enabled or disabled per business process. Tracking state management and message archival are not available — these are Custom Logging-only features.

Steps

Use the following steps to create, edit, delete, import, and export business processes. Navigate to Business Activity Monitoring in the tree view to get started.

Create a business process

Creating a business process establishes the top-level tracking container for a Data Queries workflow.

1. Click the Actions dropdown on the homepage and select Create Business Process, or click the Context menu ( ⋮ ) next to any business process group in the tree view and select New Business Process.
2. Enter a Tracking name — used to identify and correlate the process at runtime; must be unique across the BAM product.
3. Enter a Friendly name — the display name within Turbo360; must be unique within the business process group.
4. Click Save.

Edit and delete a business process

Editing lets you update the name and description; deleting removes the process and all associated data permanently.

1. Click the Context menu ( ⋮ ) next to the business process in the tree view.
2. Select Edit to update the tracking name, friendly name, or description, then save.
3. To delete, select Delete from the Context menu ( ⋮ ), then confirm.

Import a business process

Importing loads a previously exported process definition from a JSON file. The Data Queries import flow includes a transaction selection step and a resource remapping step to connect each transaction and stage to the correct Azure data source in the target environment.

1. Click the Context menu ( ⋮ ) next to the target business process group in the tree view, then select Import.
2. Select the downloaded business process JSON file, then click Open.
3. Enter a unique Tracking name to avoid data conflicts, or enable Import all the Business Process tracking names dynamically to auto-generate tracking names for all selected processes.
4. Click Next. The Import transactions screen appears, listing each transaction from the JSON file alongside its Status:
   • Added — the transaction does not exist in the target business process and will be created on import.
   • Not found — the transaction exists in the JSON file but was not found in the target environment. Select Include changes to include it in the import.
5. Select the transactions to import using the Include changes checkbox, then click Next.
6. The Linked resource details screen appears. For each transaction and each stage within it, select the Azure data source resource to use in the target environment.

7. Click Validate to confirm the resource selections.
8. Click Import.

Export a business process

Exporting saves one or more business process definitions to a JSON file for backup or migration.

1. Click the Context menu ( ⋮ ) next to the business process group in the tree view, then select Export.
2. Select the business processes to export.
3. Click Export.
4. Enter a Name for the JSON file.
5. Click Export to download.

How it works

Enable and disable monitoring

By default, monitoring is enabled for every business process. To toggle monitoring for a process:

1. Click the Context menu ( ⋮ ) next to the business process in the tree view.
2. Select Enable monitoring or Disable monitoring.

Health indicator

The health status shown next to a business process in the tree view reflects alert incidents from all monitor types over the past 24 hours. The status hierarchy is: Error < Warning < Healthy < Not Monitored.

Manually closing all active incidents within the 24-hour window updates the business process status to Healthy.

Limitations

• Purge policy, message archival, cloning, and the Disable tracking option are not available in the Data Queries type.
• Deleting a business process is irreversible — all tracked transactions, dashboards, and configurations are permanently removed.
• Tracking name must be unique at the BAM product level.
• During import, a transaction with status Not found will only be imported if Include changes is selected for that transaction.

Troubleshooting

1. Actions dropdown is not visible
   Cause: The user does not have the required Manage business process permission.
   Fix: Request a role assignment with Manage business process permission from your administrator.

2. Import fails with a tracking name conflict
   Cause: The imported business process uses a tracking name already in use at the BAM product level.
   Fix: Enter a unique tracking name during import, or enable Import all the Business Process tracking names dynamically.

3. Resource selection step shows no available resources during import
   Cause: The service principal configured in the BAM module does not have access to the subscription containing the target resources.
   Fix: Verify the service principal permissions and subscription access under Settings > Service principals in the Pull Model.

4. Transaction shows status "Not found" during import
   Cause: The transaction exists in the exported JSON file but does not match any transaction in the target business process.
   Fix: Enable Include changes for the transaction to add it during import. If the transaction should already exist, verify the target business process contains the expected transaction configuration.

5. Health indicator shows Error but no active alerts are visible
   Cause: Alert incidents from the past 24 hours may still be open after the underlying issue was resolved.
   Fix: Manually close all active incidents from Alert history to reset the indicator to Healthy.

Related articles

• Managing business process groups
• Understanding the Pull Model
• Managing business transactions
• Managing service principals