In some cases, it is sufficient to add or delete a node, to change single properties within an object. In such cases, extensions are best suited to configuring the web application. This method of configuration allow you to describe changes to an object.
You can add any number of extensions to the Web Designer's base object module, component and web project. Some default extensions are already supplied when the database modules are installed. You can add custom extensions yourself.
Extensions are edited when you configure the base objects. That means you add an extension to the object and change the property value. You then compile the base object and the modification resulting from the extension is highlighted in the Web Designer.
You can identity base objects, which you want to extend, by their colored nodes in the Objects definitions view in the definition tree view. You edit extensions in the Configuration (custom) view.
Figure 1: Workflow in the Web Designer
To overwrite a single property in an extension
|
NOTE: An edited extension node is labeled with in the Object definition |
This swaps you to the Configuration (custom) view and marks the node with the modified property value.
|
NOTE: You can swap between Configuration (custom) and Object definition views with the button, if the extension is found under the Add node or Remove node node. |
Each extension is its own object in the Web Designer. The advantage of extensions is that database objects that have been extended are updated by migration without the database objects being overwritten. This does not apply in the case of object copies. In that case, the copy is not updated on migration.
The following extension rules are listed in the table.
Extension rule | Description |
---|---|
Inserting a node | Adds a new node to the read-only base object. |
Moving a Node | Removes a node from the base document and places it in an extension. |
Editing a property |
Modifies a node property in the read-only base object. |
Deleting a node |
Deletes a node from the read-only base object. A deletion is carried out, for example, when you want to delete a bookmark on the Web Portal start page. |
|
NOTE: You recognize an extension node by the colored bar marking it. |
You add a new node in the definition tree view using the context menu on your selected node. The entries in the context menu vary and depend on which type of node you are adding the extension node to. You can, for example, add new form or component nodes.
Because there are numerous types of node, which can be added to, the example of how to add a node is based on a node of type title.
To add a new node
The selected base object is displayed in the Object definition (read-only) view in the definition tree view.
|
NOTE: You can also select another item as New node if you know on which node type to base the extension. |
The new node is added with a custom prefix and a mark in form of a bar under the selected node. is displayed at the bottom of the definition tree view. Use
to go to the definition object.
|
NOTE: Fields marked with * are compulsory. |
|
NOTE: The text must be enclosed in quotes. |
The button is displayed in the definition tree view with the name you entered.
To modify the position of an extension node.
The edited new node is displayed in the Configuration (custom) view in the definition tree.
In the custom configuration view, you can, for example, edit the position of the button. This is how you do this.
The value is displayed after the Add node node (sort order: 0). You will see the change after compiling the preview. When you swap back to the Object definition (read-only) view, you will see that your added node is placed above the extension you marked.
You can move nodes, which are on a parent node in an extension. This assumes that the node to move is on a custom object which is not write protected. An example of this would be objects found in a container node. Other examples of moveable extension nodes are columns in a collection or parameters of a configuration parameter section.
|
NOTE: The menu item Move to extension is only available to custom objects. |
To move a node
The selected base object is displayed in the Object definition view in the definition tree view.
The node is marked in color as in the extension mode.
A change can take the form of extending viewing conditions for a container, for example, as explained below. Other changes are not gone into here. For more information, see How Extensions Work.
To edit a property
The view switches to Configuration (custom) and the Modify property value extension is selected. You can edit the extension.
The edited extension is displayed with the modification in the definition tree view and in the preview. The edited node is marked with in the definition tree view.
Before you can delete the node, you must create a deletion rule for the mode in question. You can only add a deletion rule to a node that does not contain an extension.
A use case would be if you want to remove a container node from a write protected base object.
To create a deletion rule
The node changes its colored mark and you can see the message, Remove node in the Node editor. You can also see this message on the extension when you swap to the Configuration (custom) view.
To remove a deletion rule
|
NOTE: The menu item Delete is only available to custom objects. |
You can use this wizard to create new Hyper Views or Hyper View shapes or to import existing ones.
Option | Description |
---|---|
Import a complete Hyper View | Imports a complete Hyper View definition from the database dialog structure to be used in the Web Portal. |
Import one or more Hyper View shapes | Adds one or more shapes, imported from the database dialog structure, to a Hyper View. |
Define a new Hyper View shape | Adds a new shape, which can represent data from any table, to a Hyper View. |
To import an complete Hyper View
Select an element from the list on the Select central element page and click Next.
The Wizard closed page is shown and the component is created.
To import one or more Hyper View shapes
Select a Hyper View from the list on the Extend an existing Hyper View page and click Next.
The Wizard closed page is shown and the component is created.
To define a new Hyper View shape
Select a Hyper View from the list on the Extend an existing Hyper View page and click Next.
The Wizard closed page is shown and the component is created.
© 2023 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy