You have described a document management solution. While LiveCycle has connectors to document and content management systems, it does not manage documents natively.
The LiveCycle repository is not intended for storing application content. It is for storing form-related assets used as input to applications, primarily. Files of type .pdf, .xdp, .xsd, .xml and image formats for example. The Foundation operation readApplicationAsset is for getting assets to be consumed by an application.
Once a .pdf or .xdp is rendered and delivered to a Reader/Acrobat client and filled, the completed or partially-completed PDF could then be saved locally, submitted to a non-LiveCycle application (such as a content management system) or returned to LiveCycle application for further processing (whether it is saving the form to a network folder, a content management system or a home-grown document management system).
I didnt get the whole idea.
You mean to say , it is not possible to save the partially filled form in the livecycle repository. And we have to use some other document management system to do the same.
Is my understanding right?
Yes, you should not persist the partially saved form in the LiveCycle repository. In fact, saving the partially completed form to the repository would require a hack. Additionally, there is no incremental value in having the form in the repository versus another storage mechanism.