Here’s What’s New in Aurachain v3.14

This new release of the Aurachain platform highlights are:


  • App builders can now create complicated business flows with many synchronous or asynchronous (sub-)processes.
  • Task deadlines can now be customized to work around your company’s schedule.
  • Aurachain’s Single Sign On now works with OpenID Connect providers as well as SAML.
  • To help you comply with GDPR, we’ve enhanced the Process Inspector so admins can delete messages, API calls, documents, and comments.
  • The UI builder now allows numbers to be shown in bespoke or region-specific forms. A new script editor makes it easy to build and debug custom scripts on UI components.
  • The Global Data Model was improved to better coordinate collaborative efforts.

What’s new?

Multi-Process Capability

Applications built on Aurachain are no longer restricted to a single, linear process. Starting with Aurachain v.3.14, app creators can define any number of processes per application. Furthermore, they can link these processes to one another either synchronously or asynchronously in order to support the most complex of use cases:


Synchronous sub-processes are independent instances of the same application.


This allows you to build a parent-child relationship within a flow with the mention that the parent in this case will always wait for the child’s execution before continuing with its own.


Asynchronous sub-processes need to be completed before the parent process that triggered them can continue.


This allows the child process to get started while the parent process continues its flow.

We changed the Diagram into the Processes Module.


Here users will be able to:

  • Add new processes
  • Unpublished processes can be deleted
  • Processes can be duplicated and/or archived
  • Publish the application
  • Access each process’s diagram
  • Set the processes name, type, description and configure the retention

In order to have the possibility to create complex business flows, a new type of activity was added named “Process.”


The builder will be able to add the process activity to another process and map within the added activity the desired process that better fits the business case.


For complex flows to have more meaning, builders can decide on which route the main process takes depending on the decision on the child process.


Users can easily start processes from an application directly from the Dashboard or from the applications module and also filter tasks based on processes.


To answer more complex business cases, we’ve added the possibility to start processes directly from the task interface on demand.


These types of processes will always have an asynchronous execution, meaning that consumers will be able to continue their work while the interface’s started process works independently.


Because the multi-process feature is adopted platform-wide, the reports module was also updated.


The “Task and instances” label was changed to “Process data”.


The “Statistics” module was also updated to show the turnaround time per process.


All processes will be listed in the Reports left side bar so that users can easily navigate between processes.


A new column was added to the instances table, named “Creation Source”.


It will display the creation source for processes that are also used as child processes within other processes.

  • General Start – when a process is started via the create button in the start a process modal.
  • Start from external event (the name of the external event) -when a process is started via a start from an external event.
  • Parent process – Process activity (activity Name) – when a process is started from another process via the process activity.
  • Parent Process – Interface – Activity name – when a process is started via an interface component.
  • Scheduled start – when a process is started via a scheduled start.

Users can also load a child process’ data by accessing the process activity from the Reports diagram.


Given the fact that the reports module was crowded by the injection of an application’s processes list, we moved the Favorite Filters component to ease access for the reports type of consumer user.

The Process inspector module has also been updated to incorporate the multi-process feature. To this effect:


A new “process” was added in the filters section.


Now also archived applications can be included in the filter search.


For sync instances, a new field was added in the “Summary” section. The “Root instance ID” will display the child’s parent ID.


The retention period capability was also added to the summary card for every instance for a plus of control.


The deletion time capability was also added to the summary card for every instance for a plus of control

Note that running and failed instances once they reach Terminated, Completed, Archived, statuses then the retention period will change to deletion time.


Note that for sync processes the retention period and the deletion time cannot be modified. Only their parents can have these modifications made. Modifications on parent processes will persist immediately on the sync child process.


For both consumers and admin users, the timeline was updated so that it highlights where, when and by whom a child process was started.


Task interface-initiated process will also be highlighted in its parent process timeline.


Each parent process will display the location, time and user who started a process.


Each process will have its own timeline.

Schedules (working hours)

Want to prevent task deadlines from elapsing during off-hours? Working days, working hours, and holidays can now be defined in a new Admin area: Work Schedule. When a new task is created, its deadline will be computed based on the organization’s work schedule.

Single-Sign-On via OpenID Connect

OpenID Connect is replacing SAML as the most popular Single-Sign-On protocol. Therefore, we’ve added support for authenticating users via any OpenID Connect Identity Provider.

Additional GDPR Compliance Functionality

The GDPR gives data subjects control over their personal data. They may request that their personal data is removed, or they may withdraw consent for data processing. To help you comply with such requests, we’ve introduced the ability to anonymize or remove any kind of data from any process instance. This includes the ability to delete individual documents, notifications, comments, and even content sent or received as part of an API or Blockchain call. Even the instance name can now be changed.


Another requirement of the GDPR is specifying retention periods for personal data. To support this, we’ve introduced the ability to define retention periods per application, per process, and even per instance. Furthermore, the retention period of individual instance can be extended if data needs to be kept longer.

Global Data Model Enhancements

We enhanced the Global Data Model capabilities by introducing some new features like:


  • Individual entity publishing: Each entity can now be published individually, thus eliminating potential conflicts caused by publishing other draft-entities at once.
  • Single-user entity edit: To avoid editing clashes between two users, the entity edited by one user is disabled for any other users attempting to edit the same one. Nevertheless, multiple users will be able to edit different entities at the same time.
  • Also, GDM users will be warned when they leave the entity page without saving data.

Interface Builder Improvements

The script editor has been greatly improved and users will benefit from new capabilities like better warnings and error highlights, autocomplete for custom methods & functions, variables, and user interface elements.


Also, users can generate the code for the interface elements based on their label. The code pattern is camelCase and the code is unique at interface level.


Numbers may need to be displayed using specific separators for thousands and decimals, depending on corporate or regional standards. With Aurachain v3.14, app creators can apply three types of formatting to UI fields that are mapped to integers or decimals:


  • None (displays the value with no separators)
  • System settings (displays the value in the user’s regional format)
  • Custom (displays the value using custom separators)

Other Improvements

At a deeper technical level, we made some improvements too, so now the 50MB upload limit can be easily configured (can be removed, increased, or decreased) for several platform services by a DevOps engineer as per customer requirements.


On the advanced logic activity, we added a new capability (readFile method) and now users will be able to access the content of data model attachments on scripting activities.


In the Reports module, a new column (“Final stage”) is available, showing information about where each instance has been completed. This information can also be easily exported now.

Subscribe to Our Blog