Aurachain v3.8.0- Release Notes

Aurachain Blockchain module is growing and expanding so that it can offer the best functionalities and user experience on the market. There is a long way to go and we are far from being done, but we are excited to show you where we are now:

• We unified the blockchain module design to be on par with the Aurachain Platform
• A lot of work was done under the hood in order to make all applications backwards compatible
• The creation of multiple Smart Contracts on each application is now a reality with a new user-friendly design

• Users can create functions with their respective Requests and Responses for each created Smart Contract belonging to an application.

• Users can create events with their respective Requests for each created Smart Contract belonging to an application.

• Functions have many types like public and private, while events can be set-up to be continuous or on-demand.

• Users can preview, download and delete the Smart Contracts code.

• Functions code can also be previewed and deleted on demand for a more flexible use of Smart Contracts.

• Created functions and events can be easily edited at any given movement but you need to remember that all changes will be executed when the application is published.

• Users are able to import Smart Contracts, in the Blockchain module of any application, by uploading a Smart Contract file – ABI – for Ethereum based blockchain.

.

• We added a new activity node called Blockchain Event, that will listen for added events on a smart contract.

Basically, when the instance will reach this activity, it will listen for a specific configured event that could be any type of transaction.

• We implemented an integration with MetaMask which is an extension for accessing Ethereum enabled distributed applications.

MetaMask lets the user create and manage their own identities (via private keys, local client wallet and hardware), so when a transaction is performed to the blockchain, the user gets a secure interface to review the transaction, before approving or rejecting it.

• Two new activities were added to the Smart Contract diagram (the former Blockchain diagram): Call Function Node and Emit Event.

Call Function Node will help the user to add functions from other Smart Contracts, linked to the application, to a certain function’s logical schema;

Emit Event is used to emit any events. An event is triggered to which anyone can listen. Different libraries offer different implementations and for different purposes, but the basic idea is to provide a framework for issuing events and subscribing to them.

• Design tweaks were made on the User Modal from the Admin module, for a cleaner UI.

• We also introduced a brand-new component in the UI Builder – the data “Grid” component.

It can be populated with data received via an API-Call, its columns are highly customizable to allow displaying and hiding data and it also gives the user data import/export capabilities. Finally, data imported via this grid can be persisted in the data-model.

• We removed the HTML display of sent messages from the messages tab in Process Inspector.

• • Filtering for attributes in the Document Builder’s data model selector has been upgraded for easier use (the search text box is now focused by default).