Web projects now compile directly to the asynchronous VI.DB entity layer. Database-bound Web Designer collections now contain entities (IEntity objects) instead of IColElem/ISingleDbObject objects.
Web projects now compile directly to the asynchronous VI.DB entity layer. Database-bound Web Designer collections now contain entities (IEntity objects) instead of IColElem/ISingleDbObject objects.
Selecting the correct entity load type can have a significant impact on application performance. The new Web Designer node type Database access options allows selecting the best load type for every use case. See the One Identity Manager Web Designer Reference Guide for this node type for more information on the different options.
It is recommended to load read-only entities first, and then convert an entity to a writable or interactive entity only when required. The new Web Designer action node type Create interactive entities can be used to convert an entity of any type into an interactive one, which can be used to set values or call customizer methods.
When calling this function on proxy objects (such as UNSGroup), in previous versions the key of the proxy entity was returned (such as <Key><T>UNSGroup</T><P>…</P></Key>).
Because this key is an artificial key that mostly cannot be used for database comparisons, the function was changed to return the key of the proxy entity instead, which will include the actual object type (such as <Key><T>ADSGroup</T><P>…</P></Key>).
The ListView control has been removed. Any ListView nodes will still be displayed in Web Designer, however the compiler will generate an error when it encounters a ListView node.
It is strongly recommended to replace any usage of the ListView control in custom web components before migrating to One Identity Manager 7.1.
© ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center