Implement testing and validation processes to ensure only authorised changes are promoted to Higher Environments




In an Adobe Target implementation, how to ensure only authorized changes are promoted to production (Development, Test, and Production Environments)?

Like someone designated for this task will look at all changes and approve some and disapprove others and only approved changes move forward.

My understanding is that if we integrate SVN (source code system), only bug free code could be checked in and only checked in code could be moved up in the higher environments.

Before checking in, we perform correct amount of testing.

Is this view correct, or any other option is available, either out of box or through any tool?

The other point is that typically out of all AMC products, only AEM has Java code along with JS, CSS, etc, but all other AMC products have just JS or just configurations.

If it is JS, it could be stored in a source code control system, like SVN, how to version configurations?

Also, how to move configurations to higher environments automatically, given that they are not stored in SVN?

In the absence of automatic deployments options, do we have to manually configure?

Appreciate your support.



View Entire Topic




In Adobe Target users have different roles. Only users with Approver role can "activate" an activity. You can find more about roles here: Users.

Besides that Adobe Target has the concept of Hosts and Environments. You can choose to associate hosts with environments and you can choose to which environments you want to serve saved or approved activities. You can find more about hosts and environments here: Hosts.

If you want more granular control around users, hosts or environments you could try: Enterprise User Permissions

As you can see we have quite a few options that allows you to create a workflow in which saved/draft activities can be reviewed in QA or Staging environments and once those are approved promote them to production.