Author: Colm Carew
Each time a report is finished another member of staff should go through the report with you with the following checklist and ensure everything is in order
https://docs.google.com/document/d/1fzRQtcqlGCfCoXOaSA_CwZ3luE-kw0WYRH5qH3i1uho/edit
If you have not had any of your previous reports corrected, now may be a good time to get your mentor to correct a report using this checklist.
A report executes SQL queries against a live database. If a query takes too long to return or worse, doest not return then this will impact every other report or any other feature that uses the same database. The more queries running against a database the longer it will take to return and thus breeds more and more problems. Hence why we have this checklist which ensures a report performs correctly.
Another reason for the checklist is that the person sitting in with you to check it may have new ideas or different approaches that may aid the report. Alternatively they will catch something that you may have missed when reviewing the report.
/***************************************************************
* Copyright (c) 2016 Errigal Inc.
*
* This software is the confidential and proprietary information
* of Errigal, Inc. You shall not disclose such confidential
* information and shall use it only in accordance with the
* license agreement you entered into with Errigal.
*
*************************************************************** */
/**
* Created by David McGee on 3/21/16.
*/
public static void main(String[] args) {
/**
* Original Author: David McGee
* Create Date: 1-Oct-2010
* Developer Notes: Report to capture hub audit data.
*
* Update History:
*
* (Date - Contributor - Support Ticket - Quick 1 line note on modification. Example below)
* 01-Nov-2016 - David McGee - CUST-123 - Updated report to use new datasource
*/
}