Skip to content

Release 23.1

Latest
Latest
Compare
Choose a tag to compare
@commi235 commi235 released this 10 Aug 14:56
· 1 commit to master since this release
v23.1
ef777f0

Changes in this Release

  • Adds Due Dates and Priorities to bpmn:processes and to bpmn:userTasks, allowing declarative tracking of scheduling, priority and due dates.
  • Adds Task Assignment to bpmn:userTasks, allowing easier declarative assignment of tasks to potential users and groups.
  • Adds REST-enabling of the Flows for APEX API
  • Major upgrade to the BPMN Modeler, with new, modern-looking properties panel.
  • Enhanced support for modeling and viewing of collapsed subProcesses that can be easily expanded / collapsed.
  • Adds support for BPMN Child Lane sets, allowing nesting of lane sets inside parent lanes.
  • Adds explicit definition of relationship (or not) between Lanes and APEX roles/groups.
  • Adds Timestamp with Time Zone datatype option for Process Variables.
  • Adds binding of Process Variables into PL/SQL scripts, variable expressions, and element settings.
  • Adds support for binding non-varchar2 typed (i.e., number, date, timestamp with time zone) process variables.
  • Allows process variable substitutions to be used in all of the parameters of an APEX Page task.
  • Adds 'is Startable' information to Processes, along with users and groups that can start a process.
  • Allows BPMN diagrams to contain Groups and attached Annotations.
  • Adds Automation to create daily, month-to-date, monthly, and quarterly statistics on process and step performance.
  • Enhances Flows for APEX Application dashboard to display process and step performance, errors, and waiting time statistics.
  • Adds auditing / logging of changes made to process diagrams, to complete the existing logging capabilities
  • Adds the ability to create a summary document, as a JSON document, describing all actions taken to run a process instance.
  • Adds an Automation creating archive summaries for all recently completed process instances into an archive table or OCI Object Storage.
  • Adds an automation for automated purging of old logging data and statistics summaries.
  • Allows an administrator to easily change the timer polling frequency, or temporarily enable / disable timers on non-production systems.
  • Experimental Feature - Adds MessageFlow between sendTasks, receiveTasks, Intermediate Message Catch and Throw events. Phase 1 of more...
  • Adds support for additional languages Italian, Simplified Chinese, Traditional Chinese, Korean.
  • Required APEX version increased to APEX v20.2

Installation Instructions

1. Fresh Install

See installation instructions

2. Upgrade from Flows for APEX v22.2

See Migration Instructions

3. Plugin for APEX Approval Tasks Integration (APEX 22.1+)

  1. Download the file f4a_approval_return_result_plugin.sql.
  2. Import the plugin into your application.
  3. More information can be found in our documentation.

4. Enabling the REST API

Use the steps as documented in the installation instructions.
We also include a Postman Collection and the OpenAPI specification in the release assets.

  • FlowsForAPEX_v23.1_Postman_Collection.zip
  • FlowsForAPEX_v23.1_openapi_3_0_0.yml

5. Combined Task List for APEX Approval Tasks and Flows User Tasks

If you are running on an APEX release which support Approval Tasks you might want to run FlowsForAPEX_v23.1_Combined_Task_List.sql as the Flows schema from the assets below.
This view allows you to have a combined view of Flows & APEX Tasks.
You can find more information in our documentation.

6. If you upgrade APEX to a new version after installing Flows for APEX

If you upgrade APEX to a new version, run the after_apex_upgrade.sql script as the Flows for APEX user after upgrade. You will be prompted / reminded to do this on opening the Flows for APEX application if it detects that APEX has been upgraded.

Bug Fixes

Issue 681 - Logging of Step Key, Due Dates and Priority.

Adds Step Key to subflow_log and step_event_log so that a unique task identifier is present in the logs. Also corrects an omission of priority and due date information from the logs. Step Key, Priority and Due Due are also added the instance summary JSON document.
You should NOT run this after running the combo-675-676-681.sql script. You can run the combo-675-676-681.sql script instead of running this script (better option).
To install - Run the fix-681.sql script as the Flows for APEX user.

Issues 675, 676 and 681 - Support for Oracle Database 23c (23.3.0)

This provides support for Oracle Database 23c (23.3.0) by fixing an issue in Flows for APEX and providing a workaround for a database 23c 23.3.0 issue. Running on 23c requires issue 681 to also be fixed, and so is released as a combo script that fixes issues 681, 675 and 676. It can be run if 681 has or has not already been fixed. This script can be run on 19c or 23c databases.
To install - Run the combo-fix-675-676-681.sql script as the Flows for APEX user.

Issue 690 - Updating Flows for APEX after upgrading APEX version.

The Flows for APEX app added compatibility checks on startup in 23.1 to check that the app is being used on the matching engine version, and to check if APEX has been upgraded. If APEX has been upgraded, a script is required to updated the environment parameter and then to re-compile all of the Flows for APEX PL/SQL packages. This script was omitted from the distribution, but is provided here as after_apex_upgrade.sql. If you upgrade APEX to a new version and receive a warning, run this script as the Flows for APEX user.

Assets 11
3 Join discussion