<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>idea Re: Version Control in Adobe campaign in Adobe Campaign Classic Ideas</title>
    <link>https://experienceleaguecommunities.adobe.com/t5/adobe-campaign-classic-ideas/version-control-in-adobe-campaign/idc-p/331829#M5</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;-Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 11 Sep 2019 19:47:36 GMT</pubDate>
    <dc:creator>Jonathon_wodnicki</dc:creator>
    <dc:date>2019-09-11T19:47:36Z</dc:date>
    <item>
      <title>Version Control in Adobe campaign</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-campaign-classic-ideas/version-control-in-adobe-campaign/idi-p/331825</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I&amp;nbsp; think we should have version control for Transnational&amp;nbsp; Messaging templates .Because when X creates&amp;nbsp; 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&amp;nbsp; in the changed document.So its better we have version control system in adobe campaign.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Apr 2019 12:14:17 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-campaign-classic-ideas/version-control-in-adobe-campaign/idi-p/331825</guid>
      <dc:creator>anandm94792738</dc:creator>
      <dc:date>2019-04-02T12:14:17Z</dc:date>
    </item>
    <item>
      <title>Re: Version Control in Adobe campaign</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-campaign-classic-ideas/version-control-in-adobe-campaign/idc-p/331826#M2</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I agree, although I would also like to extend the scope to other (all?) entities. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Preferably with functionality to do rollbacks, see diffs between versions etc, as would be expected in a version control system.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Apr 2019 12:31:32 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-campaign-classic-ideas/version-control-in-adobe-campaign/idc-p/331826#M2</guid>
      <dc:creator>jonasn92134656</dc:creator>
      <dc:date>2019-04-04T12:31:32Z</dc:date>
    </item>
    <item>
      <title>Re: Version Control in Adobe campaign</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-campaign-classic-ideas/version-control-in-adobe-campaign/idc-p/331827#M3</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Audit trail will give you capability to track modifications: &lt;A href="https://docs.campaign.adobe.com/doc/AC/en/PRO_Production_procedures_Audit_trail.html" title="https://docs.campaign.adobe.com/doc/AC/en/PRO_Production_procedures_Audit_trail.html"&gt;Audit trail&lt;/A&gt; &lt;/P&gt;&lt;P&gt;Next step is to adding a "previous state" button. This is not planned yet.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 May 2019 14:55:50 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-campaign-classic-ideas/version-control-in-adobe-campaign/idc-p/331827#M3</guid>
      <dc:creator>Perrininho</dc:creator>
      <dc:date>2019-05-29T14:55:50Z</dc:date>
    </item>
    <item>
      <title>Re: Version Control in Adobe campaign</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-campaign-classic-ideas/version-control-in-adobe-campaign/idc-p/331828#M4</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All ACC objects are XML so they can be backed up as text files&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;More info on &lt;A href="https://blog.floriancourgey.com/2019/06/version-control-adobe-campaign" title="https://blog.floriancourgey.com/2019/06/version-control-adobe-campaign"&gt;this blog post&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Jun 2019 09:26:01 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-campaign-classic-ideas/version-control-in-adobe-campaign/idc-p/331828#M4</guid>
      <dc:creator>Florian_Courgey</dc:creator>
      <dc:date>2019-06-27T09:26:01Z</dc:date>
    </item>
    <item>
      <title>Re: Version Control in Adobe campaign</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-campaign-classic-ideas/version-control-in-adobe-campaign/idc-p/331829#M5</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;-Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Sep 2019 19:47:36 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-campaign-classic-ideas/version-control-in-adobe-campaign/idc-p/331829#M5</guid>
      <dc:creator>Jonathon_wodnicki</dc:creator>
      <dc:date>2019-09-11T19:47:36Z</dc:date>
    </item>
    <item>
      <title>Re: Version Control in Adobe campaign - Status changed to: Declined</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-campaign-classic-ideas/version-control-in-adobe-campaign/idc-p/395778#M185</link>
      <description>&lt;P&gt;&lt;SPAN&gt;This is not in our product roadmap.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 03 Feb 2021 10:46:00 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-campaign-classic-ideas/version-control-in-adobe-campaign/idc-p/395778#M185</guid>
      <dc:creator>Sukrity_Wadhwa</dc:creator>
      <dc:date>2021-02-03T10:46:00Z</dc:date>
    </item>
  </channel>
</rss>

