Overview
The workflow service is a Nirva service that implements the logic of workflow scenarios for managing long running transactions.
The Nirva workflow service helps to architect an application from a business point of view. The workflow supports the business logic that is coded into activities. This business viewpoint only displays the different activities, their status and how they are organized together to meet requirements.
The service provides all the environment and functionality to control workflow processes and their various states. The execution of the activities is not part of the workflow and remains controlled by Nirva applications by using standard Nirva features. As usual, Nirva provides all the necessary functionality to start and run activities directly or in the background, scheduled or not, to wait for events, to send and receive messages, etc.
This allows the sharing of a complex business process on different servers, optionally having dedicated servers for some activities. The processing of some workflow activities can also be controlled by external software that can communicate with the Nirva workflow using client connectors.
The main features are:
Current version 3.07
Downloads
The Nirva workflow service helps to architect an application from a business point of view. The workflow supports the business logic that is coded into activities. This business viewpoint only displays the different activities, their status and how they are organized together to meet requirements.
The service provides all the environment and functionality to control workflow processes and their various states. The execution of the activities is not part of the workflow and remains controlled by Nirva applications by using standard Nirva features. As usual, Nirva provides all the necessary functionality to start and run activities directly or in the background, scheduled or not, to wait for events, to send and receive messages, etc.
This allows the sharing of a complex business process on different servers, optionally having dedicated servers for some activities. The processing of some workflow activities can also be controlled by external software that can communicate with the Nirva workflow using client connectors.
The main features are:
- Workflow definition and deployment.
- Logic defined around activities and links.
- Unlimited number of workflow processes (only limited by disk size).
- No need of external database.
- Auditing.
- Correlation data for retrieving workflow processes using business data.
- Possibility to associate business specific data with process or activities.
- Web configuration, administration and history.
- Deployment facilities.
Current version 3.07
Downloads
Updates
Version 3.07
Version 3.06
Version 3.05
Version 3.04
Version 3.03
Version 3.02
Version 3.01
Version 3.00
- Optimisation of database synchronisation process. Now if you have many workflows, starting the service is faster.
- Changing the audit page size to 50 in the configuration.
Version 3.06
- The purge mecanism was based on process creation date instead of process end date. This has been corrected by adding a new end date field in the workflow process database. When updating the service, it may take some time for the service to load because it has to update the database for each workflow. For processes created and ended before the update, the end date is equal to the creation date.
- Extended status has been implemented. It is possible now to search for processes terminated successfully (completed), with error or manually stopped.
- Possibility to edit process variables from the interface (except system variables).
Version 3.05
- Compatibility with Nirva server 4.8.000: The management of variables has changed with the server 4.8.000. It is possible now to define the character used to recognize a variable in a Nirva command. This can be changed at application level (in application.dsc file) and at command level (parameter NV_VAR_IDENT). If you don't change the default character (#) you don't need to update the service. If you change it it is recommended to update the service otherwise some configuration screens may not work properly.
Version 3.04
- Linux compatibility: we compiled with older versions of glibc (2.11.3) in order to be compatible with more linux versions.
Version 3.03
- Minor bug correction for linux versions: the internal time functions were not thread safe. We didn't see any impact until now for this bug.
Version 3.02
- Linux 64 bits version (x64).
- Linux 32 bits version has been recompiled using libstd6 instead of libstd5.
Version 3.01
- Exception and locking issue. In some rare circumstances, the workflow service may produce an exception making some functions to block. This occurs on queue activities when several threads in parallel work on the same process. Another consequence is that some activity variables are suddenly re-affected to their parent activity.
- Windows 64 bits version (x64).
Version 3.00
- Removing license control.