PREEvision

Release Notes

Version 10.6
English
Imprint

Vector Informatik GmbH

Ingersheimer Straße 24
70499 Stuttgart, Germany

Vector reserves the right to modify any information and/or data in this user documentation without notice. This documentation nor any of
its parts may be reproduced in any form or by any means without the prior written consent of Vector. To the maximum extent permitted
under law, all technical data, texts, graphics, images and their design are protected by copyright law, various international treaties and
other applicable law. Any unauthorized use may violate copyright and other applicable laws or regulations.
© Copyright 2023, Vector Informatik GmbH. Printed in Germany.
All rights reserved.
 Contents

Contents

1 PREEvision 10.6 5
1.1 Version numbers 6
1.2 Installation and compatibility information 7
1.3 New features in PREEvision 10.6 9
1.4 Fixed issues 11
1.4.1 Common 11
1.4.2 Diagrams 12
1.4.3 Tables 12
1.4.4 Requirements 13
1.4.5 AUTOSAR 14
1.4.6 Software architecture 15
1.4.7 Diagnostics 15
1.4.8 Communication 16
1.4.9 Hardware architecture 16
1.4.10 Geometry 17
1.4.11 Product line engineering 17
1.4.12 Variant management 18
1.4.13 Change and release management 18
1.4.14 Test engineering and test management 18
1.4.15 Rules 19
1.4.16 Metrics 19
1.4.17 Reports 19
1.4.18 Collaboration 20
1.4.19 Administration 20
1.4.20 License 21
1.4.21 Backup, restore, and migration 21
1.5 Known issues 22

2 PREEvision 10.5 24
2.1 Version numbers 26
2.2 Installation and compatibility information 27
2.3 New features 30
2.3.1 Requirements engineering and requirements management 30
2.3.2 Test engineering and test management 35
2.3.3 Function driven and system design 36
2.3.4 AUTOSAR system and software design 37
2.3.5 Communication design 39
2.3.6 Diagnostics design 42
2.3.7 Wiring harness design 44
2.3.8 Product line engineering 52
2.3.9 Collaboration 57
2.3.10 Usability 59
2.3.11 Administration 62
2.3.12 Configuration 63
2.4 Changes 76
2.5 Fixed issues 78
2.5.1 Common 78
2.5.2 Diagrams 83

© Vector Informatik GmbH Version 10.6 3

 Contents

2.5.3 Tables 85
2.5.4 Requirements 90
2.5.5 Logical function architecture 97
2.5.6 AUTOSAR 98
2.5.7 Software architecture 107
2.5.8 Diagnostics 111
2.5.9 Communication 114
2.5.10 Hardware architecture 123
2.5.11 Geometry 133
2.5.12 Product line engineering 134
2.5.13 Variant management 140
2.5.14 Functional safety 141
2.5.15 Change and release management 141
2.5.16 Test engineering and test management 142
2.5.17 Rules 143
2.5.18 Metrics 145
2.5.19 Reports 148
2.5.20 Collaboration 149
2.5.21 Administration 156
2.5.22 Installation 163
2.5.23 License 164
2.5.24 Backup, restore, and migration 165
2.6 Known issues 167

© Vector Informatik GmbH Version 10.6 4

 PREEvision 10.6

1 PREEvision 10.6

This chapter contains the following information:

1.1 Version numbers 6

1.2 Installation and compatibility information 7
1.3 New features in PREEvision 10.6 9
1.4 Fixed issues 11
Common 11
Diagrams 12
Tables 12
Requirements 13
AUTOSAR 14
Software architecture 15
Diagnostics 15
Communication 16
Hardware architecture 16
Geometry 17
Product line engineering 17
Variant management 18
Change and release management 18
Test engineering and test management 18
Rules 19
Metrics 19
Reports 19
Collaboration 20
Administration 20
License 21
Backup, restore, and migration 21
1.5 Known issues 22

© Vector Informatik GmbH Version 10.6 5

 PREEvision 10.6

1.1 Version numbers

Version numbers Application Version number

PREEvision client 10.6.0
PREEvision license server 3.0.0
PREEvision database server 10.6.0.02
PREEvision application server 10.6.0

Documentation Manual Version number

PREEvision manual 10.6.0
PREEvision configuration manual 10.6.0
PREEvision operating manual 10.6.0
PREEvision system requirements 10.6.0
PREEvision server API 10.6.0

© Vector Informatik GmbH Version 10.6 6

 PREEvision 10.6

1.2 Installation and compatibility information

For detailed information about the installation of PREEvision 10.6 and the migration to
PREEvision 10.6, refer to the PREEvision operating manual.

For detailed information about the hardware and software requirements of

PREEvision 10.6, refer to the PREEvision system requirements.

System requirements The following system requirements have been changed:

> It is recommended to use Apache Tomcat version 9.0.70.

Compatibility The PREEvision client, the database server and the PREEvision server are only
compatible within exactly the same PREEvision version. Using a new client version on a
previous server version or a previous client version on a new server version is not
supported and may lead to data inconsistencies or data loss.

Client version Server version Database server Metamodel change

script version ID
10.5.0 10.5.0 10.5.1.41 2022-10-05
10.6.0 10.6.0 10.6.0.02 2023-04-03

Migration and update PREEvision 9.5 and 10.0 can be migrated to PREEvision 10.6.
For the migration to PREEvision 10.6, it is recommended to update PREEvision 10.0 to
the latest version (service pack update) before creating a backup and starting the
migration.
Note the following restrictions of the different PREEvision 10.0 versions:
> PREEvision 10.0 SP13 must not be used for backup, restore, and migration because
of an issue regarding the commit information.
> The model preparation framework, which supports an incremental and final model
preparation, is available starting from PREEvision 10.0 SP6. Older PREEvision
versions use the previous preparation mechanism, which always prepares all model
versions from anew and does not persist preparation information in the database.

An update of PREEvision 10.5 to PREEvision 10.6 requires no data migration and can be
performed as minor release update.
An update of PREEvision 10.5 to a following minor release, for example,
PREEvision 10.6, requires no update of licenses. PREEvision 10.5 licenses are used for
the minor releases following PREEvision 10.5.

For an update of an existing PREEvision collaboration platform environment, all

components with a changed version number in the compatibility table must be updated,
which includes:
> PREEvision client
> PREEvision database server script
> PREEvision application on the application server
> PREEvision monitoring server
> PREEvision broker:
> PREEvision messaging server

© Vector Informatik GmbH Version 10.6 7

 PREEvision 10.6

> PREEvision staging server

> PREEvision administration server
> PREEvision SVN gateway
> optional: PREEvision API server

For detailed instructions on how to update a PREEvision collaboration platform

environment, refer to the PREEvision operating manual, chapter "Minor release
update".

© Vector Informatik GmbH Version 10.6 8

 PREEvision 10.6

1.3 New features in PREEvision 10.6

Diagnostic concept For specifying diagnostics, you can now create a diagnostic design independent of
explorer software design in early concept phases. In the next stage, the diagnostic concept can
then be implemented by different software technologies, for example, AUTOSAR Classic
or AUTOSAR Adaptive. For modeling diagnostic concepts, PREEvision 10.6 provides the
Diagnostic Concept Explorer. Here you can create and define diagnostic data like
Diagnostic Data Identifiers (DIDs) or Diagnostic Routines with additional design details
like application data types, base type requirements or initial values. Therefore, Data Type
Packages can now be created under Diagnostics.

For creating diagnostics for existing software, the existing Diagnostic Specification
Explorer has been renamed to Diagnostic Realization Explorer.

Data type mapping Since version 10.5, PREEvision can automatically create the mappings between
synthesis application data types and the corresponding platform implementation data types. This
can be done including the creation of references between mapping and implementation
data type with option Create custom Implementation Data Type.
PREEvision 10.6 offers a new option in the mapping configuration dialog relevant for
complex data types. The option Create a Reference for each Implementation Data
Type creates additional references for each sub-element of a complex data type.

KBL import and export: To support individual use cases and improve the usability for the KBL import and export,
using individual it is possible to use individual configuration files, besides the standard configuration files
configuration files for the import and export. Thus, for example, several users can work on the same model
but each of them can use an individual configuration file for the import and export.
The individual configuration files can be selected in the KBL import and KBL export
wizard.
For KBL import and export via metrics, the KBL import and export metric blocks provide
an additional port for the definition of a configuration file.
The selected configuration is applied to the import and export and is persisted during
client runtime.

© Vector Informatik GmbH Version 10.6 9

 PREEvision 10.6

KBL import and export The KBL interface supports segments containing wires and connecting nodes. These
of 3D waypoints segments may contain waypoints which describe the approximate routing of these
segments in the 3-dimensional way.
The routing path is described in the KBL artifact Center_curve. The Center_curve
contains the Control_points which reference Cartesian_points.
KBL import of waypoints:
> Control_points in KBL can be imported as 3D Way Points into PREEvision. The
import can be enabled and disabled via an importControlPoints setting in the
KBL importer.config configuration file.
KBL export of waypoints:
> 3D Way Points below a Topology Segment are exported to KBL.
> The start node of a Topology Segment in PREEvision becomes the first
Cartesian_point of the Center_curve in KBL.
> The end node of a Topology Segment in PREEvision becomes the last
Cartesian_point of the Center_curve in KBL.
> A 3D Way Point in PREEvision is treated as an intermediate Cartesian_point in
KBL.

Auto-layout diagram Auto-layout diagrams for Wiring Diagrams and Wiring System Diagrams are created in a
editing extensions special read-only view with a clear and easy-to-read layout. Editing in auto-layout
diagrams is restricted to pure layout changes, so far. The creation and deletion of
artifacts in these diagrams is prevented. Additionally, there are restrictions with respect to
the display of specific artifacts:
> Only wiring harness-specific artifacts are displayed in the auto-layout diagram.
Artifacts like documentation artifacts, sheet connectors, or conditions cannot be
displayed.
> The automatic display of cable symbols is not ensured for all Cables due to layout
limitations. In particular, symbols for the inner Cables of nested Cables are not
automatically displayed.
However, an auto-layout diagram may require manual extensions for specific kinds of
artifacts to ensure a complete export of a diagram. For this reason, the auto-layout
function has been extended in a way that specific artifacts can be created in an auto-
layout diagram.
The following artifacts can be manually added to an auto-layout diagram. The diagram
palette has been enhanced accordingly.
> Cable symbols
> Documentation artifacts
> Conditions
> Sheet connectors

© Vector Informatik GmbH Version 10.6 10

 PREEvision 10.6

1.4 Fixed issues

Fixed issues in You will find the important fixed issues in the following tables. Please note that some
PREEvision 10.6 issues depend on specific configurations, views, or models.

Further information > Common

> Diagrams
> Tables
> Requirements
> AUTOSAR
> Software architecture
> Diagnostics
> Communication
> Hardware architecture
> Geometry
> Product line engineering
> Variant management
> Change and release management
> Test engineering and test management
> Rules
> Metrics
> Reports
> Collaboration
> Administration
> License
> Backup, restore, and migration

1.4.1 Common

ID Resolution
8682711553043912061 E/E model export: The option for loading configuration
diagrams Export all included rule, metric and table
configuration diagrams has been removed.
The E/E model export now automatically loads all
configuration diagrams which are part of the selected
artifacts. This improves performance for exporting small
parts with no or only a few contained diagrams.
8682711553311962041 An artifact selected in the Model View can be switched
again to edit mode by pressing the <F2> once.
8682711554395712101 Checks have been added to avoid exceptions when
opening portlets.
8682711553679802071 In the Property View, the performance of the
Dereference action has been improved: For tables within
the Property View, a refresh is only triggered once for
multiple events instead of once per single event.

© Vector Informatik GmbH Version 10.6 11

 PREEvision 10.6

ID Resolution
8682711553543442039 It is again possible to set references on the External
Manual Links property page.
17938309342081992 In the Search dialog, the content of the User drop-down
list is correctly sorted. The wildcard * is the default
selection if the usernames are alphanumeric.
17938309315302049, In the Compare table, artifacts displayed on the two
17938309303512000 comparison sides are ordered as displayed in the Model
View.
8682711553300842108 The quick search in tables now also works in the
Compare table.
8682711553524492041 The MENU-ID in the Context Menu Blocklist
Configuration File no longer considers the revision within
the UUID of a Context Menu Metric Executor. In this way,
it is no longer necessary to change the MENU-ID after a
check-in or check-out of the Context Menu Metric
Executor.
8682711553554252036 Only Primary Editors that are set as default editor are
opened when creating an artifact via an Artifact Creation
Template. Other editors are ignored.
8682711554173803043 The LibreOffice editor no longer crashes, when selecting
more than one table cell of a text table in the LibreOffice
editor via mouse select, and then reducing the selection
to one cell and releasing the mouse button.

1.4.2 Diagrams

ID Resolution
8682711553438402036 In the Label Configuration view, the Select Object
dialog for the creation of a new object for a meta class,
provides a type-ahead search filter to filter for the proper
meta class.
8682711553354300000 LibreOffice now properly starts after using Publish
Diagram… in a server API metric.

1.4.3 Tables

ID Resolution
8682711553989382102 If an explorer configuration references Query Rules that
are missing, because of a wrong scope or deleted Query
Rule Groups, the missing rules are reported in the
Information View. When opening the explorer, a
warning is displayed.
8682711553875262105 Tables can be exported to Excel if they contain more
than eight hierarchy levels. Hierarchy levels greater than
eight are exported like level eight. Additionally, a warning
is reported in the Information View.

© Vector Informatik GmbH Version 10.6 12

 PREEvision 10.6

ID Resolution
8682711553269641914 The table scope is now properly handed over to the
toolbar action enablement metric.
8682711554379941003 Combined tables can be properly refreshed in explorers
by pressing <F5>.
17938309341102113 If a Query Rule returns duplicate artifacts, the duplicates
are filtered out if the Query Rule results are displayed in
a table.
8682711553347942105 When changing the name of an opened Table Proxy, the
tab header is updated accordingly.
8682711553460262070 When committing while table cells with formatted text are
open, placeholders are properly displayed.

1.4.4 Requirements

ID Resolution
8682711552487071783 Synchronization of Attribute Definitions and Meta
Attributes now works for formatted texts and is correctly
displayed in the Property View, in the form editor, and in
tables.
8682711554197182084 File Attachment placeholders of PDF files now always
show icons as automatic preview image.
17938311392162049 Icons for artifacts which are tagged as deleted are
available for safety requirement-related artifacts, like for
example, Safety Goal or Functional Safety Requirement.
These icons have been added to the PREEvision demo
model and the corresponding Add-Ins. The object
configuration has also been adapted accordingly.
8682711552635652105 ReqIF export: Mappings without target no longer prevent
the ReqIF export. Instead, a warning is reported in the
Information View.
8682711553515093059 ReqIF export: The REQ-IF-TOOL-ID and SOURCE-
TOOL-ID are set to the current PREEvision version.

8682711553506123059 ReqIF import: In the ReqIF Import wizard, the option for
validating the imported model has been adapted
concerning capitalization.
8682711553500302106 The Open with context menu now displays table
instances and tables templates even if the Open with
context menu is opened on an artifact that is displayed in
the incoming and outgoing links pop-up of the
Requirement Text Editor.

© Vector Informatik GmbH Version 10.6 13

 PREEvision 10.6

1.4.5 AUTOSAR

ID Resolution
8682711552994871806 AUTOSAR demo model: Broken tables in the demo
model have been removed.
8682711553353451998 AUTOSAR demo model: Runnable Entities have been
adapted to be AUTOSAR compatible.
8682711553517091998 AUTOSAR export: Pre-Build Variant Conditions are
correctly exported.
8682711552994812051, AUTOSAR export: The attribute Array Size for Literals is
8682711552915480000 now exported to AUTOSAR correctly for all relevant data
types based on the attribute Maximum Number of Axis
Points of the respective axis object.
8682711553437491002 AUTOSAR export: The AUTOSAR service instance
manifest export does not export
ServiceInstanceToPortPrototypeMappings
anymore.
8682711553501581024 AUTOSAR export: A logic has been added to keep the
IDs of SIGNAL-BASED-EVENT-ELEMENT-TO-I-
SIGNAL-TRIGGERING-MAPPING stable over multiple
AUTOSAR exports if the Event Platform Data Type
Mapping does not exist in the PREEvision model.
8682711553631860000 AUTOSAR export: The Consistency Rule
"aECUInterface_without_BusConnector" is set to error
instead of warning. A violation of this check produces a
fatal error in the AUTOSAR export.
8682711553347561998 ECU extract: Global Time Domains that are not relevant
are not exported.
8682711553437491002 AUTOSAR service instance manifest: The AUTOSAR
service instance manifest export does not export
ServiceInstanceToPortPrototypeMappings
anymore.
8682711551928661992 AUTOSAR system description: Software ports cannot be
exported without their parent software component.
Therefore, the parent must also be included in the active
variant. The consistency check "AUTOSAR Classic
Design" can be executed anywhere in the model and will
show such a modeling inconsistency.
8682711553633551913 Software cluster design description: The software cluster
design description has been corrected to only export data
type maps and data type mapping sets that are
associated with a Service Interface.
8682711553597322113 AUTOSAR import: Collections are now imported even if
they have long names.

© Vector Informatik GmbH Version 10.6 14

 PREEvision 10.6

1.4.6 Software architecture

ID Resolution
8682711554383131992 An error message in the log files of the Provided Port
Connection Editor regarding an old configuration has
been corrected.
8682711553662172052 For the class Process Design, the entry Executable on
Properties property page is now navigable.
17938307005852003 The Data Access property page of Parameter Access
has been changed:
> Runnable of Parameter Access is displayed.
> The relation Local Parameter has been renamed to
Parameter.
> The relation Shared Axis Parameter is displayed.
> The relation Sub Elements displays sub-element
reference targets of the application data type and the
implementation data type of a Shared Axis
Parameter or a local Parameter. The element for a
local Parameter will only be shown, if no Shared
Axis Parameter is set.
8682711553097541998 The description for the assignment of Parameter
Interfaces to ports has been refined in the manual.
8682711554518152051 An error in the manual in the description of service
instantiation via AUTOSAR Adaptive Explorer has been
corrected.
8682711553521272010 In the Startup Dependencies Editor, the column Kind
has been removed, the columns Option and Argument
Value have been grouped.
8682711553509361024 For the class Consumed SOME/IP Method Instance, the
attributes UDP Collection Trigger and UDP Collection
Buffer Timeout have been added to Method
Configuration property page.
8682711553632562196 The tables Fires Event Instances and Data Instance
Providing State Machines have been added to the
State Machine Integration property page of state
machine data consumer like, for example, Data
Elements, UML Properties or Signal Transmissions.
8682711551799251029 A restriction for setting initial values has been removed.
The setting of initial values is now possible without an
initial value configuration.

1.4.7 Diagnostics

ID Resolution
8682711553655412196 The consistency check
"aDiagnosticDataIdentifier_without_ReadableWriteable"
hits only DIDs without readable or writable service.

© Vector Informatik GmbH Version 10.6 15

 PREEvision 10.6

1.4.8 Communication

ID Resolution
17938309379541810 Signal router: Socket Connection Ipdu Identifiers for both
SOME/IP Events and SOME/IP Notifier Events are now
created below Socket Connection Bundles in all cases.
8682711554380232069 Signal router: The attribute Requires LdCom
Transmission is now handled correctly for signals that
are based on SOME/IP Notifier Events.
8682711554187121003 Signal router: The signal router uses existing signal
transmissions regardless of assigned signal ports, adds
missing ports, and removes obsolete ones.
8682711553303431810 Signal router: The workspace behavior of the SOA &
Ethernet Explorer including the creation of new Layout
Packages while signal routing has been corrected.
8682711553506792004 J1939 DBC import: In case Signals are part of a System
Signal, port assignments and data mappings are created
only for the System Signal.
8682711553543802159 The default behavior of port
implementsLegacyStringSerialization of the
custom metric block PDU Length Calculation has been
corrected.
8682711553644162159 The Frame-PDU synthesis now keeps existing Gateway
Routing Entries of container PDU Transmissions that are
transmitted independently over the bus.
8682711554007261029 The Frame-PDU synthesis behaves correctly if an ECU
interface of a gateway has no assigned Bus Connector.

1.4.9 Hardware architecture

ID Resolution
17938306904992083 Applying the Populate function on a logical connector in
a Network Diagram with the selected option Show
Connected Hard-Wired Connectors (With
connections), now shows all components connected to
the logical connector.
This works regardless of whether the logical connector is
contained in a Section or the diagram area.
8682711553162931913 On the Connected Connectors property page of an
Internal Bus Connector, the Internal Bus System
attribute has been implemented as link which is
navigable. Additionally, the Connected Connectors
table now properly displays the connected internal
connectors.
8682711554092301912 Defining a label configuration for the artifacts Computer
and Other Technology in a Wiring Diagram and an
Electric Circuit Diagram including their system diagrams
is enabled.

© Vector Informatik GmbH Version 10.6 16

 PREEvision 10.6

ID Resolution
8682711554028871268 Connections of documentation artifacts (comment,
information, Todo) or conditions to components in an
autolayout diagram are removed when the
documentation artifact or the condition is removed.
8682711553655612036 The wiring harness auto-layout function was not able to
process wires from Splices to the same location. Parallel
wires from a Splice and to a Splice are now supported by
the wiring harness auto-layout function.
8682711553907882062 KBL import: In the Import KBL wizard, all Custom
Attribute Profiles for KBL can be selected.
8682711552061922036 KBL export: 3D Way Points below a Topology Segment
are exported as Control_points to KBL.

8682711553092062036 KBL import and export: In the KBL import and export
wizard it is possible to use individual configuration files,
besides the standard configuration files for the import
and export. For KBL import and export via metrics, the
KBL import and export metric blocks provide an
additional port for the definition of a configuration file.

1.4.10 Geometry

ID Resolution
8682711553644161914 The refactoring Insert Branch-Off on a Topology
Segment with already routed wires can be properly
executed.
17938307855602062 The refactoring Insert Branch-Off on a Topology
Segment in a Geometry Diagram adds the created
Branch-Off to the Section or the Installation Space which
lays below the inserting position.
17938301257112081 The refactorings Insert Branch-Off and Change
Topology Segment Point to Branch-Off in a Geometry
Diagram now treat Topology Segment Points and
Topology Segment Intervals in the same way. They are
moved to the new Topology Segment according to their
offsets. Topology Segment Intervals that would start in
one segment and end in the other segment are split.
8682711553349491268 Several consistency checks have been implemented for
the Geometry layer.

1.4.11 Product line engineering

ID Resolution
8682711553577281995 During automatic integration of Assets, the automatic
naming rules are disabled for generating the parent
artifact structure.

© Vector Informatik GmbH Version 10.6 17

 PREEvision 10.6

ID Resolution
8682711553338671806 In the context of Asset integration, a warning is reported
in the Information View when canceling the action to
copy or reuse an artifact which has external relations to
invisible artifacts due to restricted user permissions.
8682711554536772046 A commit after an Asset cluster update no longer causes
incorrect "Reuses do not match" errors.
8682711554483532101 After an Asset update, the Asset external to :1 relations
in the foreign Product Line are no longer removed.
8682711554180942012 Drag and drop actions for Assets from the Version
History in the Property View to the Model View are no
longer allowed.
8682711554093942101 A reuse or copy of a Product Line from history can be
created if the Product Line contains an artifact whose
meta class has been changed via a refactoring.

1.4.12 Variant management

ID Resolution
17938307942461801 The Set Content View table is no longer cleared after
deactivating a variant.
17938306329891789 It is no longer possible to accidentally add Alternatives to
foreign Concept Templates in the Variant Diagram.
8682711553553371825 Documentation artifacts are displayed properly in
diagrams when variants are active and highlighted.

1.4.13 Change and release management

ID Resolution
8682711553028652112 The Change history no longer shows duplicate attribute
entries when an artifact or artifacts in relation are
checked-out/checked-in.
8682711554193091877 Both the Agreement Task Item and its last comment are
considered now to show the right last modification date in
the table column.
17938293806029199 An error message concerning the ReqIF Agreement
Import is now available in German and English.

1.4.14 Test engineering and test management

ID Resolution
8682711553339812102 After executing a manual test sequence synthesis, any
placeholder in the description of Test Step or Test
Procedure artifacts is still functional.

© Vector Informatik GmbH Version 10.6 18

 PREEvision 10.6

1.4.15 Rules

ID Resolution
8682711554380412077 The Consistency Rule Group "Metric-Editor" under
"Administration" | "Rules" | "ConsistencyRuleModel" |
"Product" | "L230_Verify_Model" |
"L233_Metric_Framework" | "Javabased Online Checks"
| "Metric_Editor" can again be used as an online check. It
no longer causes the deactivation of the server-side
online check framework.
8682711553678392102 The new online check "IllegalFrameworklinkOnRHS" has
been added to the rule group
"RuleConfigurationChecks". It checks if there are
creation rules using invalid framework links.
8682711553169183013 The Progress dialog reports the progress for "Updating
UI" after completing the online check calculation.
8682711553559432101 The version number of the MOF model
"Inconsistency_metamodel" is now displayed in the
correct format. The online check no longer displays the
hit "The meta model is outdated".
8682711553655992024 Client-side online checks are now properly initialized.
8682711553049121995 If a Query Rule Group is used as metric block and the
option Run as Model Operation is active, then the block
is shown in the metric diagram in a different color.

1.4.16 Metrics

ID Resolution
8682711553677672024 Source codes can now be opened after renaming the
metric and changing only letters from upper to lower case
or vice versa.
8682711553273942181 Special paste actions are no longer available for source
artifacts not adhering to the configured meta class
restrictions. The paste was allowed for a mixture of valid
and invalid source artifacts. Now, all pasted artifacts
must match the meta class restriction.

1.4.17 Reports

ID Resolution
17938311463042040 In the PREEvision demo model, erroneous placeholders
in the "Wiring Harness Comparison" report have been
updated.
8682711553438901783 Recursions in included formatted texts of placeholders
are detected during report generation and reported in the
Information View.

© Vector Informatik GmbH Version 10.6 19

 PREEvision 10.6

ID Resolution
8682711554639042025 Reports containing placeholders with Query Context
properly display the defined language.

1.4.18 Collaboration

ID Resolution
8682711552036022049 If a check-out is rejected because of invisible artifacts, a
message is reported in the Information View.
8682711553214982106 The Change history context menu entry is now disabled
if the client is in the scope definition mode.
8682711553653182034 In the Version History, the Load Revision read-only
action can be executed even if the model contains a life
cycle trigger metric.

1.4.19 Administration

ID Resolution
8682711553214862039 The dialog for deleting or initializing the authority model
no longer blocks user interface refreshes leading to a
client freeze.
8682711553089811993 Logging has been added for most REST calls belonging
to remote backup, model preparation, and migration use
cases which are started in the administration panel.
8682711553393791993 The information codes MON5004 and MON5005 have
been replaced by more precise information codes:
> MON5010 : Health Status set(<number>):
WARNING: <message>
> MON0011 : Health Status set(<number>): ERROR:
<message>
> MON0012 : Health Status set(<counter>): CRITICAL
ERROR: <message>
> MON5013 : Health Status recovered from previous
state. (State was: <message>)
> MON5014 : Health Status recovered from previous
state. (State was: <message>)
> MON5015 : Health Status recovered from previous
state. (State was: <message>)
8682711553505132076 Improved progress error message when database
memory runs out during Add-ins installation.
8682711553633321995 The Add-in propagation has been extended to include
table icons.
8682711553977682102 The Add-in propagation has been extended to include
Metric Executors of Artifact Pickers.

© Vector Informatik GmbH Version 10.6 20

 PREEvision 10.6

ID Resolution
8682711554417902011 The creation of an Add-ins delivery model is now
canceled if the Add-ins to be deployed contain Assets.
8682711554417912011 The creation of an Add-ins delivery model is now
canceled if the Add-ins to be deployed contain reuses
under the same parent.

1.4.20 License

ID Resolution
8682711552451121918 The proxy setting issue that prevented the client from
reaching the license server has been fixed.
8682711554535352051 The license selection dialog works properly even if
multiple named licenses are assigned to a user.

1.4.21 Backup, restore, and migration

ID Resolution
8682711554004691036 Restore on top is now also possible if the model
preparation has not been completed before. Model
preparation information is created if it has not been
created before when checking a delta backup entry.

© Vector Informatik GmbH Version 10.6 21

 PREEvision 10.6

1.5 Known issues

Known issues in You will find the important known issues in the following table. Please note that some
PREEvision 10.6 issues depend on specific configurations, views, or models.

ID Known issue
8682711554031661036 In rare cases, the restore fails with the following error
message:
"Error while executing model version <version>: Newly
created reuses do not match existing reuses."
Contact the Vector support for getting instructions on
how to proceed with the migration/restore.
8682711554406702203 If the PREEvision administration server is installed under
Linux, models cannot properly be initialized via the
administration panel. The initialized model does not
contain any files.
Workaround: Initialize the model via the PREEvision
client.
17938307791212069 The AUTOSAR export is interrupted if artifacts to be
exported are identified which are out of scope. The
artifacts out of scope must be added to the scope
temporarily. The export cannot be properly finished until
all required artifacts which are out of scope are added to
the scope. This means, adding artifacts to the scope
must be repeated several times until all artifacts are
added to the scope. It may be very time consuming until
the export can be finally executed.
8682711552649222003 In the import wizard for an AUTOSAR import with merge,
the aggregation of changed and deleted artifacts is not
always feasible. The filter settings for the model merge
do not always work reliably, and the selection of artifacts
in the model trees does not have an effect on the update
mechanism.
8682711554383191029 Some parts of the new feature for handling initial values
are currently located in a product Add-in. This prevents a
customizing of the feature. In case the default
configuration is not suitable for a specific project, contact
the Vector support for a workaround.
8682711554417372014 Some parts of the new feature for configuring the content
assist are currently located in a product Add-in. This
prevents a customizing of the feature. In case the default
configuration is not suitable for a specific project, contact
the Vector support for a workaround.
8682711554417442013 Some parts of the new feature for the automatic creation
of application data type to implementation data type
mapping, which is used for data types in the new Primary
Editors is currently located in a product Add-in. This
prevents a customizing of the feature. In case the default
configuration is not suitable for a specific project, contact
the Vector support for a workaround.
8682711554206562068 During Add-in installation, error messages occur due to
non-executable metrics.

© Vector Informatik GmbH Version 10.6 22

 PREEvision 10.6

ID Known issue
Workaround: To continue the installation, confirm the
error messages with [OK].
8682711554645581003 After customization of an Add-in, context relations
between successor artifacts and singleton artifacts get
lost.
Workaround: Set the necessary relations manually.
8682711554636281897 After Add-in installation, in rare cases, the client cache
may be broken.
Workaround: Close the project, clear the client cache
and reconnect.
8682711554644941202 In the Add-In Update Table, no context menu entry for
the update of a customized Add-in is available.
Workaround: Use the context menu for the customized
Add-in in the Model View.
8682711554645241202 In the Compare table, the order of the displayed artifacts
is different on the two comparison sides. The artifacts to
be compared with each other must be identified
manually.
8682711553529641783 When manually adjusting the size of a text table in the
LibreOffice editor, for example, decreasing the width of
the text table, this change in the formatted text leads to a
schema violation during ReqIF export, and the formatted
text containing the text table is not exported. If the XML
schema validation option is activated for the ReqIF
export, detailed information on the schema validation is
reported in the Information View.

© Vector Informatik GmbH Version 10.6 23

 PREEvision 10.5

2 PREEvision 10.5

This chapter contains the following information:

2.1 Version numbers 26

2.2 Installation and compatibility information 27
2.3 New features 30
Requirements engineering and requirements management 30
Test engineering and test management 35
Function driven and system design 36
AUTOSAR system and software design 37
Communication design 39
Diagnostics design 42
Wiring harness design 44
Product line engineering 52
Collaboration 57
Usability 59
Administration 62
Configuration 63
2.4 Changes 76
2.5 Fixed issues 78
Common 78
Diagrams 83
Tables 85
Requirements 90
Logical function architecture 97
AUTOSAR 98
Software architecture 107
Diagnostics 111
Communication 114
Hardware architecture 123
Geometry 133
Product line engineering 134
Variant management 140
Functional safety 141
Change and release management 141
Test engineering and test management 142
Rules 143
Metrics 145
Reports 148
Collaboration 149
Administration 156
Installation 163

© Vector Informatik GmbH Version 10.6 24

 PREEvision 10.5

License 164
Backup, restore, and migration 165
2.6 Known issues 167

© Vector Informatik GmbH Version 10.6 25

 PREEvision 10.5

2.1 Version numbers

Version numbers Application Version number

PREEvision client 10.5.0
PREEvision license server 3.0.0
PREEvision database server 10.5.1.41
PREEvision application server 10.5.0

Documentation Manual Version number

PREEvision manual 10.5.0
PREEvision configuration manual 10.5.0
PREEvision operating manual 10.5.0
PREEvision system requirements 10.5.0
PREEvision server API 10.5.0

© Vector Informatik GmbH Version 10.6 26

 PREEvision 10.5

2.2 Installation and compatibility information

For detailed information about the installation of PREEvision 10.5 and the migration to
PREEvision 10.5, refer to the PREEvision operating manual.

For detailed information about the hardware and software requirements of

PREEvision 10.5, refer to the PREEvision system requirements.

System requirements The following system requirements are changed:

> Windows 11 is now supported for the PREEvision client.
> Amazon Corretto version 11.0.15.9.1 is provided with the PREEvision client
installation. It is recommended to use this version on all server components as well.
> It is recommended to use Apache Tomcat version 9.0.62.
JVM and server settings of all PREEvision server components must be checked. The
required settings are documented in the PREEvision operating manual.
> Subversion 1.9 is no longer supported.
> The standalone license server is available in the new version 3.0.0.
> The hardware and software requirements, as well as the installation instructions of all
components have been updated.

