hero-angle-alpha hero-angle-beta icon-rss-square icon-instagram icon-rss icon-facebook icon-facebook-square icon-facebook-official icon-twitter icon-twitter-square icon-google-plus icon-google-plus-square icon-linkedin icon-linkedin-square icon-pinterest icon-pinterest-square icon-youtube icon-youtube-square icon-youtube-play icon-search icon-gift icon-graduation-cap icon-home icon-bank icon-envelope icon-envelope-square Cabrini Logo Cabrini Logo icon-chevron-right icon-chevron-left category academics category athletics category just for fun category service and mission category living on campus category profiles category advice category activities and events Cabrini University logo with crest
Return Home

Banner Test environments

In order to ‘test drive’ new configurations and customizations certain applications are also available as ‘Test’ instances.  These instances are only used by a subset of the main, Production user base.  These Test instances are occasionally cloned from their corresponding Production instances so that the data is reasonably recent.  Banner Test, for example, was last refreshed with data from EOD Tuesday, July 24.

Accounts in Test Banner are created when the Production database is cloned into Test.  Users will access Test Banner using the credentials (ID and password) that they had as of the last data refresh (identified above).  If your password has been updated since the last refresh, make sure you use your previous password.  If your user account was added to Production Banner after the last clone date then you will need to submit a PSC ticket requesting that your Production access be cloned to Test.

NOTE: The Test instance is never used for Production purposes, and the data contained within Test can be overwritten (i.e., by another user or by a Production clone) with little or no notice/warning.  It is incumbent upon the users of Test to make certain they are aware of which instance they are in (Test or Production).  Data entry completed in Test can not be migrated systemically/automatically into Production, it must be manually rekeyed.