In this section:


Flows are one or more nodes that can perform specialized tasks (see Working with Nodes). Flows are grouped into services to more evenly distribute data processing across endpoints, which results in more stable execution (see Working with Services for instructions on creating services).

There are a few ways to create flows:

The tabs are a construct for visually organizing flows. You can click the + icon to add more tabs if the tab you're working on becomes difficult to work with. All flows added to the a service will execute when the service is deployed.  

You can also minimize the Extension Designer sidebar and use the navigation buttons on the bottom of the tab to zoom out and increase overall visibility. 

Creating Flows

You can manually build flows or import prebuilt flows into your service. 

Manually Creating Flows

  1. Click and drag nodes from the parasoft palette on the left into the tab.
  2. Double-click on the node to open the node editor and configure the node. Different types of nodes have different configuration options, which are documented in the node Info tab. See Working with Nodes
  3. When nodes have been added to the tab, you can click and drag input/output points between nodes to chain together their functions into a flow. Flows are stored using JSON for easy sharing and versioning. 

    You should use Debug nodes to verify functionality as you create your flows. See Debugging Services and Flows.

Importing and Exporting Flows

  1. Click the menu icon and choose Import> [source] to import workflows/slices a flow from your library or OS clipboard.

    The library contains example components shipped with Extension Designer, as well as extensions downloaded and installed from the marketplace. See Downloading and Installing Artifacts for more information.
  2. Configure the nodes in the imported flow according to your needs (see Working with Nodes). You should use Debug nodes to verify functionality as you create your flows. See Debugging Services and Flows.

You can also export a workflow/slice you created as JSON to your OS clipboard or to your artifact library.


  1. Click the menu icon and choose Export> Clipboard.
  2. Choose whether you want to export selected nodes, current flow, or all flows, as well as whether the JSON should include line breaks when prompted. 
  3. Click Export to clipboard.


  1. Click the menu icon and choose Export> Library.

    Flows exported to any of the library directories shipped with Extension Designer (Common, Components, Examples, etc.) will not be restored during a restore or upgrade process.

  2. Enter a name for the file. You can use forward slashes to nest the file into a subdirectory.
  3. Click Export to finish.

About the Artifact Library

Artifacts that have been downloaded and installed are stored for use in the Extension Designer library. In addition to storing artifacts, the library also includes commonly used flows, examples, and other building blocks to help you quickly build custom flows and understand how Extension Designer works. 

Artifacts are organized into category by type:

Additional flows shipped with Extension Designer are organized into the following folders:

The additional flows contain documentation the describe how to use them. See Extension Designer Tutorials for additional information.

Disabling Flows

You can disable a flow to prevent its endpoint from being called. Widgets associated with the flow are also unavailable in DTP. If a widget has already been deployed to DTP, the widget will show a "No permission or deprecated" message.

  1. Open a service and double-click the tab containing the flow you want to disable.

  2. Click the Status button to disable the flow and click Done.
  3. Click Deploy save the changes to your flow.

To verify that the flow and its endpoint is disabled, click on the service category and expand the Available Endpoint page to the disabled flow.

Next Steps

When flows have been added to your service and configured, you can click the Deploy button to make them available to DTP. See Deploying Services for details.