The idea is to test the whole process on a test environment and when you are happy, download .zip file of app and upload it to Live. We have multiple apps where reuse models are used , hence same models exists in two different app. Hence once we import both app into productive system , models with same key is created twice . Any idea how we can prevent to import duplicates even if it exists in two APPs.
I would like to know if there is any configuration that can be done in Productive system to prevent creation of duplicates but allow overwriting of same model.
The same is the case with decision tables and formsā¦ it creates duplicates if the same model exists in two app.
No, thatās currently not supported with the Flowable Modeler. Youād need a check on the key on import and throw an exception (but that would need code changes).
I know that there is a procedure how to request such a feature to become a standard in Flowable. Could you tell us how to subject the development request?
Basically, duplicate keys should not be allowed and it should ask the user to skip or overwrite the respective model, form or decision table.
We add new features to the open source project when thereās enough community demand. As this hasnāt been implemented yet, it means it hasnāt been crucial for most users. Furthermore: the open source UI applications come with no support.
As this is an open-source forum, we try very hard not to mix this with our enterprise products and support. The only thing I want to say here is that we do have commercial products where customers can influence the roadmap and/or get support with SLAās.
the expression āwe are frustratedā was actually proposed by Flowable Issue editor as standard text, so I thought to just use it. No bad intentionsā¦