Best practices for source control / release process for Adobe Campaign projects

[#1]

Hi,

I'm looking for best practices for versioning Adobe Campaign files (schemas, forms, templates, etc.) and setting up a release process with the ability to build / deploy new releases.

All functionality of Campaign seems to be available via its SOAP API, so it seems to be possible to build something that exports/imports various sources. Browsing the internet I found tools that are built on the SOAP API.

What is Adobe's recommendation? What do the community recommend?

Thanks!

[#2 · Accepted solution]

Hello,

You can setup a process where you export and import packages (containing schemas, forms, etc.) using Campaign's SOAP API.

From xtk:builder you can access the InstallPackage method that you can use to import packages.

From xtk:specFile you can access the generate and generateDoc methods that you can use to export packages.

You can apply those files to your source control system.

Hope this helps,

Florent.

[#3]

florentlb wrote...

Hello,

You can setup a process where you export and import packages (containing schemas, forms, etc.) using Campaign's SOAP API.

From xtk:builder you can access the InstallPackage method that you can use to import packages.

From xtk:specFile you can access the generate and generateDoc methods that you can use to export packages.

You can apply those files to your source control system.

Hope this helps,

Florent.

Thank you for your reply! I'll look into the SOAP option. Fyi, I found similar solutions that utilize the SOAP API, for example https://github.com/cumpstey/campaign-sync