Forward-Compatible Models

Forward-Compatible Models

Accessing the features mentioned in this article
Your access to some of the features mentioned in this article depends on your license package and pricing plan.
To learn which features are available to your organization and how to add more, contact your Hyperscience representative.

In v42, models for flows created in v40 and above are forward compatible, meaning that you can use them in v42 without having to retrain them during the upgrade process. As a result, forward-compatible models allow you to:

Which models are forward-compatible

In v42, the following types of models are forward-compatible:

The following types of models are not forward compatible, so you need to train v42 versions of these models in order to use them in v42:

Using v40 and v41 models and flows in v42

As mentioned earlier, you can continue using v40 and v41 flows in v42 without interruption or loss of automation, provided that their models were last trained on v40 or later. For more information on what combinations of flow and model versions you can use in v42, see Compatibility Across Application, Flow, and Model Versions.

When using v40 or v41 flows, you can use cloned versions of the releases you used in v40 or v41. However, if you add Semi-structured layouts to those releases, there is no automation for the submissions matched to these layouts. That is, the system generates Supervision tasks for these submissions.

Memory Management

If you are using flows from multiple versions of the application and out-of-memory errors occur, you should enable the Memory Management feature. This feature assigns flows that were created in specific application versions to specific application machines in your instance.

To learn more about Memory Management, see Memory Management.

How to know when to train forward-compatible models

When you open a flow created in v40 or later in Flow Studio, the system lets you know which models for the flow need to be trained.

From there, you can click on an issue's Go to Model Management button.

Models from unsupported versions do not appear in the Model Library.