Say Hello to Aurachain v3.10.0 – Release Notes


RELEASE DATE: 2 – February – 2020

Say hello to Aurachain v3.10.0. We’ve made more than a few tweaks and improvements under the hood in this version to make your Aurachain experience even better than before.

We also made important steps forward by adding new functionalities to help you gain more control over how you create and use the Global Data Model feature.

What’s new?

One of the most exciting pieces of news is about our functionality regarding the shared database across the platform’s applications. With the new Global Data Model, your business experience across every application within the platform becomes truly seamless.

We also made a few additions to improve your overall user experience within our low-code platform.


No-code connections to existing databases

There’s a new capability to the Global data model. Now, we can work with external source entities. Working with these external databases is handled by what we call “connectors”.

Aurachain-integration landing page

Integration landing page

The first connector we implemented is for Microsoft SQL Server databases. This connector allows application builders to retrieve data from these databases and represent it as Global Data Model entities.

Create Integration

Create integration

It is easy to configure multiple connections to Microsoft SQL Server databases in order to retrieve data from them and use them in Aurachain applications.

The configuration is very user friendly and requires absolutely zero coding experience.

Add data from integration in GDM

Add data from integration in Global Data Model

All connections can be easily managed in a separate page called “Integrations” that supports all operations like create, read, update and delete.

Aurachain - integration edit

Integration edit

That’s it for our first connector. Stay tuned as there are more connectors to come in the next releases.

We’ve also added new interactions on the Global Data Model in order to improve and streamline your experience when creating apps.

Dynamic Task Execution

The only constant in life is change. To celebrate one more change, we are happy to share with you that we now support the generation of individual tasks to all stage attributed assignees.

In other words, all users that are assigned to a single task are now able to execute that activity at the same time.

We added an option named “Create a separate task for each assignee” to the Assignees tab in each human activity. The option will be displayed once a minimum of 2 assignees are selected or at least a data model attribute is selected.

Aurachain_v3.10.0_dynamic human task

How to create a dynamic human task in Aurachain v3.10.0 

If the option is checked:

  • The assignee source can be either a data model attribute or assignees from the user’s selector.
  • The system will send an individual task to all assignees assigned to the Human activity.
  • The flow will go to the next step after all tasks are completed (submitted by the user or expired).
Create a separate task for each assignee

Under the Hood updates

We here at Aurachain are preparing a lot of new and exciting stuff for the near future. That is why we are actively preparing for this future by making important updates under the hood. You might not see them, but you will discover a much-needed improvement in the quality of life using the Aurachain Platform.

Also, the engine, which puts everything in motion, got a well-deserved update and cleaning. We have worked diligently to uniform the behavior of every module throughout the platform.

  • Save behavior has been improved in the UI Builder module. Ensures better visibility of what changes are made in the UI Builder.
  • We updated the look and feel of every last one of the interactive interfaces for a much-needed sense of standardization.
  • The scripting capabilities have been enhanced. Now the onSave event will receive an additional parameter called “action” so that users can build logic around it. Also, the event order of execution has been fine-tuned. It is now possible to change whether a field is mandatory or not, at runtime, based on the submit action. Hence, the order of event execution is now: onSubmit scripts, mandatory check, onSave scripts.