It is designed for easy creation of new components that inherit functionality from other components or add inheritance to an already created component.
It guides you through the whole inheritance process. This table explain the fields of Component Information page.
Table 1. Component information | Field |
Description |
|---|
| Name |
Name of a new inherited component |
| Component Description |
Description of the inherited component |
Note: Using this wizard, you can either create a new inherited component or add inherited methods to an already-created component.
After entering the relevant information in Component Information page, click Next. The figure below shows the Interface definition page.
Figure 1. Interface definition page 
This table explains the fields of Interface definition page.
Table 2. Interface definition | Field |
Description |
|---|
| Inherit |
Selects if that specific method will be inherited |
| Scope |
Scope of the method - The visibility and reimplementation of the method - Private - The method is implemented in an ancestor, and descendant can call it. This method is not visible in the descendant (in the page Methods)
- Published - The method is implemented in an ancestor. It is also visible in the descendant (the same like if it was method of the descendant), but is read only, that is you cannot change its name, parameters, etc. The descendant generates only macro that calls the ancestor
- Override - Combination of previous two ones, that is method is implemented in an ancestor but descendant overrides this implementation
|
| Mode |
There are seven values: - ALWAYS_REQUIRED - ALWAYS REQUIRED - Method/event must be in the ancestor and is always generated.
- REQUIRED_IF_EXIST - REQUIRED IF EXIST - Method/event is generated if it exists in the ancestor.
- OPTIONAL_MUST_EXIST - OPTIONALLY REQUIRED, BUT MUST EXIST - Method/event must exist in descendant, it may not be set for generating (code design), but it can be changed in the CHG file of the descendant component. For more details, see CHG File topic.
- OPTIONAL_IF_EXIST - OPTIONALLY REQUIRED, MAY NOT EXIST - Method/event may not exist, but if it exists it may not be set for generating (code design), but it can be changed in the CHG file of the descendant. For more details, see CHG File topic.
- OWNER_MUST_EXIST - MAY NOT EXIST, GENERATE IF OWNER - Method/event may not exist; if exists it will be generated only if descendant has method/event with the same name.
- OWNER_IF_EXIST - MUST EXIST, GENERATE IF OWNER - Method/event must exist; it will be generated only if descendant has method/event with the same name.
- SAME_AS_OWNER - The method may not exist in ancestor component, and is generated if it is required in descendant component. The settings of descendant component method is updated automatically.
|
| Read Only |
Select if method is set as read-only |
When you have to modify the interface, choose the appropriate inherited component (interface). In the Interface editor, select the Basic Settings pane, select the Interface Name from the drop-down list and then click the Edit button to open and modify the interface.
Figure 2. Interface editor 
The following screen appears after clicking the Edit button.
Figure 3. Interface edit screen
For more information on Inheritance, see Inheritance chapter.