There is often a requirement to perform an action or group of actions before (and/or after) publishing from a data pool. For example, in some cases it may help overall performance if triggers are disabled before the publish job and then re-enabled after the publish (of course, extreme care has to be taken to inspect what the triggers do exactly as they may perform other inserts that the application depends on later).
The steps to create these actions are below: (This specific scenario deals with creating an action for a disable trigger DDL statement. Similiar steps may be applied for executing SQL statements or system commands for example)
Each time the data pool is published, the pre and post actions created will be executed before and after the publish respectively.