Identity Manager 9.2 - Web Designer Reference Guide

The collection User contains the database of type Person that corresponds to the current user.

The UserRuntimeModule collection contains all module instances generated during a session. A module can be called up several times. Every time a module is called up, a new instance is generated. A module instance is a fixed instance of a module definition.

A component is a part of a module, which has been separated out. The module references these component using cross-references. It can be use by several modules and components and rendered multiple times in a browser simultaneously. Instances arise from components that are used more than once. To differentiate various instances from each one another, each instance is given an automatically generated suffix at runtime. All nodes of this instance have the same suffix.

Apart from that, components are part of the definition tree and keep it free from redundancies. This property reduces the effort of programming and ensure a uniform appearance as well as homogeneous functionality of the web application. Another feature is the different component type. The position of the component in the definition tree determines which component type can be referenced.

A form type specifies the structure of HTML pages, which are rendered in the browser. It defines the available form parts and their positions in the HTML tree structure. The Form types area is found in the navigation view and the form definitions are found as DialogAEDS objects in the database.

The default version supplies different VI objects as templates. To edit a form type, you must make a copy of the object. For more information, see Creating object copies with the wizard. Each form type is made up of the form parts Title and Main and other output nodes. Form types are often differentiated by mobile and desktop view.