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

Removed Web SQL functions

Removed Web SQL functions

  • The function GetToXML has been removed.
  • The function Eval has been removed.

Semantic changes

The following Web SQL functions have changed their internal implementation. This may cause unexpected behavior in custom components that rely on details of the old implementation.

  • The function TranslateColumn does not recognize "%" as a place holder character anymore. This change was made to increase performance for the general case, where place holders are not required.
  • The function Concat now behaves differently when the input set is empty. In the case where the input does not contain any rows, the result is not NULL but an empty string.
  • The function GetViPrimaryKey has been removed. It is no longer necessary to handle the special case where an artificial internal primary key was created for database objects. Use the function PrimaryKey instead.

Changed features

Execution of arbitrary SQL statements

Due to security considerations, it is not recommended to execute arbitrary SQL statements from the web application layer. When the web application is installed on top of the new application server, execution of arbitrary SQL statements generates an exception.

This change affects all "Database query" type collections defined in Web Designer components.

All SQL statements must be encapsulated as "predefined SQL statements" (QBMLimitedSQL-type objects) and stored in the database. Refer to the One Identity Manager Configuration Guide for more information on how to define predefined SQL statements.

For additional security, predefined SQL statements must be assigned to permission groups. Execution of predefined SQL statements always occurs with the permissions of the user who is logged in to the web application can.

Note that WHERE clauses, as well as the WebSQL functions Exists and GetSingleProperty, are not considered "arbitrary SQL statements" and may be used as before.

Related Documents