Installation and The following changes and new features are available for the installation and operating of
operating the PREEvision collaboration platform:
> A new Collaboration Platform build is available for building server components. The
new build provides a possibility to build preconfigured Apache Tomcat instances for
all server components having already set the recommended server settings for each
component. For the messaging server it is also possible to only build the messaging
application without preconfigured Apache Tomcat.
> The deploy.properties for building server components have been reworked and
the property names have been aligned according to a consistent naming pattern.
> The parameter ModelAccessEnabled has been removed from the
deploy.properties since it is no longer needed to build the „vCollab“ application
as standalone middleware license server. The standalone middleware license server
also requires access to the model.
> The installation of the monitoring infrastructure service has been simplified.
> An audit log file is available on the application server to report and monitor security-
related actions.
> New error and information codes are available.
> New server health status bits have been introduced.

Administration server For the administration panel (vCollabAdmin), a new server component is available:
> Direct access to the application server is no longer necessary for the vCollabAdmin
web application.
> A demilitarized zone with corresponding firewall configurations is now possible.
> The administration server is deployed together with the SVN gateway on a separate
Apache Tomcat instance.

© Vector Informatik GmbH Version 10.6 27

 PREEvision 10.5

Migration For the migration to PREEvision 10.5, it is recommended to update PREEvision 10.0 to
the latest version (service pack update) before creating a backup and starting the
migration.
Note the following restrictions of the different PREEvision 10.0 versions:
> PREEvision 10.0 SP13 must not be used for backup, restore, and migration because
of an issue regarding the commit information.
> The model preparation framework, which supports an incremental and final model
preparation, is available starting from PREEvision 10.0 SP6. Older PREEvision
versions use the previous preparation mechanism, which always prepares all model
versions from anew and does not persist preparation information in the database.

Compatibility The PREEvision client, the database server and the PREEvision server are only
compatible within exactly the same PREEvision version. Using a new client version on a
previous server version or a previous client version on a new server version is not
supported and may lead to data inconsistencies or data loss.

Client version Server version Database server Metamodel change

script version ID
10.5.0 10.5.0 10.5.1.41 2022-10-05

Licenses and license For PREEvision 10.5, new licenses are required.
server
PREEvision workspace Existing workspaces from earlier PREEvision versions cannot be reused for PREEvision
and PREEvision.ini 10.5. Overwriting the PREEvision.ini is not allowed as well.

© Vector Informatik GmbH Version 10.6 28

 PREEvision 10.5

Operating system: Please use an operating system with a full character set of your language. For example,
character set to support Japanese in PREEvision, the Japanese operating system must be installed.
An English operating system with Japanese character set might not support all
characters. Therefore, this may result in displaying wrong characters in PREEvision.

© Vector Informatik GmbH Version 10.6 29

 PREEvision 10.5

2.3 New features

Further information > Requirements engineering and requirements management

> Test engineering and test management
> Function driven and system design
> AUTOSAR system and software design
> Communication design
> Diagnostics design
> Wiring harness design
> Product line engineering
> Collaboration
> Usability
> Administration
> Configuration

2.3.1 Requirements engineering and requirements management

Placeholders in Several usability and performance improvements are available for inserting and updating
formatted texts placeholders in formatted texts.
> Default placeholder attributes can be defined in the Insert Placeholder dialog (user
default) and in the Perspective Configuration (model default). If an artifact with a
default placeholder attribute is dropped on a formatted text field, the placeholder is
automatically created without displaying the Insert Placeholder dialog.

> Drag and drop of several artifacts into a formatted text field now creates multiple
placeholders. For each dropped artifact, a placeholder is created. If the dropped
artifacts are of different meta classes, the Insert Placeholder dialog offers a list of
common attributes that are available for all dropped artifacts.

© Vector Informatik GmbH Version 10.6 30

 PREEvision 10.5

> Inserting a different placeholder type in formatted texts is now possible without
switching the Insert Placeholder dialog to expert mode. The Insert Placeholder
dialog automatically preselects the corresponding placeholder type and hides the
other types. For example, if you drop a diagram into a formatted text, the Insert
Placeholder dialog, preselects the Diagram placeholder type. The Text placeholder
type is always available.

> The tooltips displayed for placeholders have been enhanced. For text placeholders,
the referenced meta class and attribute is displayed in the tooltip. File attachment
placeholders also show the file attachment information.

> When exporting a table to Excel, for example, during the ReqIF export or when
generating reports, the placeholders are now also updated before the export. This
ensures that the current values of the placeholders are transferred to Excel.
> The performance of adding placeholders in formatted text fields has been improved.
> Undo and redo in formatted texts in combination with creating or deleting
placeholders now reliably restores placeholders. This is only possible if the editor is
opened and if no PREEvision undo reverts changes applied onto the attribute with
formatted text.
Restoring placeholders with undo or redo in formatted texts resets the change-marker
as if the placeholder was inserted anew.

File attachments in When inserting files into formatted texts, instead of OLEs, placeholders to file
formatted texts attachments with previews embedded in formatted text are created.
File attachments in formatted text can be created:
> by drag and drop or copy and paste of a file from the Model View to a formatted text
field
> by drag and drop or copy and paste from the Windows Explorer to a formatted text
field
> by drag and drop or copy and paste of a file from a formatted text field to another
formatted text field
Images are integrated directly into the formatted text.
> Via multi selection, the creation of several file attachment placeholders with previews
is possible.
If a file is added to a formatted text field, the Insert Placeholder dialog opens, and the
new placeholder type File Attachment with Preview Image is selected. When inserting
the placeholder, a preview image is generated that has a reference to the file attachment.

© Vector Informatik GmbH Version 10.6 31

 PREEvision 10.5

The preview image is displayed in the formatted text at the position where the
placeholder was inserted. Under the artifact, the File Attachment and the Preview Image
are created in the model.

You may manually change and update the Preview Image via context menu on the
preview in the formatted text.

Automatic formatting of In the preferences, under PREEvision | LibreOffice you can activate to automatically
images in formatted format images when they are inserted into formatted texts in PREEvision. The default
texts properties for images are:
> anchored as character
> keep ratio and width relative to paragraph area
Additionally, you can define a default width relative to the paragraph area.

Existing images can be set to this default using a new button in the LibreOffice editor
toolbar.

Handling of files, During the ReqIF import:

images, and OLE > File attachments in formatted texts are imported as file attachments. The file
objects during ReqIF attachments are stored in the PREEvision model. The alternative PNG from the
import and export *.reqifz file is used as preview image. A preview image with a reference to the file
attachment is inserted in the formatted text.

© Vector Informatik GmbH Version 10.6 32

 PREEvision 10.5

> OLE objects in formatted texts are imported as before and can be edited in
PREEvision.
> Images in formatted texts are imported and displayed in formatted texts.
> Reimporting OLEs into PREEvision no longer distorts the preview image.
During the ReqIF export:
> File attachments in formatted texts are exported as native files and the preview image
is exported.
> Existing OLE objects in formatted texts are retained in their current form and are
exported as *.ole file embedded in an *.rtf file. The export of OLE objects
remains as in previous versions.
> Images in formatted texts can be exported as OLEs (for example, for DOORS) or as
native files.
> Diagrams are exported as PDF file attachments.
> Shapes in formatted texts are automatically converted to images. The resolution for
this conversion can be defined in the ReqIF Export wizard with the Resolution for
Shape-Conversion setting.
High resolutions lead to increased file sizes, especially when converting images to
OLEs.

Checks for the ReqIF Before exporting to ReqIF, you can execute several checks to ensure OLEs and
export placeholders within formatted texts are complete and can be correctly exported. In the
Files and Files and Formatted Text context menu the following checks are available
and can be started on Requirements and Requirement Packages:
The Check OLE objects in rich texts action now also checks:
> if an integrated OLE object can be opened on the client by checking whether a
suitable OLE-capable program can be found in the Windows Registry with which the
OLE object can be edited.
> if a contained OLE object is completely broken.
During the ReqIF export, the size of the contained OLE objects (serialized) and images is
checked, as other tools such as DOORS only support OLEs/images up to a size of
50 MB. If the size of contained OLE objects or images is greater, a warning is reported in
the Information View after the ReqIF export.
The Update rich texts action:
> refreshes all formatted texts containing an OLE object to update the OLE preview.
> checks whether integrated OLE objects can be opened.
The Search defective placeholders action reports defective placeholders in the
Information View.
In the Information View the corresponding formatted text can be opened by clicking on
the link in the Attribute column.

Defective placeholders are also reported when a report is created.

Metric blocks for ReqIF Before exporting to ReqIF, you can execute several checks to ensure OLEs and
export checks placeholders within formatted texts are complete and can be correctly exported. The
actions available in the Files and Files and Formatted Text context menu can also be
executed via metric.

© Vector Informatik GmbH Version 10.6 33

 PREEvision 10.5

Therefore, the following metric blocks are available in the Product Goals palette
category of the Metric Diagram:
> Check OLE objects in formatted texts metric block
The metric block checks for defective OLE objects, that are OLEs without a preview
image.
The metric block has been extended by the new input port "checkOLEIsOpenable".
If set to true, the block also checks whether integrated OLEs can be opened. If set
to true, a longer runtime is required because every formatted text that contains an
OLE must be opened in the background.
> Update Rich Texts metric block
The new metric block refreshes all formatted texts containing an OLE object to
update the OLE preview.
If the input port "Check OLE" is set to true, the block also checks whether integrated
OLEs can be opened (like the Check OLE objects in formatted texts metric block).
> Search defective placeholders metric block
The new metric block searches in a hierarchy of artifacts in all contained formatted
texts for defective placeholders. If the input port "postInfo" is set to true, defective
placeholders are reported in the Information View.

ReqIF import and The configuration possibilities of the ReqIF import and export have been extended to
export configuration enhance compatibility with various third-party tools (for example, DOORS next
generation).
> A new configuration flag allows to choose between using one SpecObjectType or
multiple SpecObjectTypes.
> For attribute definitions, the synchronization method can be left empty instead of
having to configure a rule that returns the source artifact.
> Attributes and custom attributes are exported for each SpecObjectType and
imported individually for each mapped PREEvision meta class. Additionally, attributes
can be exported and imported for SpecificationTypes. This allows importing and
exporting attribute values for requirement packages on specification level.
> A unified syntax in the configuration file allows a more flexible export of PREEvision-
attributes and mapping of attributes during the import.
> A new configuration flag allows to disable pretty print in the *.reqif file, enhancing
compatibility with various importing tools.
> A new configuration flag allows to export Product Goal Links having a target outside
the exported artifacts.
> Attribute definitions without data type can be exported.
> For headings, isHeading = Heading is sufficient and can be used as subclass for
attribute mappings.
> Import of test data now always requires a proper class mapping in the configuration
file.
> Identifiers for ReqIF objects are now stable.
> A new configuration flag allows to define whether images are exported as native
image file with a PNG preview or as OLE file.
> Background color in formatted texts is now exported in accordance with the ReqIF
schema. The schema validation can be configured to be stricter than the standard.
The new configuration possibilities come with a new syntax in the configuration file.
Therefore, existing configuration files must be adapted during migration to
PREEvision 10.5.

© Vector Informatik GmbH Version 10.6 34

 PREEvision 10.5

Overwrite character For Reports, the new text placeholder option Overwrite character styles of the
styles of text included text is available. If the option is activated, all character styles in the included
placeholders in reports formatted text are replaced by character styles explicitly set on the placeholder in the
Report, for example, to format all Information Requirements in italic.
All formatting except direct formatting is overwritten. Conflicts with paragraph styles or
direct formatting are resolved as defined by LibreOffice. Direct formatting has the highest
priority, then character styles, then paragraph styles.

Warning for lost A warning is displayed if moving an artifact leads to lost reuses or external relations.
relations Details are displayed in the Information View to analyze the lost relations.

2.3.2 Test engineering and test management

Alignment of test The Test Specification Editor has been further aligned with the Requirement Text
specification editor and Editor.
requirement text editor Text styles are aligned:
> Test Data Package, Test Specification, Test Heading, Test Specification Library
Shortcut actions are aligned:
> New Test Item as Child and New Test Item on Same Level
Action New Comment as Child is now also available in the Test Specification Editor.

© Vector Informatik GmbH Version 10.6 35

 PREEvision 10.5

The column Priority is added to the Test Specification Editor.

Improvements for the > A new column Test Condition Links is available.
test specification editor > The column Test Links is renamed to Test Demand Links.
> Drag and drop actions are consolidated on the following columns:
> Text
> Req/CF Links
> Test Condition Links
> Action New Test Item (on same level) is improved:
> A new Test Item is now added directly after selected Test Item instead of as last
artifact.

Further enhancements > Test Headings, Test Informations, and Test Routines can now have File Attachments.
> Responsibles can be assigned to Manual Test Cases and Automatic Test Cases.
> Manual Test Cases, Automatic Test Cases, and Test Items can be assigned to view
packages.
> Subject under Test and Device under Test can be assigned to a Test Environment.
> An online check can check whether Test Implementations have been assigned to
more than one Test Task to avoid double testing.
> A metric can check whether a Test Case Run failed in other Test Runs to avoid
duplicate creation of tickets.
> Test Items can now be created directly in the test coverage tables Test
Specification Coverage, Test Implementation Coverage, and Test Execution
Coverage.

2.3.3 Function driven and system design

Added value by PREEvision now offers Activity Diagrams.
integrated activity Behavior description:
diagrams
> The activity supports the development of complex architectures from a behavioral
perspective.
> The integrated modeling of activities enables two main use cases:

© Vector Informatik GmbH Version 10.6 36

 PREEvision 10.5

> deriving the logical architecture from activity diagrams

> modeling the detailed behavior of the decomposed system
> The combined modeling of the structural logical architecture and the corresponding
behavior enables the specification of functional requirements as a prerequisite for the
SWC code.
> Coupling of activities and State Machines: pass-through of port/data provider/
consumer from Data Instance of a State Machine to an Activity Data Instance.
> Saving as Condition or as non-parsable condition for description at an early stage via
aligned condition editor for State Machines and activity descriptions.

2.3.4 AUTOSAR system and software design

Support of AUTOSAR PREEvision 10.5 supports the AUTOSAR release 20-11. AUTOSAR files of the new
release 20-11 AUTOSAR version can both be imported or exported.

Improvements for Regarding AUTOSAR Adaptive, PREEvision 10.5 provides the following extensions and
AUTOSAR Adaptive improvements:
> The Adaptive Application, a modeling element already known in 10.0, is extended to
a Software Cluster Design, covering relevant aspects of the AUTOSAR meta class of
the same name. The AUTOSAR Adaptive Explorer supports the modeling with
multiple tables.
> The AUTOSAR Adaptive Explorer also supports Network Management Design.
> PREEvision supports Signal to Service Mappings for complex data types.

Improvements in the Editors of the SOA & Ethernet Explorer covering the design workflow steps of the service
SOA & Ethernet definition, service interface definition and service interface binding have been optimized
explorer rearranged within the explorer.
The categories covering Services and Service Interfaces are harmonized between the
AUTOSAR Adaptive Explorer and the SOA & Ethernet Explorer.

© Vector Informatik GmbH Version 10.6 37

 PREEvision 10.5

Usability of data types For the creation and definition of data types, new data type editors are introduced. The
dedicated editors for the most important application data types are based on the
Property View and provide a user guidance. The data type editors are based on the
newly introduced concept of the primary editor.

The step Implementation provides a toolbar action that creates and maps an
implementation data type (IDT) based on the corresponding application data type (ADT).
The data type editors are based on the newly introduced concept of the primary editor. To
better guide the user, configurators can create application-specific primary editors for the
configuration of artifacts of a particular meta class. Primary editors:
> can be configured to simplify the modeling in PREEvision
> are based on the Property View
> provide a navigation widget that guides through the necessary steps to create or
modify an artifact
> contain a description for every step and show only necessary attributes

Handling of initial The setting of initial and invalid values is much easier now:
values > The initial values, for example, for Sender Communication Specifications can be set
like a direct attribute.
> Further model and GUI details for the value setting can be configured in a dedicated
Value Handling Configuration.
> A new content assist supports the setting of values in fields and cells with configured
value proposals.
> Setting of an initial value in tables with content assist is possible.
> Initial and invalid values for complex data types can be set with a new dialog.
> The complex data type of the source artifact is displayed in a tree structure.
> Values can be set accordingly for the whole structure.
> The value object structure is created according to the used complex data type by a
background synthesis.

© Vector Informatik GmbH Version 10.6 38

 PREEvision 10.5

Improved port The port connector works on the logical architecture in the same way as in the software
connector architecture.

Extensions in the show/ Populate and Show/Hide Port dialog is now possible on the diagram background for the
hide port dialog following diagrams:
> Software Architecture Diagram
> Composition Type Diagram
> Partial Composition Type Diagram

The Show/Hide Port dialog for drag and drop operation via Model View has been
improved for the following diagrams:
> Software Architecture Diagram
> Composition Type Diagram
> Partial Composition Type Diagram
> Logical Architecture System Diagram
> Logical Architecture Diagram
The improvements included:
> The dialog supports multi selection.
> The dialog can be hidden with Do not show this dialog anymore option. This can
be undone via the preferences (PREEvision | Diagram | LA/ SW).

Extensions in the The Software Design Explorer, introduced with PREEvision 10.0, is further optimized.
software design This includes:
explorer > improved usability of virtual package assignment via a new category and table in the
Software Design Explorer
> modeling of Mode Switch Interfaces
> modeling of (Typed) Per Instance Memory via a new category and table
> easy navigation across categories via the selection propagation

2.3.5 Communication design

Extensions in frame The Frame PDU synthesis now supports CAN Frames containing multiplexed IPDUs. The
PDU synthesis to synthesis creates Frame Transmissions and PDU Transmissions for the multiplexed
support of multiplexed IPDUs for each Bus System.
IPDUs Gateway routing scenarios and nested combinations of IPDUs using multiplexed IPDUs
are also supported.
Further usability improvements:
> Multiplexed IPDUs can be modeled with System Signals in the Frame Layout View.
> A new table in the Communication Design Explorer displays details of multiplexed
IPDUs.

© Vector Informatik GmbH Version 10.6 39

 PREEvision 10.5

Support of adaptive A new category Network Management Design is added to the AUTOSAR Adaptive
network management Explorer. Its editors NM Configuration Editor, Partial Network Cluster Editor and
Network Management Handle Editor allow to create and configure the corresponding
elements.

To export these network management elements, a newly implemented export format

Machine Design Description Extract is available. The export can be executed on a
Computer or an Execution Context.

Support of complex In PREEvision 10.5, interface relations are replaced by Platform Interface Mappings,
signal-to-service which can map a Service Interface to fitting interfaces of the AUTOSAR Classic Platform
mappings (Client Server Interfaces, Sender Receiver Interfaces or Trigger Interfaces).
Using Platform Interface Mappings, mappings can also be created for Events and
property notifiers, which are composed from Signals resulting from several different Data
Elements.
A new category Platform Interface Mapping Design has been introduced to the
AUTOSAR Adaptive Explorer and provides detailed editors for the creation of a
Platform Interface Mapping and the necessary (complex) sub mappings.
Several Platform Interface Mappings may exist for a Service Interface covering different
mapping scenarios, for example, service to signal and SOME/IP. A Port Adapter used to
model a connection between Classic and Adaptive Software components is always based
on a single Platform Interface Mapping.

© Vector Informatik GmbH Version 10.6 40

 PREEvision 10.5

Ethernet modeling in The SOA & Ethernet modeling has been restructured according to release 19-11.
AUTOSAR 20-11 PREEvision 10.5 supports AUTOSAR release 20-11. This includes:
> easier and clearer modeling of service discovery configuration
> better support of static service discovery
> one PREEvision EEA Meta Model for both AUTOSAR approaches (4.4 or earlier and
19-11 or 20-11)
> full support in meta model, import and export, migration, Ethernet tooling (signal
router, metrics) and tables

Support of 10BASE- 10 MBit/s Ethernet physical channel (10BASE-T1S) is supported. Ethernet bus systems
T1S ethernet physical with tree structure are now possible. PREEvision provides new bus type and new bus
channel connector types as well as a table to support setup of physical layer attributes (PLCA as
bus access mechanism).

© Vector Informatik GmbH Version 10.6 41

 PREEvision 10.5

Bus connector as With PREEvision 10.5 the signal router can be influenced with a "Must use" Condition
condition for signal between Bus Connector(s) (directed) and SW Port (undirected). This allows a more
router detailed influencing of the routing behavior and enables use cases for mesh and platform
reuse.

2.3.6 Diagnostics design

Extended data Exchange of Scale Linear Verbal Table Conversions
exchange with The data exchange with CANdelaStudio now supports linear conversions. Scale Linear
CANdelaStudio via Verbal Table Conversions are often used, typically with just one linear conversion.
PVCDI format
The linear conversion part out of the overall conversion is now considered in case of:
> Linear Conversion
> Linear Verbal Table Conversion
> Scale Linear Conversion (with just one Linear Conversion)
> Scale Linear Verbal Table Conversion (with just one Linear Conversion)
The verbal table conversion parts are ignored in the exchange.

Usage of the ImEx-ID

The attribute ImEx-ID is used for different use cases:
> The ImEx-ID can represent the AUTOSAR ID.
> The ImEx-ID can represent the CANdelaStudio UUID.
The CANdelaStudio UUID is persisted in the reference product line.

© Vector Informatik GmbH Version 10.6 42

 PREEvision 10.5

The diagnostic export via PVCDI only considers the ImEx-ID out of reference product
line.

Versionless ID
The versionless ID is considered as matching criteria for the updating PVCDI import:
> The PVCDI file contains UUIDs to identify objects for the updating import (both in
PREEvision and CANdelaStudio).
> The considered ID in PVCDI files is now stable over different branches and versions.
> The updating PVCDI import is possible now, even if objects do not have the same
version anymore.

Support of multi-instantiation scenarios in data exchange

Diagnostic objects with references to different instantiations of the same port type need to
be consistent in their details:
> Details are derived from Data Elements or Client Server Interfaces.
> IO Controls, Diagnostic Data Objects and Diagnostic Routines can be applied.
Updating import detects inconsistencies since PREEvision 10.0.
PVCDI is enhanced with the information about dependencies:
> Export is writing this information.
> Import ignores it, available mechanism based on UUIDs is continued.
CANdelaStudio gets the information about dependencies and can now prevent the user
from changing any details.

New PVCDI export The diagnostic exchange now prioritizes software over logical architecture.
options

© Vector Informatik GmbH Version 10.6 43

 PREEvision 10.5

> It is possible to model diagnostics without a concrete software realization or with a

realization in logical architecture.
> If just one software realization is available, this realization is considered for the data
exchange with CANdelaStudio.

Extensions for initial The DID independent modeling of Diagnostic Data Objects by system responsibles is
DID specification steps now supported:
> Diagnostic Data Objects can be defined in dedicated packages (without DIDs as
parents).
> Diagnostic Data Object Lists provide a possibility to bundle Diagnostic Data Objects.
It is possible to define an order, required services, and assign diagnostic classes.

This concept is not relevant for PVCDI data exchange.

> Also, the Diagnostic Specification Explorer provides various new tables.

2.3.7 Wiring harness design

New wiring harness A Wiring Harness Explorer is available for schematics and wiring harness.
explorer The Wiring Harness Explorer primarily provides all tables which are required for the
specification and handling of wiring harness inline connectors, especially Wiring Harness
Multi Inline Connectors. Additionally, the explorer provides further relevant tables used in
the context of the overall wiring harness design workflow.

The Wiring Harness Explorer provides the following categories:

> Component Overview
> Schematic Connection Overview
> Wiring Connection Overview
> Header Connector Design
> Wiring Connector Design
> Plug-in Location Design
> Inline Connector Design

© Vector Informatik GmbH Version 10.6 44

 PREEvision 10.5

Classic and complex In wiring harness design, different kinds of inline connectors can be distinguished:
wiring harness inline > Wiring Harness Inline Connectors
connectors
> Wiring Harness Multi Inline Connectors

Classic wiring harness inline connector

The classic Wiring Harness Inline Connector consists of two connector sides and has
exactly one Wiring Connector for each of its connector sides.

Complex wiring harness multi inline connector

The new complex Wiring Harness Multi Inline Connector may contain more than one
Wiring Connector on each of its connector sides. The assignment of the Wire Pins to the
Wiring Connectors is represented by the Wiring Connector brackets. For Wiring Harness
Multi Inline Connectors different representations with respect to the contained number of
Wiring Connectors can be distinguished.

For the creation and specification of Wiring Harness Multi Inline Connectors, the Wiring
Harness Explorer is recommended. The explorer provides all necessary tables for
comfortably specifying the complete inline connector design, comprising the creation of
the inline connector itself, the definition of Wiring Connectors and the creation and
assignment of Schematic Pins.
The following functions have been adapted, extended, or newly implemented to support
the design and handling of complex Wiring Harness Multi Inline Connectors:
> The Show / Hide Pins dialog for pin assignment has been extended and adapted for
Wiring Harness Multi Inline Connectors.

© Vector Informatik GmbH Version 10.6 45

 PREEvision 10.5

> New pin sorting functions for Wiring Harness Multi Inline Connectors.
> Extended existing pin sorting functions for inline connectors.
> New and extended refactorings for complex Wiring Harness Multi Inline Connectors
as well as classic Wiring Harness Inline Connectors.
> New object configuration for the color of a Wiring Harness Multi Inline Connector its
Wiring Connectors.
> Implementation of various validity checks for Schematic Pins / Wire Pins.

Design of zonal New zonal architecture design for the geometry based on the zonal design of the network
architectures architecture.

> The network components grouped and clustered into network zones provide the
basis for the zonal architecture design of the vehicle geometry.

© Vector Informatik GmbH Version 10.6 46

 PREEvision 10.5

> The zonal architecture design approach groups vehicle functions according to their
location in the vehicle by dividing the overall vehicle topology into separate zones and
defining interzone connections. The zones may be modeled as outer zones
containing inner zones. Zones are represented by Installation Spaces. Installation
Spaces can have nested or inner Installation Spaces.

> The zonal architecture design describes a conceptual design for the placement of
hardware components into possible zones of the vehicle geometry.
The placement of hardware components to the different zones and zone connectors
is realized by assigning the components to the Installation Spaces and Topology
Inline Connectors via Topology Placement Conditions.

> The conceptual design of the zonal architecture can be used for deducing the later
placement of components with the help of an attribute-based mapping.

Extensions for Installation Spaces can now be modeled as nested Installation Spaces. Inner Installation
installation spaces Spaces have a different frame color in the Geometry Diagram.

Cable symbols in wiring The creation and handling of cable symbols in Wiring Diagrams has been adjusted and
diagrams improved.

© Vector Informatik GmbH Version 10.6 47

 PREEvision 10.5

> During the creation of a cable symbol, the cable symbol is automatically sized and
positioned across all Cores belonging to the Cable with one grid overlapping at the
outermost Cores or Shielding.

> When creating a cable symbol for a nested Cable, a dialog opens via which you can
determine if the cable symbol shall be created on the top Cable or a subordinate
Cable.

Limitations for automatic size and position adjustment of cable symbols:

> If a maximum distance between the Cores or Shielding of a Cable is exceeded, the
Core or Shielding is not covered by the cable symbol.
> For foreign wires or objects which are not part of a corresponding Cable, an error
highlight is displayed on the cable symbol as well as on the foreign wire. Error
highlights are reliably activated and removed and are also displayed for nested
Cables.

Further improvements:
> The deletion of a section in a Wiring Diagram without removing the content does no
longer remove the cable symbols.
> Cable symbols snap to grid while moving and changing the size.

Icons in labels External labels on all artifacts can display an icon in front of the label text:
> For each label and each condition on the label, an icon can be configured.

© Vector Informatik GmbH Version 10.6 48

 PREEvision 10.5

> Labels only consisting of icons can be defined as well.

Sheet connectors New and improved functions have been implemented for sheet connectors.
Sheet Connectors with displayed links work across different diagrams such as:
> Network Diagram
> Electric Circuit Diagram
> Wiring Diagram

Sheet connectors are customizable via object configuration Content of Sheet Connector
Link and Orientation of Sheet Connector Link with respect to:
> default orientation plus manual rotation of the link boxes
> displayed content of the sheet connector links
> default sheet connector style

Improved usability with respect to:

> navigable links
> automatic refresh of the link box content
> establishing sheet connectors in a diagram or a section:
> at a single pin or port
> while splitting a connection
> adding from the palette
> adding from the pop-up bar

© Vector Informatik GmbH Version 10.6 49

 PREEvision 10.5

For linking sections and diagrams within the Product Line, connections can be created
and visualized:
> from one diagram to another diagram
> within a diagram space and sections
> between sections

Wiring harness auto- Improved existing auto-layout functionality for Wiring Diagrams:
layout improvements > Optimization concerning the layout of the target diagrams
> Support of nested components: the uppermost component is displayed in the auto-
layout diagram

> When creating auto-layout diagrams via the Create Diagram-Based Auto-Layout
Wiring (System) Diagram and Create Model-Based Auto-Layout Wiring (System)
Diagram customized blocks, you can handle the paper format and paper settings of
the target diagram. There is the possibility to provide a set of templates with possible
section heights and a fallback mechanism to create an auto-layout with calculated
height.

Model-based wiring A read-only Wiring (System) Diagram can be created automatically, based on a part of
harness auto-layout the E/E model by using the Create Model-Based Auto-Layout Wiring (System) Diagram
metric block.
An auto-layout Wiring (System) Diagram is created based on a set of artifacts you can
define as input. The given artifacts are arranged in a clear way.

© Vector Informatik GmbH Version 10.6 50

 PREEvision 10.5

Example: Starting at a component, displaying its functional network, that is, all connected
components.

Ground point and fuse Airlines in an Electric Circuit Diagram are now displayed if Schematic Pins of the same
relay box handling logical connector kind do have the same Terminal Number types assigned.

© Vector Informatik GmbH Version 10.6 51

 PREEvision 10.5

> The Schematic Connection dialog has been improved and aligned.

> New concept artifacts for Fuse Relay Box, Schematic Pin and Schematic Connection
are available.

2.3.8 Product line engineering

Extensions for product The following product line engineering extensions and improvements are available in
line engineering PREEvision 10.5:
> Asset change cluster: calculation and Asset cluster update
> Substitution: Improvements and extensions for component substitution in wiring
harness design
> Robustness improvements
> Usability and performance improvements

Asset update The two technical terms "update context" and "revoke context" have been implemented to
improvements: revoke handle which artifacts to be displaced to which Asset after an Asset update. This means,
context and update which artifacts and relations between artifacts will be protected in the Assets if the
context updated Asset causes a conflict with other Assets.
Whether an Asset has a predecessor is important for the definition of the revoke context.
The revoke context can be different if:
> an Asset is revoked manually

© Vector Informatik GmbH Version 10.6 52

 PREEvision 10.5

> an Asset is revoked due to a conflict with an updated Asset (displacement)

The parent Asset of the revoke context is always checked-out when an artifact in the
revoke context is revoked. A checked-out artifact cannot be revoked. Checking-in an
Asset with non-integrated artifacts is prohibited.

Asset cluster When an Asset is updated, the foreign Assets that conflict with the updated Asset are
calculation and asset revoked. In some product line engineering use cases, the revoke operation or
cluster update displacement is not always necessary to handle the conflict, especially if all Assets shall
be updated simultaneously. To update multiple Assets without a revoke, the following two
extensions are implemented:
> Calculating the Asset cluster
> Performing an Asset cluster update considering a substitution use case

Improvements for The substitution is improved to support more use cases:

substitution > New meta model substitution link "substitutedOrigins--substitutedUsages" as new
substitution marker to replace the old marker "abstraction link with different
objectUUID"
> Transferring the template component to the downstream Product Line and
substituting it in the local Product Line.
> Transferring the library component to substitute to the downstream Product Line and
substituting it again in the local Product Line.
> the component in the local Product Line is substituted, and after transferring it to the
downstream Product Line again it is substituted in the downstream Product Line

© Vector Informatik GmbH Version 10.6 53

 PREEvision 10.5

The artifact from upstream to substitute is reused in the local Product Line only after
confirming the substitution.

Information output in If a reuse-out-of-sync scenario occurred during an action, for example, an Asset update
case of non- due to an error in the merge algorithm, the commit was rejected without providing
synchronous reuses detailed information.
For reuse-out-of-sync scenarios, detailed and transparent information output regarding
the affected artifacts and corresponding reference artifacts is provided, now. Additionally,
an integrated compare table for comparing the artifacts with specific representation of the
asynchronous content, is available. The information reported in the Information View has
been significantly improved, in case of illegal Asset states.

Ground point and fuse A new modeling concept in the product line engineering wiring harness workflow has
relay box handling in been implemented.
the product line > No Ground Point template will be modeled, and will not be propagated as boundary
engineering wiring to the system Asset.
harness design
workflow > The terminal number type at the Schematic Pin is used to represent a Ground Point.
> A Concept Fuse Relay Box has been implemented to support the following use case:
> n Fuse Relay Boxes realized by one library Fuse Relay Box in a specific platform

The following use cases are not supported:

> One Ground Point from an upstream Product Line substituted with n library Ground
Points

© Vector Informatik GmbH Version 10.6 54

 PREEvision 10.5

> n Fuse Relay Boxes from an upstream Product Line substituted with one library Fuse
Relay Box

Further improvements The following further improvements have been implemented.

Substitution:
> Only one template component within one System is allowed to be substituted with
one library component.
> Refactoring
Substitute With table: new column for Asset and status of the Asset.

© Vector Informatik GmbH Version 10.6 55

 PREEvision 10.5

> New column in the Review and Confirm Substitution table.

Automatic integration of Assets:

> No integration via move if a merge integration is not possible
> If no unique and mergeable integration target can be identified, a manual integration
via the Asset View is required.

External relation The External Relation Analyzer can be used to identify and resolve external relations:
analyzer > Relations to artifacts of other Product Lines
> Relations to artifacts of model layers like, for example, the global Administration, the
global Library, or the Plan layer
> Relations to artifacts out of the currently active scope
The External Relation Analyzer supports in identifying and resolving model
inconsistencies to ensure consistent model structures.

Performance Current situation:

improvements for > The activation and deactivation of a variant/set took a lot of time (for example, several
variant activation minutes, depending on the loaded artifacts).
> Different indicators were used for artifacts which are not part of the active variant
(blue exclamation mark) and for those artifacts which are excluded from the active
variant (grey exclamation mark).

© Vector Informatik GmbH Version 10.6 56

 PREEvision 10.5

PREEvision 10.5:
> The performance for the activation, deactivation, and switch of a variant/set has been
significantly improved.
> Common indicator for all artifacts which are part of the active variant (green V).

2.3.9 Collaboration
Performance A new model cache improves the performance:
improvements with new > faster loading of the model during startup of client and server because of
model cache parallelization
> faster Scope calculation and Scope delivery to the client and therefore faster initial
login

© Vector Informatik GmbH Version 10.6 57

 PREEvision 10.5

> faster shutdown of PREEvision because the model cache is always up to date

Update and commit The update cache is now stored on the hard disc:
improvements > updates are still available after server restart
> large updates which are out of scope for the user will not trigger a reload of the model
> reduced update time and less memory need for an update
> the size of update cache on the hard disc can be larger than in memory and can be
configured
Improvements for commits:
> Commits can now always be cancelled as long as writing into the data base has not
been started.
> For a large commit, a warning dialog is displayed to the user. The limits for the large
commit can be configured.

Online check Server-side online checks are now calculated in parallel and asynchronously after
calculation completing the commit, which reduces the duration of commits.
The number of available threads for the online check calculation can be configured.
The state of the online check calculation is displayed in the status bar.

© Vector Informatik GmbH Version 10.6 58

 PREEvision 10.5

2.3.10 Usability
Dashboard and entry Dashboards offer personalized entry points for users, present the artifacts that are
points relevant for the use case and provide direct access to the associated editors and
perspectives. Hence users are introduced to their use case and can focus on the relevant
artifacts without being overwhelmed by the complexity of the model and the multitude of
editors.
> Personalized entry points are set via user specific favorited artifacts.
> Directly from the Dashboard users can easily trigger metrics which open the right
editor and perspective for their artifacts.
> Dashboard Widgets can be configured to contain Charts and Tables to gain more
detailed information and insights in one look.
> The Complexity is further reduced by selecting one Product Line in the Dashboard.
The artifacts displayed in the Dashboard are limited to the selected Product Line.
> A workspace metric can be configured to automatically set workspaces for the
selected Product Line. The metric is automatically triggered upon selecting a Product
Line which reduces a common source of error, as users who are not familiar with the
workspace concept no longer need to worry about.

Checking workspaces A workspace check icon in the toolbar of every editor displays if the set workspaces
correspond with the Product Line of the artifact users are currently working on. Users can
open a Workspace Editor via click in the icon to get more information on the currently
set workspaces.

© Vector Informatik GmbH Version 10.6 59

 PREEvision 10.5

Diagram palette search Elements and artifact entries of the diagram palette can now easily be found via the
palette search function using a type-ahead filter and then directly be added to a diagram.

Diagram palette filter Elements and artifact entries of the diagram palette can now easily be filtered out from
the palette. Entries to be filtered out can be easily searched for via the type-ahead filter.
Either single artifact entries can be filtered out or even entire folders. The palette filter can
be saved to the local workspace or to the model.

Aligning artifacts in The behavior of the diagram toolbar actions for aligning artifacts has been changed. The
diagrams artifacts are now aligned to the first selected artifact instead of the last selected artifact.

© Vector Informatik GmbH Version 10.6 60

 PREEvision 10.5

Switching tables The performance of switching between Tables Proxys and Table instances via the table
toolbar has been improved. The PREEvision client remains operable, even when
switching large tables.

High DPI support in When using high-resolution monitors, the user interface of PREEvision may show an
PREEvision unwanted display behavior, for example, different font sizes in tables or diagrams. This
problem can be experienced especially when using multiple monitors where each display
has a different scale factor.
For example, the primary monitor has a scale factor equal to/higher than 175% and the
secondary monitor has a scale factor lower than 175%.
A scaling equal to/higher than 175% is set to 200%. A scaling lower than 175% is set to
100%.
If PREEvision is run on the secondary monitor (scale factor 100%), most settings are
taken over from the primary monitor (scale factor 200%). This leads to display problems
since formatted text uses the settings of the active monitor where PREEvision is run, the
secondary monitor.
During the start of the PREEvision client, the scaling settings are checked. If the used
monitors use different scaling settings, an information message is displayed.

It is recommended to adjust the scaling settings as follows:

> The monitors should use identical Windows scaling options.
> Alternatively, the monitors should use scaling options which are scaled to the same
value (either scaling lower than 175% or scaling equal to/higher than 175%).

© Vector Informatik GmbH Version 10.6 61

 PREEvision 10.5

Alternatively, a manual scaling of formatted text in tables can be defined (100% or 200%)
via a table setting in the PREEvision preferences.

Exploring the demo The PREEvision demo model now includes a Demo Model Contents table and
model perspective.
Benefits of the new perspective:
> Easy navigation to the instructive modeling and configuration examples of the demo
model
in the Model View:

> The corresponding manual entry can be opened with one click in the online help:

2.3.11 Administration
Add-ins for Add-ins cover the complete PREEvision configuration:
configuration and > Product configurations are delivered by product Add-ins.
customization
> Installed Add-ins are updated version-safe and automatically.
> Add-ins can be easily adapted and extended.

© Vector Informatik GmbH Version 10.6 62

 PREEvision 10.5

> Add-ins replace Factory Reset. From PREEvision 10.0. Factory Reset is no longer
supported.
Add-ins enable easy customization of PREEvision configurations:
> The product Add-ins, that is all Add-ins provided by the product development, are
delivered with the PREEvision client.
> To configure installations at the customers, customer Add-ins can be added.
There are two types of customer-specific Add-ins:
> dedicated customer Add-ins that are newly created
> updateable customized Add-ins derived from customer or product Add-ins

Migration from Migration preparation is significantly improved:

PREEvision 10.0 to > less storage and runtime required
10.5
> migration preparation can be done as a separate step or during backup/migration
> incremental migration preparation (resume is supported)
> enables faster migration time slot and therefore less downtime of the system

Administration package The "generic" Administration Package, which could contain configurations for various use
replaced by new cases, can no longer be created in the Administration. The following new package types
package types are available in the Administration to replace the existing Administration Packages:
> Categorization Model and Categorization Package
> Diagram Configuration Model and Diagram Configuration Package
> Hardware Classification Configuration and Hardware Classification Package
> Property Editor Configuration Model
> Uniqueness Cache Package
Existing Administration Packages shall be replaced. A metric is available to transform
existing Administration Packages into the new structure.

2.3.12 Configuration
Dashboard Dashboards are perspectives that help you to navigate as fast and easy as possible to
the data and the editors you need for your work in PREEvision.
Dashboards and their contained Dashboard Widgets can be configured according to the
customer's use case.

© Vector Informatik GmbH Version 10.6 63

 PREEvision 10.5

Primary editor To better guide the user, you can configure application-specific Primary Editors for the
configuration of artifacts of a particular Meta Class. Primary Editors are based on the
property pages presented in the generic Property View.

Custom diagram Two new configuration features are available which enable the user to focus on working
palette tools and in a diagram or table and avoid switching to other views or editors:
custom menu items > Customized diagram palette tools can be added to a diagram. It is possible to directly
call custom metrics to create new artifacts with additional information or to open the
Artifact Picker for creating new artifacts based on indirect information.
> Menu items can be opened directly from within a diagram, table, or primary editor,
other tables or can call custom metrics directly with the same source artifact to modify
content of the table.

Relations filters in the Relation Filters allow you to configure use case-specific filters for property page drop-
property view down lists. By using such filters, the origin of the entries in a drop-down list can be
narrowed down to a specific product line, library, or package, for example.

Value handling for A value handling mechanism can be configured to set initial and invalid values in the
initial and invalid values Property View like they are direct attributes. Value handling can be configured under
Administration | Property Editor Configuration Model | Value Handling Configuration
Package | Value Handling Configuration.

Content assistance for A content assist can be configured for text fields of the Property View and table cells to
text fields and cells propose valid values. The content assist can be configured under Administration |
Property Editor Configuration Model | Content Assist Configuration Package | Content
Assist Configuration.

Table configuration The Table Configuration Diagram has been improved. You may need to check and adjust
diagram the layout of existing diagrams. Column actions implemented by query or metric can now
have inputs from other columns.

Drag and drop actions The configuration of drag and drop actions in tables has been changed. For standard
in tables drag and drop actiony you can now define which actions are listed in the drag and drop
menu in tables.
Two new meta classes are available for the configuration:
> Allowed DnD Standard Action for programmed standard drag and drop actions
> Allowed Configured DnD Standard Action for configured standard drag and drop
actions
Other standard drag and drop actions are disabled in a table, if one of the new meta
classes is configured for a column of the table.

© Vector Informatik GmbH Version 10.6 64

 PREEvision 10.5

Toolbar action groups For the table toolbar, the order of Action Groups can be configured.
in tables

Configuration of If variant-sensitive Query Rule Groups are used to obtain data within tables, you must
variant-sensitive tables activate the Table Regards Variant Activation option to activate variant support in the
table configuration:
With the help of the metric Metrics | Migration Support | Migration 10.5 |
Search for Variant Sensitive Tables, you can analyze whether your tables would
require the option:

Enablement of column In previous PREEvision versions, the meta class of the source column artifact had to be
actions in tables assigned to enable column actions in tables.
Now, the meta class of the current cell must be assigned to enable column actions in
tables. This also applies for enablement metrics of column actions.
Additionally, the source port of the column action gets the cell artifact instead of the row
artifact. If needed, the row artifact can be retrieved using an additional port "rowObject".

Update of hidden table The default update behavior of hidden table columns has been changed. Hidden table
columns columns are only updated if the new option Force data acquisition if column is hidden
is activated on the hidden table column. Per default, the option is deactivated.
The new behavior has impacts on cell actions of other cells if those actions have an input
from a hidden table column. Impacts include:
> Metrics accessing data from a hidden column only get the latest/updated info from
the hidden colum/cell if the option is activated on the hidden column.
> The dereference action icon (gray x) is not displayed on a visible cell in a column, if
the corresponding deletion query has an input from a hidden column on which the
option is deactivated.

Selection propagation The automatic selection propagation can be deactivated for a table column by activating
for table columns the new option Automatic Selection Propagation. By default, the option is active.
If the option is deactivated:
> selecting a table cell no longer propagates the selection to other view, for example,
the Model View.

> the selection propagation can be executed manually via the cell action button.

© Vector Informatik GmbH Version 10.6 65

 PREEvision 10.5

Context menu Prioritized perspective elements or default editors can be displayed at the top-level in the
configuration context menu. This can be configured via perspective-specific setting and is applied to
the Open With and the New context menu. Non-prioritized artifacts are display in the
Others context menu.
The configuration possibility is available for:
> metric executors
> tables
> primary editors
> explorers
> reports

New menu The configuration files under Administration | Configuration File Container | New Menu
configuration files File Package are now managed files contained in the E/E model and must be added to
each model in which they shall be used:
> New Menu Creation Properties File
> New Menu Creation Properties Delta File
> Scratchpad New-Menu Configuration File
> Scratchpad New-Menu Configuration Delta File
> Scratchpad New-Dialog Configuration File
> Scratchpad New-Dialog Configuration Delta File

Renamed consistency/ The following views have been renamed:

online check views > The E/E Model Online Check view has been renamed to Online Check Results
> The Inconsistencies view has been renamed to Consistency Check Results

Online check handling The handling of Add-ins has been optimized with regard to online checks and consistency
during add-ins checks:
installation > Online checks can be active during installation or update of Add-ins.
> The severity of checked-in Consistency Rules can be changed.
> In the Add-ins dialog, in the Advanced settings, the new option Update
consistency and online check properties is available. If deactivated, the Add-ins
update no longer overwrites the Online Check and the Directly executable options
of a Consistency Rule Group.

Consistency rule group The new Configure Consistency Rule Groups table is available on the Consistency Rule
configuration Model and on Consistency Rule Packages.
The table provides a more convenient configuration possibility of Consistency Rule
Groups by displaying all relevant settings in one table.

Rule names must not To improve the rule execution, rule names are no longer allowed to include space
contain space characters. If existing rules have names with space characters, correct them manually.
characters

© Vector Informatik GmbH Version 10.6 66

 PREEvision 10.5

Online checks must not A Consistency Rule that is used as online check must not use a metric, except for
use metrics Consistency Rules that are used for Uniqueness Caches. The online check framework
cannot be activated if metrics are wrongly used.

Number format in The Number Format setting is no longer available in the object configuration. The
object configuration number format can be configured via tags in the Customized Label setting.

Attribute values of The meta model has been changed. The composition from AbstractAttributeOwner
attribute owner no to AbstractAttributeValue (role "ownedAttributeValues") is no longer order
longer ordered relevant.

Metric diagram palette The Metric Diagram palette has been cleaned up and restructured. Most of the metric
blocks have been renamed according to a unified naming convention. The categories in
the diagram palette have been restructured and new categories have been introduced.
You may use the new Palette Search to quickly find a metric block.

Removed metric The following utilities must no longer be used within metrics:
utilities > TableSelectionUtil
> SelectionUtil
> SelectionHelper
> CommitObjectCollector

Metrics progress The progress monitor was improved to make it possible to us sub progresses in metrics.
monitor The following methods have been removed:
> createSubTask()
> workSubTask()
> getProgressMonitor()
Instead, the following methods can be used:
> createChildProgress()
> createChildProgressWithDelay()
Example:
IProgressMonitor progressMonitor = createChildProgress();
//beginTask(<NameOfTheTask.String>,<Steps.Int>)
progressMonitor.beginTask(sendingChangeRequestMessage(), 50);
// Set progress counter worked(<Step.Int>)
progressMonitor.worked(5);
progressMonitor.done();

Removed library The library org.joda.time has been removed and should be replaced in metrics by
java.time.

External JAR files External JAR Files are now managed files contained in the E/E model and must be added
to each model in which they shall be used.

Pre commit hook metric The Pre Check-in Hook Metric Executor is deprecated and can no longer be created.
executor Existing Pre Check-in Hook Metric Executor are not executed and must be manually
migrated to Pre Commit Hook Metric Executors.

© Vector Informatik GmbH Version 10.6 67

 PREEvision 10.5

Therefore, the Pre Commit Hook Metric Executor is now executed on commit and on
check-in. When implementing the metric, create two Model Contexts to distinguish
between a commit or check-in:
> Model Context "ArtifactsToCommit"
> Model Context "ArtifactsToCheckin"

It is recommended to activate the Consistency Rule Group "Product" |

"L310_Administration" | "316_Add-ins" | "ConfigurationChecks" | "Metrics" |
"MetricConfigurationOnlineChecks" as online check to check the configuration of the
hook metric executors.

Label metric executor Metric-based labels must only be configured via the Label Metric Executor. Other metric
executors are no longer supported. Existing metric executors can be refactored via the
context menu Refactoring | Typechange to Label Metric Executor.

Displaying hyperlinks in Metrics that are used to display hyperlinks in tables must use the new class
tables aquintos.generictable.renders.hyperlink.ProtocolBasedHyperlink
to create the hyperlink.
Example:
new ProtocolBasedHyperlink(externalLink.getExternalLink(),
externalLink.getName());

New metric blocks In the Common palette category of the Metric Diagram, the following new metric blocks
are available for handling workspaces:
> Get Workspace metric block
> Get Workspace Categories metric block
> Set Workspace metric block
> Reset Workspace metric block

In the Tables palette category of the Metric Diagram, the Open Editor in Area metric
block is available. The block opens an editor in a defined client area. For example, a table
can be opened directly below the currently opened diagram.
The Open Editor in Area metric block can be used to open the following editors:
> tables
> explorers
> charts
> primary editors
> form editors
Optionally, the editor can be opened together with a perspective.

Changed metric blocks The Consistency Rule Group metric block has a new optional input port
"postResultToInconsistencyView".
If set to true, the consistency check results are posted in the Consistency Check
Results view.

© Vector Informatik GmbH Version 10.6 68

 PREEvision 10.5

The Check OLE objects in formatted texts metric block has a new input port
"checkOLEIsOpenable".
If set to true, the block also checks whether integrated OLEs can be opened. If set to
true, a longer runtime is required because every formatted text that contains an OLE
must be opened in the background.

The following metric blocks have new or changed ports:

> Signal Router metric block
> Create Diagram-Based Auto-Layout Wiring (System) Diagram metric block
> Create Wiring System Diagram metric block
> Create Wiring Diagram metric block
> KBL Import Transformation metric block
> KBL Reader metric block
> Finish Asset Update After Substitution metric block
> Asset Update with Embedded Substitution metric block
> Asset Variant Extractor metric block
> Establish Abstraction After Shaped Replace metric block
> AUTOSAR Export metric block
> Add-ins Install/Update metric block
> Replace metric block
> Artifacts Touched by Replace metric block

The following metric blocks have been renamed:

Old name New name New category

Loop Block Loop Components
ReqIF Export Block ReqIF Export Product Goals
ReqIF Export Identification ReqIF Export Identification Product Goals
TestRoutines Test Routines
ReqIF Export TestRoutines ReqIF Export Test Routines Product Goals
ReqIF REQ-LA-Mapping ReqIF REQ-LA-Mapping Product Goals
targets Targets Export Extension
ReqIF Specific Export ReqIF Model Based Product Goals
Specification Export
ReqIF Writer Block ReqIF File Writer Product Goals
ReqIF Identity Detector ReqIF Identity Function Product Goals
Block
ReqIF Import Block ReqIF Import Product Goals
ReqIF Import TestRoutines ReqIF Import Test Routines Product Goals
ReqIF Reader Block ReqIF File Reader Product Goals
RIF Import Block RIF Import Product Goals
LA Delegate Contained Logical Architecture Logical Architecture
Open Ports Contained Open Ports
Delegator

© Vector Informatik GmbH Version 10.6 69

 PREEvision 10.5

Old name New name New category

LA DelegatePorts Logical Architecture Ports Logical Architecture
Delegator
AUTOSAR (Source defines AUTOSAR Identity Software Architecture
ImExId matching) Identity Function (Source defines
Function ImExId matching)
AUTOSAR Import/Update AUTOSAR Deletion Software Architecture
Deletion Function Function
(Re)Assign Mapped Mapped Implementation Software Architecture
Implementation Data Types Data Types Assignment
SWA Delegate Contained Software Architecture Software Architecture
Open Ports Contained Open Ports
Delegator
SWA Delegate Ports Software Architecture Ports Software Architecture
Delegator
Create/Update SOMEIP SOME/IP Interface Software Architecture
interface deployment Deployment Synthesis
Arrange IPDUs Arrange PDUs Communication
AUTOSAR Export Block AUTOSAR Export Communication
AUTOSAR Identity AUTOSAR Identity Communication
Function Function
AUTOSAR Import Block AUTOSAR Import Communication
AUTOSAR Import with AUTOSAR Import with Communication
Merge Block Merge
AUTOSAR Reader AUTOSAR Reader Communication
AUTOSAR SW Component AUTOSAR Software Communication
Update Component Update
AUTOSAR Transformer AUTOSAR Import Communication
Transformation
Communication Path Communication Path Communication
Router Router
COM-Synthesis Communication Synthesis Communication
Convert To Enumeration AUTOSAR Import Communication
Application Enumeration
Converter
Com Lengthcalculation Communication Length Communication
Create / Update SOMEIP/ SOME/IP Transport Communication
TP Synthesis Protocol Synthesis
Create Network Synthesize Network Communication
Management for Cluster Management for Cluster
Create PDU-Transmission PDU Transmission Communication
Structure Structure Synthesis

© Vector Informatik GmbH Version 10.6 70

 PREEvision 10.5

Old name New name New category

Dereference Secured IPDU Dereference Secured IPDU Communication
from IPDU from IPDU
DBC Export Block DBC Export Communication
DBC Import Block DBC Import Communication
FIBEX Export Block FIBEX Export Communication
FIBEX Import Block FIBEX Import Communication
LIN (LDF) Export Block LDF Export Communication
LIN (LDF) Import Block LDF Import Communication
Manual Communication Manual Communication Communication
Router Router
Service Instances Creator Create Service Instances Communication
Frame DLC Calculation Calculate Frame Data Communication
Length Code (DLC)
Dissolve PDU FanInFanOut PDU Fan-In/Fan-Out Communication
Dissolver
FUP-Export-Transformation FUP Export Transformation Communication
FUP Export Writer FUP Writer Communication
FUP Import Identity FUP Identity Function Communication
Function
FUP Import Reader FUP Reader Communication
FUP Import Transformation FUP Import Transformation Communication
PlmXml Document Creator PLM XML Document Communication
Creator
Software Library Relevance Software Library Relevance Communication
Function Function
FlexRay Scheduling Core FlexRay Scheduling Communication
Reference Secured IPDU to Reference Secured IPDU Communication
IPDU to IPDU
Diagnostic DefinitionSet Diagnostic Definition Set Diagnostics
Assignment and Creation of Assignment and Creation of
Attribute Profiles Attribute Profiles
Diagnostic Lib Identification Diagnostic Library Diagnostics
Function Identification Function
Diagnostic Library Creator Diagnostics
Diagnostic PL Selection Diagnostic Product Line Diagnostics
Selection
Diagnostic Ref Identification Diagnostic Reference Diagnostics
Function Identification Function

© Vector Informatik GmbH Version 10.6 71

 PREEvision 10.5

Old name New name New category

Compare PVCDI with ECU PVCDI with ECU Extract Diagnostics
extract Comparison
Nested Values Presenter Record/Array to String Diagnostics
Converter
Execute Circuit Synthesis Circuit Synthesis Electrologic and Harness
Optimization Manager Splice Optimization Electrologic and Harness
Block
KBL Export Block KBL Export Electrologic and Harness
KBL Import Block KBL Import Electrologic and Harness
Create Standard Catalogue Create Splice or Inline Electrologic and Harness
Connector
Wiring Autolayout Diagram Create Diagram-Based Electrologic and Harness
Auto-Layout Wiring
(System) Diagram
Change Variants Block Change Variants Variant Management
Variant Propagation Block Variant Propagation Variant Management
Artifact Substitute plus Artifact Substitute Plus Product Line Engineering
Asset Factory Asset Factory
Asset Analysis for Asset Integration Model Product Line Engineering
Automatic Integration Calculator
Asset Delete with Clean Up Asset Delete With Clean Product Line Engineering
Up
Asset Update and Reattach Finish Asset Update After Product Line Engineering
continue Substitution
Asset update with Asset Update With Product Line Engineering
embedded substitution Embedded Substitution
Autointegrate Asset Asset Automatic Integration Product Line Engineering
Automatic Reattach for Automatic Substitution if Product Line Engineering
Non-Conflict Non-Conflict
Compare and Reattach Review and Confirm Product Line Engineering
Substitution
Create Replace Create Replace Product Line Engineering
Configuration for Compare Configuration for
and Reattach Substitution Table
Create replace Create Replace Product Line Engineering
configuration for compare Configuration for Compare
table Table
Execute Analysis based Asset Integration Model Product Line Engineering
Asset Integration Integrator
Get Assets from upstream Get Assets From Upstream Product Line Engineering
to convert foreign relation To Convert Foreign
Relation

© Vector Informatik GmbH Version 10.6 72

 PREEvision 10.5

Old name New name New category

Integrate Integrate Artifact via Asset Product Line Engineering
Reuse
Preparation for second Prepare Boundary Artifact Product Line Engineering
reattach of boundary in L2 for Added Substitution
Root Finder Search Outermost Parent Product Line Engineering
Artifact
Transfer external relations Transfer External Relations Product Line Engineering
of Artifact
Unintegrate Asset Revoke Asset Product Line Engineering
Use Asset Use Asset Product Line Engineering
Add artifact to Set/System Add Artifact to Set/System Product Line Engineering
Compare Table Export Compare Table Export Change Management
Block
Compare Artifacts Artifact Comparision Change Management
Create OEM Agreement OEM Agreement Task Change Management
Task Items Items Creator
Requirement Coverage Requirement and Test Test Engineering
Specification Coverage
Check-In Block Check-In Collaboration
Commit Block Commit Collaboration
API Server Calculation API Server Calculation Collaboration
Block
Delegator Calculation Block Delegate Calculation Collaboration
Server Calculation Block Server Calculation Collaboration
ModelContext Migration Model Context Migration Administration
Placeholder Cleanup Block Cleanup Placeholder Administration
Add-ins Delivery Export Add-ins Delivery Administration
Add-ins Install/Update Add-ins Installation/Update Administration
Customize Add-ins Add-ins Customizing Administration
Prepare Customizing Add-ins Customizing Administration
Preparation
Propagate Add-in Block Propagate Add-in Content Administration
Enumeration Result Block Enumeration Result Common
Evaluation Hub Block Evaluation Hub Common
Lights Block Lights Common
Scale Block Scale Common
Sort and Filter Block Sort and Filter Common

© Vector Informatik GmbH Version 10.6 73

 PREEvision 10.5

Old name New name New category

Validator Block Validate Common
CSV Export Block CSV Export Common
Excel Export Excel Export Common
CSV Import Block CSV Import Common
Excel Import Block Excel Import Common
Application Context Block Application Context Common
Artifact Creation Template Artifact Creation Template Common
Instantiation Creator
Code Generator Block Code Generator Common
Collector Block Flat List Common
Compare Product Lines Product Lines Comparison Common
Consistency Check Online Check Findings Common
Findings Collector Collector for Quick Fix View
Create Outermost Package TempModel Creation Common
Directory Chooser Open Directory Dialog Common
File Chooser Open File Dialog Common
File Chooser Export Save File Dialog Common
Finde Relation Search relation of virtual Common
Folder
List Block List Common
Load all Rich Texts Load rich texts Common
Metrik executing Block Metrik executing Common
Model Connection Block Model Connection Common
Naming Convention Attribute Convention Common
Velocity Template Block Velocity Template Common
VerbalTable2TempTableBl Verbal Table to TempTable Common
ock Converter
Assert Block Configuration Test Assert Configuration Test
Compare Model Tree Model Tree Comparison Configuration Test
CSV Compare CSV Comparison Configuration Test
Stimulus Container Block Stimulus Container Configuration Test
Table2CSV Table to CSV Converter Configuration Test
Compare Table to Table to Reference Configuration Test
Reference Comparison
Create Table Reference Table Reference Creator Configuration Test

© Vector Informatik GmbH Version 10.6 74

 PREEvision 10.5

Old name New name New category

Debug Rule Open Rule Debugger Configuration Test
JUnitRunner Block JUnitRunner Configuration Test
Write Table Reference Table Reference Writer Configuration Test
Diagram Artifacts Block Diagram Artifacts Collector Diagrams
Change Diagram Diagram Configuration Diagrams
Configuration Block Changer
Create Datasource Data Source Creator for Diagrams
Calculated Labels
Diagram Publish Block Publish Diagram Diagrams
Diagram Render Block Render Diagram Diagrams
Labels in diagrams (reset) Reset Labels in Diagrams Diagrams
Labels in diagrams (update) Update Labels in Diagram Diagrams
Remove graphical Remove Graphical Diagrams
representation Representation
Chart Block Chart Reports and Charts
Chart Property Block Chart Properties Reports and Charts
Chart Renderer Block Chart Renderer Reports and Charts
Chart Report Block Chart Report Reports and Charts
Report Result Block Report Result Reports and Charts
Model Object Extractor Table Selection List Tables
Table Export Block Table Export Tables
Open Table Editor Open Table Tables
Table Render Block Publish Table Tables

Removed metric blocks The following metric blocks are no longer available:
> Delete Artifact if no relevance to asset
> Asset Update and Reattach
> Set abstraction relation
> Compare and Reattach Post Processing
> Update from Predeccesor
> Update from Predeccesor (multi)
> ID Control Function AGR
> Product Lines Comparison, use the block Compare Model Tree instead

© Vector Informatik GmbH Version 10.6 75

 PREEvision 10.5

2.4 Changes

Deprecated features The following features are no longer supported by PREEvision 10.5:

BTV View
> This undocumented feature is used in a few customer projects.
> The complete configuration possibilities are removed.
> Similar use cases can be implemented with the new primary editor in PREEvision
10.5.

RIF import and export

> RIF is an outdated method and procedure to transfer requirements.
> RIF is completely replaced by ReqIF.
> The complete functionality is no more available with PREEvision 10.5.

OLE in attributes with formatted text (such as description fields)

> The insertion of OLE files into formatted text attributes is removed and existing OLEs
are longer be maintained.
> The complete functionality is no more available with PREEvision 10.5.
> Instead of OLE files, embedded files with previews must be used.
> The ReqIF import and export are still supporting OLEs.

Several PLE custom metric blocks

The following blocks are no more available with PREEvision 10.5 and 10.0:
> set abstraction relation (ID: SetAbstractionRelationID)
> asset update and reattach (ID: UpdateReattachedAsset.ID)
> delete artifact if not in asset (ID: ReattachDeleteObsoleteArtefactsID )
> compare and reattach post processing (ID: ReattachPostProcessingID)

Multiplexed IPDU Viewer

> The table Multiplexed IPDU Viewer is replaced by the table Multiplexed IPDU
Overview in the PREEvision Communication Design Explorer.

J1939 library use case

> The metrics for the J1939 library use case are not supported anymore and are
removed with PREEvision 10.5.

Name correction algorithm after creation of AUTOSAR artifacts

> An outdated name correction algorithm that runs after creation of AUTOSAR related
artifacts will be removed. This algorithm is redundant to the SHORT-NAME correction
algorithm that is applied on the AUTOSAR export. The algorithm at the export side
completely replaces the other one offering a better performance and completeness.

Some concepts for AUTOSAR Adaptive modeling

> Several references and attributes are removed or replaced following the changes in
the AUTOSAR Adaptive release R20-11.
> Notably, the Adaptive Application is replaced by the Software Cluster.

© Vector Informatik GmbH Version 10.6 76

 PREEvision 10.5

Some concepts for modeling of combined systems

> Interface relations, used to connect elements of Service Interfaces and interfaces of
the AUTOSAR Classic platform are replaced by dedicated platform interface
mappings of the same purpose.
> This transformation is supported by the migration.

© Vector Informatik GmbH Version 10.6 77

 PREEvision 10.5

2.5 Fixed issues

Fixed issues in You will find the important fixed issues in the following tables. Please note that some
PREEvision 10.5 issues depend on specific configurations, views, or models.

Further information > Common

> Diagrams
> Tables
> Requirements
> Logical function architecture
> AUTOSAR
> Software architecture
> Diagnostics
> Communication
> Hardware architecture
> Geometry
> Product line engineering
> Variant management
> Functional safety
> Change and release management
> Test engineering and test management
> Rules
> Metrics
> Reports
> Collaboration
> Administration
> Installation
> License
> Backup, restore, and migration

2.5.1 Common

ID Resolution
17938308307242099 The form editor now refreshes after editing, for example,
in the Property View or the Model View.
17938307793732203 The language of the PREEvision client has been preset
to English (United States).
17938308060401036 The information on failed E/E model exports has been
improved.
17938309199152050 If the display of the Graphics Device Interface (GDI)
information in the status bar has been deactivated on the
client, this setting is retained: changing the perspective
does not reactivate the display.

© Vector Informatik GmbH Version 10.6 78

 PREEvision 10.5

ID Resolution
17938308865552101 A more descriptive text has been added to the progress
bar that appears after clicking the Finish button in the
New Project wizard.
17938308756822034 If the user attempts to add a selection of artifacts to a Set
that already contains some of the selected artifacts, the
artifacts not already included in the Set are added to it.
8682711552963422106 The start of LibreOffice shows and information if it fails
and, in general, is faster.
8682711553262941791 Inconsistencies in the PREEvision demo model have
been fixed.
8682711553509512041 Correct MENU-ID ouput in the Status view by using
<Alt>+<Ctrl>+<F6>.

Property view ID Resolution

12113 The client problem (client freeze) which was caused by
an infinite loop in the Property View has been resolved,
and the client performance improved.
8682711552409011037 Property pages with dynamic entries are shown again
after being filtered out.
8682711552928032034 When clicking on an empty space within a Property
View table, the Artifact Picker is opened on the
"Content from Property View" page. This resolves the
problem of a wrongly loaded Artifact Picker.
17938309365222052 In the Property View, sporadic problems with drag and
drop actions have been resolved.
17938308840042051 During a drag and drop action of an artifact from the
Model View or Artifact Picker into an already selected
property page, the selected target property page remains
active.
8682711551922932105 When selecting multiple artifacts in a Property View
table via <Shift> + arrow key, all selected artifacts are
also selected int he Model View.
17938308224841875 When changing the selection in the Property View, the
selection change is properly propagated to the Model
View.
17938305558022039, When using the Locale en_GB in the PREEvision.ini,
8682711552764792039 the formatting of dates in the Property View now works
according to the current Unicode standard of Java 11.
For the Locale en_GB, the date now also uses 4-digit
years.
Entering years is only allowed with 4-digit notation and
entering dates before 1.1.1970 is no longer possible.
17938309118222092 To allow specification of the package type, a Package
Type field has been added to the General property
pages of the Customer Feature Package, Variant
Package, Asset Package, and Layout Package artifacts.

© Vector Informatik GmbH Version 10.6 79

 PREEvision 10.5

ID Resolution
8682711551998992045 In the Property View, the correct value of Light Weight
String Attributes is displayed, with leading zero, if
defined.
8682711552948732050 A configured Generic Table Artifact Picker that displays
Diagram Configurations can be opened from the
Property View without displaying an error.
17938308145971032 A verification has been implemented in the Property
View for the Table Value artifact class, which ensures
that only integer type values can be entered for the X-
Index and Y-Index attributes.
17938311517902108 A problem with displaying property pages that occurred
on Application Axis Types has been resolved.

Model view ID Resolution

17938307534153017 File attachments are correctly displayed in the Model
View.
17938307564392001 The performance has been improved, when working with
a pinned Model View.
17938309315242101 The selection of artifacts in the Search result view is
propagated to the Model View.
8682711552288902099 If the Model View is pinned, the automatic navigation
and selection propagation is suppressed even on drag
and drop actions.
8682711553334332111 When opening a new Model View instance, the new
Model View is opened expanded up to the selected
artifact on which it has been opened. The new Model
View opens next to the Property View so that both
Model Views are visible.
17938311467381204 In a large-scale tree, the selection of an artifact is kept
after a drag and drop.
17938311467391204 In a large-scale tree, the selection of an artifact is kept
after a drag-and-drop, even if the tree has been partially
collapsed.
17938311473392049 Large-scale trees are now displayed below diagrams,
containers, or packages to improve the usability for
artifact navigation.
8682711552406681806 Ordering in large-scale trees uses the label instead of the
artifact names.

Context menu ID Resolution

17938307499612070 For artifacts with virtual folders containing many artifacts
(more than 1000 artifacts), all relevant context menu
entries are available now.

© Vector Informatik GmbH Version 10.6 80

 PREEvision 10.5

ID Resolution
17938307669632106 The special paste action Paste as copy without
external relations is now only available if the exact meta
class of the source artifact is copyable. In particular, this
prevents unintended copying of diagrams below
Requirements.
17938299596052090 Since the meta class Naming Convention was renamed
to Attribute Convention, the icon of the Attribute
Convention has been changed. In the Refactoring
context menu, the, entries have been renamed to Apply
Attribute Conventions.
17938307799872111 Submenu entries are no longer displayed twice in context
menus.
17938311319481030 Submenus in the context menu are properly displayed.
8682711552342101995 The New context menu no longer displays duplicate
entries for creating Conditions.
17938308936151037 Prioritized tables and explorers of a perspective are
correctly displayed in the context menu.
17938311600272049 All types of metric executors that are not prioritized for a
perspective are displayed in the Others context menu.

Information view ID Resolution

8682711551930992102 The preferences for setting the maximum number of
entries in the Information View are saved and applied
after a new client start.
8682711553067011992 The content of the Information View is now properly
exported to Excel, even if the Information View results
are reported via a metric.
8682711553095012111 The selection propagation from the Information View to
the Model View works correctly.
8682711553114182159 When the Clear contents action is executed in the
Information View, all contents on both sides of the view
are removed.

Object and label ID Resolution

configuration
17938307380242112 Switching the Positioning of a label in the Label
Configuration view between midpointlable,
endpointlabel, or embeddedlabel is now possible without
losing the information of the label being a calculated
label.
17938307443012111 Change markers are now correctly updated for localized
attributes. Object configurations are properly displayed in
tables.

© Vector Informatik GmbH Version 10.6 81

 PREEvision 10.5

ID Resolution
17938307513201031 Object configuration artifacts are now displayed in the
Model View if the corresponding parameters in the
PREEvision.ini file are set.

17938308952172081 In the Label Configuration view, the drop-down list for

choosing a Query Rule Group now provides auto-
completion. The entry "default" is displayed as first entry
and is initially selected.
8682711552995261918 For an enablement of an embedded name label
configuration, embedded name labels must exists and
therefore, this is no longer offered in the Object or label
configuration dialog. To change external labels, use the
Label Configuration view, instead.
17938311658381030 When working in multi-user mode, images can be
replaced in the object configuration.

Comparison and merge ID Resolution

17938307767972042 When merging artifacts, artifacts of different meta
classes are not merged in case that only their names
match. The artifact merge does not change the meta
class of an artifact and does not consider the Alias
Name.
17938309314692049 When configuring the artifact comparison and filtering all
relations of an artifact, all relations of an artifact are
filtered – including the relations to its children. This
setting is configured per meta class.
17938309315242049 The default colors for displaying comparison results in
the Property View, have been changed and can be
defined in the Preferences.
8682711551964921914 After an artifact merge of reused artifacts, the commit
works correctly.
8682711552271132101 The Model merge wizard always displays zero artifacts
to be deleted if no reference model is selected.
8682711552593571999 When comparing artifacts/models, the Show equal
option can be activated to display all relations and
attributes of the comparison sides even if they are equal.
17938311439532050 Comparing creation times no longer causes a
NullPointerException.

© Vector Informatik GmbH Version 10.6 82

 PREEvision 10.5

2.5.2 Diagrams

ID Resolution
24491912 When renaming an artifact in a diagram, for example via
the shortcut <F2>, labels which are invisible due to
constraints in the label configuration are ignored. As a
result, the text control for editing is always open for one
visible label with the corresponding label formatting.
17938308756452034 The text of a Title Block now scales with the Windows
scaling.
17938308756832034 Zooming no longer cuts off strings in diagrams. The text
is now scaled proportionally.
17938309359252041 The fan waypoints are now moved correctly again when
two pins are swapped to avoid overlapping routing
results.
17938308053831992 The duration of the multiselect option in diagrams has
been improved.
17938311660752041 The context menu entry Open all Diagrams on an
artifact works properly again.
8682711552491832041 The text in comment fields now ignores HTML tags and
shows the text as it was entered.
8682711552055372039 Sections are now ignored by the variant highlight.
8682711553188042041 The calculation of the modifiable state of the Software
Architecture Diagram and other projected diagrams has
been corrected. If a diagram contains invisible artifacts,
the red frame around the diagram is now correctly
displayed.
8682711552500331995 Trying to add a composition to a type diagram now
reports the correct error in the Information View instead
of displaying a black box.
8682711552714812081 During automatic creation of a diagram via metric, all
required connections on ports are created, including bus
connections with more than two ends.
17938308850881861 Checks have been added to prevent an
IndexOutOfBoundsException in diagrams.

8682711551958071030 Formatted texts of Comment and Information artifacts are

available again in diagrams.
8682711553067840000 The performance of calculating or displaying the severity
of online checks has been improved when opening a
diagram. Online check icons are only refreshed if the
status of the severity changes.
8682711553369973071 The tooltip of the alignment actions in all diagrams now
contains the information that the first selected artifact is
used as reference.
8682711553547742041 Labels in diagrams do no longer draw an unintended
white background.

© Vector Informatik GmbH Version 10.6 83

 PREEvision 10.5

ID Resolution
17938309408412046 The new line tag </n> for labels can be used in metrics
to create a line break and properly display labels in
diagrams.
17938308850441861 If multiple diagrams are open in read mode, redundant
asynchronous refreshes are avoided.
8682711552398361914 The refresh of mapping boxes has been improved.
Internal mapping boxes in locked diagrams now refresh
immediately.
8682711553353002100 An error that occurred when moving objects in a diagram
has been resolved.

Diagram configuration ID Resolution

17938311642322112 Figures which are set to invisible by the object
configuration, label configuration, or filters, are no longer
reset to visible by other settings. This prevents that labels
briefly appear while opening a diagram.
17938311323242073 Calculated labels consider configured rule constraints in
the label configuration.
8682711552652071038 To improve performance, connections only once regard
the object configuration.
17938309328882044 The Local filter for displaying artifacts of the current
Product Line works for Meta Class Artifact Pickers that
are used in diagrams via a Diagram Configuration.
17938309329522044 Metric Artifact Pickers can be used in the Diagram
Configuration.
8682711553171381806 When assigning the Diagram Configuration to a diagram
it is now correctly applied.
The behavior of publishing a diagram was changed.
Labels set as invisible by the object configuration are not
displayed when publishing the diagram.
17938309342502101 Object configurations for artifacts that have certain
properties set, like for example a start node of a
Topology Segment, can be saved, now. An object
configuration is only modified (locked and possibly
checked-out) if a modification has been carried out.

Exporting and ID Resolution

publishing diagrams
17938309312192102 A printed diagram now only has a red background if the
diagram contains invisible artifacts.
8682711552491502041 The corners of the rounded rectangles in diagrams are
correctly connected to their lines even on high zoom
levels in the PDF export.

© Vector Informatik GmbH Version 10.6 84

 PREEvision 10.5

ID Resolution
8682711553056422042 When a diagram which contains transparent artifacts is
published as diagram file via context menu Publish
diagram…, multiline labels of these artifacts are now
properly displayed in the published diagram file.
17938309366281038 When exporting a diagram as report or PDF labels
ending with empty lines are now aligned properly in
positions lists.
8682711552433822045 Font sizes in diagrams are the same independent of
whether the diagram is displayed in PREEvision or
exported as PDF or ODG.
8682711552451732041 The Use maximum resolution option has been
removed from the Page/Print Settings preferences.

Tables in diagrams ID Resolution

17938309032261912 Tables in diagrams are displayed at the correct position
regardless of the screen resolution.
17938308107701038 Tables in diagrams are no longer highlighted when
navigating to an opened diagram from the Model View.
8682711553092362159 Tables can be displayed in a diagram on an artifact with
the Show Table dialog. If the artifact is shown multiple
times in different sections and/or the diagram area, the
table can be displayed for each occurrence
independently.
The Show Table dialog now correctly recognizes if a
table for a specific artifact is already displayed in this
section or diagram area.
8682711552683152001 The context menu entry Delete from Model has been
removed for tables that are displayed in a diagram.
17938308166022099 When displaying tables in diagrams, the error in the
calculation of the table size of a table with multiple
columns due to a maximum table height is fixed. The
calculation now also works if the table size is determined
by the last column.
17938307717622050 When displaying tables in diagrams, the context menu
action Show Table now considers the localized names
for tables in the Show Table dialog.

2.5.3 Tables

ID Resolution
17938307506972112 A double click on an artifact now only opens tables which
are defined as default editor and are associated to the
meta class. If the current perspective has defined
prioritized default table editors, only these are opened.

© Vector Informatik GmbH Version 10.6 85

 PREEvision 10.5

ID Resolution
17938307778561992 Names of software types and prototypes are
synchronized when the name is edited in tables.
17938309242941027 A selection propagation between Combined Table Proxy
artifacts works properly again.
17938307554012106 A validation check for drag and drop actions in tables has
been implemented to avoid invalid drop operations.
17938311331272098 Copy and paste of a multi-selection into direct attribute
columns works properly.
17938311441763039 A check box within a table column in read-only mode
cannot be edited anymore.
8682711551845231992 The gray area inside a table cell which usually displays,
for example, a drop-down functionality, is only displayed
if such a functionality is available for the active table cell.
8682711552860642102 It is now possible to cancel the printing of a table.
8682711553163282001 The selection column in tables only considers selections
in the table but not from outside the table, for example,
by selection propagation from the Model View.
8682711552430302045 When activating the table search in combined tables, the
search field is writable for all child tables.
17938305535212106 Pinning in tables is still active after embedded formatted
text cells have been opened.
17938307557592105 Moving a table tab of a table which is not in the
foreground has led to an operation in progress which did
not terminate. This issue has been resolved.
17938308025761806 A table cell that has set a width of zero pixels does no
longer cause display errors. The table is properly
displayed.
17938308772882045 No system crash occurs anymore when temporarily
adding an artifact to a scope while a table is open.
8682711553039172105 Tables are no longer collapsed after executing a commit.
8682711553105783013 Within tables, the selection is kept after collapsing and
expanding.
8682711553258912106 Table rows are expanded on table updates if the option
Show expanded is activated.
8682711553081023042 A double click on an artifact in a read-only column no
longer leads to losing the selection. The table cell keeps
the selection.
17938307956621025 An error dialog is displayed again when copying cell
values of different columns with gaps between the
selected cells.
17938311633421810 It is now possible to copy values from cell metrics and
paste them into another cell.
17938308048812113 The Delete artifact button for table cell entries in tables
is now also displayed if multiple cells are selected.

© Vector Informatik GmbH Version 10.6 86

 PREEvision 10.5

ID Resolution
17938311331162102 For tables with charts, the incorrectly displayed error
message in the Information View concerning a missing
life cycle color is no longer displayed.
17938311473772113 Custom attributes having set no value no longer cause
an error message on opening a table in which they are
displayed.
17938311514852113 Table cell actions are only displayed if the table cell is
selected and focused.
17938311345712106 The performance of selecting artifacts in table cells has
been improved.
17938307782281045 The performance for working in tables has been
improved, when calculating the cell sum for tables.
17938308102982104 Action buttons for table cell entries in tables are now only
visible if the corresponding table is also visible.
17938307554002106 When changing from one table to another already
opened table while there are pending updates, the
Progress Information dialog shows a text which informs
the user about updating table contents.
8682711552040552104 The copy and paste behavior in tables has been
corrected in case the selected cell has no label
configuration.
8682711553288322101 The Excel export of a table works if the table contains
headers with the same name.
17938307511243017 No exception occurs anymore for tables for which cell
content is calculated via a metric.
17938305494192106 The column width is persisted when saving a table into
the model.
17938309241212065 Table editors opened as a temporary table via a Table
Proxy or Open with … context menu may not change
the table model. Therefore, all context menu entries
which would lead to changing the originating table have
been removed.
17938311665222113 Searching in combined tables also works with collapsed
or hidden columns.
8682711552765201806 The selection is set to the correct artifact in the Model
View also if columns are hidden in the table.
8682711552925843042 Changing the sort order of the first table column no
longer leads to hidden values in the last table row.
17938311421722101 For tables with hidden columns, active column filters
work properly after refresh.
17938311524072106 Pasting clipboard content into tables that contain hidden
columns works properly, now.
17938311682752101 If columns of tables are set as hidden, the content of
columns with check boxes is kept and displayed.

© Vector Informatik GmbH Version 10.6 87

 PREEvision 10.5

ID Resolution
17938308307252099 After a refresh in a table, the active filters are applied
again, and the table shows the correctly filtered content.
8682711553161912099 When filtering a table, the currently selected artifacts/
elements are removed from the selection if they are no
longer visible in the table.
8682711553105713013 The expand state in front of subtrees within tables is
correctly displayed after filtering the table.
8682711552769572112 When a table is opened on multiple selected artifacts, the
Artifact Picker now displays the correct scope of
artifacts depending on the set filter.
8682711552331152106 A sporadic problem with copy and paste in filtered tables
has been resolved. Cells are now copied in the correct
order into cells of another table column.
17938309273602036 Drag and drop actions work with prototype columns.
17938311473792049 The refactoring Create Table Instance to convert a
Table Proxy into a table instance is now also possible if
the Table Proxy contains prototype columns.
17938308088892105 The correct column in tables is now filtered when the
table is opened for a Table Proxy and the column to filter
is a prototype column with a table element source.
8682711552971133042 The toolbar action enablement state is updated when the
selection is changed in a Portlet.
8682711553095042102 To better support selecting elements from a link column
overlay menu, the tooltip is now closer to the mouse
pointer.
8682711553462092041 For table rows that are displayed as help lines in tables,
artifact icons are displayed again.
8682711554010272100 Within tables, pasting artifacts is also allowed on
columns that display several artifacts in one cell.
8682711553352342106 The Predefined filter option is available on a column
even if preceding columns are hidden and following
columns use a formatted text renderer.

Explorer ID Resolution
17938309365052106 When switching the table in an explorer, the selection is
maintained.
17938311391031804 When using the Navigate to Artifact action in an
explorer, the active explorer category is maintained, if the
target table is set as default table for this explorer
category.
17938311631412102 The submenus of the navigation bar are correctly
displayed in explorers.

© Vector Informatik GmbH Version 10.6 88

 PREEvision 10.5

ID Resolution
8682711552705982048 Explorers can now also be opened on artifacts for which
no direct Name attribute can be set but which receive
their name from the corresponding prototype, like for
example, on Compositions.
17938307747931992 In explorers and portlet views, the Open With context
menu entry is correctly displayed depending on the
selected artifact.
17938311538352113 When opening the context menu in an explorer, Open
With is displayed as first entry of the context menu.
17938311444403039 In explorers, meta classes are correctly filtered including
virtually displayed artifacts.
8682711551860041038 The [Save] button, which allows a commit in a multi-user
environment, is now available and active in an explorer
and in the Favorites view if there are model changes.
8682711552087682044 Explorer categories of meta class Explorer Category
(ModelView Filter or Query) use artifacts from the scope
root query as category roots even if no content provider
query is available.
17938309342301810 The Status view no longer displays error messages
when opening an explorer. The errors were caused by an
outdated filter.xml file containing references to old
meta classes.
8682711553388601992 Creating artifacts in explorers does no longer lead to
displaying duplicates of these artifacts in the Model View
and the categories of the explorer.
17938307379292108 If the last selection in an explorer category shall be
stored, can be defined with the attribute Take Over the
Last Category Selection of the Explorer in the
Administration.

Table configuration ID Resolution

8682711552552802083 When using the table column configuration Horizontal-
Alignment = "right" the icon is still rendered on the left
side of the text. The icon and the text are together
aligned to the right edge of the table cell.
8682711552561772106 The formatting tag <dec> </dec> has been
implemented for the Customized Label configuration to
force a decimal format representation of numbers, for
example, for numbers in tables.
17938307946942102 It is now possible to open editors under a Table Editors
Package.
17938309386412049 Adding an already associated table column that displays
a custom attribute multiple times to a table is no longer
possible.
17938311685172101 Moving a table column does no longer result in hiding
other columns or prototype columns.

© Vector Informatik GmbH Version 10.6 89

 PREEvision 10.5

ID Resolution
8682711552539621220 The initial state of column group elements in the Add/
Remove/Reorder Columns dialog is now visualized
correctly.
8682711552708592106 Hiding selected prototype columns is now possible in
tables.
8682711553038071032 Cell metrics used in tables now show the returned string
as plain text without style range formatting.
17938308315432041 Embedded Metric Executors that are assigned as action
query to a table column are only executed if the dropped
artifact has a suitable meta class.
8682711553964471027 For Direct Attribute Table Columns, the column
configuration works properly.
8682711553269731914 In the Property View of tables, the Toolbar Actions
property page has been added to the Characteristics
category.

2.5.4 Requirements

ID Resolution
17938308131332101 Changing the type of a checked-in Requirement that has
a life cycle without changing its reuses no longer leads to
a class cast exception.
8682711552337612107 Attributes that are read-only due to meta rights are now
correctly set when copying between models.
8682711553140751030 The online check "Requirement attribute value is
incorrect" correctly checks multi-attribute definitions with
an enumeration data type. The individual enumeration
literals are now checked for correct values.
8682711553170902101 Copy and paste of Requirements no longer changes their
order.
8682711552944241791 An error in the Identity Function Abstraction (Custom ID
for Requirements) metric block has been corrected: Plan
artifacts which are direct children of the root Product
Lines are now matched between source and target
model.
17938308996852105 In the Property View of Requirements, cut and paste
actions between property pages are possible now. The
corresponding property pages are properly displayed.

Requirement text editor ID Resolution

17938291663539243 In the Requirement Text Editor, the Open With context
menu on Product Goal Links contains the same entries
as the context menu in the Model View.

© Vector Informatik GmbH Version 10.6 90

 PREEvision 10.5

ID Resolution
17938306651292105 After moving an artifact via the move button in the
Requirements Text Editor and then carrying out the
undo operation, the table is properly refreshed.
17938309369442106 Switching between tables of the Requirement Text
Editor via the toolbar button is possible again.
8682711552104362105 When deleting Requirements in the Requirement Text
Editor, no empty table rows are displayed anymore.
8682711552418141030 In the Requirement Text Editor, the font color in
formatted text table cells is now rendered correctly
according to the object configuration.
8682711553027022105 During an export from the Requirement Text Editor to
Excel, placeholders are updated, and the correct
placeholder information is exported.
17938306401202105 The performance of filtering in the Requirement Text
Editor has been improved.
17938307537762101 Pasting the first cell of the Requirements For column of
the Requirements Text Editor into all other cells of this
column via multi select, now finishes with good
performance.

Formatted text and ID Resolution

placeholders
17938311460702105 When displaying the preview of formatted texts in table
cells, lines indented by tabulators in the formatted text
are now also displayed as indented lines in the preview.
17938311512092105 Formatted text containing OLE objects can now be edited
directly in table cells of the Requirement Text Editor.
17938311666232106 Pasting formatted text with placeholders into custom
attributes is possible now.
8682711551847412106 Sporadic problems with rendering formatted text in tables
have been resolved.
8682711552341902105 A performance problem has been resolved that occurred
in tables when copying formatted texts containing
placeholders.
8682711553181462105 The previews of formatted texts within tables are now
correctly rendered when they contain tables with
vertically merged cells.
17938307539672023 The Check OLEs in Formatted Texts action no longer
displays hidden artifacts in the Information View results.
17938307553992106 Placeholders in formatted texts can now be properly
restored using the redo or undo functionality of the
integrated editor for formatted texts.
17938307564382001 Pasting formatted text into a table cell which is only
selected without opening the Libre Office editor is
enabled. The pasted text is inserted as plain text.

© Vector Informatik GmbH Version 10.6 91

 PREEvision 10.5

ID Resolution
17938307671152023 The Check OLEs in Formatted Texts action now uses
the configured localizations for attribute definitions in the
Information View message.
17938307683663017 Inserting images into formatted texts via drag and drop
now works properly if the filename contains Unicode
characters.
17938308107832023 Frame styles are now displayed in the Styles and
Formatting view when using the Rich Text Template File
in the PREEvision demo model.
17938308840082070 The performance of auto updates has been improved by
caching the information whether the formatted text
workspace directory exists in the file system.
17938308865672040 Shapes are now disabled in the formatted text editor
since they cause rendering errors in the preview of
formatted texts.
17938308926362113 If preferred placeholder attributes are configured for a
perspective, only the assigned (configured) attributes are
available for selection in the Insert Placeholder dialog,
again.
17938308931662106 In a sporadic constellation, newly created placeholders in
formatted texts were displayed as <undefined>. The error
has been resolved.
17938309056902025 The messages that are reported when executing the
Update Rich Texts metric block have been improved.
17938309197172106 Formatted text placeholders which reference other
formatted texts are no longer resolved when creating a
preview. A text note is displayed instead. The
placeholders are still resolved when creating reports or
when they are exported, for example to ReqIF or Excel.
17938309198032106 Placeholders which reference out of scope artifacts now
display <artifact out of scope> instead of <undefined
value> as content in a generated report or a ReqIF
export.
17938309237292106 Recursively embedded placeholders in formatted texts
now reflect the current model state when viewed in
tables.
17938309359282105 An error in the LibreOffice editor has been resolved. OLE
objects in artifacts are now accessible and can be
opened with read-only rights.
17938311364202106 To prevent errors during formatted text handling, the tool
state is reset after a model compare.
17938311391022106 Formatted text without available HTML previews no
longer causes error messages when opening the
Change history view for an artifact.
17938311519132104 The sporadic loss of OLE object previews has been
resolved. OLE objects are correctly displayed in reports
again.

© Vector Informatik GmbH Version 10.6 92

 PREEvision 10.5

ID Resolution
17938311530392106 Several problems have been resolved concerning
formatted text of meta classes which do not support
placeholders at all.
17938311674121783 Editing placeholders in formatted texts no longer
produces empty spaces at the end of a line.
8682711552081441030 Line breaks in formatted text previews created via ReqIF
import are now displayed correctly.
8682711552419472106 If loading formatted text from the server fails due to
network problems, an additional attempt to reload the
formatted text is executed when accessing the formatted
text again.
8682711552495132106 Creating placeholders works properly if a save action is
triggered.
8682711552759542023 The editor for formatted texts now allows inserting
images via drag and drop at positions which are already
occupied by images. The new image is then inserted left
of the existing image.
8682711553066032105 EMF graphics can now be inserted into PREEvision
formatted texts without rendering errors.
17938300517172105 Images and OLEs exported by PREEvision are no longer
distorted when imported again into a PREEvision model.
17938306022802107 LibreOffice has been updated to resolve problems with
OLE objects in IBM Doors.
8682711552050411030 When creating nested placeholders, no misleading
warning is displayed.
17938307341861806 With incomplete formatted text, LibreOffice could not
process the input and the editor could not be opened.
Now, missing information is synthesized, and the
LibreOffice editor opens.

ReqIF import and ID Resolution

export
17938305319212106 ReqIF import: The preview of OLE objects that are
imported via the ReqIF import could increase in size after
editing the object. The ReqIF import now prevents the
creation of such corrupted objects.
17938306878892084 ReqIF import: OLE objects with the MIME type
"application/rtf" are correctly imported.
17938309340622049 ReqIF import: The performance of the import has been
significantly improved for very big scopes.
17938311461882040 ReqIF import: Importing the same ReqIF file twice no
longer leads to changes in the model due to instable list
IDs.

© Vector Informatik GmbH Version 10.6 93

 PREEvision 10.5

ID Resolution
17938311651362105 ReqIF import: Default values for the Object type attribute
are now properly interpreted for the class matching
during when using this mode.
8682711552275772023 ReqIF import: Unnecessary model tree locks for new
artifacts created during a ReqIF import are no longer
required.
8682711552720992105 ReqIF import: The content of CDATA sections is no longer
ignored when importing ReqIF-XHTML.
8682711552922323059 ReqIF import: The import reads REQIFZ files which link
the same file attachment multiple times in the same
XHTML attribute.
8682711552929783059 ReqIF import: The german message text reported in the
Information View for ReqIF files that are not compliant
to the schema has been corrected.
17938306709112105 ReqIF import: A "Multiple roots" error has been resolved,
which was caused by an import of comment artifacts for
Test Specification Libraries. In case of an import of such
comments, an error message is reported in the
Information View, including the SourceID of the object
causing the error. The import of supported artifacts is
continued.
17938307396702023 ReqIF import: The file choosing dialog of the ReqIF
import metrics now offers to filter the shown files by
compatibility.
8682711552015482106 ReqIF import: The attribute Custom ID is updated
correctly during the import.
8682711552442692049 ReqIF import: When updating existing artifacts with a
ReqIF import, reuses of these artifacts that are checked-
in are not changed.
8682711552683701859 ReqIF import: The ReqIF configuration files in the
PREEvision demo model are updated to use the correct
attribute names precondition and postcondition instead of
preCondition and postCondition.

8682711551893672106 ReqIF agreement import: For supplier comments,

unnecessary space characters are no longer set.
17938306022842107 ReqIF export: Shapes in formatted texts are
automatically converted to images or OLEs.
17938311661192105 ReqIF export: Bookmarks in formatted texts are no
longer exported to avoid schema validation errors.
8682711552510132098 ReqIF export: Images and OLE objects with vertical or
horizontal spacing in formatted texts no longer cause
schema validation errors.
17938305543782065 ReqIF export: An error message is reported if the export
is started with the option Active variant only and no
Requirement Package or Customer Feature Package is
part of the active variant.

© Vector Informatik GmbH Version 10.6 94

 PREEvision 10.5

ID Resolution
17938307225372113 ReqIF export: Exporting formatted texts containing block
quotes no longer causes schema validation errors.
17938307570112107 ReqIF export: Correct previews are displayed for
exported Visio OLE objects.
17938307810772023 ReqIF export: In the PREEvision demo model, a typo has
been corrected in the documentation block of the ReqIF
export metric.
17938308140791807 ReqIF export: The export no longer contains unwanted
line breaks for plain text.
17938308161942105 ReqIF export: Custom attributes for which no attribute
values are set, are filtered out during the export executed
via metric, and the schema validation is successful.
17938308177661806 ReqIF export: Attribute Definitions without data type can
be exported.
17938308192542104 ReqIF export: The reliability of the ReqIF export
performance has been improved.
17938308756822107 ReqIF export: Exporting nested lists no longer causes a
schema validation error.
17938309047742023 ReqIF export: An error message has been improved that
is reported during the export for large images/OLEs.
17938311460762105 ReqIF export: <li> elements in the exported ReqIF
XHTML file are properly closed if they wrap multiple
paragraphs.
8682711551829472107 ReqIF export: Attributes with localization are correctly
exported.
8682711551881482105 ReqIF export: Non-printable characters in formatted texts
are properly handled during the export.
8682711552283401783 ReqIF export: Tables with background colors in formatted
texts no longer cause schema validation errors.
8682711552292512104 ReqIF export: If diagrams with conflicting names are
correctly exported to OLE objects, without causing an
endless loop.
8682711552337552065 ReqIF export: For requirement links with multiple targets
only the first target is exported. The relevant requirement
links are shown in the Information View.
8682711552458671783 ReqIF export: In the PREEvision demo model, an
example for referencing a description has been added to
the example report for specific ReqIF exports.
8682711552458681783 ReqIF export: Using the ReqIF export via report,
formatted texts containing only an OLE, image, or table
can now be exported.
8682711552462962101 ReqIF export: The performance has been improved for
ReqIF exports containing a lot of variant information.

© Vector Informatik GmbH Version 10.6 95

 PREEvision 10.5

ID Resolution
8682711552495812101 ReqIF export: The ReqIF export of structures with reuses
with different branch or revision is now aborted with an
appropriate error message.
8682711552500681783 ReqIF export: Using the ReqIF export via report, artifacts
without name can now be exported.
8682711552542202105 ReqIF export: Custom attribute values containing only
non-textual content are now correctly exported.
8682711552553813059 ReqIF export: Text sections in formatted texts no longer
cause schema validation errors.
8682711552560653059 ReqIF export: Defective OLE objects embedded in
formatted texts no longer cause schema validation
errors.
8682711552561273059 ReqIF export: OLE objects with broken previews in
formatted texts no longer cause schema validation
errors.
8682711552650413059 ReqIF export: The outdated metrics "ReqIF import
classic" and "ReqIF export classic" have been removed
from the PREEvision demo model.
8682711552721861783 ReqIF export: The PREEvision demo model has been
updated and contains valid example Attribute Definitions
compatible with the changes of the ReqIF export.
8682711552732302105 ReqIF export: The export is aborted if the conversion of a
formatted text to ReqIF XHTML fails and an error
message with hints for solving the problem is displayed.
8682711552921932111 ReqIF export: The LibreOffice restriction evaluation of the
authority model is ignored while executing the ReqIF
agreement export. Thus, the placeholder highlighting is
always exported.
8682711553316031783 ReqIF export: Tables with vertically merged cells no
longer cause schema validation errors.
8682711553316061783 ReqIF export: Attributes of the normal HTML export were
created for table cells styled in a specific way. Since
these information are not part of the ReqIF XHTML
specification, their synthesis is excluded during the
ReqIF export.
17938307705401859 ReqIF export: Changes made by the ReqIF Export
TestRoutines metric block are now executed inside a
model operation per default. This only affects newly
created blocks, existing blocks in existing metrics are
unchanged.
8682711552275612049 ReqIF export: The ReqIF export of test data no longer
exports spec relations without source or target.
8682711552442692023 ReqIF export: In the PREEvision demo model, entries
which are only relevant for requirement exports or
imports have been removed from the ReqIF TDM
configuration files.

© Vector Informatik GmbH Version 10.6 96

 PREEvision 10.5

ID Resolution
8682711553047162101 ReqIF export: Relations are no longer lost between Test
Item Steps and Test Routines if there are reused Test
Routines outside the Product Line from which the export
was started.
8682711553181472105 ReqIF export: Centered tables in formatted texts no
longer cause schema validation errors.
8682711553655572107 ReqIF export: During synthesis of the supplier comment
attribute definition, the name was taken as part of the
representing ReqIF identifier. ReqIF identifier may not
contain space, which were contained in the name. These
spaces are removed for the ReqIF identifier.
In the PREEvision demo model, the ReqIF Agreement
import metric has been updated to work with changed
attribute definition names for the supplier status and
comment.
8682711553517132049 ReqIF export: The check for standard ReqIF profiles now
only considers profiles, which are children of the Custom
Attribute Profile Container under the global
Administration. Profiles of test data in metrics are not
considered.
8682711552419192065 ReqIF import and export: In all example ReqIF import
and export configuration files, a comment concerning the
class mapping has been updated.
8682711552442742023 ReqIF import and export: ReqIF import and export
configuration files are uniformly formatted.

2.5.5 Logical function architecture

ID Resolution
8682711551969802062 Missing translation for Service Required Port Groups and
Service Provided Port Groups have been added.
8682711552516761030 An issue with incomplete interface generalizations has
been resolved. Now the superior interfaces will be also
represented in the Property View with its available Data
Elements.
8682711552635661875 Signal Transmissions inside a Transmission Frame in a
Concept Diagram snap to the grid.
8682711553353022100 Selection and highlighting of ports is now calculated after
opening a Logical Architecture Diagram with Open With.
8682711553353032100 The entries in the Open With menu at a logical
architecture port have been consolidated.
8682711553074502101 Assemblies with more than one Assembly Connector will
not be deleted when hiding the corresponding Bus
Connection.
17938308061641806 When moving blocks into Building Blocks either in the
Model View or in a diagram, assemblies are now treated
similarly. Assemblies between a moved block and

© Vector Informatik GmbH Version 10.6 97

 PREEvision 10.5

ID Resolution
delegation ports of the Building Block are deleted and
new assemblies within the Building Block are created so
that the moved block is still connected to the delegation
ports but from within the Building Block.
8682711553353012100 A new group has been added to the Open With menu to
harmonize menu structures.

