PREEvision 10.20 Release Notes

release notes for Vector Informatik models including: PREEvision, Vector Informatik, Release Notes, Version 10.20, AUTOSAR, Systems engineering, Requirements engineering, Diagnostics, Communication, Hardware architecture, Software architecture, Product line engineering, Variant management, Change and release management, Test engineering, Metrics, Collaboration, Administration, Installation, Server API

PREEvision ReleaseNotes 10.20.0 EN

PREEvision

Google Docs
Google Drive
Download [pdf]

File Info : application/pdf, 476 Pages, 11.86MB

PREEvision
Release Notes
Version 10.20 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 2025, Vector Informatik GmbH. Printed in Germany. All rights reserved.

Contents

PREEvision 10.20

1.1

Version numbers

1.2

Installation and compatibility information

1.3

New features in PREEvision 10.20

1.4

Configuration information

1.5

Fixed issues

1.5.1 1.5.2 1.5.3 1.5.4 1.5.5 1.5.6 1.5.7 1.5.8 1.5.9 1.5.10 1.5.11 1.5.12 1.5.13 1.5.14 1.5.15 1.5.16 1.5.17 1.5.18 1.5.19 1.5.20 1.5.21

Common Diagrams Tables Systems engineering Requirements Logical function architecture AUTOSAR Diagnostics Communication Hardware architecture Geometry Product line engineering Variant management Change and release management Rules Metrics Reports Collaboration Administration Installation Server API

1.6

Known issues

PREEvision 10.19

2.1

Version numbers

2.2

Installation and compatibility information

2.3

New features in PREEvision 10.19

2.4

Configuration information

2.5

Fixed issues

2.5.1 2.5.2 2.5.3 2.5.4 2.5.5 2.5.6 2.5.7 2.5.8 2.5.9 2.5.10 2.5.11 2.5.12 2.5.13

Common Diagrams Tables Requirements AUTOSAR Diagnostics Communication Hardware architecture Product line engineering Test engineering and test management Rules Metrics Collaboration

Version 10.20

Contents
12
13 14 17 25 28 28 28 29 29 30 30 31 31 32 33 33 34 34 35 35 35 36 36 36 37 37 38
41
42 43 45 51 53 53 54 54 55 55 56 56 57 58 58 58 59 59
3

2.5.14 2.5.15 2.5.16

Administration License Backup, restore, and migration

2.6

Known issues

PREEvision 10.18

3.1

Version numbers

3.2

Installation and compatibility information

3.3

New features in PREEvision 10.18

3.4

Configuration information

3.5

Fixed issues

3.5.1 3.5.2 3.5.3 3.5.4 3.5.5 3.5.6 3.5.7 3.5.8 3.5.9 3.5.10 3.5.11 3.5.12 3.5.13 3.5.14

Common Diagrams Tables Requirements Logical function architecture AUTOSAR Software architecture Diagnostics Hardware architecture Geometry Product line engineering Metrics Collaboration Administration

3.6

Known issues

PREEvision 10.17

4.1

Version numbers

4.2

Installation and compatibility information

4.3

New features in PREEvision 10.17

4.4

Configuration information

4.5

Fixed issues

4.5.1 4.5.2 4.5.3 4.5.4 4.5.5 4.5.6 4.5.7 4.5.8 4.5.9 4.5.10 4.5.11 4.5.12 4.5.13 4.5.14

Common Diagrams Tables Requirements AUTOSAR Software architecture Diagnostics Communication Hardware architecture Product line engineering Change and release management Metrics Collaboration Administration

Version 10.20

Contents
59 59 59 60
62
63 64 67 72 74 74 74 75 75 75 76 77 77 77 78 78 79 79 79 81
83
84 85 87 90 91 91 91 92 92 93 94 95 95 95 96 96 96 97 97
4

4.6

Known issues

PREEvision 10.16

5.1

Version numbers

5.2

Installation and compatibility information

5.3

New features in PREEvision 10.16

5.4

Changes

5.5

Configuration information

5.6

Fixed issues

5.6.1 5.6.2 5.6.3 5.6.4 5.6.5 5.6.6 5.6.7 5.6.8 5.6.9 5.6.10 5.6.11 5.6.12 5.6.13 5.6.14

Common Diagrams Tables Requirements Logical function architecture AUTOSAR Diagnostics Communication Hardware architecture Product line engineering Metrics Collaboration Administration Server API

5.7

Known issues

PREEvision 10.15

6.1

Version numbers

6.2

Installation and compatibility information

6.3

New features in PREEvision 10.15

6.4

Configuration information

6.5

Fixed issues

6.5.1 6.5.2 6.5.3 6.5.4 6.5.5 6.5.6 6.5.7 6.5.8 6.5.9 6.5.10 6.5.11 6.5.12 6.5.13 6.5.14 6.5.15 6.5.16 6.5.17 6.5.18 6.5.19 6.5.20

Common Diagrams Tables Requirements AUTOSAR Software architecture Diagnostics Communication Hardware architecture Product line engineering Variant management Change and release management Test engineering and test management Metrics Reports Collaboration Administration Installation Server API Backup, restore, and migration

Version 10.20

Contents
98
100
101
102
104
109
110
114 114 114 114 115 115 115 116 117 117 118 118 118 119 120
121
123
124
125
127
130
132 132 132 133 133 133 134 135 135 136 137 137 137 137 138 138 138 139 139 139 139
5

6.6

Known issues

PREEvision 10.14

7.1

Version numbers

7.2

Installation and compatibility information

7.3

New features in PREEvision 10.14

7.4

Changes

7.5

Configuration information

7.6

Fixed issues

7.6.1 7.6.2 7.6.3 7.6.4 7.6.5 7.6.6 7.6.7 7.6.8 7.6.9 7.6.10 7.6.11 7.6.12 7.6.13 7.6.14 7.6.15 7.6.16 7.6.17 7.6.18 7.6.19 7.6.20

Common Diagrams Tables Requirements and customer features Logical function architecture AUTOSAR Software architecture Diagnostics Communication Hardware architecture Product line engineering Change and release management Test engineering and test management Rules Metrics Reports Collaboration Administration License Backup, restore, and migration

7.7

Known issues

PREEvision 10.13

8.1

Version numbers

8.2

Installation and compatibility information

8.3

New features in PREEvision 10.13

8.4

Changes

8.5

Configuration information

8.6

Fixed issues

8.6.1 8.6.2 8.6.3 8.6.4 8.6.5 8.6.6 8.6.7 8.6.8 8.6.9 8.6.10 8.6.11 8.6.12 8.6.13 8.6.14

Diagrams Tables Requirements AUTOSAR Diagnostics Communication Hardware architecture Geometry Product line engineering Change and release management Functional safety Metrics Collaboration Administration

Version 10.20

Contents
140
142
143
144
146
151
152
153 153 153 154 154 155 155 156 157 158 158 159 159 160 160 160 160 160 161 162 162
163
165
166
167
169
172
173
174 174 175 175 176 176 177 178 178 178 179 179 179 179 180
6

8.6.15 8.6.16 8.6.17

License Server API Backup, restore, and migration

8.7

Known issues

PREEvision 10.12

9.1

Version numbers

9.2

Installation and compatibility information

9.3

New features in PREEvision 10.12

9.4

Changes

9.5

Configuration information

9.6

Fixed issues

9.6.1 9.6.2 9.6.3 9.6.4 9.6.5 9.6.6 9.6.7 9.6.8 9.6.9 9.6.10 9.6.11 9.6.12 9.6.13 9.6.14 9.6.15 9.6.16 9.6.17 9.6.18

Diagrams Tables Requirements Logical function architecture AUTOSAR Diagnostics Communication Hardware architecture Product line engineering Change and release management Variant management Test engineering and test management Rules Metrics Reports Collaboration Administration Installation

9.7

Known issues

10 PREEvision 10.11

10.1 Version numbers

10.2 Installation and compatibility information

10.3 New features in PREEvision 10.11

10.4 Configuration information

10.5 Fixed issues

10.5.1 10.5.2 10.5.3 10.5.4 10.5.5 10.5.6 10.5.7 10.5.8 10.5.9 10.5.10 10.5.11 10.5.12 10.5.13 10.5.14

Common Diagrams Tables Requirements Logical function architecture AUTOSAR Software architecture Diagnostics Communication Hardware architecture Product line engineering Variant management Metrics Reports

Version 10.20

Contents
180 180 181
182
184
185
186
188
193
194
196 196 197 198 198 199 200 200 200 201 202 202 202 202 203 203 203 204 205
206
208
209
210
212
216
217 217 217 218 218 219 219 220 220 221 221 222 222 222 222
7

10.5.15 10.5.16 10.5.17 10.5.18

Collaboration Administration Installation Backup, restore, and migration

10.6 Known issues

11 PREEvision 10.10

11.1 Version numbers

11.2 Installation and compatibility information

11.3 New features in PREEvision 10.10

11.4 Changes

11.5 Configuration information

11.6 Fixed issues

11.6.1 11.6.2 11.6.3 11.6.4 11.6.5 11.6.6 11.6.7 11.6.8 11.6.9 11.6.10 11.6.11 11.6.12 11.6.13 11.6.14 11.6.15 11.6.16 11.6.17 11.6.18 11.6.19

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

11.7 Known issues

12 PREEvision 10.9

12.1 Version numbers

12.2 Installation and compatibility information

12.3 New features in PREEvision 10.9

12.4 Changes

12.5 Configuration information

12.6 Fixed issues

12.6.1 12.6.2 12.6.3 12.6.4 12.6.5 12.6.6 12.6.7 12.6.8 12.6.9 12.6.10

Common Diagrams Tables Requirements Logical function architecture AUTOSAR Software architecture Diagnostics Communication Hardware architecture

Version 10.20

Contents
223 223 223 224
225
227
228
229
231
235
236
237 237 238 238 238 239 240 240 241 241 242 242 242 243 243 243 243 244 244 244
245
247
248
249
251
256
257
258 258 259 259 259 260 261 261 262 263 264
8

12.6.11 12.6.12 12.6.13 12.6.14 12.6.15 12.6.16 12.6.17 12.6.18 12.6.19

Geometry Product line engineering Change and release management Test engineering and test management Metrics Reports Collaboration Administration Backup, restore, and migration

12.7 Known issues

13 PREEvision 10.8

13.1 Version numbers

13.2 Installation and compatibility information

13.3 New features in PREEvision 10.8

13.4 Changes

13.5 Fixed issues

13.5.1 13.5.2 13.5.3 13.5.4 13.5.5 13.5.6 13.5.7 13.5.8 13.5.9 13.5.10 13.5.11 13.5.12 13.5.13 13.5.14 13.5.15 13.5.16 13.5.17 13.5.18 13.5.19

Common Diagrams Tables Requirements Logical function architecture AUTOSAR Software architecture Communication Hardware architecture Geometry Product line engineering Variant management Rules Metrics Reports Collaboration Administration Installation Backup, restore, and migration

13.6 Known issues

14 PREEvision 10.7

14.1 Version numbers

14.2 Installation and compatibility information

14.3 New features in PREEvision 10.7

14.4 Changes

14.5 Fixed issues

14.5.1 14.5.2 14.5.3 14.5.4 14.5.5 14.5.6 14.5.7 14.5.8

Common Diagrams Tables Requirements Logical function architecture AUTOSAR Software architecture Diagnostics

Version 10.20

Contents
264 265 265 265 265 266 266 266 266
267
269
270
271
273
278
279 279 280 280 280 281 281 282 282 283 284 284 284 284 284 285 285 286 287 287
288
290
291
292
294
298
299 299 300 300 301 301 301 302 303
9

14.5.9 14.5.10 14.5.11 14.5.12 14.5.13 14.5.14 14.5.15 14.5.16 14.5.17 14.5.18 14.5.19

Communication Hardware architecture Geometry Product line engineering Rules Reports Collaboration Administration Installation License Backup, restore, and migration

14.6 Known issues

15 PREEvision 10.6

15.1 Version numbers

15.2 Installation and compatibility information

15.3 New features in PREEvision 10.6

15.4 Fixed issues

15.4.1 15.4.2 15.4.3 15.4.4 15.4.5 15.4.6 15.4.7 15.4.8 15.4.9 15.4.10 15.4.11 15.4.12 15.4.13 15.4.14 15.4.15 15.4.16 15.4.17 15.4.18 15.4.19 15.4.20 15.4.21

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

15.5 Known issues

16 PREEvision 10.5

16.1 Version numbers

16.2 Installation and compatibility information

16.3 New features

16.3.1 16.3.2 16.3.3 16.3.4 16.3.5 16.3.6 16.3.7 16.3.8 16.3.9

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

Version 10.20

Contents
303 304 305 305 306 306 306 307 308 308 308
309
312
313
314
316
319 319 320 320 321 322 323 323 324 324 325 325 326 326 326 327 327 327 328 328 329 329
330
332
334
335
338 338 343 344 345 347 350 352 359 363
10

16.3.10 Usability 16.3.11 Administration 16.3.12 Configuration

16.4 Changes

16.5 Fixed issues

16.5.1 16.5.2 16.5.3 16.5.4 16.5.5 16.5.6 16.5.7 16.5.8 16.5.9 16.5.10 16.5.11 16.5.12 16.5.13 16.5.14 16.5.15 16.5.16 16.5.17 16.5.18 16.5.19 16.5.20 16.5.21 16.5.22 16.5.23 16.5.24

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

16.6 Known issues

Contents
365 369 370
383
385
385 390 392 397 404 405 414 418 421 430 440 441 447 448 448 449 450 452 455 456 463 470 471 472
474

Version 10.20

1 PREEvision 10.20

This chapter contains the following information:

1.1

Version numbers

1.2

Installation and compatibility information

1.3

New features in PREEvision 10.20

1.4

Configuration information

1.5

Fixed issues

Common

Diagrams

Tables

Systems engineering

Requirements

Logical function architecture

AUTOSAR

Diagnostics

Communication

Hardware architecture

Geometry

Product line engineering

Variant management

Change and release management

Rules

Metrics

Reports

Collaboration

Administration

Installation

Server API

1.6

Known issues

PREEvision 10.20
13 14 17 25 28 28 28 29 29 30 30 31 31 32 33 33 34 34 35 35 35 36 36 36 37 37 38

Version 10.20

1.1 Version numbers

Version numbers

Application PREEvision client PREEvision license server PREEvision database server PREEvision application server

Documentation

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

PREEvision 10.20
Version number 10.20.0 3.0.4 10.20.0.05 10.20.0
Version number 10.20.0 10.20.0 10.20.0 10.20.0 10.20.0

Version 10.20

PREEvision 10.20

1.2 Installation and compatibility information
For detailed information about the installation of PREEvision 10.20 and the migration to PREEvision 10.20, refer to the PREEvision operating manual.
For detailed information about the hardware and software requirements of PREEvision 10.20, refer to the PREEvision system requirements.

System requirements

The following system requirements have been changed: > VisualSVN Server 5.4.4 is recommended for the PREEvision Subversion server. > The recommended version of Apache Tomcat has been changed to 9.0.107.

Server configuration connector timeouts

In the server.xml of the PREEvision application server and the PREEvision administration server, the following timeout parameters must be set for the HTTP/HTTPS connector:
disableUploadTimeout="false" connectionTimeout="1200000" connectionUploadTimeout="86400000" keepAliveTimeout="900000"
These parameters are especially required for long-running actions like the direct migration.

Backup options

In the administration panel, the following options have been removed from the Backup Configuration:
> Only the model versions with new artifact versions (Check-in versions)
> Include last model version
> Reuse svn repository
The backup option Omit change logs and referenced model versions now also includes referenced model versions of suspect links.

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
10.5.0 10.6.0 10.7.0 10.8.0 10.9.0 10.10.0 10.11.0 10.12.0

Server version
10.5.0 10.6.0 10.7.0 10.8.0 10.9.0 10.10.0 10.11.0 10.12.0

Database server script version 10.5.1.41 10.6.0.02 10.7.0.02 10.8.0.02 10.9.0.03 10.10.0.03 10.11.0.03 10.12.0.02

Metamodel change ID 2022-10-05 2023-04-03 2023-06-01 2023-07-20 2023-09-18 2023-11-13 2024-01-19 2024-03-14

Version 10.20

PREEvision 10.20

Client version
10.13.0 10.14.0 10.15.0 10.16.0 10.17.0 10.18.0 10.19.0 10.20.0

Server version
10.13.0 10.14.0 10.15.0 10.16.0 10.17.0 10.18.0 10.19.0 10.20.0

Database server script version 10.13.0.02 10.14.0.05 10.15.0.02 10.16.0.04 10.17.0.03 10.18.0.01 10.18.0.01 10.20.0.05

Metamodel change ID 2024-05-06 2024-07-08 2024-08-29 2024-11-08 2025-01-07 2025-02-24 2025-02-24 2025-07-24

Migration and update

PREEvision 10.0 SP17 or later can be migrated to PREEvision 10.20.
Migrating to PREEvision 10.20 is only possible from PREEvision 10.0 SP17 or later.
All remote operations (backup and direct migration) available in the PREEvision 10.20 administration panel can only be performed on PREEvision 10.0 SP17 or later. Remote model preparation must be performed on PREEvision 10.0 SP18 or later.
If you want to migrate a PREEvision 10.0 version before 10.0 SP17 or PREEvision 9.5, contact the Vector support.
For the migration to PREEvision 10.20, it is recommended to update PREEvision 10.0 to the latest version (service pack update), at least PREEvision 10.0 SP17, before creating a backup and starting the migration.
An update of PREEvision 10.5 or one of its following minor releases, starting with version 10.6, to PREEvision 10.20 requires no migration and can be performed as minor release update.
An update of PREEvision 10.5 to a following minor release, for example, PREEvision 10.20, 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 > PREEvision staging server > PREEvision administration server > PREEvision SVN gateway > optional: PREEvision API server

Version 10.20

PREEvision 10.20
For detailed instructions on how to update a PREEvision collaboration platform environment, refer to the PREEvision operating manual, chapter "Minor release update".

Version 10.20

PREEvision 10.20

1.3 New features in PREEvision 10.20

Systems engineering explorer

With the Systems Engineering Explorer, PREEvision provides a complete solution for systems engineering in one tool for: > requirements > system specifications > test specifications > software architecture > hardware architecture

The Systems Engineering Explorer offers built-in bidirectional vertical and horizontal traceability tables with an identical user interface.
The PREEvision demo model contains a Systems Engineering Explorer example of a robot vacuum cleaner. Demo model path: "DesignModel" | "Systems Engineering" | "SE Example: Robot Vacuum Cleaner"

Sequence diagram improvements

For sequence diagrams, the following improvements have been implemented:
> You can move Interaction Operands with all contained artifacts within a Simple Combined Fragment or Loop Fragment.
> You can change the distance between Lifelines via the toolbar of the diagram.
> The width of the Lifeline is automatically adjusted to the length of the name of the Lifeline (maximum width 500 pixels).
> Changing the runnable of an Execution Specification no longer dereferences related message representatives.
> You can navigate from the representative of a Lifeline, a message, an Action Execution Specification or an Activity Execution Specification in the diagram to the corresponding representative in the Model View via the shortcut <Alt> + left click.
> Execution Specifications can be assigned to artifacts of the Logical Function Architecture.
> Messages of an Interaction in the Logical Function Architecture can be assigned to all relevant logical port prototypes and their Interface-specific data.
> Messages of an Interaction in the Hardware Architecture can be assigned to Bus Connectors and Conventional Connectors and their associated Signal Transmissions.

Version 10.20

PREEvision 10.20

Functional activity diagram

> Further interaction operators are available on a combined fragment including "Parallel".
> The "Systems Engineering" Product Line Package in the PREEvision demo model is enhanced:
> SysML Concepts: extensions in the Logical Function Architecture demonstrating the supported logical representatives for Execution Specifications and messages.
> Window Lifter Example: Interaction extensions under Logical Function Architecture and Hardware Architecture.
The Functional Activity Diagram is structurally identical to the Activity Diagram but differs semantically regarding the Functional Viewpoint.
In the Functional Viewpoint, you can describe in a creative step what a system shall do, with focus on the control flow and data flow of the individual subsystems. It offers an isolated perspective for every system, from sensors to actuators and from inputs to outputs.
In the Logical Viewpoint, you can describe how subsystems (partitions) shall be integrated and define their interfaces. It offers an integrated perspective of all systems for shared sensors, shared actuators, and system interfaces.

Class diagram

In addition, the following differences apply to the Functional Activity Diagram: > Within one owner, one or more Functional Activities can be created in dedicated
Functional View Packages. > Only logical blocks in the logical architecture of the local Product Line can be
assigned as partition provider. > A logical block can be assigned to multiple partitions within the same Functional
Activity. > Input Activity Data Instances and Output Activity Data Instances are not available. The Window Lifter Example in the "Systems Engineering" Product Line Package in the PREEvision demo model is enhanced by a Functional Activity Diagram example.
In Class Diagrams, all atomic software component types can now be connected to UML Packages as implementation content. The Window Lifter Example in the "Systems Engineering" Product Line Package in the PREEvision demo model is enhanced by implementation content of software component types in a Class Diagram.

Version 10.20

PREEvision 10.20

Importing test scripts into a model subtree

During the import of test scripts from vTESTstudio or CANoe.DiVa, you can now restrict Test Item linking to a model subtree. The model subtree can be selected in the Import Test Script from Test Design Tool dialog. As model subtree, you can select the following artifacts:
> Product Line
> Test
> Test Data
> Test Data Package

Franca

The Franca interface has been extended. Besides the exchange of service interfaces and data types as FIDL files, you can now export Franca deployment (FDEPL) files for SOME/ IP deployments.

IPC binding

For high-performance computers and complex ECUs, the modeling of inter-process communication (IPC) has been simplified. New tables support the modeling of IPC bindings. The attributes needed are defined as AUTOSAR ADMIN-DATA extended by the usage of DaVinci Developer Adaptive Model Extension (DvMex) revision 11.

PREEvision supports the creation of the needed artifacts and the definition of the relevant attributes. Users get an example demo configuration and demo data to integrate DaVinci model extension in their model.
Support for composite PREEvision 10.20 supports the specification of network representation for leaf elements network representation of application composite data types such as application records and application arrays.

Version 10.20

PREEvision 10.20

Enhancements for communication design

For communication design, the following improvements have been implemented:
> The Label of Partial Network Clusters is considered for AUTOSAR import and export as ShortLabel.
> Tp addresses can be named by the attribute Tp Address Name at Tp nodes.
> Multiple Socket Connections can be assigned to one Socket Connection IPDU Identifier.
> Service Instance Packages can be nested and are exported or imported as ServiceInstanceCollectionSets.
> LIN Controller Configuration provides additional attributes for AUTOSAR imports and exports.

Enhancements for Ethernet communication design

For Ethernet communication design in particular, the following improvements have been implemented:
> Ethernet properties can be configured at an Ethernet Configuration Package.
> PREEvision supports the Ethernet Wakeup Sleep On Data Line Configuration and provides additional Ethernet Ip Properties.
> TCP option filters can be defined in a TCP Option Filter Package.

> For Global Time Ethernet Masters, sub-tag length values (Sub-TLV) can be defined. > You can set a preferred VLAN for Port Communication Requirements.

System version

Two new artifacts for version information of software have been introduced. With the System Version Information artifact, you can define the version of a Root Composition. And with the ECU Version Information you can define the version of an ECU extract. With the ECU Version Information you can also define a name of Root Composition Prototypes and Root Composition Types that will be used in the ECU extract.

AUTOSAR consistency For valid models and seamless interaction with downstream tools, PREEvision provides

checks

improved AUTOSAR consistency checks that can be applied to the model more easily.

PVCDI export of units and invalid values for primitive data types

The data exchange with CANdelaStudio has been improved: Units and invalid values that are directly referenced from a primitive data type can now be exported via PVCDI data exchange.
Therefore, no Computation Method is required to export units or invalid values of data types anymore. Invalid value and unit of an existing Computation Method are prioritized by the export framework.

Support of J1939 properties for DTCs

Diagnostic Trouble Codes provide additional attributes. In case the DTC Format of the Fault Memory Diagnostic Instance is set to "J1939":
> Failure mode identifier (FMI) can be set.
> A System Signal with a suspect parameter number (SPN) can be assigned to the Diagnostic Trouble Code.
> The attribute Code needs to be synchronized with FMI and SPN manually or via a metric.

Version 10.20

PREEvision 10.20

Wiring harness explorer The Wiring Harness Explorer has been enhanced with a new category for the

enhancements

Geometry.

The Geometry Overview category of the Wiring Harness Explorer contains three tables:

> The Installation Location to Component Overview table displays the mappings between the Installation Locations and the corresponding hardware including connectors.

> The Topology Inline Connector to WH Inline Connector Overview table displays the mappings between the Topology Inline Connectors and the wiring harness inline connectors including Connector Locations and Wiring Connectors.

> The Topology Segment Overview table displays the Topology Segments, which realize the wires of the Wiring Harness. The path mappings between the individual wires and the segments are displayed as well as specific characteristics of the Topology Segments.

Additionally, traceability tables have been implemented for the Component Overview category and the Inline Connector Design category. The tables display the mappings of components and wiring harness inline connectors to their corresponding topology artifacts in the Geometry.

Diagram-based KBL export with propagation and consistency check

PREEvision offers the possibility to execute a complete and valid KBL export based on diagrams.
The KBL export process comprises different steps, which are supported by individual metrics:

> KBL export preparation including a check of the diagrams and a conversion of the diagram content into a KBL export variant structure

> KBL export consistency checks for checking diagram content for KBL consistency

> KBL export with propagation and KBL export with propagation including consistency checks

The diagram content is checked for relevant artifacts and converted into a KBL export variant structure. The necessary artifacts for the export are propagated automatically based on the extracted diagram content and can be checked for KBL consistency before the final KBL export is executed and the KBL file is generated.

Asset update improvements

Updating Assets from upstream Product Lines will not result in checkouts of locally built Assets, which were previously caused by relations between artifacts of the used and the locally built Assets. This measure significantly improved the performance of Asset updates.
Additionally, when Assets are updated, the relations of their artifacts to artifacts outside the source and target Product Lines are taken over.

Version 10.20

PREEvision 10.20

Moving and copying table filters

Filters that have been saved for a table proxy or a table instance can be moved or copied to another table proxy or table instance via drag and drop, via the context menu, or via shortcuts. As a precondition, the source and the target table must be based on the same table template. You can also move or copy a filter from a table proxy or a table instance to the associated table template.

Suspect links

If the Description of an artifact that is related to another artifact is changed, the related
artifact is automatically marked for review with the suspect links indicator ( ). The suspect links indicator is displayed in the Property View and in tables.
The Suspect Links property page displays detailed information about the changes that have triggered the suspect links indicator. After reviewing the changes and making necessary adaptations, you can remove the suspect links indicator.

The suspect links feature is available for the following relations:

Source artifact Requirement Customer Feature Requirement Customer Feature Requirement
Requirement
Requirement

Relation Assigned Test Item

Target artifact Test Item

Product Goal Link

Requirement

REQ-LA:Mapping

Artifacts of the Logical Function

REQ-HW/LA:Mapping Architecture

REQ-HW/LA:Mapping Artifacts of the Hardware Architecture

REQ-SW:Mapping

Artifacts of the System Software

REQ-SW:Port Mapping Architecture

Version 10.20

PREEvision 10.20

The suspect links feature is deactivated by default. To use this feature, contact the Vector support.

Grouping consistency check results

Consistency check results can now be displayed in groups in the Consistency Check Results view, allowing you to cluster them by subject.
To display groups in the Consistency Check Results view, activate the Use as grouping for consistency-check-results option on the Consistency Rule Groups. Consistency Rules that are contained in a Consistency Rule Group with activated grouping are displayed in this group. Consistency Rules that are contained in a Consistency Rule Group with deactivated grouping are displayed in the "Other Inconsistencies" group.

If grouping is deactivated for all executed Consistency Rule Groups, no groups are displayed in the Consistency Check Results view.

API server extensions

The commit REST call (POST http://<host>:<port>/vCollabAPI/<model>/ transactions/current) responds with a conflict and error code 409 if the changed artifacts are locked by another user. The response now also contains the user name of the user who has locked the artifacts.
Example response:
{ "errorCode": "MDF0008", "errorMessage": "Could not lock artifacts", "details": { "notLockedXmiids": [ 210135, 210134 ], "reserved": [], "lockOwners": { "210135": [ "Mathew.Miller" ], "210134": [ "Mathew.Miller" ] } }
}

The server information REST call (GET http://<host>:<port>/vCollabAPI/ serverinformation) now additionally returns the product version of the API server.
Example response:
{ "buildInfo": { "productVersion": "10.20.0" },

Version 10.20

PREEvision 10.20

Meta model help

...
The PREEvision Metamodel Reference has been revised and now provides: > a compact and visually clear layout > a modern representation > descriptions of packages > meta class names in English and German > diagrams in high resolution

Version 10.20

PREEvision 10.20

1.4 Configuration information

ECU version information

In previous PREEvision versions, the following attributes can be set on the System Information:
> Export Name of Root Composition Prototype
> Export Name of Root Composition Type
In PREEvision 10.20, both attributes have been moved to the ECU Version Information.
The ECU Version Information can be assigned to an ECU and thus can be considered for the AUTOSAR and PVCDI import and export.
There is no automatic migration that moves existing attribute values of the System Information to the ECU Version Information. For migration, manual customization is necessary, if required.

Size limitation for loading and changing the version of an artifact

When loading or changing the version of an artifact, the transfer of the artifact's subtree uses a serialization format that is limited to a size of 2 GB. This corresponds to 9.4 million artifacts or relations. The maximum size refers to the selected artifact and its subtree, as well as additionally required external types and their relations.
Take this limitation into account when you structure the model, so that the affected actions run successfully for your use cases.

In PREEvision 10.0 versions prior to 10.0 SP17 and in PREEvision 10.x versions prior to 10.11, the size of the artifact's subtree is limited to 3.1 million artifacts or relations.

The following actions are affected by the size limitation: > Asset update > replace with version > replace with selected version > restore selected version > reuse historical version > update Asset to historical version in checked-in Product Line (customer-specific
action) > load Product Line in read-only mode (customer-specific action) > compare against historical version > compare for reuse inconsistencies Other actions are not affected, for example: > loading the (full) model and updating the model > loading the scope > backup and restore > migrating models > using Assets

PREEvision 10.20 provides the following performance monitoring measurement point to observe the utilization if the serialization format is used:
> ID: M0.21
> Name: Create Binary Transfer Model Data

Version 10.20

PREEvision 10.20

> Information: Utilization of the artifact storage in percent. Rounded integer value between 0 and 100. Utilization of the relation storage in percent. Rounded integer value between 0 and 100.
Example based on the restore of a version of a Product Line:
[PMON;781b3e460e3a324d0d1214a3c8e350dc;Create Binary Transfer Model Data;202;M0.21]{2025-06-23 13:06:50.4}{2025-06-23 13:06:50.5}{62 ms}{Utilization Artifact Storage [%]: 0.0}{User: c9691a4bfd47a177b35e0ca55cb2dc8e}{Free Memory [%]: 75.42391427689128}{OperationID: M0.21}{Model: LATEST}{Utilization Relation Storage [%]: 0.0}
Note that an Asset update uses the serialization format twice and provides two measurements for each update.

Grouping consistency check results

Consistency check results can now be displayed in groups in the Consistency Check Results view, allowing you to cluster them by subject.
To display groups in the Consistency Check Results view, activate the Use for grouping option on the Consistency Rule Groups. Consistency Rules that are contained in a Consistency Rule Group with activated grouping are displayed in this group. Consistency Rules that are contained in a Consistency Rule Group with deactivated grouping are displayed in the "Other Inconsistencies" group.

Table configuration: Edit event queries

If grouping is deactivated for all executed Consistency Rule Groups, no groups are displayed in the Consistency Check Results view.
When you configure a table column, you can now assign an Edit Event Query. An Edit Event Query can be used to trigger a metric each time you manually change the data within the table column. You can use this, for example, to automatically synchronize names. The Edit Event Query is only applied when you change data within the table. It is not applied when you change data, for example, in the Property View. The Edit Event Query works with: > custom attributes > columns that are configured via Object Configuration > copy and paste > copy and paste via fill handle like in Excel > copy and paste with multi-selection > formatted text editors which are opened from a table The Edit Event Query is not executed through Creation Query, Action Query, or Deletion Query. Undo and redo are supported together with the original manual change.

Version 10.20

PREEvision 10.20

Changed metric blocks: AUTOSAR export

The AUTOSAR Export metric block has a new optional input port "unmodifiableCompositionTypes" (data type: Collection<MCompositionType>, default: NULL). The input is relevant for classic AUTOSAR exports if "delegatePortsAndCreateConnections" is activated. As input, provide a collection of Composition Types that shall not get synthesized delegation ports.

Version 10.20

PREEvision 10.20

1.5 Fixed issues

Fixed issues in PREEvision 10.20

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

Further information

> Common > Diagrams > Tables > Systems engineering > Requirements > Logical function architecture > AUTOSAR > Diagnostics > Communication > Hardware architecture > Geometry > Product line engineering > Variant management > Change and release management > Rules > Metrics > Reports > Collaboration > Administration > Installation > Server API

1.5.1 Common
ID 9082949059433402051

Resolution
When you compare several artifacts in the Property View, and these artifacts reference the same artifact, for example the same Computation Method, the attribute values of the referenced artifact are displayed as identical.

1.5.2 Diagrams
ID 9082949059865002112

Resolution
For use cases or actions which cause diagrams to switch to read-only mode, additional log entries have been added to be able to better trace the cause if the error occurs again.

Version 10.20

PREEvision 10.20

ID 9082949059599843042

Resolution
When opening a diagram containing a Sheet Connector with a label, the label is now displayed at the correct position of the Sheet Connector. No refresh via <F5> is necessary anymore.

1.5.3 Tables
ID 9082949058188121799
9082949059105392105 9082949059405192105 8682711686253683042 9082949059152801995 9082949059154451995
9082947084846791995 9082949059233872101

Resolution
An error with table filters using prototype columns has been resolved. Using an AND combination of two column filters if one of the filtered columns is a prototype column works properly.
You can use the Show Parents button in the table toolbar to display parent artifacts in a filtered table.
Tables in the Property View can be filtered with a predefined filter. Selecting (All) in the drop-down list of the column header resets an active filter.
Configured actions in a table toolbar are reactivated after use.
Metric-based column filters work properly in combined tables.
The table performance has been improved via a configuration adjustment that prevents table updates for specific relations. Additionally, a table in a Portlet View will no longer be updated unnecessarily when it is in the background.
Opening an explorer that directly displays a combined table no longer causes a NullPointerException.
The rendering of formatted texts during the full refresh of a table is done asynchronously. This prevents the client from being sporadically unresponsive.

1.5.4 Systems engineering

ID 9082949058540873108
9082949059768742196

Resolution
Sequence diagrams support combined fragments with more interaction operators to define their semantics including "parallel". A "parallel" combined fragment enables the modeling of concurrent execution between the behaviors of the Interaction Operands of the combined fragment.
The following Object Configuration of a Composite State and an Orthogonal State in a State Machine Diagram are correctly applied:
> Composite State Color
> Orthogonal State Color

Version 10.20

PREEvision 10.20

Resolution

In addition, Composite States and Orthogonal States in a printed or image exported diagram now looks closer to the diagram itself.

1.5.5 Requirements
ID 8682711687572062012
8682711553269751995 9082949059433632105 8682711687649632049 9082949059619392105 8682711554502771992 9082949059397552049

Resolution
The shortcut to open the editor of an artifact shown in a placeholder has been changed from <Ctrl> + click to <Ctrl> +<Shift> + click. This also prevents unwanted opening of editors during cut or copy and paste of placeholders.
ReqIF export: Test Specifications are shown as exported artifacts in the ReqIF Export dialog.
ReqIF export: The caching mechanism for text styles in the ReqIF and Excel export has been improved to prevent loss of styles in rare cases.
ReqIF export: The messages in the Information View after executing a ReqIF export are displayed with consistent text styles.
ReqIF import: The performance of the model analysis step during the ReqIF import has been improved.
ReqIF import: The ReqIF import of formatted texts containing nested text tables no longer leads to tables that are missing a part of the border.
ReqIF import: When canceling the ReqIF import via [Cancel], the import is aborted.

1.5.6 Logical function architecture

ID 9082949058624652042
9082949059534571030

Resolution
In the Create Logical Architecture System Diagram dialog, the Create System Section option has been removed. The option is only present if the diagram is created in a System.
The synchronization of logical ports of a Building Block or Logical Domain from a Logical Architecture (System) Diagram into their contained Logical Architecture Diagram and vice versa has been removed. Therefore, a checked-in Logical Architecture Diagram of a Building Block or Logical Domain will no longer be checked-out if ports will be added or removed to them in other diagrams.

Version 10.20

PREEvision 10.20

1.5.7 AUTOSAR
ID 9082949059106572159 9082947086053982052 9082949059866792108
9082949058960012052 9082949059684152108 9082949059561501024 9082947086163512052 8682711687400921917 9082949059829693089 9082949058959982052 9082949059058522013
9082947086107991024

Resolution
ECU extract: When exporting empty compositions with flattening active, signal ports are exported correctly.
AUTOSAR export: All valid values for the artifact Tag With Optional Value are exported.
AUTOSAR export: Data type mappings are sorted deterministically in the AUTOSAR export. The sorting is determined by the linked application data types and implementation data types.
AUTOSAR export: The system version can be set for AUTOSAR exports.
AUTOSAR export: A performance problem that occurred after the execution of consistency checks has been resolved.
AUTOSAR software cluster design description: <REQUIRED-FIBEX-ELEMENT-REFS> are no longer exported for an Adaptive Software Cluster Design.
AUTOSAR import: Boolean initial values are correctly imported.
AUTOSAR import: As PREEvision does not support more than one MixedTextItem within a list, it will not be imported.
AUTOSAR import: E2EProfileCompatibilityPropsCollection is now imported completely.
AUTOSAR export and import: The naming of CAN-TP ADDRESSEs is stable on import and export.
AUTOSAR export and import: The AUTOSAR export and import with AUTOSAR version 24-11 now support the creation of Coupling Port Details with more than 8 Coupling Port Traffic Classes, FIFO Traffic Class Assignments or Assigned Priorities.
AUTOSAR Adaptive Explorer: The mode of a function group is displayed in the Startup Dependencies Editor of the Software Cluster Deployment category.

1.5.8 Diagnostics
ID 9082949059167491875, 9082949059040662111
9082949059626972113

Resolution
Diagnostic export: The Export Compare metric block indicates deltas in case attribute values are listed in a different order, even if their values are the same.
Diagnostic export: Complex initial values are now exported with correct prioritization of the Name and Value attributes for enumeration type modeling.

Version 10.20

PREEvision 10.20

ID 9082949059137192005 9082949058119532113
9082949058119522113
9082949058885333108

Resolution
Diagnostic export: The attributes AsrDataElementRef and AsrServiceDependencyRef use a single blank as separator to be in line with downstream toolchain.
Diagnostic export: The invalid value of an application data type is consideerd in case there is no Scale Linear Verbal Table Conversion or Linear Verbal Table Conversion used on the data type.
Diagnostic export: The Data Type Unit of an application data type is considered for the export in case there is no Data Type Unit available on the Computation Method or no Computation Method available at all.
J1939 Diagnostic Trouble Codes: The PREEvision metmodel and the Property View have been extended to allow the possibility to set a Failure Mode Identifier (FMI) attribute and an SPN attribute for Diagnostic Trouble Codes relevant for J1939.

1.5.9 Communication
ID 9082949058230361029 9082949059503651807 9082949059801961917 9082947087148943089
9082949058587751807 8682711686993061917 9082949059703791911

Resolution
Frame-PDU synthesis: The frame-PDU synthesis now supports Secured IPDUs which reference Signal IPDUs that are also part of a Container IPDU.
Frame-PDU synthesis: The performance of the framePDU synthesis when synthesizing a lot of Multiplexed IPDUs has been improved.
Frame-PDU synthesis: The Information View indicates Signal Gateway Routing Entries without In/Out transmissions.
Signal router: The correct data type mapping is considered to determine reuseable signals in case of complex classic-adaptive routing with asymmetric data type mappings.
Signal router: Fire and Forget Methods of Service Interfaces which are deployed to software compositions are handled correctly.
Merge signal refactoring: A hint was added to the manual that only artifacts that are not checked-in and have the same revision can be merged.
All valid values can be entered for PNC wakeup attributes of CAN ECU Interfaces.

Version 10.20

PREEvision 10.20

1.5.10 Hardware architecture

ID 9082949059549603090 9082949059073222081
9082949059547642112 9082949059723802083
9082949059795191994 9082949059263652062 9082947085810882062

Resolution
The size of Sheet Connector link boxes is automatically adjusted after splitting a connection to properly display all referenced targets, independent of whether a target range limitation is set via object configuration.
Auto-layout diagrams for wiring harness (diagram-based or model-based auto-layout diagrams) do not support wire bridges, this means wires connected to one inline connector or one Splice cluster. An appropriate error message is displayed which references the affected wires. Appropriate error messages are displayed both when creating the auto-layout diagram via refactoring or via metric.
In the Show/Hide Headers and Pins dialog of a component in an Electric Circuit Diagram or Wiring Diagram individual pins can be selected and deselected again.
In the Assign Pins to Contactings table, assigning and replacing a Hardware Device pin via drag and drop action Assign and Replace Hardware Device Pin, replaces the formerly set Hardware Device pin, removes the Internal Schematic Connection from the replaced Hardware Device pin and reassigns the Internal Schematic Connection to the newly assigned Hardware Device pin.
The wiring harness router properly routes a wire with assigned "Must Use" Condition on a Topology Segment containing a Topology Segment Point.
The Add-in "Electrologic and Harness", which contains the KBL import and KBL export metrics, also contains the corresponding required KBL Custom Attribute Profiles as well as the KBL import and export configuration files, to ensure the proper use of the KBL import and export metrics.
KBL export: For the custom attribute CrossSectionArea, comma separated decimal values are converted into the correct data format (point as decimal separator) and are properly exported to KBL.

1.5.11 Geometry
ID 9082947085784933090

Resolution
When creating a diagram representation of a Connector Location in a Geometry Diagram, for example via drag and drop, only one label is created and displayed instead of two.

Version 10.20

PREEvision 10.20

ID 9082949059154712083 9082949059762252083
9082949059684342112

Resolution
In a Geometry Diagram, the waypoint handles of an Installation Space which has been changed to a polygon, can be selected and moved. Additionally, a feedback figure is displayed.
There are two scenarios for the calculation of a Splice position:
> Calculation of the Branch-Off (as Splice position) based on the shortest total length of all wires connected to the Splice.
> Calculation of the Branch-Off (as Splice position) based on the minimal total weight of all wires connected to the Splice.
If for one or more wires no valid weight can be obtained, for example, if no weight is set on the corresponding Wire Type of the wire or if a wire does not have assigned a Wire Type at all, the calculation falls back to the scenario of a calculation based on the shortest total length.
In the Geometry Diagram, the toolbar buttons to align figures are now activated when multiple Installation Locations within the same Installation Space are selected. The prerequisite for this is that the alignment action does not move a figure outside the Installation Space.

1.5.12 Product line engineering

ID 9082949059066931912
9082949059426142012

Resolution
The checkout of an Asset when routing a wire, which is a core artifact of the Asset, is avoided.
Updating an Asset will no longer trigger an unnecessary checkout of related Assets without predecessors. Because external relations are no longer considered conflicting, updates run faster.

1.5.13 Variant management

ID
9082947086104872042
9082947085110861914, 9082947085889122108, 9082949058825761917, 9082949058111331998

Resolution
The Object Information property page is available for Sets.
The performance problems when opening the VM Explorer or the VM Explorer without Customer Feature Model which were caused by filter configurations set on specific explorer categories, have been resolved.

Version 10.20

PREEvision 10.20

1.5.14 Change and release management

ID 9082949059687992080
9082949059416592105 8682711684953992106 9082949059594142080, 9082947086001030064

Resolution
A problem with the Triggering Changes table on the Suspect Links property page has been resolved: The target artifact was linked to a source artifact that had several reuses with different versions. If the source artifact was deleted, the Triggering Changes table of the target artifact displayed multiple identical entries, although the reuses of the deleted artifact were not linked to the target artifact.
When you select the artifacts that shall be attached to the selected Ticket in the Commit Dataset dialog, deselecting an artifact does not add any other artifacts.
When you compare formatted texts in the Compare perspective, the differences are properly highlighted within the formatted texts instead of highlighting the complete formatted text.
When you compare formatted texts in the Compare perspective, the compared formatted texts are displayed read-only and cannot be edited.

1.5.15 Rules
ID 9082949058805422051

Resolution
Consistency check results can be exported to Excel even if the linked artifacts are no longer available in the model, for example, after an ARXML export.

1.5.16 Metrics
ID 9082949058301642102
8682711686828932024 8682711687341612039 9082949058956302102

Resolution
Log messages of the metric execution status with severity "Info" are only written to the log if the client initialization parameter DshowConfiguration is set to true. Log messages of the metric execution status now include the XMIID and the UUID of the context artifacts.
An error has been fixed that occurred in the identity comparison of the Compare Model Tree metric block.
The Compare Model Tree metric block correctly executes the metric-based matching via a Compare Configuration, if a metric is provided.
Metric tests are now executed in their own context. This prevents concurrent modification exceptions.

Version 10.20

PREEvision 10.20

1.5.17 Reports
ID 9082949058781112105
9082949059685401992

Resolution
Generating reports has been improved in case the generated report contains many bookmarks, for example, for placeholders.
You can define chart settings for generating a report regardless of which PREEvision license you use. All literal artifacts are available in all licenses.

1.5.18 Collaboration
ID 9082949058766053013
9082949058092213104 8682711687346422051
9082949059817891030

Resolution
Changing the installationMode initialization parameter no longer causes an error when loading the local model cache.
The performance of loading a Product Line for comparison has been improved.
A commit error has been fixed that occurred if a user deleted an artifact that had been changed by another user.
An error has been resolved that occurred when replacing an Asset with a version from history and led to unnecessary check-outs.

1.5.19 Administration
ID 9082949059700061868
9082949059708921995 9082949059820342012 9082949059798152080 9082947087364681028 9082949059605602012 9082949058202253046

Resolution
Add-ins now propagate the context artifacts of a Model Context below a metric executor. This allows for the static assignment of artifacts to a Model Context within the scope of a metric executor.
Add-ins now propagate the Table Update Filter for tables.
Add-ins now propagate Consistency Rules and their Quick Fixes for Explorer Categories.
Add-ins now propagate the Query Rule Group that is assigned to a Query Context below a DnD Action.
After an Add-in installation, reuses are synchronized.
An error that caused unwanted relations to be created in the model after an Add-in installation has been fixed.
With partial Add-in delivery, the same checks are performed as with full Add-in delivery.

Version 10.20

PREEvision 10.20

ID 9082949059667723108

Resolution
When the Life Cycle State of a checked-in artifact in a "Version" Type Life Cycle changes, creating a comment during a life cycle transition no longer causes the artifact to be checked-out.

1.5.20 Installation
ID 9082949059424771860

Resolution
In the deploy.properties, the MailFromAuthUser parameter has been added for configuring the email notification in the application server. It is now possible to distinguish between an email user that is used for authentication at the email server and the email address that is used as sender email address.

1.5.21 Server API
ID 9082949059718721861
9082949059688191993, 9082949059874852203

Resolution
In the API server, models are only preloaded when the application server is fully started.
An issue has been fixed that occurred in the API server during the refreshToken REST call when using OpenID Connect authentication.

Version 10.20

PREEvision 10.20

1.6 Known issues

Known issues in PREEvision 10.20

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

ID 17938307791212069
8682711552649222003 8682711555165912106 9082949059853333059 9082949059882312105 9082949059821032062

Known issue
The suspect links feature requires Oracle database version 19.13 or later. To avoid malfunctions, the suspect links feature must be activated by setting a client INI parameter. If you use Oracle database version 19.13 or later and want to use the suspect links feature, contact the Vector support.
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.
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.
ReqIF export: For empty attributes, the string defined in the Text for empty Labels property is exported instead of and empty string. By default, this is "---". Workaround: In the Preferences, under PREEvision | General, remove all characters from the Text for empty Labels property.
When comparing two artifacts, in the Compare perspective one of the Property Views of the artifacts to be compared is, in some cases, not displayed in compare mode. Workaround: Close the Compare perspective and execute the artifact compare again.
In review and vote tables (Review Table) with an active filter, it may happen that a table may not be updated automatically if an attribute value in the table is changed in a way that the active filter would have to filter out the corresponding artifact. Workaround: Deactivate the filter and activate it again.
During KBL export with propagation, more artifacts are exported than were propagated. This is caused by an issue in the export framework. For example, it is currently not possible to export only a specific Connector Location

Version 10.20

PREEvision 10.20

ID 8682711555191801873 8682711685521992014 8682711687181061868 9082949059943151029 9082949059944112068
9082949058916421857 9082949059717192203

Known issue
if its Installation Location is part of the propagated artifacts, since all contained Connector Locations are exported. The exported KBL file however is valid.
During reinitialization of the authority model an error message may be displayed reporting an unexpected error with the ramc.ser file. Workaround:
1. Delete the authority model.
2. Connect to the authority model.
3. Initialize the authority model.
For Application Curve Types and Application Cube Types, the Calibration Attributes property page is missing in the Property View. It will be restored in a future minor release.
The automatic integration of an Asset may be incomplete during use, reuse, or update of the Asset if related artifacts with abstraction or substitution links in a downstream Product Line are read-only. Workaround: Execute the automatic integration again.
Axis Point Number, Axis Value and Function Value, which can be created under a Calibration Parameter Record Layout, are not yet propagated by a software Asset and the corresponding Add-ins. Workaround: Manually assign Axis Point Number, Axis Value and Function Value of each Calibration Parameter Record Layout to the Asset or Add-in.
When updating the "Example Data: Systems Engineering" Demo Add-in, an error may occur that causes the update to fail. The new version of the example data can require changing the type of State Machine conditions from Condition to Non-Parsable Condition. The latter type does not allow child artifacts. The error can occur when Conditions with child artifacts are changed to Non-Parsable Conditions. Workaround:
1. Delete the existing Demo Add-in from your model.
2. Delete the "SE Example: Robot Vacuum Cleaner" Product Line containing the conflicting demo data.
3. Install the new version of the Demo Add-in.
Due to an error in the compatibility check, service packs of minor releases, for example, 10.17 SP1, cannot be used for backup and restore. Workaround: Update to the next minor release without service pack, for example, 10.18.
If the application server is installed on Linux, committing files with a file size larger than 500MB causes an error.

Version 10.20

PREEvision 10.20

ID 9082949059891171896

Known issue
Artifacts that have been unloaded from the temporary scope are kept in memory. Workaround: Commit the model to remove artifacts of the temporary scope from memory.

Version 10.20

2 PREEvision 10.19

This chapter contains the following information:

2.1

Version numbers

2.2

Installation and compatibility information

2.3

New features in PREEvision 10.19

2.4

Configuration information

2.5

Fixed issues

Common

Diagrams

Tables

Requirements

AUTOSAR

Diagnostics

Communication

Hardware architecture

Product line engineering

Test engineering and test management

Rules

Metrics

Collaboration

Administration

License

Backup, restore, and migration

2.6

Known issues

PREEvision 10.19
42 43 45 51 53 53 54 54 55 55 56 56 57 58 58 58 59 59 59 59 59 60

Version 10.20

2.1 Version numbers

Version numbers

Application PREEvision client PREEvision license server PREEvision database server PREEvision application server

Documentation

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

PREEvision 10.19
Version number 10.19.0 3.0.4 10.18.0.01 10.19.0
Version number 10.19.0 10.19.0 10.19.0 10.19.0 10.19.0

Version 10.20

PREEvision 10.19

2.2 Installation and compatibility information
For detailed information about the installation of PREEvision 10.19 and the migration to PREEvision 10.19, refer to the PREEvision operating manual.
For detailed information about the hardware and software requirements of PREEvision 10.19, refer to the PREEvision system requirements.

License server

With PREEvision 10.19, the new version 3.0.4 of the standalone license server is available.
When you use the standalone PREEvision license server (RMI), it is recommended to update the license server to the new version 3.0.4.

System requirements

The following system requirement has been changed: The recommended version of Apache Tomcat has been changed to 9.0.104.

Backup directory

The Configuration page of the administration panel has been removed for security reasons.
You can now define the backup directory in the deploy.properties via the parameter vCollab.Backup.Directory.
You can also set the backup directory in the context file of the application server vCollab.xml via the following parameter:
<Environment name="servermigration/vCollab.Backup.Directory" value="<backup directory>" type="java.lang.String" override="false"/>
The backup directory is automatically created if it does not exist. If the application server has no access rights to write into the directory, a warning is reported in the server log file.
If no backup directory is specified, a backup directory within the workspace directory of the application server is used, for example: %TOMCAT_HOME%\work\Catalina\eclipse\workspace\backup

Compatibility

Client version
10.5.0 10.6.0 10.7.0 10.8.0 10.9.0 10.10.0 10.11.0 10.12.0

Server version
10.5.0 10.6.0 10.7.0 10.8.0 10.9.0 10.10.0 10.11.0 10.12.0

Database server script version 10.5.1.41 10.6.0.02 10.7.0.02 10.8.0.02 10.9.0.03 10.10.0.03 10.11.0.03 10.12.0.02

Metamodel change ID 2022-10-05 2023-04-03 2023-06-01 2023-07-20 2023-09-18 2023-11-13 2024-01-19 2024-03-14

Version 10.20

PREEvision 10.19

Client version
10.13.0 10.14.0 10.15.0 10.16.0 10.17.0 10.18.0 10.19.0

Server version
10.13.0 10.14.0 10.15.0 10.16.0 10.17.0 10.18.0 10.19.0

Database server script version 10.13.0.02 10.14.0.05 10.15.0.02 10.16.0.04 10.17.0.03 10.18.0.01 10.18.0.01

Metamodel change ID 2024-05-06 2024-07-08 2024-08-29 2024-11-08 2025-01-07 2025-02-24 2025-02-24

Migration and update

PREEvision 10.0 SP17 or later can be migrated to PREEvision 10.19.
Migrating to PREEvision 10.19 is only possible from PREEvision 10.0 SP17 or later.
All remote operations (backup and direct migration) available in the PREEvision 10.19 administration panel can only be performed on PREEvision 10.0 SP17 or later. Remote model preparation must be performed on PREEvision 10.0 SP18 or later.
If you want to migrate a PREEvision 10.0 version before 10.0 SP17 or PREEvision 9.5, contact the Vector support.
For the migration to PREEvision 10.19, it is recommended to update PREEvision 10.0 to the latest version (service pack update), at least PREEvision 10.0 SP17, before creating a backup and starting the migration.
An update of PREEvision 10.5 or one of its following minor releases, starting with version 10.6, to PREEvision 10.19 requires no migration and can be performed as minor release update.
An update of PREEvision 10.5 to a following minor release, for example, PREEvision 10.19, requires no update of licenses. PREEvision 10.5 licenses are used for the minor releases following PREEvision 10.5.

Version 10.20

PREEvision 10.19

2.3 New features in PREEvision 10.19

ReqIF import improvements

PREEvision variant information is no longer excluded from the ReqIF import. The variants are imported as custom attributes and transferred as multi value enumerations.
An updating ReqIF import of multi value enumerations is now possible and a changed set of selected values is now correctly processed during import. In addition, it is now possible to change an attribute definition from an enumeration to a multi value enumeration via updating ReqIF import, and vice versa.
REQ-LA:Mappings are no longer excluded from the ReqIF import, Logical Architecture Mappings can be imported as custom attributes with data type String.

Sequence diagram improvements

For sequence diagrams, the following improvements have been implemented:
> Lifelines can now be moved in an Interaction using drag and drop.
> Messages can now be moved and reattached in an Interaction using drag and drop.
> Software architecture artifacts, for example, port types or runnables, can now be assigned from the Model View using drag and drop.
> Reopening an Interaction applies the last zoom setting.
> In the Select Representative dialog for Execution Specifications and messages, a context help into the PREEvision User Manual can now be opened via help button or <F1>.
> To improve performance, the Select Representative dialog for Execution Specifications and messages is now switched from tree view to list view when exceeding a maximum number of represented artifacts. The maximum number of represented artifacts shown in tree view can be defined in the Sequence Diagram preferences.
> Positioning feedback is shown in the Interaction when inserting Execution Specifications.
> Messages of an Interaction in an UML Package in the software layer can now be assigned to Methods and Properties of Classes and Interfaces as well as to content of Service Interfaces.
> The creation of self-messages is now supported.
> The "Systems Engineering" Product Line Package in the PREEvision demo model is enhanced by several Interaction examples:
> SysML Concepts: new System Software Architecture demonstrating the supported software representatives for Execution Specifications and messages.
> Window Lifter Example: Interaction extensions under System Software Architecture and UML Package.

Copying of test items, test item steps and test routines

The copy and paste actions of test artifacts have been extended and integrated into the Test Specification Editor. Copy and paste before/after actions can now also be executed via context menu and shortcuts for the following artifacts: > Test Item -> Test Item > Test Item -> Test Routine > Test Routine -> Test Routine > Test Routine -> Test Item Step

Shortcuts for special paste actions: > Copy before: <Ctrl>+<Shift>+<Arrow up> > Copy after: <Ctrl>+<Shift>+<Arrow down>

Version 10.20

PREEvision 10.19

The copy and paste before/after action of Test Item Steps can be executed via: > drag and drop > context menu > shortcut <Ctrl>+<C> and <Ctrl>+<V>

Relations subject to

New classes can be linked as subject to verify with Test Items for horizontal traceability:

verify and artifact under > SW block instances test
> SW Ports

> Interaction

> Logical block instances

> Logical ports

To define a test specification context, an artifact under test can be assigned to a Test Specification / Test Heading via drag and drop in the Property View.

Support of AUTOSAR 2411

PREEvision 10.19 supports the import and export of AUTOSAR 24-11 files both for AUTOSAR Classic and Adaptive.

Optimization for software architecture modeling

For faster development and smaller model sizes, PREEvision supports the modeling of software architectures without using assembly connectors or delegation ports:
> Assembly connectors are implicit in case provider ports and receiver ports use the same port interface.
> For composition types, delegation ports provide the communication of contained software component types to the outside world. In some scenarios, they do not carry additional information compared to the software ports at the software component type.

In this case, you can reduce the size of the model excluding those artifacts. During AUTOSAR export, PREEvision synthesizes missing assembly connectors and delegation ports temporarily. These artifacts are added to the export file, but do not persist in the model.

Version 10.20

PREEvision 10.19

IO control with client server interface

Diagnostic IO Controls can be realized in the software either by a Sender Receiver Interface or a Client Server Interface. In case of a realization with a Client Server Interface, the I/O control must have a Diagnostic Data Object which is referenced to the Client Server Interface with the relevant Operations and Operation Arguments.

PREEvision 10.19 supports the realization with a Client Server Interface. The Diagnostic Realization Explorer now provides for each use case a dedicated table:
> IO Control SR table
> IO Control CS table

Wiring harness explorer: New table

The Wiring Harness Explorer has been enhanced with a new table in the Wiring Connection Overview category.
The Same Wire Color Combinations at Wiring Connector table provides an overview of all those wires connected to a Wiring Connector which have the same Color or Color Combination. Those wires could cause difficulties in the proper manufacturing of the wiring harness.
The new table is integrated in the Wiring Harness Explorer but can also be opened as a standalone table on a Product Line via context menu Open with | Electrologic and Harness| Same Wire Color Combinations at Wiring Connector.

Asset core artifact modifications performance optimization

Core artifact consistency checks are now bundled and run deferred at the end of interactions/metrics.
Especially Assets with many (propagated) core artifacts benefit from the improved scaling behavior.

Asset creation or refresh warnings in case of product line external core artifacts

Assets always focus on their Product Line. Using or updating an Asset integrates artifacts in the target Product Line even if they are not part of the source Product Line. Such external core artifacts typically mean unwanted dependencies.
During a create or refresh Assets and check-in, a warning is now reported in the Information View if core artifacts are located in a different Product Line than the Product Line of the Asset.
Configurators can easily disable the check, or they can use it to enforce model and Asset quality.

Version 10.20

PREEvision 10.19

Extended filter management in tables

For the extended filter management in tables, the following improvements have been implemented:
> Indicators for unavailable table columns If a table filter uses columns that are not available in the opened table, because they are hidden or have been deleted, an indicator informs you accordingly. In the filter drop-down list, a filter that uses unavailable columns is grayed out. In the Define
Filter dialog, the icon and a tooltip inform you that the column that is used by the selected filter is not available.

> Improved information about multiple paths In the Define Filter dialog, an overview pop-up displays columns that cannot be used for filtering, because they are part of a table configuration with multiple paths. A direct link to the relevant online help chapter provides further information.
> New option for resetting filters With the new Reset Filters option in the filter drop-down list, you can reset an active filter in a table without deactivating column filters.

Version 10.20

PREEvision 10.19
> Dedicated dialog for user-defined column filter Via the User-defined Filter option in the drop-down list of a column header, you can open a dedicated dialog for user-defined column filters. This dialog allows you to apply a user-defined filter on a column that is part of a table configuration with multiple paths.

Search and replace in tables: Editing placeholder attributes

When you replace a placeholder with another placeholder, two new columns in the Replace view display the current Placeholder Attribute and the New Placeholder Attribute. Via a button in the New Placeholder Attribute column, you can open the Edit Placeholder dialog to change the attribute that is referenced by the new placeholder. For attributes with language support, you can also change the language of the attribute.

Quick fixes for consistency checks

In the Consistency Check Results view, a new column has been added that displays the
Quick Fix State. The icon indicates that a Quick Fix is available for an inconsistency. Via the context menu, you can execute Quick Fixes for single or multiple elements that
are listed in the Consistency Check Results view. The icon indicates that a Quick Fix has already been executed for an inconsistency.

Via the button in the toolbar of the view, the consistency check results can be recalculated for the same artifacts and checks.

Information view: severity decorators for custom icons

If a custom icon has been defined for the Information View, the severity of an entry can now be identified at the top level of the entry. For entries with the severity "Error", the
decorator is added to the custom icon, and for entries with the severity "Warning", the decorator is added to the custom icon.

API server extensions You can now configure if and which models shall be loaded in advance during the API server start-up. This significantly reduces the duration of the initial login.

Version 10.20

PREEvision 10.19

It is now possible to retry the commit of a transaction if the commit call returned a lock conflict (response code 409).
For detailed information, refer to the PREEvision server API manual.

Overview of artifacts that are not part of an add-in

The Configuration without Add-in Reference table provides an overview of all artifacts in a subtree that are not part of an Add-in. The table is delivered with the product Add-in "Add-ins Development".

Version 10.20

PREEvision 10.19

2.4 Configuration information

Size limitation for loading and changing the version of an artifact

In PREEvision 10.0 versions prior to 10.0 SP17 and in PREEvision 10.x versions prior to 10.11, the size of the artifact's subtree is limited to 3.1 million artifacts or relations.

New metric blocks: Diagnostic operation creator

The Diagnostic Operation Creator metric block can be used to create dedicated Operations of a Client Server Interface used for diagnostics. Palette category: Diagnostic Required inputs (Data Target Ports): > "interface" (data type: MClientServerInterface): The Client Server Interface in
which the Operation is to be created. > "requiredOperation" (data type: String): Operation to be created.
Possible values: > ReadData > WriteData > ReturnControlToECU > ResetToDefault > FreezeCurrentState > ShortTermAdjustment > Start > Stop > RequestResult

Version 10.20

PREEvision 10.19

Outputs (Data Source Ports): > "infoView" (data type: MInformation)
> "interface" (data type: MClientServerInterface): Returns the changed Client Server Interface.

Changed metric blocks: AUTOSAR export

The AUTOSAR Export metric block has a new optional input port "delegatePortsAndCreateConnections" (data type: Boolean, default: false) which is relevant for classic AUTOSAR exports. If set to true, necessary delegation ports are temporarily created and exported. In case when provider and receiver share the same port interface, assembly and delegation connectors are temporarily created and exported.

Changed metric blocks: The Export Compare metric block has a new output port "numberOfDifferences" (data

Export compare

type: Long) which returns the number of differences between the compared files.

Version 10.20

PREEvision 10.19

2.5 Fixed issues

Fixed issues in PREEvision 10.19

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

Further information

> Common > Diagrams > Tables > Requirements > AUTOSAR > Diagnostics > Communication > Hardware architecture > Product line engineering > Test engineering and test management > Rules > Metrics > Collaboration > Administration > License > Backup, restore, and migration

2.5.1 Common
ID 9082949058725391003
9082949058777642039
9082949058587232105 9082949058652072039

Resolution
In the PREEvision configuration manual, the chapter "Filtering the context menu" has been updated. It now correctly describes how to filter submenus by using the PARENT-ID as MENU-ID for filtering.
When switching a perspective which contains a Model View without filters but with Query Rule Groups that extend the model tree, the Model View is now correctly refreshed.
If you work with a split editor area displaying several editors at the same time, the focus is maintained after you commit your changes.
In the Model View, the performance of loading folders that are displayed via Query Rule Groups has been improved.

Version 10.20

PREEvision 10.19

2.5.2 Diagrams
ID 9082947086053671874
9082947086141341204 9082949058744152081 8682711687197671999
9082949058764532045

Resolution
In the Populate Artifact dialog, the naming of the different populate tabs has been adjusted. The naming of the tabs has been changed to Classic, Advanced and Metric-based. The descriptions of the different populate functions have been adjusted accordingly.
It is no longer possible to paste artifacts via Paste as copy from a diagram into the Model View. The Paste Layout functionality is not affected.
Icons of diagrams which are set via object configuration are displayed in the diagram tab as well. This is possible especially if the object configuration uses constraints.
Multiple diagrams in the Label Configuration view have been renamed from "Editor" to "Diagram". For example, Lifecycle Editor has been renamed to Lifecycle Diagram.
Diagrams which are opened in the background, for example when executing an action in a table which requires the execution of the Diagram Artifacts Collector block, do not persist their last viewport information (position, zoom level) when the diagram is closed. No error concerning the former viewport information is displayed anymore.

2.5.3 Tables
ID 9082949058780840064
9082949058332872112 9082949058542013126, 9082949058696092111
9082949059131373082, 9082949058931410099
9082949059265921897

Resolution
When you add a temporarily opened table to the model as Table Proxy, the Define Filter dialog can only be opened after the creation of the Table Proxy has been completed. This prevents an active table filter from being erroneously displayed as invalid in the Define Filter dialog.
In table cells that are read-only, no buttons for opening a cell editor are displayed.
For table cells that contain multiple artifacts, the selection propagation works properly. If you select one of the artifacts in the table cell, only the selected artifact is selected in the Model View and in the Property View as well.
An artifact in a table cell can be copied to the table cells below using the fill handle, even if the action query of the table cell is implemented by a metric executor that has an enablement condition.
If replacing text with an artifact creates several placeholders within the same formatted text, each of the created placeholders is unique and can be edited separately.

Version 10.20

PREEvision 10.19

2.5.4 Requirements
ID 9082949058606162105
9082947087398773082
9082949059146672101

Resolution
ReqIF export: Borders around images in formatted texts are ignored when exporting them as ReqIF. The borders do therefore no longer cause ReqIF schema validation errors.
ReqIF import: PREEvision variant information is no longer excluded from the ReqIF import. Variants are imported as custom attributes. They are transported as multi valued enumerations from the exporting PREEvision instance.
ReqIF export: The entry exportExternalLinks in the ReqIF export configuration file no longer has any effect on the test data export. This also removes the observed need for writing access to requirement data during the test data ReqIF export.

2.5.5 AUTOSAR
ID 8682711687278812051, 8682711687278822051 9082949059040982014
9082949058938152010 9082949058910332010 9082947087131372051

Resolution
Consistency checks: Redundant checks for initial values have been consolidated. All related checks were renamed according to a new naming convention.
Consistency checks: Several AUTOSAR checks have been corrected for service-oriented architecture use cases.
Consistecy checks: Several AUTOSAR checks of the rule group "ServiceNeeds" have been renamed or fixed.
Consistecy check: Several AUTOSAR checks for the Internal Behavior have been renamed or fixed.
Consistency check: The following checks will not hit anymore for an Application Literal with a string as value that is used as an initial value in combination with a Bit Table Conversion.
> cac1221_DataTypedInformationUnit_with_invalid_ InitValue_for_Enumeration
> cac1221_NvDataReceiverComSpec_with_invalid_ InitValue_for_Enumeration
> cac1221_ParameterRequiredComSpec_with_ invalid_InitValue_for_Enumeration
> cac1221_SenderComSpec_with_invalid_InitValue_ for_Enumeration
> cac1221_ParameterProvidedComSpec_with_invalid_ InitValue_for_Enumeration
> cac1221_ReceiverComSpec_with_invalid_InitValue_ for_Enumeration

Version 10.20

PREEvision 10.19

ID 9082949058715811808 9082949058915433089 9082949058913151913
9082949058888481024
9082949059029172052, 9082949059029202052
9082949058985521024 9082949059077491024 9082949058766582052

Resolution
AUTOSAR export: The creation of J1939-ClusterConditional in export has been corrected.
AUTOSAR export: Data constraints of implementation data types are now merged by ImEx-ID as well.
AUTOSAR ECU extract: The constant specification mappings are completely exported if they are entirely defined in the application and implementation domains.
AUTOSAR import and export: The roundtrip for ARPackages and their assigned artifacts has been corrected.
AUTOSAR import: The import considers AUTOSAR version specific modeling of the LIN attributes P2 Max, P2 Timing and Max Number Of Resp Pending Frames for LIN Tp Nodes.
AUTOSAR import: If circular static socket connections exist in the import file, the import file will be rejected.
AUTOSAR import: Exceptions during AUTOSAR import regarding integer literals without values are prevented.
Dereferencing a port from an Assembly SW Connector in Property View is possible.

2.5.6 Diagnostics
ID 9082949059058452005
9082949059040662111 9082949058940182113

Resolution
In the Diagnostic Realization Explorer and the Diagnostic Concept Explorer, columns for the attributes Automatic end and Cycle status storage have been removed from the tables for the Diagnostic Operation Cycle.
Diagnostic export: The Export Compare metric block indicates deltas in case attribute values are listed in a different order, even if their values are the same.
Diagnostic export: The export considers only the relevant Sender Communication Specification or Receiver Communication Specification in the context of diagnostic data objects.

2.5.7 Communication
ID 9082949058766041024

Resolution
Signal router: When starting the signal router on a Composition, both sending and receiving ports will be routed.

Version 10.20

PREEvision 10.19

ID 9082949058831252005

Resolution
The context menu for Communication has been reorganized with a sub menu for communication packages.

2.5.8 Hardware architecture

ID 9082949058444430084
9082949058911022083 9082949058696772045 9082949058827091037
9082949058712912041
9082949058928113104

Resolution
An issue during ground spot optimization with activated preference Exclude from active variant has been corrected. If multiple wires, Splices or Wiring Harness Inline Connectors are excluded from the active variant, all hardware to topology mappings of those artifacts are excluded from the active variant, instead of excluding only the mappings up to the first Splice or Wiring Harness Inline Connector.
When executing the refactorings Assign Connector Type and Create Wiring Connector or Assign Connector Prototype and Create Wiring Connector for a Splice, the relation between the created Contacting at the Wire Pin of the Splice and the connected wire is set.
When trying to commit a model structure which has been identified as invalid (for example invalid modeling of internal connections between internal and external Hardware Devices), the client no longer switches to readonly mode. The client instead rejects the commit and creates a bug report. Additionally, an error dialog including an information view entry is reported.
In the Select Cable dialog, the Show recently used Cables option triggers an update of the table content when changes are made. Show recently used Cables in this context means that the last ten artifacts (Cables) which have been used in this dialog before, are displayed when activating the option. The creation of a new Cable or Core in the Model View does not mean this artifact is "recently used" and is displayed in the dialog.
An issue has been resolved for the Show/Hide Headers and Pins function in Electric Circuit Diagrams and Wiring Diagrams. If a Component Combination and one of its child components are placed in the same section or diagram area, hiding pins of one component does not remove those pins from the other. Showing pins that are already shown by the other component displays them correctly.
When routing Cables during wiring harness routing, it is irrelevant, for different Cores of the same Cable, whether the routing endpoint is a Connector Location or a BranchOff.

Version 10.20

PREEvision 10.19

2.5.9 Product line engineering

ID 9082949058960402101 9082949059246591914 9082949059272632012
9082949059137202012
9082949059245042012
9082949059034181804

Resolution
An Asset update no longer changes the type of the asset-external instance to asset-internal.
The use of an illegal external type (external type of source Asset is part of updated Asset) no longer leads to a stack overflow if an artifact has multiple different types.
The Asset propagation now considers units of data constraints (generic, long, double) assigned to application data types (boolean, enumeration, value, array, record, axis) or implementation data types (array, value, vector, reference).
Loading an historical version of a Product Line including the historical context relations does not establish relations to external artifacts at a specialization relation end anymore. This requires less locks.
Core artifact consistency checks are now bundled and run deferred at the end of interactions/metrics. The execution time for an Asset with 100,000 core artifacts can decrease from 1.5 hours to 9 seconds.
The performance for Asset creation and refresh has been significantly improved, especially for a large number of core artifacts, for example 100,000 core artifacts, due to an optimization of the core artifact consistency checks. The execution time for an Asset with 100,000 core artifacts can decrease from 1.5 hours to 9 seconds.

2.5.10 Test engineering and test management

ID 9082949058711163082
9082949059093361030

Resolution
Multiple Test Items of different source Test Specifications can be moved into a new Test Specification.
For classes, for example Test Case Runs, for which custom attribute values can be set, these can now be displayed again.

2.5.11 Rules
ID 9082947084956741792
9082949058279521918, 9082947085602182023

Resolution
Multi Classifier Object LHS artifacts are now properly displayed on the Objects property page of MofClasses.
In the Consistency Check Results view, the error message that is displayed if the number of results exceeds the limit has been adjusted.

Version 10.20

PREEvision 10.19

2.5.12 Metrics
ID 9082949058107302024 9082947085943102039

Resolution
Metric Diagrams are no longer unintentionally closed.
The Get Assets from Upstream to Convert Foreign Relations block can now handle downstream artifacts that are not located in Product Lines.

2.5.13 Collaboration
ID 9082949058733102049 9082949058963781992 9082949059042141849

Resolution
Removing an artifact from the temporary scope unloads only the temporarily added artifacts.
A performance optimization has been implemented for loading a model from the hard disc.
An issue during a Replace With Selected Version has been resolved. The correct instance relations for external types are created.

2.5.14 Administration
ID 9082949058137631995

Resolution
The "Defining life cycle transition constraints" chapter of the PREEvision configuration manual now includes additional information on naming the Model Context and how life cycle transition execution depends on the severity of the consistency checks.

2.5.15 License
ID 9082947087399592054

Resolution
The logging of the license server has been improved to avoid unnecessary log entries.

2.5.16 Backup, restore, and migration

ID 9082947085101292020

Resolution
During the backup process, the richtexts directory, in which formatted texts are stored, is cleaned up after the verification model has been written.

Version 10.20

PREEvision 10.19

2.6 Known issues

Known issues in PREEvision 10.19

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

ID 17938307791212069
8682711552649222003 9082949059058522013 8682711555165912106
8682711687572062012 9082949059167491875 8682711555191801873

Known issue
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.
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.
AUTOSAR export and import with AUTOSAR version 24-11 do not support the creation of Coupling Port Details with more than 8 Coupling Port Traffic Classes, FIFO Traffic Class Assignments or Assigned Priorities.
ReqIF export: For empty attributes, the string defined in the Text for empty Labels property is exported instead of and empty string. By default, this is "---". Workaround: In the Preferences, under PREEvision | General, remove all characters from the Text for empty Labels property.
Using the control-key to navigate in a formatted text which contains a placeholder or using shortcuts to cut or copy and paste a placeholder may lead to editors being opened in the background. Workaround: Close the opened editors and continue.
The Export Compare block for PVCDI files has identified differences in the order of artifacts even if the order is not relevant. This occurs for listed attribute values inside an Attribute Definition and for enumeration values inside an enumeration entry.
During reinitialization of the authority model an error message may be displayed reporting an unexpected error with the ramc.ser file. Workaround:
1. Delete the authority model.
2. Connect to the authority model.
3. Initialize the authority model.

Version 10.20

PREEvision 10.19

ID 8682711685521992014 8682711687181061868
9082947085110861914, 9082947085889122108
9082949058188121799
9082949058916421857

Known issue
For Application Curve Types and Application Cube Types, the Calibration Attributes property page is missing in the Property View. It will be restored in a future minor release.
The automatic integration of an Asset may be incomplete during use, reuse, or update of the Asset if related artifacts with abstraction or substitution links in a downstream Product Line are read-only. Workaround: Execute the automatic integration again.
Opening the VM Explorer or the VM Explorer without Customer Feature Model may lead to performance problems. This may be due to filter configurations which are set on specific explorer categories. Workaround: Customize the corresponding "VM Explorer" and "VM Explorer without Customer Feature Model" Add-ins, and remove the Explorer Filter Configurations set on the affected explorer categories.
If you define an AND combination of two prototype column filters where the content of one column is defined via a search query and the content of the other column is defined without using a search query, the filter result might be wrong. Workaround: If you filter combinations of prototype columns, make sure that all filtered prototype columns are based on search queries.
Due to an error in the compatibility check, service packs of minor releases, for example, 10.17 SP1, cannot be used for backup and restore. Workaround: Update to the next minor release without service pack, for example, 10.18.

Version 10.20

3 PREEvision 10.18

This chapter contains the following information:

3.1

Version numbers

3.2

Installation and compatibility information

3.3

New features in PREEvision 10.18

3.4

Configuration information

3.5

Fixed issues

Common

Diagrams

Tables

Requirements

Logical function architecture

AUTOSAR

Software architecture

Diagnostics

Hardware architecture

Geometry

Product line engineering

Metrics

Collaboration

Administration

3.6

Known issues

PREEvision 10.18
63 64 67 72 74 74 74 75 75 75 76 77 77 77 78 78 79 79 79 81

Version 10.20

3.1 Version numbers

Version numbers

Application PREEvision client PREEvision license server PREEvision database server PREEvision application server

Documentation

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

PREEvision 10.18
Version number 10.18.0 3.0.3 10.18.0.01 10.18.0
Version number 10.18.0 10.18.0 10.18.0 10.18.0 10.18.0

Version 10.20

PREEvision 10.18

3.2 Installation and compatibility information
For detailed information about the installation of PREEvision 10.18 and the migration to PREEvision 10.18, refer to the PREEvision operating manual.
For detailed information about the hardware and software requirements of PREEvision 10.18, refer to the PREEvision system requirements.

License server

With PREEvision 10.18, the new version 3.0.3 of the standalone license server is available.
When you use the standalone PREEvision license server (RMI), it is recommended to update the license server to the new version 3.0.3.

System requirements

The following system requirement has been changed: VisualSVN Server 5.4.3 is recommended for the PREEvision Subversion server.

Server configuration

The Java parameters for the Java Virtual Machine have been changed.
The following Java parameters must be set for the start-up of Apache Tomcat:
--add-modules=ALL-SYSTEM --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/sun.nio.ch=ALL-UNNAMED --add-opens=java.base/java.nio=ALL-UNNAMED --add-opens=java.base/java.lang.reflect=ALL-UNNAMED --add-opens=java.base/java.text=ALL-UNNAMED --add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.desktop/java.awt.font=ALL-UNNAMED
These Java parameters have been updated in the preconfigured Apache Tomcats of all server components. For manually configured Apache Tomcats, update the parameters on all server components.

The following parameter must no longer be set for the start-up of the application server and the standalone middleware license server:
Djdk.util.zip.disableZip64ExtraFieldValidation=true

Compatibility

Client version
10.5.0 10.6.0 10.7.0 10.8.0

Server version
10.5.0 10.6.0 10.7.0 10.8.0

Database server script version 10.5.1.41 10.6.0.02 10.7.0.02 10.8.0.02

Metamodel change ID 2022-10-05 2023-04-03 2023-06-01 2023-07-20

Version 10.20

PREEvision 10.18

Client version
10.9.0 10.10.0 10.11.0 10.12.0 10.13.0 10.14.0 10.15.0 10.16.0 10.17.0 10.18.0

Server version
10.9.0 10.10.0 10.11.0 10.12.0 10.13.0 10.14.0 10.15.0 10.16.0 10.17.0 10.18.0

Database server script version 10.9.0.03 10.10.0.03 10.11.0.03 10.12.0.02 10.13.0.02 10.14.0.05 10.15.0.02 10.16.0.04 10.17.0.03 10.18.0.01

Metamodel change ID 2023-09-18 2023-11-13 2024-01-19 2024-03-14 2024-05-06 2024-07-08 2024-08-29 2024-11-08 2025-01-07 2025-02-24

Migration and update

PREEvision 10.0 SP17 or later can be migrated to PREEvision 10.18.
Migrating to PREEvision 10.18 is only possible from PREEvision 10.0 SP17 or later.
All remote operations (backup and direct migration) available in the PREEvision 10.18 administration panel can only be performed on PREEvision 10.0 SP17 or later. Remote model preparation must be performed on PREEvision 10.0 SP18 or later.
If you want to migrate a PREEvision 10.0 version before 10.0 SP17 or PREEvision 9.5, contact the Vector support.
For the migration to PREEvision 10.18, it is recommended to update PREEvision 10.0 to the latest version (service pack update), at least PREEvision 10.0 SP17, before creating a backup and starting the migration.
An update of PREEvision 10.5 or one of its following minor releases, starting with version 10.6, to PREEvision 10.18 requires no migration and can be performed as minor release update.
An update of PREEvision 10.5 to a following minor release, for example, PREEvision 10.18, requires no update of licenses. PREEvision 10.5 licenses are used for the minor releases following PREEvision 10.5.

Version 10.20

PREEvision 10.18
For detailed instructions on how to update a PREEvision collaboration platform environment, refer to the PREEvision operating manual, chapter "Minor release update".

Version 10.20

PREEvision 10.18

3.3 New features in PREEvision 10.18

Sequence diagram improvements

For sequence diagrams, the following improvements have been implemented:
> Activities and Actions can be assigned to Activity Execution Specifications/Action Execution Specifications in the diagram via drag and drop.
> Non-Parsable Conditions of Interaction Operands can now be created in the diagram via the Palette.
> A new type of Execution Specification is introduced for an Interaction in the System Software Architecture layer allowing assignments to Compositions, software components, and Runnables.
> Messages of an Interaction in the System Software Architecture layer can now be assigned to all relevant port types and their interface-specific data. Additionally, a message can be assigned to a Runnable of the target SW Component Type.

Support of record layouts

In AUTOSAR, record layouts describe how data objects are stored and serialized in the memory of an ECU.

In PREEvision the record layout for calibration parameters can be defined using a Calibration Parameter Record Layout that corresponds to the AUTOSAR meta class SwRecordLayout. Within the Calibration Parameter Record Layout, you can define artifacts representing the number of axis points, the axis values and the function value. PREEvision supports the export and import or record layouts for calibration parameters via AUTOSAR.

Version 10.20

PREEvision 10.18
Software composition The composition type structure diagram provides a quick overview of the hierarchical type structure diagram structure of a Composition Type.

The read-only diagram displays a Composition Type and the software types and composition types it contains and allows easy navigation through the structure. Therefore, the diagram behaves differently from the other diagrams in PREEvision:
> You do not have to model the diagram. The layout is automatically created.
> You always see the current structure of the composition type. Any changes in the composition type are automatically reflected in the diagram. For example, if you add an Atomic SW Component Prototype to the "SystemSWA", the Atomic SW Component Type will immediately be visible in the diagram.
> Since the diagram is read-only, no locks or check-outs are needed when working with the diagram.

Hardware library explorer

The Hardware Library Explorer for the electrologic and harness layers has been enhanced by new categories and additional tables. The following categories with corresponding tables have been added: > Connector Type Overview > Pin Type Overview > Seal and Plug Type Overview

Refactoring for creating missing wiring connectors

The refactoring Create missing Wiring Connectors has been adapted with respect to the naming of created Wiring Connectors. The Wiring Connector created for the Header receives the same name as the associated Header to facilitate the assignment between Wiring Connector and Header.

When creating an appropriate Wiring Connector for a Header via the refactoring, the refactoring automatically creates the following assignments:

> The Wire Pins of the Wiring Connector are automatically assigned to the Wiring Cavities of the created Wiring Connector if the pin numbers of the Wire Pins match the cavity numbers of the Wiring Cavities. The corresponding pin Contactings via which the Wire Pins are assigned to the Wiring Cavities are created as well.

> If a Wire Pin has an assigned wire, the relation between pin Contacting and wire is set automatically.

Additionally, the Create Missing Wiring Connectors block can be used to create an appropriate Wiring Connector for an already defined Header.

Version 10.20

PREEvision 10.18

Refactoring for creating The refactoring Create missing Installation and Connector Locations has been

missing installation

enhanced. The refactoring can now additionally be carried out on a Component Package.

locations and connector When carrying out the refactoring on a Component Package, Installation Locations,

locations

Connector Locations as well as corresponding mappings are created for all components

of the Component Package.

Test specification editor In the Test Specification Editor, the role of a Test Item Step or a Test Routine can be set

improvements

via a drop-down list in the Type column. If the role is changed, the Test Item Step or the

Test Routine is automatically reordered accordingly.

Artifacts displayed in the Test Specification Editor can be ordered via the drag and drop menu.

Filtering table cells with In columns that display multiple values in one cell, you can use the predefined filter to

multiple values

filter for single values.

Version 10.20

PREEvision 10.18
Via the Define Filter dialog, you can create filter definitions that combine the single values of a cell with AND, OR, XOR, and NOT operators.

Searching and replacing placeholders in tables

In tables, you can search and replace placeholders in formatted text that reference a specific attribute of an artifact. To search for a placeholder, insert the artifact that is referenced by the placeholder via drag and drop from the Model View into the search field. To replace the placeholder with another placeholder, you can insert another artifact into the replace field.

In the Search result view and in the Replace view, the search values and the replace values are highlighted in blue gray.

Version 10.20

PREEvision 10.18

Searching and replacing in multiple table columns

For searching and replacing attribute values in tables, you can now select several columns that contain attribute values of the same data type.

An additional column in the Search result view and in the Replace view displays the column of the result.

Bug report improvements

The Create Bug Report dialog has been improved.
The location of the saved bug report in the file system is displayed in the Information View.

Version 10.20

PREEvision 10.18

3.4 Configuration information

Size limitation for loading and changing the version of an artifact

In PREEvision 10.0 versions prior to 10.0 SP17 and in PREEvision 10.x versions prior to 10.11, the size of the artifact's subtree is limited to 3.1 million artifacts or relations.

New metric blocks: Create missing wiring connectors

The Create Missing Wiring Connectors metric block can be used to create an appropriate Wiring Connector for an already defined Header. The metric block can be executed on a hardware component which has an assigned Header. If the Connector Type of the Header has a defined applicable opposite Connector Type with corresponding Connector Prototype, the Wiring Connector receives this defined Connector Type and Connector Prototype. Based on the structure and content of the Connector Prototype, slots, cavities and contactings for the Wiring Connector are created as well. Wires connected to the Wire Pins of the Wiring Connector are directly assigned to their corresponding contactings.
Palette category: Electrologic and Harness
Required inputs (Data Target Ports):
> "components" (data type: List<MDetailedElectric>): One or multiple components for which missing Wiring Connectors shall be created.
> "wiringHarness" (data type: MWiringHarness): Location where the created Wiring Connectors are stored.

Changed metric blocks: The functionality of the "suppressInfoView" Data Target Port of the Get Workspace metric

Get workspace

block has been corrected. If "suppressInfoView" is set to true, no results are reported in

the Information View.

Version 10.20

PREEvision 10.18

Changed metric blocks: The behavior of the following input ports of the Model Export metric block has been

Model export

changed:

> "exportElement" Data Target Port: Defines the artifacts that shall be exported to an EEA file. If the Data Target Port "exportActiveVariantOnly" is set to true, all artifacts and their child artifacts that are part of the active variant are considered for the export.

> "setToAddExportedArtifacts" Data Target Port: If an active variant is exported ("exportactiveVariantOnly"= true) the port defines a Set to which all exported artifacts are added. Known issue: The assignment to the Set does not work properly, use the export wizard instead.

Version 10.20

PREEvision 10.18

3.5 Fixed issues

Fixed issues in PREEvision 10.18

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

Further information

> Common > Diagrams > Tables > Requirements > Logical function architecture > AUTOSAR > Software architecture > Diagnostics > Hardware architecture > Geometry > Product line engineering > Metrics > Collaboration > Administration

3.5.1 Common
ID 8682711554206582001
8682711554420462023 9082949058624632105

Resolution
The Quick Fix View only takes focus when a new quick fix entry is created. The focus is not changed if the quick fix entries stay the same or if entries are removed.
In the Create Bug Report dialog, the file name of the bug report is kept while browsing for a file location.
A check has been added to avoid an error that occurred when closing the client.

3.5.2 Diagrams
ID 9082949058595701995

Resolution
Selecting multiple labels with <Ctrl> + <Shift> in a diagram and resizing them, no longer moves the selected labels to the same position. If the selected labels have the same orientation, they are resized by maintaining their current position. If the selected labels have a different orientation, the resize operation is prohibited.

Version 10.20

PREEvision 10.18

3.5.3 Tables
ID 9082949058415842107
9082949058780900064
8682711555198283126

Resolution
If tables with charts are filtered, parent artifacts that are displayed in the table via the corresponding button in the table toolbar are not considered in the chart or the chart table.
In the Define Filter dialog, clicking on the edit button for Predefined Filters always opens a dialog where you can select the filter values. The selection is only applied when you click on the [Select] button.
In the selection dialog for setting attributes with multiple values and in the selection dialog for predefined column filters, the button label has been changed to [Apply].

3.5.4 Requirements
ID 8682711555133422025 9082949058348522106 9082949058770942105
9082949058678982042
9082949058578293082 9082949058529122100

Resolution
<Ctrl> + click on a preview image in a formatted text opens the linked File Attachment.
A deadlock has been solved that could occur when exporting certain constellations of OLEs via ReqIF or Excel export.
ReqIF import: Improved robustness when embedded objects (file attachments) contain additional technical tags. Additionally, the robustness of the import has been improved in case of various errors in the ReqIF file.
ReqIF import: During import of files containing ReqIF tool extensions which are not supported due to their structure appropriate information is reported in the Information View.
Improved robustness of the ReqIF export in case formatted texts contain file links with invalid file paths which cannot be resolved in the Windows file system.
In the Requirement Text Editor, all formatted texts are displayed with the same font size, independently from the monitor resolution and scaling of the user who creates the texts. Formatted texts that are loaded from the database have the same font size as formatted texts that are stored locally.

3.5.5 Logical function architecture

ID 9082947086141342042

Resolution
The selection of multiple ports in Logical Architecture System Diagrams is propagated in the Model View.

Version 10.20

PREEvision 10.18

ID 9082949058501851030

Resolution
When creating an Assembly connection in a Logical Architecture System Diagram between two Logical Functions, which are located in different Building Blocks or Logical Domains, and starting from an existing port the newly created target port automatically adopts the name and interface of the existing Port Prototype.

3.5.6 AUTOSAR
ID 9082949058403491024 9082949058444431024 9082949058183071024
9082949058777491852
9082949058539521911 9082949058736571807 9082947086005442051
9082949058698872003
9082949058708432108

Resolution
AUTOSAR import: AUTOSAR Adaptive 2011 files that contain a UCM-Module-Instantiation can be imported.
AUTOSAR import: AUTOSAR Adaptive 2011 files that contain an IDSM-Module-Instantiation can be imported.
AUTOSAR import: The import can handle AUTOSAR Adaptive 20-11 files that contain a PlatformModuleEthernetEndpointConfiguratio n.
AUTOSAR import: When importing an AUTOSAR file that contains an artifact without short name, an error dialog and detailed information in the Information View are shown.
AUTOSAR export: ECU extracts contain the Sender Receiver To Signal Group Mappings of degraded Signals.
AUTOSAR export: Data Transformations are exported in the AUTOSAR system description.
AUTOSAR export block: For child elements of MIExecutionOrderConstraints and MIEOCExecutableEntityRefGroups no default sorting is applied.
Consistency checks: PREEvision provides the two new checks "cac2544_ApplicationValueType_with_invalid_MinMax_V alue" and "cac2544_ApplicationValueType_with_invalid_MinMax_T ypeReference" that cover the AUTOSAR constraint 2544.
Consistency checks: The obsolete rules c3010 and c3013 have been removed. The rules c3009, c3011, and c3012/px3050 have been optimized to improve performance.

Version 10.20

PREEvision 10.18

3.5.7 Software architecture

ID 9082947087294201807

Resolution
The Property View of software artifacts correctly shows BSW-NET Mappings.

3.5.8 Diagnostics
ID 9082949058664103056 9082949058829732113 9082949058193642113 9082949058691422111
9082949058768562005

Resolution
Diagnostic export: Freeze Frame Data Assignments and Diagnostic Routine operations are considered when exporting variants.
Diagnostic export: Default values of data types that are used multiple times are exported, even for Application Enumerations.
Diagnostic export: Export files that contain custom attributes are readable for CANdelaStudio.
Export Compare block: If an Application Enumeration is used indirectly by a Diagnostic Data Object, for example, as the type of a Record Element or array, the UUIDs of the enumeration entries are now exported. Note: PVCDI reference files must be newly exported for use in the Export Compare block.
Diagnostic import: PREEvision versions that support PVCDI 2.1.0 files will also import PVCDI 2.0.0 files.

3.5.9 Hardware architecture

ID 9082949058347771029
9082949058293571029
9082949058605981808

Resolution
When creating a Wiring Connector for a Header via the refactoring Create Missing Wiring Connectors, the Wiring Connector receives the same name as the associated Header. Additionally, when creating and assigning a Wiring Connector for a Splice via refactoring or drag and drop, the Wiring Connector receives the name from the Splice.
When creating a Wiring Connector for a Header via the refactoring Create Missing Wiring Connectors, the Wiring Connector is created with slots, cavities and contactings for the Wire Pins, if an applicable opposite Connector Type is set for the Connector Type of the Header. If a Wire Pin has an assigned wire, the relation between pin Contacting and wire is now set as well, if the relation can be clearly identified.
KBL import: During KBL import, a KBL.Node with an assigned KBL.Fixing_occurrence is imported into PREEvision as a Branch-Off with a relation to the corresponding Topology Type.

Version 10.20

PREEvision 10.18

ID 9082949058411432083
9082949058725391784

Resolution
KBL export: The export option Use coordinates based on Connector Locations now correctly exports the coordinates for each Connector Location.
The Attribute Definitions for installation instructions and processing instructions of Splices must be defined on the Wiring Connector. The corresponding Attribute Definitions set on Splices are omitted and are no longer exported to KBL.

3.5.10 Geometry
ID 9082949058718142083

Resolution
When creating missing Installation Locations and Connector Locations via the refactoring Create missing Installation and Connector Locations, the names are derived from the mapped artifacts according to naming attribute conventions. The name of the Installation Location is taken over from the name of the mapped component, the name of the Connector Location is taken over from the name of the mapped Wiring Connector. Additionally, Topology Inline Connectors receive their names from the mapped Wiring Harness Inline Connectors according to the naming attribute convention.

3.5.11 Product line engineering

ID 9082949058416563108 9082949058713001914 9082949058733882082
9082949058723102068 9082949058767971030
9082949058822491842

Resolution
The instance of a type referenced in an Asset as a core artifact is not copied after an Asset update if the instance of the type exists outside the Asset.
During Asset update, an inconsistent reuse of software types after a replace of an orphaned type has been fixed.
An Asset update does not add types to to-n-type-of relations in case the types leave the Asset during the update but remain in the model (due to other Assets). Now, the types of the upstream Asset win.
The type of an instance is no longer moved if the instance is moved from Asset internal to external after Asset update.
Context relations between asset-internal types and other core artifacts are not lost during Asset update if instances of these asset-internal types are children of the Asset, for example, because a custom attribute definition is in the core of an Asset and is used for a value describing the Asset.
A missing revoke of foreign Asset(s) has been resolved in case a to-n-type of end leaves an Asset during update.

Version 10.20

PREEvision 10.18

3.5.12 Metrics
ID 9082949058192932039
9082949058387331912, 8682711687064211912, 9082949058276842013
9082949058382690091
9082949058562062111, 9082949058688573056

Resolution
The functionality of the "suppressInfoView" Data Target Port of the Get Workspace metric block has been corrected. If "suppressInfoView" is set to true, no results are reported in the Information View.
The behavior of the Model Export metric block has been corrected. If the "exportActiveVariantOnly" port is set to true, all artifacts provided by the "exportElement" port and their child artifacts are considered for the export if they are part of the active variant.
The Table Selection List metric block no longer causes exceptions in the log file when a null input is set.
The result table of a Consistency Rule Group metric block can be exported via the CSV Export metric block.

3.5.13 Collaboration
ID 9082949058824231993
9082949058291802051, 9082949058260082051
9082949058689202105
9082949058654062044, 9082949058661701914 9082949058675662203

Resolution
The defragmentation of the model cache on the server no longer leads to scope loading errors.
An error in the file defragmentation has been resolved. Artifacts can be temporarily added to the scope again via the Scope Quickview.
Renaming configuration files no longer leads to an error during the model update.
A special model configuration is now correctly handled during the Asset update and can be committed.
Changing the package path of a metric source code no longer leads to errors when executing the metric in the API server.

3.5.14 Administration
ID 9082949058619382203
9082949058695861028

Resolution
STARTTLS can be configured as the protocol for mail server. In the deploy.properties, the parameter MailProtocol must be set to smtp. Using the JavaMail API, all required parameters for encryption must be set as JVM parameters starting with Dmail.smtp.*.
The checkout model has been corrected to prevent commits from being denied when installing Add-ins in certain situations.

Version 10.20

PREEvision 10.18

ID 9082949058703222011

Resolution
A global Change Profile Model that is referenced by Addins is no longer moved to a Generic Package when the Add-ins are delivered.

Version 10.20

PREEvision 10.18

3.6 Known issues

Known issues in PREEvision 10.18

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

ID 17938307791212069
8682711552649222003 8682711555165912106 8682711687572062012 8682711555191801873
8682711685521992014 8682711687181061868

Known issue
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.
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.
ReqIF export: For empty attributes, the string defined in the Text for empty Labels property is exported instead of and empty string. By default, this is "---". Workaround: In the Preferences, under PREEvision | General, remove all characters from the Text for empty Labels property.
Using the control-key to navigate in a formatted text which contains a placeholder or using shortcuts to cut or copy and paste a placeholder may lead to editors being opened in the background. Workaround: Close the opened editors and continue.
During reinitialization of the authority model an error message may be displayed reporting an unexpected error with the ramc.ser file. Workaround:
1. Delete the authority model.
2. Connect to the authority model.
3. Initialize the authority model.
For Application Curve Types and Application Cube Types, the Calibration Attributes property page is missing in the Property View. It will be restored in a future minor release.
The automatic integration of an Asset may be incomplete during use, reuse, or update of the Asset if related artifacts with abstraction or substitution links in a downstream Product Line are read-only. Workaround: Execute the automatic integration again.

Version 10.20

PREEvision 10.18

ID 9082947085110861914, 9082947085889122108
9082949058188121799
9082949058916421857

Known issue
Opening the VM Explorer or the VM Explorer without Customer Feature Model may lead to performance problems. This may be due to filter configurations which are set on specific explorer categories. Workaround: Customize the corresponding "VM Explorer" and "VM Explorer without Customer Feature Model" Add-ins, and remove the Explorer Filter Configurations set on the affected explorer categories.
If you define an AND combination of two prototype column filters where the content of one column is defined via a search query and the content of the other column is defined without using a search query, the filter result might be wrong. Workaround: If you filter combinations of prototype columns, make sure that all filtered prototype columns are based on search queries.
Due to an error in the compatibility check, service packs of minor releases, for example, 10.17 SP1, cannot be used for backup and restore. Workaround: Update to the next minor release without service pack, for example, 10.18.

Version 10.20

4 PREEvision 10.17

This chapter contains the following information:

4.1

Version numbers

4.2

Installation and compatibility information

4.3

New features in PREEvision 10.17

4.4

Configuration information

4.5

Fixed issues

Common

Diagrams

Tables

Requirements

AUTOSAR

Software architecture

Diagnostics

Communication

Hardware architecture

Product line engineering

Change and release management

Metrics

Collaboration

Administration

4.6

Known issues

PREEvision 10.17
84 85 87 90 91 91 91 92 92 93 94 95 95 95 96 96 96 97 97 98

Version 10.20

4.1 Version numbers

Version numbers

Application PREEvision client PREEvision license server PREEvision database server PREEvision application server

Documentation

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

PREEvision 10.17
Version number 10.17.0 3.0.2 10.17.0.03 10.17.0
Version number 10.17.0 10.17.0 10.17.0 10.17.0 10.17.0

Version 10.20

PREEvision 10.17

4.2 Installation and compatibility information
For detailed information about the installation of PREEvision 10.17 and the migration to PREEvision 10.17, refer to the PREEvision operating manual.
For detailed information about the hardware and software requirements of PREEvision 10.17, refer to the PREEvision system requirements.

System requirements

The following system requirement has been changed: The recommended version of Apache Tomcat has been changed to 9.0.98.

Secure SMTP (SMTPS)

SMTPS can now be configured as protocol for the automated e-mail notification for life cycle state changes. The protocol that is used is reported in the application server log file. You can configure SMPTS in the deploy.properties with the following parameters:
> MailProtocol
> mailing.Internal.Ssl.*
You can also configure SMPTS in the context file of the PREEvision server application (vCollab.xml).

Compatibility

Client version
10.5.0 10.6.0 10.7.0 10.8.0 10.9.0 10.10.0 10.11.0 10.12.0 10.13.0 10.14.0 10.15.0 10.16.0 10.17.0

Server version
10.5.0 10.6.0 10.7.0 10.8.0 10.9.0 10.10.0 10.11.0 10.12.0 10.13.0 10.14.0 10.15.0 10.16.0 10.17.0

Database server script version 10.5.1.41 10.6.0.02 10.7.0.02 10.8.0.02 10.9.0.03 10.10.0.03 10.11.0.03 10.12.0.02 10.13.0.02 10.14.0.05 10.15.0.02 10.16.0.04 10.17.0.03

Metamodel change ID 2022-10-05 2023-04-03 2023-06-01 2023-07-20 2023-09-18 2023-11-13 2024-01-19 2024-03-14 2024-05-06 2024-07-08 2024-08-29 2024-11-08 2025-01-07

Migration and update PREEvision 10.0 SP17 or later can be migrated to PREEvision 10.17.

Version 10.20

PREEvision 10.17
Migrating to PREEvision 10.17 is only possible from PREEvision 10.0 SP17 or later. All remote operations (backup and direct migration) available in the PREEvision 10.17 administration panel can only be performed on PREEvision 10.0 SP17 or later. Remote model preparation must be performed on PREEvision 10.0 SP18 or later. If you want to migrate a PREEvision 10.0 version before 10.0 SP17 or PREEvision 9.5, contact the Vector support.
For the migration to PREEvision 10.17, it is recommended to update PREEvision 10.0 to the latest version (service pack update), at least PREEvision 10.0 SP17, before creating a backup and starting the migration. An update of PREEvision 10.5 or one of its following minor releases, starting with version 10.6, to PREEvision 10.17 requires no migration and can be performed as minor release update. An update of PREEvision 10.5 to a following minor release, for example, PREEvision 10.17, 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 > 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".

Version 10.20

PREEvision 10.17

4.3 New features in PREEvision 10.17

Sequence diagram

PREEvision now offers sequence diagrams with full auto-layout of all created artifacts, and modeling support of interactions on different abstraction layers. The window lifter demo in the PREEvision demo model has been enhanced by examples of Interactions.

Automatic comparison of export files

AUTOSAR and PVCDI exports new files made by a new PREEvision version can be compared with reference files made by previous PREEvision version. This is meant to check if a new version of PREEvision affects your exports. Differences in the export files can be caused by changes in the meta model or model transformation of the new PREEvision version.
The Export Compare metric block searches for differences in export files with the same name. The results are provided in Excel files listing all new, deleted and changed elements. The metric framework supports automation with an automation server, for example, Jenkins.

Name and path of root Keeping the AUTOSAR references inside a PVCDI file in sync with the software structure

compositions in ECU inside the ECU extract allows an automatic integration of the DCM/DEM with the

extracts

application software in later tools, like DaVinci Configurator or DaVinci Team.

Version 10.20

PREEvision 10.17
You can now define the name of the root composition created for an ECU extract and adapt it to the name used for the AUTOSAR references in PVCDI to keep them in sync. The name can be defined via a new attribute of the System Information.

Instantiation of

The creation of a Hardware Device based on a hardware device type does no longer

hardware device types require a diagram. A Hardware Device based on a hardware device type can now be

in the model view

created within the Model View via a drag and drop action.

Hardware library explorer

A new Hardware Library Explorer for the electrologic and harness layers has been implemented. The explorer structures all hardware- and harness-related types and parts defined in the Library. By means of different categories and tables, the explorer offers a structured overview of all types and parts relevant for consistently modeling the hardware.
The Library Explorer can be opened on a Product Line or a Library.

Asset creation or refresh warning in case of external types of core artifacts

Used types are part of an artifact's version. External types violate the self-containment principle of Assets. External types of core artifacts or their children can lead to unwanted cross-product line dependencies or import packages.
The creation or refresh of Assets and check-in warns if the self-containment is violated due to external types.
Configurators can easily disable the check or use the check to enforce Asset quality.

Tables in diagrams:

The usability and performance have been increased when using tables in diagrams.

Performance and

usability improvements

Version 10.20

PREEvision 10.17

Tables in diagrams can be refreshed individually. Especially for large diagrams containing many tables, it is less time consuming to refresh individual tables instead of refreshing the entire diagram.
The reference lines between tables and corresponding artifacts can be hidden. This way, disturbing overlaps of the reference lines with the diagram content, and reference line crossings can be avoided to ensure a better readability of the diagram.

Extended filter management in tables

In the filter logic tree of the Define Filter dialog, you can now replace operators via the context menu or the respective shortcuts.
Via drag and drop, you can move column filters and operators with their entire substructure to a different position. A black horizontal line shows you the exact drop location.

If a filter is currently active in a table, the active filter is preselected, when you open the Define Filter dialog.

Search and replace in tables

The search and replace function has been further enhanced:
> As search values and as replace values, you can now also enter numbers.
> In formatted texts, you can replace a character string with a placeholder by inserting an artifact into the replace field via drag and drop.

Version 10.20

PREEvision 10.17

4.4 Configuration information

New metric blocks: Export compare

The Export Compare metric block searches for differences in export files with the same name. The results are provided in Excel files listing all new, deleted and changed elements. The metric framework supports automation with an automation server, for example, Jenkins.
Palette category: Configuration Test
Required inputs (Data Target Ports):
> "exportedFilesFolderPath" (data type: String): Path to the folder with the files to be compared.
> "referenceFilesFolderPath" (data type: String): Path to the folder with the files that serve as references for the comparison.
> "resultFolderPath" (data type: String): Path to the folder with the Excel file containing the comparison results.
Outputs (Data Source Ports):
> "result": Since the results are posted in the Excel files, the result port has no function for the Export Compare block.

Changed metric blocks: The Populate metric block is used to populate connected artifacts of a given start artifact

Populate

in a diagram.

The "routingStyle" input port (Data Target Port) now also supports the value "rectangular" in addition to "rectilinear" to define the line routing style for displayed connections.

Version 10.20

PREEvision 10.17

4.5 Fixed issues

Fixed issues in PREEvision 10.17

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

Further information

> Common > Diagrams > Tables > Requirements > AUTOSAR > Software architecture > Diagnostics > Communication > Hardware architecture > Product line engineering > Change and release management > Metrics > Collaboration > Administration

4.5.1 Common
ID 17938293798689312
9082947087339343042

Resolution
When editing/configuring the Customized Label or Customized Name Label in Diagram via the Label Configuration or the Object Configuration, the entered text can be saved and the corresponding dialog closed via the shortcut <Ctrl>+<Enter>.
External synchronization links for which no Channel ID is defined are properly displayed in the Property View.

4.5.2 Diagrams
ID 9082947087146443099 9082949058442532083
9082949058423032196

Resolution
The icons and texts for routing style split buttons in the toolbar of diagrams have been adjusted and unified.
The routing style "rectilinear" has been replaced by "rectangular" in the Routing preferences of diagrams. Additionally, the Populate metric block also accepts both, the value rectangular and rectilinear as possible values of the routingStyle input port.
The possibility has been added to assign an Activity of an UML Method to an Activity Execution Specification.

Version 10.20

PREEvision 10.17

4.5.3 Tables
ID 9082949058115432101, 9082949058234572105 9082947086104711897
9082947087361942105
9082947087356040123 9082949058145032023
8682711554740723126
9082949058192963042
9082947085911062101
9082949058615833082

Resolution
The performance of the search in formatted texts has been improved by downloading the formatted texts in one batch.
In case of large numbers of results, the Replace view displays only a part of the results. After you have replaced the displayed results via [Replace All], the next batch of results is automatically loaded in the Replace view.
If the Replace view displays attribute values of artifacts that are locked by another user, you can still use [Replace All] to replace attribute values of artifacts that are not locked.
The Replace view always displays an information if the table in which the search was performed contains collapsed table cells.
If you reopen the predefined filter of an active filter in the Define Filter dialog, the Predefined Filters drop-down list offers all entries that are available in the selected column.
In case of existing file attachments, the column for file attachments in the Test Specification Editor and the Requirement Text Editor now displays the corresponding icon correctly.
If an Artifact Picker is configured via Metric Artifact Picker or Meta Class Artifacts Picker, the Show all artifacts in Artifact Picker action is available if more than 500 artifacts are displayed.
When a portlet view which displays an editor (for example a table) is duplicated, the new portlet also displays the editor instead of an empty pane. The portlet view is reset to its initial state if the displayed artifact has been deleted.
The navigation button on a table column cell opens the registered default editors for the corresponding artifact.

4.5.4 Requirements
ID 9082947086108091790, 9082947086115112051
8682711555195363013

Resolution
A problem when pasting content from the Microsoft Windows clipboard into formatted texts has been resolved: sometimes, the last text copied or cut from a formatted text was pasted instead of the current content of the clipboard.
In the Requirement Text Editor, it is again possible to copy a Resource into a cell that is already filled using the shortcuts <Ctrl>+<C> and <Ctrl>+<V>.

Version 10.20

PREEvision 10.17

ID 9082949058355542105 9082949058216222101 9082949058219852105 8682711686179212044
9082947087393672105

Resolution
ReqIF export: Formatted texts containing hyperlinks with target properties are exported in a schema valid way.
ReqIF export: Unordered lists containing special formatting are exported to ReqIF in a schema valid way.
The handling of OLE objects has been improved to prevent deadlocks during the conversion of OLE objects.
An error occurred during report generation with a corrupt template. A specific error message has been implemented to inform the user about the current problem and how to solve it. Additionally, an information detail page refers to the corrupt template.
The scaling and offset in SVG images in report generated documents (PDF files) has been improved to avoid missing content.

4.5.5 AUTOSAR
ID 9082947085852652003
9082949058194312003 9082949058293622003 9082949058298332003
9082949058298372003 9082949058303652003 9082949058303662003
9082949058303702003

Resolution
The AUTOSAR consistency check "cac5398_EthernetEcuConnectorWithoutController" has been renamed and corrected. Redundant checks have been removed.
The AUTOSAR consistentcy check "AR_010703_ARC_430_PortDefinedArgument_without_ IDT" has been corrected and renamed.
The AUTOSAR consistency check "Constr1087_AssemblySwConnector" has been corrected and renamed.
The AUTOSAR consistency check "AR_010806f_PV_ModeSwitchReceiverComSpec Without_MDGE" has been deleted because of redundancy.
The AUTOSAR consistency check "aConstantSpecification_without_Value" has been deleted because of redundancy.
The AUTOSAR consistency check "aServerComSpec_without_Operation" has been deleted because of redundancy.
The AUTOSAR consistency check "aApplicationTypeImplementationTypeMapping_ without_ImplementationDataType" has been deleted because of redundancy.
The AUTOSAR consistency check "C3101_emptySRInterface" has been deleted because of redundancy.

Version 10.20

PREEvision 10.17

ID 9082949058310922003 9082949058265162003 9082949058293612003 9082949058347943013 9082947086046781914
9082949058234262005 9082947086101312108
9082949058221522051 9082949058261351807 9082949058238041992

Resolution
Multiple AUTOSAR consistency checks have been deleted because of redundancy.
Several consistency checks for the AUTOSAR constraint constr_1088 have been corrected and renamed.
Several consistency checks for the AUTOSAR constraint constr_1086 have been corrected and renamed.
The AUTOSAR consistency check "pc1003_SharedAxisWithoutAxisType" does not fail if the parent artifact of the xAxis is an Application Axis Type.
Implementation Function Pointers and Implementation Data Pointers with their target are now included in the ECU extract even if their target is used by other data types.
AUTOSAR export: Instance references used in COLLECTIONS are exported in the correct order.
AUTOSAR export: Default values for the attributes canBeInvokedConcurrently and supportsMultipleInstantiation are exported up to AUTOSAR version 4.4.
A Role Based Data Assignment of an Nv Block Needs is now properly exported to the ECU extract.
The AUTOSAR import can handle incomplete SenderRecRecordElementMappings.
The structure and behavior of Virtual Packages for AUTOSAR exports has been clarified in the manual (chapter "General AUTOSAR concepts").

4.5.6 Software architecture

ID 9082947086096592106
9082947086114692106 9082949058331523042

Resolution
Drop down widgets in cells configured for value handling close automatically if an entry is selected by keyboard or mouse.
The creation of literals for enumerations has been simplified.
The value handling now merges new values of enumerations properly with existing values.

Version 10.20

PREEvision 10.17

4.5.7 Diagnostics
ID 9082949058388732005
9082949058634721875

Resolution
The attributes Automatic end and Cycle status storage for Diagnostic Operation Cycles have been removed from the Property View as they are no longer supported in AUTOSAR.
In the Diagnostic Realization Explorer in the SW Type Preparation category, a Sender Port Type with a Parameter Interface for a Diagnostic Data Identifier can be created in the DID table.

4.5.8 Communication
ID 9082949058412891029
9082947087381891911

Resolution
In the Property View of a Container IPDU, on the PDU Attributes property page, the Collection Semantics attribute has been added.
The frame-PDU synthesis now checks for recursions in the modeling of PDU Transmissions which prevents stack overflow errors.

4.5.9 Hardware architecture

ID 9082947085852672083
9082949058234633104 9082949058359882046 8682711687672632062

Resolution
The refactorings of the hardware diagrams to corresponding system diagrams provide the option to be created Without System Master. The option is active by default. The following diagrams are affected:
> Network Diagram
> Electric Circuit Diagram
> Wiring Diagram
> Geometry Diagram
When executing a Ground Spot Optimization refactoring and canceling the subsequent Lock dialog, all changes applied by the refactoring are correctly reverted.
Creating an auto-layout diagram for a Wiring Diagram has caused an error in case multiple parallel wires are connected between the same Wire Pin and the same Splice. The creation algorithm has been enhanced to correctly handle parallel wires during the creation of autolayout diagrams.
In the Assign Pins to Cavities table, improvements and enhancements for drag and drop actions for several table columns have been implemented, such as improvements of the descriptions and used icons for the individual drag

Version 10.20

PREEvision 10.17

Resolution

and drop actions. Additionally, the default merge drag and drop action has been removed.

4.5.10 Product line engineering

ID 9082949058303002112, 9082949058403492052 9082949058501832113
9082949058535542012
17938307714742040
9082949058347980091
9082947087293581995

Resolution
The issue that has caused an unwanted check-out of a revoked Asset during an Asset update has been resolved.
Changing the composite relation of recursive children of core artifacts does no longer result in out-of-sync problems during Asset updates.
Asset updates correctly reset attributes of artifacts from "-not set-" to their initial value if the initial value is set in the target version.
When reusing and automatically integrating several Assets via drag and drop, a progress information is provided.
The unnecessary setting of change markers that have caused full locks during a version replace or restore has been resolved.
The error feedback has been improved in case no target or multiple targets are given at the "target" input port of the Use Asset metric block.

4.5.11 Change and release management

ID 9082949058585102112

Resolution
When using Change Profiles, the [Commit] button in the Commit Dataset dialog is disabled if the model contains validation errors (for example, commit rejecting online checks).

4.5.12 Metrics
ID 9082949058365030124
9082947086115262023

Resolution
Embedded Metric Executors used in table actions revert the operation and any model changes previously made within that metric execution if the result state or sub-state in a metric block is set to "CANCEL".
When executing the Check-In metric block, check-in validation errors are always reported in the Information View, even if the metric executor suppresses check-in dialogs.

Version 10.20

PREEvision 10.17

4.5.13 Collaboration
ID 9082949058276442034
9082949058529123139 9082949058203202108 9082947087376092108 9082949058127702101

Resolution
The Change history displays the full history of an artifact, even if a Localization or Localization Package was previously deleted. If the Localization and the Localization Package are recreated, the history continues accordingly.
The Extended Lockstatus Information, which can be displayed if an artifact is locked by another user, has an additional column with the user's Mobile Phone Number.
The actions to show reuses that are available on the Version History property page, now include the selected version of the artifact in the Search result view, even if that version does not have any reuses.
If you replace or restore an artifact version via the Version History, the Progress Information now correctly states if a replace or restore process is in progress.
Canceling a check-in in certain use cases is now possible without the need of restarting PREEvision after the cancel.

4.5.14 Administration
ID 9082949058245671028
9082949058161721995

Resolution
Fixed an issue that could cause metrics to recompile during Add-in installation.
Add-ins now propagate the Configuration Test Suites and Test Metric Executors of Configuration Test Suites topdown.

Version 10.20

PREEvision 10.17

4.6 Known issues

Known issues in PREEvision 10.17

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

ID 17938307791212069
8682711552649222003 8682711555165912106 8682711555133422025 8682711686247202025
8682711687572062012

Known issue
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.
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.
ReqIF export: For empty attributes, the string defined in the Text for empty Labels property is exported instead of and empty string. By default, this is "---". Workaround: In the Preferences, under PREEvision | General, remove all characters from the Text for empty Labels property.
<Ctrl> + click on a preview image in a formatted text may not open the linked File Attachment. Workaround: Use the context menu on the preview image or double click on the File Attachment artifact in the Model View to open the file attachment.
When inserting a diagram placeholder based on templates, an error message is reported that the used template is incomplete. Workaround:
1. Navigate to the selected template under Administration | Configuration File Container | Report Template Package and select the affected template file.
2. Open the location of the file in the Windows Explorer and delete the file.
3. Update from the server to force a reload of the file.
Using the control-key to navigate in a formatted text which contains a placeholder or using shortcuts to cut or copy and paste a placeholder may lead to editors being opened in the background. Workaround: Close the opened editors and continue.

Version 10.20

PREEvision 10.17

ID 8682711555191801873
8682711685521992014 8682711687181061868
9082947085110861914, 9082947085889122108
9082949058188121799

Known issue
During reinitialization of the authority model an error message may be displayed reporting an unexpected error with the ramc.ser file. Workaround:
1. Delete the authority model.
2. Connect to the authority model.
3. Initialize the authority model.
For Application Curve Types and Application Cube Types, the Calibration Attributes property page is missing in the Property View. It will be restored in a future minor release.
The automatic integration of an Asset may be incomplete during use, reuse, or update of the Asset if related artifacts with abstraction or substitution links in a downstream Product Line are read-only. Workaround: Execute the automatic integration again.
Opening the VM Explorer or the VM Explorer without Customer Feature Model may lead to performance problems. This may be due to filter configurations which are set on specific explorer categories. Workaround: Customize the corresponding "VM Explorer" and "VM Explorer without Customer Feature Model" Add-ins, and remove the Explorer Filter Configurations set on the affected explorer categories.
If you define an AND combination of two prototype column filters where the content of one column is defined via a search query and the content of the other column is defined without using a search query, the filter result might be wrong. Workaround: If you filter combinations of prototype columns, make sure that all filtered prototype columns are based on search queries.

Version 10.20

5 PREEvision 10.16

This chapter contains the following information:

5.1

Version numbers

5.2

Installation and compatibility information

5.3

New features in PREEvision 10.16

5.4

Changes

5.5

Configuration information

5.6

Fixed issues

Common

Diagrams

Tables

Requirements

Logical function architecture

AUTOSAR

Diagnostics

Communication

Hardware architecture

Product line engineering

Metrics

Collaboration

Administration

Server API

5.7

Known issues

PREEvision 10.16
101 102 104 109 110 114 114 114 114 115 115 115 116 117 117 118 118 118 119 120 121

Version 10.20

100

5.1 Version numbers

Version numbers

Application PREEvision client PREEvision license server PREEvision database server PREEvision application server

Documentation

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

PREEvision 10.16
Version number 10.16.0 3.0.2 10.16.0.04 10.16.0
Version number 10.16.0 10.16.0 10.16.0 10.16.0 10.16.0

Version 10.20

101

PREEvision 10.16

5.2 Installation and compatibility information
For detailed information about the installation of PREEvision 10.16 and the migration to PREEvision 10.16, refer to the PREEvision operating manual.
For detailed information about the hardware and software requirements of PREEvision 10.16, refer to the PREEvision system requirements.

System requirements

The following system requirements have been changed:
It is recommended to use VisualSVN Server version 5.4.1 for the PREEvision subversion server.

License server

If the standalone license server is connected via a proxy, the parameter Djava.rmi.server.hostname=<proxy server> must be set in the Virtual Machine Parameters of the license server.

Compatibility

Client version
10.5.0 10.6.0 10.7.0 10.8.0 10.9.0 10.10.0 10.11.0 10.12.0 10.13.0 10.14.0 10.15.0 10.16.0

Server version
10.5.0 10.6.0 10.7.0 10.8.0 10.9.0 10.10.0 10.11.0 10.12.0 10.13.0 10.14.0 10.15.0 10.16.0

Database server script version 10.5.1.41 10.6.0.02 10.7.0.02 10.8.0.02 10.9.0.03 10.10.0.03 10.11.0.03 10.12.0.02 10.13.0.02 10.14.0.05 10.15.0.02 10.16.0.04

Metamodel change ID 2022-10-05 2023-04-03 2023-06-01 2023-07-20 2023-09-18 2023-11-13 2024-01-19 2024-03-14 2024-05-06 2024-07-08 2024-08-29 2024-11-08

Migration and update

PREEvision 10.0 SP17 or later can be migrated to PREEvision 10.16.
Migrating to PREEvision 10.16 is only possible from PREEvision 10.0 SP17 or later. All remote operations (backup and direct migration) available in the PREEvision 10.16 administration panel can only be performed on PREEvision 10.0 SP17 or later. Remote model preparation must be performed on PREEvision 10.0 SP18 or later. If you want to migrate a PREEvision 10.0 version before 10.0 SP17 or PREEvision 9.5, contact the Vector support.

Version 10.20

102

PREEvision 10.16
For the migration to PREEvision 10.16, it is recommended to update PREEvision 10.0 to the latest version (service pack update), at least PREEvision 10.0 SP17, before creating a backup and starting the migration. An update of PREEvision 10.5 or one of its following minor releases, starting with version 10.6, to PREEvision 10.16 requires no migration and can be performed as minor release update. An update of PREEvision 10.5 to a following minor release, for example, PREEvision 10.16, 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 > 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".

Version 10.20

103

PREEvision 10.16

5.3 New features in PREEvision 10.16

Usability and performance improvements

Spell checking in automated use cases have been disabled with PREEvision 10.16 resulting in an improved performance, for example, when exporting table content to Excel. The technical character styles starting with "AQ" have been removed from the Styles and Formatting view to improve clarity and to avoid using of a formatting intended for technical purposes. When needed, these styles are automatically assigned and receive special treatment in subsequent processes.

Support of persistency interfaces

PREEvision 10.16 supports persistency interfaces used in AUTOSAR Adaptive to access persistent data by application software. Persistency File Storage Interfaces and Persistency Key Value Storage Interfaces can now be created in the Model View including Persistency File Elements and Persistency Data Elements.

Export of variants vCANdrive demo

Additionally, Persistency Data Required Com Specs can be modelled under Adaptive port types. Also, bidirectional Adaptive Provided Required Port Types are now available to enable full AUTOSAR compliant modeling of persistency interfaces.
The EEA export of active variants has been improved. Only artifacts that are selected and that are part of the active variant will be exported. With an export profile, for example, the implicit selection can be extended.
To showcase the Vector software factory for the development of software-defined vehicles, the vCANdrive demo was presented during the SDV Symposium Europe 2024.

The modeling data of the vCANdrive demo is part of the demo model delivered with PREEvision 10.16. This model serves as a basis for Vector's evaluation and testing platform and covers almost all layers of the design process.

Version 10.20

104

PREEvision 10.16

Handling of write protection for replace and restore

Historical versions can be restored in place including context attributes, such as the ImEx-ID. A write protection of artifacts in the historical version could prevent a restore. A restore could fail due to write protection of child artifacts in the head.
A replace or restore is now carried out successfully regardless of write protection of artifacts in the historical version or modified artifacts in the head. Restoring a historical version in place is possible if it includes artifacts with enabled write protection.

Extended information about lock owner

If an artifact is locked by another user, you can now display extended information about the user in the Extended Lockstatus Information popup and the Current users dialog. New contact options via mail and messenger allow you to directly contact the user who has locked the artifact.

Administration panel: The administration panel provides a new page for administering backup files. Backup files

On the Backup Files page, you can: > display all backup files that are available on the application server. > download backup files. > delete backup files. > upload backup files to the application server. > copy and share the download link of backup files. Additionally, if a backup job is completed, the backup file can be downloaded from the Job Details.

Version 10.20

105

PREEvision 10.16

Improved client startup with large updates

During client startup, large model updates on the server are now directly detected and handled without displaying a dialog. If a large update is detected on the server, the client cache is automatically cleared, and the model is instantly reloaded from the server. This reduces unnecessary waiting times since the model is not initially loaded from the client cache file.

PREEvision server API extension: tracked artifact set

The new tracked artifact set part of the PREEvision server API allows users to configure different sets of artifacts to monitor for changes. It is roughly based on the Tracked Resource Set (TRS) specified by the Open Services for Lifecycle Collaboration (OSLC).
The API extension allows monitoring model parts for changes via REST, for example, allowing a third-party tool to react to model changes.
The tracked artifact set API extension provides the following options:
> Configuring sets of artifacts to track in the form of individual artifacts or artifacts of specific meta classes in model subtrees.
> Retrieving all individual artifacts that are currently tracked by a set.
> Retrieving the changelog of a set, which chronologically records the changes, additions, and deletions of artifacts in the set.

Extended filter management in tables

Via the Define Filter dialog, you can create and edit complex table filters combining several column filters with the operators AND, OR, XOR, and NOT. The filter logic is displayed in a graphical and a textual overview.

Version 10.20

106

PREEvision 10.16

Version 10.20

107

PREEvision 10.16

Search and replace for formatted text in tables

In tables, you can now search and replace values in formatted text. As search and replace values you can enter character strings, blanks, and special characters, and it is also possible to search for text in placeholders. To show the context, the Search view and the Replace view also display text before and after the searched value, and the searched value itself is highlighted.

Version 10.20

108

PREEvision 10.16

5.4 Changes

Undo lock action no longer available

The Undo Lock action, which allowed you to release locks of artifacts that had not been modified, is no longer available. To release locks and discard changes, you can still use the Undo all own locks action.

New demo model content

The "Systems Engineering" Product Line Package in the PREEvision demo model has been enhanced with the "RFLP Concepts: Requirement, Functional, Logical and Physical" and the "SE Example: Crash Detection System" Product Lines. > "RFLP Concepts: Requirement, Functional, Logical and Physical"
> Generic concepts to support RFLP > "SE Example: Crash Detection System"
> Stakeholder Requirements > Feature model > Use Case Diagram > System Requirements > Activity Diagram > Logical System Architecture > Network Topology and Component Diagram > System/Component Matrix > SW Architecture > Class Diagram > State Machine > System Test Specification

Version 10.20

109

PREEvision 10.16

5.5 Configuration information

Table filters: Migration of tables

The format of table filters has been changed. All custom tables and table templates must be migrated to be compatible with the new filter format. Table templates that are part of the product configuration are updated through updating Add-ins.
During the migration, the following steps are processed:
> Saved filters in the old format are migrated.
> Relations are set between the column filter artifact and the filtered column.
> Relations are set between the column in the table instance and its associated column in the table template.
During the migration, the following restrictions apply:
> Tables are only migrated in the current model version. Historic model versions are not migrated.
> Checked-in tables are not migrated.
> If a table is locked, the migration is cancelled and rolled back completely. Therefore, make sure to have exclusive access to the model and all users have released their locks.
> Opened tables are not migrated correctly. Therefore, close all tables before starting the migration.
> If a table template is migrated, all its associated table instances and table proxies are migrated as well.
> If a table instance or a table proxy is migrated, its associated table template is not migrated.

The following procedure is recommended to migrate all custom table templates and their associated table instances and proxies:
> Precondition: The following initialization flag is set in the PREEvision.ini: DshowConfiguration=true
> Precondition: The complete E/E model is loaded and in the active scope.
> Precondition: You have exclusive access to the model. All users have released their locks in the model.
> Precondition: All tables are closed.
> Precondition: Add-ins have been installed/updated to update the table templates of the product configuration.
1. In the Model View, under Administration |Table Editors Configuration, select the Table Editor Packages that contain custom table templates.
2. Open the context menu and select Metrics | Migration Support | Migration 10.16 | Migrate Tables for Filters.

All table templates and their associated table instances and table proxies are migrated to be compatible with the new filter format.
To migrate all tables that are not associated to a table template: 1. In the Model View, either select the artifacts/packages that contain tables or, to
ensure all tables are migrated, select the Repository Root. 2. Open the context menu and select Metrics | Migration Support | Migration 10.16 |
Migrate Tables for Filters.

Version 10.20

110

PREEvision 10.16

All tables are migrated to be compatible with the new filter format.

During the Migrate Tables for Filters action, the Information View lists all tables and table templates that are processed during migration. Depending on whether the migration was successful or not, the following categories are reported in the Information View:
> "Migration successful": Lists tables that have been completely migrated to be compatible with the new filter format.
> "Migration failed": Lists tables that could not be migrated at all, for example, because they are checked in or locked by another user.
> "Filter migration failed": Lists tables and those filters that could not be migrated, either because the filter could not be migrated or because the relation to the filtered column could not be set.
> "Template column not assigned to instance column": Lists table templates and templates columns that could not be associated to a column in the table instance.

Possible reasons and solutions for tables with "Migration failed":

Reason The table is checked in.

Solution Check-out the table and migrate it again.

Possible reasons and solutions for tables with "Filter migration failed":

Reason Columns are hidden. Columns have been renamed or deleted.
Columns are neither hidden nor available in the table template.

Solution
Show all columns and migrated the table again.
Synchronize the table with its table template (action Update Table Instance Keep Local Filters) and migrate the table again.
Delete the filter and create it anew.

Possible reasons and solutions for tables with "Template column not assigned to instance column":

Reason Columns in the table instance have been renamed or deleted.
Columns in the table template are not uniquely named.

Solution
On the Settings property page of the instance column, manually assign the Associated Template Column. or Synchronize the table instance with its table template (action Update Table Instance Keep Local Filters or Update Table Instance Reset Local Filters).
1. In the table template, define a unique name for each column.
2. Update all table instances of the table template.
3. Migrate the table instances again.

Version 10.20

111

PREEvision 10.16

The migration is implemented via metric. The preconfigured metric is installed via the Add-in "Migrate Table for Filters" and can be found under:
"Administration" | "Metrics" | "Product" | "L270_UI_Concepts" | "279_Table Framework" | "Table Filter Configuration Format Head Migration"
In the Metric Diagram palette under Tables, the new Migrate Tables for Filters metric block is available to individually configure the migration of tables.

If a table is not migrated, the table can still be opened. The table can also be filtered in the new filter format and filters can be saved. Restrictions for not migrated tables: > Old filters are not listed. > The Create Table Instance action cannot be executed. > The Update Table Instance action cannot be executed. > An error dialog is displayed if old filters exist in the table.

Table filters: Multiple paths in table configuration

"Multiple path" in the table configuration means that multiple Data Providing Table Columns depend on the same source Data Providing Table Column. The Data Providing Table Columns with multiple paths cannot be used for complex filtering in the Define Filter dialog since the filter result may be misleading. Data Providing Table Columns with multiple paths can still be used for filtering via the table column header. However, the filter result may be misleading, like in previous PREEvision releases.
Direct Attribute Columns can always be used for filtering.

Therefore, it is strongly recommended that you check your custom tables and table templates for multiple paths and redesign your table configuration.
To check your table configurations for multiple paths:
> Precondition: The following initialization flags are set in the PREEvision.ini: DshowConfiguration=true DcheckTBEContracts=true
> Precondition: Add-ins have been installed/updated to update the table templates of the product configuration.
In the menu bar, select Administration | Check Table Configurations (in Scope).
All tables in the active scope are checked for multiple paths. The Information View lists tables for which multiple paths have been detected.
Alternatively: If you open a table that contains multiple paths, the Information View reports a warning.

The Define Filter dialog also indicates if a table contains columns that cannot be selected for filtering.

Version 10.20

112

PREEvision 10.16
To redesign affected table configurations and resolve multiple paths, the following solutions are available:
> Redesign table configuration: If possible, redesign your table configuration and configure all columns with a 1:1 relation between the input/output.
> Option All Values in Same Cell: If this option is activated on a Data Providing Table Column, all values are listed in the same table cell separated by a semi-colon. Activate the All Values in Same Cell option on the General property page of all dependent Data Providing Table Columns. Then the columns are offered for filtering in the Define Filter dialog.
> Option Use Only Single Result for Filtering on all Dependent Columns: If you make sure that all dependent Data Providing Table Columns only deliver one value, you can use this option. For example, if the dependent Data Providing Table Columns display all values in the same cell. Activate the Use Only Single Result for Filtering on all Dependent Columns option on the General property page of the source Data Providing Table Column. All dependent Data Providing Table Columns are then offered for filtering in the Define Filter dialog.
> Use a combined table: You may use a Combined Table Based Editor in which the source Data Providing Table Column and one dependent Data Providing Table Column are displayed in one table of the Combined Table Based Editor and the other dependent Data Providing Table Column is displayed in another table of the Combined Table Based Editor.

Version 10.20

113

PREEvision 10.16

5.6 Fixed issues

Fixed issues in PREEvision 10.16

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

Further information

> Common > Diagrams > Tables > Requirements > Logical function architecture > AUTOSAR > Diagnostics > Communication > Hardware architecture > Product line engineering > Metrics > Collaboration > Administration > Server API

5.6.1 Common
ID 8682711554193192051, 9082947087133851783
9082947086003442048

Resolution
If the details table of the Information View has been sorted by columns, the initial sort order can now be restored. When the sort order is changed, the expansion state does not change.
Custom attributes: Values for custom attributes can be reset to the default value if a default value is provided in the attribute definition. The property editor refreshes and displays the current value.

5.6.2 Diagrams
ID 9082947087358672101

Resolution
Object configurations with Query Rule constraints are properly applied to the master diagram of Legends and to the Legend displayed in diagrams that use the corresponding Diagram Configuration.

5.6.3 Tables
ID 8682711687091882001

Resolution
If several artifacts are displayed in a table cell, the tooltip for the table cell now displays all artifacts.

Version 10.20

114

PREEvision 10.16

ID 8682711687179133082
9082947086141902107 9082949058115432101

Resolution
If you display the table pop-up by moving the mouse on a table cell with links, the focus is set on the table. If you select an artifact in the table pop-up, the selection is propagated to the Model View.
Opening the filter drop-down list on column headers of tables with many rows is faster now.
The performance of the search in formatted texts has been improved by downloading the formatted texts in one batch.

5.6.4 Requirements
ID 9082947087146442101
9082949058107302105
9082947086108091790, 17938299155002108
9082949058129022105

Resolution
ReqIF agreement export: During export, placeholders contained in Attribute Definitions of type Application Text Type (formatted text) are exported properly.
The handling of links with invalid file paths in formatted texts has been improved so this will no longer disrupt a ReqIF export.
A problem when pasting content from the Microsoft Windows clipboard into formatted texts has been resolved: sometimes, the last text copied or cut from a formatted text was pasted instead of the current content of the clipboard.
The problem of invalid characters in links has been resolved, an Excel export is now possible.

5.6.5 Logical function architecture

ID 9082947085560841807
9082947086107862106

Resolution
When moving logical ports from one logical block (for example a Logical Function) to another logical block, they are now automatically removed from the origin block in all opened and non-locked Logical Architecture (System) Diagrams.
The issue that a table displayed in a Logical Architecture Diagram could not be rendered, and which then resulted in an incomplete diagram export as image, has been resolved.

5.6.6 AUTOSAR
ID 9082947085954611003

Resolution
AUTOSAR export: The ARXML file header contains the correct PREEvision version.

Version 10.20

115

PREEvision 10.16

ID 9082947086174741867
9082947086366032005
9082947085181792052 9082947087310083042 9082947087417842003 9082949058118441045
9082947087418891024

Resolution
If an AUTOSAR file to be exported contains COLLECTIONS of the category RELATION, it does now contain the full instance reference including SWCOMPONENT-PROTOTYPEs and ROOT-SWCOMPOSITION-PROTOTYPE.
If an AUTOSAR file to be imported contains COLLECTIONS of the category RELATION, the contained instance references are properly considered for the import even in cases of multi-instantiations of software compositions.
AUTOSAR export: VLANs are exported correctly even if they are linked to a Virtual Package, which is not necessary.
The consistency check "AR_010104_PV_SharedAxisWithoutAxisType" correctly returns only X-Axis artifacts with the Axis Category set to "Common".
The consistency checks in the cluster AUTOSAR Software Design now evaluates the same artifacts as the export considers.
AUTOSAR system description: A software architecture selected for export that contains elements belonging to the AUTOSAR Adaptive platform might lead to an erroneous export of the system description. To export only AUTOSAR Classic relevant artifacts, an active variant can be used to define a valid export scope.
AUTOSAR import with replace: Import with replace can be executed for root ports with the same port type.

5.6.7 Diagnostics
ID 9082947086046770063 8682711684967902005 9082949058146862005 9082947085805991875

Resolution
Diagnostic Event Info Needs can be created from context menu.
Diagnostic export: The attribute XMI:UUID will not be written into PVCDI files anymore.
Diagnostic export: The PVCDI Migrator delivered with PREEvision has been updated to version 1.0.2.
Diagnostic export: The handling of Multi Value Attribute Definitions during Diagnostic Exchange Export for CANdelaStudio has been improved. The export can be executed but the Multi Value Attribute Definitions will not be included in the export.

Version 10.20

116

PREEvision 10.16

5.6.8 Communication
ID 9082947086170391825
9082947087358721032

Resolution
ECU communication extract: LIN Schedules are exported correctly.
DBC export: If a frame that has multiple senders, the alphabetically first sender will be considered for export.

5.6.9 Hardware architecture

ID 9082947087417942083
9082947087380242112
9082947087342771027 9082949058119571874 9082947086020632083
9082947086019122083

Resolution
For ground spot optimization some improvements have been implemented with respect to the Wiring Harness target package. The drop-down list for the selection of the target Wiring Harness no longer displays a Wiring Harness which is located in the Administration. If a workspace is set on a Wiring Harness, this workspace is preselected when opening the Ground Spot Optimization dialog.
When performing the ground spot optimization on pins with existing Ground Connections, affected Wiring Harness Inline Connectors are not deleted. Only if all contained Schematic Pins would be deleted, the Wiring Harness Inline Connector is deleted as well. Furthermore, selected invalid solutions in the Ground Spot Optimization dialog cannot be executed anymore.
Contents provided by a Query Rule Group or metric in a Title Block Diagram is displayed in the corresponding Title Block of an auto-layout diagram when opening the diagram. No refresh of the diagram is necessary.
Providing contents by a new Query Rule Group or metric in an existing Title Block Diagram which is displayed in the corresponding Title Block of an auto-layout diagram, does no longer lead to a client crash.
When assigning a Plug-in Location to a Hardware Device, an information is reported in the Information View in case one or more pins of the Hardware Device could not be assigned to the cavities of the Plug-in Location. Additionally, the Assign Pins to Contactings table is opened, where the pins can be assigned manually.
When working with Plug-in Locations, the Assign Pins to Contactings table is opened in case the pins of the Hardware Device could not be matched to the cavities of the Plug-in Location. Two actions are available to assign a Hardware Device pin to a Contacting of a Plug-in Location Cavity via the table. The first action assigns the Hardware Device pin and replaces the existing Hardware Device pin. The second action additionally assigns the Hardware Device pin.

Version 10.20

117

PREEvision 10.16

5.6.10 Product line engineering

ID 9082947087379822108 9082947086068432024 9082949058112752012
9082947087373432108 9082947086183262012
9082949058230212102

Resolution
The problem that too many locks have been allocated during a restore / replace operation has been resolved.
Running metric blocks for updating Assets can be aborted to reduce the waiting time after cancelling the operation.
A replace or restore with selected version could have failed due to the initialization of Life Cycles in case the Life Cycle was introduced after the version was created. Life Cycles are not initialized anymore for checked-in historical versions.
The commit performance for restored Assets has been significantly improved.
Restoring a version may include checked-out artifacts. If a restore would have created a reuse the restore operation was prevented. Now, instead of preventing the restore, a warning is displayed. The next commit runs all necessary checks to prevent inconsistent reuses.
With the Update Asset metric block, an artifact that has its own non-versionable child artifact referenced as type can be replaced successfully again, for example, Title Block.

5.6.11 Metrics
ID 9082947085995372034 8682711687064211912 9082947087334482102 9082947087424441995

Resolution
An error during highlight calculation in Metric Diagrams which occurred after a model update has been resolved.
Model Export block: Only artifacts which are selected and are part of the active variant are exported.
The error handling for the Label to String Converter block has been improved.
Editors opened by metrics open in the expected area of the Perspective.

5.6.12 Collaboration
ID 8682711687176861856
9082947087330042034, 9082947087386452101

Resolution
Sending an e-mail during a life cycle transition properly works if the SendMail action is triggered in a Delegate Calculation metric block.
The Undo all own locks action is only displayed in the context menu, if own locks are active.

Version 10.20

118

PREEvision 10.16

ID 8682711685290971877
9082947086156333082 9082947087149211030 9082947085489302017 8682711684953952104 9082947085944073089, 9082947085984471806

Resolution
If an artifact is locked by another user, you can now display extended information about the user in the Extended Lockstatus Information popup and the Current users dialog. New contact options allow you to directly contact the user who has locked the artifact.
The action Restore Selected Version in the Version History can now also be executed if a context freezing point is set on the Product Line.
A commit error in the context of a fixed localization of complex external types during a Replace With Selected Version has been resolved.
The issue concerning erroneously detected activated/ deactivated partial model support during client start has been resolved.
The performance has been improved in case of large updates during the startup of PREEvision, and no more blocking message dialogs are displayed.
Importing artifacts from an EEA file with new UUIDs is now possible even if the EEA file contains artifacts with different branch names.

5.6.13 Administration
ID 9082947086100172068 9082947087137001028 9082947086103911028
9082947086164131995
9082947087304192011

Resolution
Check-in of Demo Add-ins or Test Add-ins that contain propagated artifacts is working again.
An error message is now displayed if an Add-in installation fails due to a missing Localization Package in the target model.
Corrected handling of Add-in installation of localized attributes: Installing a localized attribute overwrites the string values of the attribute in the target model. Unset values of the installed attribute are also reset in the target model.
Add-in propagation now includes the following prioritized perspective elements of Perspective Configurations: Reports, Context Menu Metric Executors, Collaboration Metric Executors, Consistency Rule Groups, Primary Editors, and Quick Search Extensions.
Non-relevant findings regarding change and default markers in reuse recovery validation no longer cause an Add-in installation to fail.

Version 10.20

119

PREEvision 10.16

5.6.14 Server API
ID 9082947087372862203 9082947087372872203
9082947087372912203
9082947087372982203 9082947087373052203 9082947087394332061

Resolution
Deleting a non-existent tracked artifact set configuration now returns HTTP status 404.
The REST call to create tracked artifact set configurations has been changed to PUT /tas/ config/<identifier>.
The REST call for creating and updating tracked artifact set content has been unified: POST is now used in both cases.
Correct endpoint is now used when configuring tracked artifact sets.
Added restrictions on valid configuration identifiers for tracked artifact sets.
The tracked artifact set configuration now has a description field for adding additional information.

Version 10.20

120

PREEvision 10.16

5.7 Known issues

Known issues in PREEvision 10.16

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

ID 17938307791212069
8682711552649222003 8682711555165912106 8682711555133422025 8682711686247202025
8682711686179212044

Known issue
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.
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.
ReqIF export: For empty attributes, the string defined in the Text for empty Labels property is exported instead of and empty string. By default, this is "---". Workaround: In the Preferences, under PREEvision | General, remove all characters from the Text for empty Labels property.
<Ctrl> + click on a preview image in a formatted text may not open the linked File Attachment. Workaround: Use the context menu on the preview image or double click on the File Attachment artifact in the Model View to open the file attachment.
When inserting a diagram placeholder based on templates, an error message is reported that the used template is incomplete. Workaround:
1. Navigate to the selected template under Administration | Configuration File Container | Report Template Package and select the affected template file.
2. Open the location of the file in the Windows Explorer and delete the file.
3. Update from the server to force a reload of the file.
When generating a report for a diagram as PDF, an error message is reported that the report generation was not able to write any data in the Temp directory and is aborted. Workaround:
1. Navigate to the report under Administration | Report Model and select the report file.

Version 10.20

121

PREEvision 10.16

ID 8682711687572062012 8682711555191801873
8682711685521992014 8682711687181061868 9082947085110861914, 9082947085889122108
9082949058145032023
9082949058188121799

Known issue
2. Open the location of the file in the Windows Explorer and delete the file.
3. Update from the server to force a reload of the file.
Using the control-key to navigate in a formatted text which contains a placeholder or using shortcuts to cut or copy and paste a placeholder may lead to editors being opened in the background. Workaround: Close the opened editors and continue.
During reinitialization of the authority model an error message may be displayed reporting an unexpected error with the ramc.ser file. Workaround:
1. Delete the authority model.
2. Connect to the authority model.
3. Initialize the authority model.
For Application Curve Types and Application Cube Types, the Calibration Attributes property page is missing in the Property View. It will be restored in a future minor release.
The automatic integration of an Asset may be incomplete during use, reuse, or update of the Asset if related artifacts with abstraction or substitution links in a downstream Product Line are read-only. Workaround: Execute the automatic integration again.
Opening the VM Explorer or the VM Explorer without Customer Feature Model may lead to performance problems. This may be due to filter configurations which are set on specific explorer categories. Workaround: Customize the corresponding "VM Explorer" and "VM Explorer without Customer Feature Model" Add-ins, and remove the Explorer Filter Configurations set on the affected explorer categories.
If you reopen the predefined filter of an active filter in the Define Filter dialog, the Predefined Filters drop-down list offers only those entries that are currently shown in the filtered table. Workaround: Deactivate the filter and open the filter definition in the Define Filter dialog again.
If you define an AND combination of two prototype column filters where the content of one column is defined via a search query and the content of the other column is defined without using a search query, the filter result might be wrong. Workaround: If you filter combinations of prototype columns, make sure that all filtered prototype columns are based on search queries.

Version 10.20

122

6 PREEvision 10.15

This chapter contains the following information:

6.1

Version numbers

6.2

Installation and compatibility information

6.3

New features in PREEvision 10.15

6.4

Configuration information

6.5

Fixed issues

Common

Diagrams

Tables

Requirements

AUTOSAR

Software architecture

Diagnostics

Communication

Hardware architecture

Product line engineering

Variant management

Change and release management

Test engineering and test management

Metrics

Reports

Collaboration

Administration

Installation

Server API

Backup, restore, and migration

6.6

Known issues

PREEvision 10.15
124 125 127 130 132 132 132 133 133 133 134 135 135 136 137 137 137 137 138 138 138 139 139 139 139 140

Version 10.20

123

6.1 Version numbers

Version numbers

Application PREEvision client PREEvision license server PREEvision database server PREEvision application server

Documentation

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

PREEvision 10.15
Version number 10.15.0 3.0.2 10.15.0.02 10.15.0
Version number 10.15.0 10.15.0 10.15.0 10.15.0 10.15.0

Version 10.20

124

PREEvision 10.15

6.2 Installation and compatibility information
For detailed information about the installation of PREEvision 10.15 and the migration to PREEvision 10.15, refer to the PREEvision operating manual.
For detailed information about the hardware and software requirements of PREEvision 10.15, refer to the PREEvision system requirements.

License server
LibreOffice update Compatibility

With PREEvision 10.15, the new version 3.0.2 of the standalone license server is available.
When you use the standalone PREEvision license server (RMI), it is recommended to update the license server to the new version 3.0.2.
The standalone license server 3.0.2 starts with the parameter PREEvisionLS.forcePermanentPort=true, by default. The parameter defines, that the license server only uses a single port for the communication (by default 1099) instead of a port range.
Amazon Corretto that is provided with the Windows installer of version 3.0.2 has been updated to version 11.0.23.9.1.

The internal LibreOffice component has been updated for more stable use and editing of formatted texts.

Client version
10.5.0 10.6.0 10.7.0 10.8.0 10.9.0 10.10.0 10.11.0 10.12.0 10.13.0 10.14.0 10.15.0

Server version
10.5.0 10.6.0 10.7.0 10.8.0 10.9.0 10.10.0 10.11.0 10.12.0 10.13.0 10.14.0 10.15.0

Database server script version 10.5.1.41 10.6.0.02 10.7.0.02 10.8.0.02 10.9.0.03 10.10.0.03 10.11.0.03 10.12.0.02 10.13.0.02 10.14.0.05 10.15.0.02

Metamodel change ID 2022-10-05 2023-04-03 2023-06-01 2023-07-20 2023-09-18 2023-11-13 2024-01-19 2024-03-14 2024-05-06 2024-07-08 2024-08-29

Migration and update PREEvision 10.0 SP17 or later can be migrated to PREEvision 10.15.

Version 10.20

125

PREEvision 10.15
Migrating to PREEvision 10.15 is only possible from PREEvision 10.0 SP17 or later. All remote operations (backup and direct migration) available in the PREEvision 10.15 administration panel can only be performed on PREEvision 10.0 SP17 or later. Remote model preparation must be performed on PREEvision 10.0 SP18 or later. If you want to migrate a PREEvision 10.0 version before 10.0 SP17 or PREEvision 9.5, contact the Vector support.
For the migration to PREEvision 10.15, it is recommended to update PREEvision 10.0 to the latest version (service pack update), at least PREEvision 10.0 SP17, before creating a backup and starting the migration. An update of PREEvision 10.5 or one of its following minor releases, starting with version 10.6, to PREEvision 10.15 requires no migration and can be performed as minor release update. An update of PREEvision 10.5 to a following minor release, for example, PREEvision 10.15, 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 > 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".

Version 10.20

126

PREEvision 10.15

6.3 New features in PREEvision 10.15

AUTOSAR import of relation context for instances

PREEvision 10.15 supports the AUTOSAR concept of Collections. Under Library | Library Package | Relation Context, you can create a Collection Instance. You can currently use a Collection Instance to combine an Atomic SW Component and a Service Dependency.

Model adaptions and checks during value handling

The value handling for the comfortable setting of values like initial values or invalid values has been improved. To adapt the value handling to your needs, you can integrate metrics that are executed right before and right after the values are created or changed via value handling.
The pre value handling metric can perform checks, model corrections or other adaptions before the product value handling mechanism starts. The post value handling metric can analyze or adapt the model the right after the value handling mechanism has been carried out.

Support of parameter interfaces for DIDs

Ports with parameter interfaces can now be used for Diagnostic Data Identifiers (DIDs) in diagnostic design. The Diagnostic Realization Explorer supports creation of port types with Parameter Interfaces as well as the preparation of the ports types for DIDs.

Version 10.20

127

PREEvision 10.15

Usability improvements The diagram toolbar buttons for changing the line routing style of connections between

for diagram toolbar

Rectilinear Style Routing, Oblique Style Routing, and Bezier Style Routing have

buttons

been consolidated into a split button.

The triple toggle button for changing the line routing style for new connections between the rectangular, oblique, and Bezier style has been changed to a split button.

The triple toggle button for showing and disabling the pop-up bar/tooltips has been changed to a split button.

Resetting fan size and fan waypoints

In the diagram toolbar, the new button resets the fan size and fan waypoints of a previously increased/decreased sender port.

The fan size and fan waypoints can also be reset via the diagram context menu.

Version 10.20

128

PREEvision 10.15

Extended populate function for wiring harness artifacts

In wiring harness design, the standard populate function for Wiring Diagrams and Wiring System Diagrams has been enhanced by an extended populate option. With the extended populate, all wiring artifacts from one Schematic Pin to all target Schematic Pins of components, including all wires, Splices and inline connectors, are populated into the diagram in a stepwise manner.

The extended populate function can also be executed via the new Populate metric block.

Asset creation: detection of insufficient permissions during propagation

During Asset creation or refresh, reasons for an incomplete propagation of artifacts due to out-of-scope or invisible artifacts are reported in the Information View.

The reasons for an incomplete propagation are also provided at the "invisibleAndOutOfScopeArtifacts" output port of the Asset Factory metric block.

Variant management

The Variant Condition Editor has been improved to display an icon and headline as well as an information if no default Data Type Package is set.
The new Open Condition Editor metric block is available to:
> open the Variant Condition Editor, for example, on a Pre Build Variant Condition that is displayed in a table.
> open the Condition Editor for Activities and the Condition Editor for State Machines, for example, on a condition that is displayed in a table.

Version 10.20

129

PREEvision 10.15

6.4 Configuration information

New metric blocks: populate

The new Populate metric block executes the extended populate function for Wiring Diagrams and Wiring System Diagrams. With the extended populate, all wiring artifacts from one Schematic Pin to all target Schematic Pins of components, including all wires, Splices and inline connectors, are populated into the diagram in a stepwise manner.
Required inputs (Data Target Ports):
> "startArtifact" (data type: MDIRepresentableArtefact): Start artifact of the populate function. Depending on the kind of diagram, different meta classes are allowed/expected.
> "diagram" (data type: MDiagram): Diagram in which the populate function is executed.
Optional inputs (Data Target Ports):
> "artifactsToPopulate" (data type: Collection<MDIRepresentableArtefact>): After execution, the populate generally fetches all technically relevant artifacts. Only artifacts that are part of the "artifactsToPopulate" are finally displayed in the target diagram. The artifacts displayed (and contained in the "artifactsToPopulate") are then the starting point for a successor populate. If "artifactsToPopulate" is empty, all found artifacts are displayed in the diagram. If incorrect artifacts are part of the list for the respective diagram, they are ignored.
> "direction" (data type: String): Direction in which all populated artifacts are shown in the target diagram. Possible values:
> "right" (default)
> "left"
> "up"
> "down"
> "populateKind" (data type: String): Kind of populate. Possible values:
> "standard" (default): classic populate function. All populate options are active and all available artifacts are to be shown.
> "externalMultiHop": The populate result is largely depending on the type of diagram. The function does point outwards to external connected artifacts and does not stop at an intermediate artifact. It is performed until the chain of artifacts end at a target artifact.
> "routingStyle" (data type: String): Line routing style of the displayed connection. The default value is defined by the current line routing style of the target diagram. Possible values:
> "oblique"
> "rectilinear"
> "Bezier"
Outputs (Data Source Ports):
> "notPopulatedArtifacts" (data type: Collection<MDFObject>): Returns the artifacts which do not exist in the diagram or where not populated in the diagram.

New metric blocks: open condition editor

The new Open Condition Editor metric block:
> opens the Variant Condition Editor, for example, on a Pre Build Variant Condition that is displayed in a table.
> opens the Condition Editor for Activities and the Condition Editor for State Machines, for example, on a condition that is displayed in a table.

Version 10.20

130

PREEvision 10.15

Required inputs (Data Target Ports): > "inCondition" (data type: MPreBuildVariantCondition or
MAbstractCondition): Condition on which the Condition Editor shall be opened.
Outputs (Data Source Ports): > "outCondition" (data type: List(MPreBuildVariantCondition,
MAbstractCondition)): Condition on which the Condition Editor was opened.
> "dialogFinished" (data type: Integer): Number of the dialog button pressed by the user: > 0 = [OK]
> 1 = [Cancel]
> -1: the dialog cannot be opened

Changed metric blocks: The Add-in Delivery metric block has the following new optional inputs (Data Target

add-in delivery

Ports):

> "cancelOnPropagationFindings" (data type: Boolean) Possible values:

> true: The delivery is canceled in case the Add-ins are not propagated properly.

> false (default)

> "cancelOnBranchSuffixFindings" (data type: Boolean) Possible values:

> true: The delivery is canceled in case contained artifacts do not have a branch suffix.

> false (default)

Changed metric blocks: asset factory

The Asset Factory metric block has the following new output (Data Source Ports):
> "invisibleAndOutOfScopeArtifacts" (data type: Map <CoreArtefact, ITempTable>): Information on invisible and out of scope artifacts during propagation grouped by direct core artifact / asset. It contains the source artifact, the relation that contains the artifact with insufficient permissions and the XMIID of the target artifact. Users with sufficient rights can look up the artifact for the XMIID and resolve the rights issue.

Version 10.20

131

PREEvision 10.15

6.5 Fixed issues

Fixed issues in PREEvision 10.15

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

Further information

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

6.5.1 Common
ID 9082947085201491866

Resolution
Formatted texts containing formula objects are no longer treated as changed when opened in the text editor. No lock or check-out dialogs are displayed anymore.

6.5.2 Diagrams
ID 9082947085490292081
9082947085965342024 9082947085944382046

Resolution
In the German equivalent of the Populate Artifact dialog, Nachbarn zeigen, the option Zeige Auswahldialog has been changed to Anzuzeigende Artefakte auswählen.
The performance has been improved for opening diagrams with certain label configurations.
Object configuration constraints that use an Embedded Metric Executor and are triggered from a diagram, receive the correct input artifact.

Version 10.20

132

PREEvision 10.15

ID 8682711687361192050 8682711687689231878
8682711687637842041

Resolution
When selecting a diagram in the Model View and subsequently selecting artifacts in the diagram via multiselect, the initial selection of the diagram is kept.
A Legend displayed in diagrams can no longer be resized manually in a diagram. Its size is always determined by the size of the Section defined in the Legend diagram.
The table border rendering during a PDF export of a Geometry Diagram has been improved.

6.5.3 Tables
ID 9082947084981671992
9082947085872961030

Resolution
In a table cell that provides a drop-down list, you can now use copy and paste to filter the entries or to select an entry.
When filtering tables that contain charts, the charts display results according to the filtered data in the table.

6.5.4 Requirements
ID 9082947085784772105
8682711686994932017

Resolution
A problem has been resolved that an Excel export aborts without helpful information for the user. An error message and a message in the Information View are shown when the content which should be written into an Excel cell exceeds the maximum of 32,767 characters.
The handling of hyperlinks in formatted texts that link to files on unreachable network targets has been improved.

6.5.5 AUTOSAR
ID 9082947085954611003 8682711686649931003 9082947084846702052
9082947086046791915 9082947086101302108

Resolution
File header contains correct PREEvision version in AUTOSAR exports.
AUTOSAR export: The payload of Secured IPDUs is exported for ECU extracts and for cluster extracts.
AUTOSAR export: Nv Data Receiver Com Specs are exported properly in case no NV Data is referenced but an Initial Value.
AUTOSAR export: LIN Frames for sporadic frames are ordered in a deterministic on export.
AUTOSAR export: The attribute isService is only exported for Classic interfaces.

Version 10.20

133

PREEvision 10.15

ID 9082947086065032108 8682711687044903013 9082947086149422051
9082947085967191825 9082947085480742113
8682711687100782052 9082947085099021911
9082947085889683042
9082947085984600091
9082947086061081915
9082947086046781915 9082947085767421807

Resolution
AUTOSAR export: The version of AUTOSAR schema regarding AUTOSAR 4.3.1 and 4.4.0 has been corrected.
AUTOSAR export: AUTOSAR software component export can handle out of scope artifacts via the relation from implementation data type to its users.
AUTOSAR import: To adapt the package structure, an 'Implementation Data Type Pointer' data type package is created under the 'Implementation Data Types' package on import.
AUTOSAR import: ARXML files are correctly imported.
AUTOSAR import and export: Collections with InstanceReferences in an ARXML file are now considered on import and export and represented as Relation Context in PREEvision.
ECU extract: The ECU Extract can handle Root Compositions which are directly mapped to the exported ECU.
ECU extract: Socket connections on client side are exported properly for ECU centric exports, like ECU extract or ECU communication extract with AUTOSAR version 19-11 or higher.
Consistency check: The performance of the Consistency Rule "cx2508_redundant_shortNames_in_virtualPackage" has been improved.
Consistency check: The performance of the Consistency Rule "AR_019908_ARC_all_ComponentWithSameName_ PortPrototype" has been improved.
Consistency check: The localization texts of the Consistency Rule "c3148_DataTransformation_with_invalid_ ExecuteDespiteDataUnavailability" reference the correct AUTOSAR constraint.
Consistency check: Signal transmissions related to Signal Groups are not flagged as erroneous.
Variation Points will not be exported if no AUTOSAR variant is selected.

6.5.6 Software architecture

ID 9082947085105201825

Resolution
The property page General shows the attribute ASIL decomposed for Application SW Components, Compositions, Sensor Actuator SW Components, ECU Abstraction Components, Complex Device Driver Components, and Adaptive Application SW Components.

Version 10.20

134

PREEvision 10.15

ID 9082947085590601825 9082947085901231804
9082947086096042106
9082947086067922111
9082947085903861804
9082947085897991268, 9082947085567782196, 9082947084934901029

Resolution
Minor Version and Major Version of Service Interfaces are imported and exported via Franca.
The property page Ports has been removed for software component types. The property page Unit Groups has been added for software component types.
When defining invalid values or inital values, enumeration values in table cells are displayed correctly when the cell editor is closed.
Data types with conversions now only get an enumeration widget in table cells using value handling if the conversion is a Verbal Table Conversion.
When the value handling mechanism creates a clone of a value specification structure with multiple users, the naming conventions are carried out for the cloned objects within the value handling business logic.
In the Property View of Input Activity Data Instances and Output Activity Data Instances only artifacts with the right meta class are shown.

6.5.7 Diagnostics
ID 9082947085600373056
8682711553173592113
9082947086062551867
9082947085895012113

Resolution
Diagnostic export: Diagnostic Trouble Codes are not exported if they are not contained in an active variant and the export option Export only active variant is set.
The property page Diagnostic Realization of Diagnostic Data Objects displays the Package that contains the Assigned Data Elements.
Diagnostic export: The attributes Encoding and Bit Length of primitive data types that are mapped to Parameter Interfaces are exported.
Diagnostic export: Irrelevant information removed from log information during export.

6.5.8 Communication
ID 9082947085560892046
9082947085588182046

Resolution
Signal router: In case System Signals are routed, an already routed path is identified, even if more than one Bus System is involved.
Signal router: System Signals and Signal IPDUs created by the signal router are assigned to the active variant if necessary.

Version 10.20

135

PREEvision 10.15

ID 9082947084966211914
17938307346772040

Resolution
Signal router: The user information has been improved in case of routing errors when dynamic VLAN edge weightings are applied, for example, if a preferred VLAN is set.
The description of the design approaches with Signals and System Signals or with Signals only in the manual has been clarified.

6.5.9 Hardware architecture

ID 9082947085592203084 9082947085824852083 9082947085055062062 9082947085854172083
8682711686800132112

Resolution
For a Single Wire or Core, the Property View displays the Wiring Connectors of the Wire Pins on the Connected Pins in Electric Circuit property page. The directly connected Wiring Connectors are displayed as well as the Wiring Connectors of Wire Pins which are connected via Contactings. If both relations are established, the relation via Contactings has priority.
The Property View of a Cable Prototype additionally displays all contained Shielding Prototypes. Due to this, the name of the corresponding property page and the name of the table on the property page have been changed to Contained Prototypes.
The Choose Counterpintype dialog and the Choose Pintype dialog have been renamed and the dialog descriptions adapted accordingly. The Choose Counterpintype dialog has been renamed to Choose Opposite Pin Type or Pin Type Family. The Choose Pintype dialog has been renamed to Choose Pin Type or Pin Type Family.
The Property View of a Wire Pin has been improved with respect to a directly assigned Wiring Connector. The relation Directly assigned Wiring Connector now displays the correct directly assigned Wiring Connector. If there is no directly assigned Wiring Connector for the Wire Pin, the relation remains empty. If the directly assigned Wiring Connector differs from the Wiring Connector assigned via Contacting, a warning icon is displayed.
The standard populate function for Wiring Diagrams and Wiring System Diagrams has been enhanced by an extended populate. It is possible to populate all wires, splices, inline connectors from component to component in a stepwise manner.

Version 10.20

136

PREEvision 10.15

6.5.10 Product line engineering

ID 9082947085939132112 9082947085995432012
8682711686591192023

Resolution
When integrating artifacts of Assets, detailed information is reported in the Information View if a merge is prevented due to the current Scope or permission restrictions.
Restoring a historic Asset has failed if an artifact of the historic Asset has had an external relation to an artifact that is still in the head. Restoring a historic Asset is only aborted if a restored artifact is a checked-out reuse of an artifact outside the Asset.
If the External Relation Analyzer is already open, an information dialog is displayed if you try to open the External Relation Analyzer again on another artifact. Via the dialog you can decide whether to close the already opened External Relation Analyzer and automatically open the new one on the newly selected artifact, or to keep the already opened External Relation Analyzer.

6.5.11 Variant management

ID 9082947085767411807

Resolution
VM Explorer: Check for AUTOSAR compliance has been updated to the latest specification.

6.5.12 Change and release management

ID 9082947085834521029
9082947086001030064

Resolution
The demo Add-ins of the product delivery have been updated to contain the complete Change Profile configuration.
The Compare Table correctly displays differences of formatted texts. Additionally, unedited formatted texts are no longer saved when closing the Compare Table.

6.5.13 Test engineering and test management

ID 9082947085591492101

Resolution
An issue has been fixed where for specific Test Specification Editor tables an invalid threat access message was shown when opening the table.

Version 10.20

137

PREEvision 10.15

6.5.14 Metrics
ID 9082947085022702024
9082947085592202102

Resolution
The error handling of Collaboration Metric Executors has been improved to report the same error only once in the user interface. When the metric execution fails, the status is now reported in the same way as for Embedded Metric Executors, which is as flat entries instead of nested entries.
The behavior of the Open Editor in Area metric block has been improved:
> When an editor is to be opened without a defined "Split Option" port in an area that is already subdivided ("sash"), it is now added to one of the subdivision's stacks.
> When the target area for the new editor is already split ("sash"), no additional areas are created.

6.5.15 Reports
ID 9082947085073431995
9082947085905842046

Resolution
The handling of reports has been improved to avoid rare cases in which the report could no longer be opened because of erroneous placeholders.
Generating reports has been improved to resolve placeholders in headings that are referenced by the table of content.

6.5.16 Collaboration
ID 9082947085573222105
9082947085601052203
9082947085965352024, 9082947085965132024, 9082947085967182106 8682711687660712101
8682711687495052041
9082947085962002106

Resolution
If the identity provider for authentication is not available, the client no longer repeatedly shows error messages. Instead, the client switches to offline mode.
The model update works properly even if many reuses (more than 1.000) have been updated.
An update error has been resolved that occurred if an artifact with localization support and model roots in a generic package was deleted.
The commit and update performance has been improved when changing the subtree to another revision.
The Commit dialog correctly displays changed custom attributes in the popup window of the changed artifact.
Undo All Own Locks cannot be executed when the client model is in read-only mode after an error during a model update.

Version 10.20

138

PREEvision 10.15

ID 9082947084934482105

Resolution
The performance has been improved for temporarily loading many artifacts into the scope. The performance of cancelling the action has been improved as well and no longer leads to errors.

6.5.17 Administration
ID 8682711687484481808 9082947087135501786
8682711554642701806

Resolution
Improved check that customized Add-ins cannot be customized again, which is not a supported use case.
A commit error has been fixed that was caused by the online check calculation of Propagate Definitions on the server if the underlying Propagate Definition rule was modified. The error occurred after manual change of the Propagate Definition or during Add-ins installation/update.
Model consistency checks are not executed redundantly when loading a model and model consistency check results are not redundantly reported in the Information View.

6.5.18 Installation
ID 8682711687651811229

Resolution
A check for special characters has been added to the validation of file paths during installation. If invalid characters are found in the path, an error dialog is displayed.

6.5.19 Server API
ID 9082947085982233115

Resolution
The ISO-8601 date time format is supported in the API server.

6.5.20 Backup, restore, and migration

ID 9082947085911601806

Resolution
A model preparation streaming error has been fixed that could occur if a remote backup or restore was executed in the administration panel and the user enabled model preparation. The model preparation is also automatically executed during a remote backup or a remote restore.

Version 10.20

139

PREEvision 10.15

6.6 Known issues

Known issues in PREEvision 10.15

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

ID 17938307791212069
8682711552649222003 9082947086366032005 8682711555165912106 8682711555133422025 8682711686247202025

Known issue
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.
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.
If an AUTOSAR file to be imported contains COLLECTIONS of the category RELATION, the contained instance references might not be imported correctly in cases of multi-instantiations of software compositions. If an SW Component Type is instantiated only once, the import works correctly.
ReqIF export: For empty attributes, the string defined in the Text for empty Labels property is exported instead of and empty string. By default, this is "---". Workaround: In the Preferences, under PREEvision | General, remove all characters from the Text for empty Labels property.
<Ctrl> + click on a preview image in a formatted text may not open the linked File Attachment. Workaround: Use the context menu on the preview image or double click on the File Attachment artifact in the Model View to open the file attachment.
When inserting a diagram placeholder based on templates, an error message is reported that the used template is incomplete. Workaround:
1. Navigate to the selected template under Administration | Configuration File Container | Report Template Package and select the affected template file.
2. Open the location of the file in the Windows Explorer and delete the file.
3. Update from the server to force a reload of the file.

Version 10.20

140

PREEvision 10.15

ID 8682711686179212044
8682711687572062012 8682711555191801873
8682711685521992014 8682711687181061868 9082947085110861914, 9082947085889122108

Known issue
When generating a report for a diagram as PDF, an error message is reported that the report generation was not able to write any data in the Temp directory and is aborted. Workaround:
1. Navigate to the report under Administration | Report Model and select the report file.
2. Open the location of the file in the Windows Explorer and delete the file.
3. Update from the server to force a reload of the file.
Using the control-key to navigate in a formatted text which contains a placeholder or using shortcuts to cut or copy and paste a placeholder may lead to editors being opened in the background. Workaround: Close the opened editors and continue.
During reinitialization of the authority model an error message may be displayed reporting an unexpected error with the ramc.ser file. Workaround:
1. Delete the authority model.
2. Connect to the authority model.
3. Initialize the authority model.
For Application Curve Types and Application Cube Types, the Calibration Attributes property page is missing in the Property View. It will be restored in a future minor release.
The automatic integration of an Asset may be incomplete during use, reuse, or update of the Asset if related artifacts with abstraction or substitution links in a downstream Product Line are read-only. Workaround: Execute the automatic integration again.
Opening the VM Explorer or the VM Explorer without Customer Feature Model may lead to performance problems. This may be due to filter configurations which are set on specific explorer categories. Workaround: Customize the corresponding "VM Explorer" and "VM Explorer without Customer Feature Model" Add-ins, and remove the Explorer Filter Configurations set on the affected explorer categories.

Version 10.20

141

7 PREEvision 10.14

This chapter contains the following information:

7.1

Version numbers

7.2

Installation and compatibility information

7.3

New features in PREEvision 10.14

7.4

Changes

7.5

Configuration information

7.6

Fixed issues

Common

Diagrams

Tables

Requirements and customer features

Logical function architecture

AUTOSAR

Software architecture

Diagnostics

Communication

Hardware architecture

Product line engineering

Change and release management

Test engineering and test management

Rules

Metrics

Reports

Collaboration

Administration

License

Backup, restore, and migration

7.7

Known issues

PREEvision 10.14
143 144 146 151 152 153 153 153 154 154 155 155 156 157 158 158 159 159 160 160 160 160 160 161 162 162 163

Version 10.20

142

7.1 Version numbers

Version numbers

Application PREEvision client PREEvision license server PREEvision database server PREEvision application server

Documentation

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

PREEvision 10.14
Version number 10.14.0 3.0.1 10.14.0.05 10.14.0
Version number 10.14.0 10.14.0 10.14.0 10.14.0 10.14.0

Version 10.20

143

PREEvision 10.14

7.2 Installation and compatibility information
For detailed information about the installation of PREEvision 10.14 and the migration to PREEvision 10.14, refer to the PREEvision operating manual.
For detailed information about the hardware and software requirements of PREEvision 10.14, refer to the PREEvision system requirements.

System requirements

The following system requirements have been changed:
> Oracle 12.1.0.2 and Oracle 12.2.0.1 are no longer supported for the PREEvision database server.
> It is recommended to use VisualSVN Server version 5.3.2 for the PREEvision subversion server.

KeyCollector

A new version of the PREEvision KeyCollector (keyinfo_collector.bat) is available. You can use the PREEvision KeyCollector to create a file that contains the system information that is necessary for issuing a license. The script can either be found in the client installation directory under ../res/tools or can be separately downloaded.

Compatibility

Client version
10.5.0 10.6.0 10.7.0 10.8.0 10.9.0 10.10.0 10.11.0 10.12.0 10.13.0 10.14.0

Server version
10.5.0 10.6.0 10.7.0 10.8.0 10.9.0 10.10.0 10.11.0 10.12.0 10.13.0 10.14.0

Database server script version 10.5.1.41 10.6.0.02 10.7.0.02 10.8.0.02 10.9.0.03 10.10.0.03 10.11.0.03 10.12.0.02 10.13.0.02 10.14.0.05

Metamodel change ID 2022-10-05 2023-04-03 2023-06-01 2023-07-20 2023-09-18 2023-11-13 2024-01-19 2024-03-14 2024-05-06 2024-07-08

Migration and update

PREEvision 10.0 SP17 or later can be migrated to PREEvision 10.14.
Migrating to PREEvision 10.14 is only possible from PREEvision 10.0 SP17 or later. All remote operations (backup and direct migration) available in the PREEvision 10.14 administration panel can only be performed on PREEvision 10.0 SP17 or later. Remote model preparation must be performed on PREEvision 10.0 SP18 or later. If you want to migrate a PREEvision 10.0 version before 10.0 SP17 or PREEvision 9.5, contact the Vector support.

Version 10.20

144

PREEvision 10.14
For the migration to PREEvision 10.14, it is recommended to update PREEvision 10.0 to the latest version (service pack update), at least PREEvision 10.0 SP17, before creating a backup and starting the migration. An update of PREEvision 10.5 or one of its following minor releases, starting with version 10.6, to PREEvision 10.14 requires no migration and can be performed as minor release update. An update of PREEvision 10.5 to a following minor release, for example, PREEvision 10.14, 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 > 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".

Version 10.20

145

PREEvision 10.14

7.3 New features in PREEvision 10.14

Usability improvements for working with file attachment placeholders

When pasting images onto Preview Images of File Attachments, the new Replace With Image From Clipboard dialog offers the possibility to replace the Preview Image of a File Attachment or to replace the entire File Attachment placeholder.

Usability improvements The usability of the Styles and Formatting view has been improved. When changing

for the styles and

perspectives or upon closing and reopening of the Styles and Formatting view, the

formatting view

previously chosen tab is retained.

Usability improvements Multiple usability improvements for Class Diagrams have been implemented:

for class diagrams

> Default multiplicities are defined based on relation type.

Version 10.20

146

PREEvision 10.14
> Default role names based on associated class name and multiplicity have been optimized, the multiplicity suffix is adjustable via the new Class Diagram preferences page.

> Default names of generalizations and realizations have been optimized. > No labels on relations are displayed in the diagram per default.

Activity diagram: modeling activities for methods and fire and forget methods

An Activity can now be created under Methods and Fire and Forget Methods. UML Parameters serve as input/output data for the Activity. The Condition Editor for Activities now support using UML Parameters to express conditions. An enhanced window lifter example is available in the demo model.

Behavior modeling: additional online checks

Additional online checks to verify that UML Parameters with direction IN or OUT are not connected as output or input data, respectively. This applies to the following artifacts: > State Machine Data Instance > Input Activity Data Instance > Output Activity Data Instance > Input Activity Data Instance Proxy > Output Activity Data Instance Proxy

Version 10.20

147

PREEvision 10.14

Support of timeouts of process startup configurations

The Enter Timeout Value and the Exit Timeout Value can now individually be set for Process Startup Configurations. You can enter the values on Timeouts page in the Property View or in the Startup Dependencies Editor in the AUTOSAR Adaptive Explorer. The values can be exported via the software cluster design description and the execution manifest.

Support of generic

For AUTOSAR Adaptive designs, Generic Module Instantiations can be assigned to

module instantiation on Machine Desployments.

a machine

The Generic Module Instantiations can be exported using AUTOSAR Adaptive exports like machine manifest, machine design extract, software cluster design description, and execution manifest. Consistency checks prevent Processes with more than one Machine Deployment and Generic Module Instantiations without a process assignment in the model.
Usability for calibration The value handling for objects typed by calibration data types like axis, curves or maps is parameters: take over further simplified. When setting values for objects typed by such data types, the Unit of of unit in value handling the data type is directly taken over to the literal carrying the value. Prioritization rules
defined by AUTOSAR are considered.

Version 10.20

148

PREEvision 10.14
The inheritance of the unit can be enabled or disabled with the Boolean flag Inherit Data Type Unit on the Value Handling Configuration.

Support of parameter interfaces for DIDs

Diagnostic Data Identifiers and their Diagnostic Data Objects are realized with a combination of a software port and selected details of its interface. This can be:
> a Data Element of a Sender Receiver Interface
> an NV Data of a NV Data Interface
> a Client Server Interface and its details
With PREEvision 10.14, also Parameters and Parameter Interfaces are supported. Diagnostic Data Identifiers with Parameters and their details are considered for the diagnostic export.

3D coordinates for topology segment points

3D coordinates can be defined for Topology Segment Points Tt properly import and export 3D coordinates of Topology Segment Points via KBL.
3D coordinates are supported by the KBL import and KBL export as Cartesian_points referenced by a Fixing_occurrence (a Topology Segment Point with assigned Topology Type) or an Accessory_occurrence (a Topology Segment Point with assigned Mounting Clip).

Product line engineering improvements

For product line engineering, improvements for the following use cases have been implemented.
Revoking assets:
> A uniform revoke behavior has been implemented for Assets. A revoke is executed until the integration target candidate is orphaned, this means no core artifact of an Asset with predecessor anymore.
> For a revoke via reuse, the external duplicate relations of an Asset are removed in the following cases:
> if the relation is no type-of-relation and is not marked with forceCopyContent
> if the relation is not contained in another Asset with predecessor

Integrating assets:
Integrations via move are now part of the integration order. To-one-relations or type-ofrelations are considered. Generally, integrations via move are placed after integrations via merge in the integration order. The automatic integration via move fails if the artifact to be integrated has a to-one-relation or a type-of-relation to an artifact to be integrated.

Extended model consistency checks:
Extended model consistency checks are available to cover invalid states of artifacts to be integrated. For example, a core artifact must not be contained in a core integration assigned to another Asset or no Asset.

Version 10.20

149

PREEvision 10.14
Integration via merge for abstraction from downstream: An integration via merge is now possible if the abstraction or substitution from downstream is invisible or out-of-scope.
Activation conditions for For Propagate Definitions, it is now possible to define an activation condition. To define a propagate definitions condition, Object LHS of the Propagate Definition can be linked with each other via a
Rule Object Condition. Rule Object Conditions can be modeled in the new Rule Object Condition Diagram, which can be created in a Rule Object Condition Package under the Propagate Definition Package. In the Rule Object Condition Diagram, Object LHS of the Propagate Definitions can be assigned to a logical operator via drag and drop. In the Propagate Definition Diagram, Object LHS that are assigned to a Rule Object Condition are indicated by an icon.

Add-ins installation:

In the Add-in Installation dialog on the Add-ins tab, the new Installation Type column

mandatory and optional displays whether an Add-in is mandatory or optional. Alle mandatory product Add-ins are

add-ins

installed/updated by default and cannot be deactivated. Optional Add-ins can be

additionally installed.

Version 10.20

150

PREEvision 10.14

7.4 Changes

Naming of prototypes in The name of the root software component prototype of an Executable

software cluster design (Executable.rootSwComponentPrototype) is set during the export of a software

description

cluster design description. For the RootSwComponentPrototype.shortName, the

(868271168694007102 following rules apply:

If via software component an Executable references:

> an Adaptive Application SW Component Type for which exactly one Atomic SW Component Prototype exists, the name of this Atomic SW Component Prototype is used.

> a Composition Type for which exactly one Composition Prototype exists, the name of this Composition Prototype is used.

> a Composition Type which is instantiated as a Root Composition, the name of the Root Composition is used.

> a Composition Type which is instantiated both as a Composition Prototype and a Root Composition, the name of the Composition Prototype is used.

> an Adaptive Application SW Component Type or a Composition Type for which multiple instantiations exist (Atomic SW Component Prototypes or Composition Prototypes, respectively), then, as currently, the name of the Executable is used.

To allow different names used for a type and a prototype of a software component, the checkbox If only one instance exists, synchronize type name and instance name should be deactivated under Window | Preferences | PREEvision | Editors LA / SW.

Variant propagation rules in demo model

For more consistency within the demo model, the existing Variant Propagation Rules have been moved to a new package structure that reflects the modeling layers. Some obsolete Variant Propagation Rules have been deleted.

Enhanced "Wiring Harness Demo Model" product line

The "Wiring Harness Demo Model" Product Line in the PREEvision demo model has been enhanced with additional Wire Type Families, Pin Types, Seal Types, and Connector Types. In addition, the used parts for the demo harness represent real parts with real part numbers of the mentioned suppliers.

Version 10.20

151

PREEvision 10.14

7.5 Configuration information

Rule name uniqueness

During rule generation, uniqueness of rule names is now checked case insensitive. For example, the rule names "BusTypes" and "busTypes" are identified as identical and are reported as error during rule generation.
Rule names must be unique throughout the entire rule model type. For example, within the Query Rule Model, the names of the Query Rules must be unique.

Changed metric blocks

To the Update Asset With Historical Version metric block, the following Data Target Port has been added:
> "restrictSelectionToHigherRevisionsInSameBranch" (optional, data type: Boolean): Only those checked-in versions of the Product Line are shown in the selection that contain an Asset predecessor in the same branch but with a higher revision number. Default: false

The Add-in Content metric block has been changed:
> The block can now be used to propagate several Add-ins at once.
> The "addInContent" Data Source Port has been removed. The propagated artifacts can instead be accessed via the method MDFReuseUnitUtility.getPropagatedReuseUnit(addin).mdfGetReuseUnitCore().

Version 10.20

152

PREEvision 10.14

7.6 Fixed issues

Fixed issues in PREEvision 10.14

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

Further information

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

7.6.1 Common
ID 8682711687676021995

Resolution
The default Export Profile for the model export has been added to the "EEA Export" Add-in. The "EEA Export" Add-in is installed as mandatory product Add-in.

7.6.2 Diagrams
ID 9082947085174091843 9082947084906702059
8682711687614392046

Resolution
Custom attributes are evaluated properly for labels defined in the Label Configuration.
In the search field of diagrams, the shortcuts <Ctrl>+<C>, <Ctrl>+<V>, <Ctrl>+<A>, and <Ctrl>+<X> are correctly executed and are only applied to the search field if the focus is set on the search field.
The text color in diagrams is exported again when choosing the WMF file format.

Version 10.20

153

PREEvision 10.14

ID 9082947084962572196, 9082947085484832196
9082947085484832196, 9082947084962572196
8682711686960422041

Resolution
In the Property View, the enclosing method name is correctly displayed in the display name of the Parameter for the Data Provider and Data to Set relations of Input Activity Data Instances/Output Activity Data Instances if the Activity is created under a UML Class.
In the Property View, additional information, for example, context, direction, or data type are included in the display name of the Parameter, Operation Argument, NV Data, and Data Element for the Data Provider and Data to Set relations of Input Activity Data Instances/ Output Activity Data Instances.
Diagram export as PNG file: The representation of rotated texts has been fixed.

7.6.3 Tables
ID 9082947084906630095 8682711687075110069 8682711687471372105
9082947084966342080
9082947084989621884
9082947085015131884

Resolution
When editing formatted text in a table cell, the text editor is properly closed when leaving the table cell.
Expanded artifacts in tables are reliably re-expanded after a table refresh (<F5>).
In the search field and in the replace field of tables, the shortcuts <Ctrl>+<C>, <Ctrl>+<V>, <Ctrl>+<A>, and <Ctrl>+<X> can be executed correctly.
In the Search result view and Replace view, the shortcuts indicated in the tooltips for Show Next Match and Show Previous Match are consistent and work as expected.
In the Object Configuration Error View, an error in the same object configuration is only reported once, even if it is reported for different artifacts.
In the Object Configuration Error View, the Error Status column displays a message if the execution of a rule or metric was skipped because it is part of an already deactivated object configuration.

7.6.4 Requirements and customer features

ID 9082947085490482107 9082947085052252100
8682711687688162105

Resolution
The integrated LibreOffice version has been updated to fix the deadlock during the report to PDF conversion.
A deadlock has been fixed which occurred if editing a formatted text was not possible and the restorable formatted text from the Information View was empty.
ReqIF Export: Formatted texts that contain hyperlinks with a name no longer cause schema validation errors.

Version 10.20

154

PREEvision 10.14

ID 8682711687501582025
9082947085563152105 8682711554419382106 9082947084933612102

Resolution
The PREEvision undo action correctly works after replacing a text placeholder with a file attachment preview image.
It is now possible to assign multiple values to custom attributes.
Icons and texts listed in table columns with check box lists are aligned properly with all display resolutions.
For Customer Features, an icon has been implemented to indicate Customer Features as tagged for deletion.

7.6.5 Logical function architecture

ID 9082947084905622105

Resolution
Opening a Logical Architecture Diagram which contains broken mapping boxes does not lead to client freezes anymore.

7.6.6 AUTOSAR
ID 8682711554188122004 9082947085110801825 8682711685439951807 8682711687081002004 9082947084966161914 8682711687395961029 8682711686532692051 8682711686939801024

Resolution
ECU extract: Value Specifications under the port types are exported correctly.
ECU extract: The severity of the Consistency Check "pc1000_PduGroupWithoutECU " has been changed to error and the error message has been improved.
ECU extract: In exports >19-11, service instances of the opposite ECU are only exported if they are relevant in the communication.
ECU extract: RemoteUnicastAddresses for static service discovery are exported correctly.
The demo Product Line "Vector Calculator" has been corrected by adding relations between Service Providers or Service Consumers and software component types.
AUTOSAR platform types are now provided in a dedicated demo Add-in called "AUTOSAR Platform Types". This Add-in is not mandatory.
AUTOSAR import: When importing a folder with an unsupported AUTOSAR version, an error dialog will be shown.
AUTOSAR import (AR 20-11): An exception during the import of unsupported artifacts or attributes, like DiagnosticParameter, DiagnosticDataElement, or DiagnosticTroubleCodeUds.severity, has been resolved.

Version 10.20

155

PREEvision 10.14

ID 9082947085061771998
9082947085111021794, 9082947085096251024
9082947085171821794, 9082947085096251024 9082947084901510091
9082947084916991024, 9082947085096251024 9082947085110281003
9082947084989673089

Resolution
AUTOSAR import: Formulas for variation points that consist of a single literal are now correctly handled and can be imported.
AUTOSAR import: The behavior of the parser has been fixed for old AUTOSAR versions before the multiplicity changed for the relations ServiceInstanceToMachineMapping. secureComPropsForUdp and ServiceInstanceToMachineMapping. secureComPropsForTcp.
AUTOSAR import with merge: PortTransformationSpecifications are now correctly imported and merged.
AbstractGlobalTimeDomainProps. globalTimeDomainProperty in AUTOSAR is supported by import and export for version 4.4.0 and higher.
AUTOSAR Adaptive import: Also incompletely modeled EthernetCommunicationConnectors can be imported.
AUTOSAR export: The attribute Event Group Control Type of So Ad Routing Groups with value "TRIGGERUNICAST" is now exported correctly.
AUTOSAR Adaptive Explorer: A column for the Major Version has been added to SOME/IP Consumed Service Instance SD Editor.

7.6.7 Software architecture

ID 9082947085490552196 8682711687278111917
8682711687347542051 8682711687394533013

Resolution
For object-oriented modeling with Class Diagrams, icons for indicating the virtual folders "Realizations" and "Generalizations" in the Model View have been implemented.
Two Consistency Checks have been added: "p1000_wrong_synchronization_name_for_attribute_ definition" checks if the synchronization name does not match any attribute of the configured classes for the attribute definition. "p1001_wrong_synchronization_name_for_attribute_ definition" checks if the synchronization name does not match any attribute of the returned class by the configured Query Rule at the synchronization method.
DBC export: Attribute Definitions of type enumeration for Frame Transmissions are now correctly handled.
In the dialog for initial value it is now possible to enter initial values for arrays.

Version 10.20

156

PREEvision 10.14

ID 8682711687494201804 8682711687672551045 9082947084768291825
9082947084769491024 9082947085174212052
9082947085022692108 9082947085763001804

Resolution
Variables and parameters in an Internal Behavior are now exported as local or global ("autosar") according to the variable and parameter type.
Missing attributes on property pages of Constant Memory were added.
Attribut convention for java default values works now. When an attribute convention is applied that sets the value of an attribute to the java default value (for example, "0 "), then the default marker for the attribute will be set to FALSE and the change marker will be set to TRUE.
The property page Executables has been added for Composition Types and Adaptive Application SW Component Types including a table that shows the referenced Executables and their parent.
When creating a new software type and prototype via the Select or Create SW Type dialog, the last selected Software Type Package where to insert the new software type persisted. Thus, no new selection is necessary when the dialog is opened another time. If no package is selected or if no package can be found, the active Software Type Package or Software Types workspace is used as initial package selection.
For calibration data types like maps and curves with a shared axis, the Set Values dialog now correctly displays the name of the shared axis.
Multiple Value Handling Configurations for the same meta relation now lead to less errors, due to the configuration prioritization of the relation of the concrete meta class compared to the abstract meta class.

7.6.8 Diagnostics
ID 8682711687441283013
9082947085109672005 9082947085181642111 9082947085488712113

Resolution
Diagnostic export: The diagnostic export is possible if an interface that is used for a software realization of a diagnostic object is additionally assigned to another port in the same ECU.
Diagnostic export: The content of a PVCDI file is now written in a deterministic way. The contained artifacts have a fixed order after export.
Diagnostic export: Default values of custom attributes are properly considered for export if the Attribute Definition is part of the export profile and of the active variant.
Diagnostic export: If the Bit Length of data types is "0", is only checked for data types that are used in the context of a diagnostic object, not in the context of an Attribute Definition.

Version 10.20

157

PREEvision 10.14

ID 9082947085889122113

Resolution
Diagnostic export: Initial values of data types with a Scale Linear Verbal Table Conversion can be shared with other data types (that is, with a linear conversion). Only enumerations and data types with Verbal Table Conversions require individual initial values.

7.6.9 Communication
ID 8682711687711581030
9082947085195792050
9082947084956721032
9082947084933901029

Resolution
Frame-PDU synthesis: The frame-PDU synthesis now creates dedicated Frame Transmissions and PDU Transmissions for every sending J1939 Nm Node.
The communication path router no longer attempts to route the communication path if either the source or the target artifact is not part of the active variant.
DBC export: A warning in the Information View indicates if there are invalid selector signals in a multiplexed frame.
DBC-specific property pages are now located in the Property View of CAN Signal Transmission instead of the Signal Transmission.

7.6.10 Hardware architecture

ID 8682711687409022081 9082947085014631878
8682711687689972050 8682711687664123090

Resolution
The icon of the Electric Circuit System Diagram is now used consistently. For indicating Electric Circuit System Diagrams in PREEvision, the icon of the Electric Circuit System Diagram meta class as displayed in the Model View is used.
When canceling the progress dialog while executing a synchronicity check for an auto-layout diagram or an origin diagram, no message is displayed at all, anymore. A message is only displayed in case of errors or after the synchronicity check has been executed displaying the result of the check.
In the Model View, a Schematic Pin can be moved from one connector to another connector if the target connector is of the same type as the original connector. Logical power out and logical power in connectors are considered as equal.
The error which occurred during the calculation of highlighting in the context of tables displayed in a Wiring Diagram has been resolved.

Version 10.20

158

PREEvision 10.14

ID 9082947085580222083 9082947085574592083
9082947085580522083 9082947085481212083
9082947085137532083

Resolution
The online check "C8023_AbstractWire_withoutWiringModule" has been adjusted and is triggered if a wire is not assigned to a Wiring Module.
The online check "C8115_WiringConnector_withoutHeaderConnector" has been adjusted and only considers Wiring Connectors which are not part of a Wiring Harness Inline Connector or Wiring Harness Multi Inline Connector.
The online check "C8111_Wirepin_withoutWiringConnector_ onInlineConnector" has been adjusted and is triggered if a Wire Pin is not assigned to a Contacting.
The online check "C8755_Artifact_withLength_HasNoDataTypeUnit" has been adjusted and is only triggered for wiring harness relevant artifacts which have no assigned Data Type Unit as length unit.
KBL export: The export of a Cross Section Area set for a Cable Type is properly executed. As decimal separator for the defined numerical value a "." must be used. Invalid entries are exported as "0.0" to KBL.

7.6.11 Product line engineering

ID 8682711687570561995
9082947084982491029

7.6.12 Change and release management

ID 8682711687667032024

Resolution
The "createAgreementTaskItemIfAbsent" metric of the Review Table now checks whether the core artifact is null prior to further processing.

Version 10.20

159

PREEvision 10.14

7.6.13 Test engineering and test management

ID 9082947085049262008

Resolution
In the Test Specification Editor, the column Req/CFLinks has been renamed to Subjects to Verify.

7.6.14 Rules
ID 9082947085055051837

Resolution
During rule generation, uniqueness of rule names is now checked case insensitive. For example, the rule names "BusTypes" and "busTypes" are identified as identical and are reported as error during rule generation.

7.6.15 Metrics
ID 8682711687055213090

Resolution
Using ICloneEnvironment in a metric for creating artifacts no longer leads to a different check-out behavior.

7.6.16 Reports
ID 8682711687182481783

Resolution
Existing and newly created conditional placeholders as well as additional text contained in the placeholder are correctly formatted with a character style.

7.6.17 Collaboration
ID 9082947085793571918
8682711687669772106
9082947084769602106, 9082947085110471024 8682711687502592101 8682711687618912081

Resolution
Checked-out artifacts like ECUs can be reused without external relations. However, Product Lines must be checked-in so that they can be reused.
An issue has been fixed that lead to an error during the undo operation. An automatic model update is no longer triggered during an undo operation.
An error has been fixed which occurred during loading the model from the local model cache file.
An issue has been fixed, which caused an error when the user cancelled the locking of artifacts.
In the Property View, the highlighting for out-of-scope contents is only displayed if a formatted text field contains a placeholder that references an artifact that is

Version 10.20

160

PREEvision 10.14

Resolution

out-of-scope. If the referenced artifact itself is in the scope and contains another placeholder to an artifact out-of-scope, no highlighting is displayed.

7.6.18 Administration
ID 9082947085071782054, 8682711686653982050
8682711687661042011
9082947085011703046
9082947085015412012
9082947085490292011 9082947085546783046 9082947085543300063 9082947085586041995 9082947085819752020 9082947085886251868 8682711687095223115 8682711686247122101

Resolution
Administration panel: The maintenance mode can be deactivated by the administrator who activated the maintenance mode even if another administrator tried to deactivate the maintenance mode, which was denied by the administration panel.
In the Add-In Installation wizard, the default setting for selecting the Add-ins model to install has been changed from Use Product Add-ins Model to Use customized Add-ins Model.
The Installation/Update Of Add-ins page of the Add-In Installation Wizard now updates after changing the selection of the Add-ins model to be installed. The [Install] button is now active only on this page.
The Add-in Type column of the selection table on the Installation/Update Of Add-ins page of the Add-in Installation wizard has been renamed to Installation Type.
To the Add-ins Overview table, an Installation Type column has been added.
The Add-in Delivery block now accepts Add-ins, Add-in Packages, and both local and global Add-ins models as input.
Obsolete Rule Groups will not be moved to the "Obsolete" Add-in but deleted directly.
Object and Label Configuration Delta Files have been removed from mandatory and recommended Add-ins to allow for customization of these Add-ins.
Non-versioned artifacts are now checked out when updating Add-ins. Previously failed commits can now be completed.
The toolbar button for checking-in Add-ins in the Add-ins Overview table has been made functional.
Life Cycle Triggers with undefined Trigger Type are now treated as Life Cycle Triggers of the "Manual" Trigger Type.
The Information View no longer displays unnecessary messages related to transitions between Life Cycle States.

Version 10.20

161

PREEvision 10.14

7.6.19 License
ID 9082947085490482051

Resolution
An error in the PREEvision KeyCollector has been fixed. A new version of the PREEvision KeyCollector (keyinfo_collector.bat) is available. The script can either be found in the client installation directory under ../res/tools or can be separately downloaded.

7.6.20 Backup, restore, and migration

ID
8682711686593812054, 9082947085816431837

Resolution
An issue has been fixed in the server-to-server backup/ restore from PREEvision 10.5 to PREEvision 10.5.

Version 10.20

162

PREEvision 10.14

7.7 Known issues

Known issues in PREEvision 10.14

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

ID 17938307791212069
8682711552649222003 8682711555165912106 8682711555133422025 8682711686247202025
8682711686179212044

Known issue
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.
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.
ReqIF export: For empty attributes, the string defined in the Text for empty Labels property is exported instead of and empty string. By default, this is "---". Workaround: In the Preferences, under PREEvision | General, remove all characters from the Text for empty Labels property.
<Ctrl> + click on a preview image in a formatted text may not open the linked File Attachment. Workaround: Use the context menu on the preview image or double click on the File Attachment artifact in the Model View to open the file attachment.
When inserting a diagram placeholder based on templates, an error message is reported that the used template is incomplete. Workaround:
1. Navigate to the selected template under Administration | Configuration File Container | Report Template Package and select the affected template file.
2. Open the location of the file in the Windows Explorer and delete the file.
3. Update from the server to force a reload of the file.
When generating a report for a diagram as PDF, an error message is reported that the report generation was not able to write any data in the Temp directory and is aborted. Workaround:
1. Navigate to the report under Administration | Report Model and select the report file.

Version 10.20

163

PREEvision 10.14

ID 9082947085201491866
8682711687572062012 8682711555191801873
8682711685521992014 8682711687181061868 9082947085110861914, 9082947085889122108
9082947085911601806

Known issue
2. Open the location of the file in the Windows Explorer and delete the file.
3. Update from the server to force a reload of the file.
Formatted texts containing formula objects are erroneously treated as changed when opened in the text editor. This may lead to unwanted and unnecessary locks and check-out dialogs. Workaround: Deny lock/check-out in the dialog. A way to repair these formula objects will be implemented in one of the following releases.
Using the control-key to navigate in a formatted text which contains a placeholder or using shortcuts to cut or copy and paste a placeholder may lead to editors being opened in the background. Workaround: Close the opened editors and continue.
During reinitialization of the authority model an error message may be displayed reporting an unexpected error with the ramc.ser file. Workaround:
1. Delete the authority model.
2. Connect to the authority model.
3. Initialize the authority model.
For Application Curve Types and Application Cube Types, the Calibration Attributes property page is missing in the Property View. It will be restored in a future minor release.
The automatic integration of an Asset may be incomplete during use, reuse, or update of the Asset if related artifacts with abstraction or substitution links in a downstream Product Line are read-only. Workaround: Execute the automatic integration again.
Opening the VM Explorer or the VM Explorer without Customer Feature Model may lead to performance problems. This may be due to filter configurations which are set on specific explorer categories. Workaround: Customize the corresponding "VM Explorer" and "VM Explorer without Customer Feature Model" Add-ins, and remove the Explorer Filter Configurations set on the affected explorer categories.
Remote backup or migration may be terminated by a model preparation streaming error. This only affects remote backup or restore in the administration panel when the user enables model preparation. Workaround: The model preparation should be executed as an independent step on the source server. The backup or migration can then be performed.

Version 10.20

164

8 PREEvision 10.13

This chapter contains the following information:

8.1

Version numbers

8.2

Installation and compatibility information

8.3

New features in PREEvision 10.13

8.4

Changes

8.5

Configuration information

8.6

Fixed issues

Diagrams

Tables

Requirements

AUTOSAR

Diagnostics

Communication

Hardware architecture

Geometry

Product line engineering

Change and release management

Functional safety

Metrics

Collaboration

Administration

License

Server API

Backup, restore, and migration

8.7

Known issues

PREEvision 10.13
166 167 169 172 173 174 174 175 175 176 176 177 178 178 178 179 179 179 179 180 180 180 181 182

Version 10.20

165

8.1 Version numbers

Version numbers

Application PREEvision client PREEvision license server PREEvision database server PREEvision application server

Documentation

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

PREEvision 10.13
Version number 10.13.0 3.0.1 10.13.0.02 10.13.0
Version number 10.13.0 10.13.0 10.13.0 10.13.0 10.13.0

Version 10.20

166

PREEvision 10.13

8.2 Installation and compatibility information
For detailed information about the installation of PREEvision 10.13 and the migration to PREEvision 10.13, refer to the PREEvision operating manual.
For detailed information about the hardware and software requirements of PREEvision 10.13, refer to the PREEvision system requirements.

System requirements

The following system requirements have been changed:
> The recommended version of Apache Tomcat has been changed to 9.0.88.
> Amazon Corretto version 11.0.23.9.1 is provided with the PREEvision client installation. It is recommended to use this version on all server components as well.

Compatibility

Client version
10.5.0 10.6.0 10.7.0 10.8.0 10.9.0 10.10.0 10.11.0 10.12.0 10.13.0

Server version
10.5.0 10.6.0 10.7.0 10.8.0 10.9.0 10.10.0 10.11.0 10.12.0 10.13.0

Database server script version 10.5.1.41 10.6.0.02 10.7.0.02 10.8.0.02 10.9.0.03 10.10.0.03 10.11.0.03 10.12.0.02 10.13.0.02

Metamodel change ID 2022-10-05 2023-04-03 2023-06-01 2023-07-20 2023-09-18 2023-11-13 2024-01-19 2024-03-14 2024-05-06

Migration and update

PREEvision 10.0 SP17 or later can be migrated to PREEvision 10.13.
Migrating to PREEvision 10.13 is only possible from PREEvision 10.0 SP17 or later. All remote operations (backup and direct migration) available in the PREEvision 10.13 administration panel can only be performed on PREEvision 10.0 SP17 or later. Remote model preparation must be performed on PREEvision 10.0 SP18 or later. If you want to migrate a PREEvision 10.0 version before 10.0 SP17 or PREEvision 9.5, contact the Vector support.
For the migration to PREEvision 10.13, it is recommended to update PREEvision 10.0 to the latest version (service pack update), at least PREEvision 10.0 SP17, before creating a backup and starting the migration. An update of PREEvision 10.5 or one of its following minor releases, starting with version 10.6, to PREEvision 10.13 requires no migration and can be performed as minor release update.

Version 10.20

167

PREEvision 10.13
An update of PREEvision 10.5 to a following minor release, for example, PREEvision 10.13, 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 > 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".

Version 10.20

168

PREEvision 10.13

8.3 New features in PREEvision 10.13

Usability improvements for working with file attachment placeholders

Preview images of File Attachment placeholders can now be changed without navigating to preview images via a file chooser dialog. With the new context menu entry Replace Preview Image from Clipboard preview images of File Attachment placeholders can now be changed directly from the clipboard. It is also possible to paste the same image formats as before.

Usability improvements for the styles and formatting view

Multiple usability and user guidance improvements for the Styles and Formatting view have been implemented:
> Styles can now be assigned via a single click.
> The Styles and Formatting view now reacts to the selection in formatted texts and shows the applied style. If no active formatted text is edited the Styles and Formatting view is disabled.

Support of AUTOSAR 23-11

PREEvision 10.13 supports AUTOSAR 23-11 for AUTOSAR Classic and AUTOSAR Adaptive. ARXML files for AUTOSAR 23-11 can be imported and exported.

Diagnostic port

All diagnostic port interfaces for the Adaptive platform including the new interfaces from

interfaces for Adapitve AUTOSAR Release R23-11 are supported in PREEvision. The AUTOSAR Adaptive

Explorer provides dedicated tables to create and edit the diagnostic port interfaces.

Data type strategy of signal router

The signal router offers an initial creation of System Signals, Signals, System Signal Groups and Signal Groups that are derived from the software model.
The signal router considers the details of data types used in this software modeling:
> If Create System Signals is activated in the signal router options, the Unit and Computation Method is set on the System Signal.
> If Create System Signals is deactivated in the signal router options, the Computation Method is set on the Signal.
> Base Type and Bit Length are set on the Signal.
The details are selected based on the following priority:
> If there is an application data type directly assigned to the Data Element of the Sender Receiver Interface:

Version 10.20

169

PREEvision 10.13

> Priority 1: The details of the Implementation Data Type Reference are considered (Computation Method).
> Priority 2: The details of the mapped implementation data type are considered (Computation Method, Base Type).
> Priority 3: The details of the application data type are considered (Computation Method, Unit, as a fallback the Unit of the Computation Method)
> Otherwise, the directly assigned implementation data type is consider:
> Prioritiy 4: details of directly assigned implementation data type are considered (Computation Method, Base Type).

Read-write-services in diagnostics tool chain

For Diagnostic Data Identifiers, the AUTOSAR standard requests bi-directional senderreceiver ports that can both read and write. The Diagnostic Realization Explorer does now support the creation and usage of these ports.

Target range limitations Sheet Connectors can be used to visualize and relate connections across different for sheet connectors diagrams of the hardware layer. The Sheet Connector target links are displayed in
corresponding link boxes.
The range for the Sheet Connector targets can now be configured via object configuration. Thus, it is possible to limit the range of displayed Sheet Connector targets to package level, for example. Only connections in diagrams which are contained in a certain defined package are then considered and only the Sheet Connector targets for these connections are displayed in the link boxes.

Improved change identification of autolayout diagrams

For diagram-based Auto-Layout Wiring Diagrams/Auto-Layout Wiring System Diagrams and Wiring Diagrams for which auto-layout diagrams are available, a synchronicity check can be used to check whether the diagrams are still up to date.
The synchronicity can be checked via context menu on the auto-layout diagram or on the origin diagram.
For auto-layout diagrams the synchronicity with the origin diagrams can be checked.

Version 10.20

170

PREEvision 10.13
For origin diagrams the synchronicity of the corresponding auto-layout diagrams can be calculated.
The synchronicity check provides direct information on the result of the check.

Object configuration error view

The Object Configuration Error View can now be opened via the quick access in the main toolbar or select Window | Show View | Common in the main menu.
When you publish a diagram, a status is delivered in case that contained object configurations are deactivated.

Tooltips for explorer categories

Tooltips can now be defined for an Explorer Category by adding a Localization under the Explorer Category and defining a Tooltip on the Localization. You can use formatted text to define the content of the tooltip. The tooltip is displayed when moving the mouse over the category in the explorer.

Exporting files from commit history and version history

Historic versions of file artifacts can be exported from the Commit History property page and the Version History property page via the Export File... context menu.

Version 10.20

171

PREEvision 10.13

8.4 Changes

Working copies

PREEvision 10.13 no longer supports external SVN working copies:
> The Create Working Copy context menu entry has been removed from the Model View, the Test Implementation Editor, and the Test Execution Editor.
> The Working Copies view has been removed.
> The Create URL action no longer provides the possibility to create a Subversion URL.

Client-side backup, restore, and model preparation

PREEvision 10.13 no longer supports the client-side backup, restore, and model preparation.
Use the administration panel for server-side backup, restore, and model preparation.

Deprecated online check

The online check "Checksum Diagram Differences" and thus the visual labeling of outdated auto-layout Wiring Diagrams and Wiring System Diagrams is no longer supported with PREEvision 10.13.

Version 10.20

172

PREEvision 10.13

8.5 Configuration information

New metric blocks: Object selection dialog

The new Object Selection Dialog metric block opens the Select Object dialog to select an artifact or multiple artifacts from a list.
Optional inputs (Data Target Ports):
> "objectList" (data type: List<MDFObject>): List of artifacts to be displayed in the dialog.
> "overwriteSelection" (data type: List<MDFObject>): List of artifacts to be used as selected artifacts without displaying the dialog. If "overwriteSelection" is set and provides a valid list of artifacts, these artifacts are used as selection and the dialog is not displayed. If "overwriteSelection" is not set, "objectList" must be set and the dialog is displayed.
> "multiSelectionAllowed" (data type: Boolean, default: true): If set to true, multiselection is possible. If set to false, only one artifact can be selected.
Outputs (Data Source Ports):
> "selectedObjects" (data type: List<MDFObject>): Returns a list of the selected artifacts.

Changed metric utilities The library com.google.guava has been updated to version 33.0.0. This could affect metrics that use the import package com.google.common*.

Server API: get artifacts The Server API REST call for fetching multiple artifacts (GET <baseURL>/<model>/ artifacts/<xmiids>) has been changed.
Since the URL must not contain comma-characters, the comma can now be encoded with "%2C".
Example request: GET <baseURL>/EEA_MODEL/artifacts/1%2C2%2C3
The request gets the artifacts with XMIID 1,2, and 3.

Version 10.20

173

PREEvision 10.13

8.6 Fixed issues

Fixed issues in PREEvision 10.13

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

Further information

> Diagrams > Tables > Requirements > AUTOSAR > Diagnostics > Communication > Hardware architecture > Geometry > Product line engineering > Change and release management > Functional safety > Metrics > Collaboration > Administration > License > Server API > Backup, restore, and migration

8.6.1 Diagrams
ID 17938291894399295
8682711687109682050 8682711687100792081
8682711687212292039

Resolution
The default width for displaying labels of ports and pins in diagrams can be configured by means of the -DmaxDefaultLabelWidth parameter in the PREEvision initialization file PREEvision.ini. How to configure the default width is documented in the PREEvision configuration manual.
When opening diagrams, the last view and zoom level is now saved.
If an artifact in a diagram has a mapping box which displays the current mappings of the artifact, the Select Mappings dialog, opened via Show/Hide Mappings, displays these mappings as preselected. When closing the dialog, no additional mapping box is created but, instead, the current mapping box of the artifact is updated, for example, if further mappings are selected or mappings are removed.
When creating mappings via drag and drop from the Model View on a rotated figure in a diagram, the drag and drop menu is displayed at the mouse position on the rotated figure.

Version 10.20

174

PREEvision 10.13

ID 8682711687210152112
8682711686802341268, 8682711686780091843 8682711687654952083
9082947084917013042

Resolution
Inner edges of connections in diagrams can only be deleted from a diagram if both ends are connected to Sheet Connectors or to waypoints to which Sheet Connectors are attached.
Diagrams and Sections are printed on separate pages.
Diagram Configurations have been moved from the Administration Packages to new Diagram Configuration Packages of the corresponding category in the Diagram Configuration Model. Furthermore, all package structures of rules, metrics, reports, and tables in the Administration have been adapted to a new package structure.
No error is displayed if the Object Configuration Error View is not available because of insufficient rights.

8.6.2 Tables
ID 8682711687010913082 8682711687560011995 8682711685414782105
8682711686784481877

Resolution
In tables, the Show Column context menu action now also properly works for prototype columns (column categories).
The table profiler export has been enhanced by better formatting, for example, it now provides the number of columns.
To prevent long processing times, a warning dialog is displayed when you use the Select all cells action or press <Ctrl>+<A> in a table with more than 5.000 lines. In the dialog, you can cancel the action.
Table columns that display dates can now be filtered correctly with the User-defined Filter dialog.

8.6.3 Requirements
ID 8682711554181022001
8682711687494172049, 8682711687580502105

Resolution
The buttons in the toolbar of the Requirement Text Editor which are available for creating a new requirement or Customer Feature are displayed in the same order as the corresponding buttons in the individual table cells.
During the ReqIF export the conversion of formatted text containing OLE objects is properly executed.

Version 10.20

175

PREEvision 10.13

8.6.4 AUTOSAR
ID 8682711687100772052 9082947084849252051
8682711687182621998 8682711687426362069 8682711687690171024 8682711687488452014 8682711687690191024 8682711687190803013
8682711687484441045 8682711687619082003

Resolution
AUTOSAR software component description: Triggers and Trigger Interfaces are properly exported.
AUTOSAR export: For the AUTOSAR ECU extract, AUTOSAR software component description, and the AUTOSAR system description, the propagation of Data Type Unit Groups has changed. Now only directly used Data Type Unit Groups are propagated and thus also exported with all their grouped Data Type Units. Data Type Unit Groups are no longer propagated by used Data Type Units.
AUTOSAR export: An erroneous fallback has been removed which determined the parent of an ECU Interface according to the sent / received Frame Transmissions.
AUTOSAR import: For an AUTOSAR import from folder containing files with duplicate UUIDs, inconsistency checks are supported.
AUTOSAR import: The import of several artifacts belonging to the AUTOSAR Adaptive Platform, and which have a long name in AUTOSAR but have no long name in PREEvision is now possible.
AUTOSAR Adaptive export: The AUTOSAR service interface description does not export the attribute Is Service for Adaptive diagnostic interfaces.
AUTOSAR Adaptive Explorer: In the Service Interface Editor a new table column Namespace has been added.
The AUTOSAR consistency check "AR_010805b_ARC_430_constr1043_ReceiverComSpe c_ invalid_Interface" no longer incorrectly indicates an error if a Sender-Receiver Delegation Port Type is involved.
The AUTOSAR consistency check "c1044_ReceiverComSpec_with_wrong_DataFilterType" has been corrected to precisely check the AUTOSAR constraint constr_1044.
AUTOSAR consistency checks which check AUTOSAR compatible naming have been unified and improved.

8.6.5 Diagnostics
ID 8682711686352872108

Resolution
Diagnostic export: If a diagnostic exchange export is started on a Diagnostic Master referencing application data types or base types with a bit length = 0 or -not set- an export warning is reported in the Information View.

Version 10.20

176

PREEvision 10.13

ID 8682711687400932005
8682711687639892113

Resolution
Diagnostic export: The diagnostic export is possible via software realization for a Diagnostic Master, even if the collected diagnostic artifacts are located below another Diagnostic Master.
Diagnostic export: Diagnostic Events without correctly modeled Diagnostic Trouble Codes cannot be exported correctly, and therefore the export is canceled with an error.

8.6.6 Communication
ID 8682711687123261840 8682711687359821029
8682711687359351029
8682711687400901029
8682711687711571030 8682711687288031029 8682711687420602004 8682711686804291909 8682711687359381029

Resolution
Signal router: The signal router wizard not only displays existing Software Deployment Packages but also Software Deployments of the current Product Line.
Signal router: During the initial creation of Signals, the Computation Method of the software modeling is taken over to the created System Signal, if available, or the Signal. If several Computation Methods are modeled, the one with the highest priority according to AUTOSAR is considered.
Signal router initial Signal creation: If there is only an implementation data type assigned to the Data Element, the Base Type and Computation Method of this implementation data type are assigned to the created System Signal (only Computation Method) and Signal.
Signal router: During the initial creation of Signals and Signal Groups, details like Computation Method and Base Type are taken over from a mapped implementation data type structure even if the application data type structure is considered for the creation of the Signal Group.
Frame-PDU synthesis: The frame-PDU synthesis now assigns the Signal Transmission of the multiplexor signal to all PDU Transmissions of the Signal IPDUs belonging to the Dynamic Part Alternatives of a Multiplexed IPDU.
DBC export: The Base Type of a Signal is exported even if no implementation data type is assigned. If no Base Type is assigned to a Signal, the Base Type of the assigned implementation data type is used.
DBC export: The DBC export exports the Computation Method of the System Signal if no Computation Method is assigned to the ISignal.
A DBC-specific translation between send types in DBC and send modes in PREEvision has been documented in the PREEvision user manual.
Signal Receiver Attributes can now be correctly created under CAN Signal Transmissions via the context menu.

Version 10.20

177

PREEvision 10.13

Resolution

Additionally, the Property View for Signal Receiver Attribute and Frame Sender Attribute is enhanced to display the referenced CAN ECU Interface. In the Property View of a CAN ECU Interface, the tables on the Received/Sent Communication Attributes property page have been corrected, and the page is now placed below the Signal Receiver Attributes page.

8.6.7 Hardware architecture

ID 8682711687500591912 8682711687290002081 8682711687084141037
8682711687223651029

Resolution
In the Property View of a Pin Type or Pin Type Family, a table is added on the Applicable Types property page. This table displays the Cavity Types to which the Pin Type or Pin Type Family is assigned.
The refactoring Swap Wires on a Schematic Pin of an inline connector in a Wiring Diagram locks the Wiring Diagram where the refactoring is executed.
The range for the Sheet Connector targets displayed in a diagram can now be configured via metric in the object configuration of the diagram. Thus, it is possible to limit the range of displayed Sheet Connector targets to package level, for example, to Wiring Harness.
A new Application Double Type has been added to the global Library to resolve the dependencies between the "Wiring Harness Demo Model" Product Line in the PREEvision demo model and the global Administration.

8.6.8 Geometry
ID 8682711687061311843

Resolution
In a Geometry Diagram, the mapping boxes for mapping assignments to Connector Locations can be moved again, especially for rotated figures.

8.6.9 Product line engineering

ID 8682711687471372159
8682711687643853126

Resolution
The performance for the Asset update (replace with version) has been improved by removing misleading and unnecessary log entries and by improving the calculation of invisible artifacts during the Asset update.
The performance for retrieving historical versions of Assets during an Asset update with historical version has been improved.

Version 10.20

178

PREEvision 10.13

8.6.10 Change and release management

ID 8682711686958612034
8682711686361112052

Resolution
When displaying a historic version of a Source Code in the Change history view, the code can be copied from the Value column of the Change history view and pasted correctly into an external editor without changing its content (like removing HTML code).
The Merge drag and drop action works for the following configurations: "keep identity of the target and replace all data", "keep identity of the target and data of the source has higher priority", and "keep identity of the source and data of the target has higher priority".

8.6.11 Functional safety
ID 8682711687273842079

Resolution
In the demo model, the instances of the HW Failure Data Editor tables have been replaced with table proxies.

8.6.12 Metrics
ID 8682711687273562112
8682711687329312112

Resolution
The metric blocks Reset Labels in Diagrams and Update Labels in Diagrams now check all parts of a Schematic Connection.
A NullPointerException that occurred when selecting artifacts in Metric Diagrams with internal loop ports without assigned Internal Loop has been fixed.

8.6.13 Collaboration
ID 8682711687353742112
8682711687363422068
8682711687077021995 8682711555203353013

Resolution
The model is completely loaded after a server restart. In PREEvision 10.11 or lower it may happen in rare cases, that the model is loaded incompletely after a server restart.
The Check-out view shows the correct cause for the check-out when an artifact has multiple causes for the check-out.
A performance problem that occurred during the update of the Model View has been resolved.
Executing Undo all own Locks no longer leads to a client freeze.

Version 10.20

179

PREEvision 10.13

8.6.14 Administration
ID 8682711687004822024
8682711687171812203 8682711687637102068 8682711687185073046 8682711687257211790

Resolution
To improve robustness, the evaluation of role constraints has been adjusted in the roles and rights management: > Transition Authorizations on Lifecycle Transitions are
ignored if they reference no Role. > Lifecycle State Authorizations on Lifecycle States
that restrict the target state visibility based on user roles are ignored if they reference no Role.
All snapshots of the monitoring infrastructure services are stored in a single snapshot folder within the installation folder.
To avoid errors, Add-ins with the branch suffix of the target model can no longer be installed.
When the authority cache is initialized, no RefuseObjectChange listeners are informed.
When manually transitioning between Lifecycle States, the Progress Information dialog box opens earlier, preventing PREEvision from freezing.

8.6.15 License
ID 8682711687362001994

Resolution
Creating and deleting license users no longer leads to an issue where user assignments to a named user license could exceed the license's quantity.

8.6.16 Server API
ID 8682711687361242076

Resolution
The Server API REST call for fetching multiple artifacts (GET <baseURL>/<model>/artifacts/<xmiids>) has been changed. Since the URL must not contain comma-characters, the comma can now be encoded with "%2C". Example request:
GET <baseURL>/EEA_MODEL/artifacts/ 1%2C2%2C3 The request gets the artifacts with XMIID 1,2, and 3.

Version 10.20

180

PREEvision 10.13

8.6.17 Backup, restore, and migration

ID 8682711687278441036

Resolution
Check-in state errors are detected during the remote model preparation. The remote model preparation must be performed on PREEvision 10.0 SP18 or later.

Version 10.20

181

PREEvision 10.13

8.7 Known issues

Known issues in PREEvision 10.13

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

ID 17938307791212069
8682711552649222003 8682711555165912106 8682711555133422025 8682711686247202025
8682711686179212044

Known issue
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.
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.
ReqIF export: For empty attributes, the string defined in the Text for empty Labels property is exported instead of and empty string. By default, this is "---". Workaround: In the Preferences, under PREEvision | General, remove all characters from the Text for empty Labels property.
<Ctrl> + click on a preview image in a formatted text may not open the linked File Attachment. Workaround: Use the context menu on the preview image or double click on the File Attachment artifact in the Model View to open the file attachment.
When inserting a diagram placeholder based on templates, an error message is reported that the used template is incomplete. Workaround:
1. Navigate to the selected template under Administration | Configuration File Container | Report Template Package and select the affected template file.
2. Open the location of the file in the Windows Explorer and delete the file.
3. Update from the server to force a reload of the file.
When generating a report for a diagram as PDF, an error message is reported that the report generation was not able to write any data in the Temp directory and is aborted. Workaround:
1. Navigate to the report under Administration | Report Model and select the report file.

Version 10.20

182

PREEvision 10.13

ID 8682711687075110069 8682711555191801873
8682711685521992014 8682711687441283013
8682711687181061868

Known issue
2. Open the location of the file in the Windows Explorer and delete the file.
3. Update from the server to force a reload of the file.
The state of expanded artifacts in tables is not reliably restored after a refresh (<F5>).
During reinitialization of the authority model an error message may be displayed reporting an unexpected error with the ramc.ser file. Workaround:
1. Delete the authority model.
2. Connect to the authority model.
3. Initialize the authority model.
For Application Curve Types and Application Cube Types, the Calibration Attributes property page is missing in the Property View. It will be restored in a future minor release.
The diagnostic export can currently not handle situations, where an interface, that is used for a software realization of a diagnostic object, is additionally assigned to another port in the same ECU. The diagnostic object will nevertheless be exported, but the details might not be available. Workaround: Interfaces should be used exclusively for diagnostic objects and their diagnostic ports. For other ports, please use a duplicate of the original interface, or remove other interface assignments temporarily during the diagnostic export.
The automatic integration of an Asset may be incomplete during use, reuse, or update of the Asset if related artifacts with abstraction or substitution links in a downstream Product Line are read-only. Workaround: Execute the automatic integration again.

Version 10.20

183

9 PREEvision 10.12

This chapter contains the following information:

9.1

Version numbers

9.2

Installation and compatibility information

9.3

New features in PREEvision 10.12

9.4

Changes

9.5

Configuration information

9.6

Fixed issues

Diagrams

Tables

Requirements

Logical function architecture

AUTOSAR

Diagnostics

Communication

Hardware architecture

Product line engineering

Change and release management

Variant management

Test engineering and test management

Rules

Metrics

Reports

Collaboration

Administration

Installation

9.7

Known issues

PREEvision 10.12
185 186 188 193 194 196 196 197 198 198 199 200 200 200 201 202 202 202 202 203 203 203 204 205 206

Version 10.20

184

9.1 Version numbers

Version numbers

Application PREEvision client PREEvision license server PREEvision database server PREEvision application server

Documentation

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

PREEvision 10.12
Version number 10.12.0 3.0.1 10.12.0.02 10.12.0
Version number 10.12.0 10.12.0 10.12.0 10.12.0 10.12.0

Version 10.20

185

PREEvision 10.12

9.2 Installation and compatibility information
For detailed information about the installation of PREEvision 10.12 and the migration to PREEvision 10.12, refer to the PREEvision operating manual.
For detailed information about the hardware and software requirements of PREEvision 10.12, refer to the PREEvision system requirements.

System requirements

The following system requirements have been changed:
> Client requirements: The requirements for the client and for the administration client are documented in a common chapter "Client requirements".

Compatibility

Client version
10.5.0 10.6.0 10.7.0 10.8.0 10.9.0 10.10.0 10.11.0 10.12.0

Server version
10.5.0 10.6.0 10.7.0 10.8.0 10.9.0 10.10.0 10.11.0 10.12.0

Database server script version 10.5.1.41 10.6.0.02 10.7.0.02 10.8.0.02 10.9.0.03 10.10.0.03 10.11.0.03 10.12.0.02

Metamodel change ID 2022-10-05 2023-04-03 2023-06-01 2023-07-20 2023-09-18 2023-11-13 2024-01-19 2024-03-14

Migration and update

PREEvision 10.0 SP17 or later can be migrated to PREEvision 10.12.
Migrating to PREEvision 10.12 is only possible from PREEvision 10.0 SP17 or later. Also, all remote operations (model preparation, backup, direct migration) available in the PREEvision 10.12 administration panel can only be performed on PREEvision 10.0 SP17 or later.
If you want to migrate a PREEvision 10.0 version before 10.0 SP17 or PREEvision 9.5, contact the Vector support.
For the migration to PREEvision 10.12, it is recommended to update PREEvision 10.0 to the latest version (service pack update), at least PREEvision 10.0 SP17, before creating a backup and starting the migration.
An update of PREEvision 10.5 or one of its following minor releases, starting with version 10.6, to PREEvision 10.12 requires no migration and can be performed as minor release update.
An update of PREEvision 10.5 to a following minor release, for example, PREEvision 10.12, requires no update of licenses. PREEvision 10.5 licenses are used for the minor releases following PREEvision 10.5.

Version 10.20

186

PREEvision 10.12
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 > 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".

Version 10.20

187

PREEvision 10.12

9.3 New features in PREEvision 10.12

Automated import of test execution reports

The test data management toolchain provides test data exchange between PREEvision and test design tools, for example vTESTstudio or CANoe.DiVa, and test execution tools, for example CANoe.
Test runs from test execution tools previously had to be imported manually. With PREEvision 10.12 an automated import of test execution reports is supported by the Test Execution Importer metric block. The execution of this metric block can be automated via Apache Ant scripts.

An import from CANoe is supported out of the box. An import from third party tools is possible by customizing.

Extensions for signalto-service mappings

The Platform Interface Mapping Design editor has been enhanced to simplify the mapping signals of signal-based platforms to interface elements like events of serviceoriented platforms.

Also, for AUTOSAR 22-11, the handling for Fire And Forget Methods has been adapted.

Version 10.20

188

PREEvision 10.12
Diagnostic interfaces 19 different diagnostic port interfaces defined by AUTOSAR Adaptive are introduced. The for AUTOSAR Adaptive new artifacts can be created and edited in the Model View and Property View.

Export of service interface catalog

You can import and export the new diagnostic interfaces as SW Cluster Design Description. When exporting in AUTOSAR version 20-11, the required service dependency structures are generated.
New AUTOSAR Adaptive exports allow the exchange of service interfaces: > The AUTOSAR Service Interface Design Description exports one Service Interface
without deployment details. > The AUTOSAR Service Interface Design Catalog exports a catalog of Service
Interfaces without deployment details.

Usability improvements Initial values for the calibration data types Application Curve Type and Application Map

for calibration

Type can easily be set in a dedicated dialog. Also, their axes can be initialized. When

parameters

opening the dialog, all required artifacts are created automatically in the background.

Version 10.20

189

PREEvision 10.12
Additional properties of the relevant data type are provided in an expandable section. The Set Values dialog can be opened in the Property View and in tables.

Improvements for the show owning component action

The Show Owning Component action, which can be used on a Schematic Pin to display the inline connector of the Schematic Pin, has been improved. In case a pin cannot be inserted into the corresponding inline connector, an appropriate information is reported in the Information View. Additionally, the location of the inline connector sides A and B is now based on the orientation of the first selected pin. The location is independent of the defined representation of the connector sides in the preferences.

Evaluation of diagram contents and diagram refactorings

Diagram refactorings, for example the conversion of an Electric Circuit Diagram into a Wiring Diagram, access diagram data. When converting diagrams, diagram repair and update mechanisms are processed prior to the conversion, which ensures that the state of the diagram remains up to date. This applies to manually triggered refactorings as well as to refactorings via metric functions.
All diagram refactorings are affected by these new mechanisms:
> Conversion into and from system diagrams
> Refactorings across model layers, for example, the conversion of an Electric Circuit Diagram into a Wiring Diagram
> Creation of diagram-based auto-layout Wiring Diagrams or Wiring System Diagrams
The created diagrams are opened by default after creation. For the corresponding metric blocks there is the possibility to close diagrams after the creation. This is useful especially when multiple diagrams are processed.
During a refactoring for multiple diagrams, a Progress Information dialog is displayed. The refactoring can be canceled, for example, if diagrams display errors or are out-ofscope.

Rotation of figures in diagrams

In addition to text objects which can already be rotated in diagrams, it is now possible to also rotate the following objects:
> frame
> ellipse

Version 10.20

190

> picture

PREEvision 10.12

New object

Defective object configurations are hard to find and lead to many disturbing error dialogs

configuration error view when modeling.

Instead of displaying error dialogs, a new Object Configuration Error View has been implemented, which displays defective object configurations based on rules or metrics.

For the Add-in installation, for example, this ensures a smoother installation process without disturbing error dialogs.

Improvements for lifecycles

The check sequence for Life Cycle constraints has been optimized. Also, the performance for complex lifecycle scenarios with Life Cycle Transition Authorizations has been increased.
Lifecycle constraints are evaluated in the following order:
> Evaluate Life Cycle Transition Authorization first:
> If the Life Cycle Transition Authorization status >= Error, no further constraint types for this Life Cycle Transition are evaluated.
> If the Life Cycle Transition Authorization status < Error, the evaluation of all remaining constraint types continues. The status of all constraints (the highest status/severity level) are merged.

Version 10.20

191

PREEvision 10.12
> The resulting status/severity level of the Life Cycle Transition constraints determines if the transition is executed.

Version 10.20

192

PREEvision 10.12

9.4 Changes

Deprecated online check

The online check "Checksum Diagram Differences" and thus the visual labeling of outdated auto-layout Wiring Diagrams and Wiring System Diagrams will no longer be supported with PREEvision 10.13.

Version 10.20

193

PREEvision 10.12

9.5 Configuration information

New metric blocks: Test Execution Importer

The Test Execution Importer metric block imports one or more Test Runs and Test Case Runs based on a test protocol from a test execution tool like CANoe. To establish the traceability, the imported Test Case Runs are linked with the artifacts from the corresponding test implementation step.
Required inputs (Data Target Ports):
> "testProtocol" (data type: String): Path to file on the file system. Test protocol of a test execution tool (for example, CANoe) containing test verdicts.
> "destinationTestTask" (data type: MTestTask): Test Task artifact to which the resulting Test Runs are imported to.
Optional inputs (Data Target Ports):
> "userDefinedXSLTFile" (data type: String): Path to an XSL transformation file on the file system in which the mapping between the test execution tool and the PREEvision model is defined. Default: CANoeReport2ExecutionTraceabilityReport.xslt
Outputs (Data Source Ports):
> "testRuns" (data type: MTestRun, MTestCaseRun)

Changed metric blocks

The following Data Target Port has been added to the Create Electric Circuit System Diagram metric block, the Create Electric Circuit System Diagram metric block, and the Create Wiring Diagram metric block:
> "closeEditorAfterCalculation" (optional, data type: Boolean): Closes the tab of the created diagram. In case of creating multiple diagrams, you do not have to manually close multiple tabs. Default: false

The ports of the Create Diagram-Based Auto-Layout Wiring (System) Diagram metric block have been renamed: > "Origin Wiring Diagram" renamed to "originWiringDiagram" > "Package" renamed to "package" > "Diagram Configuration" renamed to "diagramConfiguration" > "scaling x-coordinate" renamed to "scalingXCoordinate" > "scaling y-coordinate" renamed to "scalingYCoordinate" > "Component Height" renamed to "componentHeight" > "Minimal Label Distance" renamed to "minimalLabelDistance" > "Close editor after calculation" renamed to "closeEditorAfterCalculation" > "template Diagrams" renamed to "templateDiagrams" > "Close Range Top" renamed to "closeRangeTop" > "Close Range Mid" renamed to "closeRangeMid" > "Close Range Bottom" renamed to "closeRangeBottom" > "Use Calculated Section Height as Fallback" renamed to
"useCalculatedSectionHeightAsFallback" > "Show Coordinate System" renamed to "showCoordinateSystem" > "Result" renamed to "result" > "Diagram" renamed to "diagram"

Version 10.20

194

PREEvision 10.12
The ports of the Create Model-Based Auto-Layout Wiring (System) Diagram metric block have been renamed: > "Input Artifact Collection" renamed to "inputArtifactCollection" > "Top Components" renamed to " topComponents" > "Diagram Class" renamed to "diagramClass" > "template Diagrams" renamed to "templateDiagrams" > "Package" renamed to "package" > "AutoLayout Origin" renamed to "autoLayoutOrigin" > "Diagram Configuration" renamed to "diagramConfiguration" > "scaling x-coordinate" renamed to "scalingXCoordinate" > "scaling y-coordinate" renamed to "scalingYCoordinate" > "Component Height" renamed to "componentHeight" > "Minimal Label Distance" renamed to "minimalLabelDistance" > "Close Range Top" renamed to "closeRangeTop" > "Close Range Mid" renamed to "closeRangeMid" > "Close Range Bottom" renamed to "closeRangeBottom" > "Use Calculated Section Height as Fallback" renamed to
"useCalculatedSectionHeightAsFallback" > "Show Coordinate System" renamed to "showCoordinateSystem" > "closeEditorAfterCalculation" renamed to "closeEditorAfterCalculation" > "Result" renamed to "result" > "Diagram" renamed to "diagram"
Deleted metric blocks The following metric block is no longer supported with PREEvision 10.12: > Prepare Transport Product Line

Version 10.20

195

PREEvision 10.12

9.6 Fixed issues

Fixed issues in PREEvision 10.12

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

Further information

> Diagrams > Tables > Requirements > Logical function architecture > AUTOSAR > Diagnostics > Communication > Hardware architecture > Product line engineering > Change and release management > Variant management > Test engineering and test management > Rules > Metrics > Reports > Collaboration > Administration > Installation

9.6.1 Diagrams
ID 8682711552015411912
8682711686736422042 8682711686971162072 17938308170242112

Resolution
In addition to text objects, the following objects in the Documentation diagram palette can be rotated in diagrams:
> frame
> ellipse
> picture
When disabling the Automatic figure completion for the current diagram via the corresponding button in the diagram toolbar, the disabled state is persisted even after a commit.
In the Property View of a Diagram Configuration, an information icon is added for the Legend and Master Diagram on the General property page to inform the user that changes may influence existing diagrams.
Diagram refactorings as well as the Diagram Artifacts Collector block consider the current state of the model instead of using the persisted state of diagrams.

Version 10.20

196

PREEvision 10.12

ID 8682711686887712081
8682711686852223090
8682711687223483077 8682711687267181204 8682711687210142112
8682711686960432041

Resolution
For a Diagram File created, for example via the Publish function for a diagram, the Diagram Configuration is persisted and cannot be changed. In the Property View of a Diagram Configuration on the property page Diagram File, the Configured Diagram Files table is read-only to prevent unwanted changes.
For tables in diagrams, it is not possible to set the scaling factor below 0.1 (10 percent) anymore, which prevented the proper diagram export as PDF. This refers to manually resizing a table as well as setting the scaling factor via the object configuration. If in the object configuration, the Table Scaling Factor for diagram tables is set below 0.1, the value is automatically changed to 1.0.
An error while exporting diagrams within a report has been resolved. The content of the diagram is printed correctly.
If the graphical representation of an artifact is not copyable, for example of a Concept Space (SpiderWebAxisGraphNode), the Copy context menu entry is not available.
If an edge of a connection with a label is deleted in a diagram, the label is moved to another edge of the same connection if possible. Labels are only moved if the same label is not already displayed on the other edge. Labels are not moved to edges that are only connected via Sheet Connectors to the deleted edge.
Trying to refresh a table during printing of a diagram will not result in the table missing in the printed file anymore.

9.6.2 Tables
ID 8682711686866022102 8682711687198632107
8682711687199292107 8682711687003202112

Resolution
Configured display names are properly displayed in tables.
Faulty Table Proxys no longer prevent that the Explorer Proxy in which they are referenced cannot be opened. Faulty Table Proxys that are not locked or checked-out are automatically deleted when an Explorer Proxy is opened. The Lock dialog is suppressed when faulty Table Proxys are automatically deleted. The Information View lists the deleted Table Proxys.
Tables of Combined Table Based Editor Proxys are displayed in the same order as defined in the table template.
In Combined Table Based Editors, the selection-sensitive table is now always visible, even if the selection-sensitive table is without content, or if a filter results in an empty table.

Version 10.20

197

PREEvision 10.12

ID 8682711687212392112
8682711687210792106 8682711687178783082 8682711687067713104

Resolution
An issue has been fixed that caused a deadlock when selecting newly created artifacts and closing the table in which they were created.
After refreshing the opened formatted text editor of a table cell, the selection propagation works properly.
Deactivating the Show empty values option of a predefined column filter properly filters empty values.
If a Query Rule Group is used to obtain the root artifacts of an Explorer category, sort and filter settings of the Query Rule Group, such as filtering duplicates, are correctly applied.

9.6.3 Requirements
ID 8682711687041922105
8682711684910072105
17938308052811030 8682711687107801839
8682711686866012105 8682711554028422106

Resolution
Unnecessary messages of report generation in the Information View during the review and vote ReqIF export have been suppressed.
After executing the Check Images/OLEs for Default Settings in Formatted Texts check, formatted text can be opened from within the Information View and edited without any problems.
Updating ReqIF imports can now change the subclass of a requirement.
LibreOffice has been updated to ensure that LibreOffice is working properly when the Windows Temp folder is cleaned while PREEvision is running.
During ReqIF export of a test specification no ReqIF schema validation errors occur anymore.
Requirement specifications with a large number of artifacts (over 20k) can be opened in the Requirement Text Editor within less than one minute.

9.6.4 Logical function architecture

ID 8682711686736582042
8682711686736412042

Resolution
When using the expand function, fan waypoints in a Logical Architecture Diagram are moved correctly, if the reference line intersects the port orthogonally (is not aligned with the port orientation).
Activity Chains can be resized in each direction, when using reference lines to create additional space.

Version 10.20

198

PREEvision 10.12

9.6.5 AUTOSAR
ID 8682711686580002052 8682711687210271804 8682711687277161998 8682711687024541917 8682711686925361807 8682711687160602052 8682711684984602052
8682711686550401914
8682711686846442108 8682711687074972108 8682711687187162108

Resolution
AUTOSAR export: The export works for Operation Arguments with assigned Implementation Union Types.
AUTOSAR export: A new consistency check has been added that checks if an Operation Argument has an initial value set. If an Operation Argument is linked to an initial value, the AUTOSAR export aborts with a fatal error.
AUTOSAR ECU extract: New consistency checks verify Bus Systems of communication channels for CAN, FlexRay, and LIN.
AUTOSAR import: An error message and an entry in the Information View indicate if the AUTOSAR file contains artifacts with duplicated UUIDs or duplicated short names.
AUTOSAR ECU extract: For pure gateways, SecOcCryptoServiceMappings are only exported, if an EcuInterface or PduPort regarding the extracting ECU sends or receives the payload PDU.
Fixed a problem where the AUTOSAR import created two Root Ports for a port type due to a wrongly calculated transformation ID within the transformation.
AUTOSAR software component update: If the DataConstrs in an AUTOSAR file have no ID, a deterministic ID will be generated based on the name of the DataConstr and the UUID or path of the parent. This generated ID will be used to merge the artifacts.
The consistency check "p1169_VirtualPackagePart_without_VirtualPackage" no longer hits for diagrams, Conventional Connectors, Conventional Connections, and artifacts belonging to the Logical Function Architecture. The consistency check now also hits for artifacts included in Product Lines that do not define a Virtual Package Root. The severity of the consistency check was changed from "Error" to "Warning" and the description was updated to reflect this change.
When setting an initial value for an enumeration using the value handling configuration the symbol attribute is set as well.
When using the value handling mechanism, existing value specifications referenced by multiple objects are now cloned properly according to the defined Value Handling Mode in the Value Handling Configuration.
AUTOSAR consistency check: It is not allowed that a TransformationComSpecProps is added under a SenderCommunicationSpecification. If this pattern is modeled, a consistency check indicates this invalid configuration.

Version 10.20

199

PREEvision 10.12

9.6.6 Diagnostics
ID 8682711687278572113
8682711687287322113

Resolution
Diagnostic export: When modeling diagnostics together with its realization in software, only diagnostic artifacts that are directly assigned to a software port are considered during export.
Diagnostic export: A clear error message informs, if initial values cannot be exported because they are used in the context of different data types.

9.6.7 Communication
ID 8682711553300091029
8682711686527141998
8682711686976312050
8682711687049672004 8682711686994871915 8682711686925932052
8682711554636272051

Resolution
For length calculation of communication artifacts, the length of a transformer is added to the signal length instead of the PDU length.
The data type of the attribute Data ID of End To End Transformation Properties has been changed from integer to long to support full range of possible values.
The communication path router aborts and provides helpful hints in the Information View if communication artifacts, like Coupling Ports, are missing.
The signal router creates Network Endpoints for all Ethernet use cases.
The consistency rule "ARC422_MultiCastMACNotValid" accepts MAC addresses using lower-case hex digits.
The refactoring to automatically connect ports uses existing Assembly connections only when all containing ports match the requirements for a valid connection.
The attribute Bit Length of Signal Groups is removed from the Property View. The attribute is not necessary for modeling.

9.6.8 Hardware architecture

ID 8682711686746941037
8682711686697532196

Resolution
Artifacts, for example a Schematic Pin at an ECU in an Electric Circuit Diagram, located inside a Section of a diagram can be moved at the containing component.
If a diagram is opened (not locked), model operations, which were caused, for example, by the wiring harness router or modeling in a different diagram, may change artifacts in the opened diagram. Carrying out an undo operation does not close the PREEvision client anymore.

Version 10.20

200

PREEvision 10.12

ID 8682711686802102101 17938307945862046
8682711686960452081 8682711687210251843

Resolution
KBL export: Special characters defined for artifact attributes, for example, Name, Alias Name, or ID are properly exported to KBL. Only characters required by the XML specification (&, <, >, ", ') are now escaped.
The refactoring of a Wiring System Diagram on an Electric Circuit Diagram via the Create WH System Diagram metric block displays the correct Headers and Pins in the Wiring System Diagram after a prior substitution of Headers in the Electric Circuit Diagram.
Hardware Devices in Wiring Diagrams, Electric Circuit Diagrams, and their corresponding system diagrams, are now correctly displayed according to their Hardware Device Template Diagram even if they are rotated.
In a Component System Diagram mapping box entries for mappings to a Basic Software are properly displayed.

9.6.9 Product line engineering

ID 8682711687091221995
8682711687210641995
8682711687211022082 8682711687191081995 8682711687194422082 8682711687207971868

Resolution
The automatic integration of an Asset is properly executed during use, reuse, or update of the Asset if related artifacts with abstraction or substitution links in a downstream Product Line are invisible or out-of-scope. Such specific relations are ignored for the integration by means of a configurable filter. You may contact the customer service for further support.
After an integration merge of an Asset with multi type-of types but without the merge of the corresponding instances (still unintegrated or integrated via move,) a commit is properly executed.
After revoking an Asset with multi type-of types, no outof-sync problems occur for the corresponding instances.
An Asset is properly updated in case the artifacts to be updated have invisible or out-of-scope relations.
An Asset is properly updated in case the artifacts to be updated are reused in a Product Line which is invisible due to missing rights.
An Asset with structural type-of (STO) artifacts is properly updated in case the STO artifacts to be updated are reused in a Product Line which is invisible due to missing rights.

Version 10.20

201

PREEvision 10.12

9.6.10 Change and release management

ID 8682711684953342106, 8682711686453692023 8682711687036562101
8682711554021822106 8682711554180702001

Resolution
When comparing formatted texts in the Property View of the Compare perspective, it is now possible to click into the read-only formatted text field.
When Custom Attributes are defined as a trigger for a Change Profile, the meta class of the owner artifact is now considered.
Review and vote: Copy and paste of comments in review and vote tables can be carried out properly.
Review and vote: In review and vote tables and the Requirement Text Editor, comments can be created via double click in the corresponding table cell.

9.6.11 Variant management

ID 8682711686868632002

Resolution
Sets, documentation artifacts and conditions can be copied from one and pasted into another Variant Diagram.

9.6.12 Test engineering and test management

ID 8682711554818603108

Resolution
An import from vTESTstudio or CANoe is properly executed even if the web application name of a PREEvision project contains a "/" character.

9.6.13 Rules
ID 8682711686939142181 8682711554430282023
8682711687100033042 8682711686901672101

Resolution
Multi Classifier Objects in Consistency Rules and Query Rules now support Framework Links.
The Query Rule Group property page of a Query Rule shows the immediate parent of a Query Rule Group which provides a convenient way to analyze the contents of an obsolete Add-in.
The performance of executing consistency checks via metric has been improved.
An Excel export of the Consistency Check Results view is now possible even if the number of findings exceeds the limit defined in the Preferences.

Version 10.20

202

PREEvision 10.12

9.6.14 Metrics
ID 8682711687195292102
8682711687067261027

Resolution
If metrics are automatically executed via Ant-scripts, undo all locks is executed on disconnect. This prevents locks by technical users which can only be reset by an administrator.
When using the ReuseUnitDeleteHelper.deleteObjectsWithSTO SyncIfNeeded() method in a metric, the subsequent commit properly works.

9.6.15 Reports
ID 8682711686425902046 8682711686737142105
8682711687036721992

Resolution
Many consecutively inserted diagrams with a specific page layout are now properly inserted in reports.
Multiple Query Contexts can be inserted in a report directly next to each other without spaces or other characters in between them.
Sections can be included as diagram placeholders in reports again.

9.6.16 Collaboration
ID 8682711687176861856
8682711686976392024
8682711687298082068
8682711687024181995, 8682711687272223013, 8682711687195423013, 8682711687407143013, 8682711687074822051, 8682711687044981995 8682711687076982203

Resolution
Sending an e-mail during a life cycle transition properly works if the SendMail action is triggered in a Delegate Calculation metric block.
An issue has been fixed where branch names were missing after an update of the model in the client. If the branch name of an artifact is changed and then checkedin and checked-out, other users may observe that the new branch name is missing after an update of the model in PREEvision 10.11 or lower. An update to 10.12 is therefore recommended.
To improve performance, the Checkout dialog shows a maximum of 1.000 artifacts.
Model View updates caused by model updates with a large number of artifacts no longer block the user interface.
If the certificate validation in the connection between client and server is activated, no unnecessary additional connections are now established between client and server.

Version 10.20

203

PREEvision 10.12

ID 8682711686983681993, 8682711687003681806, 8682711687160502099 8682711687040322076
8682711686587422054
8682711687353742112

Resolution
The server model cache remains valid even if the application server system is rebooted.
The startup of the application server has been improved, loading the model has been optimized.
An issue has been fixed that caused expensive and unnecessary update cache calculations on the application server.
A problem when loading the model after a server restart has been solved. In PREEvision 10.11 or lower it may happen in rare cases, that the model is loaded incompletely after a server restart. This then leads to several problems for users. An update to 10.12 is therefore recommended.

9.6.17 Administration
ID 8682711687065662203 8682711686548902054 8682711687006061808 8682711554206562068
8682711686232042039 8682711686983371806 8682711687210541914

Resolution
Optional Tomcat JDBC Connection Pool parameters have been removed from the vCollab default configuration, since these parameters could lead to malfunctioning database connectivity.
The "Long-running test" of the function and performance test now uses larger datasets of 15.000 artifacts to improve the comparability of the measured values.
Server-side logging of database errors is now provided when deleting models via the administration panel.
Errors caused by calculating a metric or rule which is part of an object configuration do not cause the continuous occurrence of error message dialogs anymore. Instead, such kind of errors are reported in the Object Configuration Error View. Only the first invocation of an affected object configuration is displayed in the view. For the Add-in installation, for example, this ensures a smoother installation process without disturbing error dialogs.
Custom metric hooks are disabled during Add-in installation.
The Compile metrics when creating an add-in delivery file option, which should not be used in production use cases, has been removed from the Addins preferences.
Add-in installation is rolled back if installed/updated rules or utilities that are executable in the source model are not executable in the target model at the end of the installation process.

Version 10.20

204

PREEvision 10.12

ID 8682711687277382050
8682711686537692102

Resolution
The Add-in Artifacts without Branch Suffix table now produces the same results as the existing check performed during Add-in delivery.
When a table with an Outline Table is assigned as a core artifact to an Add-in, all components of the Outline Table are now propagated in addition to the Outline Table itself.

9.6.18 Installation
ID 8682711687085682017
8682711687203802017, 8682711687190811993 8682711687160731893 8682711687048581895

Resolution
In the preconfigured Tomcats, the setenv.bat and setenv.sh files have been restructured to match the technical areas. The following options are moved from the environment variable CATALINA_OPTS to JAVA_OPTS to be available during the Tomcat shutdown process:
set JAVA_OPTS=%JAVA_OPTS% Dhttp.shutdown.port=[[VCOLLAB.HTTP.SHUTDO WN.PORT]] set JAVA_OPTS=%JAVA_OPTS% Xverify:none set JAVA_OPTS=%JAVA_OPTS% Djdk.util.zip.disableZip64ExtraFieldValid ation=true set JAVA_OPTS=%JAVA_OPTS% XX:ErrorFile=%CATALINA_BASE% \logs\hs_err_pid%%p.log
In the setenv.bat and setenv.sh files of the preconfigured Tomcats, only one parameter is set per line.
During the build of the vCollabAPI application, the deploy property vCollabAPI.vCollabMessaging.poolsize is properly integrated in the context XML file.
A security vulnerability within OpenSearch (CVE202323612) has been resolved. OpenSearch, which is used in the PREEvision monitoring infrastructure services, has been updated to version 2.11.

Version 10.20

205

PREEvision 10.12

9.7 Known issues

Known issues in PREEvision 10.12

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

ID 17938307791212069
8682711552649222003 8682711555165912106 8682711555133422025 8682711686247202025
8682711686179212044

Known issue
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.
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.
ReqIF export: For empty attributes, the string defined in the Text for empty Labels property is exported instead of and empty string. By default, this is "---". Workaround: In the Preferences, under PREEvision | General, remove all characters from the Text for empty Labels property.
<Ctrl> + click on a preview image in a formatted text may not open the linked File Attachment. Workaround: Use the context menu on the preview image or double click on the File Attachment artifact in the Model View to open the file attachment.
When inserting a diagram placeholder based on templates, an error message is reported that the used template is incomplete. Workaround:
1. Navigate to the selected template under Administration | Configuration File Container | Report Template Package and select the affected template file.
2. Open the location of the file in the Windows Explorer and delete the file.
3. Update from the server to force a reload of the file.
When generating a report for a diagram as PDF, an error message is reported that the report generation was not able to write any data in the Temp directory and is aborted. Workaround:
1. Navigate to the report under Administration | Report Model and select the report file.

Version 10.20

206

PREEvision 10.12

ID 8682711687075110069 8682711555191801873
8682711685521992014 8682711687181061868

Version 10.20

207

10 PREEvision 10.11
This chapter contains the following information:
10.1 Version numbers 10.2 Installation and compatibility information 10.3 New features in PREEvision 10.11 10.4 Configuration information 10.5 Fixed issues
Common Diagrams Tables Requirements Logical function architecture AUTOSAR Software architecture Diagnostics Communication Hardware architecture Product line engineering Variant management Metrics Reports Collaboration Administration Installation Backup, restore, and migration 10.6 Known issues

PREEvision 10.11
209 210 212 216 217 217 217 218 218 219 219 220 220 221 221 222 222 222 222 223 223 223 224 225

Version 10.20

208

10.1 Version numbers

Version numbers

Application PREEvision client PREEvision license server PREEvision database server PREEvision application server

Documentation

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

PREEvision 10.11
Version number 10.11.0 3.0.1 10.11.0.03 10.11.0
Version number 10.11.0 10.11.0 10.11.0 10.11.0 10.11.0

Version 10.20

209

PREEvision 10.11

10.2 Installation and compatibility information
For detailed information about the installation of PREEvision 10.11 and the migration to PREEvision 10.11, refer to the PREEvision operating manual.
For detailed information about the hardware and software requirements of PREEvision 10.11, refer to the PREEvision system requirements.

System requirements

The following system requirements have been changed: > The recommended version of Apache Tomcat has been changed to 9.0.83.

LibreOffice update

The internal LibreOffice component has been updated for more stable use and editing of formatted texts.

Server configuration

For the startup of all server components, the following additional Java 9 JVM parameters must be set:
--add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED

Compatibility

Client version
10.5.0 10.6.0 10.7.0 10.8.0 10.9.0 10.10.0 10.11.0

Server version
10.5.0 10.6.0 10.7.0 10.8.0 10.9.0 10.10.0 10.11.0

Database server script version 10.5.1.41 10.6.0.02 10.7.0.02 10.8.0.02 10.9.0.03 10.10.0.03 10.11.0.03

Metamodel change ID 2022-10-05 2023-04-03 2023-06-01 2023-07-20 2023-09-18 2023-11-13 2024-01-19

Migration and update

PREEvision 10.0 SP17 or later can be migrated to PREEvision 10.11.
Migrating to PREEvision 10.11 is only possible from PREEvision 10.0 SP17 or later. Also, all remote operations (model preparation, backup, direct migration) available in the PREEvision 10.11 administration panel can only be performed on PREEvision 10.0 SP17 or later. If you want to migrate a PREEvision 10.0 version before 10.0 SP17 or PREEvision 9.5, contact the Vector support.
For the migration to PREEvision 10.11, it is recommended to update PREEvision 10.0 to the latest version (service pack update), at least PREEvision 10.0 SP17, before creating a backup and starting the migration.

Version 10.20

210

PREEvision 10.11
An update of PREEvision 10.5 or one of its following minor releases, starting with version 10.6, to PREEvision 10.11 requires no migration and can be performed as minor release update. An update of PREEvision 10.5 to a following minor release, for example, PREEvision 10.11, 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 > 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".

Version 10.20

211

PREEvision 10.11

10.3 New features in PREEvision 10.11

ReqIF extensions and improvements

Class changes by an updating ReqIF import are now reflected, for example, if a Definition (must) requirement changes to an Information (can) requirement.
ReqIF export formulas embedded in the formatted text are now exported as images (PDF with image preview).
During the Excel export, formulas, diagram placeholders, and PREEvision table placeholders embedded in formatted texts are now exported as a PDF with a preview in the Excel sheet.

Conversion of OLEs to file attachments

Conversion of OLEs to file attachments can now be used without restrictions. The performance issues in the resulting formatted text have been resolved. An extraction and replacement of OLEs from formatted texts is possible using the OLE Object Extraction and Replacement metric block. The OLEs are handed over as RTF files for further treatment. When an Excel OLE (xlsx) is unpacked, the sheet is now visible by default.

Improvements in calibration parameter handling

A refactoring simplifies the setting of initial values for calibration parameters by creating the artifacts needed for complex data types. The refactoring supports Application Axis Types, Application Curve Types, Application Map Types and Application Cube Types. The synthesis can be started from the context menu on artifacts typed by a calibration data type.

Extension for signal to service mappings

Platform interface mappings allow to map a sub-element of a Service Interface to any Signal in AUTOSAR Classic. This includes combinations like mapping different elements of Classic interfaces to elements of one Adaptive Service Interface or the mapping of nested complex data types. For better usability, the platform interface mapping editors have been improved.

Version 10.20

212

PREEvision 10.11

Influencing the communication path router

The behavior of the communication path router can be influenced by conditions. You can set "Must Use" or "Shall Not Use" conditions. The conditions are assigned to a Communication Path and a topology artifact, for example, a Bus System.

The communication path router can be used for link load estimation and within the Diagnostic Communication Explorer and the Generic Communication Explorer.

Splitting a cable or set of single wires by an inline connector

A Cable or a set of Single Wires can be split by an inline connector in one step by directly inserting a complete inline connector into the individual wires (Cores/Shieldings of a Cable or Single Wires).
A Cable or a set of Single Wires can be split by the following kinds of inline connectors:
> Wiring Harness Inline Connector
> Wiring Harness Multi Inline Connector
Splitting the wires is done by inserting the inline connector into the wires via a multi-select operation. Depending on the first selected wire, a vertical or horizontal inline connector is inserted. The representation of the connector sides (side A and side B) is supported by a side selection dialog.

Cable constraint online checks

Several online checks have been implemented for Cable Constraints.
> C7020: Checks, if the same Schematic Connection is assigned multiple times to a Cable Constraint via a Schematic Connection Assignment.
> C7021: Checks, whether a Cable Constraint contains multiple assignments with Cable Content Kind "Shielding".
> C7022: Checks, whether a Cable Constraint contains no Schematic Connection Assignments at all. If so, such empty Cable Constraints can be deleted via a corresponding Quick Fix.
> C7023: Checks, whether there is a Schematic Connection Assignment with Cable Content Kind "-not set-".

Version 10.20

213

PREEvision 10.11

> Several checks for correct meta classes for derived abstract wires. It is checked whether the derived abstract wire has a different meta class than required by the Schematic Connection Assignment.
> C7024: Checks whether a Single Wire has set the Cable Content Kind "Core".
> C7025: Checks whether a Single Wire has set the Cable Content Kind "Shielding".
> C7026: Checks whether a Shielding has set the Cable Content Kind "Core".
> C7027: Checks whether a Core has set the Cable Content Kind " Shielding ".

Wiring harness explorer The Wiring Harness Explorer has been enhanced and improved to support the network

enhancements and

layer with respect to components and logical connectivity.

improvements

Overview tables have been enhanced or newly implemented to display logical connectors

and logical connections.

The Component Overview category has been enhanced with the following new tables:

> Component Attribute Overview

> Power Provider Overview

> Ground Connector Overview

> Bus Connector Overview

> Conventional Connector Overview

A new category Logical Connection Overview has been implemented which contains the following tables: > Power Connection Overview > Ground Connection Overview > Bus System Overview > Conventional Connection Overview

Improvements for replace with version

Context attributes, including AUTOSAR export ImEx IDs, can now be restored from the history for a selected context. This allows, for example, AUTOSAR exports of previously archived artifacts.

Multi-classifier object in query rules and consistency rules

In Query Rule Diagrams and in Consistency Rule Diagrams, it is now possible to create Multi Classifier Objects that match artifacts of multiple assigned meta classes.
When creating Link Pairs from or to Multi Classifier Objects, only those roles that are available for all assigned meta classes of the Multi Classifier Object are displayed in the role drop-down list.

Version 10.20

214

PREEvision 10.11
For Multi Classifier Objects, only static attribute value specifications ("=" and "!=") are supported, Java expressions are not supported.

Version 10.20

215

PREEvision 10.11

10.4 Configuration information

Custom toolbar in diagrams and tables

It is now possible to integrate Collaboration Metric Executors for actions like commit and check-in in the custom toolbar of diagrams.

Changed metric blocks: The following Data Targets Ports have been removed from the Revoke Asset metric

Revoke Asset

block:

> "ignoreImpactOfAssetPredecessor"

> "inhibitMoveOperations"

Deprecated metric blocks

The following metric blocks will no longer be supported in PREEvision 10.12: > Prepare Transport Product Line

Deleted metric blocks

The following metric blocks are no longer supported with PREEvision 10.11: > Asset Integration Model Calculator > Asset Integration Model Integrator > Asset Reverse Integration

Removed metrics

The "Analysis Based Integration" metrics have been removed.

Version 10.20

216

PREEvision 10.11

10.5 Fixed issues

Fixed issues in PREEvision 10.11

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

Further information

> Common > Diagrams > Tables > Requirements > Logical function architecture > AUTOSAR > Software architecture > Diagnostics > Communication > Hardware architecture > Product line engineering > Variant management > Metrics > Reports > Collaboration > Administration > Installation > Backup, restore, and migration

10.5.1 Common
ID 8682711686324792106

Resolution
A performance issue has been resolved where multiple views, for example, the Model View and the Favorites view, performed unnecessary updates after model changes, such as adding new artifacts, in subtrees which were not expanded in the view.

10.5.2 Diagrams
ID 8682711686081732041
8682711686682811027
8682711686247162099, 8682711686248101027, 17938305050522012

Resolution
Comments are preloaded and checked before exporting a diagram.
Exporting a diagram as PDF or generating a PDF Report that contains a diagram no longer leads to a NullPointerException.
Additional diagram contents like Title Blocks, Legends, tables in diagrams, mapping boxes, query label boxes, Sheet Connectors, or cable symbols, which are functionally not relevant, are not part of a System content

Version 10.20

217

PREEvision 10.11

ID 8682711686587502045

Resolution
anymore. The online check "SystemSectionChecker" no longer checks artifacts which are functionally not relevant.
Customized palette entries for diagrams can be properly executed.

10.5.3 Tables
ID 8682711686839092101 8682711686799463126
8682711684940262105
8682711686829101877
8682711686003903043, 8682711686788452111 8682711686828992048 8682711685246242098

Resolution
Opening tables no longer causes errors.
Tables maintain the state of expanded/collapsed artifacts when a cell content is selected in the table that is deleted by an operation.
Copied content from a formatted text in a table cell can be properly inserted into the search field of a table via <Ctrl>+<V>.
If a temporary filter is active in a table and filtering is switched off, the temporary filter can be reactivated by clicking the filter button again. The behavior is the same as if the "User-defined Filter" entry was selected directly in the filter drop-down list.
Closing a table in an explorer no longer leads to a NullPointerException.
The table cell action Navigate to artifact properly navigates to artifacts in other categories of an explorer.
The selection propagation between Model View and tables works reliably if a table has been opened with an active filter and then switching to a different filter in the table.

10.5.4 Requirements
ID 8682711686805842084
8682711686592892105 8682711686769391783

Resolution
A performance problem has been resolved that was caused by an invalid state in the content.xml of the formatted text, which occurred after converting from Excel OLE to Excel file attachment.
Rendering of formatted text completes properly so no error messages are displayed.
Images which are inserted into formatted text via copy and paste are automatically and properly layouted.

Version 10.20

218

PREEvision 10.11

10.5.5 Logical function architecture

ID 8682711686736572042

Resolution
The Set property page in the Property View of an Activity Chain in the Logical Function Architecture is available again.

10.5.6 AUTOSAR
ID 8682711554890801998 8682711686541690063
8682711686536232051 8682711687093983078 8682711687081871913 8682711686791821807 8682711686007422052 8682711553648922108 8682711555191931911
8682711686663062003

Resolution
To prevent inconsistent namespaces in AUTOSAR exports, a namespace lower case check was implemented to give feedback to the user.
AUTOSAR export: A Service Interface with a Method that directly references a data type is an inconsistency in AUTOSAR. Finding this case will cancel the export with an error message in the Information View.
AUTOSAR export: A background check was extended to also support SWC exports that are based on propagate definitions in Metric.
AUTOSAR export: The export of signal-to-service use cases as software cluster design description is now possible without transformation errors.
AUTOSAR ECU extract: An Addressing Method assigned to a Parameter of a Parameter Interface is properly exported.
AUTOSAR import: A transformation error caused by importing an Execution Context has been fixed.
AUTOSAR import: A bug concerning minimal AUTOSAR files which leads to an incomplete model structure in PREEvision has been fixed.
Consistency check: A new consistency check finds runnables with identical symbol within an Internal Behavior which is not allowed.
Consistency check: The checks "p1078_AtomicSWComponent_without_SWComponentM apping" and "p1078_AtomicSWComponent_with_invalid_SWCompon entMapping_multiplicity" have been corrected to ignore Port Adapters that are not mapped to ECUs or Computers. Port Adapters must not be mapped to hardware components.
Consistency check: The check "AR_010608_AR_all_PortTypeOffSWComponentInvalid" has been corrected to ignore Port Adapters.

Version 10.20

219

PREEvision 10.11

10.5.7 Software architecture

ID 8682711685250883013 8682711685521972014 8682711553393642113 8682711553633573043
8682711554773572052 8682711686871651825 8682711555154482051 8682711686753882196
8682711686081722106

Resolution
Consistency check: The rule "C3016_Homeless_Port" has been adjusted to avoid false positives on P-Ports of parameter components.
For Application Map Types, the Data Type Configuration property page is available in the Property View.
The table for creating Literals of Application Enumeration Types now correctly shows the value "not set" instead of "0" if the value is not set by user.
The special paste action for two-dimensional arrays now supports column wise paste of initial values for complex data types. This option can be configured with a new flag in the tool preferences.
In the dialog for setting initial values, float values can now be displayed and edited properly without errors.
The display problem of the range check for a java long has been fixed in the Property View. The proper range is now displayed.
For conversions of Computation Methods, the column Value has been added to the Value Table on Conversion Configuration property page.
Activity Diagram: A Building Block containing Logical Functions as child artifacts can be assigned to an Activity Partition, as long as the Logical Functions are not yet assigned to an Activity Partition.
Use Case Diagram: The Extension Points of Use Cases are now visible and can be changed in the Property View of an Extent Relation.

10.5.8 Diagnostics
ID 8682711686933892108
8682711555205781045

Resolution
Diagnostic export: Despite inconsistencies related to the export content, the export runs correctly. Because the export will not be complete, warnings indicate the inconsistencies after the transformation.
When creating server port types for DIDs, the Diagnostic Realization Explorer creates client-server interfaces with the attribute IsService set as true.

Version 10.20

220

PREEvision 10.11

10.5.9 Communication
ID 8682711686266731917 8682711686550171914 8682711686550341914
8682711686550371914 8682711686664261030 8682711686753511807 8682711686841492052 8682711554768591024
8682711686697463078

Resolution
The Dissolve PDU-FanIn/FanOut option is supported for Multiplexed IPDUs and properly processed during AUTOSAR export.
Consistency check: The rule "aApplicationEndPoint_without_ServiceInstance" has been removed.
Consistency check: The rules "C5616_signalTransmissionWithPDUTransmissionRecei ving" and "C5617_signalTransmissionWithPDUTransmissionSendi ng" have been removed.
Consistency check: Special rules for DBC have been moved from the group "AUTOSAR Communication" to "DBC".
The DBC export has been improved and filters frames with same identifier.
The frame-PDU synthesis now accepts two PDUs as compatible when routed over a Gateway, also if they contain Signal Groups.
Communication design explorer: In the user manual, the description to open the Communication Design Explorer has been corrected.
Signal router: An additional fallback has been implemented to use the channel (VLAN) to determine the Ethernet Cluster of existing Signal Transmissions that does not have ECU interfaces assigned.
Signal router: The signal router better considers already existing signals and PDUs.

10.5.10 Hardware architecture

ID 8682711686576042196
8682711686653032041 8682711686578102041

Resolution
When splitting Single Wires by inserting Splices or Wiring Harness Inline Connectors / Wiring Harness Multi Inline Connectors into wires via multiselection, the highlighting of the selected wires and the feedback indicators are removed after the action is finished.
Schematic Connections in an Electric Circuit Diagram are not rerouted when a hardware component is resized.
The refactoring Create Wiring Diagram can be executed properly on an Electric Circuit Diagram.

Version 10.20

221

PREEvision 10.11

ID 8682711686485643084
8682711686805852041

Resolution
The automatic assignment of pins to Contactings in the Assign Pins to Cavities table has been improved. Automatic assignment can also be carried out when either nothing, a slot or a cavity is selected. Otherwise, the action is disabled.
KBL export: When exporting a Wire Type, the KBL export only considers the artifacts that are part of the export elements to avoid the export of unnecessary KBL elements.

10.5.11 Product line engineering

ID 8682711686565022100
8682711686659292023

Resolution
Before executing an Asset update it is checked if the user permissions are sufficient, for example, all referenced types of core artifacts and all core artifacts muss be visible. If not, the Asset update is canceled, and details are reported to the Information View.
External relation analyzer: If a repair action for an external relation on a child artifact is cancelled by the user due to an external relation on the parent artifact, which should be repaired first, an information is reported in the Information View. The Information View displays the corresponding parent artifact for which the external relation is identified.

10.5.12 Variant management

ID 8682711554019072106

Resolution
If an artifact is added to a set that is assigned to an activated variant via the included relation, the artifact is no longer incorrectly displayed as active.

10.5.13 Metrics
ID 8682711686431582042

Resolution
The Render Diagram metric block renders all diagrams if the "renderInBackground" Data Target Port is set to true.

10.5.14 Reports
ID 8682711686742991806

Resolution
The report can now be created. In the customer's model, the artifacts that caused an error during report generation have been updated.

Version 10.20

222

PREEvision 10.11

10.5.15 Collaboration
ID 8682711686726561036
8682711686368623126
8682711686752232203 8682711686673382023
8682711686247341993

Resolution
The performance has been improved for loading a large number of artifacts from history during the Replace With Revision action.
Tables, Property View, and Model View now consistently display the localized name of an artifact's current Life Cycle State.
Loading historic model versions is possible again.
If a lock operation cannot be completely executed because of invisible artifacts, the Information View lists the XMIIDs of the invisible artifacts. In this way, an administrator can identify the invisible artifacts.
The update performance has been improved for certain situations where many updates are involved.

10.5.16 Administration
ID 8682711685677911825, 8682711687040531873 8682711686240482011
8682711686939152011
8682711685491993046
8682711686983102068
8682711686546032054

Resolution
The Add-in Installation... has been restricted to Architect licenses with Admin privileges.
Tooltips have been added to the advanced settings of the Add-ins installation dialog.
The Information View now shows whether an Add-in was added to the installation by installing its Test Add-in.
Rules are no longer automatically checked out when customizing Add-ins.
When installing Add-ins, the Check-out view no longer opens automatically.
Function and performance tests can now be executed when an authority model is active, even if the "FPT_MODEL" is not configured in the authority model. All users with activated Administrator option can execute the tests.

10.5.17 Installation
ID 8682711686836852017

Resolution
When building preconfigured Apache Tomcats for the PREEvision server components, the JVM parameters for configuring JMX access (com.sun.management.jmxremote.*) are now added under the CATALINA_OPTS instead of JAVA_OPTS.

Version 10.20

223

PREEvision 10.11

10.5.18 Backup, restore, and migration

ID 8682711686588622020

Resolution
The server-side backup with activated model preparation correctly handles changes of non-versioned file artifacts.

Version 10.20

224

PREEvision 10.11

10.6 Known issues

Known issues in PREEvision 10.11

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

ID 17938307791212069
8682711552649222003 8682711554206562068 8682711555165912106 8682711555133422025 8682711686247202025

Known issue
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.
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.
During Add-in installation, error messages occur due to non-executable metrics. Workaround: To continue the installation, confirm the error messages with [OK].
ReqIF export: For empty attributes, the string defined in the Text for empty Labels property is exported instead of and empty string. By default, this is "---". Workaround: In the Preferences, under PREEvision | General, remove all characters from the Text for empty Labels property.
<Ctrl> + click on a preview image in a formatted text may not open the linked File Attachment. Workaround: Use the context menu on the preview image or double click on the File Attachment artifact in the Model View to open the file attachment.
When inserting a diagram placeholder based on templates, an error message is reported that the used template is incomplete. Workaround:
1. Navigate to the selected template under Administration | Configuration File Container | Report Template Package and select the affected template file.
2. Open the location of the file in the Windows Explorer and delete the file.
3. Update from the server to force a reload of the file.

Version 10.20

225

PREEvision 10.11

ID 8682711686179212044
8682711687075110069 8682711555191801873
8682711685521992014 8682711686697532196 8682711687181061868 8682711687091221995

Known issue
When generating a report for a diagram as PDF, an error message is reported that the report generation was not able to write any data in the Temp directory and is aborted. Workaround:
1. Navigate to the report under Administration | Report Model and select the report file.
2. Open the location of the file in the Windows Explorer and delete the file.
3. Update from the server to force a reload of the file.
The state of expanded artifacts in tables is not reliably restored after a refresh (<F5>).
During reinitialization of the authority model an error message may be displayed reporting an unexpected error with the ramc.ser file. Workaround:
1. Delete the authority model.
2. Connect to the authority model.
3. Initialize the authority model.
For Application Curve Types and Application Cube Types, the Calibration Attributes property page is missing in the Property View. It will be restored in a future minor release.
Model operations, caused for instance by the wiring harness router or modeling in a different diagram, may change artifacts in an opened but not locked diagram. Activating the undo action may unintentionally close the PREEvision client.
The automatic integration of an Asset may be incomplete during use, reuse, or update of the Asset if related artifacts with abstraction or substitution links in a downstream Product Line are read-only. Workaround: Execute the automatic integration again.
The automatic integration of an Asset may be incomplete during use, reuse, or update of the Asset if related artifacts with abstraction or substitution links in a downstream Product Line are invisible or out-of-scope. Workaround: Temporarily add the relevant artifacts to the active scope and ensure you have the necessary rights. You may also contact the customer service for further support.

Version 10.20

226

11 PREEvision 10.10
This chapter contains the following information:
11.1 Version numbers 11.2 Installation and compatibility information 11.3 New features in PREEvision 10.10 11.4 Changes 11.5 Configuration information 11.6 Fixed issues
Common Diagrams Tables Requirements AUTOSAR Software architecture Diagnostics Communication Hardware architecture Geometry Variant management Change and release management Test engineering and test management Rules Reports Collaboration Administration License Backup, restore, and migration 11.7 Known issues

PREEvision 10.10
228 229 231 235 236 237 237 238 238 238 239 240 240 241 241 242 242 242 243 243 243 243 244 244 244 245

Version 10.20

227

11.1 Version numbers

Version numbers

Application PREEvision client PREEvision license server PREEvision database server PREEvision application server

Documentation

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

PREEvision 10.10
Version number 10.10.0 3.0.1 10.10.0.03 10.10.0
Version number 10.10.0 10.10.0 10.10.0 10.10.0 10.10.0

Version 10.20

228

PREEvision 10.10

11.2 Installation and compatibility information
For detailed information about the installation of PREEvision 10.10 and the migration to PREEvision 10.10, refer to the PREEvision operating manual.
For detailed information about the hardware and software requirements of PREEvision 10.10, refer to the PREEvision system requirements.

Apache ActiveMQ security vulnerability

A critical security vulnerability within Apache ActiveMQ (CVE-2023-46604) is resolved. The Apache ActiveMQ libraries, which are integrated in the PREEvision messaging server, have been updated to version 5.16.7.
The Apache ActiveMQ version delivered with previous PREEvision 9.0, 9.5, 10.0, and 10.x versions contains a critical security vulnerability (CVE-2023-46604). Thus, it is highly recommended that you update the PREEvision messaging server. Contact the Vector support to provide you with a possible solution.

System requirements

The following system requirements have been changed: > Application server requirements: The recommended free hard disk space has been
increased to 300 GB. > Subversion server requirements: Subversion 1.10 is no longer supported. > The recommended version of Apache Tomcat has been changed to 9.0.82.

Oracle JDBC driver

The Oracle JDBC driver, which is included in the deployment files of the application server, has been updated to version 19.21. On the application server, update the Oracle JDBC driver as follows: 1. Unpack the product delivery of the PREEvision Collaboration Platform
(PREEvisionCollaborationPlatform_<version>.zip).
The database driver is located in the folder /dbdrivers.
2. Copy the ojdbc8.jar to the %TOMCAT_HOME%/lib folder.

Server configuration

For the startup of all server components, the following additional Java 9 JVM parameters must be set:
--add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED

License server

With PREEvision 10.10, the new version 3.0.1 of the standalone license server is available.
When you use the standalone PREEvision license server (RMI), it is recommended to update the license server to the new version 3.0.1.

Compatibility

Version 10.20

229

PREEvision 10.10

Client version
10.5.0 10.6.0 10.7.0 10.8.0 10.9.0 10.10.0

Server version
10.5.0 10.6.0 10.7.0 10.8.0 10.9.0 10.10.0

Database server script version 10.5.1.41 10.6.0.02 10.7.0.02 10.8.0.02 10.9.0.03 10.10.0.03

Metamodel change ID 2022-10-05 2023-04-03 2023-06-01 2023-07-20 2023-09-18 2023-11-13

Migration and update

PREEvision 10.0 SP17 or later can be migrated to PREEvision 10.10.
Migrating to PREEvision 10.10 is only possible from PREEvision 10.0 SP17 or later. Also, all remote operations (model preparation, backup, direct migration) available in the PREEvision 10.10 administration panel can only be performed on PREEvision 10.0 SP17 or later.
If you want to migrate a PREEvision 10.0 version before 10.0 SP17 or PREEvision 9.5, contact the Vector support.
For the migration to PREEvision 10.10, it is recommended to update PREEvision 10.0 to the latest version (service pack update), at least PREEvision 10.0 SP17, before creating a backup and starting the migration.
An update of PREEvision 10.5 or one of its following minor releases, starting with version 10.6, to PREEvision 10.10 requires no migration and can be performed as minor release update.
An update of PREEvision 10.5 to a following minor release, for example, PREEvision 10.10, requires no update of licenses. PREEvision 10.5 licenses are used for the minor releases following PREEvision 10.5.

Version 10.20

230

PREEvision 10.10

11.3 New features in PREEvision 10.10

Conversion of OLEs to file attachments

PREEvision 10.5 introduced the possibility to work consistently with file attachments, for example, the embedding into a formatted text or an import and export via ReqIF. Even though importing or exporting OLEs is still possible, file attachments increase the compatibility with third party tools. An extraction and replacement of OLEs from formatted texts is possible using the new OLE Object Extraction and Replacement metric block. The OLEs are handed over as RTF files for possible further treatment. Without further treatment, an OLE is replaced by an RTF as file attachment placeholder and the preview image remains unchanged.
Optionally, an individual Calculation Block can be added to extract the original file from the OLE and hand it over to the OLE Object Extraction and Replacement metric block instead of the RTF.

Improvements for working with formatted texts

With PREEvision 10.10, various rarely used options that additionally caused inconsistencies have been removed from the LibreOffice editor menu in previews of formatted texts, reports, and ReqIF exports, for example: > Formatted texts (still possible in reports)
> Insert | Footnote and Endnote > Insert | Shapes > Formatted texts and reports > Insert | Media

Model view

To prevent performance issues, in the Model View, the following changes have been implemented:
> The expand action only expands the next three hierarchy levels.
> The number of hierarchy levels to be expanded can no longer be configured in the Preferences.
> The expand action is disabled on root artifacts.
> The toolbar action to collapse a selected artifact has been removed.

In the Model View, the button opens a table of available commit versions. By default, commit versions that are automatically created by asynchronously calculated online check results are not displayed in the table. To display online check commit versions, click on the filter button and select No filter.

Version 10.20

231

PREEvision 10.10

Link load estimation

For architecture design in early stages, PREEvision 10.10 can calculate the data load for Bus Systems based on estimations. The basis of the calculation are estimations of the data load of individual streams, that is the communication between exactly one sender and one or more receivers. To define the available bandwidth, you can now define for Bus Types if they are operating in half duplex of in full duplex mode.

Diagnostic concept explorer

If you change, for example, the network topology, a new link load estimation immediately shows the consequences of your modifications. Note: To utilize link load estimation, a configuration is necessary.
The Diagnostic Concept Explorer to specify diagnostic data in early phases has been further improved: > In the tables for DIDs, I/O controls, routines, event handling and fault memory
diagnostic instances, diagnostic data can be assigned to a Diagnostic Master.

> For the creation of Fault Memory Diagnostic Instances, Enable Condition Groups and Storage Condition Groups, new tables have been added to the explorer.

> To support the management of diagnostic design, Diagnostic Packages and Diagnostic Master artifacts can now be planned.
> In PREEvision 10.10, DTCs can be specified without a Fault Memory Diagnostic Instance. This allows to define DTCs and their event handling in an early specification step. Therefore, DTC Packages can be created in a Diagnostic Packages. Error codes are displayed with 4 Bytes. Note: These DTCs are not considered for export.

PVCDI import and export

> The display of the import content in the import wizard has been improved by structuring the data by meta class.
> The selection of the relevant Diagnostic Master in the export wizard has been simplified by displaying to path information of the Diagnostic Master.
> PREEvision 10.10 provides a tool to migrate PVCDI file to the version supported by the import.

Inserting inline connector schematic pins into a cable

A Cable can be split by inserting an inline connector Schematic Pin into a Core or Shielding of the Cable. When inserting a Schematic Pin into a Core or Shielding, a Wiring Harness Multi Inline Connector is created. All subsequent Schematic Pins which are

Version 10.20

232

PREEvision 10.10
inserted into further Cores of the Cable are automatically added to the already existing inline connector, and the pins connected to the corresponding Cores or the Shielding of the already existing Cable duplicate.

The Show owning Component context menu action for a Schematic Pin has been improved in so far that Schematic Pins are automatically and properly moved into the corresponding inline connector.

Enhanced preferences for inline connectors

The preferences for the orientation when inserting an inline connector have been enhanced. The vertical or horizontal orientation can be defined as well as a vertical or horizontal side selection for the different sides of the inline connector determined.
Additionally, inserting a Schematic Pin from the diagram palette into a Single Wire is now disabled by default.

Cable constraints

A new wiring artifact Cable Constraint has been implemented which is intended to technically group Schematic Connections which are later implemented as Cores or Shieldings of a Cable in the wiring harness.
A Cable Constraint can be used as a template to model a Cable based on the assigned Schematic Connections. A cable content kind can be specified which determines if a Schematic Connection is later represented as a Core or a Shielding.

Version 10.20

233

PREEvision 10.10

Search and replace in tables

A new search and replace function for tables allows you to select an attribute displayed in a table column and search only in the values of this attribute. Attribute values that are editable can be replaced. The Search and Replace view shows the search results and a preview of the replace results.

Version 10.20

234

PREEvision 10.10

11.4 Changes

Working copies no longer supported

Working with Subversion working copies is no longer supported.

Mapping view no longer The generic Mapping View is deprecated and no longer supported with

supported

PREEvision 10.10.

Version 10.20

235

PREEvision 10.10

11.5 Configuration information

New menu creation properties

Issue ID: 8682711685295062039
Translations can be adapted via New Menu Creation Properties Delta Files. In previous PREEvision versions, it was only possible to extend the model creation files via the deltas, but not the translations (group translations). To ensure that the configured new menu entries (model creation) and the associated translations (group translation) work properly, the files must be named accordingly:
> Model creation delta files must contain "modelcreation" in the file name.
> Group translation delta files must contain "grouptranslation" in the file name.

New metric blocks: OLE Object Extraction and Replacement

The OLE Object Extraction and Replacement metric block extracts OLEs from formatted texts. The OLE is extracted as an RTF containing this OLE. Using the loop ports, this RTF can be further modified to extract the original file. Subsequently, the file or the RTF is included as file attachment placeholder on the same place the OLE was. The OLEs preview is taken as preview for the file.

Changed metric blocks: The Communication Path Router metric block has been changed.

Communication Path Router

The new input port "calcLinkLoad" enables link loads to be calculated in parallel with communication path routing. The data type is Boolean. The default value is true.

Deleted metric blocks

The following metric blocks of the diagnostics import are no longer supported with PREEvision 10.10: > Diagnostic Abstraction Link Creator > Diagnostic Abstraction Link Refresher > Diagnostic Definition Set Assignment and Creation of Attribute Profiles > Diagnostic Reference Identification Function > Diagnostic Library Creator > Diagnostic Replace Relevance Function > Diagnostic Product Line Selection > Diagnostic Library Identification Function

Version 10.20

236

PREEvision 10.10

11.6 Fixed issues

Fixed issues in PREEvision 10.10

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

Further information

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

11.6.1 Common
ID 8682711554188622106
8682711553592481029 8682711685296932108 8682711686298661992

Resolution
To prevent performance issues, in the Model View, the following changes have been implemented: > The expand action only expands the next three
hierarchy levels. > The number of hierarchy levels to be expanded can
no longer be configured in the Preferences. > The expand action is disabled on root artifacts. > The toolbar action to collapse a selected artifact has
been removed.
The Information View is properly opened and displayed.
The performance of loading the dialog for selecting active mapping containers has been improved to prevent client freezes.
On the General property page of Background Images, the attributes Keep Image Ratio, Adjust Image Size Automatically, and Background Image Fix Point have been added.

Version 10.20

237

PREEvision 10.10

ID 8682711686301351998 8682711686179092203
8682711686301351998 8682711555150891783

Resolution
Made evaluation of disadvantageous structured packages in consistency view more resilient to prevent freezes in client.
The performance of the quick search has been improved when searching by XMIID or UUID on large models with over two million artifacts and restricting the search to the selected artifact.
An issue has been fixed that sporadically lead to a client freeze when opening the Artifact Picker.
The Check-out dialog is not displayed when opening a formatted text editor and closing it without having carried out any changes.

11.6.2 Diagrams
ID 8682711554638731998
8682711686544692062, 8682711686571832050, 8682711553471062041
8682711686246071825

Resolution
The object configuration of artifacts in a Software Architecture Diagram is kept, if the artifact is moved.
Previously, the visibility of an artifact's background image in a diagram was not always updated correctly according to its condition in the object configuration. Now, all background images are always properly updated and displayed when opening or exporting the diagram.
Opening a diagram does not result in an error if a configured icon cannot be rendered. A fallback has been implemented to render the icon. If the configured icon still cannot be rendered, a new log entry provides further information.

11.6.3 Tables
ID 8682711686179382048, 8682711686571732050 8682711686392002008

Resolution
The table cell action Navigate to artifact properly navigates to artifacts in other categories of an explorer.
Filtering table columns via predefined filters: In the Predefined Filters ... dialog, the displayed number of hits for non-activated values is displayed correctly, even if the filter dialog is closed and reopened.

11.6.4 Requirements
ID 8682711685484412105

Resolution
Tables with borders in formatted texts no longer cause schema validation errors when being exported to ReqIF.

Version 10.20

238

PREEvision 10.10

ID 8682711685501392105
8682711684912852106
8682711554406631783
8682711685481082106
8682711686391982101, 8682711686430842106, 8682711686431572106, 8682711686430442105, 8682711686293742105, 8682711686372232105 8682711684910001992

Resolution
Selected Requirement Packages that are temporarily added to the scope are checked and displayed in the ReqIF Export dialog.
Adding a file attachment to a checked-in formatted text works at the first try.
The formulation that notifies users about overwritten model contexts while defining reports has been improved.
Consistent filtering behavior in table-based editors: when changing the object type of Requirement artifacts with an active column filter on the object type, only artifacts are shown that correspond with the active filter.
The system behavior has been stabilized while working with formatted texts.
After importing requirements into the model, it is possible again to switch to Is Heading type in the Property View.

11.6.5 AUTOSAR
ID 8682711686532692013
8682711686250021917 8682711686234451807 8682711685818571998 8682711554721442014
8682711555035481003
8682711684967232051

Resolution
The improved AUTOSAR SW component description considers also an Addressing Method used by a Memory Section.
The ECU Extract can handle logical functions that are mapped to the ECU.
The Bus Off Recovery attributes of CAN Clusters are imported and exported.
The export of an Adaptive Application Description can handle multiple reference targets.
Literals for numerical values (double, integer, long, float) are exported to AUTOSAR as Application Value Specification with category VALUE.
Consistency check: The rule "c1221_DataTypedInformationUnit_with_invalid_ ApplicationValueType_InitValue_B" checks now also Linear Verbal Table Conversions.
Data constraints that are used multiple times in an imported ARXML file are merged to one constraint at export time again, in case their min and max values still match, even if the representation of these values was different in PREEvision (for example, 100 and 1E2).

Version 10.20

239

PREEvision 10.10

ID 8682711686301112108
8682711686550201914 8682711686550211914

Resolution
Consistency check: The rule "AR_010701b_MoreThanOneApplRecordElementFor ApplRecord" has been removed. It previously hit for Application Record Types that are referenced by more than one Application Record Element of another record. This pattern is allowed.
Consistency check: The rule "aSWPortPrototype_without_ReceiverComSpec_ InitValue" has been removed due to a duplicate.
Consistency check: The severity of the rules "C5506a_muteProvidedPort", "C5506b_muteProvidedSWPort", and "C5506c_muteProvidedRootPort" has been changed from "Information" to "Warning".

11.6.6 Software architecture

ID 8682711686312752052
8682711552654251024
8682711685250883013

Resolution
The operation Update SW Component Type is also available in the context menu for software component types located in the System Software Architecture.
In the Property View of Runnable Entities, the unit of the attribute Minimum Start Interval has been corrected from ms to s.
Consistency check: The rule "C3016_Homeless_Port" has been adjusted to avoid false positives on P-Ports of parameter components.

11.6.7 Diagnostics
ID 8682711684979942113
8682711686356952005

Resolution
In the Property View of Diagnostic Packages und Diagnostic Structure Packages the Planning page has been added.
Diagnostic export: In case of incomplete software realizations for diagnostic objects (missing relation between SW Port and diagnostic objects), the software realizations are not exported anymore. If a diagnostic concept is available instead, this is considered for the export.

Version 10.20

240

PREEvision 10.10

11.6.8 Communication
ID 8682711553094891825, 8682711686540882052, 8682711686556351024 8682711686448061807
8682711686448191807
8682711686550391914
8682711686550381914 8682711686550361914
8682711686550351914
8682711686565081914
8682711554826071917 8682711686446891914 8682711553303801913, 8682711552654241024

Resolution
Performance problems of signal router with certain service interfaces (high number of artifacts inside the service interface) have been solved by checking routing compound artifacts only once.
SOA & Ethernet Explorer: The Artifact Picker in the VLAN Switch Configuration Editor displays all relevant VLANs.
SOA & Ethernet Explorer: The Service Instance Communication Design table gets properly refreshed after the calculation of Header IDs.
Consistency check: The severity and fault description of the consistency check "p1163_Signal_with_illegal_DataType" has been corrected.
Consistency check: The rule "EthPortConfWoMacAddr" has been removed due to a duplicate check.
Consistency check: The rule "dataElementWithoutApplicationDataType" has been removed due to a duplicate check.
Consistency check: The rule "ConsumedEventGroupNotSameAEP" has been removed because the check is not valid.
Consistency check: The rule "C5502_Uninformed_Signal" to check all relevant mappings on Signal and on System Signal side has been improved.
DBC export: Large numbers are supported for signal table values.
LDF export: Byte values of LIN Free Format frames are exported in the order they were defined.
In the Property View of Timing Events, the unit of the attribute Offset has been corrected from ms to s.

11.6.9 Hardware architecture

ID 8682711686282601992
8682711685480271912

Resolution
Internal Logical Connector Types can be created under a Library Package via the context menu entry New | Other Types | Internal Logical Connector Type.
The following new attributes concerning electrical properties have been added for a Schematic Pin: > Max Stall Current > Inrush Current Duration > Max Stall Current Duration

Version 10.20

241

PREEvision 10.10

ID 8682711685458722112 8682711685484321204 8682711686528021038 8682711554646962083 8682711685822991914
8682711686665122083

Resolution
All attributes include a unit.
For Single Wires, Cores and Shieldings, the new attribute Nominal Operating Voltage including a unit has been added to the Electrical Properties property page.
A warning dialog is displayed in case an invalid Schematic Pin of a Wiring Harness Inline Connector has been added to a wire via drag and drop.
No error occurs concerning highlighting diagram content which is not active.
Importing a KBL file via the advanced KBL import metric creates Contactings below the Wiring Cavities.
Wiring harness router: The wiring harness router did not route Schematic Connections for which the start and end points were not located at the same component. This issue occurred due to multiple Wiring Connectors which were mapped to a single Connector Location. This issue has been resolved for wiring harness routing.
The "Wiring Harness Demo Model" Product Line in the PREEvision demo model has been enhanced with an example of Cable Constraints.

11.6.10 Geometry
ID 8682711685999491912

Resolution
The endpoint of a Topology Segment is no longer displaced at a Connector Location on irregular zoom factors, for example 133%. This error occurred especially if the Geometry Diagram was printed with the Print Quality setting Draft.

11.6.11 Variant management

ID 8682711555119922003

Resolution
The Consistency Rule which checks the compliance of artifacts with AUTOSAR Pre Build Variant Conditions and Post Build Variant Conditions has been updated.

11.6.12 Change and release management

ID 8682711554011401894
8682711554916332106

Resolution
The Compare Table displays the layers of the E/E model in the same order as the Model View.
In the Compare Table, the performance of filtering columns during a model comparison has been improved.

Version 10.20

242

PREEvision 10.10

ID 8682711685315583082

Resolution
Review and vote: When changing the status in the Review Table, the last modification date is updated.

11.6.13 Test engineering and test management

ID 8682711685414613126
8682711686453381030

Resolution
New test artifacts are sorted in a consistent order even if the list contains artifacts with and without a chapter ID.
Import of CANoe test reports: Test results of Automatic Test Cases with the same name but different ImEx-IDs are now imported.

11.6.14 Rules
ID 8682711553143551999

Resolution
The names within the Propagate Definition Diagram palette have been renamed to improve clarity and precision. The CompletenessCheckLinkPair meta class has been renamed to Propagate Definition Link Pair.

11.6.15 Reports
ID 8682711685984473056, 8682711686304422105

Resolution
Formatted texts that contain a text table as first element are now properly handled during report generation when combined with conditional formatting placeholders.

11.6.16 Collaboration
ID 8682711554740723013
8682711686448320064 8682711686441192108
8682711686525922105

Resolution
A filter to show or hide online check commits has been added to the commit history dialog that is available in the Model View via the "Change to historic model version" icon.
The logging has been extended so that it will be possible to identify the cause of an update error after a commit in special cases.
The performance of the commit has been improved in case the committed change set contains large amounts of reuses (new or old), changed branches, or changed revisions.
If the update fails after switching from offline to online mode because of still existing network problems, then the user will not be forced to reload the model.

Version 10.20

243

PREEvision 10.10

ID 8682711686247190000
8682711554027241995

Resolution
During the creation of file attachments via the API Server the correct file name is used. Unicode and URL-encoded characters are properly handled.
The specification of the boolean Transition Expansion Parameter using the values true or false has been documented.

11.6.17 Administration
ID 8682711686294432011
8682711686530193046 8682711684967892054
8682711554406702203

Resolution
If an Add-in installation is aborted because of an error, the operation will be completely rolled back, leaving the model is in the same state as before the installation.
Add-in installation rolls back (in case of error) only its own operations, not previous operations.
If an administrator is connected via OpenID Connect, expired sessions no longer cause errors in the Administration perspective.
If the PREEvision administration server is installed under Linux, models including files can be properly initialized via the administration panel.

11.6.18 License
ID 8682711686406373090, 8682711686577952054

Resolution
With PREEvision 10.10, the new version 3.0.1 of the standalone license server is available. The new version provides an improved mechanism for license reservation and improved logging during license reservation.

11.6.19 Backup, restore, and migration

ID 8682711554031661036
8682711686360131036

Resolution
In previous PREEvision versions, in rare cases, the restore failed with the following error message: "Error while executing model version <version>: Newly created reuses do not match existing reuses." The issue has been resolved.
Restoring artifacts with a changed XMIID works properly.

Version 10.20

244

PREEvision 10.10

11.7 Known issues

Known issues in PREEvision 10.10

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

ID 17938307791212069
8682711552649222003 8682711554206562068 8682711555165912106 8682711555133422025 8682711686247202025
8682711686179212044

Known issue
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.
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.
During Add-in installation, error messages occur due to non-executable metrics. Workaround: To continue the installation, confirm the error messages with [OK].
ReqIF export: For empty attributes, the string defined in the Text for empty Labels property is exported instead of and empty string. By default, this is "---". Workaround: In the Preferences, under PREEvision | General, remove all characters from the Text for empty Labels property.
<Ctrl> + click on a preview image in a formatted text may not open the linked File Attachment. Workaround: Use the context menu on the preview image or double click on the File Attachment artifact in the Model View to open the file attachment.
When inserting a diagram placeholder based on templates, an error message is reported that the used template is incomplete. Workaround:
1. Navigate to the selected template under Administration | Configuration File Container | Report Template Package and select the affected template file.
2. Open the location of the file in the Windows Explorer and delete the file.
3. Update from the server to force a reload of the file.
When generating a report for a diagram as PDF, an error message is reported that the report generation was not able to write any data in the Temp directory and is aborted. Workaround:

Version 10.20

245

PREEvision 10.10

ID
8682711686769391783 8682711555191801873
8682711685521972014 8682711685521992014 8682711686697532196

Known issue
1. Navigate to the report under Administration | Report Model and select the report file.
2. Open the location of the file in the Windows Explorer and delete the file.
3. Update from the server to force a reload of the file.
No automatic layouting is done for images which are inserted into formatted text via copy and paste. Preview Images of inserted File Attachments, however, are correctly layouted. Workaround: Manually format the selected image via context menu Default setting for image or via the corresponding button in the formatting toolbar.
During reinitialization of the authority model an error message may be displayed reporting an unexpected error with the ramc.ser file. Workaround:
1. Delete the authority model.
2. Connect to the authority model.
3. Initialize the authority model.
For Application Map Types, the Data Type Configuration property page is missing in the Property View. It will be restored in a future minor release.
For Application Curve Types and Application Cube Types, the Calibration Attributes property page is missing in the Property View. It will be restored in a future minor release.
Model operations, caused for instance by the wiring harness router or modeling in a different diagram, may change artifacts in an opened but not locked diagram. Activating the undo action may unintentionally close the PREEvision client.

Version 10.20

246

12 PREEvision 10.9
This chapter contains the following information:
12.1 Version numbers 12.2 Installation and compatibility information 12.3 New features in PREEvision 10.9 12.4 Changes 12.5 Configuration information 12.6 Fixed issues
Common Diagrams Tables Requirements Logical function architecture AUTOSAR Software architecture Diagnostics Communication Hardware architecture Geometry Product line engineering Change and release management Test engineering and test management Metrics Reports Collaboration Administration Backup, restore, and migration 12.7 Known issues

PREEvision 10.9
248 249 251 256 257 258 258 259 259 259 260 261 261 262 263 264 264 265 265 265 265 266 266 266 266 267

Version 10.20

247

12.1 Version numbers

Version numbers

Application PREEvision client PREEvision license server PREEvision database server PREEvision application server

Documentation

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

Version number 10.9.0 3.0.0 10.9.0.03 10.9.0
Version number 10.9.0 10.9.0 10.9.0 10.9.0 10.9.0

PREEvision 10.9

Version 10.20

248

PREEvision 10.9

12.2 Installation and compatibility information
For detailed information about the installation of PREEvision 10.9 and the migration to PREEvision 10.9, refer to the PREEvision operating manual.
For detailed information about the hardware and software requirements of PREEvision 10.9, refer to the PREEvision system requirements.

System requirements

The following system requirements have been changed:
> Client requirements: The recommended free hard disk space has been increased to 50 GB.

LibreOffice update

The internal LibreOffice component has been updated for easier maintenance and better functional support within PREEvision.

Server configuration

For startup of the application server and the standalone middleware license server, the following JVM parameter must be set:
-Djdk.util.zip.disableZip64ExtraFieldValidation=true
For the startup of all server components, the following Java 9 JVM parameter must be set:
--add-opens=java.base/sun.nio.ch=ALL-UNNAMED

Compatibility

Client version
10.5.0 10.6.0 10.7.0 10.8.0 10.9.0

Server version
10.5.0 10.6.0 10.7.0 10.8.0 10.9.0

Database server script version 10.5.1.41 10.6.0.02 10.7.0.02 10.8.0.02 10.9.0.03

Metamodel change ID 2022-10-05 2023-04-03 2023-06-01 2023-07-20 2023-09-18

Migration and update

PREEvision 9.5 and 10.0 can be migrated to PREEvision 10.9.
For the migration to PREEvision 10.9, 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.

Version 10.20

249

PREEvision 10.9
An update of PREEvision 10.5 or one of its following minor releases, starting with version 10.6, to PREEvision 10.9 requires no migration and can be performed as minor release update. An update of PREEvision 10.5 to a following minor release, for example, PREEvision 10.9, 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 > 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".

Version 10.20

250

PREEvision 10.9

12.3 New features in PREEvision 10.9

Showing and hiding headers and pins

Pins and headers can be displayed and arranged on components in Wiring Diagrams or Electric Circuit Diagrams by using the Show/Hide Headers and Pins dialog.
With the Show/Hide Headers and Pins dialog it is possible to define the side of the component where to place selected pins and their Headers. The side selection function for placing pins and Headers can only be carried out for newly created pins which are not yet added to the diagram. For pins and Headers which are already assigned to a component a side selection is not possible.

Splice position calculation

To properly run the wiring harness router, Splices need to be mapped to Branch-Offs in the Geometry. For mapping a Splice to a Branch-Off, the optimal target position where to map a Splice can be calculated automatically via the Splice Position Calculation metric.
Via the context menu Metrics | Splice Position Calculation available for a Splice, an optimal mapping target is calculated based on the shortest total length and minimum total weight of the wires.

Diagram-based change management and evaluation of diagram content

Various functionalities, like for example diagram reports, printing, or publishing diagrams, access diagram data. Currently, the data stored in the model is taken into consideration for these functionalities.

Version 10.20

251

PREEvision 10.9

A diagram synchronization mechanism ensures that the state of the diagram is always up to date. Diagram repair and update mechanisms are processed prior to the conversion of a diagram. This applies to a manually triggered conversion as well as to conversions via metric functions.

Filter preview in

The predefined filters selection for filtering table columns now displays the number of hits

predefined filters dialog within the table column for each filter option. The number of hits is only displayed if more

of tables

than one hit is found.

Editing file attachments After a double click on a File Attachment, the Edit/View File Attachment dialog opens.

If you select Edit, the file is directly locked and opened for editing without displaying the lock dialog.

Extensions for value handling

In PREEvision, initial values or invalid values are stored individually in appropriate literals according to their data types. PREEvision 10.5 introduced a simplified definition of these values. With a value handling configuration, the user can simply enter initial or invalid values directly in the Property View, in data type editors, or tables. The system automatically creates the required value specifications in the background and associates them with the artifacts the user is editing.

Version 10.20

252

PREEvision 10.9
With PREEvision 10.9 you can now decide if the unit of a value shall also be overtaken from the corresponding data type. This functionality can be enabled or disabled depending on the modeling style of each customer.

Also, values for Data Types that are interpreted as enumerations according to AUTOSAR, get drop-down lists in various editors.

Extensions for FlexRay controller configurations

Three new AUTOSAR attributes for the class FlexRay Controller Configuration are introduced:
> Key Slot Only Enabled
> Key Slot Used for Sync
> Key Slot Used for Startup
The meta model including range checks, the Property View, and AUTOSAR import and export have been extended accordingly.

Diagnostic import and export for diagnostics concept

PREEvision 10.6 introduced the possibility to define diagnostic concepts in early development phases independent of its later realization in software.
To better support the definition of diagnostic concepts, the data structure has been adapted as follows:
> Diagnostic objects are stored in a generic diagnostic structure in parallel to Diagnostic Master.
> A new relation between Diagnostic Master and diagnostic objects is introduced.
> All information is part of the Diagnostics layer including Data Type Packages.

> Local Administration for attribute definitions is supported.

Version 10.20

253

PREEvision 10.9
With PREEvision 10.9, the PVCDI data exchange with CANdelaStudio supports these diagnostic concepts.

> Diagnostic import: > The diagnostic import now considers the new meta model for diagnostic concepts. > The diagnostic import of *.pvcdi files is started with the import wizard. > All data type relevant information is imported to application data types. > Encoding, bit length and byte order is imported as base type requirements.
The updating PVCDI import in the software realization is no longer supported.
> Diagnostic export: > The diagnostic export considers the diagnostic concept. > If both diagnostic concept and software realization are available, the software realization is prioritized. > For a Diagnostic Master a mix of both is possible. > The prioritization is handled for each diagnostic object individually.
With the introduction of the new diagnostic concept, the diagnostic import and export behavior has been changed. Diagnostic import is now imported as diagnostic concept. The diagnostic export now either considers diagnostic realizations or the diagnostic concept. The diagnostic export no longer considers diagnostic data that was initially created by a diagnostic import in a PREEvision version prior to 10.9 and that is not yet realized in software. For detailed instructions on how to migrate existing diagnostic data according to the diagnostic concept, contact the Vector support.

Improvements for life cycles

User-defined severity levels for all life cycle transition constraints: > New attribute severity as return status for life cycle transition constraints
> Attribute value checks > Lifecycle transition authorizations > Available severities: Error (continue evaluation of other possible transitions) or Fatal Error (stop evaluation and rollback of trigger event) > Default Value for severity: Error (=present behavior)

Version 10.20

254

PREEvision 10.9
New severity level for life cycle transition actions: > Life cycle transition actions return severity level Fatal Error (new behavior: rollback
of trigger event)
Additional improvements of life cycle handling: > New option for life cycle state authorization:
> Deny Check-Out > Fixed options:
> Deny Create Branch > Deny Create Revision

Version 10.20

255

PREEvision 10.9

12.4 Changes

Deprecated product line health viewer

The Product Line Health Viewer has been replaced with the External Relation Analyzer since PREEvision 10.5 and is no longer supported with PREEvision 10.9.

Deprecated mapping view

The generic Mapping View is deprecated and will no longer be supported with PREEvision 10.10.

Version 10.20

256

PREEvision 10.9

12.5 Configuration information

Table configuration: Improve performance of loading artifact pickers

Issue ID: 8682711553599113013
If a Generic Table Artifact Picker is referenced in a table and displays many artifacts, use the following configuration guideline to improve the performance of loading the artifact picker.
On the Data Providing Table Column of the Generic Table Artifact Picker:
1. Use a metric (Embedded Metric Executor) to obtain the contents.
2. Disable the default sorting by creating a generic EE Attribute (Name: "sort", Value: "false") under the column.
3. In the metric, implement parallel sorting by:
Stream<MAbstractNameAttributeArtefact>.parallel().sorted (Stream<MAbstractNameAttributeArtefact> java.util.stream.Stream.sorted(Comparator<? super MAbstractNameAttributeArtefact> arg0))

Changed metric blocks: The Diagram Artifacts Collector metric block has been changed:

Diagram artifacts collector

> The "source" input port of the Diagram Artifacts Collector metric block has been changed to accept a list of diagrams (List<Diagram>) instead of a single diagram.

> The new, optional input port "metaClassFilter" has been introduced to only collect artifacts of the given meta class (data type: List<MMetaClassAuthorityProxy>).

> The new output port "diagramArtifacts" returns the represented artifacts of the defined meta classes for each diagram (data type: HashMap<MDFObject, MDFObject>).

Changed metric blocks: Issue ID: 8682711555181132101

CSV export

For the CSV Export metric block, the behavior of the "quote" input port has been changed

depending on the set value of the "quote" port.

Quote port

Quote character Quote mode

No value or empty " value (default)

minimal: Values that contain the separator character are quoted by quotation marks. Values that contain no separator character are not quoted.

"NONE"

no quotes

none: Values are not quoted.

Defined character, Defined character all: All values are quoted by the defined quote

for example, "

character. For example, to quote all values by

quotation marks, set " as quote character.

Changed metric utilities: GenericAttribUtil

The GenericAttribUtil class is moved from aquintos.bridge.utils to vi.mm.commoncore.util.

Changed metric utilities: ScratchpadUtil

Issue ID: 8682711684968112106
The method ScratchpadUtil.isScratchpadArtifact(artifact) has been changed to ScratchpadUtil.isScratchpadArtifact(artifact, scratchpad). This improves performance for checking if an artifact has a relation to the scratchpad.
Existing metrics that use this method must be adjusted.

Version 10.20

257

PREEvision 10.9

12.6 Fixed issues

Fixed issues in PREEvision 10.9

You will find the important fixed issues in the following tables. Please note that some 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 > Change and release management > Test engineering and test management > Metrics > Reports > Collaboration > Administration > Backup, restore, and migration

12.6.1 Common
ID 8682711685677142039, 8682711685540101897 8682711685246322034
8682711685347962001
8682711553592293111
8682711684940262105, 8682711685463331865

Resolution
The expand icon is shown correctly in the Information View and Information View entries can be expanded.
The action Window | Reset all Perspectives to Model Definitions properly resets all perspectives.
Opening a File Attachment for editing automatically allocates all required locks without opening the lock dialog.
Special paste of diagrams works properly and has the same result when executed by drag and drop, shortcut, and context menu.
The Check-out dialog is not displayed when opening a formatted text editor and closing it without having carried out any changes.

Version 10.20

258

PREEvision 10.9

12.6.2 Diagrams
ID 8682711555023062039

Resolution
The value defined for variant highlighting in the Preferences is also applied to the online check indicators of the corresponding artifacts in the diagram.

12.6.3 Tables
ID 8682711555133221032
8682711554380662101 8682711555166051992
17938305535212106 8682711554396602001
8682711684966583042 8682711685476702023

Resolution
Changes in the model, for example deleting elements or removing associations, do not lead to empty cells or missing rows in open table-based editors with active column filters anymore.
Table help entries are not shown in case that the main column is hidden.
The background color constraint metric of a column monitors also the first change of a custom attribute value. Therefore, the object configuration cache is cleared for every tree element which needs an update before the update is executed.
Pinning in tables is still active after embedded formatted text cells have been opened.
An error when resizing a table column that belongs to a prototype, changed the size of all other columns belonging to the same prototype has been fixed. Now, the column width of prototype columns can be changed separately.
Key bindings of other opened tables are deregistered on tab switch to have the correct key bindings for the active table available.
Hyperlinks are directly exported as plain text content to Excel.

12.6.4 Requirements
ID 8682711555182422106, 8682711685535942105, 8682711555195472106, 8682711685409162106, 8682711685497042105 8682711684912742101
8682711685463712105

Resolution
Various model constellations which have led to multiple roots during the ReqIF export have been identified. In these situations, artifacts that erroneously were part of the exported set are ignored and thus no longer produce the multiple roots error.
XHTML attributes having a text as default value are imported correctly via ReqIF.
The ReqIF import can handle attributes with enumeration values that have an empty or missing name.

Version 10.20

259

PREEvision 10.9

ID 8682711685535322101
8682711552408672105 8682711552922422023
8682711685246242098, 8682711686314283082 8682711554764972106, 8682711685449862106

Resolution
ReqIF export with reused test routines is now complete also if some reuses have a UUID containing the bit local reuse sequence.
The User-defined Filter correctly filters with the setting "contains not".
Layout problems in formatted texts when setting default styles for a multi-selection of OLE objects and images which are anchored at a paragraph have been fixed.
The selection propagation between Model View and tables works reliably if artifacts with empty name attributes are selected.
If the routine that converts formatted texts during the ReqIF export stops, the error log has been extended to inform about the artifact that produces this state and therefore enable better analysis and correction.

12.6.5 Logical function architecture

ID 8682711554420841992
8682711554721251992 8682711685248702196 8682711555127641992 8682711685506471874 8682711685498692196

Resolution
In the Logical Architecture System Diagram, port labels are displayed for the following ports:
> Service Provided Ports
> Service Required Ports
> Environment Sender Ports
> Environment Receiver Ports
In a Logical Architecture System Diagram, ports of Building Blocks can be connected even if one Building Block is located inside a Section and the other Building Block is outside the Section.
When creating a new logical port via a logical assembly connection in a Logical Architecture Diagram or Logical Architecture System Diagram, the new port instance takes over the name of its logical port prototype.
When connecting logical functions below Building Blocks in Logical Architecture System Diagrams across Product Lines, delegation ports are created below the Building Blocks. As a precondition, a workspace must be set in one of the Product Lines.
In a Logical Architecture Diagram or Logical Architecture System Diagram the context menu entry Open with | Ports on a bus port is available again. Via this context menu a diagram can be opened in which one of the ports is represented.
Refactoring: When carrying out the Convert Block refactoring on a logical function, additionally to creating new types, also all possible existing types are displayed

Version 10.20

260

PREEvision 10.9

Resolution

and can be selected in the Convert block dialog. On the right-hand side in the ports table, only those ports are listed which match the selected existing type.

12.6.6 AUTOSAR
ID 8682711684970511029
8682711554391981913 8682711554636281917
8682711686287891031 8682711686244821024 8682711685486411024 8682711685521492013
8682711686003892108 8682711686006172108
8682711684984612052

Resolution
ECU Extract: If an ECU Extract aborts because there are necessary artifacts outside the user's scope and loading these artifacts into scope leads to an update then the user is informed that the model is updated.
AUTOSAR export: The attribute literalPrefix of an IncludedDataTypeSet is now exported.
AUTOSAR export: The attributes allowHaltDueToClock, keySlotOnlyEnabled, keySlotUsedForStartUp, and keySlotUsedForSync of the FlexRay communication controller are now exported.
AUTOSAR export: The variant sensitive AUTOSAR export terminates properly.
AUTOSAR export: The attribute Is Service of Service Interfaces will not be exported.
AUTOSAR export: The type emitter for platform types for AR 21-11 and AR 22-11 has been corrected.
The AUTOSAR SW Component Description (improved) has been improved: The Addresing Method is not considered during export, Per Instance Memory and Constant Memory are included in the export.
The consistency check "AR_019911a" has been adapted to [constr_1175] of the AUTOSAR specification.
An "IOControlRequest" Sender Receiver Interface must have three data elements that have one of the following names: "controlState ", "underControl" or "IOOperationRequest " or "data". The corresponding consistency check has been adapted so that the alias name is no longer checked.
AUTOSAR software component update: The selection of the reference model works properly.

12.6.7 Software architecture

ID 8682711555034402108

Resolution
Initial value fields for enumeration data types according to AUTOSAR now get a dropdown widget in the Property View and tables.

Version 10.20

261

PREEvision 10.9

ID 8682711553775382052 8682711685987671029 8682711686006172108
8682711555203732108
8682711554452891807 8682711555198512108 17938311317982042 8682711684984612052 8682711685249852051

Resolution
The Data Type Package Type for the implementation data type assignment is now global.
New consistency checks insure the consistency of event data access of an Internal Behavior.
An "IOControlRequest" Sender Receiver Interface must have three data elements that have one of the following names: "controlState ", "underControl" or "IOOperationRequest " or "data". The corresponding consistency check has been adapted so that the alias name is no longer checked.
The value handling mechanism is now able to automatically take over units from data types onto the value literals. This optional functionality is controlled by a dedicated configuration flag.
For the "AUTOSAR Adaptive Product Line" creation template, the attribute Branch Name Template is changed to "not set".
For objects with referenced initial values the Constant Reference is now visible in the Property View.
The Service Deployment Editor supports the creation of multiple software instances via sequential drag and drop of service roles on a valid target.
AUTOSAR Software Component Update: problem with the selection of the reference model has been fixed.
For Application Axis Types, Calibration Access and Record Layout are displayed on the property page Data Type Configuration.

12.6.8 Diagnostics
ID 8682711685486431875 8682711685524621875
8682711686095402005
8682711686095412005

Resolution
Diagnostic export: Only conversions that are used by application data types in PVCDI are considered for export.
Diagnostic import: The attribute HealingCycleCounterThreshold is now also imported from PVCDI to EEA if there is no diagIndicator connected to the diagConnectedIndicator.
The consistency check "p1201" has been adapted. The severity has been changed from Error to Warning and the data types that are checked have been further specified.
The consistency checks "i1001", "i1002", and "i1003" have been adapted: the severity has been from Error to Warning and the error message has been extended.

Version 10.20

262

PREEvision 10.9

ID 8682711553097502113

Resolution
For Diagnostic Data Objects, details for NV Data port interface types can be defined on the Realization Requirement property page.

12.6.9 Communication
ID 8682711685475151915
8682711685475171915
8682711685475161915 8682711685475191915 8682711685475181915 8682711684983401807
8682711685250811024 8682711685328641807 8682711685440361807 8682711685475131915
8682711686007001003

Resolution
The consistency checks "p1190_PDUTransmissions_without_ ReceivingECUInterface" and "p1190_PDUTransmissions_without_ SendingECUInterface" have been adapted. No errors are reported for PDU Transmissions of a Multiplexed IPDU that are completely transmitted over a gateway.
The consistency check "C5603_multiFramedTransmission" has been adapted. No errors are reported for Signal Transmissions correctly referencing a Signal IPDU which is part of a Dynamic Part Alternative of a Multiplexed IPDU.
The consistency check "C5505_targetlessInfoMapping" no longer leads to an error for Sender Receiver To Signal Mapping artifacts that are mapped to a System Signal.
The consistency check "C5509_deafLogicalRequiredPort" no longer leads to a warning for provided SW ports.
The consistency check "C5506_muteLogicalPorts" no longer leads to a warning for required SW ports.
Signal router: Signal Transmissions and port mappings on delegation ports are properly cleaned up if they are not used anymore, that is after changes of the software architecture.
AUTOSAR import: the import wizard allows navigating forward and backward between the wizard pages.
AUTOSAR export: I-SIGNAL-I-PDU-GROUP is now correctly exported.
The property page Time Domains of Global Time Domains properly displays assigned Master Domains and Sub Domains.
Frame-PDU synthesis: As soon as parts of a multiplexed IPDU are received by a gateway, its contained PDU Transmissions are now referenced to the receiving ECU interface by the frame-PDU synthesis.
Frame-PDU synthesis: The updated PDU Transmissions and Frame Transmissions are now at the right model location after repeated runs of the Frame-PDU synthesis.

Version 10.20

263

PREEvision 10.9

ID 8682711685500121030
8682711554383211918 8682711685491722004, 8682711685486381915
8682711686234441807

Resolution
DBC export: Pure gateway frames that are not sent or received by the ECU (node based) are not exported anymore.
DBC export wizard: The DBC export wizard applies DBC export properties to all export routines.
On Node Configuration property page of CAN Tp Nodes the group Multicast has been renamed to Adress Configuration. Also, the attribute Tp Address Extension Value has been added to the group.
For CAN Clusters, additional parameters for Bus-off recovery are displayed on the property page CAN Cluster Parameters.

12.6.10 Hardware architecture

ID 1792900832696
8682711685475252083
8682711684934163104, 8682711684934153104
8682711685673902036

Resolution
The Populate of Conductors options for influencing the display of Cables and Cores during a populate have been removed from the preferences Electrologic and Harness | Wiring Editor.
If a Splice is created during wiring harness synthesis, the relation between Splice and Schematic Connection is set. Additionally, the naming convention for Cores during the creation of Cables based on wiring synthesis constraints is applied.
When creating autolayout wiring diagrams with a coordinate system, the coordinate system is taken into consideration when calculating the Section width. Especially for wide Title Blocks in narrow autolayout diagrams, the coordinate system does no longer overlap the Title Block.
When creating autolayout wiring diagrams, the labels for Wiring Connectors are displayed.

12.6.11 Geometry
ID 8682711555194112039

Resolution
The delta configuration and corresponding artifacts for the bundle diameter calculation of Topology Segments have been moved to new optional Add-in. Duplicate label definitions of Topology Segments are thus avoided.

Version 10.20

264

PREEvision 10.9

12.6.12 Product line engineering

ID 8682711685420272012
8682711685988701029

Resolution
The Product Line Health Viewer has been replaced by the more powerful External Relation Analyzer. The Product Line Health Viewer has been removed permanently.
Assets for software types only propagate artifacts via an Interface Assignment of a port and not, additionally, via type-local references, for example from communication specifications. Less artifacts are propagated than before if the model has inconsistencies. It is recommended to check for inconsistencies prior to Asset creation or refresh.

12.6.13 Change and release management

ID 8682711554916322106, 8682711685547812051 8682711684953342106
8682711684942532052

Resolution
The performance of loading the Compare Table during a model comparison has been improved.
When comparing formatted texts in the Property View of the Compare perspective, it is now possible to click into the read-only formatted text field.
When merging two artifacts, the selected identity of the surviving object (source/target) now correctly determines the order of sorted children.

12.6.14 Test engineering and test management

ID 8682711685494373126

Resolution
The drag and drop actions Move and Paste as copy without external relations for Test Routine have been enabled in the Text column of the Test Specification Editor.

12.6.15 Metrics
ID 8682711554746032012
8682711685198392111
8682711555201921207

Resolution
The Collaboration Referable Metric Executor now supports static inputs. The Model Context must be named "static".
Source code editors remains open when switching between explorer tabs, when switching the active table instance in a table, and when closing tables.
In the authority model, the Property View displays the Overwriting Model Context of Model Contexts.

Version 10.20

265

PREEvision 10.9

ID 8682711554478612041

Resolution
The transparency check for variant highlights is done in the Render Diagram metric block.

12.6.16 Reports
ID 8682711554027481992

Resolution
The entry for creating an (outdated) Report Template File has been removed from the New menu.

12.6.17 Collaboration
ID 8682711686232021791

Resolution
A commit or check-in operation that is canceled because a life cycle constraint returns an error, no longer triggers the creation of a bug report.

12.6.18 Administration
ID 8682711555144692174 8682711685522002012 8682711685295072039 8682711555163161855
8682711555024583046
8682711554418592068
8682711685422411993

Resolution
The About PREEvision dialog has been simplified.
Demo Add-ins for Dashboards are now available.
The "Warmup Metric Run" Add-in is now optional.
Add-in context menu: All items in the context menu are displayed when the mouse pointer hovers over the menu.
The automatic integration of Add-ins now correctly detects merge conflicts.
Consistency Rule Groups can contain Propagate Definitions. Propagation extensions of Propagate Definitions are now also propagated.
The API server supports the configuration of the username_claim for the OpenID Connect authentification.

12.6.19 Backup, restore, and migration

ID 8682711554488311808
8682711684937731036

Resolution
The migration error caused by an incorrect UUID handling has been resolved.
If a restore on top fails and the delta between RAMC and database is greater than a given value (default 100,000 elements), the RAMC is deleted and rebuilt.

Version 10.20

266

PREEvision 10.9

12.7 Known issues

Known issues in PREEvision 10.9

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

ID 8682711554031661036 8682711554406702203 17938307791212069
8682711552649222003 8682711554206562068 8682711555165912106 8682711555150891783 8682711555133422025

Known issue
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.
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.
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.
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.
During Add-in installation, error messages occur due to non-executable metrics. Workaround: To continue the installation, confirm the error messages with [OK].
ReqIF export: For empty attributes, the string defined in the Text for empty Labels property is exported instead of and empty string. By default, this is "---". Workaround: In the Preferences, under PREEvision | General, remove all characters from the Text for empty Labels property.
Templates, like report templates, opened with the new LibreOffice version may be shown as changed and can be saved directly, giving the impression that they have not been migrated. This apparent error can be ignored.
<Ctrl> + click on a preview image in a formatted text may not open the linked File Attachment. Workaround: Use the context menu on the preview image or double click on the File Attachment artifact in the Model View to open the file attachment.

Version 10.20

267

PREEvision 10.9

ID 8682711686247202025
8682711686179212044
8682711555191801873
8682711685521972014 8682711685521992014 8682711686356952005 8682711686392002008

Known issue
When inserting a diagram placeholder based on templates, an error message is reported that the used template is incomplete. Workaround:
1. Navigate to the selected template under Administration | Configuration File Container | Report Template Package and select the affected template file.
2. Open the location of the file in the Windows Explorer and delete the file.
3. Update from the server to force a reload of the file.
When generating a report for a diagram as PDF, an error message is reported that the report generation was not able to write any data in the Temp directory and is aborted. Workaround:
1. Navigate to the report under Administration | Report Model and select the report file.
2. Open the location of the file in the Windows Explorer and delete the file.
3. Update from the server to force a reload of the file.
During reinitialization of the authority model an error message may be displayed reporting an unexpected error with the ramc.ser file. Workaround:
1. Delete the authority model.
2. Connect to the authority model.
3. Initialize the authority model.
For Application Map Types, the Data Type Configuration property page is missing from the Property View. It will be restored in a future minor release.
For Application Curve Types and Application Cube Types, the Calibration Attributes property page is missing in the Property View. It will be restored in a future minor release.
Diagnostic export: In case of incomplete software realizations for diagnostic objects (missing relation between SW Port and diagnostic objects), these software realizations may be exported instead of an available diagnostic concept.
Filtering table columns via predefined filters: In the Predefined Filters ... dialog, the displayed number of hits for non-activated values is increasing every time the filter dialog is closed and reopened. Workaround: Deactivate the column filter and activate the column filter again, or filter for all values in the table column.

Version 10.20

268

13 PREEvision 10.8
This chapter contains the following information:
13.1 Version numbers 13.2 Installation and compatibility information 13.3 New features in PREEvision 10.8 13.4 Changes 13.5 Fixed issues
Common Diagrams Tables Requirements Logical function architecture AUTOSAR Software architecture Communication Hardware architecture Geometry Product line engineering Variant management Rules Metrics Reports Collaboration Administration Installation Backup, restore, and migration 13.6 Known issues

PREEvision 10.8
270 271 273 278 279 279 280 280 280 281 281 282 282 283 284 284 284 284 284 285 285 286 287 287 288

Version 10.20

269

13.1 Version numbers

Version numbers

Application PREEvision client PREEvision license server PREEvision database server PREEvision application server

Documentation

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

Version number 10.8.0 3.0.0 10.8.0.02 10.8.0
Version number 10.8.0 10.8.0 10.8.0 10.8.0 10.8.0

PREEvision 10.8

Version 10.20

270

PREEvision 10.8

13.2 Installation and compatibility information
For detailed information about the installation of PREEvision 10.8 and the migration to PREEvision 10.8, refer to the PREEvision operating manual.
For detailed information about the hardware and software requirements of PREEvision 10.8, refer to the PREEvision system requirements.

Severe issue resolved: Incorrect deletion of model contexts

In PREEvision 10.8, a severe issue has been resolved, which may have led to deleted Model Contexts when editing formatted texts. If you use PREEvision 10.5, 10.6, or 10.7, it is highly recommended to perform a minor release update to PREEvision 10.8.
In PREEvision 10.5, 10.6, and 10.7, when formatted texts are edited, all Model Contexts below the associated artifact are automatically refactored to Placeholder Contexts. Additionally, orphaned Placeholder Contexts, which are not used as placeholder in the formatted text, are deleted.
This may have led to data loss if the Model Contexts are not used as placeholders in formatted texts, but, for example, to define relations between model artifacts. These Model Contexts are deleted when any formatted text of the artifact is edited.
For detailed information, refer to the following presentation in the download center: Information and Workarounds Unwanted Model Context Deletion.
Contact the Vector support to provide you with a database script and metric to identify and analyze deleted Model Contexts.

System requirements

The following system requirements have been changed:
> Client requirements: If the Internet Explorer is installed as system browser, for displaying the online help, Internet Explorer version 11 must be installed.

Compatibility

Client version
10.5.0 10.6.0 10.7.0 10.8.0

Server version
10.5.0 10.6.0 10.7.0 10.8.0

Database server script version 10.5.1.41 10.6.0.02 10.7.0.02 10.8.0.02

Metamodel change ID 2022-10-05 2023-04-03 2023-06-01 2023-07-20

Migration and update

PREEvision 9.5 and 10.0 can be migrated to PREEvision 10.8.
For the migration to PREEvision 10.8, 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.

Version 10.20

271

PREEvision 10.8
> 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 or one of its following minor releases, starting with version 10.6, to PREEvision 10.8 requires no migration and can be performed as minor release update. An update of PREEvision 10.5 to a following minor release, for example, PREEvision 10.8, 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 > 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".

Version 10.20

272

PREEvision 10.8

13.3 New features in PREEvision 10.8

Working in parallel with In previous PREEvision versions, a check-out as revision fully locks all reuses, which

checked-in reuses

makes it impossible for other users to work with these reuses in parallel, for example, to

check-out as branch.

In PREEvision 10.8, a check-out as revision only locks the artifact to be checked-out. In this way, it is possible to check-out the other reuses as branch.

Handling splices for cables

The handling of splices for cores/shieldings of cables has been expanded and improved. Different ways for different use cases are supported:
Successively inserting splices into individual cores/shieldings of a cable
Splices can be inserted into individual Cores/Shieldings of a Cable successively via the diagram palette entry Splice.
When inserting a Splice into a Core/Shielding of a Cable, a duplicate of the Cable including its Cores/Shieldings is created, and the Splice is connected to the corresponding Core/Shielding.
All subsequent Splices which are inserted into further Cores/Shieldings of the Cable, are automatically connected to the corresponding Core/Shielding of the already existing Cable duplicate.

Inserting splices for all cores/shieldings of an entire cable in one step
Splices for each Core/Shielding of a Cable can be inserted in one step via the diagram palette entry Splice Group, instead of splitting each Core/Shielding of a Cable separately.

Version 10.20

273

PREEvision 10.8
Via the Splice Group palette entry, you only need to select a Core/Shielding of the Cable once, and a Splice is automatically inserted into each Core/Shielding of the Cable in one step. Specific splice feedback indicators on the individual Cores/Shieldings indicate where the Splices will be inserted.

Additionally, the refactoring Insert Splice for Each Wire is available on a single Core/ Shielding in the diagram or Model View to insert a Splice for each Core/Shielding of a Cable in one step.

Excel export of requirement specifications including images

The Excel export of table contents has been improved.
Table contents exported to Excel is not limited to unformatted text but is exported including most of the formatting as it is defined for formatted text in PREEvision. Formats supported are, for example, lists, bullet lists, font color, bold or italic font.

Table contents like images, file attachments, tables, or OLE objects contained in formatted text are exported and displayed in Excel on separate Excel sheets.

Version 10.20

274

PREEvision 10.8
The different Excel sheets can be reached via attachment hyperlinks provided in an extra table column on the main Excel sheet. The navigation back from the separate Excel sheets to the main Excel sheet is also supported via hyperlinks.
File attachments can be directly opened from within the corresponding Excel sheet via a file attachment link. File attachments are stored in a folder next to the exported main Excel file.

Version 10.20

275

PREEvision 10.8
The content of tables within formatted text is properly exported and displayed in the Excel table on the corresponding separate Excel sheet.
Data formats like OLE objects are wrapped in RTF files. This ensures the display of preview images of OLEs independent of the underlying software which is needed to edit the OLEs. The hierarchy of a package structure in PREEvision can be displayed in the exported Excel file via indentation. Hierarchy levels can be set via column configuration on a table column in PREEvision and are then displayed via indentation according to the hierarchy groups in Excel.

Version 10.20

276

PREEvision 10.8

Table export block

The Excel export Table Export metric block can now handle table template artifacts from the Admininstration. Via the metric, batch operations for the Excel export can now be carried out. A new input port "tableScopeArtifact" has been added to provide the artifact on which the table is exported into Excel.

AUTOSAR multiversion support

A multi-version support of AUTOSAR releases in PREEvision allows the support of several non-backward compatible AUTOSAR versions. The new AUTOSAR versions supported for AUTOSAR Classic and Adaptive are 21-11 and 22-11.

AUTOSAR software component description

In addition to the standard AUTOSAR software component description export, an improved software component description is available, AUTOSAR SW Component Description (improved).
This new export offers the following improvements:
> better performance, up to 50 % for large models
> improved error handling for hidden artifacts and artifacts with read-only rights
The new AUTOSAR software component description export will finally replace the previous export in PREEvision 10.11.

Version 10.20

277

PREEvision 10.8

13.4 Changes

Deprecated metric blocks

The following metric blocks of the product line engineering are no longer supported with PREEvision 10.8: > Asset Integration Model Calculator > Asset Integration Model Integrator > Asset Reverse Integration

Deprecated product line engineering features

The Product Line Health Viewer has been replaced with the External Relation Analyzer since PREEvision 10.5 and will no longer be supported with PREEvision 10.9.

Version 10.20

278

PREEvision 10.8

13.5 Fixed issues

Fixed issues in PREEvision 10.8

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

Further information

> Common > Diagrams > Tables > Requirements > Logical function architecture > AUTOSAR > Software architecture > Communication > Hardware architecture > Geometry > Product line engineering > Variant management > Rules > Metrics > Reports > Collaboration > Administration > Installation > Backup, restore, and migration

13.5.1 Common
ID 8682711685314021995
8682711553600482041, 8682711553775342052, 8682711684912722045, 8682711685338592068, 8682711553961961038 8682711685246322034
8682711554733332014, 8682711684958012101 8682711684937883054
8682711555165072024

Resolution
When editing formatted texts, Model Contexts that are not used as placeholders in the formatted text are no longer deleted.
In the Information View, displayed icons no longer overlay the text.
The action Window | Reset all Perspectives to Model Definitions properly resets all perspectives.
Model export: The log output for tree artifact collisions is disabled by default to prevent client freezes.
The artifacts that are displayed by Query Rule Group extensions in the Model View are properly refreshed when changing the perspective or restarting the client.
Moving several selected artifacts before or after an artifact in the Model View maintains the order of the selected artifacts.

Version 10.20

279

PREEvision 10.8

ID 8682711685348732042

Resolution
In the PREEvision system requirements, the following client requirement for the Internet browser has been added: If the Internet Explorer is installed as system browser, for displaying the online help, Internet Explorer version 11 must be installed.

13.5.2 Diagrams
ID 8682711554779911994, 8682711554729512041
8682711684925282046
8682711684951892046

Resolution
Diagrams which are displayed in the Search result view via the context menu Show diagrams in Search View, are propagated to the Model View when selecting a diagram in the Search result view.
A highlighting is no longer calculated for deactivated elements in diagrams. This prevents resulting errors.
The Child Area Graph Node for background images is removed when the object configuration of the background image is removed.

13.5.3 Tables
ID 8682711554492202024
17938311332152098 8682711554888343082

Resolution
If a create action is executed on a table cell that has no children, the table is refreshed and shows the newly created artifact.
The table selection is maintained if an artifact that is not contained in the table is selected in the Model View.
If you select multiple artifacts of different meta classes and different parents in the Model View and open them in a table via Open with, the artifacts are ordered by meta class.

13.5.4 Requirements
ID 8682711554894201783
8682711554829312084, 8682711554750572105, 8682711685443922105

Resolution
ReqIF export: Formatted texts containing tables that are aligned right via the table properties are exported in a schema valid way.
ReqIF export: Formatted texts containing specific list structures are exported in a schema valid way.

Version 10.20

280

PREEvision 10.8

ID 8682711555127671783
8682711553529641783 8682711555203942023
8682711555129181038 8682711552408672105

Resolution
ReqIF export: Formatted text containing two following ordered lists is exported in a schema valid way. The list start level which has caused a schema violation and is not supported by the ReqIF schema is no longer exported.
ReqIF export: Formatted text containing text tables which have been manually adjusted in size are exported in a schema valid way.
ReqIF export: If a requirement contains a defective placeholder, the ReqIF Agreement Export does not abort anymore. Defective placeholders are diagram, table, or chart placeholders that reference an artifact that is no diagram, table, or chart, but, for example, an ECU. Defective placeholders are not exported.
The performance of the Excel export of requirement specifications has been significantly improved.
The User-defined Filter correctly filters with the setting contains not.

13.5.5 Logical function architecture

ID
8682711554725130000, 8682711685346102113

Resolution
The synchronization of names between port instance and port type works now in the Logical Function Architecture layer if only one instance is available and the option is activated.

13.5.6 AUTOSAR
ID 8682711552506261029
8682711553537611024
8682711554188122004 8682711554631081058 8682711554395361029

Resolution
AUTOSAR export: Handling of read-only artifacts during ECU extract or SW component description export (improved) has been corrected.
Process Designs of Service Instance To Port Prototype Mappings are considered when exporting or importing Software Cluster Designs.
ECU extract: Value Specifications under the port types are exported correctly.
Software cluster design description: the software cluster design description exports only the relevant Signals.
In the Property View of port types, the tables on The Port Communication Specification page include columns for RAM and ROM initial values and show NV Data.

Version 10.20

281

PREEvision 10.8

ID 8682711554455871807
8682711684910190063 8682711685226072051
8682711685296732108

Resolution
When creating an AUTOSAR Adaptive Product Line, the packet Service Interface Transformation is also created. Missing Root Compositions are indicated by a tooltip.
Data Constraints of an implementation data type element of the category "reference" are exported correctly.
The consistency check "c1221_DataTypedInformationUnit_with_invalid_Applicati onValueType_InitValue" has been adapted to correctly work with Application Enumerations.
In the AUTOSAR export wizard, model elements are now selectable on second wizard page.

13.5.7 Software architecture

ID 8682711555127633013
8682711554918561909 8682711554721252014

Resolution
The consistency check "p1169_VirtualPackagePart_without_VirtualPackage" will not hit for a Constant Reference without Virtual Package, but the consistency check "p1169_VirtualPackagePart_with_illegal_VirtualPackage" will now hit for a Constant Reference with a referenced Virtual Package.
The Consistency Rule to check if the attribute Period of Timing Events is set correctly works as expected.
The value handling mechanism sets the attribute "Category" to "Value" on Application Literals typed by an Application Value Type.

13.5.8 Communication
ID 8682711554535451918 8682711554884531810 8682711555144622043
8682711555114232043 8682711554492261003

Resolution
DBC export: Minimum and maximum values of application data types are correctly exported.
Signal router: VLANs of existing service instances are considered during signal routing over Ethernet.
Signal router: The signal router also considers System Signals when looking for existing and correctly routed signal transmissions in gateway scenarios.
Signal router: When routing port groups the Information View informs about reachable and unreachable targets.
Signal router: Application data types are not set for Signal Groups and the contained Signals during signal routing.

Version 10.20

282

PREEvision 10.8

ID 7883112550092273727, 8682711554687372051 8682711554421291807
8682711554601572159 17938311447942004

Resolution
Ethernet: The calculation of Fire and Forget Methods without argument has been improved in the SOA & Ethernet Explorer.
The creation of Socket Connection IPDU Identifiers has been improved. Socket Connection IPDU Identifiers are only assigned to a So Ad Routing Group if the identifier belongs to the same Service Instance as the routing group's Event Handler (for events) or to the same Service Instance as the routing group itself (for methods). The routing group name now also includes the name of the Service Instance it belongs to.
The frame-PDU synthesis removes ECU interfaces of IPDUs contained in a Container IPDU if it is fully transmitted over a Gateway.
When synthesizing the communication infrastructure in the Diagnostic Communication Explorer, cluster assignments are properly created and updated for Do Ip Tp Configurations.

13.5.9 Hardware architecture

ID 17938288953319012 8682711554395341874
8682711555198611037 8682711555202122196
8682711555173511268

Resolution
To assign a Connector Type to a Wiring Connector, a refactoring is available in the context menu of a Splice.
When using the refactoring Create Missing Wiring Connectors for a Header which already has assigned a Wiring Connector, a dialog is opened. In the dialog you can decide to either cancel the refactoring or create Wiring Connectors for Headers only which do not have assigned a Wiring Connector. Similarly, Wire Pins which are not assigned to a Wiring Connector are assigned to the proper Wiring Connector.
Components in a Wiring Diagram can be moved or resized up to the edge of the diagram Section, independent of the diagram zoom factor.
When carrying out the Resolve Splices refactoring on a Schematic Connection, the Resolve Splices dialog properly displays the Schematic Pins to select the target pin also in case the Splices to be resolved have a relation to the Schematic Connection.
The palette entries Gateway and Software Gateway have been removed from the Component Diagram.

Version 10.20

283

PREEvision 10.8

13.5.10 Geometry
ID 8682711554907222083

Resolution
The Cut, Copy and Move action for template diagrams (Connector Template Diagram and Hardware Device Template Diagram) has been disabled. Instead, a special paste metric has been implemented to copy the diagrams and set the proper represented artifact relation to the target artifact afterwards.

13.5.11 Product line engineering

ID 8682711554536752046
8682711554768852100

Resolution
A checkout of Assets during cluster update is prevented in case of overlapping artifacts.
Assets can be updated if a core artifact to be updated is referenced upstream in an invisible foreign Asset.

13.5.12 Variant management

ID 8682711553517111998
8682711554764721995

Resolution
The Consistency Rule that is checking if artifacts are compliant to AUTOSAR pre-/post-build variant conditions has been updated.
The selected filter in the Set Content View is persisted.

13.5.13 Rules
ID 17938311673332049
8682711554024192106

Resolution
The Consistency Check Results view displays tooltips when moving the mouse over a message in the view. Therefore, the Tooltip must be defined on the Localization of the Consistency Rule.
Changes in a Query Rule Diagram, such as renaming an object, are directly displayed in the Outline view.

13.5.14 Metrics
ID 8682711555117411848
8682711555198482100

Resolution
The Update Metric Block action only creates a new port representation in the Metric Diagram if the port is also missing in the model.
A NullPointerExecption that occurred in the Property View during metric execution has been fixed.

Version 10.20

284

PREEvision 10.8

ID 8682711555153612046
8682711685447682084

Resolution
Newly created artifacts can be deleted in a pre-commit hook.
Model Contexts or Placeholder Contexts with out-ofscope or invisible context artifacts are now handled correctly by the Cleanup Placeholder metric block.

13.5.15 Reports
ID 8682711684953922112

Resolution
After large pages in PDF exports, for example, for large diagrams, the page scaling factor of the following pages is correctly handled.

13.5.16 Collaboration
ID 8682711554417533082, 8682711684915512106 8682711555117312076
8682711555122151790 8682711555127672112
8682711554778402100
8682711555198482101, 8682711685290821995 8682711685463701993 8682711555162831229
8682711555190372070

Resolution
Reusing from the Version History via drag and drop is possible again.
Loading the Version History can only be started once per client. An error message is displayed if the [Load Version History] button is clicked while another version history is currently being loaded.
Commit History entries which are older than the requested artifact are not displayed.
The check-out of an artifact does not lock all reuses of the artifact anymore. Instead, the check-out creates a revision and only locks the artifact to be checked-out. In this way, it is possible for other users to work with the reuses in parallel and, for example, check-out the reuses as branch.
Changing access rights, for example from invisible to visible, on a scope root artifact is properly handled. All scope root artifacts are always known on server and client side and are no longer filtered on the server-side scope cache.
An error in the initialization of the model cache (RAMC) during client startup has been resolved.
Update requests no longer block the system because large updates are loaded from the database.
Fixed bug in Life Cycle transition evaluation handling for attribute value checks with multiple transition extension parameters.
Artifacts whose Life Cycles cause Life Cycle transitions to fail are now reported.

Version 10.20

285

PREEvision 10.8

ID 8682711555203531229

Resolution
Tables can now be created using the context menu under the following artifacts: Lifecycle States, Life Cycles, and Lifecycle Packages.

13.5.17 Administration
ID 17938311719341204 8682711553989402102
8682711554632482064 8682711554779451225, 8682711554636281897 8682711554779851806
8682711555022821028
8682711555164282102
8682711555186351217 8682711555191602102
8682711684912363046
8682711684973372011, 8682711554636332068 8682711554640422203 8682711555186071993

Resolution
Query Rule Group icons set via object configuration are now part of the Add-in propagation.
A single Query Rule Group set as a filter configuration for the model view in an explorer is now part of the Add-in propagation. There is no propagation if multiple Query Rule Groups are set as filters.
Add-ins delivery: Improved error reporting if installation mode or scope is active.
After Add-in installation, updates from server are properly loaded.
In the "Configuration" Add-in, unnecessary core relations to Source Codes which prevented Calculation Blocks from being deleted have been removed.
The check-out and check-in behavior of Add-ins during Add-ins installation has been corrected: Add-ins contained in the *.addins file of the installation are checked-in after installation.
The Add-in propagation of Diagram Settings now includes the Perspective Configuration, but does not propagate the Perspective Configuration itself.
Installation of default Add-ins is again possible without manual check-in of artifacts before installation.
The Add-in propagation of tables now includes Collaboration Referable Metric Executors in addition to Embedded Metric Executors for column actions, toolbar actions, and for metric executors that are direct children of a table.
When customizing Add-ins, Add-in-internal relationships to singletons that are not directly contained in the Add-in but indirectly through their parent are no longer lost.
Add-ins installation: Improved Information View error reporting.
Initializing a server model with a file is possible when using a role with restricted access rights.
In the Model Management view, the download of all bug reports from the server is possible again.

Version 10.20

286

PREEvision 10.8

13.5.18 Installation
ID 8682711554631081872

Resolution
Unnecessary installation scripts of the monitoring server have been removed from the PREEvision collaboration platform delivery.

13.5.19 Backup, restore, and migration

ID 8682711685397011036
8682711685315831036

Resolution
Function Groups of moved Component Deployment Packages are properly handled during restore.
Migration error caused by already existing item in repository has been resolved.

Version 10.20

287

PREEvision 10.8

13.6 Known issues

Known issues in PREEvision 10.8

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

ID 8682711554031661036 8682711554406702203 17938307791212069
8682711552649222003 8682711554206562068 8682711555165912106 8682711555150891783 8682711555133422025

Version 10.20

288

PREEvision 10.8

ID 8682711555191801873
8682711685521972014 8682711685521992014

Version 10.20

289

14 PREEvision 10.7
This chapter contains the following information:
14.1 Version numbers 14.2 Installation and compatibility information 14.3 New features in PREEvision 10.7 14.4 Changes 14.5 Fixed issues
Common Diagrams Tables Requirements Logical function architecture AUTOSAR Software architecture Diagnostics Communication Hardware architecture Geometry Product line engineering Rules Reports Collaboration Administration Installation License Backup, restore, and migration 14.6 Known issues

PREEvision 10.7
291 292 294 298 299 299 300 300 301 301 301 302 303 303 304 305 305 306 306 306 307 308 308 308 309

Version 10.20

290

14.1 Version numbers

Version numbers

Application PREEvision client PREEvision license server PREEvision database server PREEvision application server

Documentation

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

Version number 10.7.0 3.0.0 10.7.0.02 10.7.0
Version number 10.7.0 10.7.0 10.7.0 10.7.0 10.7.0

PREEvision 10.7

Version 10.20

291

PREEvision 10.7

14.2 Installation and compatibility information
For detailed information about the installation of PREEvision 10.7 and the migration to PREEvision 10.7, refer to the PREEvision operating manual.
For detailed information about the hardware and software requirements of PREEvision 10.7, refer to the PREEvision system requirements.

Deleted model contexts when editing formatted texts

PREEvision 10.7 contains a severe issue which may lead to data loss:
When formatted texts are edited, all Model Contexts below the associated artifact are automatically refactored to Placeholder Contexts. Additionally, orphaned Placeholder Contexts, which are not used as placeholder in the formatted text, are deleted.

This may lead to data loss if the Model Contexts are not used as placeholders in formatted texts, but, for example, to define relations between model artifacts. These Model Contexts are deleted when any formatted text of the artifact is edited.

The issue has been resolved in PREEvision 10.8. Therefore, it is highly recommended to perform a minor release update to PREEvision 10.8.

For detailed information and possible workarounds, refer to the following presentation in the download center: Information and Workarounds Unwanted Model Context Deletion.

Contact the Vector support to provide you with a database script and metric to identify and analyze deleted Model Contexts.

LibreOffice update

The internal LibreOffice component has been updated for easier maintenance and better functional support within PREEvision.

Compatibility

Client version
10.5.0 10.6.0 10.7.0

Server version
10.5.0 10.6.0 10.7.0

Database server script version 10.5.1.41 10.6.0.02 10.7.0.02

Metamodel change ID 2022-10-05 2023-04-03 2023-06-01

Migration and update

PREEvision 9.5 and 10.0 can be migrated to PREEvision 10.7.
For the migration to PREEvision 10.7, 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.

Version 10.20

292

PREEvision 10.7
An update of PREEvision 10.5 or 10.6 to PREEvision 10.7 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.7, 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 > 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".

Version 10.20

293

PREEvision 10.7

14.3 New features in PREEvision 10.7

ReqIF import: restrict link repair to selected product line

During the ReqIF import, the automated closing of links is now limited to links or associations having source and target in the import Product Line. This is the Product Line where the actual data (for example, requirements or test data) is imported into.
If there are relations imported with source or target in a different Product Line, a new action can be used to close these links. The action Resolve open ReqIF Links can be found in the Refactoring menu and can be executed on Product Lines.
The Information View shows all created links and relations and therefore can also be used as an analysis tool.

Improvements for KBL

More than 100 new online checks support the modeling from start to the file export via KBL. And the existing online checks were consolidated in function, naming, and error message.
Also, KBL files are instantly validated during import. Violations of the schema are indicated in the import wizard as well as in the Information View.

Inserting a common splice into several single wires

Inserting Splices into existing Single Wires via diagram palette has been improved. You can insert a common splice into multiple single wires using the Splice action in the diagram palette:
1. Select the Splice action in the diagram palette.
2. Hold <Ctrl> to select multiple Single Wires. Selected Single Wires are highlighted in yellow, valid selectable Single Wires are highlighted in blue.

3. Press <Enter> or release <Ctrl> before selecting the last wire to insert the Splice.

Version 10.20

294

PREEvision 10.7
The Splice for the selected Single Wires is aligned with the bold highlighted Single Wire.

Only Single Wires that reference the same Schematic Connection are valid. Cores or Shieldings are not supported.

Asset integration

Automatic asset integration has been enhanced for Assets containing artifacts that are

support of model cycles linked to themselves via a relation cycle in the model. Typical examples are artifacts like

variants that represent alternatives which as such are linked by to-1 relations.

As calculated by the integration task, the tables of the redesigned Asset View display the cycle and its artifacts in the To Integrate columns, and the target cycle and its artifacts for the integration in the Integration Target columns. Cycles can be integrated in a

similar way to artifacts by using the context menu or the cell action.

Version 10.20

295

Icon facelift

PREEvision 10.7
The icons have been converted to flat design for a more modern and fresh appearance of PREEvision. Flat design means no gradients and mostly no outlines around the icons. All icons have also been provided in a higher resolution for high-resolution monitors.

Improvements for tables

The following improvements have been introduced for tables:
> In the Add/Remove/Reorder Columns dialog, the Search for list has been added and helps finding the right content.

> The display name of table artifacts is extended by "Proxy" or "Instance" after the name of the table template. In this way, you can quickly identify and characterize the table.
> New icons have been introduced for table filters.

Version 10.20

296

PREEvision 10.7
> If a table is opened and a filter is applied that does not match any artifacts, a message is displayed informing you that the filter has been deactivated because no artifacts were found with these filter criteria.

> When dragging and dropping an artifact in a table, it is now possible to scroll the table vertically even during the drop action.

Improvements for life cycles

The following features have been added to the life cycle framework: > Events on custom attributes such as value changes can be used to trigger life cycle
transitions > Definition of display and execution orders (priorities) of life cycle transitions. > Prioritized evaluation of life cycle transitions until a valid target state is found.

> Initial life cycle state for copied artifacts.
> Improved reporting of life cycle transition results and errors in the Information View.
> Life cycle transition constraints can be defined directly in the E/E model using metrics and consistency checks.

Version 10.20

297

PREEvision 10.7

14.4 Changes

Deprecated metric blocks

The following metric blocks of the product line engineering are deprecated and will no longer be supported with PREEvision 10.8: > Asset Integration Model Calculator > Asset Integration Model Integrator > Asset Reverse Integration

Version 10.20

298

PREEvision 10.7

14.5 Fixed issues

Fixed issues in PREEvision 10.7

You will find the important fixed issues in the following tables. Please note that some 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 > Rules > Reports > Collaboration > Administration > Installation > License > Backup, restore, and migration

14.5.1 Common
ID 8682711554778461918 8682711554645241202 8682711554436712051
8682711554653672036
8682711554395712101 8682711554525532100

Resolution
Attribute Conventions can now be correctly applied to a greater number of checked-in artifacts without an exception.
Within the Compare Table, the right side of the table is sorted in the same way as the left side of the table.
When filtering attributes in the Compare Table with the Filter Attribute action, UUID and XMIID remain. Opening the Filter Metaclass Dialog overwrites the filtering of the Filter Attribute action.
Rules are found correctly within the Label Configuration view when having a different revision. An obsolete warning tooltip as well as warning icon are not displayed anymore.
Checks have been added to avoid exceptions when opening portlets.
User-defined graphic styles that are also used in the Rich Text Template File are displayed in the Styles and Formatting view.

Version 10.20

299

PREEvision 10.7

ID 8682711554380242101

Resolution
When editing formatted texts, the context menu shows sub menu entries again, for example, Paste Special | Unformatted Text.

14.5.2 Diagrams
ID 8682711554636202083 8682711554045482083
8682711554779991994 8682711554746131030

Resolution
The size adjustment of multiple objects in a diagram is now done with reference to the first selected element.
The creation date and the printing date in the Title Block of a diagram is formatted according to the client language settings. The formatting is depending on the client language when the Diagram Configuration is assigned.
The text that is displayed in the diagram Title Block considers the width specified in the header.
Software Architecture System Diagrams and Rule Diagrams that contain pictures can be opened again.

14.5.3 Tables
ID 8682711553603532111
8682711554258142001 8682711553438612049 8682711554380541914 8682711554421082113 8682711553506812050
8682711554653783046
8682711554773281030
8682711554743592112

Resolution
Dependent columns are refreshed when the suborder changes, even if the column data is provided via search rules.
A table scrolls automatically when drag and drop is executed by the user.
Showing previously hidden columns triggers data calculation of columns.
Metric based filters are working in combined tables.
The Add/Remove/Reorder Columns dialog is working for all tables in a combined table editor.
The configuration of own filters for relations in the Property View is also possible if only a special filter is available for the drop-down list.
Right click in a table cell with TableCellContent no longer loses the selection but correctly opens the context menu.
The Excel export of large tables works properly. To improve performance, formatted texts are automatically loaded from the server before the export.
Switching the input of an explorer works properly if the explorer is used in a portlet.

Version 10.20

300

PREEvision 10.7

ID 8682711554536262113

Resolution
Opening an explorer via the Open Editor in Area metric block with a given explorer category as input no longer reports a cancel message in the Information View.

14.5.4 Requirements
ID 8682711554019072106
8682711554725091877
17938309277132049, 8682711552960532049, 8682711554032522101

Resolution
The settings of the Requirement Text Editor and the Test Specification Editor are changed to immediately react to variant information changes.
ReqIF export: Corrupted placeholders which expect a diagram but reference an artifact that is not a diagram (for example a requirement) no longer block the ReqIF export. These corrupted placeholders are skipped during the export.
Open ReqIF links are only resolved inside the target product line of an import. A refactoring is available for manually resolving open ReqIF links in several product lines.

14.5.5 Logical function architecture

ID 8682711554724970000
8682711554725130000

Resolution
The selection propagation works properly for artifacts in the Logical Architecture System Diagram.
The synchronization of names between port instance and port type works properly in the Logical Function Architecture layer if only one instance is available.

14.5.6 AUTOSAR
ID 8682711555022882003
8682711553517101998
8682711555034332051

Resolution
A new consistency check is available that checks for application data types that are not supported by AUTOSAR.
The Consistency Rule has been corrected that is checking if artifacts are compliant to AUTOSAR pre-/ post-build variant conditions.
The AUTOSAR import can handle ARXML files that contain a non-supported port interface. The import will be aborted with a posting in the Information View explaining which interfaces in the ARXML file is not supported by PREEvision.

Version 10.20

301

PREEvision 10.7

ID 8682711554737861998
8682711554452501003
8682711554640571917
8682711554636341917 8682711553505000000 8682711554639061998 8682711554733522014

Resolution
AUTOSAR ECU extract: a transformation error when exporting certain configuration of the transport layer has been resolved.
AUTOSAR ECU extract: both source Signal und target Signal of signal mappings which corresponds to Signal Gateway Routing Entrys are exported.
AUTOSAR ECU extract: SYNC-DATA-ID-LISTs for FlexRay Global Time Domain properties are now exported.
AUTOSAR ECU extract: the attribute ALLOW-DYNAMICL-SDU-LENGTH of FlexRay transmissions is exported.
AUTOSAR ECU communication extract: LIN slave configurations are now correctly exported.
AUTOSAR Export: the export can handle models containing non-supported application data types.
AUTOSAR Export: string literals used as Init Value are exported as APPLICATION-VALUE-SPECIFICATION.

14.5.7 Software architecture

ID 8682711554417442013
8682711554383191029 8682711554417372014 8682711554601843013 8682711554724980000 8682711554685602014 8682711554725080000

Resolution
The required parts for the automatic creation of application data type to implementation data type mapping, which are used for data types in the new Primary Editors are available in a specific non-mandatory Add-in.
The required parts for handling initial values are available in a separate Add-In and can therefore be comfortably customized.
The required parts for configuring the content assist and content assist with value handling are available in specific non-mandatory Add-ins.
A new consistency check is available that checks for an empty Category of an Application Literal.
The context menu item to start the Show/Hide Ports dialog is available in Software Architecture System Diagrams.
The Add-in Software Design Explorer contains all necessary metrics to show or hide specific table columns.
A problem with the Show/Hide Ports dialog in the Software Architecture System Diagrams has been resolved.

Version 10.20

302

PREEvision 10.7

ID 8682711554440462043 8682711554383201029 8682711554654372014 8682711554918441913
8682711554193182051 8682711554608382051

Resolution
The Selection Dialog which is shown if the option Select artifacts to be populated is activated within the Populate Artifact dialog of a Software Instance Diagram has been resolved.
When using the value handling feature, initial values can be properly set in the Property View although the data type might not yet be supported.
The new Add-in "Content Assist with Value Handling" allows an enhancement of the combined use cases of setting values more easily and having an additional content assist in Property View fields or cells in a table.
The Mapped Implementation Data Types Assignment refactoring does not dereference DataTypeMappingSet with a child ModeRequestImplementationTypeMapping anymore.
When dereferencing an Assembly Connector from a port, lower bound violations are now properly recognized for relations which are lower bounded and ordered.
A new consistency rule checks if an internal behavior references a software implementation since some attributes of the software implementation are mandatory for the RTE generation.

14.5.8 Diagnostics
ID 8682711554951091992

Resolution
The metric "Create communication infrastructure" in the Diagnostic Communication Explorer creates now TP ECUs while the diagnostic communication for CAN is synthesized.

14.5.9 Communication
ID 17938309309891810
8682711554746241807
8682711554825971825

Resolution
The "Create Service Instances" metric is available and executable on all subclasses of the abstract class AbstractECUInstance.
The signal router has been fixed to avoid stack overflows when routing a Composition with minimum a receiving port and a delegation port to a child Composition.
The signal router has been fixed, so that no exception is thrown, if a Bus System is in a different Product Line as the Bus Connector itself, and the signal router option Artifacts outside the current used product line are also considered is deactivated.

Version 10.20

303

PREEvision 10.7

ID 8682711554197230000 8682711554471301913
8682711553615190000
8682711553036581807 17938309307981810 8682711552912970000 8682711554635631917 8682711554194041807

Resolution
The signal router creates new Signals in case that signal transmissions for a different Bus System already exist.
The signal router better handles must-use conditions: outgoing edges are not blocked in case a must-use condition is set for an incoming edge that is part of current path.
For signal-driven communication design, the signal router does not delete signal transmissions with rx/tx associations or signal transmissions that are part of a network management PDU.
The overall routing costs of a routing group reflects the sum of the individual routing path costs.
Hidden artifacts in the VLAN-ECU Allocation table are handled properly.
Explanation of the behavior and usage of the Force 1939 Protocol check box has been added in the user manual.
DBC export: Very big numbers, such as "4123123123", are supported for signal table values during DBC export.
Several metrics and tables in the SOA & Ethernet Explorer have been fixed to support all subtypes of AbstractECUInstance as well as InternalBusConnectors, too.

14.5.10 Hardware architecture

ID 17938309312192083
8682711553104622062 8682711554636282083

Resolution
When using the refactoring Synthesis of Cavities for Connector Prototype and Instances on Connector Types, and the assigned Connector Prototypes do already have instances (Wiring Connectors), the Wire Pins connected to the Wiring Connectors are assigned to newly created Contactings. If the pin number of the Wire Pin does not match the cavity number of the Cavity Prototype, a message is reported in the Information View. In case of an empty cavity number of a Cavity Prototype, a message is reported in the Information View as well.
In a Wiring Diagram or Wiring System Diagram, a drag and drop of a Schematic Pin which is already represented in the diagram is not possible, independent of whether the <Shift> key is pressed or not. The same Schematic Pin cannot be represented multiple times in the diagram.
When connecting two Schematic Pins in a Wiring Diagram or Wiring System Diagram with a Single Wire, and the Schematic Pins already have assigned a Schematic Connection, the Schematic Connection which is selected via Connect with existing Schematic

Version 10.20

304

PREEvision 10.7

ID 8682711554871871918 8682711554644211795 8682711554607863084
8682711554197151807

Resolution
Connection in the Create or Connect a Schematic Connection dialog is assigned to the Schematic Pins connected by the Single Wire.
The electric circuit synthesis creates the additional Schematic Pins for the new Bus Connector and extends the existing Schematic Connections to the new Bus Connector.
Pin Type Families can also be assigned to Wire Pins via drag and drop in the Model View and in tables.
Note the following hints for influencing the routing behavior of the Wiring Harness Router:
> In general, it is sufficient to set one condition to control a routing path.
> If there are several possible routing paths and the router is influenced by other conditions, it is possible that the Wiring Harness Router cannot find a route. Then it might be necessary to set another condition to determine the exact desired routing path.
In the Network Diagram, the names of Execution Contexts, Backend Servers, Actuator Sensors, Terminators, Diagnostic Testers, Hardware Hypervisors and Software Hypervisors can be initially set.

14.5.11 Geometry
ID 8682711553678172062
8682711554748981912

Resolution
The refactoring Insert Branch-Off has been removed from the context menu of a Topology Segment in the Model View. On a Topology Segment in a Geometry Diagram, the refactoring can still be carried out via the context menu.
Topology Inline Connectors are properly displayed in a Geometry Diagram and are movable after the refactoring Switch from classical representation to type-based representation.

14.5.12 Product line engineering

ID 8682711554646142046
8682711554631992046

Resolution
The calculation of the Asset cluster also works if the type of the core artifact in the upstream Product Line has been changed.
New child Assets that need to be checked out during asset update with substitution are now correctly checked out to the branch of the target Product Line.

Version 10.20

305

PREEvision 10.7

ID 8682711555191592104

Resolution
In the Cached Historic Product Lines dialog, for baselines in read-only mode the status display has been corrected.

14.5.13 Rules
ID 8682711554200902062 8682711554024192106 8682711554016842012

Resolution
The graphical outline of Rule Diagrams is displayed correctly.
Changes in a Rule Diagram, for example renaming an object, are displayed in the Outline view.
The new online check "InvalidIterationType" is available for modeling rules. It checks for the iteration type "maximal", which is not supported. If "maximum" is set, the iteration is performed with the setting "normal".

14.5.14 Reports
ID 8682711551949032109
8682711554440602106

Resolution
User fields created by placeholders are deleted on save if they are no longer utilized in the report.
When loading a report with many tables, an algorithm to ensure the uniqueness of table names in a report has been optimized.

14.5.15 Collaboration
ID 8682711554778442099 8682711554782112076 8682711554740452099
8682711554773241877
8682711554458052101 8682711554418942023

Resolution
The performance of various collaboration use cases has been improved especially after large commits.
Loading the Commit History can only be started once per client.
The performance of reading the Commit History of an artifact with many non-versioned child artifacts has been improved.
Commit and check-in performance has been improved for use cases that involve a large number of changed artifacts via replace with revision and asset updates.
The commit performance has been improved especially for commits with imported artifacts.
The number of saved check-in and commit comments has been increased to 25.

Version 10.20

306

PREEvision 10.7

ID 8682711555114172101 8682711555153531038 8682711555182422196

Resolution
Deleting and moving artifacts no longer leads to an update error.
An update error has been fixed that could occur in models with invisible reuses.
Moving an open diagram into another package no longer leads to a commit error.

14.5.16 Administration
ID 8682711554440621029 8682711554519351868
8682711554644941202 8682711554645581003, 8682711554645251202 8682711554646552203
8682711554685563017 8682711554829321993
8682711555023072039 17938309244531030 8682711555127692112 8682711555145012071

Resolution
The Add-ins installation has been enabled to update reuses with external relations in the target system.
An error message is displayed in the Information View when target artifacts of an Add-ins installation are checked out. The artifacts are listed in the error message.
In the Add-In Update Table, a context menu entry for the update of a customized Add-in has been added.
Context relations between successor artifacts and singleton artifacts are copied during Add-in customization.
The number of log messages in the server log file has been reduced in case that a central component is not available.
The Add-in Artifacts Without Branch Suffix table can be opened for all types of Add-ins.
After a failed login attempt on a remote server in the administration panel, a meaningful error message is displayed.
NullPointerException check added to Add-ins installation. The result is logged.
Events on custom attributes such as value changes can be used to trigger life cycle transitions.
Life cycle transition constraints can be defined directly in the E/E model using metrics and consistency checks.
Consistent with the client, the API server does not prevent all lifecycle transitions, only those that return errors from constraint metrics.

Version 10.20

307

PREEvision 10.7

14.5.17 Installation
ID 8682711553650752017

Resolution
Unused internal properties have been removed from the deploy.properties file.

14.5.18 License
ID 17938308083402101

Resolution
The license selection dialog works properly even if only one named license is assigned to a user.

14.5.19 Backup, restore, and migration

ID
8682711555129881806, 8682711554746071036
8682711554016791036

Resolution
Several issues have been fixed for backup, restore, and migration for certain model constellations.
An incremental backup is now possible without errors even if the model preparation was not executed for all model versions. The model preparation is now executed together with the incremental backup.

Version 10.20

308

PREEvision 10.7

14.6 Known issues

Known issues in PREEvision 10.7

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

ID 8682711685314021995
8682711554031661036 8682711554406702203 17938307791212069 8682711552649222003

Known issue
When formatted texts are edited, all Model Contexts below the associated artifact are automatically refactored to Placeholder Contexts. Additionally, orphaned Placeholder Contexts, which are not used as placeholder in the formatted text, are deleted. This may lead to data loss if the Model Contexts are not used as placeholders in formatted texts, but, for example, to define relations between model artifacts. These Model Contexts are deleted when any formatted text of the artifact is edited. Workaround: For artifacts that contain Model Contexts that are not used as placeholders in formatted texts:
1. Before editing any formatted text of the artifact, move the Model Contexts to another artifact.
2. Edit the formatted text.
3. Move the Model Context back to the original artifact. The issue has been resolved in PREEvision 10.8. Therefore, it is highly recommended to perform a minor release update to PREEvision 10.8.
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.
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.
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.
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.

Version 10.20

309

PREEvision 10.7

ID 8682711554206562068 8682711554636281897 8682711553529641783
8682711554894201783 8682711554829312084

Known issue
During Add-in installation, error messages occur due to non-executable metrics. Workaround: To continue the installation, confirm the error messages with [OK].
After Add-in installation, in rare cases, the client cache may be broken. Workaround: Close the project, clear the client cache and reconnect.
ReqIF export: 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.
ReqIF export: The export of formatted texts containing tables that are aligned right via the table properties leads to a schema violation.
ReqIF export: The export of formatted texts containing specific list structures leads to a schema violation. Examples:

8682711555127671783 8682711555165912106
8682711555150891783

ReqIF export: The export of formatted text containing two following ordered lists leads to a schema violation.
ReqIF export: For empty attributes, the string defined in the Text for empty Labels property is exported instead of and empty string. By default, this is "---". Workaround: In the Preferences, under PREEvision | General, remove all characters from the Text for empty Labels property.
Templates, like report templates, opened with the new LibreOffice version may be shown as changed and can be saved directly, giving the impression that they have not been migrated. This apparent error can be ignored.

Version 10.20

310

PREEvision 10.7

ID 8682711555133422025 8682711555203942023
8682711555202122196 8682711554888343082 8682711555191801873

Known issue
<Ctrl> + click on a preview image in a formatted text may not open the linked File Attachment. Workaround: Use the context menu on the preview image or double click on the File Attachment artifact in the Model View to open the file attachment.
If a requirement contains a defective placeholder, the ReqIF Agreement Export aborts with a NullPointerException. Defective placeholders are diagram, table, or chart placeholders that reference an artifact that is no diagram, table, or chart, but, for example, an ECU.
The table in the dialog to select a Pin when resolving a new Splice on a Schematic Connection does not show any Pins. To get selectable Pins in the dialog remove the relation between Splice and Schematic Connection before starting the Resolve Splice refactoring.
If you select multiple artifacts of different meta classes in the Model View and open them in a table via Open with, the order of the artifacts within the table differs from the order of the artifacts in the Model View.
During reinitialization of the authority model an error message may be displayed reporting an unexpected error with the ramc.ser file. Workaround:
1. Delete the authority model.
2. Connect to the authority model.
3. Initialize the authority model.

Version 10.20

311

15 PREEvision 10.6
This chapter contains the following information:
15.1 Version numbers 15.2 Installation and compatibility information 15.3 New features in PREEvision 10.6 15.4 Fixed issues
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 15.5 Known issues

PREEvision 10.6
313 314 316 319 319 320 320 321 322 323 323 324 324 325 325 326 326 326 327 327 327 328 328 329 329 330

Version 10.20

312

15.1 Version numbers

Version numbers

Application PREEvision client PREEvision license server PREEvision database server PREEvision application server

Documentation

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

Version number 10.6.0 3.0.0 10.6.0.02 10.6.0
Version number 10.6.0 10.6.0 10.6.0 10.6.0 10.6.0

PREEvision 10.6

Version 10.20

313

PREEvision 10.6

15.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.

Deleted model contexts when editing formatted texts

PREEvision 10.6 contains a severe issue which may lead to data loss:
When formatted texts are edited, all Model Contexts below the associated artifact are automatically refactored to Placeholder Contexts. Additionally, orphaned Placeholder Contexts, which are not used as placeholder in the formatted text, are deleted.

The issue has been resolved in PREEvision 10.8. Therefore, it is highly recommended to perform a minor release update to PREEvision 10.8.

For detailed information and possible workarounds, refer to the following presentation in the download center: Information and Workarounds Unwanted Model Context Deletion.

Contact the Vector support to provide you with a database script and metric to identify and analyze deleted Model Contexts.

System requirements

The following system requirements have been changed: > It is recommended to use Apache Tomcat version 9.0.70.

Compatibility

Client version
10.5.0 10.6.0

Server version
10.5.0 10.6.0

Database server script version
10.5.1.41
10.6.0.02

Metamodel change ID
2022-10-05
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.

Version 10.20

314

PREEvision 10.6
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 > 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".

Version 10.20

315

PREEvision 10.6

15.3 New features in PREEvision 10.6

Diagnostic concept explorer

For specifying diagnostics, you can now create a diagnostic design independent of 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.

Data type mapping synthesis

For creating diagnostics for existing software, the existing Diagnostic Specification Explorer has been renamed to Diagnostic Realization Explorer.
Since version 10.5, PREEvision can automatically create the mappings between 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: using individual configuration files

To support individual use cases and improve the usability for the KBL import and export, it is possible to use individual configuration files, besides the standard 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 blocks and the KBL export 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.

Version 10.20

316

PREEvision 10.6

KBL import and export of 3D waypoints

PREEvision supports the KBL import and export of waypoints. The KBL interface supports segments containing wires and connecting nodes. These segments may contain waypoints which describe the approximate routing of these segments in the 3dimensional 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 editing extensions

Auto-layout diagrams for Wiring Diagrams and Wiring System Diagrams are created in a 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 autolayout 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

Version 10.20

317

PREEvision 10.6

Highlighting and updating outdated metric block ports

In the Metric Diagram, metric blocks for which additional ports are available are indicated
by an icon. The ports can be updated via the context menu Update Metric Block and Place Ports on Edges (left and right).

Ports of the metric block that are not part of its definition, are highlighted by an orange port color.

Version 10.20

318

PREEvision 10.6

15.4 Fixed issues

Fixed issues in PREEvision 10.6

You will find the important fixed issues in the following tables. Please note that some 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

15.4.1 Common
ID 8682711553043912061
8682711553311962041 8682711554395712101 8682711553679802071

Resolution
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.
An artifact selected in the Model View can be switched again to edit mode by pressing the <F2> once.
Checks have been added to avoid exceptions when opening portlets.
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.

Version 10.20

319

PREEvision 10.6

ID 8682711553543442039 17938309342081992 17938309315302049, 17938309303512000 8682711553300842108 8682711553524492041
8682711553554252036 8682711554173803043

Resolution
It is again possible to set references on the External Manual Links property page.
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.
In the Compare table, artifacts displayed on the two comparison sides are ordered as displayed in the Model View.
The quick search in tables now also works in the Compare table.
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.
Only Primary Editors that are set as default editor are opened when creating an artifact via an Artifact Creation Template. Other editors are ignored.
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.

15.4.2 Diagrams
ID 8682711553438402036
8682711553354300000

Resolution
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.
LibreOffice now properly starts after using Publish Diagram... in a server API metric.

15.4.3 Tables
ID 8682711553989382102
8682711553875262105

Resolution
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.
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.

Version 10.20

320

PREEvision 10.6

ID 8682711553269641914 8682711554379941003 17938309341102113
8682711553347942105 8682711553460262070

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

15.4.4 Requirements
ID 8682711552487071783
8682711554197182084 17938311392162049
8682711552635652105 8682711553515093059 8682711553506123059 8682711553500302106

Resolution
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.
File Attachment placeholders of PDF files now always show icons as automatic preview image.
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.
ReqIF export: Mappings without target no longer prevent the ReqIF export. Instead, a warning is reported in the Information View.
ReqIF export: The REQ-IF-TOOL-ID and SOURCETOOL-ID are set to the current PREEvision version.
ReqIF import: In the ReqIF Import wizard, the option for validating the imported model has been adapted concerning capitalization.
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.

Version 10.20

321

PREEvision 10.6

15.4.5 AUTOSAR
ID 8682711552994871806 8682711553353451998 8682711553517091998 8682711552994812051, 8682711552915480000 8682711553437491002
8682711553501581024
8682711553631860000
8682711553347561998 8682711553437491002
8682711551928661992
8682711553633551913
8682711553597322113

Resolution
AUTOSAR demo model: Broken tables in the demo model have been removed.
AUTOSAR demo model: Runnable Entities have been adapted to be AUTOSAR compatible.
AUTOSAR export: Pre-Build Variant Conditions are correctly exported.
AUTOSAR export: The attribute Array Size for Literals is now exported to AUTOSAR correctly for all relevant data types based on the attribute Maximum Number of Axis Points of the respective axis object.
AUTOSAR export: The AUTOSAR service instance manifest export does not export ServiceInstanceToPortPrototypeMappings anymore.
AUTOSAR export: A logic has been added to keep the IDs of SIGNAL-BASED-EVENT-ELEMENT-TO-ISIGNAL-TRIGGERING-MAPPING stable over multiple AUTOSAR exports if the Event Platform Data Type Mapping does not exist in the PREEvision model.
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.
ECU extract: Global Time Domains that are not relevant are not exported.
AUTOSAR service instance manifest: The AUTOSAR service instance manifest export does not export ServiceInstanceToPortPrototypeMappings anymore.
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.
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.
AUTOSAR import: Collections are now imported even if they have long names.

Version 10.20

322

PREEvision 10.6

15.4.6 Software architecture

ID 8682711554383131992 8682711553662172052 17938307005852003
8682711553097541998 8682711554518152051 8682711553521272010 8682711553509361024 8682711553632562196 8682711551799251029

Resolution
An error message in the log files of the Provided Port Connection Editor regarding an old configuration has been corrected.
For the class Process Design, the entry Executable on Properties property page is now navigable.
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.
The description for the assignment of Parameter Interfaces to ports has been refined in the manual.
An error in the manual in the description of service instantiation via AUTOSAR Adaptive Explorer has been corrected.
In the Startup Dependencies Editor, the column Kind has been removed, the columns Option and Argument Value have been grouped.
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.
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.
A restriction for setting initial values has been removed. The setting of initial values is now possible without an initial value configuration.

15.4.7 Diagnostics
ID 8682711553655412196

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

Version 10.20

323

PREEvision 10.6

15.4.8 Communication
ID 17938309379541810 8682711554380232069 8682711554187121003 8682711553303431810 8682711553506792004 8682711553543802159
8682711553644162159 8682711554007261029

Resolution
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.
Signal router: The attribute Requires LdCom Transmission is now handled correctly for signals that are based on SOME/IP Notifier Events.
Signal router: The signal router uses existing signal transmissions regardless of assigned signal ports, adds missing ports, and removes obsolete ones.
Signal router: The workspace behavior of the SOA & Ethernet Explorer including the creation of new Layout Packages while signal routing has been corrected.
J1939 DBC import: In case Signals are part of a System Signal, port assignments and data mappings are created only for the System Signal.
The default behavior of port implementsLegacyStringSerialization of the custom metric block PDU Length Calculation has been corrected.
The Frame-PDU synthesis now keeps existing Gateway Routing Entries of container PDU Transmissions that are transmitted independently over the bus.
The Frame-PDU synthesis behaves correctly if an ECU interface of a gateway has no assigned Bus Connector.

15.4.9 Hardware architecture

ID 17938306904992083
8682711553162931913
8682711554092301912

Resolution
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.
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.
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.

Version 10.20

324

PREEvision 10.6

ID 8682711554028871268
8682711553655612036
8682711553907882062 8682711552061922036 8682711553092062036

Resolution
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.
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.
KBL import: In the Import KBL wizard, all Custom Attribute Profiles for KBL can be selected.
KBL export: 3D Way Points below a Topology Segment are exported as Control_points to KBL.
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.

15.4.10 Geometry
ID 8682711553644161914 17938307855602062 17938301257112081
8682711553349491268

Resolution
The refactoring Insert Branch-Off on a Topology Segment with already routed wires can be properly executed.
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.
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.
Several consistency checks have been implemented for the Geometry layer.

15.4.11 Product line engineering

ID 8682711553577281995

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

Version 10.20

325

PREEvision 10.6

ID 8682711553338671806
8682711554536772046 8682711554483532101 8682711554180942012
8682711554093942101

Resolution
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.
A commit after an Asset cluster update no longer causes incorrect "Reuses do not match" errors.
After an Asset update, the Asset external to :1 relations in the foreign Product Line are no longer removed.
Drag and drop actions for Assets from the Version History in the Property View to the Model View are no longer allowed.
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.

15.4.12 Variant management

ID 17938307942461801 17938306329891789 8682711553553371825

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

15.4.13 Change and release management

ID 8682711553028652112
8682711554193091877
17938293806029199

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

15.4.14 Test engineering and test management

ID 8682711553339812102

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

Version 10.20

326

PREEvision 10.6

15.4.15 Rules
ID 8682711554380412077
8682711553678392102
8682711553169183013 8682711553559432101
8682711553655992024 8682711553049121995

Resolution
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.
The new online check "IllegalFrameworklinkOnRHS" has been added to the rule group "RuleConfigurationChecks". It checks if there are creation rules using invalid framework links.
The Progress dialog reports the progress for "Updating UI" after completing the online check calculation.
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".
Client-side online checks are now properly initialized.
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.

15.4.16 Metrics
ID 8682711553677672024
8682711553273942181

Resolution
Source codes can now be opened after renaming the metric and changing only letters from upper to lower case or vice versa.
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.

15.4.17 Reports
ID 17938311463042040
8682711553438901783

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

Version 10.20

327

PREEvision 10.6

ID 8682711554639042025

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

15.4.18 Collaboration
ID 8682711552036022049 8682711553214982106 8682711553653182034

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

15.4.19 Administration
ID 8682711553214862039 8682711553089811993 8682711553393791993
8682711553505132076 8682711553633321995 8682711553977682102

Resolution
The dialog for deleting or initializing the authority model no longer blocks user interface refreshes leading to a client freeze.
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.
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>)
Improved progress error message when database memory runs out during Add-ins installation.
The Add-in propagation has been extended to include table icons.
The Add-in propagation has been extended to include Metric Executors of Artifact Pickers.

Version 10.20

328

PREEvision 10.6

ID 8682711554417902011
8682711554417912011

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

15.4.20 License
ID 8682711552451121918
8682711554535352051

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

15.4.21 Backup, restore, and migration

ID 8682711554004691036

Resolution
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.

Version 10.20

329

PREEvision 10.6

15.5 Known issues

Known issues in PREEvision 10.6

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

ID 8682711685314021995
8682711554031661036 8682711554406702203 17938307791212069 8682711552649222003

Version 10.20

330

PREEvision 10.6

ID 8682711554383191029 8682711554417372014 8682711554417442013
8682711554206562068 8682711554645581003 8682711554636281897 8682711554644941202 8682711554645241202 8682711553529641783

Known issue
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.
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.
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.
During Add-in installation, error messages occur due to non-executable metrics. Workaround: To continue the installation, confirm the error messages with [OK].
After customization of an Add-in, context relations between successor artifacts and singleton artifacts get lost. Workaround: Set the necessary relations manually.
After Add-in installation, in rare cases, the client cache may be broken. Workaround: Close the project, clear the client cache and reconnect.
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.
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.
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.

Version 10.20

331

16 PREEvision 10.5

This chapter contains the following information:
16.1 Version numbers
16.2 Installation and compatibility information
16.3 New features 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
16.4 Changes
16.5 Fixed issues 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

Version 10.20

PREEvision 10.5
334 335 338 338 343 344 345 347 350 352 359 363 365 369 370 383 385 385 390 392 397 404 405 414 418 421 430 440 441 447 448 448 449 450 452 455 456 463 470
332

License Backup, restore, and migration 16.6 Known issues

PREEvision 10.5
471 472 474

Version 10.20

333

16.1 Version numbers

Version numbers

Application PREEvision client PREEvision license server PREEvision database server PREEvision application server

Documentation

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

Version number 10.5.0 3.0.0 10.5.1.41 10.5.0
Version number 10.5.0 10.5.0 10.5.0 10.5.0 10.5.0

PREEvision 10.5

Version 10.20

334

PREEvision 10.5

16.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.

Deleted model contexts when editing formatted texts

PREEvision 10.5 contains a severe issue which may lead to data loss:
When formatted texts are edited, all Model Contexts below the associated artifact are automatically refactored to Placeholder Contexts. Additionally, orphaned Placeholder Contexts, which are not used as placeholder in the formatted text, are deleted.

The issue has been resolved in PREEvision 10.8. Therefore, it is highly recommended to perform a minor release update to PREEvision 10.8.

For detailed information and possible workarounds, refer to the following presentation in the download center: Information and Workarounds Unwanted Model Context Deletion.

Contact the Vector support to provide you with a database script and metric to identify and analyze deleted Model Contexts.

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 operating

The following changes and new features are available for the installation and operating of 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 securityrelated actions.

Version 10.20

335

PREEvision 10.5

> 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.

Migration Compatibility

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.
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.

Version 10.20

336

PREEvision 10.5

Client version 10.5.0

Server version 10.5.0

Database server script version
10.5.1.41

Metamodel change ID
2022-10-05

Licenses and license server

For PREEvision 10.5, new licenses are required.

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.

Operating system: character set

Please use an operating system with a full character set of your language. For example, 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.

Version 10.20

337

PREEvision 10.5

16.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

16.3.1 Requirements engineering and requirements management

Placeholders in formatted texts

Several usability and performance improvements are available for inserting and updating 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.

Version 10.20

338

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.

File attachments in formatted texts

> 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.
When inserting files into formatted texts, instead of OLEs, placeholders to file 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.

Version 10.20

339

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 images in formatted texts

In the preferences, under PREEvision | LibreOffice you can activate to automatically format images when they are inserted into formatted texts in PREEvision. The default 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, images, and OLE objects during ReqIF import and export

During the ReqIF import:
> File attachments in formatted texts are imported as file attachments. The file attachments are stored in the PREEvision model. The alternative PNG from the *.reqifz file is used as preview image. A preview image with a reference to the file attachment is inserted in the formatted text.

Version 10.20

340

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 export

Before exporting to ReqIF, you can execute several checks to ensure OLEs and 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 export checks

Before exporting to ReqIF, you can execute several checks to ensure OLEs and 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.

Version 10.20

341

PREEvision 10.5

ReqIF import and export configuration

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.
The configuration possibilities of the ReqIF import and export have been extended to 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 PREEvisionattributes 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.

Version 10.20

342

PREEvision 10.5

Overwrite character styles of text placeholders in reports

For Reports, the new text placeholder option Overwrite character styles of the included text is available. If the option is activated, all character styles in the included 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 relations

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

16.3.2 Test engineering and test management

Alignment of test specification editor and requirement text editor

The Test Specification Editor has been further aligned with the 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.

Version 10.20

343

The column Priority is added to the Test Specification Editor.

PREEvision 10.5

Improvements for the test specification editor

The following improvements have been implemented for the Test Specification Editor: > A new column Test Condition Links is available. > 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.

16.3.3 Function driven and system design

Added value by integrated activity diagrams

PREEvision now offers Activity Diagrams.
Behavior description:
> The activity supports the development of complex architectures from a behavioral perspective.

Version 10.20

344

PREEvision 10.5
> The integrated modeling of activities enables two main use cases: > 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.

16.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 AUTOSAR Adaptive

Regarding AUTOSAR Adaptive, PREEvision 10.5 provides the following extensions and 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 SOA & Ethernet explorer

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

Version 10.20

345

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.

Handling of initial values

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
The setting of initial and invalid values is much easier now: > 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.

Version 10.20

346

PREEvision 10.5

Improved port connector

The port connector works on the logical architecture in the same way as in the software 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 software design explorer

The Software Design Explorer, introduced with PREEvision 10.0, is further optimized. This includes:
> 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

16.3.5 Communication design

Extensions in frame PDU synthesis to support of multiplexed IPDUs

The Frame PDU synthesis now supports CAN Frames containing multiplexed IPDUs. The synthesis creates Frame Transmissions and PDU Transmissions for the multiplexed IPDUs for each Bus System.
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.

Version 10.20

347

PREEvision 10.5

Support of adaptive network management

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

Support of complex signal-to-service mappings

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.
In PREEvision 10.5, interface relations are replaced by Platform Interface Mappings, which can map a Service Interface to fitting interfaces of the AUTOSAR Classic Platform (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.

Version 10.20

348

PREEvision 10.5

Ethernet modeling in AUTOSAR 20-11

The SOA & Ethernet modeling has been restructured according to release 19-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 10BASET1S ethernet physical channel

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

Version 10.20

349

PREEvision 10.5

Bus connector as condition for signal router

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

16.3.6 Diagnostics design

Extended data exchange with CANdelaStudio via PVCDI format

Exchange of Scale Linear Verbal Table Conversions The data exchange with CANdelaStudio now supports linear conversions. Scale Linear Verbal Table Conversions are often used, typically with just one linear conversion. 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.

Version 10.20

350

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 options

The diagnostic exchange now prioritizes software over logical architecture.

Version 10.20

351

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 DID specification steps

The DID independent modeling of Diagnostic Data Objects by system responsibles is 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.

16.3.7 Wiring harness design

New wiring harness explorer

A Wiring Harness Explorer is available for schematics and wiring harness. 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

Version 10.20

352

PREEvision 10.5

Classic and complex wiring harness inline connectors

In wiring harness design, different kinds of inline connectors can be distinguished: > Wiring Harness Inline 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.
> New pin sorting functions for Wiring Harness Multi Inline Connectors.

Version 10.20

353

Design of zonal architectures

PREEvision 10.5
> 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 and
its Wiring Connectors. > Implementation of various validity checks for Schematic Pins / Wire Pins.
A zonal architecture design for the geometry based on the zonal design of the network architecture has been introduced.

Extensions for installation spaces

> The network components grouped and clustered into network zones provide the basis for the zonal architecture design of the vehicle geometry.
> 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.
Installation Spaces can now be modeled as nested Installation Spaces. Inner Installation 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.

Version 10.20

354

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.

Icons in labels

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.
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.

Version 10.20

355

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

PREEvision 10.5

Sheet connectors

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

The usability of working with Sheet Connectors for split connections has been improved. Thus, Sheet Connector link boxes allow you to navigate to the corresponding targets of a split connection. Navigation to the targets is possible for targets located in another diagram, targets located in diagram sections, or within a diagram area.
Sheet Connectors are customizable via object configuration with respect to the content and the orientation of their link boxes and the style of Sheet Connectors.

Wiring harness autolayout improvements

Improved existing auto-layout functionality for Wiring Diagrams: > Optimization concerning the layout of the target diagrams

Version 10.20

356

PREEvision 10.5
> Support of nested components: the uppermost component is displayed in the autolayout diagram
> When creating auto-layout diagrams via the Create Diagram-Based Auto-Layout Wiring (System) Diagram block and the Create Model-Based Auto-Layout Wiring (System) Diagram block, 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 harness auto-layout

A read-only Wiring (System) Diagram can be created automatically, based on a part of 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.
Example: Starting at a component, displaying its functional network, that is, all connected components.

Version 10.20

357

PREEvision 10.5

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.

> The Schematic Connection dialog has been improved and aligned.

Version 10.20

358

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

16.3.8 Product line engineering

Extensions for product line engineering

The following product line engineering extensions and improvements are available in 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 improvements: revoke context and update context

The two technical terms "update context" and "revoke context" have been implemented to handle which artifacts to be displaced to which Asset after an Asset update. This means, which artifacts and relations between artifacts will be protected in the Assets if the 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
> 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 calculation and asset cluster update

When an Asset is updated, the foreign Assets that conflict with the updated Asset are revoked. In some product line engineering use cases, the revoke operation or 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

Version 10.20

359

PREEvision 10.5
> Performing an Asset cluster update considering a substitution use case

Improvements for substitution

The substitution is improved to support more use cases:
> 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
The artifact from upstream to substitute is reused in the local Product Line only after confirming the substitution.

Information output in case of nonsynchronous reuses

If a reuse-out-of-sync scenario occurred during an action, for example, an Asset update due to an error in the merge algorithm, the commit was rejected without providing 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 relay box handling in the product line engineering wiring harness design workflow

A new modeling concept in the product line engineering wiring harness workflow has been implemented.
> No Ground Point template will be modeled, and will not be propagated as boundary to the system Asset.
> The terminal number type at the Schematic Pin is used to represent a Ground Point.

Version 10.20

360

PREEvision 10.5
> 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 > 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.

Version 10.20

361

> New column in the Review and Confirm Substitution table.

PREEvision 10.5

External relation analyzer

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.
The External Relation Analyzer can be used to identify and resolve external relations: > 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 improvements for variant activation

Current situation:
> The activation and deactivation of a variant/set took a lot of time (for example, several 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).

Version 10.20

362

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).

16.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

Version 10.20

363

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

Update and commit improvements

The update cache is now stored on the hard disc: > 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 calculation

Server-side online checks are now calculated in parallel and asynchronously after 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.

Version 10.20

364

PREEvision 10.5

16.3.10 Usability

Dashboard and entry points

Dashboards offer personalized entry points for users, present the artifacts that are 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.

Version 10.20

365

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 diagrams

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

Version 10.20

366

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 PREEvision

When using high-resolution monitors, the user interface of PREEvision may show an 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%).

Version 10.20

367

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.

In some cases, restarting PREEvision on the target monitor can help to apply the right scale factor.

Exploring the demo model

The PREEvision demo model now includes a Demo Model Contents table and 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:

Version 10.20

368

PREEvision 10.5

16.3.11 Administration

Add-ins for configuration and customization

Add-ins cover the complete PREEvision configuration: > Product configurations are delivered by product Add-ins. > Installed Add-ins are updated version-safe and automatically. > Add-ins can be easily adapted and extended. > 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 PREEvision 10.0 to 10.5

Migration preparation is significantly improved: > less storage and runtime required > 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.

Version 10.20

369

PREEvision 10.5

16.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.

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 palette tools and custom menu items

Two new configuration features are available which enable the user to focus on working in a diagram or table and avoid switching to other views or editors:
> 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 property view

Relation Filters allow you to configure use case-specific filters for property page dropdown 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 text fields and cells

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

Table configuration diagram

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

Drag and drop actions in tables

The configuration of drag and drop actions in tables has been changed. For standard drag and drop actiony you can now define which actions are listed in the drag and drop menu in tables.

Version 10.20

370

PREEvision 10.5
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.
Toolbar action groups For the table toolbar, the order of Action Groups can be configured. in tables

Configuration of variant-sensitive tables

If variant-sensitive Query Rule Groups are used to obtain data within tables, you must 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 actions in tables

In previous PREEvision versions, the meta class of the source column artifact had to be 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 columns

The default update behavior of hidden table columns has been changed. Hidden table 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 for table columns

The automatic selection propagation can be deactivated for a table column by activating 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.

Version 10.20

371

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

Context menu configuration

Prioritized perspective elements or default editors can be displayed at the top-level in the 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 configuration files

The configuration files under Administration | Configuration File Container | New Menu 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/ online check views

The following views have been renamed: > 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 during add-ins installation

The handling of Add-ins has been optimized with regard to online checks and consistency checks:
> 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.

Version 10.20

372

PREEvision 10.5
The table provides a more convenient configuration possibility of Consistency Rule Groups by displaying all relevant settings in one table.

Rule names must not contain space characters

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

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 object configuration

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

Attribute values of attribute owner no longer ordered

The meta model has been changed. The composition from AbstractAttributeOwner to AbstractAttributeValue (role "ownedAttributeValues") is no longer order 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 utilities

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

Metrics progress monitor

The progress monitor was improved to make it possible to us sub progresses in metrics. 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();

Version 10.20

373

PREEvision 10.5

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.

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"

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

Version 10.20

374

PREEvision 10.5

> 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.
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 targets

ReqIF REQ-LA-Mapping Product Goals Targets Export Extension

ReqIF Specific Export

ReqIF Model Based Specification Export

Product Goals

ReqIF Writer Block

ReqIF File Writer

Product Goals

Version 10.20

375

PREEvision 10.5

Old name

New name

New category

ReqIF Identity Detector Block

ReqIF Identity Function

Product Goals

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 Open Ports

Logical Architecture Contained Open Ports Delegator

Logical Architecture

LA DelegatePorts

Logical Architecture Ports Logical Architecture Delegator

AUTOSAR (Source defines AUTOSAR Identity

ImExId matching) Identity Function (Source defines

Function

ImExId matching)

Software Architecture

AUTOSAR Import/Update AUTOSAR Deletion

Deletion Function

Function

Software Architecture

(Re)Assign Mapped

Mapped Implementation

Implementation Data Types Data Types Assignment

Software Architecture

SWA Delegate Contained Open Ports

Software Architecture Contained Open Ports Delegator

Software Architecture

SWA Delegate Ports

Software Architecture Ports Software Architecture Delegator

Create/Update SOMEIP interface deployment

SOME/IP Interface Deployment Synthesis

Software Architecture

Arrange IPDUs

Arrange PDUs

Communication

AUTOSAR Export Block AUTOSAR Export

Communication

AUTOSAR Identity Function

Communication

AUTOSAR Import Block AUTOSAR Import

Communication

AUTOSAR Import with Merge Block

AUTOSAR Import with Merge

Communication

AUTOSAR Reader

Communication

AUTOSAR SW Component AUTOSAR Software

Update

Component Update

Communication

AUTOSAR Transformer

AUTOSAR Import Transformation

Communication

Communication Path Router

Communication

COM-Synthesis

Communication Synthesis Communication

Version 10.20

376

PREEvision 10.5

Old name

New name

New category

Convert To Enumeration

AUTOSAR Import Application Enumeration Converter

Communication

Com Lengthcalculation

Communication Length

Communication

Create / Update SOMEIP/ SOME/IP Transport

TP Synthesis

Protocol Synthesis

Communication

Create Network Management for Cluster

Synthesize Network Management for Cluster

Communication

Create PDU-Transmission PDU Transmission

Structure

Structure Synthesis

Communication

Dereference Secured IPDU Dereference Secured IPDU Communication

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 Router

Communication

Service Instances Creator Create Service Instances Communication

Frame DLC Calculation

Calculate Frame Data Length Code (DLC)

Communication

Dissolve PDU FanInFanOut PDU Fan-In/Fan-Out Dissolver

Communication

FUP-Export-Transformation FUP Export Transformation Communication

FUP Export Writer

FUP Writer

Communication

FUP Import Identity Function

FUP Identity Function

Communication

FUP Import Reader

FUP Reader

Communication

FUP Import Transformation FUP Import Transformation Communication

PlmXml Document Creator PLM XML Document Creator

Communication

Software Library Relevance Software Library Relevance Communication

Function

FlexRay Scheduling Core FlexRay Scheduling

Communication

Reference Secured IPDU to Reference Secured IPDU Communication

IPDU

to IPDU

Version 10.20

377

PREEvision 10.5

Old name

New name

New category

Diagnostic DefinitionSet

Diagnostic Definition Set Diagnostics

Assignment and Creation of Assignment and Creation of

Attribute Profiles

Diagnostic Lib Identification Diagnostic Library

Function

Identification Function

Diagnostics

Diagnostic Library Creator

Diagnostics

Diagnostic PL Selection

Diagnostic Product Line Selection

Diagnostics

Diagnostic Ref Identification Diagnostic Reference

Function

Identification Function

Diagnostics

Compare PVCDI with ECU PVCDI with ECU Extract

extract

Comparison

Diagnostics

Nested Values Presenter

Record/Array to String Converter

Diagnostics

Execute Circuit Synthesis Circuit Synthesis

Electrologic and Harness

Optimization Manager Block

Splice Optimization

Electrologic and Harness

KBL Export Block

KBL Export

Electrologic and Harness

KBL Import Block

KBL Import

Electrologic and Harness

Create Standard Catalogue Create Splice or Inline Connector

Electrologic and Harness

Wiring Autolayout Diagram Create Diagram-Based Auto-Layout Wiring (System) Diagram

Electrologic and Harness

Change Variants Block

Change Variants

Variant Management

Variant Propagation Block Variant Propagation

Variant Management

Artifact Substitute plus Asset Factory

Artifact Substitute Plus Asset Factory

Product Line Engineering

Asset Analysis for Automatic Integration

Asset Integration Model Calculator

Product Line Engineering

Asset Delete with Clean Up Asset Delete With Clean Up

Product Line Engineering

Asset Update and Reattach Finish Asset Update After Product Line Engineering

continue

Substitution

Asset update with embedded substitution

Asset Update With Embedded Substitution

Product Line Engineering

Autointegrate Asset

Asset Automatic Integration Product Line Engineering

Automatic Reattach for Non-Conflict

Automatic Substitution if Non-Conflict

Product Line Engineering

Compare and Reattach

Review and Confirm Substitution

Product Line Engineering

Version 10.20

378

PREEvision 10.5

Old name

New name

New category

Create Replace Configuration for Compare and Reattach

Create Replace Configuration for Substitution Table

Product Line Engineering

Create replace configuration for compare table

Create Replace Configuration for Compare Table

Product Line Engineering

Execute Analysis based Asset Integration

Asset Integration Model Integrator

Product Line Engineering

Get Assets from upstream to convert foreign relation

Get Assets From Upstream Product Line Engineering To Convert Foreign Relation

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

Product Line Engineering

Add artifact to Set/System Add Artifact to Set/System Product Line Engineering

Compare Table Export Block

Compare Table Export

Change Management

Compare Artifacts

Artifact Comparision

Change Management

Create OEM Agreement Task Items

OEM Agreement Task Items Creator

Change Management

Requirement Coverage

Requirement and Test Specification Coverage

Test Engineering

Check-In Block

Check-In

Collaboration

Commit Block

Commit

Collaboration

API Server Calculation Block

API Server Calculation

Collaboration

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

Version 10.20

379

PREEvision 10.5

Old name

New name

New category

Prepare Customizing

Add-ins Customizing Preparation

Administration

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

Validator Block

Validate

Common

CSV Export Block

CSV Export

Common

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 Findings Collector

Online Check Findings

Common

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 Folder

Common

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

Version 10.20

380

PREEvision 10.5

Old name

New name

New category

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 Reference

Table to Reference Comparison

Configuration Test

Create Table Reference Table Reference Creator Configuration Test

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 Configuration Block

Diagram Configuration Changer

Diagrams

Create Datasource

Data Source Creator for Calculated Labels

Diagrams

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 representation

Remove Graphical Representation

Diagrams

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

Version 10.20

381

PREEvision 10.5
> 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

Version 10.20

382

PREEvision 10.5

16.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.

Version 10.20

383

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.

Version 10.20

384

PREEvision 10.5

16.5 Fixed issues

Fixed issues in PREEvision 10.5

You will find the important fixed issues in the following tables. Please note that some 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

16.5.1 Common
ID 17938308307242099 17938307793732203 17938308060401036 17938309199152050

Resolution
The form editor now refreshes after editing, for example, in the Property View or the Model View.
The language of the PREEvision client has been preset to English (United States).
The information on failed E/E model exports has been improved.
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.

Version 10.20

385

PREEvision 10.5

Property view

ID 17938308865552101
17938308756822034
8682711552963422106 8682711553262941791 8682711553509512041

Resolution
A more descriptive text has been added to the progress bar that appears after clicking the Finish button in the New Project wizard.
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.
The start of LibreOffice shows and information if it fails and, in general, is faster.
Inconsistencies in the PREEvision demo model have been fixed.
Correct MENU-ID ouput in the Status view by using <Alt>+<Ctrl>+<F6>.

ID 12113 8682711552409011037 8682711552928032034
17938309365222052 17938308840042051
8682711551922932105 17938308224841875 17938305558022039, 8682711552764792039
17938309118222092

Resolution
The client problem (client freeze) which was caused by an infinite loop in the Property View has been resolved, and the client performance improved.
Property pages with dynamic entries are shown again after being filtered out.
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.
In the Property View, sporadic problems with drag and drop actions have been resolved.
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.
When selecting multiple artifacts in a Property View table via <Shift> + arrow key, all selected artifacts are also selected int he Model View.
When changing the selection in the Property View, the selection change is properly propagated to the Model View.
When using the Locale en_GB in the PREEvision.ini, 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.
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.

Version 10.20

386

Model view Context menu

PREEvision 10.5

ID 8682711551998992045 8682711552948732050 17938308145971032
17938311517902108

Resolution
In the Property View, the correct value of Light Weight String Attributes is displayed, with leading zero, if defined.
A configured Generic Table Artifact Picker that displays Diagram Configurations can be opened from the Property View without displaying an error.
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 XIndex and Y-Index attributes.
A problem with displaying property pages that occurred on Application Axis Types has been resolved.

ID 17938307534153017 17938307564392001 17938309315242101 8682711552288902099 8682711553334332111
17938311467381204 17938311467391204 17938311473392049 8682711552406681806

Resolution
File attachments are correctly displayed in the Model View.
The performance has been improved, when working with a pinned Model View.
The selection of artifacts in the Search result view is propagated to the Model View.
If the Model View is pinned, the automatic navigation and selection propagation is suppressed even on drag and drop actions.
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.
In a large-scale tree, the selection of an artifact is kept after a drag and drop.
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.
Large-scale trees are now displayed below diagrams, containers, or packages to improve the usability for artifact navigation.
Ordering in large-scale trees uses the label instead of the artifact names.

ID 17938307499612070

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

Version 10.20

387

PREEvision 10.5

Information view
Object and label configuration

ID 17938307669632106
17938299596052090
17938307799872111 17938311319481030 8682711552342101995 17938308936151037 17938311600272049

Resolution
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.
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.
Submenu entries are no longer displayed twice in context menus.
Submenus in the context menu are properly displayed.
The New context menu no longer displays duplicate entries for creating Conditions.
Prioritized tables and explorers of a perspective are correctly displayed in the context menu.
All types of metric executors that are not prioritized for a perspective are displayed in the Others context menu.

ID 8682711551930992102
8682711553067011992
8682711553095012111 8682711553114182159

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

ID 17938307380242112
17938307443012111

Resolution
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.
Change markers are now correctly updated for localized attributes. Object configurations are properly displayed in tables.

Version 10.20

388

PREEvision 10.5

ID 17938307513201031 17938308952172081 8682711552995261918
17938311658381030

Resolution
Object configuration artifacts are now displayed in the Model View if the corresponding parameters in the PREEvision.ini file are set.
In the Label Configuration view, the drop-down list for choosing a Query Rule Group now provides autocompletion. The entry "default" is displayed as first entry and is initially selected.
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.
When working in multi-user mode, images can be replaced in the object configuration.

Comparison and merge ID 17938307767972042
17938309314692049
17938309315242049 8682711551964921914 8682711552271132101 8682711552593571999 17938311439532050

Resolution
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.
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.
The default colors for displaying comparison results in the Property View, have been changed and can be defined in the Preferences.
After an artifact merge of reused artifacts, the commit works correctly.
The Model merge wizard always displays zero artifacts to be deleted if no reference model is selected.
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.
Comparing creation times no longer causes a NullPointerException.

Version 10.20

389

PREEvision 10.5

16.5.2 Diagrams
ID 24491912
17938308756452034 17938308756832034 17938309359252041 17938308053831992 17938311660752041 8682711552491832041 8682711552055372039 8682711553188042041
8682711552500331995 8682711552714812081 17938308850881861 8682711551958071030 8682711553067840000
8682711553369973071 8682711553547742041

Resolution
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.
The text of a Title Block now scales with the Windows scaling.
Zooming no longer cuts off strings in diagrams. The text is now scaled proportionally.
The fan waypoints are now moved correctly again when two pins are swapped to avoid overlapping routing results.
The duration of the multiselect option in diagrams has been improved.
The context menu entry Open all Diagrams on an artifact works properly again.
The text in comment fields now ignores HTML tags and shows the text as it was entered.
Sections are now ignored by the variant highlight.
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.
Trying to add a composition to a type diagram now reports the correct error in the Information View instead of displaying a black box.
During automatic creation of a diagram via metric, all required connections on ports are created, including bus connections with more than two ends.
Checks have been added to prevent an IndexOutOfBoundsException in diagrams.
Formatted texts of Comment and Information artifacts are available again in diagrams.
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.
The tooltip of the alignment actions in all diagrams now contains the information that the first selected artifact is used as reference.
Labels in diagrams do no longer draw an unintended white background.

Version 10.20

390

PREEvision 10.5

ID 17938309408412046
17938308850441861 8682711552398361914
8682711553353002100

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

Diagram configuration

ID 17938311642322112

17938311323242073 8682711552652071038 17938309328882044
17938309329522044 8682711553171381806

17938309342502101

Resolution
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.
Calculated labels consider configured rule constraints in the label configuration.
To improve performance, connections only once regard the object configuration.
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.
Metric Artifact Pickers can be used in the Diagram Configuration.
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.
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 publishing diagrams

ID 17938309312192102
8682711552491502041

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

Version 10.20

391

PREEvision 10.5

ID 8682711553056422042
17938309366281038 8682711552433822045 8682711552451732041

Resolution
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.
When exporting a diagram as report or PDF labels ending with empty lines are now aligned properly in positions lists.
Font sizes in diagrams are the same independent of whether the diagram is displayed in PREEvision or exported as PDF or ODG.
The Use maximum resolution option has been removed from the Page/Print Settings preferences.

Tables in diagrams

ID 17938309032261912 17938308107701038 8682711553092362159
8682711552683152001 17938308166022099
17938307717622050

Resolution
Tables in diagrams are displayed at the correct position regardless of the screen resolution.
Tables in diagrams are no longer highlighted when navigating to an opened diagram from the Model View.
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.
The context menu entry Delete from Model has been removed for tables that are displayed in a diagram.
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.
When displaying tables in diagrams, the context menu action Show Table now considers the localized names for tables in the Show Table dialog.

16.5.3 Tables
ID 17938307506972112

Resolution
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.

Version 10.20

392

PREEvision 10.5

ID 17938307778561992 17938309242941027 17938307554012106 17938311331272098 17938311441763039 8682711551845231992
8682711552860642102 8682711553163282001
8682711552430302045 17938305535212106 17938307557592105
17938308025761806
17938308772882045 8682711553039172105 8682711553105783013 8682711553258912106 8682711553081023042
17938307956621025
17938311633421810 17938308048812113

Resolution
Names of software types and prototypes are synchronized when the name is edited in tables.
A selection propagation between Combined Table Proxy artifacts works properly again.
A validation check for drag and drop actions in tables has been implemented to avoid invalid drop operations.
Copy and paste of a multi-selection into direct attribute columns works properly.
A check box within a table column in read-only mode cannot be edited anymore.
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.
It is now possible to cancel the printing of a table.
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.
When activating the table search in combined tables, the search field is writable for all child tables.
Pinning in tables is still active after embedded formatted text cells have been opened.
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.
A table cell that has set a width of zero pixels does no longer cause display errors. The table is properly displayed.
No system crash occurs anymore when temporarily adding an artifact to a scope while a table is open.
Tables are no longer collapsed after executing a commit.
Within tables, the selection is kept after collapsing and expanding.
Table rows are expanded on table updates if the option Show expanded is activated.
A double click on an artifact in a read-only column no longer leads to losing the selection. The table cell keeps the selection.
An error dialog is displayed again when copying cell values of different columns with gaps between the selected cells.
It is now possible to copy values from cell metrics and paste them into another cell.
The Delete artifact button for table cell entries in tables is now also displayed if multiple cells are selected.

Version 10.20

393

PREEvision 10.5

ID 17938311331162102
17938311473772113
17938311514852113 17938311345712106 17938307782281045 17938308102982104 17938307554002106
8682711552040552104
8682711553288322101 17938307511243017 17938305494192106 17938309241212065
17938311665222113 8682711552765201806 8682711552925843042 17938311421722101 17938311524072106 17938311682752101

Resolution
For tables with charts, the incorrectly displayed error message in the Information View concerning a missing life cycle color is no longer displayed.
Custom attributes having set no value no longer cause an error message on opening a table in which they are displayed.
Table cell actions are only displayed if the table cell is selected and focused.
The performance of selecting artifacts in table cells has been improved.
The performance for working in tables has been improved, when calculating the cell sum for tables.
Action buttons for table cell entries in tables are now only visible if the corresponding table is also visible.
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.
The copy and paste behavior in tables has been corrected in case the selected cell has no label configuration.
The Excel export of a table works if the table contains headers with the same name.
No exception occurs anymore for tables for which cell content is calculated via a metric.
The column width is persisted when saving a table into the model.
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.
Searching in combined tables also works with collapsed or hidden columns.
The selection is set to the correct artifact in the Model View also if columns are hidden in the table.
Changing the sort order of the first table column no longer leads to hidden values in the last table row.
For tables with hidden columns, active column filters work properly after refresh.
Pasting clipboard content into tables that contain hidden columns works properly, now.
If columns of tables are set as hidden, the content of columns with check boxes is kept and displayed.

Version 10.20

394

Explorer

PREEvision 10.5

ID 17938308307252099 8682711553161912099
8682711553105713013 8682711552769572112
8682711552331152106
17938309273602036 17938311473792049
17938308088892105
8682711552971133042 8682711553095042102
8682711553462092041 8682711554010272100 8682711553352342106

Resolution
After a refresh in a table, the active filters are applied again, and the table shows the correctly filtered content.
When filtering a table, the currently selected artifacts/ elements are removed from the selection if they are no longer visible in the table.
The expand state in front of subtrees within tables is correctly displayed after filtering the table.
When a table is opened on multiple selected artifacts, the Artifact Picker now displays the correct scope of artifacts depending on the set filter.
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.
Drag and drop actions work with prototype columns.
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.
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.
The toolbar action enablement state is updated when the selection is changed in a Portlet.
To better support selecting elements from a link column overlay menu, the tooltip is now closer to the mouse pointer.
For table rows that are displayed as help lines in tables, artifact icons are displayed again.
Within tables, pasting artifacts is also allowed on columns that display several artifacts in one cell.
The Predefined filter option is available on a column even if preceding columns are hidden and following columns use a formatted text renderer.

ID 17938309365052106 17938311391031804
17938311631412102

Resolution
When switching the table in an explorer, the selection is maintained.
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.
The submenus of the navigation bar are correctly displayed in explorers.

Version 10.20

395

PREEvision 10.5

ID 8682711552705982048
17938307747931992 17938311538352113 17938311444403039 8682711551860041038 8682711552087682044
17938309342301810
8682711553388601992 17938307379292108

Resolution
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.
In explorers and portlet views, the Open With context menu entry is correctly displayed depending on the selected artifact.
When opening the context menu in an explorer, Open With is displayed as first entry of the context menu.
In explorers, meta classes are correctly filtered including virtually displayed artifacts.
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.
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.
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.
Creating artifacts in explorers does no longer lead to displaying duplicates of these artifacts in the Model View and the categories of the explorer.
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 8682711552552802083
8682711552561772106
17938307946942102 17938309386412049 17938311685172101

Resolution
When using the table column configuration HorizontalAlignment = "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.
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.
It is now possible to open editors under a Table Editors Package.
Adding an already associated table column that displays a custom attribute multiple times to a table is no longer possible.
Moving a table column does no longer result in hiding other columns or prototype columns.

Version 10.20

396

PREEvision 10.5

ID 8682711552539621220
8682711552708592106 8682711553038071032 17938308315432041
8682711553964471027 8682711553269731914

Resolution
The initial state of column group elements in the Add/ Remove/Reorder Columns dialog is now visualized correctly.
Hiding selected prototype columns is now possible in tables.
Cell metrics used in tables now show the returned string as plain text without style range formatting.
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.
For Direct Attribute Table Columns, the column configuration works properly.
In the Property View of tables, the Toolbar Actions property page has been added to the Characteristics category.

16.5.4 Requirements
ID 17938308131332101 8682711552337612107 8682711553140751030
8682711553170902101 8682711552944241791
17938308996852105

Resolution
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.
Attributes that are read-only due to meta rights are now correctly set when copying between models.
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.
Copy and paste of Requirements no longer changes their order.
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.
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 17938291663539243

Resolution
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.

Version 10.20

397

PREEvision 10.5

ID 17938306651292105
17938309369442106 8682711552104362105 8682711552418141030
8682711553027022105
17938306401202105 17938307537762101

Resolution
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.
Switching between tables of the Requirement Text Editor via the toolbar button is possible again.
When deleting Requirements in the Requirement Text Editor, no empty table rows are displayed anymore.
In the Requirement Text Editor, the font color in formatted text table cells is now rendered correctly according to the object configuration.
During an export from the Requirement Text Editor to Excel, placeholders are updated, and the correct placeholder information is exported.
The performance of filtering in the Requirement Text Editor has been improved.
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 placeholders

ID 17938311460702105
17938311512092105 17938311666232106 8682711551847412106 8682711552341902105
8682711553181462105
17938307539672023 17938307553992106
17938307564382001

Resolution
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.
Formatted text containing OLE objects can now be edited directly in table cells of the Requirement Text Editor.
Pasting formatted text with placeholders into custom attributes is possible now.
Sporadic problems with rendering formatted text in tables have been resolved.
A performance problem has been resolved that occurred in tables when copying formatted texts containing placeholders.
The previews of formatted texts within tables are now correctly rendered when they contain tables with vertically merged cells.
The Check OLEs in Formatted Texts action no longer displays hidden artifacts in the Information View results.
Placeholders in formatted texts can now be properly restored using the redo or undo functionality of the integrated editor for formatted texts.
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.

Version 10.20

398

PREEvision 10.5

ID 17938307671152023 17938307683663017 17938308107832023 17938308840082070 17938308865672040 17938308926362113
17938308931662106 17938309056902025 17938309197172106
17938309198032106
17938309237292106 17938309359282105 17938311364202106 17938311391022106 17938311519132104

Resolution
The Check OLEs in Formatted Texts action now uses the configured localizations for attribute definitions in the Information View message.
Inserting images into formatted texts via drag and drop now works properly if the filename contains Unicode characters.
Frame styles are now displayed in the Styles and Formatting view when using the Rich Text Template File in the PREEvision demo model.
The performance of auto updates has been improved by caching the information whether the formatted text workspace directory exists in the file system.
Shapes are now disabled in the formatted text editor since they cause rendering errors in the preview of formatted texts.
If preferred placeholder attributes are configured for a perspective, only the assigned (configured) attributes are available for selection in the Insert Placeholder dialog, again.
In a sporadic constellation, newly created placeholders in formatted texts were displayed as <undefined>. The error has been resolved.
The messages that are reported when executing the Update Rich Texts metric block have been improved.
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.
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.
Recursively embedded placeholders in formatted texts now reflect the current model state when viewed in tables.
An error in the LibreOffice editor has been resolved. OLE objects in artifacts are now accessible and can be opened with read-only rights.
To prevent errors during formatted text handling, the tool state is reset after a model compare.
Formatted text without available HTML previews no longer causes error messages when opening the Change history view for an artifact.
The sporadic loss of OLE object previews has been resolved. OLE objects are correctly displayed in reports again.

Version 10.20

399

PREEvision 10.5

ReqIF import and export

ID 17938311530392106
17938311674121783 8682711552081441030 8682711552419472106
8682711552495132106 8682711552759542023
8682711553066032105 17938300517172105 17938306022802107 8682711552050411030 17938307341861806

Resolution
Several problems have been resolved concerning formatted text of meta classes which do not support placeholders at all.
Editing placeholders in formatted texts no longer produces empty spaces at the end of a line.
Line breaks in formatted text previews created via ReqIF import are now displayed correctly.
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.
Creating placeholders works properly if a save action is triggered.
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.
EMF graphics can now be inserted into PREEvision formatted texts without rendering errors.
Images and OLEs exported by PREEvision are no longer distorted when imported again into a PREEvision model.
LibreOffice has been updated to resolve problems with OLE objects in IBM Doors.
When creating nested placeholders, no misleading warning is displayed.
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.

ID 17938305319212106
17938306878892084 17938309340622049 17938311461882040

Resolution
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.
ReqIF import: OLE objects with the MIME type "application/rtf" are correctly imported.
ReqIF import: The performance of the import has been significantly improved for very big scopes.
ReqIF import: Importing the same ReqIF file twice no longer leads to changes in the model due to instable list IDs.

Version 10.20

400

PREEvision 10.5

ID 17938311651362105 8682711552275772023 8682711552720992105 8682711552922323059 8682711552929783059 17938306709112105
17938307396702023 8682711552015482106 8682711552442692049 8682711552683701859
8682711551893672106 17938306022842107 17938311661192105 8682711552510132098 17938305543782065

Resolution
ReqIF import: Default values for the Object type attribute are now properly interpreted for the class matching during when using this mode.
ReqIF import: Unnecessary model tree locks for new artifacts created during a ReqIF import are no longer required.
ReqIF import: The content of CDATA sections is no longer ignored when importing ReqIF-XHTML.
ReqIF import: The import reads REQIFZ files which link the same file attachment multiple times in the same XHTML attribute.
ReqIF import: The german message text reported in the Information View for ReqIF files that are not compliant to the schema has been corrected.
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.
ReqIF import: The file choosing dialog of the ReqIF import metrics now offers to filter the shown files by compatibility.
ReqIF import: The attribute Custom ID is updated correctly during the import.
ReqIF import: When updating existing artifacts with a ReqIF import, reuses of these artifacts that are checkedin are not changed.
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.
ReqIF agreement import: For supplier comments, unnecessary space characters are no longer set.
ReqIF export: Shapes in formatted texts are automatically converted to images or OLEs.
ReqIF export: Bookmarks in formatted texts are no longer exported to avoid schema validation errors.
ReqIF export: Images and OLE objects with vertical or horizontal spacing in formatted texts no longer cause schema validation errors.
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.

Version 10.20

401

PREEvision 10.5

ID 17938307225372113 17938307570112107 17938307810772023
17938308140791807 17938308161942105
17938308177661806 17938308192542104 17938308756822107 17938309047742023 17938311460762105
8682711551829472107 8682711551881482105 8682711552283401783 8682711552292512104
8682711552337552065
8682711552458671783
8682711552458681783
8682711552462962101

Resolution
ReqIF export: Exporting formatted texts containing block quotes no longer causes schema validation errors.
ReqIF export: Correct previews are displayed for exported Visio OLE objects.
ReqIF export: In the PREEvision demo model, a typo has been corrected in the documentation block of the ReqIF export metric.
ReqIF export: The export no longer contains unwanted line breaks for plain text.
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.
ReqIF export: Attribute Definitions without data type can be exported.
ReqIF export: The reliability of the ReqIF export performance has been improved.
ReqIF export: Exporting nested lists no longer causes a schema validation error.
ReqIF export: An error message has been improved that is reported during the export for large images/OLEs.
ReqIF export: <li> elements in the exported ReqIF XHTML file are properly closed if they wrap multiple paragraphs.
ReqIF export: Attributes with localization are correctly exported.
ReqIF export: Non-printable characters in formatted texts are properly handled during the export.
ReqIF export: Tables with background colors in formatted texts no longer cause schema validation errors.
ReqIF export: If diagrams with conflicting names are correctly exported to OLE objects, without causing an endless loop.
ReqIF export: For requirement links with multiple targets only the first target is exported. The relevant requirement links are shown in the Information View.
ReqIF export: In the PREEvision demo model, an example for referencing a description has been added to the example report for specific ReqIF exports.
ReqIF export: Using the ReqIF export via report, formatted texts containing only an OLE, image, or table can now be exported.
ReqIF export: The performance has been improved for ReqIF exports containing a lot of variant information.

Version 10.20

402

PREEvision 10.5

ID 8682711552495812101 8682711552500681783 8682711552542202105 8682711552553813059 8682711552560653059 8682711552561273059 8682711552650413059 8682711552721861783 8682711552732302105 8682711552921932111
8682711553316031783 8682711553316061783
17938307705401859
8682711552275612049 8682711552442692023

Resolution
ReqIF export: The ReqIF export of structures with reuses with different branch or revision is now aborted with an appropriate error message.
ReqIF export: Using the ReqIF export via report, artifacts without name can now be exported.
ReqIF export: Custom attribute values containing only non-textual content are now correctly exported.
ReqIF export: Text sections in formatted texts no longer cause schema validation errors.
ReqIF export: Defective OLE objects embedded in formatted texts no longer cause schema validation errors.
ReqIF export: OLE objects with broken previews in formatted texts no longer cause schema validation errors.
ReqIF export: The outdated metrics "ReqIF import classic" and "ReqIF export classic" have been removed from the PREEvision demo model.
ReqIF export: The PREEvision demo model has been updated and contains valid example Attribute Definitions compatible with the changes of the ReqIF export.
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.
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.
ReqIF export: Tables with vertically merged cells no longer cause schema validation errors.
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.
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.
ReqIF export: The ReqIF export of test data no longer exports spec relations without source or target.
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.

Version 10.20

403

PREEvision 10.5

ID 8682711553047162101 8682711553181472105 8682711553655572107
8682711553517132049
8682711552419192065 8682711552442742023

Resolution
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.
ReqIF export: Centered tables in formatted texts no longer cause schema validation errors.
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.
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.
ReqIF import and export: In all example ReqIF import and export configuration files, a comment concerning the class mapping has been updated.
ReqIF import and export: ReqIF import and export configuration files are uniformly formatted.

16.5.5 Logical function architecture

ID 8682711551969802062 8682711552516761030
8682711552635661875 8682711553353022100 8682711553353032100 8682711553074502101
17938308061641806

Resolution
Missing translation for Service Required Port Groups and Service Provided Port Groups have been added.
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.
Signal Transmissions inside a Transmission Frame in a Concept Diagram snap to the grid.
Selection and highlighting of ports is now calculated after opening a Logical Architecture Diagram with Open With.
The entries in the Open With menu at a logical architecture port have been consolidated.
Assemblies with more than one Assembly Connector will not be deleted when hiding the corresponding Bus Connection.
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

Version 10.20

404

PREEvision 10.5

ID 8682711553353012100

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.
A new group has been added to the Open With menu to harmonize menu structures.

16.5.6 AUTOSAR

AUTOSAR export

ID 17938311595502051

8682711552495711825

8682711551972432003

17938307346762000 17938311611322000 8682711553044011825 17938307707902040
17938308103662003
8682711552070592053

8682711553123311912

Resolution
AUTOSAR export: the message 'Artifact doesnt have name' appears only for relevant artifacts.
Implementation data types referenced by KeyTemplateArguments and ValueTemplateArguments of Implementation Associative Maps are now exported to AUTOSAR correctly.
For the following AUTOSAR exports, initial values of NV Data are now exported correctly: > AUTOSAR ECU extract > AUTOSAR SW component description > AUTOSAR system description
Sender Receiver To Signal Mappings are now properly exported.
The AUTOSAR Cluster Extract export now correctly exports the So Ad Routing Groups.
AUTOSAR package structure is now stable for consecutive exports.
Secure-Communication-Props for AUTOSAR version 4.2.2 have been implemented and are now imported and exported.
On export, AUTOSAR ApplicationArrayElement.ShortName is in every case taken from Name of the Application Array.
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.
The AUTOSAR export does not export empty Multi Value Attribute Definitions of type "Enumeration" anymore.

Version 10.20

405

PREEvision 10.5

ID 8682711553545952052 8682711552005871992 8682711552492321806 8682711552539441917 17938309027902051
17938309273472042
17938311405181792
17938311513152108 17938311631452052 17938311673342108 8682711552262711030 8682711552341932014

Resolution
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.
Symbols and Japanese characters are now properly handled during AUTOSAR export.
The attribute CATEGORY of ClientServerInterface is now imported and exported.
For the AUTOSAR import and export, the attribute Approval Status of an Evaluated Variant Set is now considered.
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.
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-6CONFIGURATION with the attribute IPV-4-ADDRESS or IPV-6-ADDRESS and value ANY.
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.
For the AUTOSAR software component description, SWC Implementations are now correctly exported.
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.
Unused Calibration Parameter Record Layouts can now be exported using a custom export and the option No Datatype Restriction.
AUTOSAR admin data for SOME/IP Transformation Properties with multiple usages are properly exported now.
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.

Version 10.20

406

PREEvision 10.5

ID 8682711551967072051
8682711552082781913 8682711552396242051 8682711552421080000 8682711552475061029 8682711552866322004 8682711552947280000 8682711553125792003 8682711553171531825 8682711553346541998 17938309299042040 8682711552647131024 8682711553356011024
8682711553487001024 8682711553114132159

Resolution
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.
UUIDs created for implementation data types during AUTOSAR export are now stable on every consecutive export.
The value HEADERTYPE_NONE for the attribute Header Type of Container IDPUs is now imported and exported.
So Ad Routing Groups are now properly exported in cluster extracts.
An ECU communication extract is now possible while using a Function Designer license.
ECU communication extract now exports implementation data types.
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.
Data Constraints that are referenced multiple times are now correctly exported as single artifact to AUTOSAR.
The attribute Constraint Level of data constraint rules is now properly exported.
SW component descriptions now export the initial value of constant memory.
Importing Associative Maps in AUTOSAR Classic files is disallowed. Exporting implementation data types without CATEGORY is avoided.
End To End Transformation Com Spec Props are now imported from AUTOSAR and exported to AUTOSAR properly.
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.
Name and option value of a Startup Option are now both exported as Process Arguments to AUTOSAR. The order name - option is always maintained.
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.

Version 10.20

407

PREEvision 10.5

ID 17938307707902040, 17938307710382003
8682711553547751024

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

AUTOSAR ECU extract ID 8682711551967081806 8682711553098930000 8682711551972032003
8682711552494842052 8682711551942991913 8682711552942822107 17938309311881914 17938307711722003 8682711552299811917 17938311454432004

Resolution
AUTOSAR ECU extract: now correctly propagates and exports the relation targetModeDeclarationAccess on the artifact Mode Switch Event.
AUTOSAR ECU extract exports the Addressing Method for Parameters of Parameter Interfaces correctly.
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
IDENT of the TpConnection, LinSlaveConfig and PncMapping is now always exported.
For an AUTOSAR ECU extract, Generic Physical Data Constraints for Application Curve Types, Application Map Types, and Application Cube Types are now properly exported.
From some special model configurations, not-used Signal IPDUs have been exported via ECU extract. That has been fixed.
Referenced invisible artifacts from the global Administration do not abort the ECU extract anymore.
During the export of an ECU extract, no foreign payload PDUs (payload PDUs of foreign ECUs) are exported anymore.
The export of an ECU extract can be properly executed if the data to be exported contains mapped Logical Functions.
Data IDs of end-to-end Profiles are now propagated and exported in ECU extract and system extract.

Version 10.20

408

PREEvision 10.5

ID 17938308170251032 17938306059752088 17938307558851024 17938309250770000
8682711551958391913 8682711552287352014 17938308264691825 17938308170241032

Resolution
Implementation data types connected to Signals will no longer be exported.
Data mappings and signal ports are not exported anymore in the case the contained multiplex PDU is transmitted over the gateway.
The ECU extract now exports TransformationComSpecProps.
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.
For an ECU extract, the physical values of Axis Literals are now correctly exported.
In the ECU extract, the payload of Secured IPDUs is now properly exported.
A transformation error which occurred during the export of an ECU extract has been resolved.
In the ECU extract, the data type of a Typed Per Instance Memory is properly exported.

AUTOSAR system description

ID 8682711551833761024 17938311321502040
8682711551895991825 8682711553067141909

Resolution
For an AUTOSAR system description, SEC-OCCRYPTO-SERVICE-CONFIGURATION is now correctly exported.
Service Interfaces are no longer exported via AUTOSAR System Description. The mixing Classic and Adaptive contents is not supported by any PREEvision AUTOSAR export.
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.
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.

Version 10.20

409

PREEvision 10.5

AUTOSAR adaptive exports

ID 17938307437292010 17938307763071024
17938307941152088
17938308210710000 17938308224821025 17938308321812040 17938309287992010 17938309365152010
17938309378680000 17938311323312052, 17938311323322052 17938311394732052 17938311724772052 8682711551904770000 8682711552446501913 8682711552484981913

Resolution
Process to Machine Mappings are now fully exported to AUTOSAR within the execution manifest.
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 SWNET:Component Mapping.
The references of an interface mapping to VARIABLEDATA-PROTOTYPEs and CLIENT-SERVER-OPERATION are exported as open references in the Adaptive application description.
For the AUTOSAR application description, the defined Namespace hierarchy is considered now.
The suffix automatically generated for RootSwComponentPrototype names during AUTOSAR export has been removed.
Base Types assigned to CPP-IMPLEMENTATION-DATATYPEs are no longer exported.
SOME/IP Transformation Properties and User Defined Transformation Properties are now also propagated to the service interface description.
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.
The propagation of process execution dependencies has been added to the software cluster design description.
Application Errors referenced to UML Methods via Application Error Groups are now also propagated to the software cluster design description.
For the AUTOSAR software cluster design description, Namespaces which are referenced by Application Error Packages are now exported.
The AUTOSAR software cluster design description has been adjusted to handle several cases of faulty open references in the exported AUTOSAR files.
The timeout set for a Machine Deployment are now correctly exported into a Machine Manifest.
Template arguments are now also exported when the Long Name is set.
ApplicationErrorDomain.value is now correctly imported and exported. The reference between ApApplicationErrors and ApApplicationErrorSet is now correctly imported as well.

Version 10.20

410

PREEvision 10.5

ID 8682711552510112051 8682711552640342051 8682711552688542010
8682711553161901024
8682711553295471024 8682711553437491002 8682711553454391024
17938307379383010 17938307756770000 17938307822191024 8682711553501581024
8682711552994941792

Resolution
References from application data types to Computation Methods are now exported in AUTOSAR software cluster design descriptions and service interface descriptions.
The import and export of TLV data IDs for application and implementation record elements has been fixed.
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 SOMEIPEVENT-PROPS.
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.
A bug has been fixed which caused multiple references between the same ApApplicationError and ApApplicationErrorSet if the set was referenced by multiple users.
The AUTOSAR service instance manifest export does not export ServiceInstanceToPortPrototypeMappings anymore.
Key Template Argument is now correctly exported as CPP-TEMPLATE-ARGUMENT with CPP-TEMPLATEARGUMENT.category == ASSOC_MAP_KEY, value Template Argument as CPP-TEMPLATE-ARGUMENT with CPP-TEMPLATE-ARGUMENT.category == ASSOC_MAP_VALUE.
Service Interfaces are not exported to the service instance manifest anymore.
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.
Adaptive internal behavior and its service dependency is now propagated and exported in the Software Cluster Design Description (formerly Adaptive Application Description).
A logic has been added to keep the IDs of SIGNALBASED-EVENT-ELEMENT-TO-I-SIGNALTRIGGERING-MAPPING stable over multiple AUTOSAR exports if the EventPlatformDataTypeMapping does not exist in the PREEvision model.
Signal IPDUs are always exported with complete ISignalToPduMappings, even in signal-to-service scenarios, when some Signals are of no interest.

Version 10.20

411

PREEvision 10.5

AUTOSAR import

ID 8682711553462111024 8682711553553362052 17938308165762101 17938308183582051
17938308952171992
17938309215602108
17938309286952108 17938309312311792 17938309322152108 17938311478870000 8682711551928361030 8682711552942720000 8682711552918202003 17938307437571792

Resolution
Software cluster designs without category can be now imported- It will be considered as ROOT_SOFTWARE_CLUSTER.
The import of IMPLEMENTS-SOMEIP-STRINGHANDLING has been corrected for AUTOSAR 4.4 and lower.
On AUTOSAR import, for COLLECTIONS without CATEGORY it is assumed that the CATEGORY=SET (fallback defined in the standard).
During AUTOSAR import, the model transformation error which occurred during the merge of an APPLICATIONVALUE-SPECIFICATION of CATEGORY=MAP has been fixed.
The import identifies the inconsistent reference GLOBALTIME-DOMAIN.MASTER used in lower versions than the AUTOSAR_00046 schema and stops the import reporting an error message in the Information View.
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.
During AUTOSAR import with replace, Addressing Methods are updated, now.
AUTOSAR import with merge/replace: COM-SPECs of PR-Port-PROTOTYPEs are now updated correctly.
During AUTOSAR import with replace, the "Replace" block correctly outputs processed roots if artifacts change their meta class during replace.
During AUTOSAR import with merge, inconsistencies between types, prototypes, and instances due to Assemblies with missing UUIDs no longer lead to errors.
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.
AUTOSAR Classic files containing AUTOSAR Adaptive machines can be imported again.
APPLICATION-VALUE-SPECIFICATION whose value is stored in a Vt object will also be correctly imported
SomeIpDataTransformationProps for primitive ArgumentDataPrototype are now imported for AUTOSAR Adaptive.

Version 10.20

412

PREEvision 10.5

ID 17938307443551024 17938309304732052 17938309312321790 17938309330302040
17938311664551024
8682711551924621840 8682711552709282064 8682711553029582005
8682711553029101825 8682711553191072052 8682711553551321825
17938311660911998 8682711553553362052 17938307618971874

Resolution
During AUTOSAR import, application to implementation data type mappings are created for CPPImplementation-Data Types, too.
During AUTOSAR import with merge, the DataID sequence of an E2E profile is now updated.
The Property View for Data Constraints no longer highlights the values "INF", "-INF" or "NaN" entered in Min or Max as an error.
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
SecOC Service Configuration is now correctly imported. The SecOC Service Configuration receives a name based on "SecuredIpdu.name" and the suffix "_SecOcConfiguration".
During AUTOSAR import with merge, UdpTp, TcpTp and HttpTp elements are merged if all their attributes have set the same values.
For AUTOSAR import with merge the messages have been improved to indicate changes in custom attributes.
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.
The performance for calculating ImEx-IDs during AUTOSAR import with large tree structures of AUTOSAR parent hierarchies significantly has improved.
AUTOSAR software component updates can now be started on all classic software component types via context menu.
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.
Improved update handling of large model trees during AUTOSAR or DBC import.
The import of IMPLEMENTS-SOMEIP-STRINGHANDLING has been corrected for AUTOSAR 4.4 and lower.
Software component update: During a software component update, the automatic model update performed when locking the artifacts needed for the update is handled properly.

Version 10.20

413

PREEvision 10.5

ID 8682711552446662043

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

16.5.7 Software architecture

ID 17938309286651995 17938305258342108
17938307564532052 17938307939282010 17938308089032051 17938308195152113 17938308928020000 17938309524372004
17938311341171843 17938311480253039 8682711552088162108 8682711552692141913

Resolution
Definitions Sets for defining custom attributes can be assigned to Software Deployment and Software Partition Package.
Delegation ports can now be populated on the background of Composition Type Diagrams, Partial Composition Type Diagrams, and Software Architecture Diagrams.
The Connect Ports with Identical Interfaces refactoring now correctly connects only ports with identical interfaces.
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.
The automatic figure completion DnD operations can now be deactivated via a toolbar button in Partial Composition Type Diagrams.
The refactoring Change Type To Enumeration Type for Application Integer Types is corrected and child artifacts of Application Integer Types are correctly converted.
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.
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.
In Interface Assignment Diagrams, Adaptive ports for Composite Types can now be added via palette.
The performance to open the Port Configuration dialog with large number of ports has been significantly improved.
Usability and performance have been improved for the Convert SW Component Type dialog. The dialog now provides additional filtering options.
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

Version 10.20

414

PREEvision 10.5

ID
8682711553044042013
8682711552915332052 17938306043741029 17938307004132040
17938294355789393
17938305951031912 17938311317882042 17938311390142107 17938311445712049 8682711552764452108 8682711553281571998 17938306961981806 8682711552398361914

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.
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.
The Consistency Check ,,Data type consistency" has been removed.
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.
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.
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.
The Start Position of Signal-IPDU-Assignments via drag and drop in the Model View is calculated correctly.
For SOME/IP Communication Connector Assignments, the dereference action in the table on TpIp Configuration property page.
The Property View of Bus Connectors shows additional information about PDUs, signals, and frames.
An error on Timing property page of Port Communication Requirements has been corrected.
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.
A menu entry to create a Constant Memory on Internal Behavior is now available.
The move ports action via <F7> in Software Architecture Diagrams and Logical Architecture Diagrams now places the moved delegation ports on the grid.
The refresh of mapping boxes has been improved. Internal mapping boxes in locked diagrams now refresh immediately.

Version 10.20

415

PREEvision 10.5

ID 8682711552433472052 8682711552716432013 17938307342772052 17938307443662108
17938307538882108
17938308234112104 17938309213622113 17938309386102052 8682711552495032051 8682711552867692108 8682711552982362003 17938311629282088

Resolution
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.
The Software Architecture Diagram displays the right icon for Compositions.
Both references Internal to Physical and Physical to Internal on Computation Methods are represented readonly but navigable in the Property View. The add and delete buttons are still active.
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.
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.
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.
The Property View has been adjusted regarding the assignment of a Validity for data constraints. A dropdown list has been added for assignment.
In the Property View of an Application Error, a drag and drop of an Application Error Group is possible now.
The Property View of Composition Prototypes now correctly displays the connected ports.
For Axis Literals, the Array Size attribute has been added to the Constraints property page of the Property View.
On General page of implementation typed artifacts in the Property View, Implementation Data Type has been removed.
On General page for Application Error Packages in the Property View, the attribute Value has been added.

Version 10.20

416

PREEvision 10.5

ID 8682711552101931825
17938309033632159 17938311515452113 8682711553140721806 8682711553281631998 8682711553343442043 8682711553285641917
17938307566901918

Resolution
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.
During Show Path operation, a message is shown if a connection cannot be displayed caused by a missing connection in the current diagram.
In tables, minimum and maximum values of Generic Physical Data Constraints can be properly set.
In the Property View of an Atomic SW Component, Application Partitions can be dereferenced from software instances.
In the Property View of a Constant Memory, the initial value can be set.
The Property View displays the Unit of relevant literal artifacts.
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.
In State Machine Diagrams, the Condition label can be reseted. Also, the labels defined in the object configuration can be displayed.

AUTOSAR Adaptive

ID 17938308156011810
17938308279211280

17938306286902010, 17938311481711810
17938308923200000

17938309117622003

Resolution
Execution Contexts are now displayed in the SOME/IP Service Instance Editor.
Computers, ECUs, Sensor/Actuators, and Execution Contexts underneath a Component Composite are now also displayed in the Service Instance Editor.
The column name in SOME/IP Consumed Service Instance SD Editor has been changed from Service ID to Service Instance ID.
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.
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.

Version 10.20

417

PREEvision 10.5

ID 8682711552726982010

Resolution
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 export

ID 17938308264962040
17938311342742040 17938311378662040 17938311394782048 17938311394792048 8682711552515761807
17938311484132040 17938309053212040

Resolution
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.
Franca export: The exact order of method parameters is maintained during the export.
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.
Franca import and export: Getter, Setter, and Notifier attributes of a Property are now considered.
Franca export: The order of Application Enumeration literals is maintained during the export.
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.
Franca export: The export cannot contain package names with spaces or other invalid characters anymore.
Franca import: Imports of incorrect FIDL files will now be aborted and an error message will be displayed in the Information View.

16.5.8 Diagnostics
ID 17938307506632005
17938305189392105
17938307004182113

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

Version 10.20

418

PREEvision 10.5

ID 17938307370192012
17938307544492113 17938307571432113 17938307740312007 17938308161532005
17938308185752007 17938308272772007 17938309053312007 8682711551930692108
17938308185752007 8682711551998222005 8682711552726661875 8682711553277282196

Resolution
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.
Moving Diagnostic Data Objects does not delete IDs anymore.
The drag and drop menu Move before/after <specific diagnostic data identifier> between Diagnostic Data Identifiers is removed.
Software ports with Sender Receiver Interface are collected again by the Propagate Definition "R100_DiagMaster_DetailedEE".
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.
A suborder is properly created for Diagnostic Data Objects created in the DID table of the Diagnostic Specification Explorer.
When creating a Sender-Receiver Interface or NV Data Interface for Diagnostic Data Objects, the attribute isService is set to false.
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].
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.
A suborder is properly created for Diagnostic Data Objects created in the DID table of the Diagnostic Specification Explorer.
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.
Improved performance for opening and switching tables in the Diagnostic Specification Explorer.
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.

Version 10.20

419

PREEvision 10.5

ID 17938308763181038
8682711552713681995
17938309056882040, 17938309334922040
8682711553303411909

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

Diagnostic import and export

ID 17938308029872113

17938311484122005
8682711552417771875 53751837, 17938308176852005 17938307384882113

17938307956582100 17938308030652113

17938308048312005 17938308050832007

Resolution
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.
Diagnostic import: The name of the reference Product Line is now set to "RefPL_" + PREEvisionCANdelaDiagnosticData.ShortName.
Diagnostic import: The import of not supported model versions of the diagnostic exchange format is denied.
Diagnostic export: The export results of diagnostic models are the same regardless of whether started by wizard or context menu.
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.
Diagnostic export: A diagnostic export is now possible for models with software Compositions without software components.
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.
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".
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.

Version 10.20

420

PREEvision 10.5

ID 17938308187512007
17938308192372007 17938308205162100
17938308264692007 17938308325512007 17938311629832005 8682711553277502005

Resolution
Diagnostic export: ContextPortReference (CPR) have been removed from AsrServiceDependencyRefs that are created during export.
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.
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.
Diagnostic export: Scale Linear Verbal Table Conversions are not supported in the diagnostic exchange format and therefore excluded from the export.
Diagnostic export: If unsupported data types are modeled in the context of a diagnostic export, these data types are ignored for the export.
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.
Diagnostic export: Default values of attributes, like 0, are now written to PVCDI if set explicitly in PREEvision.

16.5.9 Communication
ID 17938304993491003 17938286082770455, 17938300527352040 8682711552939001917 17938307783892004
17938305543132107 8682711552651461917
17938307811552040

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

Version 10.20

421

Signal router

PREEvision 10.5

ID 17938307811702040 17938305809042040 8682711552692181913
17938307161232108 8682711552262722004 8682711552553711998
8682711552929780000

Resolution
In the Secured PDU Editor the naming of columns has been correct.
Under an end-to-end profile, Data IDs can be ordered.
The alignment in tables with several Data Elements and the corresponding communication specification has been corrected.
The refactoring Connect Ports (Identical Interface) works again.
Metrics for the J1939 library use case and the J1939 catalog option in new menu have been removed.
The Property View of an ECU Interface now displays Signal Groups in the Selected I-Signals table. Additionally, drag and drop actions are supported.
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.

ID 17938308088182088 17938299783622040
8682711552720781917
8682711553125511995 8682711553653852043 8682711552558131909

Resolution
Signal router: The signal router does not create Generic Controller Configurations for Ethernet interfaces anymore.
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.
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.
PREEvision user manual now provides a more detailed description for the usage of constraints to influence the signal router.
The signal router uses correct data types to calculate the signal length when routing complex data types to multiple receivers using system signals.
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.

Version 10.20

422

PREEvision 10.5

ID 8682711552726050000 8682711553338801029 8682711553062110000 8682711553262391807
8682711553076021807
8682711553048351807 8682711552997071807 8682711553075471807 342088 8682711553338801029 17938306994952004 17938307210601024 17938307369951030 17938307557601794

Resolution
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).
An error in the signal router has been fixed which did not allow synthesizing PDU Transmissions for Container IPDUs.
The signal router now does not create Signals for composition ports (delegation ports) which are no communication end points.
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).
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.
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.
The signal router does not consider PDU Transmissions for non-Ethernet busses. Potentially obsolete PDU Transmissions are only cleaned up for ethernet channels.
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.
The relations between Signal Transmissions and the signal output port are now updated properly after running the signal router.
An error in the signal router has been fixed which did not allow synthesizing PDU Transmissions for Container IPDUs.
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).
If several VLANs are available, the signal router now handles them in a deterministic way.
The signal router does not require any locks for temporary existing artifacts, including marker and flag changes on related artifacts.
Highlighting of transmissions now considers ECU interfaces for highlighting their corresponding Bus Connectors.

Version 10.20

423

PREEvision 10.5

ID 17938307769411024 17938307769711030
17938307940771024
17938307948341807 17938307959191807 17938308161762005
17938308174511807 17938308245522040 17938308763412040 17938308898421807 17938308926091807 17938308926121807

Resolution
The signal router now updates complex data type signals/mappings for signal groups with set data transformer.
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
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.
In case signal routing is possible for multiple VLANs, signal routing always provides in a deterministic routing result.
The signal router considers the preferred VLAN for routing. If no preferred VLAN is available, the signal routing provides a deterministic routing.
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.
The signal router now considers and reuses existing transmissions for Fire and Forget Methods.
The signal router does not fail when called via custom block and misconfigured ports on Port Adapters are recognized during routing.
Signal router considers existing System Signals and Signals in mixed (Classic/Adaptive) routing scenarios that were partially routed before.
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.
The signal router removes unused PDU Transmissions of type Signal IPDU which do not contain Signal Transmissions anymore.
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.

Version 10.20

424

PREEvision 10.5

ID 17938309273581807 17938309273601807 17938309277122040 17938309281082040 17938309294661807 17938309294751807
17938309296461807 17938309296631810 17938311324841810
17938311341932005
17938311341942005

Resolution
For models with a Port Adapter, the signal router provides similar results for initial routing and later updates.
For models with Fire and Forget Methods, the signal router provides similar results for initial routing and later updates.
If the signal router is called via metric, the currently used router configuration is now displayed in the error message.
The signal router now creates method instances for getter and setter functions of SOME/IP Properties in Service Instances.
The routing of Methods and Properties now leads to two Signals per port pair, one call Signal and one return Signal.
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.
The signal router considers update scenarios in combined systems with Adaptive and Classic software components.
For AUTOSAR Adaptive communication with Events, the signal router creates one Signal Transmission for multiple receivers (instead of one per receiver).
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.
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.
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.

Version 10.20

425

PREEvision 10.5

ID 17938311391581025
17938311430352051 17938311457761810 17938311637001825 8682711551703241810 8682711551793001810 8682711551802241030
8682711551832901787 8682711551834421810 8682711551926742051 8682711551940022052 8682711552499302159 8682711552540651998

Resolution
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.
For signal routing, the Information View provides additional information about deleted PDU Transmissions and Signal Transmissions.
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.
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.
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.
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.
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.
When routing complex data types in combined Adaptive/ Classic scenarios, existing Signals that are not useable for the current ports are not reused anymore.
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.
After setting up the Tx/Rx design in the Communication Design Explorer and using the signal router, no duplicate artifacts are created anymore.
The signal router now properly creates Event to Signal Mappings as well as Method to Signal Mappings for a serialized service.
The signal router now calculates all possible routing paths when using the "BruteForce" algorithm in a deterministic way.
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.

Version 10.20

426

Ethernet communication

PREEvision 10.5

ID 8682711552545052069 8682711552760992010 8682711552920011998

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

ID 17938292522079239 17938307666912040 17938307801331807 17938307832182040
17938308850462040
17938309338122040 17938311661050000 17938311667691810
8682711552092072042 8682711552421100000 8682711553103332051 17938306277222050

Resolution
In the SOA & Ethernet Explorer, postings in the Information View have been improved for the metric Calculate Header ID.
The calculation of the Message ID in the SOME/IP Interface Deployment Editor has been corrected.
The metric for the AUTOSAR Classic technology mapping has been corrected. Interface relations are now set by creating or updating data types.
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.
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.
A duplicate consistency check "DefPCPAssPrioNotSet" has been removed.
In the category Data Serialization of the SOA & Ethernet Explorer, all Layout Packages that are contained in Communication are displayed recursively.
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.
The metric for service discovery subscription has been corrected to create So Ad Routing Groups for services with properties only.
The signal router now takes over data of Services from abstract UML level to concrete Service Instances in the Communication layer.
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.
Filtering functions in the Network Topology Editor have been improved.

Version 10.20

427

PREEvision 10.5

ID 17938306277642050 17938306642042050 17938309264311810
17938309247681810 17938306962612003
8682711553215501998

Resolution
The ECU Definition table supports IPv6 addresses.
Information about IP configuration has been added to the ECU Definition table.
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.
The performance of the Artifact Picker used in the Service Deployment Editor to display the services has been improved.
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.
On the Identifier Parameters property page for Socket Connection IPDU Identifiers, the attribute Collection Semantics has been added.

DBC import and export

ID 17938311322921032

8682711553089142065 17938308185511032

17938308195872004 17938309243111032 8682711553302121030

Resolution
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.
DBC export: A consistency check identifies incorrect modeling of nodes, based on subtypes of the abstract class ElectricElectronic in PREEvision.
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.
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.
DBC import: Multiplexed IPDUs defined with DBC notation "SG_MUL_VAL_" are supported for the DBC import.
DBC import: For every DBC Signal Group also a Signal Transmission is created in PREEvision.

Frame PDU synthesis

ID 17938305201232092

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

Version 10.20

428

PREEvision 10.5

ID 17938307943551913 17938309236962024 17938309237092024 17938309303511917 8682711552287142014 8682711552401662014 8682711552419241917
8682711552431992003 8682711552432612003 8682711552435892003 8682711553096202004 8682711553138491807 17938311661601995 17938301216491992

Resolution
The Frame-PDU synthesis now keeps existing the PDU Transmissions of long I-PDUs handled by a transport protocol.
Extended Information View content to point out missing and mismatching Bus Types during Frame-PDU synthesis.
The Package Selection dialog of the Frame-PDU synthesis supports the deletion packages via the "Delete" key.
The Frame-PDU synthesis completely ignores PDU Transmissions and Frame Transmissions for multiplexed IPDUs to support manual modeling.
The Information View now shows the complete results of the Frame-PDU synthesis.
Contained PDU Transmissions of multiplexed PDU Transmissions will not be assigned to Frame Transmissions by the Frame-PDU synthesis anymore.
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.
The Package Selection dialog in the Frame-PDU synthesis shows all labels and icons of artifacts.
For XCP PDU modeling, the warning message for the Frame PDU synthesis result reported in the Information View has been adapted.
Nm PDUs, both with and without assigned Signals, are considered during Frame-PDU synthesis.
The Frame-PDU synthesis does not create unnecessary Frame Transmissions for J1939Tp-PDUs anymore.
The Frame-PDU synthesis now keeps existing PDU Transmissions and Frame Transmissions if new Signal Transmissions are added.
Behavior of the package selection has been harmonized between Frame-PDU synthesis started in the Model View or via signal router.
The Frame-PDU synthesis now also supports multiplexed IPDUs.

Version 10.20

429

PREEvision 10.5

Signal and PDU length calculation

ID 17938307167352042

17938309279962159 17938309373292159
17938309408382159 17938309408392159

Resolution
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.
The length calculation has been improved to support Implementation Union data types.
The length calculation for communication artifacts now correctly handles Implementation Data Pointers for strings on implementation data type side.
The length calculation for communication artifacts now adds the correct padding for already aligned arrays.
The length calculation for communication artifacts can now handle a string length attribute from the SOME/IP Transformation Properties.

LDF import and export

ID 8682711552729751917

8682711552611791998

8682711552061911917

Resolution
LDF Import: Scalar initial values of Signals are now always imported as integer.
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.
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).

16.5.10 Hardware architecture

ID 17938307760502050

Resolution
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.

Version 10.20

430

PREEvision 10.5

ID 8682711552640442102 17938307941342041
17938309341102083 8682711552432812083 8682711553529001037
8682711552945132010 8682711553461271994 17938294625869051 17938307619951806

Resolution
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.
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.
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.
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.
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.
In the New context menu of a Sensor, Actuator and Sensor/Actuator, the context menu item Hardware and all submenu items are available now.
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.
External connectors can be copied without external relations via drag and drop in the Model View.
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.

Version 10.20

431

PREEvision 10.5

ID 17938307570122112 8682711552578201994, 8682711552578351994 17938309381191868 17938311321961995
17938286989688157 17938309371221995 17938308273591877 17938309327662083 17938311665181037 17938311697332083 8682711552654382112
8682711553306161038

Resolution
When selecting multiple Schematic Pins, the pin numbers of the Wire Pins of the Schematic Pins can be changed simultaneously in the Property View.
A Core Prototype or a Shielding Prototype can be 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.
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.
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
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.
The Select Connector Prototype dialog now provides a filter which supports the filtering of Product Lines (Local, Local and upstream, and Global).
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.
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.
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.
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.
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.
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

Version 10.20

432

PREEvision 10.5

ID 17938309340592083
8682711552738522083 8682711553076072083 8682711553342602083 17938307556552034 8682711552039102034

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.
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
The model tree extension rules in the "Wiring Harness Demo Model" Product Line in the PREEvision demo model have been reorganized and completed.
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.
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.
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.
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 hardware architecture

ID 17938308152221037

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

Version 10.20

433

PREEvision 10.5

ID 1792439489051
17938307262231804 17938308923242112
17938311629832081 8682711553146062099 17938308054452083 8682711552639693065 8682711553124341912 8682711553270132046 17938307169912112 17938309118222045 17938309315761037 17938301235711025

Resolution
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.
Applying the function Split Connection on a checked-in Wiring Diagram correctly results in a check-out and the application of the function.
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.
In Wiring Diagrams, the pop-up bar is displayed again when selecting a Splice or a Schematic Pin.
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.
The error highlight for cable symbols in a Wiring Diagram is now instantly calculated and therefore activated or deactivated.
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.
Wiring Diagrams containing a cable symbol with a constraining object configuration can be opened without displaying an error.
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.
Wiring Connectors of Wiring Harness Inline Connectors are properly displayed in a Wiring Diagram via the populate function <F8>.
The error in the context of opening Wiring Diagrams which has caused a deadlock, has been resolved.
In a Wiring Diagram, a component can be removed from the diagram via the shortcut <Del>.
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.

Version 10.20

434

PREEvision 10.5

ID 17938308840512112
8682711553265912034 17938307606732112 17938309412512041 8682711552335141843, 8682711552335151843 8682711552437741994 8682711552588051843 8682711553162301268
17938307942442041

Resolution
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.
The diagram framework has been improved to correctly remove corrupt connections from the Wiring System Diagram.
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.
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.
In the Wiring Diagram or Electric Circuit Diagram, a 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.
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.
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.
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.
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

Version 10.20

435

PREEvision 10.5

ID
8682711552502922112 17938308161071037 17938309300511877

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.
Checked-in diagrams are not checked-out anymore when reusing and committing them.
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.
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 autolayout diagram

ID 17938307398262112 17938307704641914 17938308754632109
17938308754652109 17938308772892081 17938307568522073 8682711552101902036 8682711552376552036

Resolution
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.
Improved auto-layout refactoring regarding Splice networks connected via Single Wires.
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.
Creating an autolayout diagram for a checked-in diagram works properly now, particularly for diagrams with Title Blocks containing images.
When creating an autolayout diagram all labels (embedded, midpoint and endpoint labels) are displayed instantly.
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.
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.
The algorithm of handling Splices in an autolayout Wiring Diagram has been improved in case the model-based metric block has been used.

Version 10.20

436

Refactorings

PREEvision 10.5

ID 8682711552510132036 8682711552540612036 8682711552544622036 8682711552545162036 8682711553036282036 8682711553036512036 8682711553036562036

Resolution
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.
The autolayout Wiring Diagram algorithm has been modified in a way that no exception occurs anymore in a certain constellation of artifacts.
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).
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.
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.
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.
Splice sorting has been improved for an autolayout Wiring Diagram. This results in fewer unnecessary crossings of wires.

ID 17938308312161029 17938309328881037 17938311670362081
8682711552409022062

Resolution
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.
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.
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.
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.

Version 10.20

437

Synthesis

PREEvision 10.5

ID 8682711552486221868 17938311484662112 17938307349782112 17938293419069328 17938307713042041
17938307572791912

Resolution
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.
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.
Wires are now correctly displayed in Wiring System Diagrams after a refactoring from an Electric Circuit System Diagram.
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.
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.
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.

ID 17938307688011877
17938307697031877 17938307570302034 17938308925201914
8682711552971212083

Resolution
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.
When synthesizing new Cables during wiring harness synthesis, the correct Cable Prototype is considered to create Cores based on the same Cable Prototype.
A circuit synthesis on a connection with a Splice works properly, now.
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.
The settings in the Circuit Synthesis dialog are now persisted for the current session.

Version 10.20

438

PREEvision 10.5

Object and label configuration

ID 8682711552291062039 17938311408472041
17938308131271992 8682711551845672112

Resolution
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.
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.
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.
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 8682711552944961031

8682711553142191782

Resolution
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.
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 17938308932291038
8682711552944951031

Resolution
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.
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.

Version 10.20

439

PREEvision 10.5

KBL import and export

ID 17938309232772036

17938309368462083

17938311409241806 8682711552693651204

17938308184671912 17938307522901031 17938308035221995

Resolution
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.
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.
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.
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.
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.
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.
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.

16.5.11 Geometry
ID 11912

Resolution
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.

Version 10.20

440

PREEvision 10.5

ID 17938309342182036 17938309312032083 17938307346571037
17938309328932083 8682711551829572039 8682711551971991914 8682711553066032036

Resolution
The workspace defined on a Geometry Package is now considered when creating topology artifacts inside an Installation Space within a Geometry Diagram.
The refactoring Set Topology Coordinates, which can be started on a Geometry Diagram, now also works with Connector Locations.
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.
The bundle diameter calculation of Topology Segments was improved. In addition, a new calculated label was added to the demo model.
Formatting of numbers via label configuration is possible again.
The logging of changes in a Geometry Diagram was improved. Commit errors caused by rearranging artifacts in the diagram are not displayed anymore.
The Show Topology Placement Condition in Component Package table can now be opened on a Hardware Component Package.

16.5.12 Product line engineering

ID 17938308928012068
17938308928022068
17938307942792108 17938309232782082 17938309246722082 17938307954151855

Resolution
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.
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.
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.
During the revocation of an Asset, no exception occurs anymore if some artifacts of the revoked artifact are out of scope.
A merge no longer changes the checked-in parent reuses.
Non-versioned artifacts are excluded from Propagate Definitions to show rule modelers that these artifacts can be assigned themselves to Assets.

Version 10.20

441

PREEvision 10.5

ID 17938309365222112 17938311451952049 8682711552943021917 8682711552436172108 17938307718062034 8682711552049021825 17938309309402049 17938307381192108 17938309213672101 17938308077601877 8682711553454762108 8682711552015141914 17938307739972012 8682711552410962003
17938307304442108
17938308077882012

Resolution
The check-in validator for the Asset hierarchy now only checks the core/boundary artifacts of a hierarchy path, not of the sibling path.
Localized attributes retain their value after delivery via Asset.
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.
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.
A repeated import of the same import file containing the same import data, does not check out any Propagated Assets anymore.
After an import with model merge operation, which has caused the name change of a core artifact, the corresponding Asset is checked-out.
Refactoring a Table Proxy now also works if the Table Proxy is reused as an effective core artifact of an Asset.
Metric class files are correctly loaded after several Metric Packages have been moved.
The check-in block in the metric now returns a correct error message when the check-in validator of the Asset is triggered.
The exception error after removing a non-existing save point when using the customized block "Update from Predecessor (multi)" has been fixed.
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.
In a system Asset, the Slot Prototype, Slot Type, Cavity Prototype, and Cavity Type for a Wiring Connector are propagated.
The data type of primitive specifications is now included in software component type Assets.
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.
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.
SWC Implementations are versionable themselves. The parent is not collected anymore by the propagation rule. This prevents the unnecessary check-out of packages.

Version 10.20

442

Asset update

PREEvision 10.5

ID 17938308194691995
17938308050132012 17938308061592012
17938308272822112 17938308319502112 17938309365232112
8682711552023842023

Resolution
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.
Assets for software instances now pick up existing Assets for Diagnostic Trouble Codes and Diagnostic Data Identifiers.
The Diagnostic Trouble Code propagation definition propagated artifacts which belong to Diagnostic Event. This part has been moved to the Diagnostic Event propagation definition.
The navigation to non-integrated artifact in the Model View is now possible from the Information View, tables, or diagrams.
The navigation to Assets via model queries, tables, diagrams, or Information View is possible now.
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.
The message in the Information View has been enhanced for the "Extract Asset to Product Line for Agreement" use case.

ID 17938306339461877 17938307232182100 17938307302222052
17938307453881877 17938307469321877 17938307555342112

Resolution
The incorrect revocation of the integration in foreign Assets during Asset update has been corrected.
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.
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.
After an Asset update, too many artifacts in the foreign Asset were revoked unnecessarily. This problem has been resolved.
The wrong check-out of foreign Assets after Asset update due to neutral changes of boundary artifacts has been corrected.
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.

Version 10.20

443

PREEvision 10.5

ID 17938307556592082
17938308048642101 17938309243282112
17938309246122082 17938309247292082 17938309300481030 17938309309392049 17938311466212112
17938311466432112 17938311552722049 8682711553258601030 8682711553315951030
8682711553356001806 17938311642222049 17938308210251877 8682711552632661995

Resolution
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.
An instance is not checked-out anymore if the type was not changed during Asset update.
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.
An Asset update from predecessor is now possible if reused types, and their reused instances are also referenced in the Asset.
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.
Updating a structural type-of instance after an Asset update now works correctly when multiple ports of the type were removed during the update.
The replace from history logic of an Asset update with type change now correctly handles order-relevant composites of non-versionable child artifacts.
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.
The missing check-out status of a Propagated Asset during the Asset update in the migration use case is now fixed.
An Asset update now keeps the local reuse sequence for child artifacts of newly added core/boundary artifacts of the Asset.
The unintended loss of a type-of relation during Asset update has been resolved.
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.
An Asset update now correctly considers the tag "deny relation copy context" for Product Line external relations.
External relations of hidden artifacts are now transferred to targets during Asset update.
The incorrect revocation of the integration in foreign Assets during Asset update has been resolved.
The abstraction link is the only matching criterion for the core artifact of the Asset during Asset update from predecessor.

Version 10.20

444

PREEvision 10.5

Asset integration

ID 8682711552635422101 8682711552922532113 8682711552964651913 8682711553135811806 8682711553770092113 8682711553548563043 17938309028792082 8682711553148011029 17938306638582112 8682711554187901030
8682711551960381914

Resolution
The correct error message is displayed if the user does not have the required permissions for some core artifacts during the Asset update.
An Asset cannot be updated if there is an incorrect typeof relation between the Asset to be updated and the updating Asset. In this case the Asset update is interrupted providing a correct error message.
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.
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.
During Asset update unnecessary artifacts have been added to the scope which has caused a long waiting time. This problem has been resolved.
During Asset replace from history unnecessary artifacts have been added to the scope temporarily. This problem has been resolved.
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.
The relations between upstream and downstream Product Lines are now correctly handled during Asset update.
Update indicators for Assets (exclamation mark icons) are correctly displayed on the successor Assets even if the successor Asset is out of scope.
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.
During the calculation of update indicators for core artifacts of Assets, possible abstraction cycles are identified, and no abstraction loops are created anymore.

ID 17938307469611877
17938307710392040

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

Version 10.20

445

Substitution Performance

PREEvision 10.5

ID 17938309246102082
17938311323391868 8682711552486242100
17938311530121029

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

ID 17938309196642082 17938309198152112 17938309330402082 17938293430318157
8682711552015412045 17938311553721877

Resolution
The Identity Configuration of the Compare Configuration is now correctly considered for pairing artifacts during a substitution.
The memory leak problem when substituting artifacts containing many child artifacts is now solved by cleaning up the substitution cache.
A substituted artifact and its Asset are now always deleted after substitution.
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.
For an unsupported substitution of artifacts with structural type-of relations, an error message is displayed, and detailed messages provided in the Information View.
In the Review and Confirm Substitution table, a matching by abstraction link has a higher priority than a matching by name.

ID 17938307765692012 17938307920221877 17938308032222104 8682711552337792100

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

Version 10.20

446

PREEvision 10.5

ID 17938308312202070

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

16.5.13 Variant management

ID 17938311664562102
17938307945391801 17938308086021874 17938308131472011 17938308157062039 17938309328802011 8682711552494743071 8682711553111582039 17938308048301875 17938307437301804 17938307811612011
17938311515802039 17938293833629393

Resolution
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.
The deletion of an active variant is now properly deactivating the variant. Also, the user interface is refreshed.
The active variant decorator is now also refreshed for members of virtual folders.
The meta class name of active variants is not displayed in the status bar anymore.
The progress dialogue for variant activation provides more detailed information.
Due to improved performance, the warning dialogue has been removed for switching active variant while diagrams are opened.
Changing the alias name of Object LHS does not affect the execution of Variant Propagation Rules.
Conditions that have no assignment are not considered in the guard calculation of Variant Propagation Rules anymore.
In the VM Architecture View, the Concept Space combo box is refreshed now when opened.
In the VM Template View, the content in the Alternative column is now sorted in ascending, alpha-numeric order by default.
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.
A tooltip on deactivated variant selection combo box in Set Content View hints to use the Artifact Picker.
Checks for the AUTOSAR compliant variant management are now correctly described as Consistency Rules in the manual.

Version 10.20

447

PREEvision 10.5

ID 17938306914162107
17938311586971884

Resolution
The function Add to Active Set is consistently named in contexts menus as well as toolbar actions and tooltips.
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.

16.5.14 Functional safety
ID 8682711551958091030

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

16.5.15 Change and release management

ID 8682711552487071918 17938307544922111 17938308185512040 17938307953401030 17938307822621030 8682711552262362100 8682711553143622102
8682711552270921030, 8682711552439121030 8682711552761161918

Resolution
In a previous PREEvision version, the Planning Editor was renamed to Project Plan. The screenshots in the user manual have been updated.
The Change history view now properly displays multilined strings.
Artifacts that contain Light Weight Attribute values without an Attribute Definition can be opened in the Change history view without error.
The Change history view now displays the life cycle state which was active when a change was made.
Changes of placeholder attributes are now also displayed in the compact display mode of the Change history view.
The widget for settings dates, which is available in tables and in the Property View, now correctly saves directly typed-in changes.
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.
For the Comment and Chat View, hidden table columns are now handled correctly. Comments are now properly displayed.
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.

Version 10.20

448

PREEvision 10.5

ID 8682711552985021918
8682711552487061918 8682711552944961918 8682711551900442023 17938307536742080 17938307698362101

Resolution
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.
The resources view in the Project Plan correctly calculates the effort of Work Packages if Backlog Items are used.
The actions in the Project Management context menu work if multiple Work Packages or multiple Planable Artifacts are selected.
The German naming for Artifact for Agreement has been improved.
In the Review Table, comments can now be added via copy and paste into the New Comment dialog.
When changing a voting status, the Review Table structure is not changed. Only the visible table properties are updated.

16.5.16 Test engineering and test management

ID 8682711551986743043 8682711553292981859 8682711551903952039 17938311673682023
17938305542692039
17938311470021995
17938305083912110 17938307693752049

Resolution
Manual Test Sequences can be copied and pasted in the Model View.
In the PREEvision demo model, the synchronization metrics for ASIL and ASIL Decomposed have been adjusted.
Test coverage metrics are no longer listed in the context menu of the meta class Customer Feature.
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.
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.
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.
In the Test Specification Editor, when dragging a Test Condition onto a Test Item, the proper link actions are now offered.
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.

Version 10.20

449

PREEvision 10.5

ID 17938308204822049 17938309210342049 17938308758952008 17938311471392049
17938311469981995 8682711552719442102 8682711553175121030 17938309307872102

Resolution
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.
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.
In the Test Specification Editor, the column with the wrong name Test Links has been corrected to Expected Result.
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.
Creating a Test Task after deleting a Test Task Package is now possible without an exception.
The Manual Test Sequence Synthesis metric block now supports the update mode.
During the import of Test Cases from vTESTstudio, the links to Test Items is now created independently from the PREEvision project name.
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

16.5.17 Rules

Consistency checks and online checks

ID 17938309360882112

17938307558342035, 8682711552297551918

17938308324861837

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

Version 10.20

450

PREEvision 10.5

ID 8682711553262742113 8682711553335512102 17938307670791994 17938308101252101
17938292067722709
8682711553145052039

Resolution
All actions for ignoring meta classes for online checks are now hidden and can be enabled with the PREEvision.ini flag DshowConfiguration=true.
Selecting a message in the Consistency Check Results view no longer leads to an error in the Property View.
An error has been fixed that occurred after executing a commit while a diagram is open that includes online check overlays.
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".
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.
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 rules
17938306906001031
17938307782272102 17938308953092070 17938311422942102 17938311422952102 17938311422992102 8682711552764782039

Resolution
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 checkedout. 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.
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.
The performance for a rule execution has been improved in case the same rule is used multiple times.
The online check "Error in MeDeLa attributes" has been deleted.
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.
The online check "Type mismatch by attribute assign. Argument wrong." was adjusted to correctly evaluate the usage of NULL in enumerations.
The rule utility "AdaptivConsistentLinkUtil" is obsolete and has been removed.

Version 10.20

451

PREEvision 10.5

ID 8682711551987551806 17938309409862106
17938309232552102
8682711552939002102 17938311553601810

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

16.5.18 Metrics

Metric framework

ID 17938307198122101

17938309247802070 8682711553052751995

17938306401312039 17938307556532035 8682711553032622106

Resolution
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.
The performance of metric calculations within customized tables has been improved.
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".
The error which prevented the automatic execution of a metric remotely via a batch job has been solved.
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.
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.

Version 10.20

452

PREEvision 10.5

Metric blocks

ID 8682711553189241914 8682711553300771994
8682711552470462102 17938307398282035
8682711552337421875
17938308918662092 17938309291541792

Resolution
The Application Context metric block works correctly if the workspace path contains spaces.
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.
The Open Diagram metric block can now open configuration diagrams that have not yet been loaded.
The Render Diagram metric block can now be executed with the port "renderInBackground"=true and integrated in a loop without producing a deadlock.
The Consistency Rule Group metric block no longer writes results to the Information View if the input port "postResultToInconsistencyView" is set to false.
The AUTOSAR Import metric block checks if the internal loop ports are connected before executing the loop.
Replace roots are correctly considered by the given deletion function of the Replace metric block.

Calculation blocks

ID 17938305543852036 17938308137352036 17938309196662101 8682711551987531806
8682711553050722009 8682711552729682106

Resolution
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.
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.
The performance of the deleteRefObjects metric framework method used in Calculation Blocks has been improved.
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).
The utility class TableSelectionUtil is deprecated and should no longer be used in custom metric code.
A new method getPlainTextWithUpdatedPlaceholders() can be used in metrics. For more information see the javadoc.

Version 10.20

453

PREEvision 10.5

Metric executors
Configuration test framework

ID 17938311513392021

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

ID 17938309379001030
8682711552082621804 8682711552654182102 8682711553169792108 8682711553351132046 8682711551859882111 17938311333542046 8682711553165123054 17938311685162101

Resolution
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.
The Source Model Context is set for enablement blocks of Collaboration Referable Metric Executors.
Icons configured by the object configuration for import and export metric executors are now displayed in the context menu.
Pre Commit Hook Metric Executors can now delete artifacts that are part of the checked-in artifacts.
Pre Delete Hook Metric Executors are now also triggered if a connection is deleted in a diagram.
Collaboration Metric Executors now properly work with Categorizations (submenus in the context menu).
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.
Collaboration Metric Executors can now be hidden from context menus by entering their unique IDs in the Blocklists of the respective Perspective Configurations.
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.

ID 8682711552080332102
8682711552865241786
8682711553283122041

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

Version 10.20

454

PREEvision 10.5

16.5.19 Reports
ID 17938306649991225 8682711553154553071 17938289992398454
17938308047371058 17938308077602101 17938308273482084
17938309032312025 8682711551949012109 8682711552420042113 8682711553034122105
17938306981511783 17938306401312109
17938309210541992 8682711552442803059
8682711553265062034 17938311350701875
17938311615982109

Resolution
When generating a report, the default suggestion for the file name is now the name of the report.
The size of the Generate Report dialog with dynamic parts has been optimized.
With the enhanced support for file attachments, pictures from the model tree can be inserted into formatted texts and be integrated into reports.
No empty pages are generated in PDF reports if the report contains a table of contents larger than one page.
Modifying report footers with multiple tables does not corrupt the footer after editing.
The report generator now correctly inserts the content of placeholders, if the placeholder is directly preceded or followed by text.
If formatted texts starting with lists are included in a report, the reports generator preserves the list order.
Reports with headings are now generated correctly if the heading is directly next to a diagram.
An error message has been improved that is displayed in case of startup problems with the report render engine.
Generated reports no longer contain an unnecessary empty space between rows if a table contains images which are anchored at a character.
Large diagrams scaled to fill the whole page are now completely visible in generated reports.
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.
Diagrams in reports are now printed without selection highlight.
The error message "Diagrams on separate fitting pages are contained in not supported segments of the report" has been corrected.
Diagrams are now shown correctly in reports if inserted on a separate page directly after a table
The lock behavior has been optimized for editing reports without active lock. Now, a lock is requested before saving the report.
Application contexts in reports, that display the active variant are now able to handle if there is no active variant set.

Version 10.20

455

PREEvision 10.5

ID 17938311667612084 8682711551701492023
8682711552088162060 17938311670361783

Resolution
Including a Report Module with option Handle Empty Value set to No Value inserts the text contained in the Report Module without error.
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.
Model Contexts are created when a placeholder is copied and pasted from a formatted text into a report.
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.

16.5.20 Collaboration

Lock and commit

ID 17938307499452049

17938307619002035

8682711551924672051

17938307542752101

17938307558902035 17938307569122104
17938307570102106 17938307709952040 17938307850402052 17938307952991038 17938308765391029 17938308926412106

Resolution
A commit error was fixed that could occur after deleting all children of a checked-in artifact in one operation.
Searching for deleted artifacts in a commit also works when many artifacts (> 25) have been deleted.
The error which occurred during a commit operation including localized attributes, has been resolved.
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.
An error that occurred after a successful commit in association with open diagrams has been solved.
Canceling a commit operation works reliable. If a transaction cannot be canceled, the [Cancel] button is inactive.
The cancel of a commit is now supported at any time as long as no data is written into the database.
The server-side check for missing locks has been improved.
A commit error in the context of the creation of a Timing Path Slot and an open diagram has been resolved.
The commit error which has led to a subsequent forced restart of the PREEvision client has been resolved.
A commit error in the context of a restart of the client and a subsequent commit has been fixed.
The error handling during a commit has been improved.

Version 10.20

456

PREEvision 10.5

ID 17938309056901037
17938311565771877 8682711551703562106 8682711551904332105 8682711552341682105 8682711552398431030 8682711552488831998 8682711553114101992 8682711552770312105 8682711552051061994 17938307542222101 8682711552636762106 8682711552948712101 8682711552540632107
8682711552591551993
17938308195822107 17938307511281031

Resolution
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.
A commit error in the context of invisible reuses has been fixed.
The error handling in the context of lost commit answers from the server has been improved.
A memory problem in the context of a commit error could be fixed.
The Commit dialog can now be closed with <Ctrl>+<Enter> in case that the comment field has the focus.
A commit error in the context of an asset update has been fixed.
A bug in the context of a diagram operation and a commit has been fixed.
A commit error in the context of multiple imports of DBC files has been fixed.
Pressing [Cancel] during commit does not lead to an error message if the server is already writing into the database.
After an import, the locked artifacts outside the scope are correctly listed in the Model View.
Committing after deleting an artifact of a checked-in Ticket is now possible without error.
In the case of an error and a necessary restart of PREEvision, the commit and update buttons are now disabled in the toolbar.
A restore does no longer cause problems during later commits.
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.
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.
An error in the context of an OpenID Connect authentication issue and a subsequent commit has been fixed.
In the case of an error during the Undo all own Locks action, no consecutive errors are produced, and the error is correctly handled.

Version 10.20

457

PREEvision 10.5

Model update

ID 17938311325821914 8682711551942702045 17938307950681806
17938311316432042 17938308898392109
17938308928042068

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

ID 17938309406321993 8682711553060562101 17938311429192105
17938288852362687 17938309307861993
8682711552770262049
8682711553259651914 8682711553162912099 8682711552539532107
8682711551924392049 8682711553661701896

Resolution
The administratively forced deletion of model cache files during update requests is now faster.
The client is not restarted during a model update if this is not necessary.
A progress informs the user if an update cannot be delivered because someone is currently updating the update cache.
Large updates requested by many users does no longer lead to memory problems.
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.
Update errors have been fixed that were caused by updates that contain type changed artifacts which also have been checked in.
The update of local copies of managed files is now working for every update use case.
The localization cache is initialized when loading a server model for the first time.
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.
The behavior has been improved for updating many artifacts to the latest revision.
Managed files are correctly updated when merging a model update during server-side model search.

Version 10.20

458

PREEvision 10.5

Check-out and check-in ID 17938311668152106 17938300811081037
8682711552760301027 17938309028792099 8682711552417741914 17938307685382111 17938308767312111
8682711552914332034 8682711551844802100

Resolution
The context menu texts of the lock and the check-out actions have been unified.
A check-out operation which requires loading missing artifacts to the active scope can now be executed properly.
The check-out of two reuses does not lead to a check-out into the same branch anymore.
A bug has been fixed in the context of disappearing Title Blocks in diagrams during check-out.
A problem in the context of a check-out of Sender Receiver Interfaces and reuses has been fixed.
The undo operation for branch name changes of a Product Line has been corrected.
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.
The check-out of one diagram does not trigger the change of the life cycle of a reused diagram.
The automatic check-out during editing an artifact now works even if the artifact has invisible reuses.

Change history and replace from history

ID 8682711551986711045 8682711551986751045 17938311715842101
17938311670622106
17938311512842101 8682711552982462049

Resolution
A Replace from history action of checked-in artifacts will no longer block other users from locking.
Checked-in reuses are no longer locked after restoring them during a Replace from history action.
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.
When types are deleted during replacing with another version, all artifacts that use that type are now automatically checked out as well.
Opening the Change History on an artifact no longer reports errors in the Information View.
The Change History correctly displays changes for artifacts that only changed a specific relation.

Version 10.20

459

PREEvision 10.5

Life cycles

ID 17938307377652109
17938309273772106

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

Scopes

ID 8682711553135471994
17938309312332106 17938309409852106 8682711553114101998 8682711553662561030 8682711552656332079 17938308311612070 17938308312192070

Resolution
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.
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.
An update error in the context of invisible artifacts which are out of scope has been fixed.
Fixed an issue, so that the highlighting in the Property View works properly for artifacts out of scope.
With the PREEvision.ini setting DInstallationMode=true, partial model support is deactivated.
Artifacts do no longer appear as out of scope when they are newly created under parents that have been moved inside the scope.
Visibility checks for scopes have been optimized.
The performance for filtering out-of-scope artifacts in update use cases has been improved.

Client startup, login, shutdown, and cache

ID 17938307701242098

17938307670771994

8682711551970842106 17938309285451993

17938309381451026

Resolution
Closing the client has been improved, so that an autoupdate is not executed during closing the client, which could have led to errors during the operation.
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.
In case of a failed login when starting the PREEvision client, the error message displayed has been improved.
If client and server are incompatible, no further reconnects of the client are executed to avoid a server overload.
Appropriate error messages are displayed if the client cache cannot be cleared.

Version 10.20

460

PREEvision 10.5

ID 17938309339172036
8682711553062122077

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

Historic model versions ID 17938311667422203
17938309376442101 17938309247792101

Resolution
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.
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.
A compare with historic versions that have changed "type of" artifacts is possible now.

Error handling

ID 17938309359511026
17938309311002049 17938307707912040 17938309312412106 17938307697002107 17938309375802076
17938311623422049

Resolution
When opening the Search dialog while the UQR model is being initialized by another user, only a single error dialog is shown.
The message that is displayed for missing external relations during copy or reuse has been improved.
The error handling during network problems has been improved.
An error in the context of a delete operation of a subtree with contents of an invisible Asset has been fixed.
Creating mappings is now allowed if one of the mapping participants is writeable.
If client and application server are incompatible, no further reconnects of the client are executed to avoid a server overload.
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 memory improvements

ID 17938308245502070

Resolution
The performance of collaboration operations has been improved.

Version 10.20

461

PREEvision 10.5

ID 17938305534681806
17938307402541037, 17938308084021038, 8682711552709492106, 8682711553092412106, 8682711551998181877 17938307682631045 8682711552494802052 17938308936031995, 17938309379732034 17938309054681993 17938309373521993 17938308312542070 17938309373611993 8682711552430311993
17938311331251045 17938309325392101 17938311379901858 17938308054592108 17938307789452108
17938307692052108 17938309307121993
17938309325521993

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

Version 10.20

462

PREEvision 10.5

ID 17938309336512070
17938311350731045

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

Server API

ID 8682711552919282203 8682711553356442203 8682711552516602076
8682711553135662203 8682711551999032203

Resolution
Error codes and messages have been updated in the operating manual.
In the API server logfile, the misleading log output "The contextId is null!..." is suppressed if no error occurred.
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"
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.
For use with the API server, the standalone license server version 2.0.8 or 3.0.0 must be used.

16.5.21 Administration

Authority model

ID 8682711553103513013

17938307614921806

17938307688261029

17938309243351806 17938311633293043 8682711552451332048 8682711552770381992

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

Version 10.20

463

PREEvision 10.5

ID 8682711553215302039
8682711553052091806

Resolution
All rules in the default authority model are compilable and generated.
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 license administration

ID 8682711551851241993

8682711551851261993

8682711552946321030

8682711552716941993

17938311716372203

17938309386342076

8682711553521872101

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

Administration panel

ID 8682711552404062076
17938311723321993

17938309348801993 8682711552680791036

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

Operating

ID 17938311659832106 8682711553019971993 8682711552868691993

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

Version 10.20

464

Add-ins

PREEvision 10.5

ID 8682711551845172054 17938309285461993 17938309325131993 17938307346702105 8682711553356001993 8682711553103513013
8682711553334321995

Resolution
The configuration of ElasticSearch has been changed so that backup and restore of the data is possible.
An exception in the server log file is prevented in context of the monitoring functionality.
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.
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.
The NullPointerException that was reported in the server logfile during model initialization has been fixed.
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.
During start-up of the PREEvision client, the ClassNotFoundException for the class IntegerHexVerifier is no longer reported in the client log file.

ID 17938306701441804
17938307281452101 17938307345131031 17938307348671036
17938307435652023 17938307511381031
17938307708432101

Resolution
Add-in propagation has been extended to cover the path from table through row and cell calculation to metric executor.
Perspectives are contained in Demo Add-ins.
A client freeze has been fixed that occurred when the Lock dialog was displayed during Add-in installation.
Product Add-ins have been updated to use a new type of value for FRAME_LINE_PATTERN in the object configuration.
After deinstalling Add-ins, empty packages are also removed from the Administration.
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.
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.

Version 10.20

465

PREEvision 10.5

ID 17938307747942011 17938307763321028 17938308161532039
17938308176611028 17938308189782039
17938308224501036 17938308279222040 17938308314832040 17938308324721837 17938308763401031 17938308938691995 17938309027981031 17938309281081036 17938309283122011 17938309359001028 17938309360932011 17938311324841806

Resolution
The installation of Add-ins is also possible now if there are still source codes in the target model which are not checked-in.
Metric source codes are no longer compiled during Addin installation.
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.
The performance of calculating locks has been improved when many artifacts are checked-in during an Add-in installation.
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).
When the database storage is full, PREEvision does not retry to apply statements but give the user feedback that the changes were rolled back.
Out of memory exceptions during Add-in installation are now handled with a dialog (default handling).
The [Install Add-Ins] button is hidden when a nonadministrator license is selected.
The Add-in propagation now includes result metrics of rules.
During Add-in installation, the property of files is correct when updating existing files to a newer version.
When installing default Add-ins, no test data is installed anymore.
When installing Add-ins, technical suffixes in branch names are not corrected.
Artifacts that are marked as read-only/write-protected do not cause an abortion of the Add-in installation anymore.
Two Add-ins with the same class files (source code or rules) can now be customized together.
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.
Uninstalling customized Add-ins is possible now. No external relations are copied anymore while customizing an Add-in.
When creating an Add-in delivery file, it is checked whether Add-ins reference incorrectly reused Assets.

Version 10.20

466

PREEvision 10.5

ID 17938311350741995 17938311369191025
17938311481501806 17938311608391036
17938311608441036 8682711551905512039
8682711551929232039 8682711551944152039 8682711551967801865 8682711551969021992 8682711552087942102 8682711552442492039 8682711552473182023 8682711552591633046 8682711552611802041
8682711552656692011 8682711552708981808

Resolution
The Add-in propagation has been extended for multivalued attribute definitions.
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.
Demo content has been removed from the "Diagnostic Design" Add-in.
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.
Obsolete Add-ins are ignored when checking for foreign branch suffixes.
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.
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.
Add-ins which have lost their branch name in the Add-ins model are not uninstalled.
Rules in customized Add-ins can be updated again.
After an Add-in installation, all installed files are contained in the saved E/E model.
Branch and revision are ignored when propagating files using Property- or XML-file links.
Versionless UUIDs are now used to refer to Query Rules and the object configuration of metric executors.
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.
The check-out dialog is shown instead of an exception when a checked-in Perspective Configuration is customized.
If the option Compile Metrics when creating an AddIns delivery file is selected and the creation of an Addins delivery file fails due to uncompilable source codes, an error message is posted, and the error is reported in the Information View.
The Add-in's check-out status has been included in the Add-in's installation information reported in the Information View.
The Add-ins installation wizard displays an error when a check-in is terminated due to missing trace assignments.

Version 10.20

467

PREEvision 10.5

ID 8682711552708991808 8682711552721302102 8682711552942042039 8682711552942141225 8682711552945131999
8682711553036271808 8682711553138523013 8682711553142392078
8682711553171832041 8682711553175122101 8682711553183212101
8682711553215373046 8682711553350992039 8682711553352382039 8682711553559431031 8682711553569842039

Resolution
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.
When adding a Diagram Configuration as core artifact to an Add-in, the constraints of a Legend are propagated.
The error information during Add-ins installation has been improved to identify the artifacts which have caused the problem.
When customizing an artifact affects just one Add-in, the Add-in selection dialog gets skipped.
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.
Customized metrics with wrong relations between Source Code and Calculation Block have been removed from the model.
The Add-ins installation commits with the comment "Addin Installation/Update".
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.
Add-ins which contain other Add-ins as core artifacts, are not deleted during an Add-ins update.
Update of customized Add-ins now detects moved children under root core artifacts during on all hierarchy levels, not just direct children.
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.
While updating a customized Add-in without a propagated Add-in, a propagated Add-in is created onthe-fly if required.
Improved robustness during Add-ins installation: reuses are repaired during the installation.
Improved robustness during Add-ins installation: reuses are repaired during the installation.
The Add-ins dialog has been extended by and additional column that displays the currently installed version and build number of Add-ins.
The initial value of the Update consistency and online check properties flag of the Add-ins installation wizard can now be specified.

Version 10.20

468

PREEvision 10.5

OpenID Connect

ID 8682711553603002101
8682711553632561202 8682711553743272039 8682711553977732068 8682711553977802068 8682711553986332068 8682711554045542023
8682711554395792068 8682711553437962036

Resolution
The performance of merging models has been improved. This also improves the performance of the Add-in installation and other imports like ReqIF.
Installing customized Add-ins no longer causes a reuse repair error.
The Build Number of an Add-in is only incremented if the Add-in is allowed to be checked out in model.
Default markers for attributes are considered during Addin installation.
Fixed handling of reuses when an Add-in installation changes parts of reuses and adds new parts to reuses.
During Add-in installation, model consistency checks for reuses are correctly applied.
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.
A false positive error that could occur during Add-in installation has been fixed.
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.

ID 17938307346581993 17938307346591993 8682711553462021993, 17938307662891993 17938307664061993
17938307953051993
17938309286771993

Resolution
During OpenID Connect authentication, better feedback is provided to the user via the progress dialog.
It is now possible to log into a middleware license server using OpenID Connect authentication when the middleware has disabled model access.
Login to the administration panel via OpenID Connect is supported, now.
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.
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.
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.

Version 10.20

469

PREEvision 10.5

ID 17938309342351026
17938311326001993 8682711552052592020

Resolution
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.
A sporadic problem in the context of a login with OpenID Connect has been resolved.
In the administration panel, simple authentication can also be used for connecting to the remote server to perform remote checks, backups, and migrations.

16.5.22 Installation

PREEvision client

ID 8682711553296521993

8682711552274692017

Resolution
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.
In the PREEvision client, the file jre\lib\security\cacerts is no longer deleted. Instead, a password is set for this keystore.

PREEvision server components

ID 8682711553279432017 8682711552762882054
17938307711702203 8682711552942592017 8682711553279622017
8682711553279652017 8682711553338922017

Resolution
In the deploy.properties, most properties have been renamed according to a unified naming scheme.
The Monitor.DataStorage. Transport.Port of the monitoring server has been changed to a single port 9300, instead of a range 9300-9400.
The default port of the monitoring data storage can be configured in the deploy.properties.
Apache Tomcat settings are adapted and configurable by the deploy.properties.
The MessageBrokerJdkPath property was removed from the deploy.properties. Instead, the tomcat.jdkhome property is used also for the messaging application.
The unused properties webapp.disp.name and webapp.descr were removed from the deploy.properties.
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.

Version 10.20

470

PREEvision 10.5

ID 8682711553518902203 8682711553147990000

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.
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.
To avoid security vulnerabilities, dependencies to Jetty have been removed in all server components.

16.5.23 License
ID 8682711552970552203
17938307762112076 8682711553292351993 17938311333222054
8682711551701471918 17938309310072101
8682711553089582203 8682711552553541998
8682711553140731030

Resolution
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.
Connecting to a standalone license server with enabled OpenID Connect authentication is working properly now.
License server connection data is logged correctly in the log file.
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.
Users with the "Requirements and Test Manager" license can now use explorers.
The Administration actions Create Performance/ Benchmark Report... and Network Performance Test are now license-independent and are available for all users.
With a PREEvision viewer license, access to the General preference pages is possible.
When importing a model, artifacts that are children of artifacts, that are not available because of license restrictions are now ignored
When using a PREEvision viewer license, the highlight for write-protected artifacts in a diagram is disabled.

Version 10.20

471

PREEvision 10.5

ID 17938308314432040

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.
An incorrect behavior of importing invisible artifacts that occurred with restricted licenses has been fixed.

16.5.24 Backup, restore, and migration

ID 17938308273601036 17938311512221036 8682711553591561036 8682711553591551036 8682711552763881993 8682711553175121036 8682711553339781036 17938307545591036 8682711552038941036 17938307953192076 17938311667532076
8682711552472461036

Resolution
For server-side restore in the administration panel, migration-relevant information is cleared to release the memory after the migration.
Missing backup directory configurations in the administration panel do not lead to failed remote migrations anymore.
In the administration panel, determining the model versions for model matching during migration has been improved.
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.
In the administration panel, remote model preparation can be executed without string limitation of 2 GB.
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.
In the administration panel, the Job Details display the correct model preparation information.
A server-to-server migration problem was resolved. The migration is executed with disabled authority management.
An error has been fixed which caused aborting a serverside restore.
A backup is possible now, even if the SVN gateway is not available.
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.
The restore is processed properly without aborting, which was caused by an unusual model constellation.

Version 10.20

472

Data migration

PREEvision 10.5

ID 8682711554032111036 8682711553092622020 8682711553122222020

Resolution
Incremental migration no longer causes a NullPointerException.
The performance of the restore has been improved for restoring large commits.
The performance of the restore has been improved for certain model constellations.

ID 8682711553575302070 8682711552631431806 8682711553613911993 8682711553554171036
8682711553632432020
8682711553145911024 8682711553500611036 8682711553509502041

Resolution
The error which has caused a missing commit history after a remote backup or remote restore has been fixed.
Fixed migration of Perspective Configuration Models containing Tables.
An error in the context of restoring formatting texts of an anonymized model has been fixed.
An error in the migration has been fixed where incorrect UUIDs were calculated for SOME/ IP SD Server Event Group Timing Configurations.
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.
During migration, the relation between Process Design and Process is set.
Socket Connection Bundles contained in generic packages are correctly migrated.
Blocklist entries of Perspective Configurations of a PREEvision 10.0 installation work after migration to PREEvision 10.5.

Version 10.20

473

PREEvision 10.5

16.6 Known issues

Known issues in PREEvision 10.5

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

ID 8682711685314021995
8682711554031661036 8682711554406702203 8682711554380412077 17938307791212069

Known issue
When formatted texts are edited, all Model Contexts below the associated artifact are automatically refactored to Placeholder Contexts. Additionally, orphaned Placeholder Contexts, which are not used as placeholder in the formatted text, are deleted. This may lead to data loss if the Model Contexts are not used as placeholders in formatted texts, but, for example, to define relations between model artifacts. These Model Contexts are deleted when any formatted text of the artifact is edited. Workaround: For artifacts that contain Model Contexts that are not used as placeholders in formatted texts:
1. Before editing any formatted text of the artifact, move the Model Contexts to another artifact.
2. Edit the formatted text.
3. Move the Model Context back to the original artifact. The issue has been resolved in PREEvision 10.8. Therefore, it is highly recommended to perform a minor release update to PREEvision 10.8.
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.
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.
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."
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

Version 10.20

474

PREEvision 10.5

ID 8682711552649222003 8682711554383191029 8682711554417372014 8682711554417442013 8682711554173803043 8682711553529641783
8682711554639042025

Known issue
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.
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.
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.
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.
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.
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.
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.
When defining placeholders with Query Context for reports, the defined localized language is not displayed in the report.

Version 10.20

475

Get more Information
Visit our Website for: > News > Products > Demo Software > Support > Training Classes > Addresses
www.vector.com

ST4 PDF Engine (Build 13.0.3.0) SCHEMA ST4

	Vector Informatik: The Future of Software-Defined Vehicles - Hanser Automotive Interview An in-depth interview with Dr. Matthias Traub of Vector Informatik, discussing the automotive industry's transition to software-defined vehicles, development process innovations, and Vector's role as a key technology partner.
	vTESTstudio Concept Manual: Develop and Automate Test Cases Comprehensive concept manual for vTESTstudio version 5.0, detailing its features for developing, implementing, and executing test cases for embedded systems. Learn about test design editors, interaction with CANoe, parameterization, and use cases.
	CANdelaStudio23 Automation Pipeline on Windows: Streamline Diagnostic Development Learn how to automate diagnostic development tasks using CANdelaStudio Server Edition (SE) with GitHub Actions and Jenkins. This guide details setting up pipelines for efficient CDD file updates, UDS/AUTOSAR checks, and ODX/DEXT file exports.
	Vector Informatik auf der IAA Mobility 2025: Software-Defined Vehicles erleben Vector Informatik präsentiert auf der IAA Mobility 2025 die Entwicklung von Software-Defined Vehicles (SDVs) mit der SDV Tour, SIL/HIL-Lösungen und Partnerkooperationen. Erfahren Sie mehr über effizientes Automotive-Software-Engineering.
	CANdb++ Manual - Comprehensive Guide to CAN Database Management Explore the CANdb++ Manual for detailed instructions on creating, managing, and linking CAN databases. Learn about the software's features, data models, and integration within the Vector CAN tool chain.
	CANoe and CANalyzer: Your Guide to Automotive Diagnostics Explore the capabilities of CANoe and CANalyzer for automotive diagnostics. This guide covers essential technical aspects, first steps, and advanced techniques for effective ECU testing and development.
	VN8900 Interface Family Manual - Vector Informatik Comprehensive manual for the Vector VN8900 Interface Family, covering system description, base modules, plug-in modules, accessories, getting started, and driver installation. Learn about real-time processing, stand-alone mode, and network extension capabilities.
	vTESTstudio Konzepthandbuch: Umfassende Anleitung zur Testautomatisierung Das vTESTstudio Konzepthandbuch von Vector Informatik GmbH bietet eine detaillierte Einführung in die Testautomatisierung für eingebettete Systeme. Erfahren Sie mehr über die integrierten Editoren, die Anbindung an CANoe, Parametrierung, Variantenmanagement und die Erstellung von Testreports für Automotive-Anwendungen.

PREEvision ReleaseNotes 10.20.0 EN

PREEvision

Related Documents