Do not forget, when upgrading to a new platform version, always ensure that your installed component versions match the versions specified in the release notes. To verify this, navigate to FLOWX.AI Designer > Platform Status.

After updating to 3.4.1 FLOWX.AI release, it is not possible to import old process definitions into the new platform release (available for exports from releases < 3.4.1).

Component versions

🧩3.4.13.4.03.3.03.2.03.1.03.0.02.14.02.13.02.12.02.11.02.10.02.9.02.8.12.8.02.7.02.6.02.5.02.4.02.3.02.2.0
process-engine4.3.14.1.03.6.02.2.12.1.22.0.70.4.1040.4.950.4.900.4.830.4.600.4.490.4.440.4.420.4.420.4.360.4.290.4.220.4.210.4.18
admin3.3.73.1.12.5.22.2.22.1.32.0.80.3.1190.3.1030.3.920.3.810.3.600.3.550.3.470.3.430.3.400.3.360.3.340.3.290.3.230.3.21
designer3.35.63.33.23.28.113.21.13.15.13.2.12.78.4-12.63.62.60.72.48.92.39.22.33.02.28.12.24.22.23.02.19.22.18.22.17.42.15.22.14.4
@flowx/ui-sdk3.35.63.33.23.28.113.21.13.15.13.2.1n/an/an/an/an/an/an/an/an/an/an/an/an/an/a
@flowx/ui-toolkit3.35.63.33.23.28.113.21.13.15.13.2.1n/an/an/an/an/an/an/an/an/an/an/an/an/an/a
@flowx/ui-theme3.35.63.33.23.28.113.21.13.15.13.2.1n/an/an/an/an/an/an/an/an/an/an/an/an/an/a
paperflow-web-components3.35.63.33.23.28.113.21.13.15.13.2.12.78.4-12.63.62.60.70.2.100.2.100.2.100.2.60.2.60.2.60.2.60.2.60.2.60.2.60.2.5
flowx-process-renderer------2.78.4-12.63.62.60.72.48.92.39.22.33.02.28.12.24.22.23.02.19.22.18.22.17.42.15.22.14.4
cms-core1.3.91.3.61.3.01.2.01.0.31.0.20.2.380.2.360.2.330.2.300.2.250.2.230.2.230.2.230.2.230.2.230.2.200.2.200.2.180.2.17
scheduler-core1.2.41.1.01.0.41.0.41.0.41.0.10.0.340.0.340.0.340.0.330.0.280.0.270.0.270.0.270.0.270.0.270.0.240.0.240.0.230.0.23
events-gateway1.1.01.0.61.0.2-----------------
notification-plugin2.0.82.0.52.0.42.0.42.0.32.0.11.0.2061.0.2061.0.2061.0.2051.0.2001.0.1981.0.1981.0.1971.0.1941.0.1941.0.1911.0.1911.0.1901.0.190
document-plugin2.0.82.0.62.0.42.0.32.0.32.0.21.0.531.0.531.0.531.0.521.0.471.0.421.0.411.0.381.0.371.0.371.0.351.0.351.0.311.0.31
ocr-plugin1.0.121.0.81.0.81.0.20.1.330.1.330.1.330.1.330.1.50.1.50.1.50.1.50.1.50.1.50.1.50.1.50.1.50.1.50.0.1090.0.109
license-core1.0.71.0.41.0.21.0.21.0.21.0.10.1.280.1.280.1.280.1.270.1.230.1.190.1.180.1.180.1.180.1.180.1.150.1.150.1.130.1.13
customer-management-plugin0.2.80.2.60.2.40.2.30.2.30.2.10.1.280.1.280.1.280.1.270.1.230.1.220.1.220.1.220.1.220.1.220.1.200.1.200.1.180.1.18
task-management-plugin3.0.33.0.02.1.21.0.41.0.41.0.10.0.420.0.420.0.400.0.370.0.290.0.280.0.280.0.270.0.270.0.270.0.220.0.220.0.210.0.21
data-search0.2.60.2.30.2.00.1.40.1.40.1.30.0.80.0.80.0.6n/an/an/an/an/an/an/an/an/an/an/a
audit-core2.1.32.1.01.0.61.0.51.0.41.0.10.0.80.0.5n/an/an/an/an/an/an/an/an/an/an/an/a
reporting-plugin0.1.20.1.20.0.400.0.400.0.400.0.390.0.39n/an/an/an/an/an/an/an/an/an/an/an/an/a
advancing-controller0.3.50.3.20.3.00.1.40.1.40.1.20.0.6n/an/an/an/an/an/an/an/an/an/an/an/an/a
iOS renderer2.3.02.3.02.1.02.0.12.0.02.0.0n/an/an/an/an/an/an/an/an/an/an/an/an/an/a
Android renderer2.1.42.1.42.0.12.0.12.0.12.0.1n/an/an/an/an/an/an/an/an/an/an/an/an/an/a

