Scope
Oto provides activity and exception views for workflows that require accountability or reconciliation. These include the existing activity logbook and the action histories required for POS, stock, occupancy, child release, integrations, and hardware operations.
Design
An authorized user opens the relevant activity or exception view, filters the records within their scope, and reviews the responsible person, affected record, branch, action, time, and any reason required by that workflow.
Failure handling
If required activity or exception information is unavailable, the affected view shows that it cannot confirm the action and does not present incomplete information as a complete history.
Requirements
- Authorized users can review the activity records required by payments, discounts, refunds, wallets, stock, occupancy, child release, configuration, and integration workflows.
- Recorded activity identifies the responsible person and affected branch where the source workflow requires it.
- Authorized support users can see failures that require review or reconciliation.
Verification
- Test that each source-required action appears in the appropriate activity or exception view.
- Test that viewers see only activity and operational problems within their permitted scope.