Bugzilla – Bug 5210
Importing Policy from Modeler always places policy under Driver
Last modified: 2011-06-03 09:51:33 UTC
DETAILED DESCRIPTION: Importing Policy from Modeler always places policy under Driver we should allow the user to place it under either the driver, publisher or subscriber. BUILD NUMBER: Oses/CONFIG: STEPS TO REPRO: RESULTS: EXPECTED: WORKAROUNDS: Go to tree mode and import directly to publisher or subscriber. 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)
Fixed. To test do the following Test #1 1. From the modeler right click on a driver an select import a policy 2. Select a policy in eDirectory that is contained in the publisher 3. The policy should be added in Designer under the publisher object. Test #2 1. From the modeler right click on a driver an select import a policy 2. Select a policy in eDirectory that is contained in the driver 3. The policy should be added in Designer under the driver object. Test #3 1. From the outline view right click on a driver an select import a policy 2. Select a policy in eDirectory that is contained in the publisher 3. The policy in this case should be added in Designer under the driver object Test #4 1. From the outline view right click on a publisher an select import a policy 2. Select a policy in eDirectory that is contained under the driver 3. The policy in this case should be added in Designer under the publisher object
Build: 20050425
Verified this fix in build 20050425 on Win XP and NLD. All four of the tests above passed on both platforms.
Marking closed/resolved fixed bugs public view.