This is a reminder that no updates or changes will be moved into the PROD environment unless they have been fully tested, verified, and approved in the test instance first.
*Unless noted otherwise, we are not testing the printing feature*
*Updates are not affecting the mods*
Recent instances have shown that we, including IT, have been skipping steps and rushing changes through without proper testing. This introduces unnecessary risks to production systems. Going forward, we will strictly enforce the following:
- All updates must be thoroughly tested in the STUDENT instance.
- Each department must test all the critical, routine, and high-priority functions they rely on in daily operations. This includes everyday processes and essential tasks that are vital to departmental workflows.
- Documentation of testing results, including workflow, must be provided.
- Formal verification from all responsible parties is required before deployment approval.
If these requirements are not met, the update will not be approved to proceed to PROD. This is non-negotiable.
Let’s maintain our standards and protect the integrity of our production environment.
In keeping with the Banner mission, our policy is to maintain the Banner system at the most current levels supported by Ellucian. We also use third-party vendors whose partnership with Ellucian provides functionality complementary to the Banner system. The following procedures are used when applying any upgrade to the system:
- Prior to the PROD upgrade, each Banner users can read/review the Banner Release Guide which will show details, related defects, etc. Each department is encouraged to look at the release guides. Previous Releases. These guides will be attached to the emails notifying you of updates pending to be tested.
- Each Banner Functional Coordinator will develop a thorough test plan for the upgraded application.
- The departmental users of each module will execute the plan by testing their normal processes and reports, and any new functionality that may be implemented.
- Any problems found during testing are investigated and corrected by either the departmental users--if data problems--or the Banner Database Manager--if application problems.
- When testing is complete, the Banner Functional Coordinators must notify IT.
Please fill out, pdf, print, and return signed to the IT Department.
Please use the Testing Sign Off link below
Table of Contents
Where to find the Student Test Instance
Your Sign on/Password is the same as Production
You can find the links to the Self Service pages that are linked to the STUDENT Instance on this card as well
Common Issues when testing
-
Printing Issues
If you encounter any problems while printing, please contact the IT Helpdesk to open a support ticket for assistance.
-
Missing Data or Closed Periods
Missing data or closed periods may indicate outdated information. Try adjusting your dates or processes. If the issue persists, reach out to the IT Helpdesk for further assistance.
-
Errors or Unexpected Results
For any errors or unusual outcomes, please take a screenshot and email it to the IT Helpdesk along with a brief description of the issue and your expected result.
Links for Testing
Student Instance Admin Pages
My Finance Dashboard for Student Instance
Registration for Student Instance
Employee Dashboard for Student Instance
Financial Aid Self Service for Student Instance
Testing Sign Off Form
Testing Sign-off
What if I need additional assistance?
SJRstate IT is here to help! Reach out to us by:
- Calling the Helpdesk at (386)312-4142
- E-mailing Helpdesk@SJRState.edu
- Using the Help Portal at help.sjrstate.edu , and filing a service request ticket for the appropriate service. If you're not sure which service to use, you can submit a general request with the button below and we'll categorize it for you!
Submit General I.T. Helpdesk Ticket (Staff And Faculty)