Datapolis Workflow App Registration
Beautiful Visual Designer
There are two visual designers included in our software. Our graphic designers and UI specialists have made every effort to make the workflow creation not only easy and intuitive, but also aesthetically pleasant.
Separating Business Logic for better readability
The main designer is used to define the business logic of the process (process phases, phase transitions, roles involved in the process, etc.). It is separated from the designer for automated activities (such as emailing, creating items in lists or mathematical calculations, etc.). This separation allows for greater readability of the business logic.
The third complementary part of the Datapolis Workflow Designer is the form wizard. Extremely easy to use, it allows you to create simple forms by dragging form fields and defining their parameters.
Flexible and Dynamic Permission Management
Datapolis Workflow Designer allows you to create any number of roles involved in the process. Participants in roles can be SharePoint users or SharePoint groups. Users can be added and removed from the role dynamically during the process.
Interface Integrated with SharePoint lists
Workflow user performs assigned assignments using an interface that is integrated with the SharePoint list. Using the context menu, user can select and perform workflow action assigned to the role in which he is assigned.
Clear Information About the Workflow phase
Sharepoint list on which the workflow is defined has 2 additional columns. First tells in what phase the workflow is, the second one informs about whether the workflow is processing or completed.
Launch Workflow Action and Fill the Form
Forms are closely related to workflow actions. Often, when user launching an action must also complete a form associated with this action. For example, by refusing a request we may be asked to fill the form and state the reason for the rejection.
Visual Workflow History
Each workflow has an easy-to-read history of its course graphically presented. The history shows who and what done in the process, where downtime occurred, what data was entered in the forms, and whether and where errors occurred in the process.