Introduction

Object linking possibilities are not limited by the HDC database. However, users can create "perspectives" that limit linking to specific classes of objects. Single A single object can have child objects in the form of documents or other objects, depending . Depending on the perspective, only objects of a given type are shown in the hierarchy tree, and only documents (or documents of a given type) are shown displayed in GridView Tesselet. This allows for flexible data presentation that is as required by user and allows for creating users and enables the creation of alternative views on the same data by through configuration only.

Interlinked objects Objects in HyperDoc Database

The image below shows depicts the management panel for Perspective Sets management panel. It consists of comprises three windows:

• The Top window: where you create is used to create a set of perspectives and define their their Root class and a specific object.

• The Bottom-left window: where lists the perspectives that are part of the set are listed.

• The Bottom-right : where you can see window displays available object classes ("child" classes) for a given Perspective ("parent" class").

Image Removed

Image Added

Several perspectives can be grouped into Perspective Set.

Each Tesselet can be configured to use any given Perspective Set, all . All object classes, including documents, can be freely mixed in any perspective , as long as this it represents any useful business logic.  As an exampleFor instance, objects of selected classes can form a hierarchy by using TreeView Tesselet and a Perspective Set definition that could look like thisresemble the following:

Perspective Set: Hierarchy: {Root:Property}, {Property:Building}, {Building:Floor}, {Floor:Space}

Each pair of classes in the above example is represents a single perspective. Please It's important to note that one class could have several relative classes specified, for example:

Perspective: {Floor:Space,Document,Equipment}

Another perspective set can be created to show display documents in the form of a GridView Tesselet:.

Perspective Set: Doclist: {Building:Document}, {Floor:Document}, {Space:Document}

Yet another Perspective perspective can be used utilized to show display a large number of Equipment equipment elements linked to objects of Class: class Space. This Perspective can be shown in perspective is suitable for display in the GridView Tesselet as it supports paging and shows full metadata at hand:

Perspective: Equipment: {Space:Equipment}

Example with object inheritance

Having the Ground Object and as a subclass: superclass, including Bench, Tree, and Trash bin, we can provides the option to add both generic Graound Object Ground Objects or specific TreeTrees.

Perspective to select When choosing Property -> Ground Object will return all, including Tree, Bench and Trash Bin but in form of a generic objects (Only perspective, all objects will be returned, encompassing Trees, Benches, and Trash Bins in the form of generic objects (containing only properties common for Ground Objects).

If the check-box "include sub-classes" checkbox is uncheckednot selected, only objects created as generic Ground Objects will be returneddisplayed.

To obtain For obtaining specific classes like Bench,   Property -> Bench, Tree, Trash bin perspective must be used.or Trash bin, one should use the respective perspective under Property.

The Tree Tesslet will present showcase generic objects, while. In contrast, for example instance Grid Tesslet will present display multiple classes as Tabs.

Indirect Perspectives

Looking at the sample objects available in HyperDoc Database, if we want to present the Tenant name on each Space, w e we have to use indirect perspectives to achieve that.

• Space -> Tenant via Rental Unit, Contract 

• Space -> Rental Unit

• Rental Unit -> Contract

• Contract -> Tenant

Set Sequence

The 'Set sequence button can be used to fix the sequence of classed inside a given Sequence' button allows you to arrange the order of classes within a specific Perspective. This will influence affects how the sets are presented, for example, a GridView tab order will follow this sequencedisplayed, such as determining the tab order in a GridView.

Include Subclasses

Include sub-classes option can be used if The 'Include Subclasses' option is used when a user wants to display not only objects that represent representing a given class directly, but also all sub typesof its subtypes.

This feature is very usefull particularly useful in situations scenarios like thisthese:

1. We want group Grouping and display displaying all Documents , no matter what sub type they are (Architectual, Vent etc)We want to group and display regardless of their subtype (e.g., Architectural, Vent, etc.)

2. Grouping and displaying Ground Objects of all subtypes in one tab , and while specific objects are displayed in other tabs.Dokuments

In this configuration, the Documents perspective is

set up to

include all

subclasses:

Image Modified

Notice that Arkitekt, K, VS, V and El are actually defined as subclasses in the Class

structure Object Classes.

Image Modified

Related pages: