After our announcement… it seems now to be a good time to give a brief introduction to Flowable. There are just two key takeaways: Flowable is Open Source, and Flowable is an awesome Business Process Management engine.

What does that mean to you? Let’s unwrap some of that and dig in more deeply, as they say.

Open Source, so what?

You can…

just download and start using it
look inside at all the codes
make whatever changes and extensions you need
contribute code back to the project (if you’re progressive enough…)
use it wherever you want
… and we may never need to be aware of each other.

There’s a healthy community of users and people contributing fixes and enhancements, all curated by the core engineers. This community can help you by answering questions on the forums, whether it’s low-level technical detail or just how to get started. There are many varieties of open source projects, and the only way you’ll find out which are the best is by experiencing their community.

And who wants to learn more about the BPM engine? We are looking forward to give u more details… coming soon!

What if more help needed? Support subscriptions are available from now on. Please check Flowable Core

We’ll be talking much more about the technology and business benefits, so remember to check back here to find out more… do not miss to follow us!

Karin Deichert
Head of Marketing
Karin.deichert@edorasware.com

“Digitalization” – probably one of the greatest forces transforming society today. It radically changes our habits, and it’s much more than just automation and making analog things digital. It affects how people, technology and things interact and relate to each other. So digitalization is on many companies’ plate. It is challenging and it is not always properly managed: many companies find digital transformation a significant challenge. Nevertheless, with some minor precautions there will be fewer stumbling blocks on the line.

A clear vision

Opportunities are massive: digitalization brings enhanced levels of service, more automation, usage of artificial intelligence, reduced environmental impact, more efficient processes in the industrial and service sectors: it simplifies everyday life. Many companies concerned with digital transformation are sometimes not looking at the big picture: every company must create a vision that shows where it should go. It must be clear why the digital transformation of the company is actually important. Employees must be involved and taken into this voyage of business transformation from the beginning. A strong vision is key, so apply one.

Cultural and organizational changes

Digitalization brings many challenges. You need knowledge and close collaboration between various actors inside and outside your company. If you believe that digital transformation can be a little side project in your company, think again. A cultural transformation has to take place.

The correct priorities must be set: the right structure is often lacking in many areas. It often makes little sense to pick the “digital” part out of every area of the company to form a dedicated project. One of the most important considerations is the appointment of the right people to the right positions. Compromises occur all too often. Employees need a clear attitude, and companies need to consider budgeting more for appropriate employee training. Training in the professional fields of respective employees is important, but there is often a lack of additional training on topics such as digital transformation.

A flexible platform

Last but not least, it is also important that companies invest in the right tools for their employees. It might be difficult to continue to work with your current legacy software platform because it may not have the capacity to grow with the company and with the needs of today. Consider introducing a modern work and collaboration management solution is certainly a good starting point. Complexity needs to be orchestrated and setting the right technological foundation is crucial.

All of this is both challenging and exciting. We are heading rapidly to a highly connected and digital world. Get in touch with us. We are a strong partner to support you in your digitalization journey.

Marc Bühler
Marketing Manager edorasware
marc.buehler@edorasware.com

Testing business processes can take a lot of time and resources. To test all the possible variations and different scenarios in a complex business process manually, can be quite challenging and time-consuming. This is further evident when we take into account that business process management processes are usually long running. This means that finding a bug by utilizing an iterative process can take several days as there may be thousands of process instances running on the potentially bug-affected process. Therefore, there is a need for a sophisticated testing framework for BPM platforms. And it is evident that automation is crucial. There are a few different ways to implement automated testing. Let us have a closer look at the key methods.

Unit testing with JUnit

JUnit is an open source unit testing framework. It is ready to use, well-known to Java developers and it is easy to use as almost everything can be expressed in Java code. This is the best tool for low level testing of technical aspects, such as testing services and REST APIs.

However, it has some disadvantages, such as when it comes to more business-oriented end-to-end testing. Testing in this instance is usually performed by business and test analysts, who may not be familiar with Java. Also, writing unit tests can be very time consuming. Last but not least, you need to build up a special infrastructure, because JUnit cannot be run directly from the workflow engine.

Using process modeling to define test procedures

A very interesting option is to use business process modeling and notation (BPMN) for testing. Using BPMN to write the test cases can bring about many benefits. It allows process modelers, such as test and business analysts, to design the tests in their usual manner on a user-friendly level.

Tests are event based and tasks can be tested step by step. Different input variables can be used and assertions tested. To achieve this though, the pallet of workflow nodes needs to be extended. New nodes need to be specifically prepared for testing. This makes the testing more user friendly and flexible. Process events (such as deploy, start, complete) can be designed manually, while evaluation is part of the process test definition.

Workflow nodes for testing the nodes available in the library (palette)

Process simulation

With these two methods, the possibilities are huge. But what about testing something in an environment that comes close to the real world?

