Who is this article for?

Users configuring Tests in the Testing module.

Testing module access is required.

In the Testing module, you can configure a test to send automatically each time a new revision of a document is published.

Understanding how the trigger works

The send with every published revision setting is triggered by the act of publication. A document must complete the full Document Control lifecycle — through creation, editing, review, and approval — before it reaches the Published stage. Only at that point does the trigger fire and the test is sent.

A document in any earlier stage (Create, Edit, Review, or Approve) is not considered published and will not trigger the send, regardless of when the test setting was configured.

Applying the setting to unpublished documents

If you apply this setting to a document that has not yet been published — for example, a brand-new document still working through its first approval — nothing is sent until that document reaches the Published stage for the first time.

Example: You create a new document and configure a test to send with every published revision before Revision 1 has been approved. The document then goes through review and approval. No test is sent during this time. When Revision 1 is approved and published, the trigger fires and the test is sent for the first time. Each subsequent published revision will also trigger a send.

Note: Once Revision 1 is published, the trigger becomes active for all future revisions. You do not need to reconfigure the test setting after the first publication.

Tip: If you want to send a test before a document's first revision is published — for example, to familiarise staff with new content ahead of its release — configure the test to send manually rather than relying on the published revision trigger.