Workflows, Replication, and Content Activation
Replication moves content from author to publish. Understand the replication agents (default, dispatcher flush), the replication queue, and how activation is triggered (page activation, tree activation, and ReplicationOptions). Know the difference between activate, deactivate, and delete, and how the dispatcher flush agent invalidates caches after replication.
Workflows automate content processes. Know the workflow model, launcher, workflow instance, and steps (participant, process, OR split). The DAM update asset workflow and the request-for-activation workflow are common examples. Understand inbox tasks, MetaDataMap, and how to write a custom workflow process step (implementing WorkflowProcess).
Traps: assuming activation is instant (it's queued); forgetting that a dispatcher flush agent must be configured for cache invalidation; confusing workflow launchers (trigger conditions) with workflow models (definitions). Another trap: tree activation of a large subtree can overwhelm the queue-use filters and batches. Also, workflow steps that throw exceptions can leave instances stuck.
Worked example: to require approval before publishing, configure the Request for Activation workflow as a launcher on page activation, so activation creates a workflow instance with an inbox task for an approver, who then triggers replication.
Rule of thumb: activation is asynchronous-verify the replication queue and dispatcher flush logs, not just the author UI.