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.
You can manually build flows or import prebuilt flows into your service.
You can also export a workflow/slice you created as JSON to your OS clipboard or to your local library.
You can export the contents of a tab to the clipboard and import to the contents of the clipboard to another tab.
Click the Clipboard tab and choose an Export option. By default, the current flow export option is selected, but you can also export all flows in the service by click the all flows option. If you selected node prior to opening the Export menu, then you can click the selected nodes option.
Choose a format to copy. You can copy the nodes as GUI representations or as JSON. In both cases, the actual flow is copied as JSON. The GUI representation just provides a more human-readable format.
Click Copy to clipboard to hold the JSON in your OS clipboard or Download to download a JSON file containing the nodes.
Flows exported to any of the local library directories shipped with Extension Designer (Common, Components, Examples, etc.) will not be restored during a restore or upgrade process. |
Artifacts that have been downloaded and installed are stored in the Workflows folder under the Local tab in the Extension Designer library. In addition to storing Parasoft artifacts, the local library includes commonly-used flows, examples, and other building blocks to help you quickly build custom flows and understand how Extension Designer works.
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.
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.
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.