Add the ability to take ECMPS offline so that people can't submit. Also, we may want a test mode where testing can be performed but outside users can't access the system.
Need to look into what can be done with the APIs.
Via the content repo, update the disabled message to state, "The ECMPS 2.0 Login has been disabled due to maintenance. Please read the notifications in home page’s "What's New" box and ECMPS Newsletter. For further assistance, please contact us.”
Note, there will likely be no link to our current ECMPS Beta "Contact Us" form as that will likely change, unless we can manage that link in the content repo, link TBD.
For ECMPS 1.0, we use three different status codes.
DOWN - used for scheduled maintenance and migration activities. Nobody can log in.
ONLINE - anyone with the appropriate CBS/ECMPS credentials can log in.
PQATEST - used during migrations and allows only the esupport user to log in post migration activities and prior to bringing the application ONLINE. The main purpose is to ensure that users will be able to download the latest release update from the Oracle host database and successfully update their clients from the previous to new release version.
The current understanding is that there will not be a related esupport user in ECMPS 2.0. ECMPS Support staff will have production CDX ECMPS Analyst roles which can only access the System Administrator module. Due to this and the fact that there will no longer be standalone desktop applications, it does not seem that the PQATEST status needs to move forward.
@esaber76 Please update the description based on how things are configured for ECMPS 1.0. Also, please add anything "new" that might be relevant for ECMPS 2.0.
Add the ability to take ECMPS offline so that people can't submit. Also, we may want a test mode where testing can be performed but outside users can't access the system.
Need to look into what can be done with the APIs.
Via the content repo, update the disabled message to state, "The ECMPS 2.0 Login has been disabled due to maintenance. Please read the notifications in home page’s "What's New" box and ECMPS Newsletter. For further assistance, please contact us.”
For ECMPS 1.0, we use three different status codes.
The current understanding is that there will not be a related esupport user in ECMPS 2.0. ECMPS Support staff will have production CDX ECMPS Analyst roles which can only access the System Administrator module. Due to this and the fact that there will no longer be standalone desktop applications, it does not seem that the PQATEST status needs to move forward.