Simple application - non-extended and extended

Original post in this newsletter.

Using only native functionality

In the example below, you can see the creation of a process-based application using our tool . After completing the application (which took only a minute), the Petriflow source code was downloaded and then uploaded in the eTask - a tool for running applications on the . With the help of NAE, eTask can compile or interpret Petriflow source code at runtime on the server, without requiring a deployment process. The entire "deployment" consists only of uploading the file.

Once the Petriflow application is uploaded and compiled into the three-tier architecture of the eTask web application, users can (provided they have the appropriate roles) create new process instances, also known as cases, of the process-based application.

Using extended functionality by Java

Our eTask is a three-tier Java Spring Boot web application. This means that developers who are not full-stack web developers, but can implement simple functions, are still able to extend the ActionsAPI by adding just a few lines of code to the CustomActionsDelegate class in their own eTask application.

NOTE

The eTask can be downloaded for free from our GitHub.

Additionally, you can request new functionality from us, and we will implement it into the NAE.

The example above shows is a simple process that generates a QR code (image) from the text provided by the user. When the value is set on the text field (via a set event), the QR code image is generated automatically.

In the first task form, the user can edit both the text field and the file field that stores the generated image. In the second task, the user can only view the file field and open or download the generated picture.