In a message flow, you can include an embedded message flow, also known as a subflow. For example, you might define a subflow that provides error handling, and include it in a message flow connected to a failure terminal on a node that can generate an error in some situations.
When an application or shared library references other shared libraries, all the subflows for a broker schema must be in a single container. Subflows for a broker schema must not be in both an application (or shared library) and a shared library that is referenced by that application (or shared library). Subflows for a broker schema must not be in two or more shared libraries that are referenced by a single application or shared library. All the subflows in a broker schema must be either in the main application or shared library, or in a single referenced shared library.
To add a subflow to a message flow or subflow, complete the following steps:
You can package subflows that are defined in .msgflow files as user-defined nodes so that you can use them in message flows and subflows; for more information, see Using a subflow as a user-defined node.