v3.4.0-September 2023 🆕
Welcome to the FLOWX.AI 3.4 release! 🚀 This update introduces exciting new features and improvements to enhance your experience with FLOWX.AI. Get ready for an extraordinary journey! 🚀
What's New? 🆕
New versioning module
We're thrilled to introduce enhancements to the Versioning module. Explore the Versioning section for more details.
Fresh nodes: Timer Events
These nodes enable you to trigger specific actions or events at predefined time intervals, durations, or cycles. With timer event nodes, you can design processes that respond to time-related conditions, ensuring smoother workflow execution and enhanced automation.
Three primary Timer Event node types:
- Timer Start Event (interrupting/non-interrupting)
- Timer Intermediate Event
- Timer Boundary Event (interrupting/non-interrupting)
So whether it's reminders, recurring tasks, or tasks with deadlines, these Timer Event nodes are your go-to for keeping things in sync with the clock.»Timer Events
Font Management allows you to upload and manage multiple font files, which can be later utilized when configuring UI templates using the UI Designer. You can now upload multiple TTF font files, the platform will identify additional data like font family, weight, and style for each file. That can be done using the new menu entry added under Content Management > Font files.
Attributed strings for Markdown support
Enhance the design of UI components with the new Markdown support, including features such as bold, italic, strikethrough, and clickable URLs. This feature integrates with the following UI components: text, switch, and message indicators, ensuring a consistent and polished rendering experience.
Supported tags in the current iteration: bold, italic, bold italic, strikethrough and URLs.
- bold italic
Let's take the following Markdown text example:
Be among the *first* to receive updates about our **exciting new products** and releases. Subscribe [here](flowx.ai/newsletter) to stay in the loop! Do not ~~miss~~ it!
When running the process, it will be displayed like this:
Bug Fixes 🔧
- Addressed a bug where the boundary sequence incorrectly moved to the parent node after copy-paste.
- Resolved an issue where the "Select Sequence" buttons within the node UI interface could overlap, ensuring a better user experience.
- To edit a selected node label, press "R," which puts the label in edit mode. After editing, press "Enter" to save the new name.
- To copy selected nodes, use "CMD/Ctrl + C," and to paste them into a selected swimlane, use "CMD/Ctrl + V."
- To delete selected node(s), press "Backspace."
- Revamped Object-Level Settings with Enhanced Attribute Flags.
- Bid farewell to the autoarrange function in the The fallback content to display on prerendering.
Gremlins to Watch Out For 🙁
- Slider UI element: Our slider component can be a bit mysterious at times. Currently, it enjoys a game of hide-and-seek with the correct value when sourced from process data.
- Document preview UI element: Our document preview component has a unique sense of style. It prefers to take up only a portion of the screen, even when told to "fill" the entire width. It's a rebel with a cause.
- Business rules: Our The fallback content to display on prerenderinghave a language barrier, but they're working on it. Changing the language of a business rule doesn't always lead to using the new language for execution. It's like they have a favorite phrase they won't let go of.
- Process Designer: Deleting a boundary node in the process designer and coming back from the UI Designer doesn't always clean up the associated sequence from the boundary event. It's like they left a party and forgot their hat.
- Timer Events:
- Our timer events can sometimes be a bit shy and not show up on the canvas when added after creating a new process version or branch. They need a little nudge to make their appearance after refreshing the page.
- Mandatory Fields Error Messages: Our system has a sense of humor when it comes to mandatory fields. It forgets to deliver the error messages when these fields are left empty. It's a bit too laid-back.
- Timer Expression Validators: Our timer expressions can be a bit wild and free-spirited because they don't always follow the rules. We haven't implemented their validators yet, so they do as they please.
- Timer Events on Read-Only Process Versions: Our timer events are a bit of a rebel when it comes to read-only process versions. They refuse to disable their fields, as if they have a mind of their own.
- Our versioning system can be a bit finicky at times. It might throw a server error when merging branches or refuse to ignore the Flowx UUID key, causing conflicts. And sometimes, the branching graph prefers to play hide-and-seek during import/export. But hey, we're working on it!
- Swimlane Allocation UI: Even after a process definition is deleted, you might catch a glimpse of the UI for swimlane allocation. It's like a ghost from the past that refuses to fade away.
For deployment guidelines, refer to:»Deployment guidelines v3.4.0