Idea Summary: Introduce an isPublished (or Active/Inactive) state at the Resource Template and Resource Handler levels within APEX RESTful Services. This would allow developers to enable or disable specific endpoints or HTTP methods individually, without needing to unpublish or delete the entire REST Module.

Use Case: Currently, the isPublished status is only available at the Module level. In real-world scenarios, a single REST Module often acts as a container for multiple Resource Templates (e.g., /employees, /departments) and their respective Handlers (GET, POST, PUT, DELETE). If a developer needs to temporarily disable a specific template (e.g., for maintenance, bug fixing, or deprecation of a specific endpoint) or block a specific action (e.g., temporarily disabling a POST handler to prevent inserts), they currently have no way to do this natively without either deleting the template/handler or unpublishing the entire module. Unpublishing the module disrupts all other fully functional templates within it. Granular status control would allow teams to manage, troubleshoot, and version their APIs much more safely and efficiently.

Preferred Solution (Optional):

1. Add a "Published" toggle switch (Yes/No) in the APEX Builder UI within the properties pane for both "Resource Templates" and "Resource Handlers".
2. Update the underlying ORDS PL/SQL APIs (such as ORDS.DEFINE_TEMPLATE and ORDS.DEFINE_HANDLER) to accept a p_status or p_published parameter.
3. When an incoming request hits an unpublished Template or Handler, ORDS should gracefully return an HTTP 404 (Not Found) or 503 (Service Unavailable), while allowing requests to published sibling templates to process normally.