nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Will Decision Table compatabile with Activiti Community?

abhitorem

Hi,

We are currently using Spring boot Application with Activiti BPM, Due to companies policies, we are being pushed from Activiti Enterprise to Activiti Community Version. Here comes the main issue with the In-flight stuff that needs to be migrated to the Community. We are trying to find the possible ways we may face issues in the process of migration.

Currently(In Enterprise) we are using a decision table in our workflow, my question is will the Decision Table would be compatible in community or will there be alternative like any Rule Engine or can pass the conditions through the Java Methods. #Spring boot #Activiti BPM

Find more posts tagged with

Alfresco Process Services

Comments

salaboy

Hi there,

In general, for migrations, you should try to keep both versions of the process engine alive until you finish in-flight processes. You might find that trying to migrate in-flight processes is a huge investment and might not be worth it.

Regarding decisions, are you targeting Activiti 6 Community? If so, you can see here: Activiti/modules at 6.x · Activiti/Activiti · GitHub that activiti-dmn-* is there already.

abhitorem

Thanks,

I would surely take your suggestion, I am not familiar how both the process engine can be kept alive keeping into consideration for New/Inflight Process, I mean how would you process Pointing to new/Inflight process. could you elaborate.

Thanks

salaboy

That's part of your application logic. Most of the time you need to analyze if in flight processes are required to keep running based on the previous process definitions for compliance. There are some cases where process definitions are created based on legal regulations, so you can just not change the process definition for processes that were already started.

Your application will need to, based on who is interacting with the process, decide which version to use.

The most common rule to pick process versions is, new process instances go to the new process definition, but in-flight processes keep running with the old one. Again, it is a very domain specific decision.