Modifying the Flow Service Pipeline while Debugging
During debugging, you can modify the contents of the pipeline and submit those changed values to the next step in the flow service. For example, if you want to see the effect that different values for a variable have on the rest of the service, you can modify the values in the pipeline and continue debugging. You can also drop values from the pipeline. This functionality is useful for debugging.
When modifying the pipeline, keep the following points in mind:
You can only modify the pipeline when a subsequent step in the service exists to which to pass the pipeline values. You cannot modify the values of the pipeline after the service ends. However, if you debug the service using the step commands, you can modify the pipeline values for the next flow step in the service.
You cannot modify the values of unconstrained Objects and Object lists. However, you can drop them from the pipeline.
You cannot modify the values of recursive documents at the top level. However, you can expand the document and set values at the individual element level.
When you modify values or drop variables from the pipeline, the changes only apply to the current debugging session. The service is not permanently changed.
You can only modify or drop existing variables. You cannot add new variables to the pipeline.
You can load an entirely different pipeline for
Designer to pass to the next step in the flow service.
You can save the contents of the pipeline to a file. You may want to save the results of specific flow steps to a file to compare with other services or to use in later debug sessions.