Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 91 Next »

iteraplan 6.4

The Share Visualisation feature stopped working

This is likely a problem with Chrome/Chromium used for generating the visualisation on the server. 

Version 71 of Chrome/Chromium has a known problem, which causes the iteraplan feature to fail. As Chrome/Chromium might automatically update itself (depends on the installation and operating system), this problem might arise suddenly without any configuration changes or manual updates on the server.

Try to avoid the version 71, if possible. Version 70 and 72 should work fine.

iteraplan doesn't respond any more after creating a Date Interval attribute (fixed in 6.5)

When creating a date interval attribute it might happen that iteraplan doesn't respond after creation of the attribute. This is only the case, if the start and/or end of the date interval is configured to be dependent on a date attribute.

Workaround: Take a look at the solution described here.

iteraplan 6.3

History creates a error [object | object] in the SEV (fixed in 6.3.3)

On working on the single element view or opening the history the error [object | object ] appears.
Fix for 6.3, 6.3.1, 6.3.2: Take a look at the solution described here.

IS-2 relation for information flows not editable using the SEV (fixed in 6.3.2)

It is not possible to edit the IS-2 relation for information flow using the SEV. Workaround: edit this relation using the list view.

Attribute group permissions problems (fixed in 6.3.2)

Attribute group permissions were not working correctly when using multiple roles for one user, or when using the role inheritance.

Relation BBT permission problems (fixed in 6.3.2)

The permissions are not handled properly for relations between building blocks.

Survey can not be created with the database "Oracle" or "MS SQL" (fixed in 6.3.2)

After the update to version 6.3 it is not possible to create surveys.
Fixed: 6.3.2 contains updated migration scripts. If you already migrated the data to 6.3: take a look at the solution described here.

VISIO export not working (fixed in 6.3.1)

The VISIO export produces corrupt files when exporting any visualization except the information flow.

iteraplan 6.2

Excel Import not working when export was done in german language (fixed in 6.3.0)

If the excel export was done while the iteraplan version was set to german, the import is not working due to some "invalid status values". Export and import using the english iteraplan instead.

iteraplan 6.1

Date Interval needs an "End Date" and cannot be empty (fixed in 6.2.0)

If the "Date Interval" attribute will be edited/created it is not possible to save an empty "End Date". 

Loading of Single Element View (fixed in 6.2.0)

The Single Element View for Building Block Types which are part of the Business Mappings can only be shown if the user has read permissions for all Building Block Types that part of the Business Mappings (this means: Business Process, Business Unit, Business Function, Product, IT Service, Information System and Business Object)

Workaround: View and edit the elements in the list view.

Saved Queries List might be broken (fixed in 6.2.0)

The Saved Queries List might not load if saved queries were migrated incorrectly from a previous version of iteraplan.

Migration script needs current MySQL Server

The migration script for MySQL databases is not working for MySQL version 5.5 and 5.6, only for version 5.7.
Fixed: Solution is described in the iteraplan Knowdledge Base article 

Link to the script

Date in the excel export/import (fixed in 6.2.0)

The date contained in the excel export file is often not read correctly when importing the file again. The import process will show “(Exported: Invalid date)” after the first step. Be aware, that in this case the import will also change building blocks that were changed after the export.

Anynomous Access is not shown in GUI

 After the installation of Version 6.1 the "Anynomous Access" is default hidden in the GUI.

Workaround: Change the line "anonymous.access.UI.enabled=${anonymous.access.UI.enabled}" to "anonymous.access.UI.enabled=true" in the config file "".
The "" will be found in the path "TOMCAT\WEBAPPS\*iteraplan instance*\WEB-INF\classes"

iteraplan 6.0

Permissions and Attribte Groups (no fix neccessary)

(A previously reported bug regarding Attribute Groups and read/write permissions turned out to be an misunderstanding - there is no bug in iteraplan.)

