Ellucian Insights

Ellucian Insights - Banner SaaS - Data Report Specification

Specification Instructions by Tab

• Red fields are considered Required.
• Blue fields are Optional.
• Green fields are completed when Request Completed.

1. General Info
   
   
   • Request - Report Identifier, Report Name, Legacy Report Name, Priority, Due Dates, and Contact Information.
   • Purpose - Description of the business need and/or processes being supported.
   • Report Type - List, Extract, Banded (formatted for viewing), Crosstab, Dashboard/Chart
   • Security - Which domains and/or users need access to run the report
   • Data Validation Methodology - Identify how the report will be validated for accuracy and sign-off for the user who validated report.
   • Report Signoff by Institution - Specification Sign Off User and Date, Report Complete Sign Off User and Date.



2. Report Fields - refer to Using Banner Metadata
   
   
   • Notes on Style, Layout, Groups, and Totals - Any information that may affect report visualizations. Charts should list which fields should be visualized and list data needed subtotals and totals should list which data element(s) to use for processing.
   • Include deceased persons? - Identify how persons should be indicated as needed.
   • Field Name - Column Header Name
   • Banner Form - Where in Banner does this data get populated? *Note: view screens that consolidate information do not always give us all the information needed to identify where data is stored in the database.*
   • Banner Form Field Name - Which field on the Banner screen is used to enter the data.
   • Banner Table Field Value - Using Banner Metadata as a guide, which table in Banner contains this data.
   • Insights Table Name - Using Banner Metadata as a guide, which Insights Object contains this data.
   • Insights Field Value - Using Banner Metadata as a guide, which column in the Insights Object contains this data.
   • Filters - Indicate any filters required for this data field.
   • Sort Order - Indicate in which order data fields should be sorted.
   • Parent/Child Grouping - Should this field appear as a header and/or footer? Should there be spacing between this grouping and/or a page break?
   • Add Calculations / Summary / Totals Fields - Is this field used to produce summary information (subtotals, totals, counts, etc)? Is this field a calculation? What logic should be used for calculation?
   • Comments - Any additional vital information that may be relevant to producing the data accurately.



3. Prompts
   
   
   • Prompt Title - Heading for the prompt
   • Required or Optional - Indicate if value is required to render report or may be left blank.
   • List of Values - Using Banner Metadata as a guide, which table in Banner contains this data.
   • Requirements/Comments - Any additional vital information that may be relevant to producing the data accurately.
   
   
   
4. Scheduling
   
   
   • Default Prompt Values - What should the prompts be set to for scheduling?
   • Final Date of Execution - Through what date should the report schedule begin?
   • Scheduled Days - Which day(s) should the schedule run?
   • Frequency - One time, Daily, Weekly, Monthly, Quarterly, etc?
   • Available Tasks - Is there any additional processing required?
   • On Success - Do you want a notification when schedule/report run is successful?
   • On Error - Do you want a notification when schedule/report run is unsuccessful?
   
   
   
5. Sample Output
   
   
   • Provide a mock-up of how the report should look.
   
   
   
6. Test Data
   
   
   • Provide 10 more more rows of data that is expected to be returned in the report for data validation by report writer prior to requestor validation.
   
   
   
7. Test Plan
   
   
   • Serves as a guide to ensure the report elements are verified indicating either acceptance or the requests fix/change.