This is a patch version part of the the long-term support for version 4.1.

Welcome to FlowX.AI 4.1.1 release. Let’s dive in and explore:

What’s New? 🆕

FlowX.AI Engine: Process Instance Data Archiving

Database Compatibility: Oracle and Postgres.

We are introducing a new system for archiving data related to old process instances. This enables the implementation of data retention policies, with more predictable storage usage and costs.

Some operations involving process instance data can be snappier, given the lower amount of data in the system and new structure. Archiving relies on partitioning data based on the process instance start time. Each partition is associated with a time period (day, week, month), and retention is defined by the number of periods maintained in the system.

Archived data remains in new tables in the database, optionally compressed, and is no longer accessible in FlowX. These tables can be compressed, copied, moved, archived, or deleted without affecting other processes in FlowX.

For more details about process instance partitioning and archiving, including configuration of the feature, see:

Process instance data archiving and partitioning

Changes 🔧

Task Manager: base URL configuration

We have enhanced the Task Manager plugin by adding the ability to update the baseUrl for tasks. If the task.baseUrl is specified in the process parameters, it will now be sent to the Task Manager to update the tasks accordingly.

Example of a Business Rule:

output.put("task", {"baseUrl": "https://your_base_url"});

This update streamlines the configuration process, ensuring that task URLs are dynamically updated and properly managed within the Task Manager.

View the application

Gremlins to Watch Out For

Keep an eye out for these quirks:

  • UI Designer: When relocating UI elements between parents, the elements’ order doesn’t always get the memo, causing a mix-up in the family tree. We’re untangling this knot!

Resources

For deployment guidelines and a seamless transition to version 4.1.1: