Expand my Community achievements bar.

How to synchronize multiples environement with cmContentCreator?

Avatar

Level 1

Hi,

I have a question regarding  Solution Accelelator - Correspondence Management.

I would like to know if there exists a way to “promote” from one environment to another one all the works done into Adobe Solution Accelerators Content Creator?

Situation: Business users work into a "Test" environment and they must promote their work into "Prod" environement.

I have tried to create by using LiveCycle Workbench an LCA having my “fragment” created in ContentCreator, but "categories" was not imported.  Do we have to redo the entire job done in ContentCreator? There exist a way to automatism the process?

Thanks in advance,

Marieve

1 Reply

Avatar

Former Community Member

Marieve,

While you can effectively create an LCA to export from one LC server and import into another, there is an unfortunate bug in LC ES Update 1 (8.2.1) that prevents any custom properties set on any assets from being exported in the LCA. This means that when you import the LCA on the other server, you lose all of the "cm" namespace properties that were set by the CGRImport tool, as well as all of the tags set in Content Creator (as you have already determined with your testing).

The CGRImport tool supports the use of .tags files. If a .tags file is found with the same name as some other file being imported, CGRImport will look in that file for any tags to set after importing the asset from the local drive. You can see an example if you look inside the //sa/building_blocks/cgr_1_0/dist/repository/samples/CustomCommunications/share/frag folder. There are XDPs in there that have sibling .tags files. Furthermore, CGRImport will properly set other custom properties (still in the "cm" namespace) that are used by Content Creator to differentiate one XDP from another (e.g. to know if it's a textual paragraph fragment vs an image fragment).

I would recommend you drag & drop what you want from the Test LC server into a local folder, create .tags files accordingly, then use CGRImport to import that folder/file structure into the Prod LC server.

Stefan

Adobe Systems