Low-Code Development

Flows for APEX is an extension for Oracle Application Express (APEX) that lets you model and run processes based on the BPMN 2.0 standard. This blog article will address some of the key features introduced with version 21.1. Setting process variables before and/or after each step With the help of process variables, information can be stored persistently in the database over the entire duration of a process instance. You can set a process variable through the PL/SQL API or, with 21.1, do this declarative for each step in the BPMN model. The variables are meant to be set at special trigger points in the model (e.g., after a task has been executed or before the process is split up at a gateway) and read out again at a later point in time without the need of an APEX session. Restart failed tasks Sometimes the execution of a step in a process fails, so that the process cannot continue. In this case, the transaction of the current step is rolled back, and the instance is set to an error stat

After months of hard work, we are proud to announce the general availability of the APEX extension Flows for APEX 21.1. If you are looking to model and run business processes all within the Oracle Database, make sure to check out Flows for APEX. You can download a free copy of this open source software at https://flowsforapex.mt-ag.com . Major new features of 21.1 are:   - Model-driven approach to set process variables before and after each step   - 3 process plugins to declaratively integrate a process model in your own APEX app   - Auditing   - Major upgrade of the Flows for APEX application with numerous functional, productivity and UI enhancements, like:     - Restarting a step     - Side-by-side view     - Dark mode support Have a look at the readme file in the software distribution to see a complete list of all enhancements. Existing Flows for APEX customers can migrate to 21.1 by script, but should be aware of the fact that the transaction model has changed with 21.1, so your ap