Why The Application-Centric Design in Joget Workflow v3?
Our previous blog post, Sneak Preview of Joget Workflow v3, has gotten a lot of attention from Joget Workflow adopters as well as industry watchers in the BPM space. Many people are surprised with the application-centric approach that we are pursuing, but at the same time, the comments and feedbacks we have received have been very encouraging!
Why The Application-Centric Design?
We have learnt a lot in the 19 months since the public release of v1.0. Based on observing numerous implementations of Joget Workflow, we were able to gather a couple of interesting facts:
Simplicity Redefined
You can still choose to develop processes with Joget Workflow v3 and integrate them into your preferred web frontend such as WordPress, Drupal, Liferay and SharePoint.
But, if you prefer to stay with minimal integration points, the new Userview Builder will enable you to create a web frontend that includes the following features:
Why The Application-Centric Design?
We have learnt a lot in the 19 months since the public release of v1.0. Based on observing numerous implementations of Joget Workflow, we were able to gather a couple of interesting facts:
- Process automation is just part of the implementation use case. Most of the time, what a customer actually needs ultimately, is an application.
- Process automation is just part of the implementation use case. A customer also needs reports in tabular format and the ability to easily export the records.
Simplicity Redefined
You can still choose to develop processes with Joget Workflow v3 and integrate them into your preferred web frontend such as WordPress, Drupal, Liferay and SharePoint.
But, if you prefer to stay with minimal integration points, the new Userview Builder will enable you to create a web frontend that includes the following features:
- Link to form
- Link to HTML page
- Link to URL
- Link to tabular report (list), with export feature
- Link to process
Comments
Post a Comment