Mechanism “Transfer of cases”

It allows you to release documents from one user to another. For example: an employee leaves and the documents, tasks, approval processes etc need to be passed to another employee.

The tool allows:

  • Transfer all the documents from one user to another user.
  • Transfer documents of various types to different users.
  • Release the role in a particular type of document to another user.

Mechanism “Document reading history and changes”

The mechanism can be quickly connected to any type of document and receive detailed information about history of reading and changes ot the document.

In the setting of the mechanism you can set the number of fields you want to track:

  • All fields in the document.
  • Only fields with a caption.
  • Selective list of fields to login.

Available information in the history of changes of the fields:

  • Who made the changes and when.
  • Which field has been changed.
  • The old and the new value of the modified field.
  • All information is grouped by sessions and easily searchable.

Mechanism “Control of document modes”

This mechanism allows you to see users who are able to read or edit the document. If someone saves a document, all users who have the document open, immediately receive a notification and updated version of the document.

You can prevent simultaneous editing of the document just turn on or turn off the setting.


Mechanism “Barcode”

This mechanism allows you to give an individual barcode to any document in the system. The barcode can be assigned automatically during registration of the document, or manually.

When the document has a bar code it can be quickly found using the barcode scanner. If you scan a barcode on a paper document, the document will be opened immediately in the system interface.

Mechanism “Requests and decisions”

This mechanism was created so users can comment and approve documents and tasks.

Capabilities of the mechanism:

  • Define a task and assign responsible employees.
  • Executive overview
  • Delegating tasks.
  • Periodic decisions.
  • Creating subtasks.
  • Notifications to the participants of the process.
  • Amending deadlines.
  • Analysis of workflow.

The “Requests and decisions” mechanism can be flexibly set for each system application. For example: you can calculate with formula who is the controller on the decision; who signed it, adjust the conditions of hiding the fields when setting assignments, etc.

Mechanism “Fields synchronization”

The mechanism is created to add background rules for synchronising fields between documents. For example, if a field value changes in one document, this rule changes field values in related documents.

To do this:

  1. Create a rule for monitoring a particular type of document.
  2. Configure rules for detection of dependent documents.
  3. Customize actions that need to be performed in case of changes.

Appearance control – static and dynamic styling

Each element of the interface has a set of properties responsible for appearance. Any element can be easily styled as you want, and also depending on various conditions.

Styling options:

  • Build in style scheme.
  • Customized CSS classes.
  • Customized CSS styles.

Also, the appearance of each element can be changed dynamically depending on various conditions. Performing any conditions the element can be assigned an additional CSS classes and styles.

For example: if the data in the “number” and less than “0”, then assign the field “color: red;” CSS style


Form properties

Form Properties has a number of settings that define the behaviour of the form.

The most important settings:

  • Determination of applications and a group of elements which are used on the form
  • The name of the form.
  • On which device should the form work (any, for pc, for mobile device).
  • Which HTML title header needs to be formed (the formula).
  • In what situation you want to prevent edit the form (formula).
  • The initial opening of form modes – read or change (formula).
  • Allow automatic saving of documents after work with any field.
  • CSS classes and CSS styles – for styling forms as you wish.

Form events

Each form has a configuration with the list of various events. Each event is executed in a certain situation. The workflow logic uses LUA language.

Events options:

  • While loading
  • Before rendering
  • After rendering
  • Before saving
  • After saving
  • When checking changes

The source code of the forms

All source code of the forms is stored in XML format.

XML can be easily modified, or replaced. Any application can be modified to the needs of your company.