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

Loading objects that were migrated from versions prior to 6.1

Web Designer 7.0 supports loading objects that were last saved in Web Designer 6.1. However, when attempting to load an object that was last saved in a version prior to 6.1, you may see the following error message:

“The model version <X> of the object <Y> is unknown. Please verify that you are using the correct product version for your database.”

To migrate these objects, execute the following steps

  1. Open Web Designer and authenticate to the database.
  2. Select the menu item Migration assistant.
  3. In the migration assistant, there will be some items that start with "Migrate XML document". Select these items and click Run selected tasks.
  4. You are now able to load the objects in Web Designer.

Table-dependent references

Table-dependent references have been replaced by object-dependent references. This may affect all web projects that were defined in versions up to (and including) 6.1.

To create object-dependent references for these web projects, execute the following steps

  1. Open Web Designer and authenticate to the database.
  2. Select the menu item Migration assistant.
  3. In the migration assistant, there will be some items that start with "Create object-dependent references". Select these items and click Run selected tasks.

Handling compiler error messages

This section provides details about some common error messages that you may see when first compiling a web project with custom components.

Message: "The return type of the function <x> is ambiguous."

Details: All functions must have well-defined return types. In some cases, the types of the argument must also be made explicit.

Solution: Double-click the error message to select the function definition. Select the proper return data type of the function.
If the function has any arguments, define the argument type in the function signature. For example, if the function has the signature Process(inputParameter), add the argument type string. The new function signature reads: Process(string inputParameter).

Message: "There is no cursor defined on the collection <x>"

Details: In previous versions, it was allowed for cursors to be used implicitly. All cursors must now be explicitly declared.

Solution: You may see this message when you are referencing an implicit cursor below one of these node types:

  • Virtual node mapping
  • Local component
  • Function

Double-click the error message to select the node, then look for the closest parent node that corresponds to one of these node types. (Note that this can be the node itself.) Right-click the node and add a cursor declaration for the collection.

Message: "The component must implement the interface <x>."

Details: In Web Designer 8.0, components that are used as object-dependent references or column editors must explicitly implement the corresponding component interface.

Solution: Double-click the error message to select the node. Look for the "Component interface" node and select it. Assign the interface that is named in the error message.

Message: "The module <x> was not found"

Details: Some modules have been removed from the Web Portal.

Solution: Remove the reference to the module.

Message: "The function {0} is not marked as a property iteration function."

Details: Functions that are used in property iterations must be explicitly marked as such.

Solution: Double-click the error message to select the function definition. Mark the function as a property iteration function.

Changes to Web SQL functions

Changes to Web SQL functions

Related Documents