With the release of FLOWX.AI 3.0, there have been some changes that you need to be aware when upgrading to the latest version:

  • The flowx-process-renderer has been migrated to @flowx\ui-sdk.
  • As of FLOWX.AI 4.0, the paperflow-web-components library will be deprecated. Instead, the new components can be found in @flowx/ui-toolkit.
FLOWX.AI Platform VersionComponent nameRecommended version (tested versions)
3.4.1Keycloak18.0.x
3.4.1Kafka3.2.3
3.4.1PostgreSQL14.3.0
3.4.1MongoDB5.0.8
3.4.1Redis6.2.6
3.4.1Elasticsearch7.17
3.4.1OracleDB19.8.0.0.0
3.4.1Angular (Web SDK)15.0.0

FlowX.AI supports any version of the third-party components listed as prerequisites.

For optimal performance and reliability, our internal QA process validates new releases using specific versions as indicated in the provided table. While exploring alternative versions that suit your company’s specific requirements, we recommend referring to the compatibility matrix for guidance.

In the unlikely event that you encounter any compatibility issues with FlowX.AI, please open a support ticket here, and our dedicated team will address and resolve any identified bugs following our standard support process.

Compatibility Matrix:

  • FLOWX.AI Platform: Recommended and tested versions
  • Third-Party Components: Supported versions based on specific requirements and client preferences

Additional configuration

This section outlines the supplementary configurations required to leverage the newly introduced features within FLOWX.AI (for a smooth transition please check first what’s new in 3.4.0).

Scheduler configuration

scheduler:
  thread-count: 30  # Configure the number of threads to be used for sending expired messages.
  callbacks-thread-count: 60 # Configure the number of threads for handling Kafka responses, whether the message was successfully sent or not
  cronExpression: "*/10 * * * * *" #every 10 seconds
  retry: # new retry mechanism
    max-attempts: 3
    seconds: 1
    thread-count: 3
    cronExpression: "*/10 * * * * *" #every 10 seconds
  cleanup:
    cronExpression: "*/25 * * * * *" #every 25 seconds

Explanation

  • SCHEDULER_THREAD_COUNT - Used to configure the number of threads to be used for sending expired.
  • CALLBACKS_THREAD_COUNT - Used to configure the number of threads for handling Kafka responses, whether the message was successfully sent or not.

New retry mechanism

  • SCHEDULER_RETRY_THREAD_COUNT - Specify the number of threads to use for resending messages that need to be retried.
  • SCHEDULER_RETRY_MAX_ATTEMPTS - This configuration parameter sets the number of retry attempts. For instance, if it’s set to 3, it means that the system will make a maximum of three retry attempts for message resending.
  • SCHEDULER_RETRY_SECONDS - This configuration parameter defines the time interval, in seconds, for retry attempts. For example, when set to 1, it indicates that the system will retry the operation after a one-second delay.

Scheduler setup guide

Revised Cache Key Organization

To ensure a smooth transition for the 3.4.1 release, it is crucial to make use of the clear cache endpoint with the following request body:

Request:

POST /api/internal/cache/clear

This endpoint is designed to purge Redis caches selectively. It will exclusively delete caches that are specified in the admin microservice properties under the property key: “application.redis.clearable-caches”.

Request body:

{
    "cacheNames": [
        "events",
        "admin",
        "allowedSwimlanes",
        "initiatedProcessFromStartEvent",
        "flowx:core"
        ]
}

Please take note that after upgrading to the new system version, you should refrain from including the flowx:core cache in the request body when invoking the clear cache endpoint to avoid unintended consequences.