With Imixs-Cloud we started a new open infrastructure project, providing a lightweight kubernetes cluster for small and medium-sized organizations. This projects goal is to build, run and maintain business applications in a production ready and self managed kubernetes cluster. The main objectives of Imixs-Cloud are simplicity, transparency and operational readiness.
The runtime environment is based on Kubernetes and provides an easy way to setup and maintain a medium-sized kubernetes cluster environment hosted on virtual servers or bare metal. The project is open source and constantly under development. You can join the project on Github.
The project contains information how to setup a kubernetes cluster on bare metal servers or cloud servers.
With the next upcoming version of Imixs-Workflow 5.1.10 we will introduce the new Multi-Model Support. With this function, a long-running business process can easily be distributed into separate model files without having to split up a running process instance or create a new sub-process. This will make modeling much easier and clearer.
In difference to the the already existing feature of the Split Events, the model version can be changed within a running process instance by simply adding a link-event:
The outgoing event describes the new model version in the workflow result definition:
The Imixs-Workflow engine will execute the new event immediately within the new model and automatically assigns the already running process instance. The consistency of the process will be guarantied by the Imixs-Workflow Kernel.
This modeling approach is particularly interesting for long-running, complex business processes with multi-stage approval procedures because it significantly increases the maintainability and overview in such models.
Today we released version 5.0.2 of the Open Source Workflow Engine Imixs-Workflow.
The new release includes – beside the general new support of Eclipse Microprofile – some important new features. The main feature of this release is a new implementation of Imixs Adapter API. This API supports now two kinds of adapter interfaces.
The SignalAdapter can be used to implement a fine grained control of the event processing life cycle.
The GenericAdapter interface provides a model independent extension point to implement generic API features.
One of the first implementations is the new AccessAdapter class. This adapter controls the ACL defined by the Imixs-BPMN Model definition. This adapter can also be a good starting point of custom generic adapters.
Together with the Imixs Plugin API the Adapter API now provides developers with a strong and flexible extension mechanism to implement all kind of human-centric and microservice based workflow applications.
Imixs-Office-Workflow is an open source platform. It helps you to digitize your business processes, connecting your employees, customers and partners. Take advantage of a powerful integrated workflow suite for your business.
BPMN: Conditional Events
BPMN models, using conditional events, can now be parsed correctly even if the model contains standard BPMN elements between an event and the condition:
The most important improvement of version 4.4 was the transaction support of Lucene event logs. With version 4.4.4 of Imixs-Workflow, this feature is now stable and shows also a very good performance in long running transactions.
Today we released our new Version 4.4 of Imixs-Workflow. The new release 4.4.0 includes new features, several bug fixes and minor enhancements of the Imixs-Workflow API.
The most important new feature is the Lucene Index which is now supporting transnational Read Committed. In the past, after a transaction was roll backed, in some situations the lucene index contains uncommitted entries, which leads to unexpected search results. With the new version 4.4 a complete re-implementation of the Lucene UpdateService has been realized. The indexer is now more robust and reflects only committed transactions.
Another new feature is the GenericSchedulerService. This new service interface can be used to implement custom schedulers. The implementation of such a scheduler is now quite easy and the scheduler is automatically managed by the new SchedulerService EJB. In the next releases we will re-implement also the existing WorkflowScheduler.
Read more about the project at: www.imixs.org. If you have suggestions or comments please contribute on Github.
The Imixs-Workflow project now supports the generation of SEPA files. The Single Euro Payments Area (SEPA) is a payment-integration initiative of the European Union for simplification of bank transfers denominated in euro. Imixs-Workflow started the new adapter project Imixs-SEPA-Adapter to simplify the SEPA integration in any kind of finance workflow. The project provides a new scheduler service to generate SEPA files on a daily basis. For example this adapter can be used to export the results of an invoice approval process into a SEPA file which can be used in any payment software.
Free and Flexible Adaptability
The Imixs-SEPA-Adapter is based on BPMN 2.0 and the Imixs-Report functionality to allows a free adaptability of the SEPA export to any custom workflow project. This adaptability is important because invoicing workflows differ from company to company. The adapter integrates seamlessly into an existing process and can be realized with a standard or a custom workflow mode based on the BPMN 2.0 standard.
The SEPA file generated by the adapter can be distributed into the task list of the companies finance team or sent via E-Mail notifications. For security reasons the distribution via the task list is recommended as this fully utilize the strict access concepts of Imixs-Workflow.
Detailed information about the adapter project can be found on Github. The project is in continuous development and contributions from the community are welcome at any time.
The interesting thing here is that you only need a few lines of code to get the full functionality of a human-centric workflow engine. This is possible because in addition to the existing Jax-rs Rest API, the Imixs-Workflow engine provides services which can be easily adapted by the core concepts of an MVC-Application. Continue reading “First MVC 1.0 Workflow App”