Publish / Export / Commit

When you have finished mapping your source applications to ACES (using the Map Applications screen), and checked for overlaps, you are ready to create ACES xml files.

The usual steps are: (These are performed at the Brand level using Process > Publish ACES Applications)

1. Publish

2. Export (For net changes, you must do export before commit).

3. Commit

If there is a problem with the exported file and you want to make changes to the applications, Rollback instead of Commit. You can still do Export after Commit, but only for full file and not for net changes.

Hint

It may be helpful to think of Commit as meaning “accept”. A good rule of thumb, then, is to Commit only when the file has been accepted by your receivers.

For this reason, it may be easiest to wait to Commit until the next time you want to Publish. Then the order becomes: Commit (last round’s file), Publish (new information), Export.

Recording Submissions is optional. It gives you a way to track who has received the file.