To set up
Business Flow
Open
Business Flow and select Business Flow to get to the configuration page.
Select the icon and rename the Configuration. In the same place, you can also describe the business flow. For example, you can create a payment process flow called ACME Payment Process.
In the rightmost side panel, under Step 1, select Add event dropdown under Events, and choose a business event to specify a step completion.
Note: You can add up to five events for each step.
Name the step by selecting Step 1 name in the side panel.
In the main panel tree, hover over Step 1 box, and select
at the bottom of the step box to add the next step.
Note: You can also add previous steps and generate a branch.
Note: That steps cannot be reordered.
Continue adding further steps until your business flow is complete.
In the rightmost side panel, set the default correlation ID in the app settings .
Note: The default correlation ID entered here is applied to all steps. Optional local correlation IDs override the default setting and can be defined for each relevant step.
The Correlation ID field is pre-filled with the default correlation ID. If an event associated with this step uses a different correlation ID, enter the new name in the Correlation ID field located in the detail view of the selected step (the rightmost side panel).
Some events can indicate a business exception; for example, an out-of-stock event. Select the events that are designated as Business exception in a step.
In the rightmost panel, find the app settings .
Select Mapping event dropdown field and choose the business event that contains the attribute to use to calculate the KPI.
Select Mapping attribute from event dropdown field and choose the KPI. Only attributes that are of type long or double are shown.
Close the Advance settings configuration window.
Select Validate & Save configuration.
Step name
Correlation ID
Business KPI
Place order
order_id
Order confirmed
order_id
order_amount
Order shipped
order_id
Order delivered
order_number
A business flow configuration can be ingested in Smartscape on Grail as a new entity that ties critical business processes with your IT entities as hosts or process group instances.
Having a business flow as an entity allows
Problems to find relationships between an IT-detected problem with any of the critical business processes that
Business Flow is monitoring. In addition,
Problems displays which business processes are impacted by the problem, allowing drill down into
Business Flow in problems investigation mode.
A business flow as entity can be seen in Notebooks exploring Smartscape nodes with the type BIZ_FLOW
SmartscapeNodes BIZ_FLOW| fields id, type, name
With a result like follows
id
type
name
BIZ_FLOW-000000001CD85158
BIZ_FLOW
Purchase order
BIZ_FLOW-FFFFFFFFF4557E37
BIZ_FLOW
Employee onboarding
To fully leverage the capabilities provided when a business flow is defined as an entity, configure at least a two‑step business flow with a correlation ID. This improves traceability across steps and ensures more accurate mapping to topology entities.
Optionally, define business KPIs to enhance observability and provide greater insight into business performance. We also recommend verifying that the business events defined in each step include topological entities, which improves Smartscape connectivity and enables more accurate impact analysis.
When a business flow is defined as an entity, Dynatrace automatically enables basic KPI monitoring through a backend scheduled job. This job generates standardized business events that follow the Semantic Dictionary guidelines for Business Flow KPI events.
Both the generation frequency and evaluation timeframe for these KPIs are user-configurable. We recommend setting the evaluation timeframe to at least three to four times the average duration of the monitored business process. This ensures accurate KPI evaluation and avoids missing data windows for long‑running processes.
Generated data is stored in Grail with a default retention period of 35 days. You can adjust this retention time by creating a custom bucket based on the event.types defined in the Dynatrace Semantic Dictionary.
Business FlowBusiness Observability