Add new flows Only Admins

Users can create folders via the Dashboard to organize their flows?.

Add/Edit a flow

Flow property	Required	Description
Flow Name	yes	A case sensitive name that describe the client interaction (example: ex. invoice request, invoice approval, …)
Folder	yes	The location of where to save the flow. Flows are always structured in folders.
Mapping	no	The mapping that's used to 'map' imported messages to this flow. Invictus treats these special business properties (Domain, Service, Action, Version) differently (loaded from 'tracked properties, for instance, when using importing them via Logic Apps. Invictus adds a dedicated WorkflowName in those cases as well to map the messages of the Logic App workflow to the flow.)
Business Properties	no	Context properties to describe the flow. These are only here to provide metadata.
Advanced Settings	no	Connected Dashboard: in a hybrid (BizTalk + Azure) setup, it's necessary to have a link from one Dashboard (BizTalk) to the other Dashboard (Azure) for hybrid flows. More details on hybrid setups. Show milestone and event text: displays the flow milestone and event text data. New since v6.2 Show Resubmit / Resume: make the 'Resubmit/Resume' flow action buttons available per flow. Custom resubmit/resume URLs: Check these options and provide the necessary URLs to use your own resume and resubmit logic.
Alerts	no	See alerting

Allow access to flow

You can allow both active Microsoft Entra ID groups and local users to access the flows in the folder. Based on the chosen role, the user will receive their allowed permissions on the flow.

info

Users with the [System admin] role can access all flows in every folder available.

Add an alert for a flow

require role assignments after installation

The Invictus Dashboard requires additional role assignments to add alerts to flows.

Alert property	Required	Description
Alert name	yes	The name for the alert rule, must be unique per flow. (Name will automatically have the flow name added as a prefix to it.)
Description	no	The optional text giving more context to the alert.
Severity	yes	The level of severity of the alert.
Schedule	yes	Frequency: how often to execute the rule - value must be between the range of 5-1440. Time window: range that Azure uses, the logs for the last x minutes - value must be between the range of 5-2880.
Trigger	yes	The Threshold value together with the Threshold Operator (Equal/GreaterThan/LessThan) defines when to trigger the alert rule.
Throttling	no	Suppress alerts (minutes): suppress triggered alerts for x minutes.
Query	yes	Invictus Activity Check Monitors flow activity via Azure logs (InvictusImportJobFlowActivityAlert custom events). Invictus logs one activity per active flow every hour. If an alert running every 60 minutes finds no logs in the last 60 minutes (threshold < 0), Invictus flags the flow as inactive and triggers an alert. Note: Logging is per flow (not per message) and may exceed one entry per hour due to scaling or multi-threading. To increase logging frequency, reduce FlowActivityIntervalInMinutes during deployment (link). Invictus Error Check Monitors flow activity via Azure logs (InvictusImportJobFlowErrorAlert). Invictus logs an entry for each flow that triggers an error. If an alert running every 10 minutes finds more than 0 logs in the last 10 minutes (threshold > 0), Invictus flags the flow as failed and triggers an alert. Azure Resource Count Use custom Azure alert syntax, see the official Microsoft documentation to learn more about alerting.
Recipients	yes	The email recipients that get notified upon a triggered alert rule.