Additional Information

Release Notes
Known Bugs
Additional Links

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

iteraplan 6.0

Saved queries & changed or deleted custom attributes

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.

iteraplan 5.5

Logout when using iteraplan in an SSO configuration

...

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

iteraplan 5.0.5

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.

iteraplan 5

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.

Internet Explorer 11 freezes by using Nested Cluster Diagram in the interactive client. (fixed in 5.0.5)

Removing filters or coloring options in the legend of the Nested Cluster Diagram in the interactive client can cause a browser freeze if you use Internet Explorer 11.

As workaround please refresh the browser page or if possible use another browser. After refresh all configuration will remain.

iteraplan 3.4.1

Manipulating the "children" relation of building blocks using PUT requests of iteraplan's REST API can cause data inconsistencies. (fixed in 5.0)

This affects only changes done directly in the "children" field of the JSON representation using iteraplan's REST API. Changing the hierarchy using the "parent" field is safe.

Effects of the resulting data inconsistencies can be error pages when accessing the detail view of the virtual root element "-" of some building block types, as well as possible errors during import/export, nested cluster diagram, and REST requests.

This issue will be fixed in the coming iteraplan release.

Customers already affected by this issue please consult iteraplan support (iteraplan.support@iteratec.de) for help.

Consistency Check "Are there any Building Blocks of type X which do not have any association to other building blocks" reporting false positives (fixed in 5.0)

This particular check can be found on the Consistency Checks page in iteraplan as 4th in the "General Landscape" section. It may wrongly report building blocks for not having any associations to other building blocks despite the presence of such associations.

There is no known workaround.

iteraplan 3.4

Excel import cannot handle formulas in data cells (fixed in 3.4.1)

Trying to import Excel sheets with formulas in data cells lead to an error.

As Workaround replace formulas with its results.
Replace formulas with their results as follows:

  1. Select the cell or range of cells that contains the formulas.
  2. Click "Copy"
  3. Click "Paste"
  4. Click the arrow next to Paste Options, and then click Values Only

Information Flow as context visualization show error page (fixed in 3.4.1)

The context visualization Information Flow, which can be achieved over the visualization tab for the Building Block “Information Systems”, lead to an error page.

As Workaround, please use the Information Flow configuration which can find in the navigation under "Visualization > Information Flow Diagram"

Bulk Update: error page when editing relationships (fixed in 3.4.1)

If you select a relationship for an bulk update, you get on the second page of bulk update an error.

As Workaround, please use the Excel Import to update relationships instead the bulk update.

iteraplan 3.3

Excel-Export or iteraQL queries return only out-of-date results or general error pages under certain circumstances (fixed in 3.4)

One possible reason for this are user-defined attributes named like internal technical attributes, for example "ID" or "name". Other problematic names are those of the building block types in any localization, or when two attribute values of the same enumeration attribute have, case-insensitively, the same names, for example "VALUE" and "value".

Attempting to load the data model for the export and iteraQL when such names are present, currently can cause the whole loading process to get stuck and never be attempted any more. This means the data status for export and iteraQL will be frozen. If this error happens on the first load, no data will be there at all, thus causing the mentioned error pages.

A workaround is to rename problematic attributes or attribute values and then restart the tomcat-server iteraplan is running on.

iteraplan cannot be deployed with Tomcat ROOT context (fixed in 3.3.1)

Due to a bug in a third party library (JAWR), the iteraplan web application cannot be deployed with ROOT context to the Tomcat servlet engine.

Workaround: Install with a different deployment context like "iteraplan". This bug is fixed in the third party project and hence in iteraplan.