Assigning a Release to a Flow

Overview

To use the layouts that you have created to process documents, you need to deploy a flow that contains a release.

You can assign each release to a flow.

Deploying a flow makes the flow’s release live. Thus, you can deploy multiple flows and have multiple live releases at the same time. 

To learn more about creating releases, see What is a Release? and Adding a New Release.

Assigning a release to a flow

Once you create a release, you can proceed with assigning the release to a flow. To assign a release to a flow, follow the steps below:

  1. Go to Library > Releases.

  2. Find the release that you would like to assign to a flow, and click on its name. Note that you can only assign locked and live releases to flows.

  3. Click the Assign to Flow button that is located in the upper-right corner of the page.

  4. Select the flow(s) you would like to assign the release to. Note that if you select a flow that you do not have access to, you will see a Restricted Permission (LockIcon.png) icon next to the flow’s name.
    RestrictedPermission.png

  5. Click Assign to Flow.

Additional details

  • A release can be assigned to multiple flows. A flow can contain only one release.
  • If a release has already been assigned to a flow and you assign a new release to the same flow, the new release will replace the previous one.
  • A release cannot be unassigned from a flow. Instead, you can assign a different release to the same flow.

Next steps and considerations

Once a release is assigned to a flow, to start using the release’s layouts, you need to deploy the flow. To learn more about deploying flows, see Managing Flows. But before you actually deploy the flow, consider the following:

Deploying a new flow with releases that contain new layout variations may not be the best option for your business needs. You must consider how much manual work your team can invest in performance improvements.

For example, when you deploy a flow containing releases with several new layout versions or layout variation versions, there may only be a small number of QA documents for the new versions. Until a sufficient number of QA documents are processed, automation will likely decrease.

On the other hand, a new version of a layout or layout variation may increase the accuracy performance for pages that match the improved version. Note that automation performance will increase as more documents pass through QA.

Highlight

Anytime a flow containing releases with new layout variations is deployed, expect a drop in automation because not enough training data has been associated with the updated layout variations.

For more information on layout versions, see What is a Layout Version? and Improving Layout Performance.

Was this article helpful?
0 out of 0 found this helpful