@Greg_Svitak Hey
We originally did not go with orbeon because it was a “beast of a software” to use and manage.
formio was providing a fairly lightweight, new generation of standards (node, json, JS, Angular, React, etc), and if you needed features that are paid, the pricing model was just way to high. (It also has a nice fit with Camunda’s Angular based Tasklist).
Also many of the paid features of orbeon are just standard OSS / expected features in formio: embedding, SQL, web hooks, services and actions, Internationalization, Signatures, Permissions, etc.
Overall orbeon “felt” like a much more closed system that places you in a smaller ecosystem. With formio we have the entire Node, Angular, and React communities to pull from.
Our OSS release as a symfony bundle should be out in coming days.
There is also this example that was posted above: Dockerized example with Form.io form builder and Camunda.
Edit: In Terms of contributions I had imagined that there was a few different levels depending on your use cases:
-
someone building a web app to work on the Camunda server, and building a modification to the Tasklist so this functionality is supported out of the box (this whole task is on our todo as a R&D gov paid project).
-
Build out other middleware implementations: would be used depending on the application you are using.
-
Build additional formio components that are useful to Camunda space, but can also be used by rest of formio community.