If you'd like to make your outbound communication ready for execution, you would do a Publish. You may also do a Publish if you have made recent changes to an existing campaign.
You can learn more about the difference between Staging and Production here.
Agillic's Recommended Best Practice for Publishing in Agillic
Publishing is a must when you're working in Agillic and have made changes to items in the Flows, Channels, Promotions, or Data module. What Agillic publishes depends on which environment you're publishing to.
To ensure there's consistency between your instances and to make sure your data isn't lost, you must always edit your items on Staging and then Publish to Production. This makes sure that Staging and Production are always synchronised and nothing will be overwritten. We recommend to Publish to Staging to make sure all changes are set on Staging before publishing to Production.
When to do a Publish
We recommended to:
- Do at least one full Publish to Production every second week to ensure data and configuration synchronisation between Staging and Production.
- Do a Publish to Production if you've changed anything in the Flows, Channels, Promotions, or Data modules.
- Do a Publish to Staging if you've changed anything in the Channels module.
- Do a full Publish to Staging to prepare for execution and testing your campaign.
- Do a full Publish to Production to prepare for execution to live recipients.
A Publish should always be a Changes Publish or a Full Publish to ensure all items are published. You shouldn't use a Partial Publish as your standard way to publish as it's likely not to publish everything you need it to.
Remember, you must always make changes to the Flows, Channels, Promotions, and Data modules on Staging and never on Production.
Ways to Publish
You can publish in several ways, depending on the changes you made to your configuration. You can learn more about the several ways to Publish in Agillic here.