Bugzilla – Bug 541
Does not save after deleting a Driver Set
Last modified: 2011-06-05 00:13:51 UTC
DETAILED DESCRIPTION: Created a new Project, Placed a new Identity vault on the Modeler then imported a Driverset, then deleted the extra Driverset. Then did a save, it appeared to save but I get errors trying to edit a Driver. BUILD NUMBER: M1.2 Oses/CONFIG: STEPS TO REPRO: Nathan wrote this defect. I moved it over to Bugzilla RESULTS: EXPECTED: WORKAROUNDS: CUSTOMER IMPACT: NTS entered defects should also include: Additional debug info like screenshots, screencams, log files, trace files, packet traces, memory coredump location. Accurate customer information so that proper prioritizing of the defect is possible (mainly for NTS defects)
This is working as designed for the "Prompting Architecture". The reason is, the Policy Editor doesn't "directly" care about the DriverSet because it's editing a Driver. Where it can be problematic, is if Policy Editor tries to access something about the DriverSet like GCVs - you won't have the latest values, if you didn't manually save. If you are uncomfortable with this UI experience, we may need revisit how the prompting behaves and re-open this bug to Will Peterson. (Note: The cloning architecture will communicate all current state information over to the new editor and this wouldn't be a problem).
Marking resolved fixed as public view.