Panel | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
When hosting with the MCOECN, the URL to access your application will be of the format: https://<itc>-<district name/code>-<application>.ssdt-ohio.org
If you create a "test" instance, the url will start with "test-"
|
Panel | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
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.
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. |
...
Panel | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
A Test instance of USAS/USPS/INVENTORY/WORKFLOWS can be created for troubleshooting purposes. Creating a test instance will find the latest backup file for the district and restore it to the Test instance. A Training instance of USAS/USPS/INVENTORY/WORKFLOWS can be created to use when training a new district on a Redesign application. Create a training instance will ALSO find the latest backup file for the district and restore it to the Training instance. NOTE: Other than the NAME, there really is no difference between a Test and a Training instance. | ||||||||||||||
Panel | ||||||||||||||
| ||||||||||||||
When hosting with the MCOECN, the URL to access your application will be of the format: https://<itc>-<district name/code>-<application>.ssdt-ohio.org
If you create a "test" instance, the url will start with "test-" Examples: https://laca-ct-usas.ssdt-ohio.org (Production) |