Version Control in Adobe campaign

[#1]

Hi guys,

I  think we should have version control for Transnational  Messaging templates .Because when X creates  a template and Y working on the same .Y makes some changes which X is not aware .If something goes wrong during production stages we cant roll back or have name of person or version number  in the changed document.So its better we have version control system in adobe campaign.

[#2]

I agree, although I would also like to extend the scope to other (all?) entities.

Preferably with functionality to do rollbacks, see diffs between versions etc, as would be expected in a version control system.

[#3]

Hello,

Audit trail will give you capability to track modifications: Audit trail

Next step is to adding a "previous state" button. This is not planned yet.

[#4]

Hi,

We set up a very simple workflow to backup all of our data schemas on a daily basis. It can be duplicated for workflows, JSSPs, forms, etc.

Just create a data package definition with the objects you want to back up, then in a workflow generate this package and save it as an XML.

All ACC objects are XML so they can be backed up as text files

More info on this blog post

[#5]

Hi,

I've done a full, secure (no execCommand) Git implementation in Campaign, where users can commit objects and check out old versions, ala Eric's 'previous state' button, within the console UI. Solves workflow undo, etc.

Also, every deployment should get a variant of what Florian mentioned, daily snapshots of non-ootb objects - this is part of my team's install checklist.

Thanks,

-Jon

[#6]

This is not in our product roadmap.