improving the FWP APEX application
Stung by the criticism of our Football Web Pages APEX application, we decide to try to address the various issues raised by end users and peer code review. When clicking ‘Fixtures’, I get ‘ORA-20999: REST Data Source returned an HTTP error: HTTP 400: Bad request’ If you enter a Competition only, it works fine. If you enter a Team only, it works fine. If you enter both a ‘Competition’ and ‘Team’, the results look weird. Should ‘Team’ be a cascading LOV based on the ‘Competition’ ? The column names and labels need tidying up. There are a lot of meaningless ID fields displayed. It would be nice to have the option to review past results separately from fixtures in the future. Performance - the Popup LOV’s for Competition and Team are sluggish. Why are they so S L O W ? The navigation menu looks chaotic and ugly. HTTP 400 error entering Fixtures report This error is because the REST parameter for ‘Competition’ or ‘Teams’ is required. When we first run this page, there no values defined for the ‘Competition’ or ‘Teams’ parameters which results in the error. ...