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.
With the latest version of Imixs-Workflow we support now a consistency Lucene search index coupled with the Java EE container based transaction concept.
Writing a Lucene Index during a Java EE transaction, coupled to JPA database operations, it becomes quickly difficult to keep the Lucene index consistent. The reason is that a lucene index can become inconsistency if you write the lucene index within a long running Java transaction. In case the transaction fails lately, there is no way to roll back the already written lucene index automatically. This is different to the build-in roll-back functionality of a SQL database which is only writing new data in case the transaction succeeds. Also clients reading the index before a running transaction is closed will read uncommitted index data which will lead to wrong search results. Continue reading “Lucene Index Consistency”
Within the Imixs-Workflow project we started our first sample application based on the new Jakarta EE web framework MVC 1.0. The sample application demonstrates how an Imixs-Workflow application can be build with MVC 1.0.
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”
With Office-DMS we introduce a new DMS solution for small and medium enterprises. DMS-Office is different from the usual DMS and archive solutions. Office-DMS connects documents and workflow and focus on the business process behind a document. The solution is based on the open source Workflow Platform Imixs-Workflow and offers a cost-effective alternative to license-chargeable DMS solutions.
Today, when you design a modern business application, you have to deal more and more with constantly changing business rules. The reason for this is that not only the software industry follows the agile path. Business processes are also subject to a permanent change. At the same time, however, business processes are becoming increasingly complex as more and more information is influencing our business world. In the following I will show how business processes and their rules can be modeled with the help of BPMN.
Continue reading “How to Model Business Rules?”
With the new version 1.8, Imixs-BPMN is now available for all current Eclipse platforms and also fully integrated into the latest version of Eclipse Oxygen.
Imixs-BPMN in based on the Open Source BPMN modelling tooling for Eclipse Oxygen, which is currently available in version 1.4.3. See the Eclipse BPMN Homepage for what’s new. The current version 1.8 of Imixs-BPMN can be installed from here.
Imixs-BPMN takes the full advantage of all the capabilities from the BPMN 2.0 standard and complements them with the requirements to a modern workflow management system. Imixs-BPMN enhances the Eclipse BPMN2 modelling Framework with the aspects of a human-centric workflow model executable on the Imixs-Workflow Engine.
The Imixs-Workflow engine provides a set of modern Java Enterprise Services to create and manage process instances based on a BPMN 2.0 definition. The Imixs-Workflow engine can be embedded into a Java Enterprise application as well be deployed into a Microservice Architecture as a Docker Container. See the Imixs-Microservice Project for more details.
Also for older versions of the Eclipse Platforms (Eclipse Mars, Eclipse Neon) Imixs-BPMN is still are available.
Why do employees in companies repeatedly use Microsoft Excel or PowerPoint to manage business data and tasks?
Companies today have a variety of business applications in use. Some for legacy reasons, some for strategic reasons and some just because they are hip and make fun. And most of the times, these applications are not enough to cover all aspects of daily working life. A lot of tasks and data that need to be processed on a daily basis are often managed with EXCEL and POWERPOINT. This is not wrong in general and provides employees a way to prepare business figures in tables or display them clearly in a presentation. But often these applications are also abused for a kind of data management. But EXCEL is no database and POWERPOINT is not a messaging tool. The problem is, that these tools often collect data that is needed to implement certain business processes and for which there is no suitable application available. In a short time, these solutions become indispensable and are passed down from generation to generation.
Continue reading “You Shouldn’t Manage Your Business Processes With Excel”
With the next minor release 4.3. of Imixs-Workflow, which will be released shortly, the Open Source Workflow Engine supports a new Rest API. The new API is easier to apply. The result data output is mashed and now always the same structure. This makes client implementations cleaner and easier to implement. At the same time, all functions of the human-centric workflow engine can be used via one common Rest API.
The old API is also still supported by the Imixs-Workflow engine. The old API can be used with the version prafix /v40/ in the request path.
Learn more about human-centric workflow here.
Imixs-Cloud is a conceptual infrastructure project, describing a way to create a server environment for business applications based on Docker Swarm. In the current version we added a new concept about how to manage all the configuration in a private git repository. This makes it more easy to setup the environment form the scratch.