Persisting Adobe Experience Manager 6.4 JCR data using a Custom Form Action

You can create an Adobe Experience Manager 6.4 application that persists application data in the Java Content Repository (JCR). When storing data within the JCR, each record can be saved as a separate node. A node can contain properties that store data values. To store data in Nodes, you can use the Node API.

For example, assume that your Experience Manager application to store your organization’s employee data. Each node can represent a different employee. In this article, a basic form is built by using Experience Manager Form components.

The following illustration shows employee nodes. Each time the form is submitted, a new node is created.

Each node contains properties that store employee details, such as the name value.

The following video shows this use case. 

To read this development artilce, click https://helpx.adobe.com/experience-manager/using/persisting-experience-manager-64.html. 

Join the Experience League

To become an Experience Business, you need more than just great tools and online help. You need a partner. Experience League is a new enablement program with guided learning to help you get the most out of Adobe Experience Cloud. With training materials, one-to-one expert support, and a thriving community of fellow professionals, Experience League is a comprehensive program designed to help you become your best.

Join the Adobe Experience League by clicking this banner.

I (Scott Macdonald) am a Senior Experience League Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more AEM or other end to end articles like this, then leave a comment and let me know what content you would like to see.

Linked In: http://www.linkedin.com/in/scottmacdonald2010

YouTube: Subscribe to the AEM Community Channel.