At the end of last week, AEM 6.0 was finally released. As both a LiveCycle and AEM developer this is very interesting news for me, since LiveCycle is being merged into the AEM product suite, under AEM Forms. This also includes Adaptive Forms – forms with a responsive design and a host of other cool features.
Here are some links where you can find more information on AEM 6.0:
AEM 6.0 Release Notes
AEM 6.0 Documentation
Sightly – The New AEM 6 Templating Language
Introduction to AEM Forms
AEM Forms Help
AEM Forms Forums
There’s a lot more information out there, but this is some good reading to get started.
Many of the clients I work with use Scrum to manage projects. I find it a great way to deal with complex projects that have ever changing requirements, as the case tends to be in large enterprises.
So in an effort to further improve my skills in this area, I recently became a Certified Scrum Master. Even if you are not planning on perusing the role of Scrum Master, the course still provides you with some great skills to use in a Scrum environment. Also, by becoming certified you get a two year membership to the Scrum Alliance which include access to job postings, user groups, discounts on Scrum gatherings, access to a wealth of information, and more.
If you’re interested in becoming more active with Scrum, be it in the Scum community or in the workplace, then this is definitely worth looking into.
While creating some AEM Forms (LiveCycle) demos for some clients, it became very apparent that they wanted to see forms in action on mobiles and tablets. One of the easiest ways I have found to do this is by using Charles.
By ensuring your demo computer and mobile/tablet are on the same network, and manually configuring the proxy settings on your device, you can route all traffic via Charles and force your device to pass through your computer when browsing. So if you have an HTML form on your computer at the URL http://localhost:8080/lc/content/xfaforms/profiles/default.html?contentRoot=repository%3A%2F%2F%2FApplications%2FFormDemo%2F1.0%2Fforms&template=SampleForm.xdp&dataRef=http://localhost:8080/lc/content/dam/lcapplications/temp_archive_storage/tempArchive_4895793046486&dataRef=4895793046486 (as is generated in the Forms Manager preview), you can open this form on your device by substituting localhost with the IP address of your computer – you now can test and demo forms on a mobile device!
I’ve not tested other AEM functionality in this way yet, but I don’t see why it would not work the same way.
For official instructions on using Charles in this way (for an iPhone), check out Using Charles From an iPhone.
I was trying to use Forms Manager in my local ES4 installation for the first time today, and even though I had installed the module when installing AEM Forms (previously known as LiveCycle) the Forms Manager option was not appearing for me in the main menu at http://localhost:8080/lc
The strange thing about this is that if I navigated directly to the actual Forms Manager URL at http://localhost:8080/lc/fm, Forms Manager was running. However none of my LiveCycle applications were listed, and when trying to syncronise my applications with Forms Manager as described in Getting forms in Forms Manager I was not allowed due to permissions errors, even though I was logged in as the Super Administrator. When I updated my own user with ALL roles in LiveCycle, I could not even access Forms Manager at all.
I asked a colleague of mine Darren about this (who runs his own LiveCycle blog The LiveCycle survival kit), and he suggested I try and run Configuration Manager again. When Configuration Manager reached the step of “LiveCycle ES4 Component Deployment Validation”, it passed validation but not without some warnings that some DSCs were not running. One of these was “adobe-formsmanager-dsc.jar is deployed but is not currently running”.
I opened Workbench, and sure enough the FormsManager DSC was in a stopped state. A simple right-click on the component to open the menu, then clicking “Start Component” started the component. After re-running the “LiveCycle ES4 Component Deployment Validation” step in Configuration Manager again, this warning did not appear. After Configuration Manager finished, I opened the Adobe LiveCycle ES4 Modules page again at http://localhost:8080/lc and sure enough, Forms Manager was listed and working correctly this time.
Last November I sat the Adobe Certified Expert LiveCycle ES4 Designer beta exam. After a couple of months waiting for the results to be compiled and the final exams to be created from the beta questions, I finally received the results this week…
Happily, I passed! :-)
Next step – the Adobe Certified Expert LiveCycle ES4 Server exam…