Chat now with support
Chat with Support

Identity Manager 8.0 - Web Designer and Web Portal Changes

One Identity Manager
Compiling web projects with customizations Updating web applications Changes in Web Designer and in Web Portal 8.0 Changes in Web Designer and in Web Portal 7.1 Changes in Web Designer and in Web Portal 7.0

ComboBox control behavior

The combobox control now automatically refreshes itself when the associated filter condition changes.

Properties moved to attributes

Some Web Designer properties correspond directly to attributes of the resulting HTML nodes. Those properties have been moved to attribute nodes. The following node types are affected:

  • ALT attribute: Image
  • TITLE attribute: Container, Label, Button, LinkContainer
  • STYLE attribute: Container, Label, Image, Cell, Button, LinkContainer

Enhanced object sheets for groups

In previous versions, the VI_Common_ObjectSheet module offered a read-only view of a group object. The module uses VI_Interfaces_ObjectSwitch_ObjectSheet components to show a view depending on the type of the group.

The group components have been upgraded to allow for editing if the logged on user is an owner of the group. By default, this means that the user must be either:

  • A member of the owner role associated with the group’s service item, or
  • A member of the administrator role for the group’s target system or container.

This affects all groups that map to the UNSGroup view.

Passing entities to components

If you have defined an object sheet component for an object type, an entity of that type is passed to the component at runtime.

The actual loading usually happens in the VI_Common_ObjectSheet module. For performance reasons, this module now loads entities in read-only mode instead of the interactive mode.

This is a change that may require modifications to existing components. If your object sheet component implements editing functionality, you will need to convert the read-only entity into an interactive entity first.

As a general rule, components should not presume that entities being passed were loaded in any particular mode. Furthermore, converting to an interactive entity should happen at the last possible moment.

If your component requires an entity to be interactive, your component should create an interactive entity. (If the entity is already an interactive entity, no actual conversion happens, so there are no side effects of doing multiple conversions.)

Related Documents