A source of confusion I’ve come across when explaining the new world of ADEP to those familiar with the LiveCycle days is what has happened to Content Services.  Content Services was essentially the repository for storing files and anything else you needed persisting in your application.  It was built around the Open Source CMS by Alfresco and was used on almost all of the projects I worked on.  In the move to ADEP it’s the one module the fate of which I wasn’t 100% sure of.

Server

On the one hand ADEP now brought in the exciting world of a Java Content Repository (JCR) in the form of CRX with its RESTful API and many other features but on the other there didn’t seem to be any clear way of utilising this fancy new repository from within processes designed in ADEP Workbench.  Sure, you could use the API, but that seemed a little too “manual” in the world of drag and drop process design.  Then I read a blog post on the official ADEP blog about a new pre-release DSC which will allow for easy access to Content Repository and it all started making sense.  Why this wasn’t released with the rest of ADEP I’m not sure (after all, this DSC will deprecate the content services DSC) but it will certainly make using that shiny new CRX repository a whole lot easier for process designers who don’t fancy getting their hands dirty.

The DSC should be available on the 14th October via Adobe’s Pre-Release programme and I’ll be posting an update when it’s out and I’ve had a chance to play with it.

Edit: Thanks to Jayan for pointing out an error in my original post.  The new DSC will not replace the existing content services DSC.  The content services DSC will just be deprecated.