This guide outlines changes in process and UI configuration from v4.1.x to 4.5.1 version.
The Applications feature in FlowX AI v4.5.0 is a new structure that organizes all dependencies and resources required for a project into a single deployable view. This enhancement simplifies configuration, deployment, and maintenance by layering applications on top of processes, offering a centralized workspace that encapsulates everything needed for project execution.
Several key configuration changes impact how resources and dependencies are managed, deployed, and maintained. This guide provides a breakdown of the configuration changes, automatic migration processes, and manual steps required to ensure a smooth transition.
To ensure a smooth transition, complete the following steps:
env = null
(displayed as “all” in the interface in versions prior to 4.5.0), will be migrated. You must ensure that you have correctly set the values for generic parameters, paying attention to environment values (which are case-sensitive), and export these generic parameters before migration to avoid any potential data loss.To set configuration parameter overrides, navigate to Your App -> Runtime -> Configuration Parameters Overrides.
v4.5.0:
v4.1.x:
Before starting the migration, complete the following steps:
During migration, resources will be transferred into a single default application with one committed version.
env = null
or that match the platform’s environment setting.Some resources will remain globally available or are deprecated:
In version 4.5, significant updates have been introduced to the Datepicker component to ensure compatibility with ISO 8601 date formats and enhanced handling of date attributes within the Data Model. This migration affects both newly created and existing processes.
Introduction of Date Types:
Properties Updates:
minDate
, maxDate
, and defaultValue
. These properties:
Backward Compatibility:
Legacy Date
type. This preserves the original formatting and ensures no disruption in business rules or workflows.Standard Date
type, saving values in ISO 8601 format.Legacy Datepickers:
Business Rules Updates:
Standard Datepickers:
defaultValue
must be in ISO 8601 format.Legacy
mode unless business rules and workflows are updated to support ISO 8601.Standard Date
to ensure future compatibility and alignment with ISO 8601 formatting.For complex projects with multiple use cases, do not use the default application for ongoing development or production builds. Instead:
This guide outlines changes in process and UI configuration from v4.1.x to 4.5.1 version.
The Applications feature in FlowX AI v4.5.0 is a new structure that organizes all dependencies and resources required for a project into a single deployable view. This enhancement simplifies configuration, deployment, and maintenance by layering applications on top of processes, offering a centralized workspace that encapsulates everything needed for project execution.
Several key configuration changes impact how resources and dependencies are managed, deployed, and maintained. This guide provides a breakdown of the configuration changes, automatic migration processes, and manual steps required to ensure a smooth transition.
To ensure a smooth transition, complete the following steps:
env = null
(displayed as “all” in the interface in versions prior to 4.5.0), will be migrated. You must ensure that you have correctly set the values for generic parameters, paying attention to environment values (which are case-sensitive), and export these generic parameters before migration to avoid any potential data loss.To set configuration parameter overrides, navigate to Your App -> Runtime -> Configuration Parameters Overrides.
v4.5.0:
v4.1.x:
Before starting the migration, complete the following steps:
During migration, resources will be transferred into a single default application with one committed version.
env = null
or that match the platform’s environment setting.Some resources will remain globally available or are deprecated:
In version 4.5, significant updates have been introduced to the Datepicker component to ensure compatibility with ISO 8601 date formats and enhanced handling of date attributes within the Data Model. This migration affects both newly created and existing processes.
Introduction of Date Types:
Properties Updates:
minDate
, maxDate
, and defaultValue
. These properties:
Backward Compatibility:
Legacy Date
type. This preserves the original formatting and ensures no disruption in business rules or workflows.Standard Date
type, saving values in ISO 8601 format.Legacy Datepickers:
Business Rules Updates:
Standard Datepickers:
defaultValue
must be in ISO 8601 format.Legacy
mode unless business rules and workflows are updated to support ISO 8601.Standard Date
to ensure future compatibility and alignment with ISO 8601 formatting.For complex projects with multiple use cases, do not use the default application for ongoing development or production builds. Instead: