Versions Compared

Old Version 5

changes.mady.by.user Chad Carson

Saved on

compared with

New Version 6

changes.mady.by.user Chad Carson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel
borderColor#000099
bgColor#dddddd
titleColor#ffffff
borderWidth2
titleBGColor#000099
borderStylesolid
titleProduction Instances

A Production instance of USAS/USPS/INVENTORY/WORKFLOWS is the live instance used by the district for their daily tasks.

A Production instance must be marked as "LIVE" on the date the district goes live with the application. 
Marking it as LIVE does two things:

  1. It adds the instance to the automated nightly backup routine at MCOECN
  2. It protects the instance from being accidentally overwritten by running the task to create a production instance in VRA. If you try to run a "Create as Production" for a district that already exists AND is marked as LIVE, that VRA request will fail.


There is a VRA task called "Mark As Live" that you must run when you are ready to mark a district application as LIVE.  Note that running this WILL take the application offline for a few minutes, so you should coordinate this downtime with the district, or schedule the "Mark as Live" task to run overnight.

Image Added



Panel
borderColor#000099
bgColor#dddddd
titleColor#ffffff
borderWidth2
titleBGColor#000099
borderStylesolid
titleDemo Instances

A Demo instance of USAS/USPS/INVENTORY/WORKFLOWS can be created to show Redesign to new customers.

A Demo instance contains randomized data, not live data, so you do not have to worry about exposing any real data.
You can add/delete/change all the data you want. The demo instance database is unique to your ITC, and is not shared with other ITCs, so you cannot hurt the demo database. 

If you mess it up, delete the Demo and create a new one to put it back to square one.

Only ONE Demo instance is allowed per application per ITC.

...