Simple features to make checking in new DeviceTemplates easier/safer
We currently have a lot of mistakes when it comes to checking in device templates that end up breaking the build. This is usually due to one of two things:
-
Having multiple attempts a a device template that fail, then when the user does a diff, they don't fully understand that they should uncheck changes related to those "bad" older attempts at a device template
-
The user doesn't check both IR and DCE repositories for some devices that need them, OR doesn't check all of the appropriate tables if they try selecting them on their own. In some cases this causes an integrity failure because of a non-existant referenced foreign key.
I propose 2 helpful tools. They are both buttons that would appear on the DeviceTemplate page in the web admin: A) A "I don't want to check this new device template in, please remove it" button, which will safely remove that device template and any other table entries that reference it. We can check the psc_batch of the entry in the DeviceTemplate field to tell if its a new Device Template, and only show this option if we verify that it is a new Device Template
B) A" Submit This New DeviceTemplate" button, which will appear only if the Device template is new (determined the same as above). When clicked, this will automatically run sqlCVS update (as many users forget to run this before attempting a checkin, which will fix some problems related to propegating new PK's), and then check in the specific DeviceTemplate table entry, along with all tables that reference it.
Having the above features would help eliminate a lot of the erroneous checkins that break the integrity of sqlCVS and the build