Bug 562

DETAILED DESCRIPTION:  
From Holger Dopp:

For Apollo.DR1, we implemented DEFECT000359312.  This provides links to
iManager's schema management tools.  In reviewing this, Holger would like to see
more done.  See the content of his email below:
- - - - -
I would like to see not only a link to the possibilities, I would prefere a more
closer integration.

Assume this scenario:

- I refresh the schema and doe see a new class in the application
- I select the class and say 'import into eDir schema'
- the wizard appearing now does this:
	- ask for the new eDir class name (default is the app schema class name)
	- per default the new class is derived from Top (if necessary this can be
specified also)
	- the class containment must be specified
	- the class type may be derived from the app schema (if necessary it can be
specified)
	- ask if I want to import all app schema class specific attributes (and lets
select all or some)
	- ask for the new eDir attribute names (default is the app schema attribute name)
	- the default type is CI_STRING but can be specified if necessary
- for a single attribute the wizard should do something similar to retrieve,
name, specify and assign the new app schema attribute

For it looks cool as all this steps would be one wizard, which may run in a
popup window as you already suggested.

One of the targets should be, to prefill as much fields in the wizard as
possible and to limit the number of clicks and characters to type in.



BUILD NUMBER: 
Oses/CONFIG: 
STEPS TO REPRO: 
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)