Bug 541

Summary:	Does not save after deleting a Driver Set
Product:	[Identity Manager] Identity Designer	Reporter:	Bill Street <bstreet>
Component:	Modeler	Assignee:	Lee Lowry <llowry>
Status:	VERIFIED INVALID	QA Contact:	Tim Pew <tpew>
Severity:	Major
Priority:	P5 - None	Keywords:	Provo
Version:	1.0.0 Designer
Target Milestone:	1.0 M2.1
Hardware:	x86
OS:	Other
Whiteboard:
Found By:	Development	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Bill Street 2004-12-10 18:47:25 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)

Comment 1 Lee Lowry 2004-12-13 22:50:17 UTC

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).

Comment 2 Bill Street 2007-08-16 15:45:19 UTC

Marking resolved fixed as public view.