This topic applies only to the IBM Business Automation Workflow Advanced configuration.

Mediation subflow limitations

Edit online
Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
Limitations of mediation subflows
  • You cannot use a Policy Resolution primitive in a subflow
  • You cannot specify a context element within a subflow. Context elements that are available in the parent flow are also available to mediation primitives in the subflow.
  • When you are debugging a subflow, be aware of these limitations:
    • You cannot step into a subflow. You must set a breakpoint in the subflow in order to view the subflow execution.
    • You cannot step out of subflow. If you try to step over the last primitive in the subflow, the flow will run to completion. To workaround this limitation, set a breakpoint in the main flow after the subflow primitive.
  • If the subflow is contained within an aggregation block (an aggregation block is a group of mediation primitives that occur between a Fan Out mediation primitive and a Fan In mediation primitive) of the parent flow then a Service Invoke mediation primitive in the subflow will not be considered as part of this aggregation from an Asynchronous Deferred response invocation style. Read the following topic for a description on the invocation styles available: How to process mediations in parallel