Studio Approval Automatic Revoke

🔄 Execution Flow

• Administrator enables Revoke Approval for any Buttons or Actions.
• User requests approval and receives authorization.
• User performs the approved action.
• The frontend detects the configured button.
• The current record is automatically saved if required.
• A lightweight ORM RPC calls the revoke service.
• Matching approval entries are removed.
• The original Odoo button action executes normally.
• If the user needs to perform the protected operation again, a fresh approval request is required.

⚙️ Backend Model Design

The module introduces a dedicated configuration model studio.approval.revoke that stores revoke mappings independently from Odoo Studio Approval Rules. It acts only as a lightweight configuration layer, keeping business models completely untouched.

• Dedicated configuration model with minimal fields.
• Indexed fields (model_name, method, action_id, active) provide efficient lookups.
• No computed fields.
• No onchange methods.
• No stored dependencies.
• No inheritance of business models.
• Configuration remains isolated from business documents.

🚀 Query Optimization

• Frequently searched columns are indexed.
• Uses highly selective ORM domains.
• limit=1 is used wherever only one configuration record is expected.
• No expensive joins or aggregation queries.
• Approval entry searches filter by Model, Rule and Record ID.
• Configuration lookups remain extremely fast even as business data grows.

🌐 Controller Architecture

Instead of replacing Web Studio behaviour, the module extends WebStudioController by introducing a single custom operation: enable_revoke_approval. This approach follows Odoo's extension architecture and minimizes maintenance effort during upgrades.

• No override of Studio's primary editing workflow.
• No duplication of existing controller logic.
• Uses Studio's native operation dispatch mechanism.
• Responsible only for applying revoke metadata to XML views.
• Minimal impact on future Studio updates.

⚡ Batched Service Optimization

The module includes a custom batched service for get_revoke_spec(). Instead of sending multiple RPC requests while Studio loads several configured buttons, requests are automatically grouped into a single ORM call.

• Combines multiple frontend requests into one RPC.
• Reduces unnecessary network traffic.
• Improves Studio sidebar responsiveness.
• Eliminates duplicate requests during rendering.
• Uses Deferred synchronization similar to Odoo's own batching strategy.
• Scales efficiently for large Studio forms containing many buttons.

🔄 Upgrade & Maintainability

• Extends WebStudioController without replacing its core workflow.
• Patches only ViewButton and Studio sidebar components.
• Uses Odoo's official patch mechanism.
• No override of business models.
• No override of ORM methods such as create(), write(), unlink(), read(), or search().
• Minimal impact during future Odoo upgrades.
• Each component has a single responsibility (Model, Controller, Service and Frontend Patch), making the module easy to maintain.

🧠 Frontend Patch Design

The frontend extends only ViewButton, which is the exact execution point for button actions. This allows approval cleanup to occur immediately before the original business operation without altering normal Odoo behaviour.

• Only configured buttons execute additional logic.
• Standard Odoo buttons remain completely unaffected.
• Automatically saves unsaved records before revoking approvals.
• Uses ORM service for secure server communication.
• Returns execution to super.onClick(), preserving native functionality.
• Includes error handling to prevent unexpected frontend failures.

⚡ Performance Analysis

📦 Database Impact

📈 Scalability

The implementation performs constant-time configuration lookups and highly selective approval searches. Runtime complexity depends only on the clicked record rather than the total number of business records.

• Suitable for enterprise production environments.
• Supports MoreThan 200 of concurrent users.
• Performs efficiently with databases containing hundreds of thousands of business records.
• Indexed lookups prevent unnecessary full table scans.
• Performance remains stable regardless of Sales Orders, Purchase Orders or Manufacturing Orders volume etc,...

🧾 Final Technical Conclusion

• ✔ Lightweight extension of Odoo Studio Approval Rules.
• ✔ Automatic cleanup of temporary approval entries.
• ✔ Optimized database queries using indexed fields.
• ✔ Batched frontend service minimizes RPC traffic.
• ✔ Minimal CPU, memory and database overhead.
• ✔ No impact on standard business workflows.
• ✔ Upgrade-friendly architecture using Odoo extension points.
• ✔ Safe for large-scale Enterprise production deployments.