Dell Vizioncore Guía de usuario descargar pdf (Pagina 57)

The Web Component Framework 57

Core Concepts

Definitions and Entities

Definitions are the configurable units in Web Component Framework. They include

Views, Queries, Tasks, Icons, Types and Units.

Entities are the types of definitions which can be referred to by an ID identifier in other

definitions. Views, Queries, Tasks, Icons are entities.

Note Views and their properties are described in the Web Component Reference.

Public

Marking an Entity as public indicates that it can be used by any definition in any other

module. For this reason the editors will not allow you to delete a public entity. However,

you have the option of replacing a view containing a public entity.

Entities that are not public can only be referenced by definitions that have a shared

module ancestry. Definitions have a shared module ancestor if they have a parent,

grandparent, and so on, module that is the same or one is an ancestor of the other.

When selecting an entity, only public entities are shown in modules that don't have a

common ancestry with the module containing the current definition.

Copying Entities

When copying entities, whether entities are public or not needs to be taken into

consideration.

You can make a shallow copy of an entity that is not public. However, if that entity

refers to a non-public entity, that is, refers to a query via a Query Selection Runtime

Value, then the copy will not be allowed if that non-public entity is not accessible from

the target module to which you want to save the copy.

The View’s deep copy feature can be used to copy a view that references a non-public

entity that is not accessible from the target module. However, a warning message will be

issued that the inaccessible, non-public entity will be copied and the reference will be

changed to refer to the copy. This may not be what you want. You may actually want the

references to be maintained because you intend to deep copy a view to a temporary

module, make the desired changes to the view and its related entities, and then deep

copy the view back to its original module.

You can perform either a copy of the view or a deep copy of the view without having to

use the Add View work flow to invoke the copy. Moreover, if you wish to do a simple

copy, but are not permitted to because of private reference restrictions, then a deep copy

1 2 ... 52 53 54 55 56 57 58 59 60 61 62 ... 167 168

Sin comentarios

Dell Vizioncore Guía de usuario Pagina 57