2.5.6 AUTOSAR
AUTOSAR export ID Resolution
17938311595502051 AUTOSAR export: the message 'Artifact doesnt have
name' appears only for relevant artifacts.
8682711552495711825 Implementation data types referenced by
KeyTemplateArguments and
ValueTemplateArguments of Implementation
Associative Maps are now exported to AUTOSAR
correctly.
8682711551972432003 For the following AUTOSAR exports, initial values of NV
Data are now exported correctly:
> AUTOSAR ECU extract
> AUTOSAR SW component description
> AUTOSAR system description
17938307346762000 Sender Receiver To Signal Mappings are now properly
exported.
17938311611322000 The AUTOSAR Cluster Extract export now correctly
exports the So Ad Routing Groups.
8682711553044011825 AUTOSAR package structure is now stable for
consecutive exports.
17938307707902040 Secure-Communication-Props for AUTOSAR
version 4.2.2 have been implemented and are now
imported and exported.
17938308103662003 On export, AUTOSAR
ApplicationArrayElement.ShortName is in every
case taken from Name of the Application Array.
8682711552070592053 The AUTOSAR export will now correctly export the
relation Mode DeclarationAccess and Target
ModeDeclarationAccess on the artifact Mode Switch
Event in regard of their order. This means that the
relation ModeDeclarationAccess will always be on the
first position and the relation Target Mode Declaration
Access on the second position in the resulting ARXML
file for the AUTOSAR artifact SwcModeSwitchEvent.

8682711553123311912 The AUTOSAR export does not export empty Multi Value
Attribute Definitions of type "Enumeration" anymore.

© Vector Informatik GmbH Version 10.6 98

 PREEvision 10.5

ID Resolution
8682711553545952052 The Update Indication Bit Position of Signal IPDU
Assignments will be now exported in case the Signal
IPDU has no PDU Frame Assignments as well.
8682711552005871992 Symbols and Japanese characters are now properly
handled during AUTOSAR export.
8682711552492321806 The attribute CATEGORY of ClientServerInterface
is now imported and exported.
8682711552539441917 For the AUTOSAR import and export, the attribute
Approval Status of an Evaluated Variant Set is now
considered.
17938309027902051 The AUTOSAR export with model query-based
propagation, for example, cluster extract, ECU
communication extract or SW component extract now
displays an entry with a link in the Information View. Via
this link the artifacts that are out of scope but are
required for the propagation can be temporarily added to
the scope.
17938309273472042 The following new AUTOSAR consistency checks have
been implemented:
"p1172_Ipv4Configuration_with_invalid_Ipv4Address"
"p1172_Ipv6Configuration_with_invalid_Ipv6Address"
The AUTOSAR export is canceled if the AUTOSAR
export version is 4.2.2 or lower, and the export includes
an artifact like IPV-4-CONFIGURATION or IPV-6-
CONFIGURATION with the attribute IPV-4-ADDRESS or
IPV-6-ADDRESS and value ANY.

17938311405181792 DataIDs are now only exported to AUTOSAR if the Data

ID attribute value is set. DataIDs are exported in the
same order as modeled in PREEvision, except for the
Sync Data ID List of a CAN Global Time Domain and
FlexRay Global Time Domain.
17938311513152108 For the AUTOSAR software component description,
SWC Implementations are now correctly exported.
17938311631452052 A memory leak has been fixed which was caused by
holding the AUTOSAR model after transformation and
not releasing it after writing the ARXML file.
17938311673342108 Unused Calibration Parameter Record Layouts can now
be exported using a custom export and the option No
Datatype Restriction.
8682711552262711030 AUTOSAR admin data for SOME/IP Transformation
Properties with multiple usages are properly exported
now.
8682711552341932014 The default setting of the flag "DBC2AR" have been
changed from "true " to "false " in the file
"autosar_import_export.properties". Otherwise, the signal
start position is converted during the AUTOSAR export,
and this is not the expected default behavior.

© Vector Informatik GmbH Version 10.6 99

 PREEvision 10.5

ID Resolution
8682711551967072051 The Virtual Package structure which was activated for an
AUTOSAR export in the export dialog, remains activated
for further exports and the Virtual Package structure is
exported properly during AUTOSAR as well as diagnostic
exports.
8682711552082781913 UUIDs created for implementation data types during
AUTOSAR export are now stable on every consecutive
export.
8682711552396242051 The value HEADERTYPE_NONE for the attribute Header
Type of Container IDPUs is now imported and exported.
8682711552421080000 So Ad Routing Groups are now properly exported in
cluster extracts.
8682711552475061029 An ECU communication extract is now possible while
using a Function Designer license.
8682711552866322004 ECU communication extract now exports implementation
data types.
8682711552947280000 The import and export now support the INTRODUCTION
of an I-PDU-MAPPING which is represented by the
Description attribute of a PDU Gateway Routing Entry.
8682711553125792003 Data Constraints that are referenced multiple times are
now correctly exported as single artifact to AUTOSAR.
8682711553171531825 The attribute Constraint Level of data constraint rules is
now properly exported.
8682711553346541998 SW component descriptions now export the initial value
of constant memory.
17938309299042040 Importing Associative Maps in AUTOSAR Classic files is
disallowed. Exporting implementation data types without
CATEGORY is avoided.

8682711552647131024 End To End Transformation Com Spec Props

are now imported from AUTOSAR and exported to
AUTOSAR properly.
8682711553356011024 CPP Implementation Data Types are now exported
with correct Type Emitter and Header File values
automatically set for the Adaptive platform types "bool",
"int8_t", "int16_t", "int32_t", "int64_t", "uint8_t", "uint16_t",
"uint32_t", "uint64_t", "float", and "double" if one of these
shortNames is used for an Implementation Value.

8682711553487001024 Name and option value of a Startup Option are now both
exported as Process Arguments to AUTOSAR. The
order name - option is always maintained.
8682711553114132159 A new property page Ports has been introduced that
replace the two pages Logical Ports and Software
Ports. The new page gives an overview over the meta
classes Signal, System Signal, Signal Group, and
System Signal Group.

© Vector Informatik GmbH Version 10.6 100

 PREEvision 10.5

ID Resolution
17938307707902040, Secure-Communication-Props for AUTOSAR
17938307710382003 version 4.2.2 have been implemented and are now
imported and exported.
8682711553547751024 Minimum and maximum limit values of generic
constraints are now exported without any conversions
and rounding.

AUTOSAR ECU extract ID Resolution

8682711551967081806 AUTOSAR ECU extract: now correctly propagates and
exports the relation targetModeDeclarationAccess
on the artifact Mode Switch Event.
8682711553098930000 AUTOSAR ECU extract exports the Addressing Method
for Parameters of Parameter Interfaces correctly.
8682711551972032003 During an AUTOSAR ECU extract Addressing Methods
of the following artifacts are correctly propagated now:
> Constant Memory
> Data Element
> Instantiation Properties
> Inter Runnable Variable
> Memory Section
> NV Data
> Operation Argument
> Parameter
> Runnable Entity
> Static Memory
8682711552494842052 IDENT of the TpConnection, LinSlaveConfig and
PncMapping is now always exported.

8682711551942991913 For an AUTOSAR ECU extract, Generic Physical Data

Constraints for Application Curve Types, Application Map
Types, and Application Cube Types are now properly
exported.
8682711552942822107 From some special model configurations, not-used
Signal IPDUs have been exported via ECU extract. That
has been fixed.
17938309311881914 Referenced invisible artifacts from the global
Administration do not abort the ECU extract anymore.
17938307711722003 During the export of an ECU extract, no foreign payload
PDUs (payload PDUs of foreign ECUs) are exported
anymore.
8682711552299811917 The export of an ECU extract can be properly executed if
the data to be exported contains mapped Logical
Functions.
17938311454432004 Data IDs of end-to-end Profiles are now propagated and
exported in ECU extract and system extract.

© Vector Informatik GmbH Version 10.6 101

 PREEvision 10.5

ID Resolution
17938308170251032 Implementation data types connected to Signals will no
longer be exported.
17938306059752088 Data mappings and signal ports are not exported
anymore in the case the contained multiplex PDU is
transmitted over the gateway.
17938307558851024 The ECU extract now exports
TransformationComSpecProps.

17938309250770000 For an AUTOSAR ECU extract, several changes in the

propagation and export of Global Time Domains and
related artifacts have been implemented:
> Global Time Master and Global Time Slaves are no
longer propagated and exported based on the
containment of the Global Time Domain. Global Time
Master and Global Time Slaves are now propagated
and exported based on the reference from the ECU
Interface.
> Global Time Gateways are no longer propagated
based on the reference from Global Time Master or
Global Time Slaves. A Global Time Gateway is now
propagated and exported based on the reference
from the Electric Electronic, for example ECU,
Sensor, Execution Context, etc.
8682711551958391913 For an ECU extract, the physical values of Axis Literals
are now correctly exported.
8682711552287352014 In the ECU extract, the payload of Secured IPDUs is now
properly exported.
17938308264691825 A transformation error which occurred during the export
of an ECU extract has been resolved.
17938308170241032 In the ECU extract, the data type of a Typed Per Instance
Memory is properly exported.

AUTOSAR system ID Resolution

description
8682711551833761024 For an AUTOSAR system description, SEC-OC-
CRYPTO-SERVICE-CONFIGURATION is now correctly
exported.
17938311321502040 Service Interfaces are no longer exported via AUTOSAR
System Description. The mixing Classic and Adaptive
contents is not supported by any PREEvision AUTOSAR
export.
8682711551895991825 A system description with Adaptive contents is not
supported. A check has been added in the export wizard
to recognize Adaptive content and reject the export.
8682711553067141909 An error which occurred during the export of a system
description, and which was caused by a missing relation
between an ECU Interface and a Bus Connector has
been resolved.

© Vector Informatik GmbH Version 10.6 102

 PREEvision 10.5

AUTOSAR adaptive ID Resolution

exports
17938307437292010 Process to Machine Mappings are now fully exported to
AUTOSAR within the execution manifest.
17938307763071024 Cores of a Microprocessor are now also exported in the
software cluster design description if they are not
assigned as Shall Run or Shall Not Run to a SW-
NET:Component Mapping.
17938307941152088 The references of an interface mapping to VARIABLE-
DATA-PROTOTYPEs and CLIENT-SERVER-OPERATION
are exported as open references in the Adaptive
application description.
17938308210710000 For the AUTOSAR application description, the defined
Namespace hierarchy is considered now.
17938308224821025 The suffix automatically generated for
RootSwComponentPrototype names during
AUTOSAR export has been removed.
17938308321812040 Base Types assigned to CPP-IMPLEMENTATION-DATA-
TYPEs are no longer exported.

17938309287992010 SOME/IP Transformation Properties and User Defined

Transformation Properties are now also propagated to
the service interface description.
17938309365152010 For the AUTOSAR Adaptive import and export, the name
of an AP-SOMEIP-TRANSFORMATION-PROPS in
AUTOSAR is now derived from the name of the
corresponding SOME/IP Transformation Properties in
PREEvision.
17938309378680000 The propagation of process execution dependencies has
been added to the software cluster design description.
17938311323312052, Application Errors referenced to UML Methods via
17938311323322052 Application Error Groups are now also propagated to the
software cluster design description.
17938311394732052 For the AUTOSAR software cluster design description,
Namespaces which are referenced by Application Error
Packages are now exported.
17938311724772052 The AUTOSAR software cluster design description has
been adjusted to handle several cases of faulty open
references in the exported AUTOSAR files.
8682711551904770000 The timeout set for a Machine Deployment are now
correctly exported into a Machine Manifest.
8682711552446501913 Template arguments are now also exported when the
Long Name is set.
8682711552484981913 ApplicationErrorDomain.value is now correctly
imported and exported. The reference between
ApApplicationErrors and
ApApplicationErrorSet is now correctly imported as
well.

© Vector Informatik GmbH Version 10.6 103

 PREEvision 10.5

ID Resolution
8682711552510112051 References from application data types to Computation
Methods are now exported in AUTOSAR software cluster
design descriptions and service interface descriptions.
8682711552640342051 The import and export of TLV data IDs for application
and implementation record elements has been fixed.
8682711552688542010 If none of the attributes UDP Collection Buffer Timeout
or UDP Collection Trigger is set for Consumed SOME/
IP Method Instance, Provided SOME/IP Method
Instance, and Provided SOME/IP Event Instance, no
COLLECTION-PROPS are exported anymore for the
corresponding SOMEIP-METHOD-PROPS and SOMEIP-
EVENT-PROPS.

8682711553161901024 AUTOSAR export now exports Application Errors

assigned to own Virtual Packages or default Virtual
Packages correctly. Assigning an artifact to more than
one Virtual Package that are all exported, the export will
be aborted, because this is not allowed.
8682711553295471024 A bug has been fixed which caused multiple references
between the same ApApplicationError and
ApApplicationErrorSet if the set was referenced by
multiple users.
8682711553437491002 The AUTOSAR service instance manifest export does
not export
ServiceInstanceToPortPrototypeMappings
anymore.
8682711553454391024 Key Template Argument is now correctly exported as
CPP-TEMPLATE-ARGUMENT with CPP-TEMPLATE-
ARGUMENT.category == ASSOC_MAP_KEY, value
Template Argument as CPP-TEMPLATE-ARGUMENT with
CPP-TEMPLATE-ARGUMENT.category ==
ASSOC_MAP_VALUE.

17938307379383010 Service Interfaces are not exported to the service

instance manifest anymore.
17938307756770000 For the AUTOSAR service instance manifest, a
Consumed Service Instance and a Provided Service
Instance with the same Data ID can now reference the
same End To End Transformation Properties.
17938307822191024 Adaptive internal behavior and its service dependency is
now propagated and exported in the Software Cluster
Design Description (formerly Adaptive Application
Description).
8682711553501581024 A logic has been added to keep the IDs of SIGNAL-
BASED-EVENT-ELEMENT-TO-I-SIGNAL-
TRIGGERING-MAPPING stable over multiple AUTOSAR
exports if the EventPlatformDataTypeMapping does
not exist in the PREEvision model.
8682711552994941792 Signal IPDUs are always exported with complete
ISignalToPduMappings, even in signal-to-service
scenarios, when some Signals are of no interest.

© Vector Informatik GmbH Version 10.6 104

 PREEvision 10.5

AUTOSAR import ID Resolution

8682711553462111024 Software cluster designs without category can be now
imported- It will be considered as
ROOT_SOFTWARE_CLUSTER.

8682711553553362052 The import of IMPLEMENTS-SOMEIP-STRING-

HANDLING has been corrected for AUTOSAR 4.4 and
lower.
17938308165762101 On AUTOSAR import, for COLLECTIONS without
CATEGORY it is assumed that the CATEGORY=SET
(fallback defined in the standard).
17938308183582051 During AUTOSAR import, the model transformation error
which occurred during the merge of an APPLICATION-
VALUE-SPECIFICATION of CATEGORY=MAP has
been fixed.
17938308952171992 The import identifies the inconsistent reference GLOBAL-
TIME-DOMAIN.MASTER used in lower versions than the
AUTOSAR_00046 schema and stops the import
reporting an error message in the Information View.
17938309215602108 AUTOSAR import with merge/replace: The identity
function for Application Type Implementation Type
Mappings has been modified to use the related Data
Type Mappings package, application type and
implementation type for identification. No ImEx IDs are
imported for Application Type Implementation Type
Mappings.
17938309286952108 During AUTOSAR import with replace, Addressing
Methods are updated, now.
17938309312311792 AUTOSAR import with merge/replace: COM-SPECs of
PR-Port-PROTOTYPEs are now updated correctly.

17938309322152108 During AUTOSAR import with replace, the "Replace"

block correctly outputs processed roots if artifacts
change their meta class during replace.
17938311478870000 During AUTOSAR import with merge, inconsistencies
between types, prototypes, and instances due to
Assemblies with missing UUIDs no longer lead to errors.
8682711551928361030 During an AUTOSAR import with merge, imported data
types are no longer merged with globally defined data
types, for example, data types from the global Library.
8682711552942720000 AUTOSAR Classic files containing AUTOSAR Adaptive
machines can be imported again.
8682711552918202003 APPLICATION-VALUE-SPECIFICATION whose value
is stored in a Vt object will also be correctly imported
17938307437571792 SomeIpDataTransformationProps for primitive
ArgumentDataPrototype are now imported for
AUTOSAR Adaptive.

© Vector Informatik GmbH Version 10.6 105

 PREEvision 10.5

ID Resolution
17938307443551024 During AUTOSAR import, application to implementation
data type mappings are created for CPP-
Implementation-Data Types, too.

17938309304732052 During AUTOSAR import with merge, the DataID

sequence of an E2E profile is now updated.
17938309312321790 The Property View for Data Constraints no longer
highlights the values "INF", "-INF" or "NaN" entered in
Min or Max as an error.
17938309330302040 The import of AUTOSAR files with the following
inconsistencies is not supported:
> No Machine assigned to Machine Design
> More than one Machine assigned to Machine Design
17938311664551024 SecOC Service Configuration is now correctly imported.
The SecOC Service Configuration receives a name
based on "SecuredIpdu.name" and the suffix
"_SecOcConfiguration".
8682711551924621840 During AUTOSAR import with merge, UdpTp, TcpTp and
HttpTp elements are merged if all their attributes have
set the same values.
8682711552709282064 For AUTOSAR import with merge the messages have
been improved to indicate changes in custom attributes.
8682711553029582005 The AUTOSAR import has been adapted, so that
transformation errors due to preconditions are shown in
the Information View together with all other AUTOSAR
relevant information.
8682711553029101825 The performance for calculating ImEx-IDs during
AUTOSAR import with large tree structures of AUTOSAR
parent hierarchies significantly has improved.
8682711553191072052 AUTOSAR software component updates can now be
started on all classic software component types via
context menu.
8682711553551321825 The import of the attribute txMask and rxMask of the
CAN-FRAME-TRIGGERING has been corrected. Large
integer values are not converted to negative values
anymore.
17938311660911998 Improved update handling of large model trees during
AUTOSAR or DBC import.
8682711553553362052 The import of IMPLEMENTS-SOMEIP-STRING-
HANDLING has been corrected for AUTOSAR 4.4 and
lower.
17938307618971874 Software component update: During a software
component update, the automatic model update
performed when locking the artifacts needed for the
update is handled properly.

© Vector Informatik GmbH Version 10.6 106

 PREEvision 10.5

ID Resolution
8682711552446662043 If a port type is deleted during the AUTOSAR import,
incomplete mappings without source or target are
deleted.

2.5.7 Software architecture

ID Resolution
17938309286651995 Definitions Sets for defining custom attributes can be
assigned to Software Deployment and Software Partition
Package.
17938305258342108 Delegation ports can now be populated on the
background of Composition Type Diagrams, Partial
Composition Type Diagrams, and Software Architecture
Diagrams.
17938307564532052 The Connect Ports with Identical Interfaces
refactoring now correctly connects only ports with
identical interfaces.
17938307939282010 In the SOME/IP Service Instance TP/IP Editor of the
AUTOSAR Adaptive Explorer, the Service ID column
has been renamed to Service Instance ID.
17938308089032051 The automatic figure completion DnD operations can
now be deactivated via a toolbar button in Partial
Composition Type Diagrams.
17938308195152113 The refactoring Change Type To Enumeration Type for
Application Integer Types is corrected and child artifacts
of Application Integer Types are correctly converted.
17938308928020000 Creating new ports for a Port Adapter via the Split Port
refactoring is not possible anymore. The refactoring has
been removed from the context menu.
17938309524372004 In the Ecu Definition table of the SOA & Ethernet
Explorer the metric for the synthesis of MAC addresses
has been improved and can now handle new types of
ECUs correctly.
17938311341171843 In Interface Assignment Diagrams, Adaptive ports for
Composite Types can now be added via palette.
17938311480253039 The performance to open the Port Configuration dialog
with large number of ports has been significantly
improved.
8682711552088162108 Usability and performance have been improved for the
Convert SW Component Type dialog. The dialog now
provides additional filtering options.
8682711552692141913 All valid port types of a software component are shown
for the events Sender Receiver Received Events, Sender
Receiver Receive Error Events, Operation Events, Mode
Switch Events, Mode Manager Error Events, and Mode
Manager Ack Events in the Events Design category of
the Software Design Explorer, and in the Property

© Vector Informatik GmbH Version 10.6 107

 PREEvision 10.5

ID Resolution
View. The visibility of the Mode Declaration Group and
the Target Mode Declaration Group of the Mode Switch
Event in the Property View depends on the mode
activation kind.
8682711553044042013 In the Software Design Explorer, category Events
Design, the tables Sender Receiver Received Events
and Sender Receiver Receive Error Events now
display the Data Elements of the assigned interfaces in
the Data Element column.
8682711552915332052 The Consistency Check „Data type consistency“ has
been removed.
17938306043741029 In the English NLS, the word component "type" has been
appended to the names of the application data types
Application Enumeration, Application Union, and
Application Record.
17938307004132040 To avoid broken data type mappings, Mode Request
Implementation Type Mappings and Application Type
Implementation Type Mappings are deleted if one of their
associated application data type, implementation data
type, or Mode Declaration Group artifacts is deleted or if
they are dereferenced by one of the associated artifacts.
17938294355789393 The relation between Implementation File Proxy, SWC
Implementation and Code Descriptor artifacts is now
properly represented in the Property View of the class
Implementation File Proxy. Relations between the
artifacts can now be set.
17938305951031912 The Start Position of Signal-IPDU-Assignments via drag
and drop in the Model View is calculated correctly.
17938311317882042 For SOME/IP Communication Connector Assignments,
the dereference action in the table on TpIp
Configuration property page.
17938311390142107 The Property View of Bus Connectors shows additional
information about PDUs, signals, and frames.
17938311445712049 An error on Timing property page of Port
Communication Requirements has been corrected.
8682711552764452108 Minimum and maximum values in read-only mode have
been added to the X-Axis, Y-Axis and Z-Axis property
pages axis data types.
8682711553281571998 A menu entry to create a Constant Memory on Internal
Behavior is now available.
17938306961981806 The move ports action via <F7> in Software Architecture
Diagrams and Logical Architecture Diagrams now places
the moved delegation ports on the grid.
8682711552398361914 The refresh of mapping boxes has been improved.
Internal mapping boxes in locked diagrams now refresh
immediately.

© Vector Informatik GmbH Version 10.6 108

 PREEvision 10.5

ID Resolution
8682711552433472052 If an existing port is connected to a component, a new
port will be created. Now the port names (type,
prototype, instance) and assigned interface from the
existing port are taken over to the new port.
8682711552716432013 The Software Architecture Diagram displays the right
icon for Compositions.
17938307342772052 Both references Internal to Physical and Physical to
Internal on Computation Methods are represented read-
only but navigable in the Property View. The add and
delete buttons are still active.
17938307443662108 In the Property View of an axis (X-Axis or Y-Axis), the
drop-down list for the assignment of a Base Type to an
axis on the Configuration property page has been
replaced by a table because multiple Base Types can be
associated. The drag and drop functionality is supported
in the table.
17938307538882108 On the Service Needs Configuration property page of
Supervised Entity Needs, relations between Supervised
Entity Needs and Supervised Entity Checkpoint Needs
have been adapted as follows:
> Supervised Entity Checkpoint Needs can now be
assigned via drag and drop in the corresponding
table.
> A new filter for the Artifact Picker has been
integrated to show only Supervised Entity
Checkpoint Needs and Supervised Entity Needs of
the current Internal Behavior.
17938308234112104 A customized drop action for the Property View of
Assembly SW Connectors has been added. The action
ensures that all instances of the Assembly SW
Connector receive the assigned port instances.
17938309213622113 The Property View has been adjusted regarding the
assignment of a Validity for data constraints. A drop-
down list has been added for assignment.
17938309386102052 In the Property View of an Application Error, a drag and
drop of an Application Error Group is possible now.
8682711552495032051 The Property View of Composition Prototypes now
correctly displays the connected ports.
8682711552867692108 For Axis Literals, the Array Size attribute has been
added to the Constraints property page of the Property
View.
8682711552982362003 On General page of implementation typed artifacts in the
Property View, Implementation Data Type has been
removed.
17938311629282088 On General page for Application Error Packages in the
Property View, the attribute Value has been added.

© Vector Informatik GmbH Version 10.6 109

 PREEvision 10.5

ID Resolution
8682711552101931825 Resizing a column in the Conversion Parameter table
of the Property Editor is now possible by simply
dragging the column separator while holding down the
left mouse button.
17938309033632159 During Show Path operation, a message is shown if a
connection cannot be displayed caused by a missing
connection in the current diagram.
17938311515452113 In tables, minimum and maximum values of Generic
Physical Data Constraints can be properly set.
8682711553140721806 In the Property View of an Atomic SW Component,
Application Partitions can be dereferenced from software
instances.
8682711553281631998 In the Property View of a Constant Memory, the initial
value can be set.
8682711553343442043 The Property View displays the Unit of relevant literal
artifacts.
8682711553285641917 Conditions in State Machines and Activities can be
included in reports out of the box. A Condition has a
customized label {$condition} as an object configuration
which shows the resolved boolean expression. Dropping
a Condition into a report as a placeholder and choosing
the DisplayName as attribute, displays the resolved
boolean expression in the report.
17938307566901918 In State Machine Diagrams, the Condition label can be
reseted. Also, the labels defined in the object
configuration can be displayed.

AUTOSAR Adaptive ID Resolution

17938308156011810 Execution Contexts are now displayed in the SOME/IP
Service Instance Editor.
17938308279211280 Computers, ECUs, Sensor/Actuators, and Execution
Contexts underneath a Component Composite are now
also displayed in the Service Instance Editor.
17938306286902010, The column name in SOME/IP Consumed Service
17938311481711810 Instance SD Editor has been changed from Service ID
to Service Instance ID.
17938308923200000 In the Provided Port Connection Editor and Required
Port Connection Editor the action button for the
creation of ports is now disabled for Port Adapters.
17938309117622003 Toolbar buttons for the creation of Service Instances
were removed from the SOME/IP Service Instance TP/
IP Editor, SOME/IP Provided Service Instance SD
Editor, SOME/IP Consumed Service Instance SD
Editor, and Service Instance to Port and Process
Editor.

© Vector Informatik GmbH Version 10.6 110

 PREEvision 10.5

ID Resolution
8682711552726982010 In the AUTOSAR Adaptive Explorer, the drop-down
menu in the column Process Unit of the Process To
Machine Editor has been replaced by an Artifact Picker
that by default shows all Process Units of the current
Product Line.

Franca import and ID Resolution

export
17938308264962040 Franca export: All available Data Type Packages are
displayed as possible export data in the Franca IDL
Export wizard. Additionally, the error that not all
referenced data types were propagated during the export
has been resolved in the Franca source-based
propagation.
17938311342742040 Franca export: The exact order of method parameters is
maintained during the export.
17938311378662040 Franca export: Due to an invalid schema the export is
aborted if it contains Application Cases of an Application
Union with no application data types assigned.
17938311394782048 Franca import and export: Getter, Setter, and Notifier
attributes of a Property are now considered.
17938311394792048 Franca export: The order of Application Enumeration
literals is maintained during the export.
8682711552515761807 Franca export: It is now possible to export data types of
Data Type Packages contained in the local Library of the
Product Line. Additionally, the name of the Product Line
is taken over for the exported package.
17938311484132040 Franca export: The export cannot contain package
names with spaces or other invalid characters anymore.
17938309053212040 Franca import: Imports of incorrect FIDL files will now be
aborted and an error message will be displayed in the
Information View.

2.5.8 Diagnostics

ID Resolution
17938307506632005 The diagnostic export provides a correct
AsrDataElementRef for Diagnostic Data Identifier
parameters of a Diagnostic IOControl.
17938305189392105 The Quick Search now allows to directly search for the
ID of diagnostic objects, for example, the Routine
Identifier of Diagnostic Routines, and others.
17938307004182113 Deletion of a Diagnostic Data Object does not remove
IDs of other Diagnostic Data Objects of the same
Diagnostic Data Identifier anymore.

© Vector Informatik GmbH Version 10.6 111

 PREEvision 10.5

ID Resolution
17938307370192012 The Select Workspace dialog for Port Interfaces now
allows to select the Software Types container as
workspace. If both the Software Types container and a
Software Types Package are set as workspace, the latter
will be preferred.
17938307544492113 Moving Diagnostic Data Objects does not delete IDs
anymore.
17938307571432113 The drag and drop menu Move before/after <specific
diagnostic data identifier> between Diagnostic Data
Identifiers is removed.
17938307740312007 Software ports with Sender Receiver Interface are
collected again by the Propagate Definition
"R100_DiagMaster_DetailedEE".
17938308161532005 Sender Port Types which are prepared for DID services
in the category SW Type Preparation of the Diagnostic
Specification Explorer are not listed anymore as
prepared for IO control services in the category SW
Instance Referencing.
17938308185752007 A suborder is properly created for Diagnostic Data
Objects created in the DID table of the Diagnostic
Specification Explorer.
17938308272772007 When creating a Sender-Receiver Interface or NV Data
Interface for Diagnostic Data Objects, the attribute
isService is set to false.
17938309053312007 The attribute Diagnostic Value Access of a Diagnostic
Service Need is not set when creating the Service
Dependency of a diagnostic port. For details see
AUTOSAR [constr_1363].
8682711551930692108 During the software type preparation via the IO Control
table of the Diagnostic Specification Editor, now an
Application Record Type is created and assigned to the
data services port representing the actual data of the
Diagnostic IOControl.
17938308185752007 A suborder is properly created for Diagnostic Data
Objects created in the DID table of the Diagnostic
Specification Explorer.
8682711551998222005 During the software type preparation via the IO Control
table of the Diagnostic Specification Editor, now an
Application Record Type is created and assigned to the
IO operation request.
8682711552726661875 Improved performance for opening and switching tables
in the Diagnostic Specification Explorer.
8682711553277282196 When creating a Sender Port Type in the DID or
IOControl tables of the Diagnostic Specification
Explorer, now a Sender Communication Specification is
additionally created. Also, the Data Element in its Sender
Receiver Interface is linked to that Sender
Communication Specification.

© Vector Informatik GmbH Version 10.6 112

 PREEvision 10.5

ID Resolution
17938308763181038 The performance for diagnostic consistency checks
which use metrics has been improved.
8682711552713681995 Diagnostic Trouble Codes can now be set in the formats
HEX, DEC, OCT, and BIN.
17938309056882040, When executing the "Create Communication
17938309334922040 Infrastructure" metric, improved feedback is provided in
the Information View.
8682711553303411909 The Diagnostic Communication Explorer and the path
creation now work with Internal Bus Connectors and all
relevant detailed kinds of ECUs.

Diagnostic import and ID Resolution

export
17938308029872113 Diagnostic import: The import only considers the
CANdelaStudio UUID in the reference Product Line (as
ImEx-Id), the ID is not taken over to the Product Line,
where the import was started.
17938311484122005 Diagnostic import: The name of the reference Product
Line is now set to "RefPL_" +
PREEvisionCANdelaDiagnosticData.ShortName.

8682711552417771875 Diagnostic import: The import of not supported model

versions of the diagnostic exchange format is denied.
53751837, Diagnostic export: The export results of diagnostic
17938308176852005 models are the same regardless of whether started by
wizard or context menu.
17938307384882113 Diagnostic export: If the diagnostic export cannot be
performed due to problems in model transformation, the
status is changed from cancel to error and an error
message is displayed.
17938307956582100 Diagnostic export: A diagnostic export is now possible for
models with software Compositions without software
components.
17938308030652113 Diagnostic export: In the diagnostic export, the ImEx-ID
is considered as CANdelaStudio UUID if an ImEx-ID is
set for an artifact on its corresponding artifact in the
reference Product Line. An ImEx-ID on the artifact itself
is not considered as it might represent the ID of a
different use case, that is an AUTOSAR ID.
17938308048312005 Diagnostic export: Incorrectly modeled Operation
Arguments of Client Server Interfaces for Diagnostic
Data Object will not be exported, for example, if several
Operation Arguments have the name "data".
17938308050832007 Diagnostic export: Different application data types, for
example, Application Integer Types, are considered for
export even if the diagnostic information is collected via
software-hardware mappings.

© Vector Informatik GmbH Version 10.6 113

 PREEvision 10.5

ID Resolution
17938308187512007 Diagnostic export: ContextPortReference (CPR)
have been removed from
AsrServiceDependencyRefs that are created during
export.
17938308192372007 Diagnostic export: The NV Data and Client Server
Interface related to Diagnostic Data Object and SW Port
and their data types are considered for the export.
17938308205162100 Diagnostic export: The diagnostic data exchange with
CANdelaStudio now also supports the Linear Conversion
of a Linear Verbal Table Conversion and Scale Linear
Verbal Table Conversion, in case of only one Linear
Conversion.
17938308264692007 Diagnostic export: Scale Linear Verbal Table
Conversions are not supported in the diagnostic
exchange format and therefore excluded from the export.
17938308325512007 Diagnostic export: If unsupported data types are modeled
in the context of a diagnostic export, these data types are
ignored for the export.
17938311629832005 Diagnostic export: Diagnostic objects that are no children
of the Diagnostic Master are properly considered for the
export to CANdelaStudio depending on their software
realization on the related ECU.
8682711553277502005 Diagnostic export: Default values of attributes, like 0, are
now written to PVCDI if set explicitly in PREEvision.

2.5.9 Communication

ID Resolution
17938304993491003 The toolbar action Create Service Discovery creates an
additional Udp Tp for the client ("ANY") socket.
17938286082770455, The Frame-PDU synthesis now also supports
17938300527352040 Multiplexed IPDUs.
8682711552939001917 A hint for a mandatory port of the LDF Export metric has
been added to the manual.
17938307783892004 On the Coupling Port Configuration property page of
Coupling Ports, the unit bit/s has been added to the
Coupling Port Speed attribute.
17938305543132107 A null pointer exception at the FlexRay Bus Load Table
has been resolved.
8682711552651461917 In the Frame Layout View, an error message reports
when PDU alternatives could not be created due to
missing configuration.
17938307811552040 In the Secured PDU Editor an error when adding an
element been resolved.

