Policies can be used to run custom code or fire off actions when an event, such as creating a content item or associating a content item into the content graph, occurs. Cloud CMS provides a wide array of policies that you can hook your custom logic into.
By default, Cloud CMS provides sensible and useful content policy handlers to manage the lifecycle of you content. You can wire in new policy handlers. Policy handlers include scripts and rules.
These policies will trigger behaviors when merging Branches or releasing Releases. For example, if you create a new node on a branch that you then merge to master, the
p:afterCreateNode policy will fire bound behaviors after the merge. The exceptions to this are attachment policies: these will only fire when an attachment is initally created, updated or deleted.
The following types of policies are available: