Skip to end of metadata
Go to start of metadata

Overview

With the migration to the Interactive Client not only the way changes, how lists and visualizations are configured. But the technical format of Saved Queries is different, too. Therefore Saved Queries in the Classic Client and the Interactive Client are not compatible.

Nevertheless, Saved Queries from the Classic Client can be migrated to the Interactive Client. This one-time migration is described below. This migration takes into account that there are some changes in the set of features and functionality when migrating from the Classic client to the Interactive Client.

Saved Queries in this context both refer to saved Spreadsheet Reports and saved Visualizations in the Classic Client.

Differences Classic / Interactive

See the following detailed comparisons for changes between Classic and Interactive Client:

Features, which are only present in the Classic Client but not in the Interactive Client, will not be migrated. You will be informed for each migrated Saved Query when this happens.

Additionally, please take into account the following changes in the behaviour:

 TopicBehavior in the Classic ClientBehavior in the Interactive ClientSaved Query Migration Remarks
Filtering



Last/third part of a clause
(e.g. the xxx in: Name contains xxx) -

Special case "clause already removed in the database"

When saving a query, the third part of a clause is saved. This third part might be the name of an element, the value of an enumaration attribute, etc.

Now consider the following situation: The attribute value/element has been deleted. Then the Saved Query is loaded. In this situation the clause will no longer contain the previously saved value, but will fall back to the first entry of the drop down.

The result of the filter/query will be different compared to the state before the deletion of the value/element etc. 

Whenever a value is saved in the query, it will stay. If the respective element, enumeration attribute value etc. has been deleted, the query will not change.

The result of the filter/query will nevertheless be different then before the deletion of the value/element etc., as the data in iteraplan has changed.

Filters will not be changed, only the behaviour changes
Informations Systems and Technical Components:
Filtering for Name with an operator like
is/contains/starts/ends (not)

Filtering is only done on the (base) name of the Information System or Technical Component, disregarding an potentially existent release number/string

e.g. "CRM #3.1": A filter for Name will take into account "CRM" only

Filtering is done on the (full) name of the Information System or Technical Component, including an potentially existent release number/string

e.g. "CRM #3.1": A filter for Name will take into account "CRM #3.1"

Affected Filters will be migrated as follows:

  • Name is 'X' -> (Name is 'X') OR (Name starts with 'X #')
    result set is identical
  • Name is not 'X' -> Name contains not 'X'
    result set might change
  • Name contains 'X' -> no change
    result set might change
  • Name contains not 'X' -> no change
    result set might change
  • Name ends with 'X' -> Name contains 'X'
    result set might change
  • Name starts with: not affected

Query extension,
Properties of assigned Business Mappings 

Semantics are: There exists at least one Business Mapping, which fulfills ....Semantics are unchanged 

Business Mappings:

(1) 4 clauses are presented:
Attributes of x
3*Properties of assigned y

If the first clause (Attributes of x) is used in some way, the configuration of the three other clauses is discarded.
If the first clause is not used, the other 3 clauses are considered, connected by AND.
All 4 clauses are always considered and connected by ANDConfiguration will not be changed, only the behaviour changes

Business Mappings:

(2) Properties of assigned y
<some attribute>:
no value / is not / contains not

Clause will be true, even if the respective Business Mapping endpoint (element of type y) is not part of a Busines MappingClause is always false, if the respective Business Mapping endpoint (element of type y) is not part of a Business MappingConfiguration will not be changed, only the behaviour changes
Nested Cluster DiagramShow orphan elements

For outer elements: Always enabled
For inner elements: Behavior will be toggled by the switch

For outer elements: Behavior will be toggled by the switch
For inner elements: Always disabled
Configuration will not be changed, only the behaviour changes
Landscape Diagram

Advanced settings:
Exact/strict – While aggregating relations keep exact relationships from lower hierarchy levels.

See Classic Landscape Diagram, paragraph Exact/StrictSee Landscape Diagram, Option Show partially connected

We distinguish 4 cases:

  • Business Mapping and option active:
    Option will be migrated, same behaviour as before
  • Business Mapping and option inactive:
    Option will be migrated, different behavior:
    Hierarchy aggregation (Distrigation) is always strict now, the option has no effect in this case
    In other cases (without Distrigation) the option behaves as before
  • No Business Mapping and option active:
    Option no longer available, but same behavior as before
  • No Business Mapping and option inactive:
    Option no longer available, different behavior:
    Content is always strict

Business Mapping means: Content and both axes have business mapping types assigned,
i.e. one of Information System, Busines Unit, Business Process and Product.

Configuration, where
a filter for content elements (A)
and
a hierarchy level constraint/filter with relationship aggreagtion (B)
are active at once
Elements, which do not fulfil the clause (A) and are therefore filtered out, might nevertheless be displayed in the diagram, if they fulfil the hierarchy filter settingElements, which are filtered by (A), are never displayed, regardless of a hierarchy filter and aggregation settingConfigured filters will not be changed, only the behaviour changes
ColoringNumerical attributesFor numerical attributes (not enumration attributes) a distribution into separate sections/ranges might be caluculated. E.g. this is the case when choosing coloring in the pie chart according to a numerical attribute. 
The sections/ranges are automatically calculated by an algorithm.
Ranges/Sections will also be calculated, but the algorithm has changed.
Therefore the resulting visualization might look differently.
Configuration will not be changed, only the behaviour changes

Please be aware

Because of changes in the functionality a migrated Saved Query in the Interactive Client might behave differently compared to the Classic Client. Please pay attention to the log output of the migration and check all migrated Saved Queries in the Interactive Client regarding correctness.

How to migrate

Saved Queries in the Classic Client are either Spreadsheet Reports or Visualizations. Both can be migrated to the Interactive Client. 

To access the migration, open the Classic Client and choose Migrate saved queries from the menu Visualisations. Only users with administrative priviledges in iteraplan can access the migration.

Select the Saved Queries to be migrated via the checkboxes on the right or use the Select all checkbox in the top right corner to select all Saved Queries.

The Button Migration to new client on the bottom of the page starts the migration of all selected Saved Queries. If a query with the same name already exists in the Interactive Client, the name will be appended with '(2)', '(3)' etc.

For each selected Saved Query a log output will be generated. Please review this log output carefully. You might also want to copy and save the log , because it is not kept within iteraplan and will be lost, when you navigate away from the migration page.

 

  • No labels