Objects may be attached to one or more application areas. The visibility of an object is defined by the possibility or impossibility of attaching it to one or more application areas.
Objects can be:
|
Multi-area objects (these may be attached to more than one application area). |
|
Single-area objects (these may only be attached to one application area). |
The ability to attach an object to one or more application areas is set using the "Visibility" field in the object definition screens (regardless of the action level, i.e. at repository level or within a given application area).
Objects can be attached to application areas in one of two ways:
By creating the object directly in the application area to which it is to be attached;
By using a special option to attach an object in the repository to the required application area.
Note: Objects with private visibility can be created in the repository. In such cases, the object will be attached to the first application area which will use it.
Special cases
Regarding visibility, certain types of object behave in a particular manner:
First case:
The visibility of the following object types:
data type,
management rule,
is special in the sense that, when these objects are public, they are systematically attached to all the application areas. Furthermore, when these objects are created in the repository, the visibility is mandatorily public.
Second case:
The following object types:
task,
folder,
can only be defined in an application area (single-area objects). Moreover, the visibility of these objects is mandatorily private.
Third case:
The concept of visibility does not apply to the following types of object:
logical entity (with a conceptual origin),
logical property,
IBM logical property (logical field),
access.
Fourth case:
The concept of visibility does not apply to the following types of objects which are visible from any application area:
logical server,
graphical object (basic or personalized object).