Configure and test an automation
Define trigger, scope, action, audience and stop rule; dry-run it; preview communications (AO02, AO03, AO05).
Authorized automation owner
/pdcc/my-work/automations?screen=AO02 Live walkthrough · Configure and test an automation
Acquisition watch (AO02)
- Name
- e.g. Pilot evidence watch.
- Trigger
- e.g. daily at 09:00 America/Denver.
- Scope
- e.g.
CT-DEMO-007required evidence gaps. - Action
- Notify, prepare for review, or a permitted automatic action — e.g. draft an in-app reminder.
- Stop rule
- e.g. evidence gap resolved or access revoked.
- Recipients
- e.g. assigned evidence owner only.
- 1
Create
From a recommendation, from a Studio view (filters become a reviewable draft), or Configure evidence watch.
- 2
Save inactive draft
New rules stay inactive until tested and approved.
- 3
Test (AO03)
Synthetic dry run: matched work, proposed actions, no dispatch.
- 4
Preview communication (AO05)
Recipient resolution, channel, subject, message, attachments — *Dispatch: Not sent*.
- 5
Submit for approval
See approval and runs.
Note — Tests use no production credentials or side effects and cover stale data, changed access, empty results, duplicate triggers and unavailable sources.
Heads up — Scope can never exceed the initiating user or approved workload-identity authority. Templates inherit content, destination and source-use constraints; selecting a template is not sending.
Related guides