© Vector Informatik GmbH Version 10.6 114

 PREEvision 10.5

ID Resolution
17938307811702040 In the Secured PDU Editor the naming of columns has
been correct.
17938305809042040 Under an end-to-end profile, Data IDs can be ordered.
8682711552692181913 The alignment in tables with several Data Elements and
the corresponding communication specification has been
corrected.
17938307161232108 The refactoring Connect Ports (Identical Interface)
works again.
8682711552262722004 Metrics for the J1939 library use case and the J1939
catalog option in new menu have been removed.
8682711552553711998 The Property View of an ECU Interface now displays
Signal Groups in the Selected I-Signals table.
Additionally, drag and drop actions are supported.
8682711552929780000 For a PDU Gateway Routing Entry, some changes
have been implemented for the Routings property page
in the Property View. The Routings property page has
been moved below the General property page. It now
contains the Pdur TP Chunk Size attribute and the Out
Default Value table with the option to create new PDU
Out Default Values.

Signal router ID Resolution

17938308088182088 Signal router: The signal router does not create Generic
Controller Configurations for Ethernet interfaces
anymore.
17938299783622040 Signal router: If the results of signal routing are not
directly applied but reported in the Information View, the
results are highlighted correctly, for example, in Network
Diagrams.
8682711552720781917 Error messages reported by the signal router have been
extended and improved. This applies to a software
component or logical component which is source or
target of a signal which is not mapped to a hardware
component.
8682711553125511995 PREEvision user manual now provides a more detailed
description for the usage of constraints to influence the
signal router.
8682711553653852043 The signal router uses correct data types to calculate the
signal length when routing complex data types to multiple
receivers using system signals.
8682711552558131909 Execution Contexts, Active Stars, and Computers which
do not contain Execution Contexts can now also serve as
gateways and are therefore considered for gateway
creation by the signal router.

© Vector Informatik GmbH Version 10.6 115

 PREEvision 10.5

ID Resolution
8682711552726050000 In case of multiple mapped Signals, the signal router
limits ambiguous signal checks to Signals that are not
attached to any port at all or to at least one port (sender
or receiver port).
8682711553338801029 An error in the signal router has been fixed which did not
allow synthesizing PDU Transmissions for Container
IPDUs.
8682711553062110000 The signal router now does not create Signals for
composition ports (delegation ports) which are no
communication end points.
8682711553262391807 The signal router is now using (instead of deleting) Signal
Transmissions of SW Ports which are associated with
software components that are not directly mapped to
hardware components (indirect composition mappings
exist and are considered).
8682711553076021807 The signal router now creates all Signals for end point
delegation ports of Compositions. The signal router only
routes external client-server communication of Ethernet
Bus Systems or internal Bus Systems but it does not
route external client-server communication over CAN,
LIN and FlexRay anymore.
8682711553048351807 The signal router has been improved in so far that the
signal routing is not aborted in case a new/cheaper path
is found, especially in complex network architectures.
8682711552997071807 The signal router does not consider PDU Transmissions
for non-Ethernet busses. Potentially obsolete PDU
Transmissions are only cleaned up for ethernet channels.
8682711553075471807 When routing System Signals and checking for existing
and usable Signals, the signal router prefers Signals that
are already routed for a current bus or cluster.
342088 The relations between Signal Transmissions and the
signal output port are now updated properly after running
the signal router.
8682711553338801029 An error in the signal router has been fixed which did not
allow synthesizing PDU Transmissions for Container
IPDUs.
17938306994952004 The signal router now considers "must use" conditions on
Bus Connectors if they are applied on the outgoing and
receiving ECU (and its bus connectors).
17938307210601024 If several VLANs are available, the signal router now
handles them in a deterministic way.
17938307369951030 The signal router does not require any locks for
temporary existing artifacts, including marker and flag
changes on related artifacts.
17938307557601794 Highlighting of transmissions now considers ECU
interfaces for highlighting their corresponding Bus
Connectors.

© Vector Informatik GmbH Version 10.6 116

 PREEvision 10.5

ID Resolution
17938307769411024 The signal router now updates complex data type
signals/mappings for signal groups with set data
transformer.
17938307769711030 The signal router now considers the following artifacts as
variant settings for an active variant:
> Set
> Variation Point Set
> Alternative
> System
> Predefined Variant
> Architecture Variant
17938307940771024 In combined routing scenarios with AUTOSAR Classic
and Adaptive communicating via a Port Adapter, the
signal router considers available Signals for connected
UML Data Elements, even if the Signals are only mapped
to classic Data Elements.
17938307948341807 In case signal routing is possible for multiple VLANs,
signal routing always provides in a deterministic routing
result.
17938307959191807 The signal router considers the preferred VLAN for
routing. If no preferred VLAN is available, the signal
routing provides a deterministic routing.
17938308161762005 In case multiple Signals are set as transmittable signal
for a sender or receiver port, the signal router only
checks whether the receiver can receive all relevant
signals. This allows to use the signal router for update
use cases even if multiple senders send the same signal.
17938308174511807 The signal router now considers and reuses existing
transmissions for Fire and Forget Methods.
17938308245522040 The signal router does not fail when called via custom
block and misconfigured ports on Port Adapters are
recognized during routing.
17938308763412040 Signal router considers existing System Signals and
Signals in mixed (Classic/Adaptive) routing scenarios
that were partially routed before.
17938308898421807 If a software component with a Service Consumer is
used to call another Service Provider at the same time,
the signal router now creates a warning in the
Information View.
17938308926091807 The signal router removes unused PDU Transmissions of
type Signal IPDU which do not contain Signal
Transmissions anymore.
17938308926121807 The signal router identifies removed Fire and Forget
Methods and considers all transmitted Signal
Transmissions from the consumer port. All unused
transmissions are removed by the signal router.

© Vector Informatik GmbH Version 10.6 117

 PREEvision 10.5

ID Resolution
17938309273581807 For models with a Port Adapter, the signal router
provides similar results for initial routing and later
updates.
17938309273601807 For models with Fire and Forget Methods, the signal
router provides similar results for initial routing and later
updates.
17938309277122040 If the signal router is called via metric, the currently used
router configuration is now displayed in the error
message.
17938309281082040 The signal router now creates method instances for
getter and setter functions of SOME/IP Properties in
Service Instances.
17938309294661807 The routing of Methods and Properties now leads to two
Signals per port pair, one call Signal and one return
Signal.
17938309294751807 The signal router now properly handles routing scenarios
in combined systems with Adaptive and Classic software
components, even if classic software components send
data to both classic and adaptive software components.
The routing results are deterministic.
17938309296461807 The signal router considers update scenarios in
combined systems with Adaptive and Classic software
components.
17938309296631810 For AUTOSAR Adaptive communication with Events, the
signal router creates one Signal Transmission for
multiple receivers (instead of one per receiver).
17938311324841810 The signal router properly handles update routing
scenarios in combined systems with classic and adaptive
software. Port Adapters in combined classic and adaptive
systems are considered when validating transmittable
Signals during signal routing pre-processing and after
signal routing. Additionally, in case of Fire and Forget
Methods, existing Signals are considered when sent from
Adaptive in combined systems.
17938311341932005 The signal router properly handles update routing
scenarios if the first signal routing is executed in a pure
Classic system, and if for a second signal routing an
Adaptive software component is added. If no interface
mappings have been manually created for the added
Adaptive software component, new Signals are created
to cover Classic to Classic and Classic to Adaptive
systems. The Signal Transmissions are consolidated.
17938311341942005 The signal router properly handles update routing
scenarios if the first signal routing is executed in an
Adaptive to Classic system and the second signal routing
is executed in an Adaptive to Adaptive and Adaptive to
Classic system. Existing I-Signals for client-server
ports in mixed Adaptive to Classic scenarios are handled
correctly.

© Vector Informatik GmbH Version 10.6 118

 PREEvision 10.5

ID Resolution
17938311391581025 In case the signal router is started for a required port,
now the connected provided port(s) are considered
instead. This enables proper reuse of available Signal
Transmissions instead of creating new Signal
Transmissions.
17938311430352051 For signal routing, the Information View provides
additional information about deleted PDU Transmissions
and Signal Transmissions.
17938311457761810 The signal router does not create Signal Groups for Data
Elements with complex data types and with assigned
SOME/IP Method anymore. A Signal or System Signal is
created instead.
17938311637001825 During signal routing, the Name of an Adaptive Service
Instance Port Mapping is now derived from the Name of
the Adaptive Service Instance and the Name of the SW
Port.
8682711551703241810 If the signal router is forced to create new Signals, it now
does not consider existing data type signal mappings for
complex data types. This leads to consistent update
behavior for Fire and Forget Methods.
8682711551793001810 The signal router now creates dedicated Signals for fire
and forget ports by default. Router options regarding
multiple senders are only considered if explicitly set.
8682711551802241030 The signal router now reuses existing artifacts, like PDU
Transmissions, Socket Addresses etc., when routing with
option „IgnoreVariantForReuse“ enabled. In case of
Ethernet routing, reused artifacts are added to the
current variant.
8682711551832901787 When routing complex data types in combined Adaptive/
Classic scenarios, existing Signals that are not useable
for the current ports are not reused anymore.
8682711551834421810 The Signal router now always creates dedicated Signals
for Fire and Forget Methods. The routing order is
optimized so Signals reflecting pure Classic to Classic
communication are created correctly.
8682711551926742051 After setting up the Tx/Rx design in the Communication
Design Explorer and using the signal router, no
duplicate artifacts are created anymore.
8682711551940022052 The signal router now properly creates Event to Signal
Mappings as well as Method to Signal Mappings for a
serialized service.
8682711552499302159 The signal router now calculates all possible routing
paths when using the "BruteForce" algorithm in a
deterministic way.
8682711552540651998 When looking for existing Signals during System Signal
routing, the signal router now prefers Signals that already
have Signal Transmissions on the current bus or have
Signal Transmissions for current sending and receiving
ECU interfaces.

© Vector Informatik GmbH Version 10.6 119

 PREEvision 10.5

ID Resolution
8682711552545052069 In Ethernet, the signal router now creates names for
PDUs and PDU Transmissions in a deterministic way.
8682711552760992010 The signal router does not clean up transmissions for
General Purpose PDUs.
8682711552920011998 The signal router now creates Adaptive service instances
also in case of communication via multiple busses.

Ethernet ID Resolution
communication
17938292522079239 In the SOA & Ethernet Explorer, postings in the
Information View have been improved for the metric
Calculate Header ID.
17938307666912040 The calculation of the Message ID in the SOME/IP
Interface Deployment Editor has been corrected.
17938307801331807 The metric for the AUTOSAR Classic technology
mapping has been corrected. Interface relations are now
set by creating or updating data types.
17938307832182040 Data types of Data Elements/Arguments are now
updated when classifiers of service or adaptive data
types are changed. Application and implementation data
types are considered: if one is set, the other is reset.
17938308850462040 The AUTOSAR Classic technology mapping in the SOA
& Ethernet Explorer has been improvements for update
use cases: data types get updated now and Operation
Arguments will not be deleted anymore.
17938309338122040 A duplicate consistency check "DefPCPAssPrioNotSet"
has been removed.
17938311661050000 In the category Data Serialization of the SOA &
Ethernet Explorer, all Layout Packages that are
contained in Communication are displayed recursively.
17938311667691810 The Service Deployment Editor and the Service
Socket Deployment Editor of the SOA & Ethernet
Explorer are now enabled for all subtypes of Detailed
Electric Electronic like, for example, Computers.
8682711552092072042 The metric for service discovery subscription has been
corrected to create So Ad Routing Groups for services
with properties only.
8682711552421100000 The signal router now takes over data of Services from
abstract UML level to concrete Service Instances in the
Communication layer.
8682711553103332051 The threshold for usage of SOME/IP TP has been
adjusted to a payload size bigger than 1400 byte
according to AUTOSAR SOME/IP Protocol Specification.
17938306277222050 Filtering functions in the Network Topology Editor have
been improved.

© Vector Informatik GmbH Version 10.6 120

 PREEvision 10.5

ID Resolution
17938306277642050 The ECU Definition table supports IPv6 addresses.
17938306642042050 Information about IP configuration has been added to the
ECU Definition table.
17938309264311810 Generic Communication Explorer: The performance of
the Artifact Picker used to display and assign the
communication participant artifacts in the
Communication Participants has been improved.
17938309247681810 The performance of the Artifact Picker used in the
Service Deployment Editor to display the services has
been improved.
17938306962612003 The software deployment synthesis of the SOA &
Ethernet Explorer now builds separate Client Server
Interfaces for every Property and one dedicated interface
for all Methods defined in the Service Interface.
8682711553215501998 On the Identifier Parameters property page for Socket
Connection IPDU Identifiers, the attribute Collection
Semantics has been added.

DBC import and export ID Resolution

17938311322921032 DBC export: Custom attributes like, for example,
GenSigInactiveValue and GenSigStartValue, are now
properly exported in case the communication artifacts are
distributed over multiple Product Lines.
8682711553089142065 DBC export: A consistency check identifies incorrect
modeling of nodes, based on subtypes of the abstract
class ElectricElectronic in PREEvision.
17938308185511032 DBC import: After import of a DBC file that contains
multiplexed messages with a Static Part, the Signal
Transmission of the selector signal only references the
PDU Transmission of the Dynamic Part.
17938308195872004 DBC import: The merge behavior for the DBC import has
been corrected. Two Signals with the same name inside
different frames are not merged anymore.
17938309243111032 DBC import: Multiplexed IPDUs defined with DBC
notation "SG_MUL_VAL_" are supported for the DBC
import.
8682711553302121030 DBC import: For every DBC Signal Group also a Signal
Transmission is created in PREEvision.

Frame PDU synthesis ID Resolution

17938305201232092 Gateway Routing Entries created by the Frame-PDU
synthesis are now also displayed in the Information
View.

© Vector Informatik GmbH Version 10.6 121

 PREEvision 10.5

ID Resolution
17938307943551913 The Frame-PDU synthesis now keeps existing the PDU
Transmissions of long I-PDUs handled by a transport
protocol.
17938309236962024 Extended Information View content to point out missing
and mismatching Bus Types during Frame-PDU
synthesis.
17938309237092024 The Package Selection dialog of the Frame-PDU
synthesis supports the deletion packages via the "Delete"
key.
17938309303511917 The Frame-PDU synthesis completely ignores PDU
Transmissions and Frame Transmissions for multiplexed
IPDUs to support manual modeling.
8682711552287142014 The Information View now shows the complete results
of the Frame-PDU synthesis.
8682711552401662014 Contained PDU Transmissions of multiplexed PDU
Transmissions will not be assigned to Frame
Transmissions by the Frame-PDU synthesis anymore.
8682711552419241917 The Frame PDU synthesis has been adapted to handle
frames without PDU Frame Assignment but existing
Frame Transmissions. That means that Frame
Transmissions of special LIN Frames, LIN Sporadic
Frame Multiplexer and LIN Event Triggered Frame
Multiplexer are not deleted, even though they do not
have PDUs assigned and therefore no PDU
Transmissions can be created.
8682711552431992003 The Package Selection dialog in the Frame-PDU
synthesis shows all labels and icons of artifacts.
8682711552432612003 For XCP PDU modeling, the warning message for the
Frame PDU synthesis result reported in the Information
View has been adapted.
8682711552435892003 Nm PDUs, both with and without assigned Signals, are
considered during Frame-PDU synthesis.
8682711553096202004 The Frame-PDU synthesis does not create unnecessary
Frame Transmissions for J1939Tp-PDUs anymore.
8682711553138491807 The Frame-PDU synthesis now keeps existing PDU
Transmissions and Frame Transmissions if new Signal
Transmissions are added.
17938311661601995 Behavior of the package selection has been harmonized
between Frame-PDU synthesis started in the Model
View or via signal router.
17938301216491992 The Frame-PDU synthesis now also supports
multiplexed IPDUs.

© Vector Informatik GmbH Version 10.6 122

 PREEvision 10.5

Signal and PDU length ID Resolution

calculation
17938307167352042 The length calculation for communication artifacts has
been adapted for transformer-based communication: The
length of a transformer header is only added to the PDU
length and not to the Signal length.
17938309279962159 The length calculation has been improved to support
Implementation Union data types.
17938309373292159 The length calculation for communication artifacts now
correctly handles Implementation Data Pointers for
strings on implementation data type side.
17938309408382159 The length calculation for communication artifacts now
adds the correct padding for already aligned arrays.
17938309408392159 The length calculation for communication artifacts can
now handle a string length attribute from the SOME/IP
Transformation Properties.

LDF import and export ID Resolution

8682711552729751917 LDF Import: Scalar initial values of Signals are now
always imported as integer.
8682711552611791998 LDF export: During LDF export the following checks are
performed:
> Missing LIN Controller Configurations for bus
participants are detected.
> A missing LIN master on the specific Bus System is
detected.
> Checking missing Signal Transmissions for a
communicated Signal is limited to the specific bus.
8682711552061911917 LDF import and export: The handling of LIN configurable
frames has been adapted. It is now possible to either
order the configurable frames alphabetically during the
export or they are ordered according to the order which
was found during the import (configurable via a
configuration properties file
ldf_import_export.properties).

2.5.10 Hardware architecture

ID Resolution
17938307760502050 When creating a Header on a Component Combination,
the behavior depends on whether the Component
Combination already contains child components or not. If
there are no child components, a new Electric Electronic
with contained Header is created. Otherwise, the Header
is created as child artifact of the Component
Combination.

© Vector Informatik GmbH Version 10.6 123

 PREEvision 10.5

ID Resolution
8682711552640442102 Relocating a wire without a Schematic Connection from
one pin to another one has caused an error. Now a
dialog opens where the missing Schematic Connection
can be created if such a wire is relocated.
17938307941342041 The default behavior of Internal Input Types and Internal
Output Types has been corrected. If the attribute
Contact Direction is not defined, Internal Input Types
open to the left, and Internal Output Types open to the
right. In this way the appearance of previous Hardware
Device Template Diagrams and thus the appearance of
Hardware Devices in regular diagrams is not changed.
If no contact direction is set, newly routed Internal
Schematic Connections are brought from the left side to
an Internal Input Type and from the right side in case of
an Internal Output Type.
For Internal In-/Output Types, the contact direction of
Internal Schematic Connections is determined based on
their position in the Hardware Device Template Diagram.
17938309341102083 The calculation of the length and weight of wires and
Cables was updated and now also considers Shieldings
of Cables. The displayed results of the Cores and
Shieldings are only for information and are not taken into
consideration for the total sum.
8682711552432812083 Various online checks and model tree extension rules
have been implemented. They now work with direct
assignment of a Wire Pin to a Wiring Connector as well
as with assignment via Contacting.
8682711553529001037 In large models containing numerous Schematic
Connections, for example, in the Electric Circuit or Wiring
Harness, the complex Java Based Consistency Rule
"Connection between different types of logical
connectors" has caused performance issues. The rule is
still available but has been removed from the "Wiring
Harness" Consistency Rule Group and is no longer
executed as online check.
8682711552945132010 In the New context menu of a Sensor, Actuator and
Sensor/Actuator, the context menu item Hardware and
all submenu items are available now.
8682711553461271994 For Wiring Harness Inline Connectors and Wiring
Harness Multi Inline Connectors, Wire Pins can be
assigned to a Wiring Connector, and a Wiring Connector
can be assigned to Wire Pins via drag and drop in the
Model View.
17938294625869051 External connectors can be copied without external
relations via drag and drop in the Model View.
17938307619951806 After assigning a Header or Wiring Connector to a pin,
the drop-down list of the connector in the Property View
is immediately refreshed.
The drop-down list to select the Header of a Header Pin
has received a special filter which offers the Headers in a
recursive way.

© Vector Informatik GmbH Version 10.6 124

 PREEvision 10.5

ID Resolution
17938307570122112 When selecting multiple Schematic Pins, the pin
numbers of the Wire Pins of the Schematic Pins can be
changed simultaneously in the Property View.
8682711552578201994, A Core Prototype or a Shielding Prototype can be
8682711552578351994 assigned to a Core or Shielding in the Property View. A
drop-down list and a special filter have been added to
select a Core Prototype or Shielding Prototype if the
corresponding Cable has set the origin Cable Prototype.
17938309381191868 In the Property View on the Material property page, the
Material Assignment table to assign and modify a
Material is editable for a Connector Type. For a Header
and Wiring Connector the table is read-only.
17938311321961995 The attribute Long Name was added to following meta
classes and is editable in the Property View:
> Conventional Connector
> Electric Power Distribution Input
> Electric Power Distribution Output
> Ground Connector
> Internal Logical Connector
17938286989688157 In the Property View, the General Connection Type
Parameters property page has been renamed to
General Type Parameters for the artifact classes Case,
CPU Type and Hardware Module Type.
17938309371221995 The Select Connector Prototype dialog now provides a
filter which supports the filtering of Product Lines (Local,
Local and upstream, and Global).
17938308273591877 In the Create and connect new Core dialog, a new
column, the Product Line column, is added to be able to
select the proper Core Prototype. The column filter
persists.
17938309327662083 In the Assign Pins to Contactings table via which pins
can be assigned to cavities of Plug-in Locations, a
dereference button has been added for the Hardware
Device Pin column.
17938311665181037 In the Assign Pins to Cavities table, the check box in
the Wire at Contacting column can now be activated
and deactivated with a single click.
17938311697332083 In the Assign Pins to Cavities table for Wiring
Connectors and Headers, a dereference button has been
added for the Wire Pin and Component Pin columns.
8682711552654382112 When working with Concept Fuse Relay Boxes, the
creation of the realizing Schematic Connection in the
Assign Fuse Relay Box to Concept Fuse Relay Box
table is now possible in the Realizing Schematic Pin
column.
8682711553306161038 No performance problems occur anymore when opening
the Assign Fuse Relay Box to Concept Fuse Relay
Box table due to the performance improvements of the

© Vector Informatik GmbH Version 10.6 125

 PREEvision 10.5

ID Resolution
Artifact Picker. This especially improves the loading
time of the Artifact Picker which does not interfere the
performance of the Assign Fuse Relay Box to Concept
Fuse Relay Box table anymore.
17938309340592083 The "Wiring Harness Demo Model" Product Line in the
PREEvision demo model has been enhanced with new
content:
> Diagram configuration with Title Block
> Special diagram configuration with Title Block for
Electric Circuit Diagram
> Icons on Schematic Connections having
distinguished bus types assigned to a Bus System
> Added Wiring Harness Multi Inline Connector which
separates the Motor Harness from the new Switch
Harness
> Added logical connection types for Power
Connections, Ground Connections, and Conventional
Connections.
> Resolved the reuse of the Sensors "B1" and "B2" to
separate artifacts.
> Additional Cable Types
8682711552738522083 The model tree extension rules in the "Wiring Harness
Demo Model" Product Line in the PREEvision demo
model have been reorganized and completed.
8682711553076072083 The newly implemented feature of displaying icons in
labels in a diagram has been added to the "Wiring
Harness Demo Model" Product Line in the PREEvision
demo model. This new feature is available at all bus
system connections in the "Electric Circuit WH-Demo"
Electric Circuit Diagram.
8682711553342602083 The labels of Conventional Connections, Ground
Connections and Power Connections use the same label
configuration as the Bus System in the "Wiring Harness
Demo Model" Product Line in the PREEvision demo
model.
17938307556552034 When importing an EPDM file containing a pin without a
ContactType, no Material is created, and none is
assigned to its Pin Type. If a pin neither has a Pin Type
nor a Material, no Pin Type is created and assigned.
8682711552039102034 The handling of renamed connectors with identical IDs of
different versions of the same component has been
adapted and corrected for a custom-specific import into
an import library Product Line.

Diagrams of the ID Resolution

hardware architecture
17938308152221037 When connecting a wire in a Wiring Diagram, the
performance with respect to finding possible connection
targets and displaying airlines has been improved.

© Vector Informatik GmbH Version 10.6 126

 PREEvision 10.5

ID Resolution
1792439489051 In a Wiring Diagram the overlapping distance of a
Header in a component is equal on both sides when
displaying Schematic Pins via the Show/Hide Headers
and Pins dialog. If only one Schematic Pin shall be
displayed in a diagram with a grid of 10x10, the
overlapping distance is unequal. This is caused by the 30
pixels default size of a Header in a Wiring Diagram.
Unintended separating of a Header on one component
edge and moving Schematic Pins when adjusting the
Header size does not longer happen.
17938307262231804 Applying the function Split Connection on a checked-in
Wiring Diagram correctly results in a check-out and the
application of the function.
17938308923242112 In a Wiring Diagram, a Single Wire can be split when a
Schematic Pin is dropped on it. If a naming convention is
available, this naming convention is used after the drag
and drop action, otherwise the suffix "_2" is added to the
newly created Single Wire.
17938311629832081 In Wiring Diagrams, the pop-up bar is displayed again
when selecting a Splice or a Schematic Pin.
8682711553146062099 Wiring Diagrams which contain a wrong label on a cable
symbol, can be opened again. Creating a wrong label on
a cable symbol is not possible anymore.
17938308054452083 The error highlight for cable symbols in a Wiring Diagram
is now instantly calculated and therefore activated or
deactivated.
8682711552639693065 When selecting a Cable (with active highlighting), the
highlight behavior in the Wiring Diagram is equal to
selecting a Cable Type. The pins of the Core and
Shielding are highlighted as well.
8682711553124341912 Wiring Diagrams containing a cable symbol with a
constraining object configuration can be opened without
displaying an error.
8682711553270132046 Relocating a wire in a Wiring Diagram from one
Schematic Pin to another which has the same Schematic
Connection does not lead to an error anymore.
17938307169912112 Wiring Connectors of Wiring Harness Inline Connectors
are properly displayed in a Wiring Diagram via the
populate function <F8>.
17938309118222045 The error in the context of opening Wiring Diagrams
which has caused a deadlock, has been resolved.
17938309315761037 In a Wiring Diagram, a component can be removed from
the diagram via the shortcut <Del>.
17938301235711025 After applying the function Split Connection in a
Network Diagram, Electric Circuit Diagram or Wiring
Diagram, both parts of the split connection will show the
updated connection label.

© Vector Informatik GmbH Version 10.6 127

 PREEvision 10.5

ID Resolution
17938308840512112 In Wiring Diagrams and Wiring System Diagrams it is
checked whether pins of Wiring Harness Inline
Connectors are displayed according to their assignment
to the Wiring Connectors of the Wiring Harness Inline
Connector. If the pin assignment to the Wiring
Connectors is changed, for example, as a result of the
refactorings Change Wire Pins or Reflect Wire Pins,
the display is repaired in diagrams as well. Schematic
Pins with inconsistent assignment of the Wire Pins to the
Wiring Connectors are removed from the diagram. The
repair mechanism works temporarily. To persist the
changes in the model, diagrams must be locked.
8682711553265912034 The diagram framework has been improved to correctly
remove corrupt connections from the Wiring System
Diagram.
17938307606732112 Figures for Shieldings are now automatically removed
from system diagrams if the reference to the Cable or the
Cable itself was removed, and the diagrams can be
opened properly again.
17938309412512041 In the Wiring Diagram or Electric Circuit Diagram the
Create or Connect a Schematic Connection dialog is
not directly shown again after a Schematic Connection
was already selected in the dialog.
8682711552335141843, In the Wiring Diagram or Electric Circuit Diagram, a
8682711552335151843 Schematic Pin cannot be dropped from the Model View
into the diagram anymore, if the Schematic Pin is already
displayed in the diagram or Section where its component
is located.
8682711552437741994 Moving Schematic Pins on a Header in a Wiring Diagram
or Electric Circuit Diagram is more tolerant. Even if the
diagram feedback shows the edge of the component, the
Schematic Pin is correctly dropped on the Header. An
unintentional moving of other pins does not happen
anymore.
8682711552588051843 When connecting pins in a Wiring Diagram or Electric
Circuit Diagram, the airlines to possible targets also show
the label of the applicable target pin. Thus, the default
label is preferred if one exists. Otherwise, the first
available label is displayed.
8682711553162301268 The New Component Circuit Diagram wizard and the
Change Input Configuration and Change Output
Configuration dialog for the Component Circuit Diagram
now have been adapted to each other concerning the
Selection of the initially displayed inputs and the
Selection of the initially displayed outputs.
Deselecting the check boxes of the Schematic Pins does
not deselect the check box of the logical connector
anymore. In addition, only selected elements will be
displayed in the diagram.
17938307942442041 Using reference lines to enlarge components does not
interfere with the routing as long as the reference line
does not intersect the axis of the Schematic Pin or its fan

© Vector Informatik GmbH Version 10.6 128

 PREEvision 10.5

ID Resolution
area. In the second case, waypoints on fans and the
connected segments are preserved to provoke as few
changes as possible in the line routing.
8682711552502922112 Checked-in diagrams are not checked-out anymore when
reusing and committing them.
17938308161071037 Canceling a previous drag and drop action prevented a
committed Wiring Diagram from being edited. The cancel
state is now correctly reset so that canceling a previous
action does not affect the execution of further actions.
17938309300511877 The diagram synchronization mechanism has been
corrected. Now, performing a populate action on a
checked-in diagram does no longer lead to model
inconsistencies. The populate action is performed
successfully.

Wiring harness ID Resolution

autolayout diagram
17938307398262112 The mechanism behind the refactoring Create
Autolayout Diagram has been improved. The algorithm
can now correctly handle Splices that are connected by
several Single Wires.
17938307704641914 Improved auto-layout refactoring regarding Splice
networks connected via Single Wires.
17938308754632109 When creating an autolayout diagram, the Section in the
target diagram is enlarged to the right in such a way that
configuration artifacts like, for example, the Positionlist
table or a Title Block, are positioned on the right end
without causing any overlaps with the contained diagram
artifacts. This behavior is independent of whether the
original diagram is checked-in or not.
17938308754652109 Creating an autolayout diagram for a checked-in diagram
works properly now, particularly for diagrams with Title
Blocks containing images.
17938308772892081 When creating an autolayout diagram all labels
(embedded, midpoint and endpoint labels) are displayed
instantly.
17938307568522073 If referenced metrics in a label configuration could not be
found or multiple metrics with matching names were
found, a corresponding message is reported in the
Information View.
8682711552101902036 The geometric graph algorithm within the metrics to
create a model-based autolayout Wiring Diagram has
been improved. Exceptions do not occur anymore. Other
error messages have been improved.
8682711552376552036 The algorithm of handling Splices in an autolayout Wiring
Diagram has been improved in case the model-based
metric block has been used.

© Vector Informatik GmbH Version 10.6 129

 PREEvision 10.5

ID Resolution
8682711552510132036 In the context of model-based autolayout Wiring
Diagrams an error has been resolved in case wires were
connected to a Splice on both sides of a Wiring Harness
Inline Connector.
8682711552540612036 The autolayout Wiring Diagram algorithm has been
modified in a way that no exception occurs anymore in a
certain constellation of artifacts.
8682711552544622036 The autolayout Wiring Diagram algorithm is now able to
process multiple connected wires and to rejoin
Schematic Connections. Especially if wires are modeled
multiple times due to variant reasons (LHD and RHD).
8682711552545162036 For the creation of autolayout Wiring Diagrams only
propagated artifacts are taken into consideration. This is
relevant for a Splice with only one propagated wire, for
example.
8682711553036282036 In an autolayout Wiring Diagram the placement of fan
way points of the bottom area has been corrected. New
generated diagrams are correct by default. Existing
diagrams need to be newly created.
8682711553036512036 In an autolayout Wiring Diagram an exception has been
added for object configuration artifacts. This allows a
refresh of, for example, Title Blocks if a layout restricted
diagram requests a lock due to a change.
8682711553036562036 Splice sorting has been improved for an autolayout
Wiring Diagram. This results in fewer unnecessary
crossings of wires.

Refactorings ID Resolution
17938308312161029 The Set a Type from the current Product Line
refactoring does no longer delete the local instance
artifacts of a Plug-in Location if they are still in line with
the newly assigned prototype.
17938309328881037 The Change Type to Shielding refactoring for a Single
Wire into a Shielding prevents the selection of a Cable
which already contains a Shielding in the Select Cable
dialog.
17938311670362081 Sorting Schematic Pins via refactoring only affects the
artifact on which the action was executed. Other
representations, for example, in another Section or
diagram area of the artifact are not affected by the
sorting.
8682711552409022062 When executing the pin sorting refactorings on a Header,
Wiring Harness Inline Connector, or Wiring Harness Multi
Inline Connector in an Electric Circuit Diagram, Electric
Circuit System Diagram, Wiring Diagram, or Wiring
System Diagram, the corresponding diagram is locked
now to preserve the changes.

© Vector Informatik GmbH Version 10.6 130

 PREEvision 10.5

ID Resolution
8682711552486221868 When merging different Bus Systems via the Merge Bus
refactoring, the assigned Schematic Connections are all
represented by the surviving Bus System after the merge
operation.
17938311484662112 The Reflect Wire Pins refactoring on a Wiring System
Diagram resets the labels of the Wire Pins according to
the label configuration of the Wiring System Diagram.
17938307349782112 Wires are now correctly displayed in Wiring System
Diagrams after a refactoring from an Electric Circuit
System Diagram.
17938293419069328 When refactoring a Network Diagram or Network System
Diagram to an Electric Circuit Diagram or Electric Circuit
System Diagram, an Information View entry displays all
logical connectors which cannot be displayed in the
newly created diagram.
17938307713042041 The refactoring of Wiring Diagrams and Wiring System
Diagrams to Electric Circuit Diagrams and Electric Circuit
System Diagrams has been improved regarding the size
and positioning of components and their inner artifacts.
Moreover, when applying this refactoring, the positioning
of Schematic Pins was improved so that the position of
pins remains the same, if possible. This ensures that the
routing behaves in a similar way like in the source
diagram.
17938307572791912 The synthesis of slots and cavities at a Connector Type
no longer considers the pin numbers of Wire Pins. The
first created cavity always starts with the cavity number
1.

