LiveCycle used to have a set value component which would allow you set an XML element value.
Based on this value, when the form is populated with the XML you can hide/disable certain fields or panels of the form.
In AEM Forms OSGI- we will have to write a custom OSGi bundle to set value in the XML. The bundle is provided as part of this tutorial.
We use Process Step in AEM workflow. We associate the "Set Value of Element in XML" OSGi bundle with this process step.
We need to pass two arguments to the set value bundle. The first argument is the XPath of the XML element whose value needs to be set. The second argument is the value that needs to be set.
For example, in the above screenshot, we are setting the value of the
In our example, we have a simple Time Off Request Form. The initiator of this form fills in his/her name and the time off dates. On submission, this form goes to "admin" for review. When admin opens the form, fields on the first panel are disabled. This because we have set the value of the initial step element in the XML to "N".
Based on the initial step fields value we show the second panel where the "admin" can approve or reject the request
Please take a look at the rules set against "Time Off Requested by".
To deploy the assets on your local system
Download and extract the content of the zip file
Point your browser to Felix console
Deploy the SetValueApp.core-1.0-SNAPSHOT.jar bundle and start the bundle
Point your browser to package manager
Import and install the setValueWorkflow.zip. This has the sample workflow model
Point your browser to Forms and Documents
Click Create | File Upload
Upload the TimeOfRequestForm.zip
Open the form
Fill in the 3 fields and submit
login as 'admin" in to
Go to "Inbox"
Open the "Review Time Off Request" form
notice the fields in the first panel are disabled
also, notice the panel for approving or declining the request
You can enable debug logging by enabling logger for
by pointing your browser to http://localhost:4502/system/console/slinglog
Make sure the Data File path in the Adaptive Form's submission options is set to "Data.xml". This is because the process step looks for a file called Data.xml under the payload folder