When making large processes with multiple process definitions, things can become a bit hard to manage. Especially when there are references to state paths in other process definitions. It can also be hard to reuse processes and start multiple instances of them within a single flow in a way that doesn't cause collisions.
For those reasons, we are introducing a new model of process development where each process has its own state.
These new features are currently in beta.
Making use of features like timers, collections and gateways previously required managing a set of variables existing outside the Flow state that were used by JUEL expressions inside the diagram.
With these new handlers, it is possible to use those features without coordinating variables across the handler code and the expressions in the diagram.
Setting up a remote debugger to remotely debug code running on an external service can seem like a complicated task. Fortunately, Node.js and most popular editors make this quite simple.
Correctly configuring message tasks in your process diagrams has been a complicated and error-prone task for a long time.
In Flow-Process v11.6 however, we are introducing a new way of implementing and interacting with message-tasks without the complexities of correctly mapping up process variables and correlation keys in your task handlers.
The high degree of flexibility in the Stacc Flow platform enables solutions with very different characteristics and requirements. Below is a guide of the different components and infrastructure that may be tuned in order to improve performance.
We recommend doing a performance test before deploying the initial solution in production to ensure the cloud setup is tuned for your solution. It is also recommended to do a performance test before deploying major changes in production.