Saved queries & changed or deleted custom attributes (fixed in 6.2.0)

If a saved query (list or visualization) relies on an custom attribute, a name change or deletion of this attribute may render the saved query unusable. The custom attribute maybe part of a filter query or part of the diagram configuration.

Copy element (fixed in 6.0.5)

Copying an element might not always work as intended. The copy functionality is affected both in the list view and the single element view. An error might be shown, even if the copy action was successful.

Adding relations in Internet Explorer 11 (fixed in 6.0.5)

In the single element view it is not possible to add a relation to an element if the element has no relations at all. The drop down field does not work in this case. This only appears in Internet Explorer 11.

Workaround 1:
Use the list view to add a new (first) relation. As soon as one relation exists with the element, other relations can be added in the single element view.

Workaround 2:
Use Chrome or Firefox instead of Internet Explorer 11.

Creating new element in Internet Explorer 11 (fixed in 6.0.5)

When using the New button in the list view to create an element, you might get stuck. The element is created, but the green line in the list view will not close.

Workaround 1:
Press F5 or navigate away from the page and back.

Workaround 2:
Use the New Element function in the single element view, not in the list view.

Workaround 3:
Use Chrome or Firefox instead of Internet Explorer 11.

Enumeration attributes with multivalue setting (fixed in 6.0.5)

Values of enumeration attributes, which are configured to have multiple values assigned, and which are put in the Top Level attribute group, might be shown multiple times in the GUI. This is only a display bug, no data corruption will occur.

Edit-Permissions for Attribute Groups (fixed in 6.0.5)

Having the view-permission but not the edit-permission for an attribute group it is still possible to edit values of contained attributes. This affects the Interactive Client (since 5.5) and the Single Element REST API (since 5.4).

iteraplan 5.5

Logout when using iteraplan in an SSO configuration

Instead of immediately being logged in again, a login screen is shown. Attempts to log in from that screen may not work.

Simply access the iteraplan base URL (for example - without additional path or parameters) to be logged in again automatically.

iteraplan 5.4

Problem with "Saved Queries" and Graphics Reactor (fixed in 5.5)

Executing a XSLT script with "Saved Queries" configured via the iteraplan Graphics Reactor is not possible with version 5.4 of iteraplan.

Error Message:
de.iteratec.iteraplan.common.error.IteraplanTechnicalException: The saved query contains illegal data or you do not possess the required permissions for all contained Buildingblocks or Attributes

New Client: Distrigation Feature in Landscape Diagram not working (fixed in 5.5)

When activating a hierarchy filter in the Landscape Diagram, the elements are correctly filtered by the level of hierarchy but the super and subelements are not distributed / aggregated (Distrigation feature).

There is currently no know workaround.

iteraplan 5.3

New Client: Filtering according to "Superordinate" or "Specialised" not working (fixed in 5.4)

When using the filter function in the New Client, filtering according to self relations to Superordinate elements (available with almost all bulding block types) or filtering according to Specialised elements (available with the Business Objects) has no effect. No error is shown.

There is currently no known workaround. 

Plugin API and History (fixed in 5.4)

Changes written to the database by plugins, using iteraplan's new plugin API, currently don't cause entries to the history data of building blocks, even if history functionality is activated.

There is currently no known workaround.

Plugin API and full text search (fixed in 5.4)

Changes written to the database by plugins, using iteraplan's new plugin API, currently don't update the search index in iteraplan. This means that after such changes the full text search may not return correct results.


  • Use the option to re-create the search index in Administration->Configuration if a full text search doesn't return expected results
  • Use the query masks in spreadsheet reports or overview pages for searching elements.

iteraplan 5.1

Oracle 12c support

When using Oracle 12c as database the bug fix / patch No. 18430870 must be applied to Oracle 12c. Without the patch iteraplan will not work correctly.

See the installation prerequesites in the Installation Guide for details about the supported configurations.

  • No labels