1 person found this helpful
AEM Forms 6.3 allows you to have forms-centric workflows with adaptive forms. You could build a form review / approval workflow that publishes using these workflows. It also keeps the whole process on the Author instance. However, I am not sure if Forms publishing works the same way as Sites publishing in workflows - this would be for Adobe to confirm.
I would avoid the AEM Forms JEE workflows for form/publish approvals as it is not really what it is built for. You would need to create a new workflow per form as the CRX asset (adaptive form) has to be specified at workflow design time.
Thanks fro the reply Darren,
I will take a look at the video. Adding more description to initial question too..
I wasn't able to edit the initial question, so adding it here..
Just to make sure I am looking for the review process that happens internally within author.
For example: Dept A submits a form (With few fields etc..).
Dept B reviews it. If there are changes to be made, they assign it back to Dept A.
Dept A makes changes and submits it back.
Dept B moves this to Dept C.
At each step a version of form is saved and email notifications are sent to whoever is assigned. While all this happens in Author, once the review is complete, the final version can be published to the publishers for users to download and apply for whatever the form is for.
Hi snbem - It sounds like you are after the Review process: AEM 6.2 Forms Help | Creating and managing reviews for assets in forms
Its not an official workflow as such so it doesnt directly route the form around but is more an informal review process where everyone can collaborate and provide feedback for the forms authors.
Note that there is not currently any way to lock a form while editing (like sites pages) and multiple authors can edit the same form at the same time, potentially ending up with undesired form contents. Just something you should be aware of.
I haven't tried to create the type of workflow you suggest using OSGi Workflows. I would be interested to hear from Adobe if this type of thing is actually possible because its a common use case we hear.
Thanks for the link, I sort of tried that while researching but the link has more details. Despite of that as you mentioned this seems more informal or provides lesser options than what I am seeking for. I am trying the OSGi workflow (POC level) but it seems with that approach also I need to find a way to save versions everytime the form is moved ahead in the flow.