Scope
This guide covers automation for Digital Twin. Availability depends on your tenant package, role and configured providers.
Purpose
Model measured funnel transitions and explore what-if scenarios.
Refresh the model from eligible observed outcomes.
Before you start
Correct tenant and project selected
Required source or provider is available
An accountable owner is identified
Test data can be separated from live activity
Procedure
- Complete the manual workflow successfully before enabling repeat execution.
- Refresh the model from eligible observed outcomes.
- Define the trigger, eligibility conditions, action and intended output.
- Add a failure path, owner, retry rule and stop condition.
- Run a controlled test and inspect every generated record or delivery event.
- Keep the automation bounded: Label assumptions and avoid presenting simulation as certainty.
Verify the result
Compare simulated changes with later actual movement. Confirm that the intended record, state, run or report is visible to another authorised operator and that its next owner is clear.
Completion checkpoint
The capability is in the intended state, evidence is current, exceptions are owned and the next action can be understood without a separate status message.
Controls and limitations
Label assumptions and avoid presenting simulation as certainty. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.