This past summer Adobe released the LiveCycle ES Update 1 release. This include LiveCycle Content Services ES, a fully integrated set of content services that enables organizations to "manage content in a lower-cost, extensible way for cross-company and cross-organizational processes". LiveCycle Rights Management ES is a core part of this offering, and allows organizations to include content protection as a part of these cross-organizational processes.
Each "space" within Content Services can be seen as a folder to hold sub-spaces or content. These spaces can be associated with business rules and security — including various access control rights as defined by LiveCycle Rights Management ES.
It’s easy for business users to interact with these spaces because content can be added in several different ways; for example: using the Web UI, FTP, CIFS, or WebDAV. Adding security is a breeze because the act of adding content can be associated with an automatic trigger that can protect the content with Rights Management. For example, an administrator can create a trigger to associate the "Confidential" policy for general documents, or the "Mergers & Acquisitions" policy for content being stored for the M&A team.
In today’s blog entry we show off a simple example of how:
- An administrator can create a rule to automatically protect all content with a specific predefined policy.
- An end user can upload a document to be automatically protected.
- A recipient can open a protected document within the Content Services repository.
Click on the following screenshot of LiveCycle Content Services for a brief tour of this functionality:
Guest Contributor: Neerav Aggarwal
Questions or feedback on this entry? Contact us at RMFeedback@adobe.com
By Jonathan Herbach
September 30, 2008