Bugzilla – Bug 507
Modeler doesn't prompt to save changes on Edit Policies after changing driverset properties
Last modified: 2011-06-03 17:49:28 UTC
DETAILED DESCRIPTION: (Migrated from Remedy DEFECT000393904) If I edit the driverset properties, then click on Edit Policies, I do not get prompted to save the changes. The asterisk appears next to the project name to indicated changes were made, but no prompt is given to save the changes when I click on Edit Policies. BUILD NUMBER: Porpoise build M1.1 with 1123 plugins. Oses/CONFIG: Windows XP and Linux. STEPS TO REPRO: 1) Create a new project, add an identity vault, driverset, driver and connection line. 2) Save the project. 3) Click on the DriverSet object and edit the Context property (I set it to "novell"). 4) Right-click the driver connection line and select Edit Policies. RESULTS: Prompt should appear to save changes, but no prompt appears. If I subsequently add a new policy on the Policy Management page, the driverset shown will be named "DriverSet.null" which indicates my Context change was not saved. EXPECTED: WORKAROUNDS: CUSTOMER IMPACT:
This, believe or not, is working according to design. But, I'm not sure if I like it. The prompting only occurs if the Driver has changed. This will lead to problems if you need to access the latest DriverSet information while editing the Driver. If you feel that there are usability issues there, re-open this under Will Peterson's name.
Assigning to Will Peterson (see Lee's previous comment).
This is working as designed. Only saved attributes should be reflected globaly. I'm not sure what user experience you would like to see.
When I click on Edit Policies, I would like to see a prompt asking me so save the changes I made to the DriverSet properties, just like the prompt that appears if I make changes to the Driver properties, then click on Edit Policies.
Brady, as we discussed in person, we'll need a more specific user experience defined. This will probably be more related to the individual editor, and is not directly related to the application framework itself.
Will, if this needs to be assigned to someone else, that is fine with me. I still think we should prompt to save changes if DriverSet properties have changed when the Driver Editor is accesssed. This might be more of an Enhancement, but I think it should be implemented.
Hi Brady- We need more specifics please.
I talked to Brent about this and discovered this is no longer going to be an issue because the Driver Editor is going away and policy management will now use the same resource set as the modeler. I also discovered that the driver set context should not be shown at the end of the policy name, which will get rid of the .null issue. I'll close this bug once these changes are verified.
Build 20050420. The Driver Editor is now gone. If the context is changed, but not saved, then Add Policy is run, the new context is shown. But the old context still appears in Policy Builder. I'll close this bug when context is removed (bug 77888).
Verified this fix in build 20050425 on Win XP and NLD. Context is now gone (bug 77888).