Bug 5210

Summary: Importing Policy from Modeler always places policy under Driver
Product: [Identity Manager] Identity Designer Reporter: Brent Thurgood <brent.thurgood>
Component: ImportAssignee: Brent Thurgood <brent.thurgood>
Status: VERIFIED FIXED QA Contact: Brady Rogers <brrogers>
Severity: Minor    
Priority: P5 - None Keywords: Built, Provo
Version: 1.0.0 Designer   
Target Milestone: 1.0 M4   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Brent Thurgood 2005-01-12 17:24:14 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)
Comment 1 Brent Thurgood 2005-04-25 16:38:18 UTC 
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
Comment 2 Howard Vanfleet 2005-04-25 20:26:19 UTC 
Build: 20050425
Comment 3 Brady Rogers 2005-04-27 17:00:45 UTC 
Verified this fix in build 20050425 on Win XP and NLD. All four of the tests
above passed on both platforms.
Comment 4 Bill Street 2007-04-30 16:37:36 UTC 
Marking closed/resolved fixed bugs public view.
Comment 5 Bill Street 2007-04-30 16:40:16 UTC 
Marking closed/resolved fixed bugs public view.