Reviewed 8 August 2026 · Omnivision Pro product documentation
Mock, Demo and Live data explained
Mock demonstrates a workflow, Demo provides illustrative scenarios and Live requires authenticated connected data.
Answer first
What is the difference between Mock, Demo and Live?
Mock demonstrates a workflow, Demo provides illustrative scenarios and Live requires authenticated connected data.
The review should preserve the source, scope and data state alongside the conclusion so another operator can understand what supports the decision.
Evidence to retain
Keep the decision connected to these signals.
Visible data-state label
Record its source, coverage and current state before interpretation.
Authentication state
Record its source, coverage and current state before interpretation.
Connected platform and scope
Record its source, coverage and current state before interpretation.
Freshness and coverage
Record its source, coverage and current state before interpretation.
Practical workflow
Read the visible data-state label.
Keep the result reviewable before moving to the next stage.
Confirm whether authentication is active.
Keep the result reviewable before moving to the next stage.
Do not transfer Demo conclusions to a Live account.
Keep the result reviewable before moving to the next stage.
Decision questions
Ask before approving a change.
- Is this workflow illustrative or connected?
- Can the result be applied to an account?
- What authentication or authorization is still required?
Common failure modes
Do not let missing context become certainty.
- Using Demo values in a performance conclusion
- Falling back to Mock after a Live error
- Hiding an unavailable connection state