Skip to Main Content
Feature Request FR-2672
Status CLOSED

19 Voters

Queries supplied for deprecated/de-supported components

pjones_dev Public
· Aug 5 2022

Idea Summary
When things are deprecated/de-supported in APEX releases it can sometimes be a bit of a puzzle to identify exactly what is affected (the release note is sometimes vague) and then identify if your application(s) are affected. Once you have worked out what has changed we have found that usually the best way to find them is to query the metadata for any instances. If these queries were supplied then it would immediately help in understanding what the change was and also what then needs changing.

As an example here is a script which checks for buttons in Legacy positions:

SELECT  *
FROM    apex_application_page_buttons
WHERE   application_id IN (:APP_ID)
AND     display_position IN ('TOP', 'BOTTOM', 'ABOVE_BOX', 'BELOW_BOX');

And one for checking the Based on attribute of the Display only item when PLSQL became unsupported:

SELECT  *
FROM    apex_application_page_items
WHERE   application_id IN (:APP_ID)
AND     display_as_code = 'NATIVE_DISPLAY_ONLY'
AND     attribute_02    = 'PLSQL'
ORDER BY  application_id
        , page_id;

Use Case
When the version of APEX is upgraded and the application requires checking

Preferred Solution (Optional)
A script supplied with each release which checks for deprecated/de-supported items in the release (and all previous ones) which can be built on over time. Alternatively and/or as well perhaps there could be a new “Utility” or the existing “Upgrade Application” utility enhanced.

This request is likely a duplicate of FR-2233.

Comments

Comments

  • jayson hanes Admin OP 3 years ago

    Oliver Lemm has created this cool app that can help in the meantime - https://twitter.com/OliverLemm/status/1555546696020643841

  • ej egyed OP 2.9 years ago

    This would fit perfectly under Application ### > Utilities > Advisor.

    I agree it is definitely hard to identify any components/attributes/settings that have been considered “Legacy” after upgrading to a new version of APEX.

  • vincent morneau Admin OP 1.8 years ago

    Hi @pjones_dev ,

    This is a great use case for an improved Advisor. I marked this idea as a duplicate and we will make sure to address those concerns when we work on improving advisor.