Workflow Server
Stand-alone ready to deployed on-premises or in the cloud
Workflow Server is a ready-to-use Workflow Engine-based application with an administrator panel that you can deploy into your infrastructure. It can be integrated with NodeJS, PHP, Ruby, .NET, or Java applications via a REST API.
Workflow Server is a key component for managing the lifecycle of business objects within your enterprise. Workflow Server supports all the functions of Workflow Engine.
· Physical servers
· Virtual machines
· Cloud
· Azure + Azure DB
· Amazon cloud
· Google cloud
· Fully multi-tenant Saas*
· Docker
· User dashboards
· Manage all Configuration for the product
· Manage workflow definitions
· Manage workflow instances
· Manage business code
· Manage plugins
· Manage logs
· Manage users
· Route tasks to users, with powerful configuration features.
· Route to roles
· Define task timeouts
· Define task reminders
· Send email notifications
· Assign based on rules
· Parallel processes
· Okta
· Custom OpenID server
· Connect to existing directory services like Active directory (LDAP)
· User synchronization
· Forms authentication
· OAuth authentication
· Single sign-on
· Role based security
· Application roles
· System wide logging
· Logs error, warning, information
· Custom logging from processes
· Complete code stack trace
· Callback API (WebHooks)
· Full REST API
· Knowledge base with many code samples and videos
· Distributed server processing
· Load balancing* (setup by customer)
· High availability* (setup by customer)
· Synchronize environments (configuration import/export )
· Easily manage all Micro services
Workflow Server can process about 200 requests per second on a typical 4 GB RAM server. The response time of a single request is about 20 ms. Performance does not degrade with up to several million records with default database server settings. Custom database server settings are required for larger volumes of data. Performance can vary drastically depending on your schemes. We have prepared SoapUI tests so that you can test performance yourself.
We tried to make Workflow Server as lightweight and simple as possible, yet, with a wide range of capabilities. Key capabilities of Workflow Server are:
· Workflow processing
· Determining a form by workflow state and current user role
· HTTP API integration
· Reports
Workflow features are:
· Workflow scheme versioning
· Changing the process scheme in real-time
· Inbox/outbox folders
· Process execution simulation
CREATE DROPLET
Architecture
Workflow Server is based on Workflow Engine and has an HTTP API, a dashboard for an administrator and a set of reports. The architecture of the product is depicted below. When developing Workflow Server, we were guided by the generally accepted rules of building program products.
# |
Built-in module |
Purpose |
1 |
Workflow Engine |
Responsible for workflow processing and has a graphic designer for workflow creation |
2 |
Business process flow |
Allows to determine the current workflow form depending on the state and user role |
3 |
HTTP API |
External API module for integration with other applications |
4 |
Dashboard |
UI for administrator. Allows to create and modify schemes and manage workflow processes |
5 |
Reports |
Statistic reports on schemes and performance |
Workflow Server Integration scheme
Workflow Server has a set of 2 APIs for integration:
1. Workflow API - allows you to create processes and set their states.
2. CallBack API (WebHooks) - allows you to include additional actions and conditions to the workflow, and get notifications on workflow state changes
An example of integration of Workflow Server into a microservice architecture with and without an enterprise service bus is depicted below. Integration with enterprise service bus:
Workflow Server integration without enterprise service bus
The foundational tool for business process management (BPM), Workflow Engine, enables automation of workflow design using low-code visual builders. It is built using JavaScript libraries and the.NET Framework/.NET Core.
Despite being a part of Workflow Server, Workflow Engine can be purchased separately. It enables workflow processing and proper integration by giving graphic designers the tools they need to construct process workflow schemes. This software component also makes workflow management, execution, and visualization easier.
Workflow Engine can resolve several tasks and issues related to process automation as described below:
· Parallel and hierarchical process resolution.
· Workload optimization.
· Business mission-critical process accomplishment.
· Process planning, implementation and follow up.
· In addition, Workflow Engine main functionalities can be implemented by creating C# objects which facilitates software integration. These objects are:
WorkflowRuntime - It provides an API for the Workflow Designer and enables process creation, document management, command execution, setting a process state and so on.
Designer allows you to easily create interactive workflows of any complexity, there’s no need to draft them programmatically. We reated this native element to let you design, model, edit and visualize your custom workflows.
Drag and drop and configure the step properties
React, Angular, plain Javascript ready
Fully graphical web-based process designer
Many out-of-the-box steps (and growing)
WYSIWYE – What you see is, what you execute
Build and use your own custom steps
Build and use your own data types
Build and use your own business objects
Embed the designer in any application
Localization (RTL)
Stores workflow definitions as XML
Write your custom code C# in the Designer
Scheme inlining
Workflow Engine offers its users all the components necessary to implement workflows of any complexity; and helps them to maintain consistent business processes. Workflow Engine is designed to improve organizational efficiency and productivity, allowing companies to concentrate on job performance rather than workflow management.
ACTIVITIES
Define document statuses, sets of methods to be executed and other workflow activities.
TIMERS
Set an interval or date/time to trigger a transition from one activity to another.
ACTIONS
Connect activities with transitions that are triggered by commands or timers.
ACTORS
Add multiple actors with different roles, including users and external systems.
COMMANDS
Specify commands that should be executed to trigger a specific transition.
TRANSITIONS
Connect activities with transitions that are triggered by commands or timers.
© Copyright 2000-2023 COGITO SOFTWARE CO.,LTD. All rights reserved