File Library

In our last APEX projects our teams went bigger and bigger and we identified some problems and requirements we got in every different project. Some of these problems could be identified by using the apex repository or the database dictionary. Even if the developer knows the coding and style guidelines there are some issues which still not every time are in their mind.
Based on these experiences a package was designed which created a simple output used on the Global Page, which is only visible when logged in as a developer. The next step was to use this approach in a flexible and re-useable way by developing an APEX plugin.
In comparison to the APEX Advisor this Plugin is much more flexible, because it’s designed to use your own SQL queries. These queries are saved in a table and can easily be edited or extended. Beside the Add-on itself, it’s possible to export or import a set of rules for using in other environments. Further on by using SQL as a Rule definition it’s also possible to create queries based on all SQL objects or table contents.
Additionally the APEX-Edit-Link (like in the APEX Builder or in the Advisor) is integrated to jump directly into the component (if it is an apex component). More Features like a categorization into Error levels and activating/deactivating a rule are supported.
Overall the mechanism in this Plugin is primary designed for a Region Plugin, but could also work as a process Plugin. By using a type with cast as a multiset for the rule queries they are performing well and the APEX_COLLECTION-Package is used to process the result with own SQL functionality.
This functionality can be a package which is using the apex_util.submit_feedback procedure to create directly a ticket for the team development area, or a database job which generates summary mails, or a mail per developer which is working on this page.
This APEX Plugin or even the approach itself can be really helpful. Already in a project with one developer, it’s easy show the bugs while the developer is working on this page. In addition every new developer who has lesser apex experience or has not read the full manual/guidelines will get a direct response while he is changing the page.
Overall if the rules are well designed and in addition metadata tables, based on the project concept were used, which are filled with information’s about labels, length and other APEX component attributes it’s a really fast and effective way to check many requirements before the page will go to the QA-Team.