You can convert .msgflow files
to .subflow files, or .subflow files
to .msgflow files.
When you
convert
.msgflow files to
.subflow files,
the following referenced files must be updated. You can complete these
updates when you convert your
.msgflow file.
- If the .msgflow file is used as a subflow,
the parent flow must be updated so that it references the new .subflow file.
- If the .msgflow file contains subflows that
are defined in .msgflow files, these subflows
must also be converted to .subflow files.
To convert a .msgflow file or a .subflow file,
complete the following steps:
- In the Application
Development view, expand
the appropriate application, library, or integration project.
- To convert a .msgflow file
to a .subflow file, complete the following steps:
- Right-click the message flow that you want to convert
and click Convert to subflow.
- If the message flow is used as a subflow or contains
subflows, the Convert message flow to subflow window
opens and shows referenced files that must be updated. Select the
files you want to update and click OK. The subflow is saved and its contents are validated. The
editor provides a report of errors and warnings in the Problems view.
- To convert a .subflow file
to a .msgflow file, complete the following steps:
- Right-click the subflow that you want to convert and
click Convert to Message Flow.
- Specify the name for the flow. You cannot
use the name of a file that already exists in that application, library,
or integration project. You must include .msgflow at
the end of your file name.
- Click OK. The
message flow is saved and its contents are validated. The editor provides
a report of errors and warnings in the Problems view.
For information about handling errors
that occur when you save a message flow or subflow, see
Correcting errors from saving a message flow or subflow.
Last updated Friday, 21 July 2017