Synthesis ID Resolution
17938307688011877 During wiring harness synthesis, the missing relation
between Bus Connectors and the existing Bus System is
created to prevent the creation of obsolete Schematic
Pins.
17938307697031877 When synthesizing new Cables during wiring harness
synthesis, the correct Cable Prototype is considered to
create Cores based on the same Cable Prototype.
17938307570302034 A circuit synthesis on a connection with a Splice works
properly, now.
17938308925201914 An error during a circuit synthesis which caused a
concurrent modification has been resolved. The error
occurred when a wire had no connection to a Schematic
Connection and the circuit synthesis was triggered
multiple times.
8682711552971212083 The settings in the Circuit Synthesis dialog are now
persisted for the current session.

© Vector Informatik GmbH Version 10.6 131

 PREEvision 10.5

Object and label ID Resolution

configuration
8682711552291062039 Labels for hardware types are now working via an object
configuration. Previously, empty strings were displayed
at the placeholder positions if an object configuration was
present on the label.
17938311408472041 When adding Hardware Devices to a Wiring Diagram or
Electric Circuit Diagram, or creating Hardware Devices in
the diagrams, the labels for the Hardware Devices are
displayed according to the label configuration defined in
the Label Configuration view.
17938308131271992 Missing artifact classes for hardware artifacts have been
added to the label configuration of a Network Diagram. A
switch does not have its own object entry since it has the
same meta class as Active Star.
8682711551845672112 Labels on Single Wires in a Wiring System Diagram are
created according to the configuration in the respective
Object and Label Configuration Delta File.

Wiring harness router ID Resolution

8682711552944961031 Wiring harness router: A Cable containing wires with
different start and end pins and ending at different
Connector Locations have caused an error during wiring
harness routing. Now, the routes are checked by
comparing the first branch based on the start topology
artifact. If there is a mismatch, the start and end pins are
swapped, and the wiring harness router can run without
error. Furthermore, the variant check has been added.
8682711553142191782 Wiring harness router: In the wiring harness router
wizard, the drop-down lists to select the target mapping
packages have been replaced by a [Select] button to
open a package selection dialog.
The selected mapping packages are displayed with their
corresponding paths in the model.

Variants ID Resolution
17938308932291038 When opening the context menu Set Workspace on a
Harness Variant Package, the context menu now only
contains the Set Workspace Harness Variant Package
context menu entry.
8682711552944951031 Parallel wires in different variants lead to faulty variant
propagation in the wiring harness router. If the option
Identify existing artifacts which could be used
multiple times without considering the variant is
activated, the wire in the active variant is routed instead
of a wire which is not in the active variant.

© Vector Informatik GmbH Version 10.6 132

 PREEvision 10.5

KBL import and export ID Resolution

17938309232772036 KBL import: When importing a KBL file, contained
Control_points of a Center_curve are imported
into PREEvision as a 3D Way Point below a Topology
Segment.
17938309368462083 KBL import: Materials with the same Material_key of
the KBL class Part are merged during the KBL import.
Materials of Pin Types with the key Plating_material
are considered separately, and are not merged with the
others from Material_key.

17938311409241806 KBL import: The KBL import is properly executed

although the KBL attribute
Logistic_control_information is longer as
10.000 characters. In such a case, a warning is reported
in the Information View.
8682711552693651204 KBL import: When importing a KBL file with Fuse Relay
Boxes not every Connector_occurrence creates an
own Fuse Relay Box anymore. Related
Connector_occurrences of one
Component_box_occurrence do only create one Fuse
Relay Box in PREEvision. The mappings are set
properly.
17938308184671912 KBL export: The Material with the usage "Plating" which
is assigned to a Pin Type, is exported to the attribute
Plating_material of a General_terminal in the
KBL export file. The first Material found with another
usage is exported to the attribute Material_key.

17938307522901031 KBL export: Wire Types are properly exported during a

full model export to KBL (General_wires), now. They
are also exported if they have multiple instances of
Single Wires, conductors and Shieldings but none of the
Single Wires is contained in the export model.
17938308035221995 KBL export: During KBL export, temporary artifacts
(NotParsableFormulas) were created for all Wiring
Modules, Harness Configurations and Variation Point
Sets in the current model scope. If one of these variant
artifacts was within a write protected Product Line, the
KBL export was aborted with an error. The KBL export
now creates these temporary artifacts only for
propagated variant artifacts, and it is assumed that the
user does have write rights.

2.5.11 Geometry

ID Resolution
11912 Tables and combined tables can now be moved freely
within Sections and also into and out of Sections. They
are now both ignored by the check that prevents artifacts
to be shown twice in the same Section.

© Vector Informatik GmbH Version 10.6 133

 PREEvision 10.5

ID Resolution
17938309342182036 The workspace defined on a Geometry Package is now
considered when creating topology artifacts inside an
Installation Space within a Geometry Diagram.
17938309312032083 The refactoring Set Topology Coordinates, which can
be started on a Geometry Diagram, now also works with
Connector Locations.
17938307346571037 The click target within a Geometry Diagram is now
determined correctly. If a table is in the upper left corner
of the diagram, it is not always selected when clicking
somewhere else.
17938309328932083 The bundle diameter calculation of Topology Segments
was improved. In addition, a new calculated label was
added to the demo model.
8682711551829572039 Formatting of numbers via label configuration is possible
again.
8682711551971991914 The logging of changes in a Geometry Diagram was
improved. Commit errors caused by rearranging artifacts
in the diagram are not displayed anymore.
8682711553066032036 The Show Topology Placement Condition in
Component Package table can now be opened on a
Hardware Component Package.

2.5.12 Product line engineering

ID Resolution
17938308928012068 The creation of hierarchical Assets only adds the root of
a tree to an Asset if artifacts below the root are included
as well. This prevents invalid artifact assignment to
Assets.
17938308928022068 The creation of hierarchical Assets now provides a
detailed error message if non-versioned artifacts are
assigned to an Asset. This eases error identification and
fixing propagation rules.
17938307942792108 During a refresh operation of an Asset, where an already
removed child Asset was tried to be removed again, an
exception occurred. This issue has been resolved.
17938309232782082 During the revocation of an Asset, no exception occurs
anymore if some artifacts of the revoked artifact are out
of scope.
17938309246722082 A merge no longer changes the checked-in parent
reuses.
17938307954151855 Non-versioned artifacts are excluded from Propagate
Definitions to show rule modelers that these artifacts can
be assigned themselves to Assets.

© Vector Informatik GmbH Version 10.6 134

 PREEvision 10.5

ID Resolution
17938309365222112 The check-in validator for the Asset hierarchy now only
checks the core/boundary artifacts of a hierarchy path,
not of the sibling path.
17938311451952049 Localized attributes retain their value after delivery via
Asset.
8682711552943021917 A new error message is provided when copying Product
Lines via a copy/reuse clone operation where types are
copied but their instances are reused.
8682711552436172108 After replacing an instance with the latest revision, the
type of the instance is not referenced with a type that is
located in the downstream Product Line.
17938307718062034 A repeated import of the same import file containing the
same import data, does not check out any Propagated
Assets anymore.
8682711552049021825 After an import with model merge operation, which has
caused the name change of a core artifact, the
corresponding Asset is checked-out.
17938309309402049 Refactoring a Table Proxy now also works if the Table
Proxy is reused as an effective core artifact of an Asset.
17938307381192108 Metric class files are correctly loaded after several Metric
Packages have been moved.
17938309213672101 The check-in block in the metric now returns a correct
error message when the check-in validator of the Asset is
triggered.
17938308077601877 The exception error after removing a non-existing save
point when using the customized block "Update from
Predecessor (multi)" has been fixed.
8682711553454762108 The cache management of the Asset Factory has been
improved. The removal of Assets as part of an Asset
update could have led to an exception.
8682711552015141914 In a system Asset, the Slot Prototype, Slot Type, Cavity
Prototype, and Cavity Type for a Wiring Connector are
propagated.
17938307739972012 The data type of primitive specifications is now included
in software component type Assets.
8682711552410962003 During the Asset creation, the Mode Request
Implementation Type Mapping and the mapped
implementation data type are now propagated for the
Mode Declaration Group. Top-level Assets can be built
now for Mode Declaration Groups.
17938307304442108 Asset propagation of application data types includes
Calibration Parameter Record Layouts (CPRT). This
means to include the Data Type Package as well, as
CPRTs are only versionable by a parent.
17938308077882012 SWC Implementations are versionable themselves. The
parent is not collected anymore by the propagation rule.
This prevents the unnecessary check-out of packages.

© Vector Informatik GmbH Version 10.6 135

 PREEvision 10.5

ID Resolution
17938308194691995 Value specifications of Implementation Data Types, for
example, for initial or invalid values, are now included in
Assets containing the data type because they are part of
the data type definition.
17938308050132012 Assets for software instances now pick up existing
Assets for Diagnostic Trouble Codes and Diagnostic
Data Identifiers.
17938308061592012 The Diagnostic Trouble Code propagation definition
propagated artifacts which belong to Diagnostic Event.
This part has been moved to the Diagnostic Event
propagation definition.
17938308272822112 The navigation to non-integrated artifact in the Model
View is now possible from the Information View, tables,
or diagrams.
17938308319502112 The navigation to Assets via model queries, tables,
diagrams, or Information View is possible now.
17938309365232112 Detailed information and improved messages are
provided in the Information View in case of invalid
constellations of core or boundary artifacts in Asset
hierarchies during check-in of Assets.
8682711552023842023 The message in the Information View has been
enhanced for the "Extract Asset to Product Line for
Agreement" use case.

Asset update ID Resolution

17938306339461877 The incorrect revocation of the integration in foreign
Assets during Asset update has been corrected.
17938307232182100 The instance which is not referenced with the Asset as
core or boundary is not changed to the reused type after
Asset update when the type is referenced in the Asset.
17938307302222052 During Asset update, when a child Asset is deleted, the
parent of the updated Asset, for example an Asset
Package, gets a shared lock instead of an exclusive lock
like before.
17938307453881877 After an Asset update, too many artifacts in the foreign
Asset were revoked unnecessarily. This problem has
been resolved.
17938307469321877 The wrong check-out of foreign Assets after Asset
update due to neutral changes of boundary artifacts has
been corrected.
17938307555342112 The parent Asset is no longer considered as foreign
Asset for the child Asset being updated. Thus, there is no
revocation of the parent Asset when an artifact is
referenced in both, the parent Asset and the child Asset
being updated.

© Vector Informatik GmbH Version 10.6 136

 PREEvision 10.5

ID Resolution
17938307556592082 The identification of conflicts of updated artifacts in
foreign Assets during Asset update has been improved
through technical optimization, for example, avoiding
unnecessary hash map generation.
17938308048642101 An instance is not checked-out anymore if the type was
not changed during Asset update.
17938309243282112 An Asset update problem has been fixed for the case the
parent Asset of the Asset being updated has an
incorrectly located core integration or boundary
integration.
17938309246122082 An Asset update from predecessor is now possible if
reused types, and their reused instances are also
referenced in the Asset.
17938309247292082 An Asset update now works properly when dereferencing
the type from the new revision of the Asset, but the
instance is always referenced with the Asset.
17938309300481030 Updating a structural type-of instance after an Asset
update now works correctly when multiple ports of the
type were removed during the update.
17938309309392049 The replace from history logic of an Asset update with
type change now correctly handles order-relevant
composites of non-versionable child artifacts.
17938311466212112 Moving core artifacts from a deleted child Asset to
another parent or child Asset is now supported by Asset
update if the artifact is not integrated in the Asset to be
deleted during the update.
17938311466432112 The missing check-out status of a Propagated Asset
during the Asset update in the migration use case is now
fixed.
17938311552722049 An Asset update now keeps the local reuse sequence for
child artifacts of newly added core/boundary artifacts of
the Asset.
8682711553258601030 The unintended loss of a type-of relation during Asset
update has been resolved.
8682711553315951030 An Asset update can be carried out properly now, if a
change refactoring to a new meta class has been carried
out for a contained artifact and the related type has
undergone a version change during the update.
8682711553356001806 An Asset update now correctly considers the tag "deny
relation copy context" for Product Line external relations.
17938311642222049 External relations of hidden artifacts are now transferred
to targets during Asset update.
17938308210251877 The incorrect revocation of the integration in foreign
Assets during Asset update has been resolved.
8682711552632661995 The abstraction link is the only matching criterion for the
core artifact of the Asset during Asset update from
predecessor.

© Vector Informatik GmbH Version 10.6 137

 PREEvision 10.5

ID Resolution
8682711552635422101 The correct error message is displayed if the user does
not have the required permissions for some core artifacts
during the Asset update.
8682711552922532113 An Asset cannot be updated if there is an incorrect type-
of relation between the Asset to be updated and the
updating Asset. In this case the Asset update is
interrupted providing a correct error message.
8682711552964651913 After Asset update, an integration via move is
interrupted, if the target parent artifact is checked-in or is
protected as core artifact in an Asset.
8682711553135811806 Inconsistencies in the model have been corrected, which
required a forced restart of the client, after an Undo all
own Locks operation has been carried out after an
Asset update.
8682711553770092113 During Asset update unnecessary artifacts have been
added to the scope which has caused a long waiting
time. This problem has been resolved.
8682711553548563043 During Asset replace from history unnecessary artifacts
have been added to the scope temporarily. This problem
has been resolved.
17938309028792082 Replacing Assets on the Version History property page
via the [Replace with selected version] function or via
the customized block "Asset Update from Predecessor"
now sets the correct predecessor for the child Assets.
8682711553148011029 The relations between upstream and downstream
Product Lines are now correctly handled during Asset
update.
17938306638582112 Update indicators for Assets (exclamation mark icons)
are correctly displayed on the successor Assets even if
the successor Asset is out of scope.
8682711554187901030 An Asset update could not be executed properly, if for
the predecessor artifact a meta class change has been
carried out and the relation of the changed artifact has
been deleted. This error has been resolved, and the
Asset update can be executed successfully.
8682711551960381914 During the calculation of update indicators for core
artifacts of Assets, possible abstraction cycles are
identified, and no abstraction loops are created anymore.

Asset integration ID Resolution

17938307469611877 The conflict detection for a manual integration merge for
an Asset with respect to an Asset composition has been
enhanced.
17938307710392040 Improved performance for Asset reuse and automatic
integration.

© Vector Informatik GmbH Version 10.6 138

 PREEvision 10.5

ID Resolution
17938309246102082 Integration merge during automatic integration of an
Asset with a checked-in Asset model or Asset package is
possible, now.
17938311323391868 In case of a Propagated Asset the parent is checked for
integration objects.
8682711552486242100 Multiple reuses of an artifact in different Product Lines as
propagated artifacts in the Propagated Asset can now be
integrated automatically after Asset update.
17938311530121029 The problem of non-synchronous reuses of Asset
contents during Asset integration, which was caused by
to:n type-of relations, has been resolved.

Substitution ID Resolution
17938309196642082 The Identity Configuration of the Compare Configuration
is now correctly considered for pairing artifacts during a
substitution.
17938309198152112 The memory leak problem when substituting artifacts
containing many child artifacts is now solved by cleaning
up the substitution cache.
17938309330402082 A substituted artifact and its Asset are now always
deleted after substitution.
17938293430318157 An Asset is used from an upstream Product Line only if
the user confirms the substitution. If the user cancels the
substitution, no Asset is used in the downstream Product
Line.
8682711552015412045 For an unsupported substitution of artifacts with structural
type-of relations, an error message is displayed, and
detailed messages provided in the Information View.
17938311553721877 In the Review and Confirm Substitution table, a
matching by abstraction link has a higher priority than a
matching by name.

Performance ID Resolution
17938307765692012 Major performance improvement for keeping the
selection in large tables upon a table refresh.
17938307920221877 The performance for calculating the matching pairs for a
component substitution has been improved.
17938308032222104 A severe performance issue related to detecting
conflicting relations during Asset updates has been fixed.
8682711552337792100 The Asset update performance has been improved by
optimizing artifact visibility checks.

© Vector Informatik GmbH Version 10.6 139

 PREEvision 10.5

ID Resolution
17938308312202070 The performance for refreshing the Asset/Add-in drop-
down list within the Asset/Add-in View after a model
change, for example, an Asset update, has been
improved.

2.5.13 Variant management

ID Resolution
17938311664562102 Fixed, clarified, and internationalized the error messages
for the translation of formulas. The error message
appears for artifacts in table columns with the described
object configuration if they lack the necessary relation to
a Pre Build Variant Condition.
17938307945391801 The deletion of an active variant is now properly
deactivating the variant. Also, the user interface is
refreshed.
17938308086021874 The active variant decorator is now also refreshed for
members of virtual folders.
17938308131472011 The meta class name of active variants is not displayed
in the status bar anymore.
17938308157062039 The progress dialogue for variant activation provides
more detailed information.
17938309328802011 Due to improved performance, the warning dialogue has
been removed for switching active variant while diagrams
are opened.
8682711552494743071 Changing the alias name of Object LHS does not affect
the execution of Variant Propagation Rules.
8682711553111582039 Conditions that have no assignment are not considered
in the guard calculation of Variant Propagation Rules
anymore.
17938308048301875 In the VM Architecture View, the Concept Space
combo box is refreshed now when opened.
17938307437301804 In the VM Template View, the content in the Alternative
column is now sorted in ascending, alpha-numeric order
by default.
17938307811612011 A drag and drop of an Integer Literal from the Artifact
Picker into a Post Build Variant Criterion Value Set in the
VM Explorer creates a reuse instead of moving it to a
new parent.
17938311515802039 A tooltip on deactivated variant selection combo box in
Set Content View hints to use the Artifact Picker.
17938293833629393 Checks for the AUTOSAR compliant variant
management are now correctly described as Consistency
Rules in the manual.

© Vector Informatik GmbH Version 10.6 140

 PREEvision 10.5

ID Resolution
17938306914162107 The function Add to Active Set is consistently named in
contexts menus as well as toolbar actions and tooltips.
17938311586971884 An error message informs that the function Evaluate
Customer Feature to Values Map is executed on a
Customer Feature to Values Map that is not located in a
Product Line.

2.5.14 Functional safety

ID Resolution
8682711551958091030 FMEA Ticket artifacts no longer refuse the reuse of
reusable parent artifacts.

2.5.15 Change and release management

ID Resolution
8682711552487071918 In a previous PREEvision version, the Planning Editor
was renamed to Project Plan. The screenshots in the
user manual have been updated.
17938307544922111 The Change history view now properly displays multi-
lined strings.
17938308185512040 Artifacts that contain Light Weight Attribute values
without an Attribute Definition can be opened in the
Change history view without error.
17938307953401030 The Change history view now displays the life cycle
state which was active when a change was made.
17938307822621030 Changes of placeholder attributes are now also displayed
in the compact display mode of the Change history
view.
8682711552262362100 The widget for settings dates, which is available in tables
and in the Property View, now correctly saves directly
typed-in changes.
8682711553143622102 When a Change Profile exists for a meta class, Tickets
on which the changes are tracked are offered during the
commit. It is now possible again to provide a preselection
of Tickets depending on the meta class of changed
artifacts.
8682711552270921030, For the Comment and Chat View, hidden table columns
8682711552439121030 are now handled correctly. Comments are now properly
displayed.
8682711552761161918 For displaying the time frame of the Project Plan, the
start and end dates of the contained Work Packages is
considered. The displayed time frame is limited to two
weeks after the latest end date of a contained Work
Package.

© Vector Informatik GmbH Version 10.6 141

 PREEvision 10.5

ID Resolution
8682711552985021918 In the Gantt view of the Project Plan, the end date and
the length of Work Packages is displayed according to
their spent effort and the remaining effort and is
calculated based on the start date.
8682711552487061918 The resources view in the Project Plan correctly
calculates the effort of Work Packages if Backlog Items
are used.
8682711552944961918 The actions in the Project Management context menu
work if multiple Work Packages or multiple Planable
Artifacts are selected.
8682711551900442023 The German naming for Artifact for Agreement has been
improved.
17938307536742080 In the Review Table, comments can now be added via
copy and paste into the New Comment dialog.
17938307698362101 When changing a voting status, the Review Table
structure is not changed. Only the visible table properties
are updated.

2.5.16 Test engineering and test management

ID Resolution
8682711551986743043 Manual Test Sequences can be copied and pasted in the
Model View.
8682711553292981859 In the PREEvision demo model, the synchronization
metrics for ASIL and ASIL Decomposed have been
adjusted.
8682711551903952039 Test coverage metrics are no longer listed in the context
menu of the meta class Customer Feature.
17938311673682023 The Test Item Coverage table has been renamed to
Test Specification Coverage table.
The Test Run Coverage table has been renamed to
Test Execution Coverage table.
17938305542692039 The Test Explorer has been removed as default editor
for Product Lines and is now the default editor for the
Test artifact. Additionally, it is now listed in the context
menu in the category Test.
17938311470021995 In the Test Increment Editor, the Artifact Picker, which
opens in the column Planned Increment Content, only
lists Test Data Packages that have been linked with the
corresponding Test Project.
17938305083912110 In the Test Specification Editor, when dragging a Test
Condition onto a Test Item, the proper link actions are
now offered.
17938307693752049 In the Test Implement Editor, Test Environment Property
artifacts can be linked with Manual Test Cases via drag
and drop and are then listed in the editor.

© Vector Informatik GmbH Version 10.6 142

 PREEvision 10.5

ID Resolution
17938308204822049 In the Test Engineering and Test Management
perspective, the default behavior of the Test Conditions
View now correctly links Test Conditions via drag and
drop to Test Items.
17938309210342049 In the Test Engineering and Test Management
perspective, in the Test Conditions View, Test
Conditions linked with Test Items can be dereferenced by
a cell action button.
17938308758952008 In the Test Specification Editor, the column with the
wrong name Test Links has been corrected to Expected
Result.
17938311471392049 The Artifact Picker for Test Conditions lists artifacts in
the alphabetic order of the Test Specification Library
name and then in the alphabetic order of the Test
Condition name.
The Artifact Picker for Test Routines lists artifacts in the
alphabetic order of the Test Specification Library name
and then in the alphabetic order of the Test Routine
name.
17938311469981995 Creating a Test Task after deleting a Test Task Package
is now possible without an exception.
8682711552719442102 The Manual Test Sequence Synthesis metric block now
supports the update mode.
8682711553175121030 During the import of Test Cases from vTESTstudio, the
links to Test Items is now created independently from the
PREEvision project name.
17938309307872102 Missing formatted text fields have been added for Test
Procedure Run:
> Description of Test Procedure
> Precondition of Test Procedure
> Actions of Test Procedure
> Expected Result of Test Procedure
> Postcondition of Test Procedure

2.5.17 Rules
Consistency checks ID Resolution
and online checks
17938309360882112 The severity is now correctly displayed in the
Consistency Check Results view if a Consistency Rule
Group is executed via a metric.
17938307558342035, The consistency check framework is less error-prone in
8682711552297551918 case of incorrect configurations. Consistency Rule
Groups can be executed even though empty or defective
rules are included in them.
17938308324861837 Consistency checks now also support the use of
localized attributes (classifier: M2MLocale).

© Vector Informatik GmbH Version 10.6 143

 PREEvision 10.5

ID Resolution
8682711553262742113 All actions for ignoring meta classes for online checks
are now hidden and can be enabled with the
PREEvision.ini flag ‑DshowConfiguration=true.

8682711553335512102 Selecting a message in the Consistency Check Results

view no longer leads to an error in the Property View.
17938307670791994 An error has been fixed that occurred after executing a
commit while a diagram is open that includes online
check overlays.
17938308101252101 An error which occurred during online check calculation
on the server has been resolved. If locally missing class
files cannot be downloaded from SVN, no empty local file
is created anymore. This avoids the follow-up error
"truncated class file".
17938292067722709 In the Add-ins dialog, in the Advanced settings, the
new option Update consistency and online check
properties is available. If deactivated, the Add-ins
update no longer overwrites the Online Check and the
Directly executable options of a Consistency Rule
Group.
8682711553145052039 The Active option on Consistency Rule Groups is now
considered. Consistency Rules are only executed if the
Consistency Rule Group has activated the Active option.

Modeling and executing ID Resolution

rules
17938306906001031 The context menu action Generate all/changed Rules
and Logic Classes only considers rules and logic
classes that are already checked-out or can be checked-
out. This means, that rules that are part of an installed
Add-in are now ignored and the customized rules can be
generated via the context menu on the rule model.
17938307782272102 Rule names are no longer allowed to include spaces to
improve the performance of the rule execution. The
names of the existing rules must be manually corrected.
17938308953092070 The performance for a rule execution has been improved
in case the same rule is used multiple times.
17938311422942102 The online check "Error in MeDeLa attributes" has been
deleted.
17938311422952102 The online check "Attribute of the Object does not exists
in the MetaModel" was adjusted and Java expressions in
the LHS will no longer be checked.
17938311422992102 The online check "Type mismatch by attribute assign.
Argument wrong." was adjusted to correctly evaluate the
usage of NULL in enumerations.

8682711552764782039 The rule utility "AdaptivConsistentLinkUtil" is obsolete

and has been removed.

© Vector Informatik GmbH Version 10.6 144

 PREEvision 10.5

ID Resolution
8682711551987551806 The Find Suitable Superclasses action can be
executed without error for objects connected via FWLink.
17938309409862106 An error has been fixed regarding removed rule Objects
which could cause errors when trying to undo model
changes.
17938309232552102 A double click on a Propagate Definition Group in the
Model View opens the Propagate Definition Diagram of
all its associated Propagate Definitions.
8682711552939002102 The Connect Rules to Metamodel action has been
extended to also work for renamed meta classes in rules.
17938311553601810 Consistency Rules and Query Rules now also consider
attribute values that are set via custom meta attribute
default values.

2.5.18 Metrics
Metric framework ID Resolution
17938307198122101 To prevent client freezes when navigating between
different explorers, canceled metric executions are no
longer logged in the error log file, in the Status view, and
in the Information View.
17938309247802070 The performance of metric calculations within customized
tables has been improved.
8682711553052751995 The automated metric execution via ANT script now
supports that both "selectedElements" and "parameters"
are set simultaneously as input. If both are set, the metric
is only executed once instead of twice. If both
"selectedElements" and "parameters" are set,
"selectedElements" overrides the first metric block below
the metric executor that matches one of the following
criteria:
> The block is a Primary Model Context block.
> The block is an overwriting Model Context block with
the name "source".
17938306401312039 The error which prevented the automatic execution of a
metric remotely via a batch job has been solved.
17938307556532035 Save points created by another metric block can now be
used in a metric block with activated option Run as
Model Operation without any error.
8682711553032622106 If a metric that is no allowed to change the model (Run
as Model Operation is deactivated), attempts to change
the model, an error is reported.

© Vector Informatik GmbH Version 10.6 145

 PREEvision 10.5

Metric blocks ID Resolution

8682711553189241914 The Application Context metric block works correctly if
the workspace path contains spaces.
8682711553300771994 If an exported artifact has a space as the first character
and the "quote" port in the CSV Export metric block is not
used, unnecessary quotation marks are no longer added.
8682711552470462102 The Open Diagram metric block can now open
configuration diagrams that have not yet been loaded.
17938307398282035 The Render Diagram metric block can now be executed
with the port "renderInBackground"=true and integrated
in a loop without producing a deadlock.
8682711552337421875 The Consistency Rule Group metric block no longer
writes results to the Information View if the input port
"postResultToInconsistencyView" is set to false.

17938308918662092 The AUTOSAR Import metric block checks if the internal

loop ports are connected before executing the loop.
17938309291541792 Replace roots are correctly considered by the given
deletion function of the Replace metric block.

Calculation blocks ID Resolution

17938305543852036 If a cancel status is used in a metric Calculation Block,
the message and icon of the cancel status is now
correctly shown in the Property View and in the
Information View.
17938308137352036 The case of a metric Calculation Block's name can now
be changed without an error that prevented the user from
editing the source code afterwards.
17938309196662101 The performance of the deleteRefObjects metric
framework method used in Calculation Blocks has been
improved.
8682711551987531806 The method AttributeDefinitionUtility.
setValueOfLightWeight
Attribute has been modified so that a new
OpaqueReference is only created if none exists for the
specified Owner and AttributeDefinition. If an
OpaqueReference already exists, the specified value is
added to the list of context artifacts (if not already
included).
8682711553050722009 The utility class TableSelectionUtil is deprecated
and should no longer be used in custom metric code.
8682711552729682106 A new method
getPlainTextWithUpdatedPlaceholders() can
be used in metrics. For more information see the
javadoc.

© Vector Informatik GmbH Version 10.6 146

 PREEvision 10.5

ID Resolution
17938311513392021 On the Implementation property page of Calculation
Blocks, the Language is now read-only since the
implementation language cannot be changed.

Metric executors ID Resolution

17938309379001030 The metric enablement block now correctly considers
only the source context metric block of the metric
executor and ignores metric context blocks that belong to
the associated metric. This prevents unintentional
opening of dialogs.
8682711552082621804 The Source Model Context is set for enablement blocks
of Collaboration Referable Metric Executors.
8682711552654182102 Icons configured by the object configuration for import
and export metric executors are now displayed in the
context menu.
8682711553169792108 Pre Commit Hook Metric Executors can now delete
artifacts that are part of the checked-in artifacts.
8682711553351132046 Pre Delete Hook Metric Executors are now also triggered
if a connection is deleted in a diagram.
8682711551859882111 Collaboration Metric Executors now properly work with
Categorizations (submenus in the context menu).
17938311333542046 If an icon has been added to the object configuration of a
metric executor, it is properly displayed in the context
menu entry of the metric executor.
8682711553165123054 Collaboration Metric Executors can now be hidden from
context menus by entering their unique IDs in the
Blocklists of the respective Perspective Configurations.
17938311685162101 Collaboration Referable Metric Executors can now be
assigned to Actions via the Metric Executor dop-down
list, via drag and drop, and via the Artifact Picker.

Configuration test ID Resolution

framework
8682711552080332102 The performance has been improved for opening the
Java stack trace console of Configuration Tests results
via the Information View.
8682711552865241786 Executing an empty Configuration Test Suite shows an
empty result in the Information View instead of no
feedback.
8682711553283122041 Configuration Tests that change the active variant while
the model includes external JAR files can now be
executed without a NoClassDefFoundError.

© Vector Informatik GmbH Version 10.6 147

 PREEvision 10.5

2.5.19 Reports

ID Resolution
17938306649991225 When generating a report, the default suggestion for the
file name is now the name of the report.
8682711553154553071 The size of the Generate Report dialog with dynamic
parts has been optimized.
17938289992398454 With the enhanced support for file attachments, pictures
from the model tree can be inserted into formatted texts
and be integrated into reports.
17938308047371058 No empty pages are generated in PDF reports if the
report contains a table of contents larger than one page.
17938308077602101 Modifying report footers with multiple tables does not
corrupt the footer after editing.
17938308273482084 The report generator now correctly inserts the content of
placeholders, if the placeholder is directly preceded or
followed by text.
17938309032312025 If formatted texts starting with lists are included in a
report, the reports generator preserves the list order.
8682711551949012109 Reports with headings are now generated correctly if the
heading is directly next to a diagram.
8682711552420042113 An error message has been improved that is displayed in
case of startup problems with the report render engine.
8682711553034122105 Generated reports no longer contain an unnecessary
empty space between rows if a table contains images
which are anchored at a character.
17938306981511783 Large diagrams scaled to fill the whole page are now
completely visible in generated reports.
17938306401312109 Report generation with diagram placeholders that have
the Scale/resize option "Complete Diagram on Separate
Fitting Page" as first parts in a loop now works properly.
17938309210541992 Diagrams in reports are now printed without selection
highlight.
8682711552442803059 The error message "Diagrams on separate fitting pages
are contained in not supported segments of the report"
has been corrected.
8682711553265062034 Diagrams are now shown correctly in reports if inserted
on a separate page directly after a table
17938311350701875 The lock behavior has been optimized for editing reports
without active lock. Now, a lock is requested before
saving the report.
17938311615982109 Application contexts in reports, that display the active
variant are now able to handle if there is no active variant
set.

© Vector Informatik GmbH Version 10.6 148

 PREEvision 10.5

ID Resolution
17938311667612084 Including a Report Module with option Handle Empty
Value set to No Value inserts the text contained in the
Report Module without error.
8682711551701492023 When inserting a placeholder for including a Report
Module into a report, the Include report module option
report module is preselected Insert Placeholder dialog.
The other options are deactivated.
8682711552088162060 Model Contexts are created when a placeholder is
copied and pasted from a formatted text into a report.
17938311670361783 If a Parameter Context or another non valid context is
dropped into a Report, a dialog informs the user that the
context is not suitable.