Simulations are the answer. For simulations, different virtualised situations can be applied and tested. The goal here is to simulate a variety of states in a fast and efficient manner. Imagine you want to test a car and you would like to run the car to the end of a pre-defined route but you also want to see its performance with different weather conditions. With virtualisation, the same flows can be retested under different circumstances very quickly and easily.

If your workflow management platform runs on the Activiti engine, then Activiti-Crystalball could be a good solution to implement this virtualisation for testing. With the appropriate tooling, it is easy to reuse data, start simulations and then to replay the workflow behaviour from the set-up history.

Conclusion

For developers, unit testing is a natural thing to do. Concluding unit tests is always useful, especially with the focus on testing at lower rather technical levels. Process testing is the friendlier option for process modelers too. In order to test a process efficiently under different complex circumstances, concluding simulations is a cost-effective and time-saving method to do so.

Last but not least, the magic lies in finding the right mix between the mentioned options as all the different options follow their own specific purpose, but finding the right combination means they can complement each other to achieve more effective results.

Martin Grofčík
Product Developer
martin.grofcik@edorasware.com

In our last blog we gave you some basic advice to help you to decide whether decision management notation (DMN) is right for you. Now if you have come to the conclusion to use the DMN standard, how would you typically start such a project and what do you need to consider?

The first step is to gain some know-how. Take an in-depth look at decision management. DMN is a notation, built from years of practice. It is a new standard and it’s developing. If you understand what it does, then you’ll know better how to use it and how to improve it based on your own practical experience.

Any modelling approach, requires a certain rigour, otherwise you will waste time and not use it long term. Pick a vendor or consultant with a demonstrated track record of implementing process and decision management platforms and who has a solid implementation project methodology. It is important to understand the distinction between business logic and decisions. Once that concept is clear, using a DMN tool that not only allows you to model but to deploy the model as an operational service across your entire organisation will allow you to make huge progress.

The analysts and modelers who create the decision models must follow an in-depth training programme to learn the principles of decision modelling and to become experts in the tools chosen. The developers of decision modelling tools must focus on the relationships and elements within the decision models and learn as much of the DMN specification as necessary to ensure the desired level of conformance with the specification and its proper implementation in their tools.

In general, start small, keep it simple, demonstrate success in a project of a small scope that potentially has a real impact on the business, and keep iterating in an expanding manner. You should understand what level of maturity you wish to reach and frequently measure your progress.

As with any project, you need to analyse the business requirements. Use a simple top-down decomposition of your business rules, involving a few days’ participation from your process owners and subject-matter experts, led by a business analyst. This investment will result in decision diagrams showing the structure of the decision-making domain and identifying all the information required for it: the data that must be collected by the process and the organisational business knowledge – business rules, analytic models and calculations – that must be applied to the data to make the necessary decisions.

Decision Model by Object Modelling Group (OMG)

Soon it will be common practice for you to specify your complete decision model in DMN, working top-down, and then deploying it directly to the execution architecture as a decision service to be consumed by your business process management platform. I hope we have given you some insights into DMN. Feel free to ask any questions or add any comments below. We are happy to discuss this with you or become your partner in finding the right way to profit from this useful new standard.

Marc Bühler
Marketing Manager edorasware
marc.buehler@edorasware.com

DMN is becoming increasingly popular. Many business processes are about approvals – for loans, expenses, travel, documents, and so on. Business process modeling notation (BPMN) is useful for defining the steps of such processes, but it doesn’t explain why things get approved or rejected. This is where DMN comes in, as it standardizes the composition of decision-tree diagrams, automating the underlying logic as decision tables and other user-friendly tabular expressions. But is it the right solution for your company?

So DMN allows us to represent decision logic in a way that’s not only easy to understand, but also able to be precisely replicated. Choosing to use DMN depends on whether:

your business processes require rule-based applications that are subject to regularly changing business rules;
your affected business domain and the business rules from which decisions are derived are suitably complex; and
you can see the potential for scaling your rules in a distinct reusable manner.

DMN is suitable for use in all industries and by all types of organisation, especially where decision-making must be accurate and compliant with legislation. Government regulations, including financial, environmental and labour regulations, have risk implications that must be taken seriously. These operational decisions can have major impacts on your operations, so even small enhancements can have considerable effects on your company’s performance and risk profile.

DMN is a great auditing tool, too, as it provides a complete and detailed audit trail of decisions and how they were reached. Plus, if you’re using BPMN, DMN is an obvious complementary choice for modeling and executing business rules, and properly maintaining them within an adaptive and agile development approach.

All of this makes DMN a convenient way of navigating today’s complex business environment, particularly for service-oriented industries such as financial services, insurance, logistics, government, legal and healthcare.

Have we awoken your interest in DMN? If so, please read our next blog, which explains how to get started and what to consider when setting up a DMN project.

Marc Bühler
Marketing Manager edorasware
marc.buehler@edorasware.com

CTA Area

Go back to top