You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 5
Next »
General requirements
- Business process automation – process definition in design view and its subsequent publication to BPM solution, where the process is executed automatically
- Business rules – the ability to integrate business rules into process and evaluate them
- Support for low-code implementation, where the development is based on graphic basis using symbols and their interconnection in a defined graphic notation
- Most of the development is Joget is Drag and Drop features -
- Integration into published interface, support of different apps
- Support for manual tasks that must be performed by specific workers without automation
- There are activities and tasks that can map to manual tasks
- Mobility support, the ability to access solutions from devices of different types
- Monitoring of process metrics, evaluation of process throughput, identification of possible improvements, data for process analysis
- Securing the execution of business processes, ensuring protection
- System setup and management, environment supervision
- Available out of the box – Check System Settings
Functional requirements:
- GUI designed for drag & drop process design, encapsulating processes into reusable sequences; collaboration to create process diagrams
- All the builders including Form, Datalist, User Interface, Process and in DX API Builder and Report Builder are all Drag and Drop
- Both Form and Processes have capabilities to reuse
- Decision-making rules: flexibility of internal decision-making rules; ease of integration of external rule engine
- Form designer with possibility to specify input fields and implement validations
- Yes, you can specify a various property
- Versioning, deploying a new “on-the-fly” version of processes, without the need to interrupt work in progress
- User portal – management of the tasks of the user and teams; integration to email clients, notifications
- Problem solving in running processes – possibility of manual intervention such as move the process to the next step, skip the step, assign it to another user, etc.
- Complete Admin functionality available to manage processes
- Process measurement and reporting. Detailed monitoring of process state, number of instances in different states, processing time of different paths, etc.
Non-functional requirements:
- Integrability:
- Support for Rest API
- Support for containerization, integration into microservice architecture or into IoC containers (Java, Spring, SpringBoot)
- Pre-assembled external connectors / plug-ins
- Most of the integration can be achieved via JSON API Tool
- Integration into message broker platforms (Apache Kafka)
- RPA integration (specifically UiPath)
- Supported databases for persistence of metadata and messages
- All Major Databases supported including MS SQL, Oracle, MySQL, etc.
- Operability:
- Deployment in on-premise, cloud, hybrid mode
- Deploying processes into production, supporting automation
- Possibilities from the perspective of SLA - high availability of solutions; 24x7 mode option
- Security, auditability, logging, integration to external SIEM, etc.
- Performance and scalability
Workflow is focused on support of manual tasks, typically as a sequence of manual activities of employees working on different roles. Workflow is a complex procedure divided into sub-sections that are performed by employees in different roles. Workflow can contain rules and assignments for different users. Workflow is manual process oriented.
Workflow functions:
- Definition of workflow in predefined view including the definition of the data sentences over which the workflow is performed
- Manage permissions in each workflow step, set workflow to roles, map people to individual roles
- Custom data visibility for each step and role that is involved in workflow
- There are various ways to manage the visibility of date based on roles
- Definition and pass-ability of workflow according to pre-defined rules
- As shared earlier there are various ways to define rules
- Notification of new assigned task, notification of assigned task with expired processing time
- Overview of workflows and status of all workflows
- Integration into the surrounding environment, the ability to trigger actions on surrounding systems
- Various ways to integration as shared earlier in the documents
- System setup and management, environment supervision
- Support for mobility (such as mobile devices, …)