2.5.20 Collaboration
Lock and commit ID Resolution
17938307499452049 A commit error was fixed that could occur after deleting
all children of a checked-in artifact in one operation.
17938307619002035 Searching for deleted artifacts in a commit also works
when many artifacts (> 25) have been deleted.
8682711551924672051 The error which occurred during a commit operation
including localized attributes, has been resolved.
17938307542752101 The commit error which occurred after modeling a
diagram in the Logical Function Architecture has been
resolved through an adjustment in the synchronization
between LibreOffice and PREEvision.
17938307558902035 An error that occurred after a successful commit in
association with open diagrams has been solved.
17938307569122104 Canceling a commit operation works reliable. If a
transaction cannot be canceled, the [Cancel] button is
inactive.
17938307570102106 The cancel of a commit is now supported at any time as
long as no data is written into the database.
17938307709952040 The server-side check for missing locks has been
improved.
17938307850402052 A commit error in the context of the creation of a Timing
Path Slot and an open diagram has been resolved.
17938307952991038 The commit error which has led to a subsequent forced
restart of the PREEvision client has been resolved.
17938308765391029 A commit error in the context of a restart of the client and
a subsequent commit has been fixed.
17938308926412106 The error handling during a commit has been improved.

© Vector Informatik GmbH Version 10.6 149

 PREEvision 10.5

ID Resolution
17938309056901037 If no commit comment is entered in the Commit dialog
although it is required as defined in the
PREEvision.ini file, a commit via shortcut <Ctrl>
+<Enter> is no longer possible.
17938311565771877 A commit error in the context of invisible reuses has been
fixed.
8682711551703562106 The error handling in the context of lost commit answers
from the server has been improved.
8682711551904332105 A memory problem in the context of a commit error could
be fixed.
8682711552341682105 The Commit dialog can now be closed with <Ctrl>
+<Enter> in case that the comment field has the focus.
8682711552398431030 A commit error in the context of an asset update has
been fixed.
8682711552488831998 A bug in the context of a diagram operation and a commit
has been fixed.
8682711553114101992 A commit error in the context of multiple imports of DBC
files has been fixed.
8682711552770312105 Pressing [Cancel] during commit does not lead to an
error message if the server is already writing into the
database.
8682711552051061994 After an import, the locked artifacts outside the scope are
correctly listed in the Model View.
17938307542222101 Committing after deleting an artifact of a checked-in
Ticket is now possible without error.
8682711552636762106 In the case of an error and a necessary restart of
PREEvision, the commit and update buttons are now
disabled in the toolbar.
8682711552948712101 A restore does no longer cause problems during later
commits.
8682711552540632107 Upon an editing conflict that causes the rollback of a
changed formatted text, the respective error message
now clearly states where the reverted content can be
found in the Information View.
8682711552591551993 Canceling a transaction only closes the transaction
dialog immediately if the transaction has not yet started
running on the server. If it is already running, the client
waits for the server to process the cancel request and
only then close the transaction dialog.
17938308195822107 An error in the context of an OpenID Connect
authentication issue and a subsequent commit has been
fixed.
17938307511281031 In the case of an error during the Undo all own Locks
action, no consecutive errors are produced, and the error
is correctly handled.

© Vector Informatik GmbH Version 10.6 150

 PREEvision 10.5

ID Resolution
17938311325821914 A commit error which only occurred in certain use cases
has been fixed.
8682711551942702045 Deleting a Product Line and a subsequent commit does
no longer cause a misleading and wrong error message.
17938307950681806 The validation has been corrected when committing file
artifacts of an imported model that keeps revision and
check-in status from the import model.
17938311316432042 A NullPointerExeception in the Commit dialog has
been fixed, which occurred in a certain use case.
17938308898392109 The model is no longer inconsistent when undoing all
own locks after adding a localized value to a previously
unlocalized attribute.
17938308928042068 During model import, the Create new UUIDs option now
keeps branch names, preventing data loss and commit
errors.

Model update ID Resolution

17938309406321993 The administratively forced deletion of model cache files
during update requests is now faster.
8682711553060562101 The client is not restarted during a model update if this is
not necessary.
17938311429192105 A progress informs the user if an update cannot be
delivered because someone is currently updating the
update cache.
17938288852362687 Large updates requested by many users does no longer
lead to memory problems.
17938309307861993 During the update of the model cache file on the server,
the old model cache file is deleted after the new model
file is created completely.
8682711552770262049 Update errors have been fixed that were caused by
updates that contain type changed artifacts which also
have been checked in.
8682711553259651914 The update of local copies of managed files is now
working for every update use case.
8682711553162912099 The localization cache is initialized when loading a server
model for the first time.
8682711552539532107 An automatic model update ends the editing mode in the
Model View, for example, when editing a name. The
value entered so far is maintained and a message is
reported in the Information View.
8682711551924392049 The behavior has been improved for updating many
artifacts to the latest revision.
8682711553661701896 Managed files are correctly updated when merging a
model update during server-side model search.

© Vector Informatik GmbH Version 10.6 151

 PREEvision 10.5

Check-out and check-in ID Resolution

17938311668152106 The context menu texts of the lock and the check-out
actions have been unified.
17938300811081037 A check-out operation which requires loading missing
artifacts to the active scope can now be executed
properly.
8682711552760301027 The check-out of two reuses does not lead to a check-out
into the same branch anymore.
17938309028792099 A bug has been fixed in the context of disappearing Title
Blocks in diagrams during check-out.
8682711552417741914 A problem in the context of a check-out of Sender
Receiver Interfaces and reuses has been fixed.
17938307685382111 The undo operation for branch name changes of a
Product Line has been corrected.
17938308767312111 It is now possible to use a Uniqueness Cache to set the
attribute of a new artifact to a unique value while
executing a check-in without a prior commit of the
artifact.
8682711552914332034 The check-out of one diagram does not trigger the
change of the life cycle of a reused diagram.
8682711551844802100 The automatic check-out during editing an artifact now
works even if the artifact has invisible reuses.

Change history and ID Resolution

replace from history
8682711551986711045 A Replace from history action of checked-in artifacts
will no longer block other users from locking.
8682711551986751045 Checked-in reuses are no longer locked after restoring
them during a Replace from history action.
17938311715842101 Performing a distinct database query for each artifact is
avoided now, which was created during a Replace from
history action. One call for the root of the replaced tree
is sufficient.
17938311670622106 When types are deleted during replacing with another
version, all artifacts that use that type are now
automatically checked out as well.
17938311512842101 Opening the Change History on an artifact no longer
reports errors in the Information View.
8682711552982462049 The Change History correctly displays changes for
artifacts that only changed a specific relation.

© Vector Informatik GmbH Version 10.6 152

 PREEvision 10.5

Life cycles ID Resolution

17938307377652109 The life cycle is correctly created during the creation of a
diagram even when the parent artifact is checked-in.
17938309273772106 The life cycle of an artifact can be changed via the life
cycle icon displayed in table cells.

Scopes ID Resolution
8682711553135471994 If a scope activation is canceled, then the client goes
back to the scope definition mode.
If a scope change is performed and canceled, then the
client tries to reactivate the last scope or otherwise goes
into the scope definition mode.
17938309312332106 If objects outside the active scope must be loaded as
part of a delete operation, this no longer fails even if the
objects are read-only.
17938309409852106 An update error in the context of invisible artifacts which
are out of scope has been fixed.
8682711553114101998 Fixed an issue, so that the highlighting in the Property
View works properly for artifacts out of scope.
8682711553662561030 With the PREEvision.ini setting
‑DInstallationMode=true, partial model support is
deactivated.
8682711552656332079 Artifacts do no longer appear as out of scope when they
are newly created under parents that have been moved
inside the scope.
17938308311612070 Visibility checks for scopes have been optimized.
17938308312192070 The performance for filtering out-of-scope artifacts in
update use cases has been improved.

Client startup, login, ID Resolution

shutdown, and cache
17938307701242098 Closing the client has been improved, so that an auto-
update is not executed during closing the client, which
could have led to errors during the operation.
17938307670771994 The login into the PREEvision client has been optimized.
No unusually long waiting times occur anymore after
closing a project and clearing the client cache.
8682711551970842106 In case of a failed login when starting the PREEvision
client, the error message displayed has been improved.
17938309285451993 If client and server are incompatible, no further
reconnects of the client are executed to avoid a server
overload.
17938309381451026 Appropriate error messages are displayed if the client
cache cannot be cleared.

© Vector Informatik GmbH Version 10.6 153

 PREEvision 10.5

ID Resolution
17938309339172036 Fixed an issue which might have been occurred due to
client cache corruption after clients heap limit had been
reached.
8682711553062122077 The performance has been improved for the very first
PREEvision startup.

Historic model versions ID Resolution

17938311667422203 Model comparison and loading a historic model version
now also requires that the client has set the flag
‑DloadCompleteHistoric
ModelVersionAllowed = true. This prevents to
unintentionally start these operations, which cause a high
CPU and memory load on the application server.
17938309376442101 To avoid loading historic models during commit and to
improve performance, the default value of the historic
sub model cache size property has been raised from 100
MB to 2000 MB.
17938309247792101 A compare with historic versions that have changed "type
of" artifacts is possible now.

Error handling ID Resolution

17938309359511026 When opening the Search dialog while the UQR model is
being initialized by another user, only a single error
dialog is shown.
17938309311002049 The message that is displayed for missing external
relations during copy or reuse has been improved.
17938307707912040 The error handling during network problems has been
improved.
17938309312412106 An error in the context of a delete operation of a subtree
with contents of an invisible Asset has been fixed.
17938307697002107 Creating mappings is now allowed if one of the mapping
participants is writeable.
17938309375802076 If client and application server are incompatible, no
further reconnects of the client are executed to avoid a
server overload.
17938311623422049 The logging has been improved to obtain more
information in case that an error due to a branch UUID
and an undo operation occurs again.

Performance and ID Resolution

memory improvements
17938308245502070 The performance of collaboration operations has been
improved.

© Vector Informatik GmbH Version 10.6 154

 PREEvision 10.5

ID Resolution
17938305534681806 The performance has been improved for loading the
version history and replacing with the latest revision for
multiple artifacts.
17938307402541037, The performance of loading the version history has been
17938308084021038, improved.
8682711552709492106,
8682711553092412106,
8682711551998181877
17938307682631045 For a better performance during export, all needed
formatted texts are now loaded with one server call.
8682711552494802052 The performance of modifying hidden artifacts has been
improved.
17938308936031995, The performance of commits with many reuses has been
17938309379732034 improved.
17938309054681993 The performance of calculating artifacts belonging to a
scope has been improved.
17938309373521993 A performance problem with updates after very large
commits has been resolved.
17938308312542070 The performance of large commits and updates has been
improved.
17938309373611993 The upload of data to the staging server has been
improved.
8682711552430311993 The performance has been improved for the case that
many clients must reload missing artifacts from the
server, for example, because of changed scopes.
17938311331251045 The performance of a data check in the database has
been improved.
17938309325392101 The performance of the Remove Locks... action has
been optimized.
17938311379901858 The performance of unloading temporary scopes has
been improved.
17938308054592108 The performance of checking for foreign locks has been
improved.
17938307789452108 The performance of the selection propagation in the
Check-out view has been improved by only selecting the
first occurrence.
17938307692052108 The performance of check-out and lock operations that
require an update has been improved.
17938309307121993 The memory usage has been reduced by avoiding the
allocation of unnecessary memory during iteration
through the model.
17938309325521993 The memory need when acquiring many locks has been
reduced. In addition, a corresponding warning dialog is
displayed.

© Vector Informatik GmbH Version 10.6 155

 PREEvision 10.5

ID Resolution
17938309336512070 The memory need on the application server has been
reduced.
17938311350731045 The performance of filtering out-of-scope artifacts from
update deltas has been improved.

Server API ID Resolution

8682711552919282203 Error codes and messages have been updated in the
operating manual.
8682711553356442203 In the API server logfile, the misleading log output "The
contextId is null!..." is suppressed if no error occurred.
8682711552516602076 When accessing artifacts via the server API, the following
attribute names in the JSON response have been
renamed:
> "Branch Name" to "branchName"
> "Branch UUID" to "branchUUID"
> "Revision" to "revision"
8682711553135662203 The logging has been extended with error messages to
indicate the cause why an HTTPS connection from the
API server to the staging server fails.
8682711551999032203 For use with the API server, the standalone license
server version 2.0.8 or 3.0.0 must be used.

2.5.21 Administration
Authority model ID Resolution
8682711553103513013 The Model View in the authority model uses the same
sorting as the Model View in the E/E model.
17938307614921806 Local changes in the authority model invalidate and
refresh the local authority-related caches of the client.
17938307688261029 In the authority model, Projects with the same name can
only be created once, independently of the case-
sensitivity. For example, if "EEA_MODEL" exists,
"EEA_model" cannot be created.
17938309243351806 In the Administration, artifact permissions can be set on
all packages via the Security... action in the context
menu.
17938311633293043 Changes to client super roles in the authority model are
now correctly recalculated when the authority model
changes.
8682711552451332048 The Excel Export action has been assigned to the
"Excel Export" Authority Group in the authority model.
8682711552770381992 Import and export actions are removed from the "All
Contributions" Authority Group.

© Vector Informatik GmbH Version 10.6 156

 PREEvision 10.5

ID Resolution
8682711553215302039 All rules in the default authority model are compilable and
generated.
8682711553052091806 The last modification date and the last modification user
are not updated if the user has no access rights on the
affected artifacts.

User, model, and ID Resolution

license administration
8682711551851241993 The client-side execution time of the function and
performance test has been reduced.
8682711551851261993 The "Update" test case, which is executed during the
function and performance test, is executed without error.
8682711552946321030 During the model initialization, the file IDs of reused File
Attachments are regenerated correctly.
8682711552716941993 When anonymizing a model, commit comments with a
size over 2000 bytes can be handled correctly.
17938311716372203 Removing the Administrator option of the technical
PREEvision user is no longer possible.
17938309386342076 In the User Management view, the new column
Authentication type is available.
8682711553521872101 Creating a Resource in the Administration no longer
displays a metric error.

Administration panel ID Resolution

8682711552404062076 The "Server Control Panel" has been renamed to
"Administration Panel".
17938311723321993 A performance problem in the graphical user interface of
the administration panel during backup has been
resolved.
17938309348801993 The administration panel can now be used in
combination with WebSEAL.
8682711552680791036 With the administration panel, remote operations are
possible on all PREEvision 10.0 versions.

Operating ID Resolution
17938311659832106 Bug report errors are now reported to the Information
View instead of via pop-up error dialog.
8682711553019971993 The star-tup of the application server is stopped if the
database server is incompatible.
8682711552868691993 The server startup error which occurred after preparing
the model for migration has been resolved.

© Vector Informatik GmbH Version 10.6 157

 PREEvision 10.5

ID Resolution
8682711551845172054 The configuration of ElasticSearch has been changed so
that backup and restore of the data is possible.
17938309285461993 An exception in the server log file is prevented in context
of the monitoring functionality.
17938309325131993 The logging on the application server has been improved
and reduced for the use case that a large update shall
not be delivered to the client.
17938307346702105 Several log level severities have been reduced to "trace"
for the staging server log. In this way, administrators can
reduce the size of the log file by increasing the log level.
8682711553356001993 The NullPointerException that was reported in the
server logfile during model initialization has been fixed.
8682711553103513013 The critical security gap (Log4Shell), which has been
reported for the Log4j Java library, is closed. The Log4j
Java library, which is used in the PREEvision client, has
been updated to version 2.17.1.
For further security information, refer to www.vector.com/
security-advisories/log4j.
8682711553334321995 During start-up of the PREEvision client, the
ClassNotFoundException for the class
IntegerHexVerifier is no longer reported in the
client log file.

Add-ins ID Resolution
17938306701441804 Add-in propagation has been extended to cover the path
from table through row and cell calculation to metric
executor.
17938307281452101 Perspectives are contained in Demo Add-ins.
17938307345131031 A client freeze has been fixed that occurred when the
Lock dialog was displayed during Add-in installation.
17938307348671036 Product Add-ins have been updated to use a new type of
value for FRAME_LINE_PATTERN in the object
configuration.
17938307435652023 After deinstalling Add-ins, empty packages are also
removed from the Administration.
17938307511381031 The check for conflicting overlapping in Add-ins during
check-in is now only applied to Add-ins that are in the
"ready for delivery" state.
17938307708432101 The Add-in propagation has been extended for internal
metric loops. In this case, the Add-in propagation
propagates the metric blocks inside the internal metric
loop logically in backward and forward direction, while
the standard propagation for metrics only propagates
backwards.

© Vector Informatik GmbH Version 10.6 158

 PREEvision 10.5

ID Resolution
17938307747942011 The installation of Add-ins is also possible now if there
are still source codes in the target model which are not
checked-in.
17938307763321028 Metric source codes are no longer compiled during Add-
in installation.
17938308161532039 For the installation of Add-ins with Diagram
Configurations, a cache has been added for the
evaluation of Life Cycle transitions, and the filter
evaluation for Diagram Configurations has been
improved.
17938308176611028 The performance of calculating locks has been improved
when many artifacts are checked-in during an Add-in
installation.
17938308189782039 If metrics are compiled when creating an Add-ins delivery
file, code attributes of the source codes are initialized
before. (Same behavior as when a compilation is
triggered manually).
17938308224501036 When the database storage is full, PREEvision does not
retry to apply statements but give the user feedback that
the changes were rolled back.
17938308279222040 Out of memory exceptions during Add-in installation are
now handled with a dialog (default handling).
17938308314832040 The [Install Add-Ins] button is hidden when a non-
administrator license is selected.
17938308324721837 The Add-in propagation now includes result metrics of
rules.
17938308763401031 During Add-in installation, the property of files is correct
when updating existing files to a newer version.
17938308938691995 When installing default Add-ins, no test data is installed
anymore.
17938309027981031 When installing Add-ins, technical suffixes in branch
names are not corrected.
17938309281081036 Artifacts that are marked as read-only/write-protected do
not cause an abortion of the Add-in installation anymore.
17938309283122011 Two Add-ins with the same class files (source code or
rules) can now be customized together.
17938309359001028 Reuses, that cause problems in the Add-in installation,
are reported in the Information View, and detailed
information on debugging is written to the log file.
17938309360932011 Uninstalling customized Add-ins is possible now. No
external relations are copied anymore while customizing
an Add-in.
17938311324841806 When creating an Add-in delivery file, it is checked
whether Add-ins reference incorrectly reused Assets.

© Vector Informatik GmbH Version 10.6 159

 PREEvision 10.5

ID Resolution
17938311350741995 The Add-in propagation has been extended for multi-
valued attribute definitions.
17938311369191025 If customized rules and metrics need an update after an
Add-ins installation, appropriate information for the
relevant rules and metrics is reported in the Information
View.
17938311481501806 Demo content has been removed from the "Diagnostic
Design" Add-in.
17938311608391036 For the installation of Demo Add-ins, the branch label for
artifacts mapped by the model structure during the
installation is correctly adapted, for example, source Sets
contained in the Rule Models.
17938311608441036 Obsolete Add-ins are ignored when checking for foreign
branch suffixes.
8682711551905512039 For refused check-in of Add-ins, the reporting in the
Information View has been improved. Errors / warnings
on artifacts remaining in the "To-integrate" virtual folder
of an Add-in can be customized.
8682711551929232039 Add-ins get the correct Add-in branch name when they
are checked-out alongside their parent artifact instead of
taking the branch name of their parent.
8682711551944152039 Add-ins which have lost their branch name in the Add-ins
model are not uninstalled.
8682711551967801865 Rules in customized Add-ins can be updated again.
8682711551969021992 After an Add-in installation, all installed files are
contained in the saved E/E model.
8682711552087942102 Branch and revision are ignored when propagating files
using Property- or XML-file links.
8682711552442492039 Versionless UUIDs are now used to refer to Query Rules
and the object configuration of metric executors.
8682711552473182023 The Customize and Update actions are only offered in
the context menu of Add-ins if the installation mode flag
is set on the client.
8682711552591633046 The check-out dialog is shown instead of an exception
when a checked-in Perspective Configuration is
customized.
8682711552611802041 If the option Compile Metrics when creating an Add-
Ins delivery file is selected and the creation of an Add-
ins delivery file fails due to uncompilable source codes,
an error message is posted, and the error is reported in
the Information View.
8682711552656692011 The Add-in's check-out status has been included in the
Add-in's installation information reported in the
Information View.
8682711552708981808 The Add-ins installation wizard displays an error when a
check-in is terminated due to missing trace assignments.

© Vector Informatik GmbH Version 10.6 160

 PREEvision 10.5

ID Resolution
8682711552708991808 Add-ins and artifacts referenced by Add-ins do not get
checked-out to the default branch if their current branch
name contains an index.
8682711552721302102 When adding a Diagram Configuration as core artifact to
an Add-in, the constraints of a Legend are propagated.
8682711552942042039 The error information during Add-ins installation has
been improved to identify the artifacts which have caused
the problem.
8682711552942141225 When customizing an artifact affects just one Add-in, the
Add-in selection dialog gets skipped.
8682711552945131999 Versioning such as "Customizing-1.2" can now be used
in the branch suffix of Add-ins. For this purpose, when
checking out Add-ins, the branch suffix check ignores
numbers and special characters.
8682711553036271808 Customized metrics with wrong relations between Source
Code and Calculation Block have been removed from the
model.
8682711553138523013 The Add-ins installation commits with the comment "Add-
in Installation/Update".
8682711553142392078 For artifacts that are moved to an Obsolete Add-in, all
relations are dereferenced from the artifacts that are part
of the original Add-in. Relations to singletons and type-of
relations are not dereferenced.
8682711553171832041 Add-ins which contain other Add-ins as core artifacts, are
not deleted during an Add-ins update.
8682711553175122101 Update of customized Add-ins now detects moved
children under root core artifacts during on all hierarchy
levels, not just direct children.
8682711553183212101 During an update of a customized Add-in, singleton
artifacts are not reused but just referenced by its core/
propagated core. If singletons contained in the core/
propagated core of the customized Add-in are not part of
the predecessor Add-in, they are dereferenced by the
update.
8682711553215373046 While updating a customized Add-in without a
propagated Add-in, a propagated Add-in is created on-
the-fly if required.
8682711553350992039 Improved robustness during Add-ins installation: reuses
are repaired during the installation.
8682711553352382039 Improved robustness during Add-ins installation: reuses
are repaired during the installation.
8682711553559431031 The Add-ins dialog has been extended by and additional
column that displays the currently installed version and
build number of Add-ins.
8682711553569842039 The initial value of the Update consistency and online
check properties flag of the Add-ins installation wizard
can now be specified.

© Vector Informatik GmbH Version 10.6 161

 PREEvision 10.5

ID Resolution
8682711553603002101 The performance of merging models has been improved.
This also improves the performance of the Add-in
installation and other imports like ReqIF.
8682711553632561202 Installing customized Add-ins no longer causes a reuse
repair error.
8682711553743272039 The Build Number of an Add-in is only incremented if
the Add-in is allowed to be checked out in model.
8682711553977732068 Default markers for attributes are considered during Add-
in installation.
8682711553977802068 Fixed handling of reuses when an Add-in installation
changes parts of reuses and adds new parts to reuses.
8682711553986332068 During Add-in installation, model consistency checks for
reuses are correctly applied.
8682711554045542023 An inconsistency in the "Test Data Management" and
"Test Analysis" Add-ins that could cause errors when
customizing or installing these Add-ins has been fixed.
8682711554395792068 A false positive error that could occur during Add-in
installation has been fixed.
8682711553437962036 A new entry in an object configuration of an Add-in is
written to delta object configuration and no longer
changes the default object configuration.

OpenID Connect ID Resolution

17938307346581993 During OpenID Connect authentication, better feedback
is provided to the user via the progress dialog.
17938307346591993 It is now possible to log into a middleware license server
using OpenID Connect authentication when the
middleware has disabled model access.
8682711553462021993, Login to the administration panel via OpenID Connect is
17938307662891993 supported, now.
17938307664061993 In the deploy.properties file, a bug has been fixed
in context of the
openid.access_token.verification_interval
parameter, which defines the time interval in seconds
after which the access token on the server is verified
against the identity provider.
17938307953051993 The logging for OpenID Connect has been improved:
> Logs are now printed correctly.
> If OpenID Connect debug is activated, information on
successful token refresh is added.
17938309286771993 In case the OpenID Connect login is not possible via the
administration panel, it is possible to log in with a
username and password if Simple Authentication
allowed is activated for the user.

© Vector Informatik GmbH Version 10.6 162

 PREEvision 10.5

ID Resolution
17938309342351026 A client with a system time that is ahead the server
system time by up to ten minutes can use OpenID
Connect authentication again. A system time delay of 5
seconds or more is logged in the client and server log
files.
17938311326001993 A sporadic problem in the context of a login with OpenID
Connect has been resolved.
8682711552052592020 In the administration panel, simple authentication can
also be used for connecting to the remote server to
perform remote checks, backups, and migrations.

2.5.22 Installation
PREEvision client ID Resolution
8682711553296521993 Registering a PREEvision client in the Windows registry
is now possible without Windows administrator rights.
The register_locally.bat can be executed to
register PREEvision in the local registry.
8682711552274692017 In the PREEvision client, the file jre\lib\security
\cacerts is no longer deleted. Instead, a password is
set for this keystore.

PREEvision server ID Resolution

components
8682711553279432017 In the deploy.properties, most properties have been
renamed according to a unified naming scheme.
8682711552762882054 The Monitor.DataStorage.
Transport.Port of the monitoring server has been
changed to a single port 9300, instead of a range
9300-9400.

17938307711702203 The default port of the monitoring data storage can be

configured in the deploy.properties.

8682711552942592017 Apache Tomcat settings are adapted and configurable by

the deploy.properties.

8682711553279622017 The MessageBrokerJdkPath property was removed

from the deploy.properties. Instead, the
tomcat.jdkhome property is used also for the
messaging application.
8682711553279652017 The unused properties webapp.disp.name and
webapp.descr were removed from the
deploy.properties.

8682711553338922017 Starting Apache Tomcat as a service may cause crashes

of the Java Virtual Machine. By default, a heap dump is
created if the JVM crashes, which may lead to large
amounts of data on the server.

© Vector Informatik GmbH Version 10.6 163

 PREEvision 10.5

ID Resolution
The following parameter should be set for the startup of
Apache Tomcat to deactivate the creation of a heap
dump when the Java Virtual Machine crashes:
‑XX:-CreateCoredumpOnCrash
The parameter is automatically set in the setenv.bat
and setenv.sh when building preconfigured Apache
Tomcats.
8682711553518902203 For security reasons, you should deactivate that Apache
Tomcat shows too much server information. In the
server.xml, within the <Host> definition, add the
following line:
<Valve
className="org.apache.catalina.valves.Erro
rReportValve" showReport="false"
showServerInfo="false" />
When building preconfigured Apache Tomcats, these
parameters are automatically set in the server.xml.

8682711553147990000 To avoid security vulnerabilities, dependencies to Jetty

have been removed in all server components.

2.5.23 License

ID Resolution
8682711552970552203 The connection data to the license server defined in the
PREEvision.ini file is completely and properly taken
over in the Choose a license from server dialog.
17938307762112076 Connecting to a standalone license server with enabled
OpenID Connect authentication is working properly now.
8682711553292351993 License server connection data is logged correctly in the
log file.
17938311333222054 The license dialog no longer freezes while the license
check is performed. The license dialog provides a
progress bar with which running actions can be canceled.
8682711551701471918 Users with the "Requirements and Test Manager" license
can now use explorers.
17938309310072101 The Administration actions Create Performance/
Benchmark Report... and Network Performance Test
are now license-independent and are available for all
users.
8682711553089582203 With a PREEvision viewer license, access to the General
preference pages is possible.
8682711552553541998 When importing a model, artifacts that are children of
artifacts, that are not available because of license
restrictions are now ignored
8682711553140731030 When using a PREEvision viewer license, the highlight
for write-protected artifacts in a diagram is disabled.

© Vector Informatik GmbH Version 10.6 164

 PREEvision 10.5

ID Resolution
With this license type write-protected artifacts are no
longer highlighted (background color + alpha value). In
addition, the highlight option was removed from the
highlight toolbar menu and the section for this highlight
was disabled in the preferences.
Other license types are not affected by this change.
17938308314432040 An incorrect behavior of importing invisible artifacts that
occurred with restricted licenses has been fixed.

2.5.24 Backup, restore, and migration

ID Resolution
17938308273601036 For server-side restore in the administration panel,
migration-relevant information is cleared to release the
memory after the migration.
17938311512221036 Missing backup directory configurations in the
administration panel do not lead to failed remote
migrations anymore.
8682711553591561036 In the administration panel, determining the model
versions for model matching during migration has been
improved.
8682711553591551036 In the administration panel, if the user is forced to log out
during model migration, the user can log in again and
proceed at the same page from which he was logged out.
8682711552763881993 In the administration panel, remote model preparation
can be executed without string limitation of 2 GB.
8682711553175121036 If Finalize Model Preparation is executed via the
administration panel on a remote 10.5 or 10.0 server, the
maintenance mode is automatically activated.
8682711553339781036 In the administration panel, the Job Details display the
correct model preparation information.
17938307545591036 A server-to-server migration problem was resolved. The
migration is executed with disabled authority
management.
8682711552038941036 An error has been fixed which caused aborting a server-
side restore.
17938307953192076 A backup is possible now, even if the SVN gateway is not
available.
17938311667532076 In the PREEvision client, backup and restore actions are
only possible with a PREEvision Architect license. If no
PREEvision Architect license is used for backup or
restore, an error dialog is displayed.
8682711552472461036 The restore is processed properly without aborting, which
was caused by an unusual model constellation.

© Vector Informatik GmbH Version 10.6 165

 PREEvision 10.5

ID Resolution
8682711554032111036 Incremental migration no longer causes a
NullPointerException.

8682711553092622020 The performance of the restore has been improved for

restoring large commits.
8682711553122222020 The performance of the restore has been improved for
certain model constellations.

Data migration ID Resolution

8682711553575302070 The error which has caused a missing commit history
after a remote backup or remote restore has been fixed.
8682711552631431806 Fixed migration of Perspective Configuration Models
containing Tables.
8682711553613911993 An error in the context of restoring formatting texts of an
anonymized model has been fixed.
8682711553554171036 An error in the migration has been fixed where incorrect
UUIDs were calculated for SOME/
IP SD Server Event Group Timing Configurations.
8682711553632432020 An error has been fixed where a newly created
Application Endpoint, Socket Address and SOME/IP SD *
Event Group Timing Configuration might cause a
migration to fail.
8682711553145911024 During migration, the relation between Process Design
and Process is set.
8682711553500611036 Socket Connection Bundles contained in generic
packages are correctly migrated.
8682711553509502041 Blocklist entries of Perspective Configurations of a
PREEvision 10.0 installation work after migration to
PREEvision 10.5.

© Vector Informatik GmbH Version 10.6 166

 PREEvision 10.5

2.6 Known issues

Known issues in You will find the important known issues in the following table. Please note that some
PREEvision 10.5 issues depend on specific configurations, views, or models.

ID Known issue
8682711554031661036 In rare cases, the restore fails with the following error
message:
"Error while executing model version <version>: Newly
created reuses do not match existing reuses."
Contact the Vector support for getting instructions on
how to proceed with the migration/restore.
8682711554406702203 If the PREEvision administration server is installed under
Linux, models cannot properly be initialized via the
administration panel. The initialized model does not
contain any files.
Workaround: Initialize the model via the PREEvision
client.
8682711554380412077 The Consistency Rule Group "Metric-Editor" under
"Administration" | "Rules" | "ConsistencyRuleModel" |
"Product" | "L230_Verify_Model" |
"L233_Metric_Framework" | "Javabased Online Checks"
| "Metric_Editor" must not be used as an online check. It
can lead to an error causing the deactivation of the
server-side online check framework. On the online check
status icon in the status bar of the client, the following
tooltip is displayed: "Error during online check calculation
on the server. Please contact an administrator."
17938307791212069 The AUTOSAR export is interrupted if artifacts to be
exported are identified which are out of scope. The
artifacts out of scope must be added to the scope
temporarily. The export cannot be properly finished until
all required artifacts which are out of scope are added to
the scope. This means, adding artifacts to the scope
must be repeated several times until all artifacts are
added to the scope. It may be very time consuming until
the export can be finally executed.
8682711552649222003 In the import wizard for an AUTOSAR import with merge,
the aggregation of changed and deleted artifacts is not
always feasible. The filter settings for the model merge
do not always work reliably, and the selection of artifacts
in the model trees does not have an effect on the update
mechanism.
8682711554383191029 Some parts of the new feature for handling initial values
are currently located in a product Add-in. This prevents a
customizing of the feature. In case the default
configuration is not suitable for a specific project, contact
the Vector support for a workaround.
8682711554417372014 Some parts of the new feature for configuring the content
assist are currently located in a product Add-in. This
prevents a customizing of the feature. In case the default
configuration is not suitable for a specific project, contact
the Vector support for a workaround.

© Vector Informatik GmbH Version 10.6 167

 PREEvision 10.5

ID Known issue
8682711554417442013 Some parts of the new feature for the automatic creation
of application data type to implementation data type
mapping, which is used for data types in the new Primary
Editors is currently located in a product Add-in. This
prevents a customizing of the feature. In case the default
configuration is not suitable for a specific project, contact
the Vector support for a workaround.
8682711554173803043 When selecting more than one table cell of a text table in
the LibreOffice editor via mouse select, and then
reducing the selection to one cell and releasing the
mouse button, the LibreOffice editor crashes.
Workaround: Instead of reducing the selection via the
mouse, use another selection method, for example, via
keyboard.
8682711553529641783 When manually adjusting the size of a text table in the
LibreOffice editor, for example, decreasing the width of
the text table, this change in the formatted text leads to a
schema violation during ReqIF export, and the formatted
text containing the text table is not exported. If the XML
schema validation option is activated for the ReqIF
export, detailed information on the schema validation is
reported in the Information View.
8682711554639042025 When defining placeholders with Query Context for
reports, the defined localized language is not displayed in
the report.

© Vector Informatik GmbH Version 10.6 168

Get more Information

Visit our Website for:

> News
> Products
> Demo Software
> Support
> Training Classes
> Addresses

www.vector.com