Preevision Release Notes Version 6.5 Sp13

Transcript

Release Notes PREEvision Version 6.5 SP13 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 2015, Vector Informatik GmbH. Printed in Germany. All rights reserved. Contents Contents 1 PREEvision 6.5 SP13 7 1.1 Version numbers 8 1.2 Installation and compatibility information 9 1.3 New features 13 1.4 Fixed issues 18 1.5 Known issues 19 2 PREEvision 6.5 SP12 21 2.1 Version numbers 22 2.2 Installation and compatibility information 23 2.3 New features 26 2.4 Fixed issues 2.4.1 Common 2.4.2 Diagrams and tables 2.4.3 AUTOSAR 2.4.4 System software architecture 2.4.5 Hardware architecture 2.4.6 Product line management 2.4.7 Metrics and reports 2.4.8 Collaboration 2.4.9 Administration 2.4.10 Authority 2.4.11 Backup 31 31 31 32 32 32 32 33 33 34 34 34 2.5 Known issues 35 3 PREEvision 6.5 SP11 37 3.1 Version numbers 38 3.2 Installation and compatibility information 39 3.3 Fixed issues 42 3.4 Known issues 43 4 PREEvision 6.5 SP9 45 4.1 Version numbers 46 4.2 Installation and compatibility information 47 4.3 Fixed issues 4.3.1 Common 4.3.2 Diagrams and tables 4.3.3 Product Goals 4.3.4 Logical Function Architecture 4.3.5 AUTOSAR 4.3.6 System Software Architecture 50 50 51 52 52 52 53 © Vector Informatik GmbH Version 6.5 SP13 -3- Contents 4.3.7 4.3.8 4.3.9 4.3.10 4.3.11 4.3.12 Communication Hardware Architecture Product Line Management Reports Collaboration Administration 53 54 54 54 55 55 4.4 Known issues 56 5 PREEvision 6.5 SP8 59 5.1 Version numbers 60 5.2 Installation and compatibility information 61 5.3 Fixed issues 63 5.4 Known issues 64 6 PREEvision 6.5 SP7 65 6.1 Version numbers 66 6.2 Installation and compatibility information 67 6.3 Fixed issues 69 6.4 Known issues 70 7 PREEvision 6.5 SP6 71 7.1 Version numbers 72 7.2 Installation and compatibility information 73 7.3 Fixed issues 75 7.4 Known issues 77 8 PREEvision 6.5 SP5 79 8.1 Version numbers 80 8.2 Installation and compatibility information 81 8.3 Changes 83 8.4 Fixed issues 8.4.1 Common 8.4.2 Diagrams and tables 8.4.3 Product Goals 8.4.4 Logical Function Architecture 8.4.5 AUTOSAR 8.4.6 System Software Architecture 8.4.7 Hardware Architecture 8.4.8 Geometry 8.4.9 Communication 8.4.10 Product Line Management 8.4.11 Metrics and reports 8.4.12 Collaboration 8.4.13 Administration, authority, license, installation and migration 84 84 84 85 85 86 87 88 88 89 90 91 91 92 8.5 Known issues 93 -4- Version 6.5 SP13 © Vector Informatik GmbH Contents 9 PREEvision 6.5 SP4 95 9.1 Version numbers 96 9.2 Installation and compatibility information 97 9.3 Fixed issues 99 9.4 Known issues 10 PREEvision 6.5 SP3 10.1 Version numbers 104 10.2 Installation and compatibility information 105 10.3 New features 107 10.4 Fixed issues 10.4.1 Common 10.4.2 Tables 10.4.3 Logical Function Architecture 10.4.4 System Software Architecture 10.4.5 Hardware Architecture 10.4.6 Geometry 10.4.7 Communication 10.4.8 Product Line Management 10.4.9 Rules, metrics and reports 10.4.10 Collaboration 10.4.11 Administration, authority and migration 108 108 109 109 109 109 110 110 111 111 112 113 10.5 Known issues 114 11 PREEvision 6.5 SP2 11.1 Version numbers 118 11.2 Installation and compatibility information 119 11.3 New features 120 11.4 Fixed issues 11.4.1 Common 11.4.2 Diagrams and tables 11.4.3 Product Goals 11.4.4 Logical Function Architecture 11.4.5 System Software Architecture 11.4.6 Hardware Architecture 11.4.7 Geometry 11.4.8 Communication 11.4.9 Product line management 11.4.10 Change management 11.4.11 Metrics and reports 11.4.12 Collaboration 11.4.13 Administration, installation and migration 121 121 122 122 122 123 123 124 124 125 125 126 126 126 11.5 Known issues 128 12 PREEvision 6.5 SP1 12.1 Version numbers © Vector Informatik GmbH 101 103 117 129 130 Version 6.5 SP13 -5- Contents 12.2 Installation and compatibility information 131 12.3 New features 133 12.4 Fixed issues 12.4.1 Common 12.4.2 Diagrams and tables 12.4.3 Product Goals 12.4.4 Logical Function Architecture 12.4.5 System Software Architecture 12.4.6 Hardware Architecture 12.4.7 Geometry 12.4.8 Communication 12.4.9 Product Line Management 12.4.10 Rules, metrics and reports 12.4.11 Collaboration 12.4.12 Administration, authority, license, installation and migration 134 134 135 137 137 138 139 140 141 141 142 143 144 12.5 Known issues 146 13 PREEvision 6.5 149 13.1 Version numbers 150 13.2 Installation and compatibility information 151 13.3 New features 153 13.4 Fixed issues 13.4.1 Common 13.4.2 Diagrams and tables 13.4.3 Product Goals 13.4.4 Logical Function Architecture 13.4.5 System Software Architecture and AUTOSAR 13.4.6 Hardware Architecture 13.4.7 Communication 13.4.8 Product Line Management 13.4.9 Rules, metrics and reports 13.4.10 Collaboration 13.4.11 Administration, license, installation and migration 160 160 161 162 162 163 164 164 165 166 167 168 13.5 Known issues 169 -6- Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP13 1 PREEvision 6.5 SP13 This chapter contains the following information: 1.1 Version numbers 8 1.2 Installation and compatibility information 9 1.3 New features 13 1.4 Fixed issues 18 1.5 Known issues 19 © Vector Informatik GmbH Version 6.5 SP13 -7- PREEvision 6.5 SP13 1.1 Version numbers Version numbers Documentation -8- Application Version number PREEvision client 6.5.13 LibreOffice dictionaries 4.0.3 PREEvision license server 2.0.3 PREEvision database server (2-tier) 2.0.14 PREEvision database server (3-tier) 6.5.13.02 PREEvision application server (3-tier) 6.5.13 Document Version number PREEvision manual 6.5.3 PREEvision operating manual 6.5.5 PREEvision system requirements 6.5.5 Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP13 1.2 Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 6.5, refer to PREEvision 6.5 - Installation and compatibility information. Backup/restore and migration The following migration paths from PREEvision 6.5 to PREEvision 7.0 are supported with the mentioned restrictions: 2-tier to 2-tier migration from PREEvision 6.5 to 7.0 > without history (migration of latest model version only) > with standard performance 2-tier to 3-tier migration from PREEvision 6.5 to 7.0: > without history (migration of latest model version only) > with standard performance > must be carried out in two steps: 1. Technology change from 2-tier to 3-tier must be performed first (on PREEvision 6.5) 2. Afterwards, data migration from PREEvision 6.5 to 7.0 can be performed. 3-tier to 3-tier migration from PREEvision 6.5 to 7.0: > with or without history possible > improved performance of history migration Backup of 2-tier models from PREEvision 6.5 and restore to PREEvision 6.5 is only supported without history (last model version only). For backup/restore including history use a database dump instead. Caution: Please contact the Vector support for getting information about: > the appropriate migration procedure if you are planning to migrate to a new PREEvision version. > the appropriate migration procedure if you are planning to switch the system architecture from 2-tier to 3-tier > which PREEvision version shall be used for valid backup and restore. © Vector Informatik GmbH Version 6.5 SP13 -9- PREEvision 6.5 SP13 3-tier migration from PREEvision 6.5 to PREEvision 6.5 and PREEvision 7.0 For the following 3-tier migration scenarios the specific parameter – DenableDeltaMofForBackup must be set in the PREEvision.ini file for creating a micro delta backup. > > PREEvision 6.5 to PREEvision 6.5 > –DenableDeltaMofForBackup=false or > The parameter need not be set at all PREEvision 6.5 to PREEvision 7.0 > Migration to PREEvision 7.0 –DenableDeltaMofForBackup=true PREEvision 6.5 SP13 should be used for migrating to PREEvision 7.0. Migration to PREEvision 6.5.11 Caution: When using PREEvision 6.5.10 or older releases of PREEvision, Vector identified the risk of unintended delete actions and successive loss of modeling data under certain prerequisites. The risk only exists when working with the PREEvision 2-tier Collaboration Platform and when PREEvision clients with different licenses (e.g. PREEvision Architect and PREEvision Electric Designer) are accessing the same project. The risk also exists when a roles and rights concept is defined in the PREEvision authority model and used. The issue has been corrected in PREEvision 6.5.11 (see issue 1792049819824 in chapter Fixed issues). Vector strongly recommends to all customers to migrate to PREEvision 6.5.11 when the above mentioned circumstances are given and to contact the Vector support if necessary. 2-tier database server With PREEvision 6.5 SP9 a new version of the 2-tier database server script is available version 2.0.14 (version 2.0.14). Existing 2-tier database servers must be updated to version 2.0.14. The following table shows the compatibility between the different PREEvision client and database server versions: Client version Database server Database server Database server version 5.5 version 6.0/6.5 version 6.5 (2.0.10) (2.0.13) (2.0.14) 5.0.x read-only read-only read-only 5.5.x compatible compatible compatible 6.0.x not compatible compatible compatible 6.5.0 - 6.5.8 not compatible compatible compatible from 6.5.9 not compatible not compatible compatible Note: The PREEvision 6.5 Manual and Operating Manual are no longer up-to-date regarding the new 2-tier database server version and compatible client and database server versions. Installation of Visual C++ 2010 during client installation - 10 - During PREEvision client installation, Visual C++ 2010 Redistributable is automatically installed. If Visual C++ 2010 Redistributable is already installed on the computer, a dialog will be displayed asking the user whether to reset or uninstall the existing installation. Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP13 In this case, select the option to reset Visual C++ 2010 Redistributable to its original state. Database access rights The database access right QUERY REWRITE is no longer required for installing and running the PREEvision database server. Restore parameters The following client/server parameters no longer have to be set for restore/migration: > -DenableDummyFileCreation > -DdisableCheckinChecks For a restore, required parameters are automatically set on the server now. Migration to a 3-tier environment For a migration from PREEvision 5.5/6.0 to a PREEvision 6.5 3-tier environment, first, carry out a 2-tier to 2-tier migration to PREEvision 6.5. Afterwards, migrate to the new 3-tier environment using backup and restore. Backup and restore from 2-tier to 2-tier and from 2-tier to 3-tier is only supported for the last model version (without history). For migration, a separate environment is required including a separate database instance. Reference: For detailed information about the migration, refer to the Operating Manual. Update of 3-tier environments In a 3-tier environment, the PREEvision client, the database server and the PREEvision application on the application server are only compatible within exactly the same 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. The following table shows compatible client, server application and database server script versions for specific PREEvision 6.5 versions: Client version Server application version Database server script version 6.5.0 6.5.0 6.5.0.24 6.5.1 6.5.1 6.5.1.3 6.5.2 6.5.2 6.5.1.3 6.5.3 6.5.3 6.5.1.3 6.5.4 6.5.4 6.5.1.3 6.5.5 6.5.5 6.5.5.0 6.5.6 6.5.6 6.5.6.0 6.5.7 6.5.7 6.5.6.0 6.5.8 6.5.8 6.5.6.0 6.5.6.1 (update is optional; installation script for Linux fixed) 6.5.9 6.5.9 6.5.6.0 6.5.6.1 (update is optional; installation script for Linux fixed) © Vector Informatik GmbH Version 6.5 SP13 - 11 - PREEvision 6.5 SP13 Client version Server application version Database server script version 6.5.11 6.5.11 6.5.6.0 6.5.6.1 (update is optional; installation script for Linux fixed) 6.5.12 6.5.12 6.5.12.10 6.5.13 6.5.13 6.5.13.02 For an update of an existing 3-tier environment, all components with a changed version number must be updated, which may include the: > PREEvision client > PREEvision database server script > PREEvision application on the application server Reference: For detailed instructions on how to update a 3-tier environment, refer to the Operating Manual. Execution of To apply to internal IT guidelines, the execution of LibreOffice is now managed by LibreOffice managed PREEvision only. Users are no longer able to separately start LibreOffice without by PREEvision PREEvision running. Additionally, the installation path of the LibreOffice installation integrated in PREEvision is read-only. The described changes only apply to the LibreOffice installation integrated in PREEvision, external LibreOffice installations remain unchanged. Installation of LibreOffice dictionaries LibreOffice is integrated in the PREEvision client for editing formatted texts and report templates. To enable the LibreOffice spell check, a dictionary with the corresponding language is required. The dictionaries (LibreOfficeExtensions_v403.zip) now have to be separately installed into the PREEvision installation directory after the PREEvision client installation: Reference: For detailed information, refer to the Operating Manual. - 12 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP13 1.3 New features Anonymization of database models for 2-tier and 3-tier environments With PREEvision 6.5 SP12 it is possible to anonymize database projects for 2-tier as well as 3-tier environments. By means of this feature sensitive productive data can be anonymized and provided to Vector for a better analysis and reproducibility of model dependent defects. Note: The PREEvision 6.5 Manual and Operating Manual are no longer up-to-date regarding the new feature of anonymizing database models. Anonymization of 2tier database model copies With PREEvision 6.5 SP12 it is possible to create anonymized copies of database projects for 2-tier environments. During the anonymize process, a copy of the selected database model will be created in the database and anonymized. Rich texts and files will not be copied. Since the model copy requires additional tablespace, sufficient tablespace and undo tablespace must be available in the database. During the copy operation the database model is in administrative mode. During this time no access to the model is possible for other users. A database project is anonymized in the Model Management view of the Administration perspective via shortcut menu command Anonymize Model or via the corresponding icon in the toolbar. For the model to be copied and anonymized a new name can be specified or the predefined model name be kept. © Vector Informatik GmbH Version 6.5 SP13 - 13 - PREEvision 6.5 SP13 Depending on the model size the operation may take a longer period of time. During this time no other user has access to the model to be copied and anonymized. Anonymization of 3- With PREEvision 6.5 SP12 it is possible to create anonymized database projects for tier database models 3-tier environments. Caution: Take into account that a 3-tier database project anonymization must never be carried out on a productive system. Instead a test system is strictly recommended. Preconditions for anonymization of database projects > Productive system and test system: > > Oracle database administrator required: > > Besides the productive system an equivalent test system must be available, i.e. identical infrastructure concerning software versions of Oracle database server, SVN and application server. An experienced Oracle database administrator is required on customer side to carry out a database export of the productive system and import into the test system. Files: > A copy of the SVN repository data from productive to test system is not required. > Files will not be considered by the anonymization process. Preliminary steps before anonymization - 14 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP13 To prepare the anonymization process, first create a copy of the productive system … 1. Stop the application server of the test system. This step can be carried out by a PREEvision administrator. 2. Carry out a data dump export of the productive system and import it into the test system. This step should be carried out by an experienced Oracle database administrator. 3. Start the test system. Anonymization of database projects on the test system The anonymization of database projects is carried out on the test system. © Vector Informatik GmbH Version 6.5 SP13 - 15 - PREEvision 6.5 SP13 1. A database project is anonymized in the Model Management view of the Administration perspective via shortcut menu command Anonymize selected Model(s) or via the corresponding icon in the toolbar. Note: Take into account that if the authority model is selected for anonymization it will no longer be possible to log on to other models after anonymization to check the result of the anonymization. 2. Once starting the anonymization, take into account that the anonymization cannot be undone. A corresponding warning is displayed. - 16 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP13 3. Confirm the warning by entering your password and the anonymization will be started. After anonymization the resulting anonymized project(s) can be directly checked on the test system client. Before checking the anonymized project(s), however, the client cache needs to be cleared. Note: As a recommendation you may check the result of the anonymized project(s) in the Model Query Rules perspective, for example. Other configured model perspectives do not function properly after anonymization since the configuration files required for these perspectives are not considered by the anonymization process. 4. As a last step, carry out a data dump export of the test system. This step should be carried out by an experienced Oracle database administrator again. © Vector Informatik GmbH Version 6.5 SP13 - 17 - PREEvision 6.5 SP13 1.4 Fixed issues You will find the important fixed issues in the following table. Please note that some Fixed issues in PREEvision 6.5 SP13 issues are depending on specific configurations, views or models. - 18 - ID Issue 1792234749824 It is now possible to save perspectives in case Common of active Property Editor filter definition mode. 1792273489824 The field "Value" in the Property View does not disappear anymore when changing the Application Data Type of an EE attribute. Common 1792277498454 Model export is working properly again. Common 1792346338454 Saving a model will not lead into a dead lock anymore. Common 1792358908454 Shortcut menu of ECU now shows correct entries in diagram when scope is activated. Common 1792363347721 Save and export are possible again for file projects. Common 1792272609824 Logical Function Architecture ports in Logical function Interface Assignment Diagrams are now architecture placed as expected (required ports on the left side, provided ports on the right side). 1791086707721 DBC import: The standard value for the preconfigured DBC-File-CharSet has changed from "default" to "guess". 1792280617721 Problems with the populate function on Single Hardware wires have been resolved, so that they can be architecture executed on Wires again. 1792220659823 Special characters are now displayed correctly in metric editor. 1792357368454 The error message in case of lock conflicts Collaboration has been adapted to provide more detailed information. In addition, special entries in the Information View are available now for artifacts not locked. 1791679548454 Fixed calculation to release outdated licenses Administration to avoid a false release of a borrowed license. Version 6.5 SP13 Category Communication Metrics © Vector Informatik GmbH PREEvision 6.5 SP13 1.5 Known issues Formatted text field cannot be edited Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams and tables in a report are not correctly printed (1715978292643) Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Software composition types cannot be changed via custom model import (1782615368223) The custom model import does not work when an existing software composition type of the target model shall be changed by the import (e.g. by adding a new software prototype). In this case, the import is aborted with an error message. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. Workaround: Perform a complete model import which creates new UUIDs for the imported artifacts. Manually merge the relevant changes from the imported data into the existing software composition type. Moving a checked-in Logical Function Type creates illegal model state (1774840030000) Moving a checked-in Logical Function Type from the Library to a Logical Function creates an illegal model state. A dependently versioned artifact is created with different revision information than its parent. "Update Reuse Unit" is only possible if latest version is contained in the model (1774844322645) The Update Reuse Unit action is aborted with an error message, if the latest version of the Reuse Unit is not contained in the current model. Backup requires increased hard disk space (1790491522658) Creating a project backup of a multi-user project requires significantly increased hard disk space. Workaround: Check out the Logical Function Type before moving it from the Library. Workaround: Add the latest version of the Reuse Unit to the current model. In addition to the backup directory, the "richtexts" directory within the PREEvision workspace allocates a lot of space. The hard disk space is allocated during backup creation only. After completing backup creation and closing the client, the allocated hard disk space is released. Workaround: Provide sufficient hard disk space. Delete action not available (1791307788454) Sporadically, the Delete action is no longer available in the shortcut menu and cannot be executed via shortcut. Workaround: Restart the PREEvision client. © Vector Informatik GmbH Version 6.5 SP13 - 19 - PREEvision 6.5 SP13 - 20 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP12 2 PREEvision 6.5 SP12 This chapter contains the following information: 2.1 Version numbers 22 2.2 Installation and compatibility information 23 2.3 New features 26 2.4 Fixed issues Common Diagrams and tables AUTOSAR System software architecture Hardware architecture Product line management Metrics and reports Collaboration Administration Authority Backup 31 31 31 32 32 32 32 33 33 34 34 34 2.5 Known issues 35 © Vector Informatik GmbH Version 6.5 SP13 - 21 - PREEvision 6.5 SP12 2.1 Version numbers Version numbers Documentation - 22 - Application Version number PREEvision client 6.5.12 LibreOffice dictionaries 4.0.3 PREEvision license server 2.0.3 PREEvision database server (2-tier) 2.0.14 PREEvision database server (3-tier) 6.5.12.10 PREEvision application server (3-tier) 6.5.12 Document Version number PREEvision manual 6.5.3 PREEvision operating manual 6.5.5 PREEvision system requirements 6.5.5 Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP12 2.2 Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 6.5, refer to PREEvision 6.5 - Installation and compatibility information. 3-tier migration from PREEvision 6.5 to PREEvision 6.5 and PREEvision 7.0 For the following 3-tier migration scenarios the specific parameter – DenableDeltaMofForBackup must be set in the PREEvision.ini file for creating a micro delta backup. > > PREEvision 6.5 to PREEvision 6.5 > –DenableDeltaMofForBackup=false or > The parameter need not be set at all PREEvision 6.5 to PREEvision 7.0 > Migration to PREEvision 7.0 –DenableDeltaMofForBackup=true PREEvision 6.5 SP12 should be used for migrating to PREEvision 7.0. Migration to PREEvision 6.5.11 Caution: When using PREEvision 6.5.10 or older releases of PREEvision, Vector identified the risk of unintended delete actions and successive loss of modeling data under certain prerequisites. The risk only exists when working with the PREEvision 2-tier Collaboration Platform and when PREEvision clients with different licenses (e.g. PREEvision Architect and PREEvision Electric Designer) are accessing the same project. The risk also exists when a roles and rights concept is defined in the PREEvision authority model and used. The issue has been corrected in PREEvision 6.5.11 (see issue 1792049819824 in chapter Fixed issues). Vector strongly recommends to all customers to migrate to PREEvision 6.5.11 when the above mentioned circumstances are given and to contact the Vector support if necessary. 2-tier database server With PREEvision 6.5 SP9 a new version of the 2-tier database server script is available version 2.0.14 (version 2.0.14). Existing 2-tier database servers must be updated to version 2.0.14. The following table shows the compatibility between the different PREEvision client and database server versions: Client version Database server Database server Database server version 5.5 version 6.0/6.5 version 6.5 (2.0.10) (2.0.13) (2.0.14) 5.0.x read-only read-only read-only 5.5.x compatible compatible compatible 6.0.x not compatible compatible compatible 6.5.0 - 6.5.8 not compatible compatible compatible from 6.5.9 not compatible not compatible compatible © Vector Informatik GmbH Version 6.5 SP13 - 23 - PREEvision 6.5 SP12 Note: The PREEvision 6.5 Manual and Operating Manual are no longer up-to-date regarding the new 2-tier database server version and compatible client and database server versions. Installation of Visual C++ 2010 during client installation During PREEvision client installation, Visual C++ 2010 Redistributable is automatically installed. If Visual C++ 2010 Redistributable is already installed on the computer, a dialog will be displayed asking the user whether to reset or uninstall the existing installation. In this case, select the option to reset Visual C++ 2010 Redistributable to its original state. Database access rights The database access right QUERY REWRITE is no longer required for installing and running the PREEvision database server. Restore parameters The following client/server parameters no longer have to be set for restore/migration: > -DenableDummyFileCreation > -DdisableCheckinChecks For a restore, required parameters are automatically set on the server now. Migration to a 3-tier environment For a migration from PREEvision 5.5/6.0 to a PREEvision 6.5 3-tier environment, first, carry out a 2-tier to 2-tier migration to PREEvision 6.5. Afterwards, migrate to the new 3-tier environment using backup and restore. For migration, a separate environment is required including a separate database instance. Reference: For detailed information about the migration, refer to the Operating Manual. Update of 3-tier environments In a 3-tier environment, the PREEvision client, the database server and the PREEvision application on the application server are only compatible within exactly the same 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. The following table shows compatible client, server application and database server script versions for specific PREEvision 6.5 versions: - 24 - Client version Server application version Database server script version 6.5.0 6.5.0 6.5.0.24 6.5.1 6.5.1 6.5.1.3 6.5.2 6.5.2 6.5.1.3 6.5.3 6.5.3 6.5.1.3 6.5.4 6.5.4 6.5.1.3 6.5.5 6.5.5 6.5.5.0 6.5.6 6.5.6 6.5.6.0 6.5.7 6.5.7 6.5.6.0 Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP12 Client version Server application version Database server script version 6.5.8 6.5.8 6.5.6.0 6.5.6.1 (update is optional; installation script for Linux fixed) 6.5.9 6.5.9 6.5.6.0 6.5.6.1 (update is optional; installation script for Linux fixed) 6.5.11 6.5.11 6.5.6.0 6.5.6.1 (update is optional; installation script for Linux fixed) 6.5.12 6.5.12 6.5.12.10 For an update of an existing 3-tier environment, all components with a changed version number must be updated, which may include the: > PREEvision client > PREEvision database server script > PREEvision application on the application server Reference: For detailed instructions on how to update a 3-tier environment, refer to the Operating Manual. Execution of To apply to internal IT guidelines, the execution of LibreOffice is now managed by LibreOffice managed PREEvision only. Users are no longer able to separately start LibreOffice without by PREEvision PREEvision running. Additionally, the installation path of the LibreOffice installation integrated in PREEvision is read-only. The described changes only apply to the LibreOffice installation integrated in PREEvision, external LibreOffice installations remain unchanged. Installation of LibreOffice dictionaries LibreOffice is integrated in the PREEvision client for editing formatted texts and report templates. To enable the LibreOffice spell check, a dictionary with the corresponding language is required. The dictionaries (LibreOfficeExtensions_v403.zip) now have to be separately installed into the PREEvision installation directory after the PREEvision client installation: Reference: For detailed information, refer to the Operating Manual. © Vector Informatik GmbH Version 6.5 SP13 - 25 - PREEvision 6.5 SP12 2.3 New features Anonymization of database models for 2-tier and 3-tier environments With PREEvision 6.5 SP12 it is possible to anonymize database projects for 2-tier as well as 3-tier environments. By means of this feature sensitive productive data can be anonymized and provided to Vector for a better analysis and reproducibility of model dependent defects. Note: The PREEvision 6.5 Manual and Operating Manual are no longer up-to-date regarding the new feature of anonymizing database models. Anonymization of 2tier database model copies With PREEvision 6.5 SP12 it is possible to create anonymized copies of database projects for 2-tier environments. During the anonymize process, a copy of the selected database model will be created in the database and anonymized. Rich texts and files will not be copied. Since the model copy requires additional tablespace, sufficient tablespace and undo tablespace must be available in the database. During the copy operation the database model is in administrative mode. During this time no access to the model is possible for other users. A database project is anonymized in the Model Management view of the Administration perspective via shortcut menu command Anonymize Model or via the corresponding icon in the toolbar. For the model to be copied and anonymized a new name can be specified or the predefined model name be kept. - 26 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP12 Depending on the model size the operation may take a longer period of time. During this time no other user has access to the model to be copied and anonymized. Anonymization of 3- With PREEvision 6.5 SP12 it is possible to create anonymized database projects for tier database models 3-tier environments. Caution: Take into account that a 3-tier database project anonymization must never be carried out on a productive system. Instead a test system is strictly recommended. Preconditions for anonymization of database projects > Productive system and test system: > > Oracle database administrator required: > > Besides the productive system an equivalent test system must be available, i.e. identical infrastructure concerning software versions of Oracle database server, SVN and application server. An experienced Oracle database administrator is required on customer side to carry out a database export of the productive system and import into the test system. Files: > A copy of the SVN repository data from productive to test system is not required. > Files will not be considered by the anonymization process. Preliminary steps before anonymization © Vector Informatik GmbH Version 6.5 SP13 - 27 - PREEvision 6.5 SP12 To prepare the anonymization process, first create a copy of the productive system … 1. Stop the application server of the test system. This step can be carried out by a PREEvision administrator. 2. Carry out a data dump export of the productive system and import it into the test system. This step should be carried out by an experienced Oracle database administrator. 3. Start the test system. Anonymization of database projects on the test system The anonymization of database projects is carried out on the test system. - 28 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP12 1. A database project is anonymized in the Model Management view of the Administration perspective via shortcut menu command Anonymize selected Model(s) or via the corresponding icon in the toolbar. Note: Take into account that if the authority model is selected for anonymization it will no longer be possible to log on to other models after anonymization to check the result of the anonymization. 2. Once starting the anonymization, take into account that the anonymization cannot be undone. A corresponding warning is displayed. © Vector Informatik GmbH Version 6.5 SP13 - 29 - PREEvision 6.5 SP12 3. Confirm the warning by entering your password and the anonymization will be started. After anonymization the resulting anonymized project(s) can be directly checked on the test system client. Before checking the anonymized project(s), however, the client cache needs to be cleared. Note: As a recommendation you may check the result of the anonymized project(s) in the Model Query Rules perspective, for example. Other configured model perspectives do not function properly after anonymization since the configuration files required for these perspectives are not considered by the anonymization process. 4. As a last step, carry out a data dump export of the test system. This step should be carried out by an experienced Oracle database administrator again. - 30 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP12 2.4 Fixed issues You will find the important fixed issues in the following tables. Please note that some Fixed issues in PREEvision 6.5 SP12 issues are depending on specific configurations, views or models. Further information > Common > Diagrams and tables > AUTOSAR > System software architecture > Hardware architecture > Product line management > Metrics and reports > Collaboration > Administration > Authority > Backup 2.4.1 Common ID Issue Category 1791679632689 The correct parent/interface information of Ports is now shown in the Property View of Assembly Software Connectors. Common 1792044282716 A mechanism for a reset of a corrupt Property Common model has been implemented. All property pages are available again. 1792054808454 Structured generic attributes (generic attributes below generic attributes) will now be displayed in the Model View. 1792077928200 After changing a column width of tables in the Common Property View the defined width is persisted for the current client session. Common 2.4.2 Diagrams and tables ID Issue Category 1792078388454 Text boxes inserted from the Documentation diagram palette into a diagram can be moved and resized in all directions again. Diagrams 1792217839824 The sorting of the main columns in table editors now works properly. Tables © Vector Informatik GmbH Version 6.5 SP13 - 31 - PREEvision 6.5 SP12 2.4.3 AUTOSAR ID Issue Category 1792030462644 AUTOSAR import: The update of Software Component Types works even if the .arxml file only contains Composition Types. AUTOSAR 1792031232644 AUTOSAR import: The large memory usage for the Update SW Component Type operation was reduced. The problem was fixed. AUTOSAR 1792079062647 AUTOSAR import: For not supported AUTOSAR AUTOSAR versions during import a corresponding message will be written to the Information View. If possible, the file will be imported anyway. 2.4.4 System software architecture ID Issue Category 1792031968157 When connecting ports in a Software Architecture System Diagram, the assigned Interface Assignments will be kept, now. System software architecture 2.4.5 Hardware architecture ID Issue Category 1792068898454 It is now possible to create single wires between ports in a Wiring System Diagram without a master if there is no active workspace set. A workspace dialog will now be opened which prompts for a suitable package. Hardware architecture 2.4.6 Product line management - 32 - ID Issue Category 1792077487721 For selection of an Architecture variant the performance has been improved (by using the table editor framework). Product line management Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP12 2.4.7 Metrics and reports ID Issue Category 1792212117721 Metrics are compiled after JAR file exchange Metrics and clearing caches to prevent compile errors. 2.4.8 Collaboration ID Issue Category 1792043172676 Shared and exclusive locks of foreign users are propagated for checked-in reuses, now. Collaboration 1792064929823 The missing/lost attribute values have been Collaboration recreated. It is possible again to commit a new check-out together with a new reuse of checked out artifacts. 1792072567721 The autosave mechanism has been Collaboration improved. The autosave first writes into the temp directory, then the content of this temp directory is moved to the final autosave directory. The read and write accesses on the relevant directory during autosave are synchronized. This way it is prevented that two autosaves executed in parallel are working on the same data. Even if an exception occurs during autosave because the user is changing the model, the delta is not copied into the final directory. 1792075329824 Commit with shared lock is possible, now. Collaboration 1792075677721 Lock operation on server corrected. If a lock is requested for an invisible artifact, the lock is granted and not silently ignored. Collaboration 1792075687721 Lock operations work correctly now. Commit is also possible. Collaboration 1792075899824, 1792075909824, 1792075919824 The server caches the authority restrictions now, not only by role but by role and feature IDs. Collaboration 1792211998454 Life cycle and ownership icons are now drawn Collaboration correctly and without errors even if their size is in one dimension too large for the possible 16x16 pixel area. © Vector Informatik GmbH Version 6.5 SP13 - 33 - PREEvision 6.5 SP12 2.4.9 Administration ID Issue Category 1792070339824 In case of short network interrupts, the release of a borrowed license on the middleware license server was stabilized. Administration 1792077012677 Rollback model version now uses the correct Administration methods to reinitialize the middle tier after the rollback. 2.4.10 Authority ID Issue Category 1792079372820 When a user tries to delete an artifact which Authority has type of and reuse unit relations, the read access of relation ends is checked and the delete action denied. 2.4.11 Backup - 34 - ID Issue Category 1792063310451 Missing local reuse sequence numbers are created at backup procedure. Backup Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP12 2.5 Known issues Formatted text field cannot be edited Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams and tables in a report are not correctly printed (1715978292643) Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Software composition types cannot be changed via custom model import (1782615368223) The custom model import does not work when an existing software composition type of the target model shall be changed by the import (e.g. by adding a new software prototype). In this case, the import is aborted with an error message. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. Workaround: Perform a complete model import which creates new UUIDs for the imported artifacts. Manually merge the relevant changes from the imported data into the existing software composition type. Moving a checked-in Logical Function Type creates illegal model state (1774840030000) Moving a checked-in Logical Function Type from the Library to a Logical Function creates an illegal model state. A dependently versioned artifact is created with different revision information than its parent. "Update Reuse Unit" is only possible if latest version is contained in the model (1774844322645) The Update Reuse Unit action is aborted with an error message, if the latest version of the Reuse Unit is not contained in the current model. Backup requires increased hard disk space (1790491522658) Creating a project backup of a multi-user project requires significantly increased hard disk space. Workaround: Check out the Logical Function Type before moving it from the Library. Workaround: Add the latest version of the Reuse Unit to the current model. In addition to the backup directory, the "richtexts" directory within the PREEvision workspace allocates a lot of space. The hard disk space is allocated during backup creation only. After completing backup creation and closing the client, the allocated hard disk space is released. Workaround: Provide sufficient hard disk space. Delete action not available (1791307788454) Sporadically, the Delete action is no longer available in the shortcut menu and cannot be executed via shortcut. Workaround: Restart the PREEvision client. © Vector Informatik GmbH Version 6.5 SP13 - 35 - PREEvision 6.5 SP12 - 36 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP11 3 PREEvision 6.5 SP11 This chapter contains the following information: 3.1 Version numbers 38 3.2 Installation and compatibility information 39 3.3 Fixed issues 42 3.4 Known issues 43 © Vector Informatik GmbH Version 6.5 SP13 - 37 - PREEvision 6.5 SP11 3.1 Version numbers Version numbers Documentation - 38 - Application Version number PREEvision client 6.5.11 LibreOffice dictionaries 4.0.3 PREEvision license server 2.0.0 PREEvision database server (2-tier) 2.0.14 PREEvision database server (3-tier) 6.5.6.0 6.5.6.1 PREEvision application server (3-tier) 6.5.11 Document Version number PREEvision manual 6.5.3 PREEvision operating manual 6.5.5 PREEvision system requirements 6.5.5 Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP11 3.2 Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 6.5, refer to PREEvision 6.5 - Installation and compatibility information. Migration to PREEvision 6.5.11 Caution: When using PREEvision 6.5.10 or older releases of PREEvision, Vector identified the risk of unintended delete actions and successive loss of modeling data under certain prerequisites. The risk only exists when working with the PREEvision 2-tier Collaboration Platform and when PREEvision clients with different licenses (e.g. PREEvision Architect and PREEvision Electric Designer) are accessing the same project. The risk also exists when a roles and rights concept is defined in the PREEvision authority model and used. The issue has been corrected in PREEvision 6.5.11 (see issue 1792049819824 in chapter Fixed issues). Vector strongly recommends to all customers to migrate to PREEvision 6.5.11 when the above mentioned circumstances are given and to contact the Vector support if necessary. Migration to PREEvision 7.0 PREEvision 6.5 SP11 should be used for migrating to PREEvision 7.0. 2-tier database server With PREEvision 6.5 SP9 a new version of the 2-tier database server script is available (version 2.0.14). Existing 2-tier database servers must be updated to version 2.0.14. version 2.0.14 The following table shows the compatibility between the different PREEvision client and database server versions: Client version Database server Database server Database server version 5.5 version 6.0/6.5 version 6.5 (2.0.10) (2.0.13) (2.0.14) 5.0.x read-only read-only read-only 5.5.x compatible compatible compatible 6.0.x not compatible compatible compatible 6.5.0 - 6.5.8 not compatible compatible compatible from 6.5.9 not compatible not compatible compatible Note: The PREEvision 6.5 Manual and Operating Manual are no longer up-to-date regarding the new 2-tier database server version and compatible client and database server versions. Installation of Visual C++ 2010 during client installation During PREEvision client installation, Visual C++ 2010 Redistributable is automatically installed. If Visual C++ 2010 Redistributable is already installed on the computer, a dialog will be displayed asking the user whether to reset or uninstall the existing installation. In this case, select the option to reset Visual C++ 2010 Redistributable to its original state. © Vector Informatik GmbH Version 6.5 SP13 - 39 - PREEvision 6.5 SP11 Database access rights The database access right QUERY REWRITE is no longer required for installing and running the PREEvision database server. Restore parameters The following client/server parameters no longer have to be set for restore/migration: > -DenableDummyFileCreation > -DdisableCheckinChecks For a restore, required parameters are automatically set on the server now. Migration to a 3-tier environment For a migration from PREEvision 5.5/6.0 to a PREEvision 6.5 3-tier environment, first, carry out a 2-tier to 2-tier migration to PREEvision 6.5. Afterwards, migrate to the new 3-tier environment using backup and restore. For migration, a separate environment is required including a separate database instance. Reference: For detailed information about the migration, refer to the Operating Manual. Update of 3-tier environments In a 3-tier environment, the PREEvision client, the database server and the PREEvision application on the application server are only compatible within exactly the same 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. The following table shows compatible client, server application and database server script versions for specific PREEvision 6.5 versions: - 40 - Client version Server application version Database server script version 6.5.0 6.5.0 6.5.0.24 6.5.1 6.5.1 6.5.1.3 6.5.2 6.5.2 6.5.1.3 6.5.3 6.5.3 6.5.1.3 6.5.4 6.5.4 6.5.1.3 6.5.5 6.5.5 6.5.5.0 6.5.6 6.5.6 6.5.6.0 6.5.7 6.5.7 6.5.6.0 6.5.8 6.5.8 6.5.6.0 6.5.6.1 (update is optional; installation script for Linux fixed) 6.5.9 6.5.9 6.5.6.0 6.5.6.1 (update is optional; installation script for Linux fixed) 6.5.11 6.5.11 6.5.6.0 6.5.6.1 (update is optional; installation script for Linux fixed) Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP11 For an update of an existing 3-tier environment, all components with a changed version number must be updated, which may include the: > PREEvision client > PREEvision database server script > PREEvision application on the application server Reference: For detailed instructions on how to update a 3-tier environment, refer to the Operating Manual. Execution of To apply to internal IT guidelines, the execution of LibreOffice is now managed by LibreOffice managed PREEvision only. Users are no longer able to separately start LibreOffice without by PREEvision PREEvision running. Additionally, the installation path of the LibreOffice installation integrated in PREEvision is read-only. The described changes only apply to the LibreOffice installation integrated in PREEvision, external LibreOffice installations remain unchanged. Installation of LibreOffice dictionaries LibreOffice is integrated in the PREEvision client for editing formatted texts and report templates. To enable the LibreOffice spell check, a dictionary with the corresponding language is required. The dictionaries (LibreOfficeExtensions_v403.zip) now have to be separately installed into the PREEvision installation directory after the PREEvision client installation: Reference: For detailed information, refer to the Operating Manual. © Vector Informatik GmbH Version 6.5 SP13 - 41 - PREEvision 6.5 SP11 3.3 Fixed issues Fixed issues in You will find the important fixed issues in the following table. Please note that some PREEvision 6.5 SP11 issues are depending on specific configurations, views or models. - 42 - ID Issue Category 1791675642687 The model import does not abort when new UUIDs are generated. Common 1792029548454 The NullPointerException which occurred when opening the property page Mappings for ECUs does not occur any more. Common 1792034188454 It is now possible to open the LibreOffice Common editor for rich texts of attributes of checked in artifacts. The LibreOffice editor can be opened via . Additionally, a corresponding button to open the editor is also available in the attribute cells of table based editors. 1791679948454 A lock is possible, if another user has locked several sub packages, which are reused in the main package. 1792049819824 A commit after tree lock of a parent of a not Collaboration visible artifact does not delete the artifact any more. 1791682668454 The error that caused the loss of formatting in Reports generated reports under certain circumstances has been fixed. 1791679892687 The actual problem occurred in the backup and restore of 6.5.9. The problem was fixed with the following backup and restore scenario: Backup 6.5.10 2-tier. Restore with 6.5.10 3-tier works properly. The subsequent backup 6.5.10 3-tier also works properly. Version 6.5 SP13 Collaboration Backup © Vector Informatik GmbH PREEvision 6.5 SP11 3.4 Known issues Formatted text field cannot be edited Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams and tables in a report are not correctly printed (1715978292643) Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Artifacts referenced by a placeholder in a report are not automatically selected (34777, 1774840069822) For generated reports, automatic selection of artifacts in the Model View has been disabled due to an error in LibreOffice. When clicking on a placeholder in a report, the selection is not automatically updated. Software composition types cannot be changed via custom model import (1782615368223) The custom model import does not work when an existing software composition type of the target model shall be changed by the import (e.g. by adding a new software prototype). In this case, the import is aborted with an error message. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. Workaround: In the report toolbar, click the Select artifact at placeholder button to select the associated artifact in the Model View. Workaround: Perform a complete model import which creates new UUIDs for the imported artifacts. Manually merge the relevant changes from the imported data into the existing software composition type. Moving a checked-in Logical Function Type creates illegal model state (1774840030000) Moving a checked-in Logical Function Type from the Library to a Logical Function creates an illegal model state. A dependently versioned artifact is created with different revision information than its parent. "Update Reuse Unit" is only possible if latest version is contained in the model (1774844322645) The Update Reuse Unit action is aborted with an error message, if the latest version of the Reuse Unit is not contained in the current model. Backup requires increased hard disk space (1790491522658) Creating a project backup of a multi-user project requires significantly increased hard disk space. Workaround: Check out the Logical Function Type before moving it from the Library. Workaround: Add the latest version of the Reuse Unit to the current model. In addition to the backup directory, the "richtexts" directory within the PREEvision workspace allocates a lot of space. The hard disk space is allocated during backup creation only. After completing backup creation and closing the client, the allocated hard disk space is released. Workaround: Provide sufficient hard disk space. Delete action not available (1791307788454) Sporadically, the Delete action is no longer available in the shortcut menu and cannot be executed via shortcut. Workaround: Restart the PREEvision client. © Vector Informatik GmbH Version 6.5 SP13 - 43 - PREEvision 6.5 SP11 - 44 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP9 4 PREEvision 6.5 SP9 This chapter contains the following information: 4.1 Version numbers 46 4.2 Installation and compatibility information 47 4.3 Fixed issues Common Diagrams and tables Product Goals Logical Function Architecture AUTOSAR System Software Architecture Communication Hardware Architecture Product Line Management Reports Collaboration Administration 50 50 51 52 52 52 53 53 54 54 54 55 55 4.4 Known issues 56 © Vector Informatik GmbH Version 6.5 SP13 - 45 - PREEvision 6.5 SP9 4.1 Version numbers Version numbers Documentation - 46 - Application Version number PREEvision client 6.5.9 LibreOffice dictionaries 4.0.3 PREEvision license server 2.0.0 PREEvision database server (2-tier) 2.0.14 PREEvision database server (3-tier) 6.5.6.0 6.5.6.1 PREEvision application server (3-tier) 6.5.9 Document Version number PREEvision manual 6.5.3 PREEvision operating manual 6.5.5 PREEvision system requirements 6.5.5 Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP9 4.2 Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 6.5, refer to PREEvision 6.5 - Installation and compatibility information. Migration to PREEvision 7.0 PREEvision 6.5 SP9 should be used for migrating to PREEvision 7.0. New 2-tier database With PREEvision 6.5 SP9 a new version of the 2-tier database server script is available server version 2.0.14 (version 2.0.14). Existing 2-tier database servers must be updated to version 2.0.14. The following table shows the compatibility between the different PREEvision client and database server versions: Client version Database server Database server Database server version 5.5 version 6.0/6.5 version 6.5 (2.0.10) (2.0.13) (2.0.14) 5.0.x read-only read-only read-only 5.5.x compatible compatible compatible 6.0.x not compatible compatible compatible 6.5.0 - 6.5.8 not compatible compatible compatible from 6.5.9 not compatible not compatible compatible Note: The PREEvision 6.5 Manual and Operating Manual are no longer up-to-date regarding the new 2-tier database server version and compatible client and database server versions. Installation of Visual C++ 2010 during client installation During PREEvision client installation, Visual C++ 2010 Redistributable is automatically installed. If Visual C++ 2010 Redistributable is already installed on the computer, a dialog will be displayed asking the user whether to reset or uninstall the existing installation. In this case, select the option to reset Visual C++ 2010 Redistributable to its original state. Database access rights The database access right QUERY REWRITE is no longer required for installing and running the PREEvision database server. Restore parameters The following client/server parameters no longer have to be set for restore/migration: > -DenableDummyFileCreation > -DdisableCheckinChecks For a restore, required parameters are automatically set on the server now. Migration to a 3-tier environment For a migration from PREEvision 5.5/6.0 to a PREEvision 6.5 3-tier environment, first, carry out a 2-tier to 2-tier migration to PREEvision 6.5. Afterwards, migrate to the new 3-tier environment using backup and restore. For migration, a separate environment is required including a separate database instance. © Vector Informatik GmbH Version 6.5 SP13 - 47 - PREEvision 6.5 SP9 Reference: For detailed information about the migration, refer to the Operating Manual. Update of 3-tier environments In a 3-tier environment, the PREEvision client, the database server and the PREEvision application on the application server are only compatible within exactly the same 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. The following table shows compatible client, server application and database server script versions for specific PREEvision 6.5 versions: Client version Server application version Database server script version 6.5.0 6.5.0 6.5.0.24 6.5.1 6.5.1 6.5.1.3 6.5.2 6.5.2 6.5.1.3 6.5.3 6.5.3 6.5.1.3 6.5.4 6.5.4 6.5.1.3 6.5.5 6.5.5 6.5.5.0 6.5.6 6.5.6 6.5.6.0 6.5.7 6.5.7 6.5.6.0 6.5.8 6.5.8 6.5.6.0 6.5.6.1 (update is optional; installation script for Linux fixed) 6.5.9 6.5.9 6.5.6.0 6.5.6.1 (update is optional; installation script for Linux fixed) For an update of an existing 3-tier environment, all components with a changed version number must be updated, which may include the: > PREEvision client > PREEvision database server script > PREEvision application on the application server Reference: For detailed instructions on how to update a 3-tier environment, refer to the Operating Manual. Execution of To apply to internal IT guidelines, the execution of LibreOffice is now managed by LibreOffice managed PREEvision only. Users are no longer able to separately start LibreOffice without by PREEvision PREEvision running. Additionally, the installation path of the LibreOffice installation integrated in PREEvision is read-only. The described changes only apply to the LibreOffice installation integrated in PREEvision, external LibreOffice installations remain unchanged. - 48 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP9 Installation of LibreOffice dictionaries LibreOffice is integrated in the PREEvision client for editing formatted texts and report templates. To enable the LibreOffice spell check, a dictionary with the corresponding language is required. The dictionaries (LibreOfficeExtensions_v403.zip) now have to be separately installed into the PREEvision installation directory after the PREEvision client installation: Reference: For detailed information, refer to the Operating Manual. © Vector Informatik GmbH Version 6.5 SP13 - 49 - PREEvision 6.5 SP9 4.3 Fixed issues Fixed issues in PREEvision 6.5 SP9 You will find the important fixed issues in the following table. Please note that some issues are depending on specific configurations, views or models. Further information > Common > Diagrams and tables > Product Goals > Logical Function Architecture > AUTOSAR > System Software Architecture > Communication > Hardware Architecture > Product Line Management > Reports > Collaboration > Administration 4.3.1 Common - 50 - ID Issue Category 1791071262689, 1791147098454 Use case form pages keep their size after setting attribute values. Common 1791094862689, 1791147228454 Use case form pages keep the current Common selection within drop-down lists after the page is refreshed (e.g. after executing an action). 1791314348454 Formatted texts are saved when closing the model even if the placeholder preview is currently active. Common 1791656498454 When switching between navigation and property views in use case perspectives, views are no longer shown twice. Common 1791659072689 Use case form pages keep the current content of combo boxes after a lock. Common 1791659572689 After switching the perspective, navigation views of use case form pages are shown correctly. Common 1791300548454 Changing the description of a hidden label no Common longer resets the object and label configuration. 1791314428454 Deactivating the placeholder preview for formatted texts no longer causes a LibreOffice crash. Version 6.5 SP13 Common © Vector Informatik GmbH PREEvision 6.5 SP9 ID Issue Category 1791315649824 On the Context Artifacts property page of a Common Model Context, the assigned artifacts are displayed in the Context Artifacts table even if they do not have an own Name attribute. 1791525799824 The table view for mappings can be now opened from the Property View without error. Common 1791526992644 Within the Select Workspace dialog, packages are sorted as in the Model View. Common 1791676188454 If the LibreOffice editor is opened for a formatted text of a table cell, changes are stored in the correct artifact now. Common 1791676288454 Within formatted texts it is now possible to set Common the style "Strikethrough" and to save graphics (shortcut menu Save Graphic...). 4.3.2 Diagrams and tables ID Issue Category 1774827932693 Artifacts can be moved to a desired position in 5x5 grid diagrams. Diagrams 1791070699823 Waypoints within sections of diagrams move correctly when the section is being enlarged or moved. Diagrams 1791074888454 Moving sections within diagrams works correctly now without affecting the layout of connections. Diagrams 1791090822644 Labels on conditions are now displayed in all Diagrams diagrams. 1791311848454 Tables are automatically refreshed after creating artifacts. Tables 1791315160452 Sorting a table column no longer creates empty cells in other table columns. Tables 1791655758454 If multiple cells of a table are edited at once none-editable artifacts remain unchanged. Tables 1791671018454, 1791671058454 Copy and paste of (multiple) attribute values from Excel to tables works as expected. Tables 1791676339822 Tables always show the same content regardless of whether they are opened via Open With or created via New. Tables © Vector Informatik GmbH Version 6.5 SP13 - 51 - PREEvision 6.5 SP9 4.3.3 Product Goals ID Issue Category 1791213528454 Requirements are now sorted correctly by their ID if a file package has been created in the same sub folder. Product Goals 1791314308454, 1791678868454 Moving Requirements or Requirement Packages before or after checked-in Requirements or Requirement Packages works correctly now. Product Goals 1791671068454 Requirements are sorted correctly after copy Product Goals and paste in the Model View. 4.3.4 Logical Function Architecture ID Issue Category 1791307872647 On the General property page of Logical Logical Function Domains, it is now possible to navigate to the Architecture associated Logical Domain Type. 1791323978200 Fans are now available in the Logical Architecture System Diagram. Logical Function Architecture ID Issue Category 1791469822644 The AUTOSAR import works with *.eea files AUTOSAR as well. 1791524432644 During AUTOSAR import, merging errors caused by AUTOSARCanTpConnectionChannel are resolved. AUTOSAR 1791653682644 During AUTOSAR import, ECUs are no longer merged if in the AUTOSAR import file a CanTpConnectionChannel references several CommunicationConnectors which belong to different ECUs. AUTOSAR 1791660882644 During AUTOSAR import (3.x and 4.x), only Micro Processors are created without a Process Unit. AUTOSAR 4.3.5 AUTOSAR - 52 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP9 4.3.6 System Software Architecture ID Issue Category 1791070239824 In the SWC System Editor, Data Elements are shown on assembly nets. System Software Architecture 1791526882689 The Integrate into new Composition System Software refactoring of the System Software Architecture Architecture has been corrected. If there is one provided port in the refactored assembly, then the port of the created Composition will be also a provided port. 1791527002689 In the Software Instance Diagram, the Pull System Software up refactoring has been corrected. A Architecture delegation port is changed to a Receiver Port, if there is only one Sender Port and this port is pulled up. 1791527012689 Fixed Assembly SW Connector over System Software Delegation Port / Port Prototype after moving Architecture an Atomic SW Component into a Composition or from a Composition to a higher hierarchy level. 1791659472644 In the Software Instance System Diagram, System Software editing an assembly bus is possible again via Architecture the Edit bus dialog. 4.3.7 Communication ID Issue Category 1791147119822 The numerical format for exporting custom communication attributes to DBC has been corrected. Communication 1791201239822 The signal router corrects wrong sending/ receiving relations on the ECU Interface, if they are wrong or no longer existing. Communication 1791201249822 In the frame synthesis dialog, Communication Communication packages located in Product Line Package hierarchies can be selected. 1791213570452 The commit performance after a DBC import with merge has been improved. Communication 1791319889822 During DBC export, attribute values of Signals, Messages, etc. of type double are written as long expression without exponential short term. Communication 1791526789824 The Create Gateway option of the DBC import works if there are LA Mappings on Signal Transmissions. These mappings are ignored. Communication 1791653712689 The Signal Router Metric Block works again. Communication © Vector Informatik GmbH Version 6.5 SP13 - 53 - PREEvision 6.5 SP9 4.3.8 Hardware Architecture ID Issue Category 1791205062693 In the Electric Circuit Diagram, the function Show path to energy source works and shows the current path from the selected hardware component to the current source. Hardware Architecture 1791213530452 The KBL export no longer produces an empty Hardware file, an error in the transformation has been Architecture fixed. 1791315289824 The "Splice Optimizer" metric has been Hardware corrected and now returns results if the pin hit Architecture count ("MaxHitCount") is set to 1. 1791321262709 When creating a Schematic Connection via the wizard in the network layer, "" can be selected to apply default naming conventions. Hardware Architecture 1791682192689 Committing the model (2-tier) is possible, after refactoring of Single Wire to Conductor under a new Cable artifact. Hardware Architecture 4.3.9 Product Line Management ID Issue Category 32614, 1790547388454 Bus and assembly nets are greyed out if variant highlighting identifies one artifact in the bus system or the assembly net which is not contained in the active variant. Product Line Management 1791151639824 Variant highlighting also works for delegation Product Line ports on logical bus systems. Management 4.3.10 Reports - 54 - ID Issue Category 1791084218454 Static columns are no longer resized when generating reports with dynamic tables. Reports 1791307918454 Generating reports on a historic model version works correctly now. Reports 1791320570451 Style placeholders are correctly applied in reports now. Reports 1791320580451 Paragraph styles are correctly applied to Reports entire description if a conditional placeholder is set. Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP9 ID Issue Category 1791671868454 Performance of report generation has been improved. Reports 1791672482985 Placeholders are checked before rendering a Reports report. Associated log entries in the Information View have been improved to show more precisely which placeholder is wrong. A warning dialog is shown before opening a report if errors have been found. 4.3.11 Collaboration ID Issue Category 1791318082709 The master database synchronization can Collaboration now be executed without error messages and correctly synchronizes the object label configuration. 1791661149824 Creating a reuse of a container and, in the Collaboration same commit, a local reuse of a child of this container, works correctly now. A subsequent check-out of the child no longer causes a commit error. 1791323199824 The mechanism to ensure data consistency for non-versioned artifacts during database restore is applied to revisions and valid reuses as well. Collaboration 1791671859824 The middle-tier server now can handle corrupt legacy data during database restore where reuses are out of synchronization. Collaboration ID Issue Category 34394 Initialization with the default setup (administration only) after a KBL export or import takes 2 minutes. Administration 1782617698454 Initialize Project with File... is possible with Administration a migrated model from PREEvision 5.5. 4.3.12 Administration © Vector Informatik GmbH Version 6.5 SP13 - 55 - PREEvision 6.5 SP9 4.4 Known issues Formatted text field cannot be edited Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams and tables in a report are not correctly printed (1715978292643) Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Artifacts referenced by a placeholder in a report are not automatically selected (34777, 1774840069822) For generated reports, automatic selection of artifacts in the Model View has been disabled due to an error in LibreOffice. When clicking on a placeholder in a report, the selection is not automatically updated. Software composition types cannot be changed via custom model import (1782615368223) The custom model import does not work when an existing software composition type of the target model shall be changed by the import (e.g. by adding a new software prototype). In this case, the import is aborted with an error message. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. Workaround: In the report toolbar, click the Select artifact at placeholder button to select the associated artifact in the Model View. Workaround: Perform a complete model import which creates new UUIDs for the imported artifacts. Manually merge the relevant changes from the imported data into the existing software composition type. Moving a checked-in Logical Function Type creates illegal model state (1774840030000) Moving a checked-in Logical Function Type from the Library to a Logical Function creates an illegal model state. A dependently versioned artifact is created with different revision information than its parent. "Update Reuse Unit" is only possible if latest version is contained in the model (1774844322645) The Update Reuse Unit action is aborted with an error message, if the latest version of the Reuse Unit is not contained in the current model. Backup requires increased hard disk space (1790491522658) Creating a project backup of a multi-user project requires significantly increased hard disk space. Workaround: Check out the Logical Function Type before moving it from the Library. Workaround: Add the latest version of the Reuse Unit to the current model. In addition to the backup directory, the "richtexts" directory within the PREEvision workspace allocates a lot of space. The hard disk space is allocated during backup creation only. After completing backup creation and closing the client, the allocated hard disk space is released. Workaround: Provide sufficient hard disk space. Delete action not available (1791307788454) - 56 - Sporadically, the Delete action is no longer available in the shortcut menu and cannot be executed via shortcut. Workaround: Restart the PREEvision client. Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP9 © Vector Informatik GmbH Version 6.5 SP13 - 57 - PREEvision 6.5 SP9 - 58 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP8 5 PREEvision 6.5 SP8 This chapter contains the following information: 5.1 Version numbers 60 5.2 Installation and compatibility information 61 5.3 Fixed issues 63 5.4 Known issues 64 © Vector Informatik GmbH Version 6.5 SP13 - 59 - PREEvision 6.5 SP8 5.1 Version numbers Version numbers Documentation - 60 - Application Version number PREEvision client 6.5.8 LibreOffice dictionaries 4.0.3 PREEvision license server 2.0.0 PREEvision database server (2-tier) 2.0.13 PREEvision database server (3-tier) 6.5.6.0 6.5.6.1 PREEvision application server (3-tier) 6.5.8 Document Version number PREEvision manual 6.5.3 PREEvision operating manual 6.5.5 PREEvision system requirements 6.5.5 Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP8 5.2 Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 6.5, refer to PREEvision 6.5 - Installation and compatibility information. Migration to PREEvision 7.0 PREEvision 6.5 SP8 should be used for migrating to PREEvision 7.0. Installation of Visual C++ 2010 during client installation During PREEvision client installation, Visual C++ 2010 Redistributable is automatically installed. If Visual C++ 2010 Redistributable is already installed on the computer, a dialog will be displayed asking the user whether to reset or uninstall the existing installation. In this case, select the option to reset Visual C++ 2010 Redistributable to its original state. Database access rights The database access right QUERY REWRITE is no longer required for installing and running the PREEvision database server. Restore parameters The following client/server parameters no longer have to be set for restore/migration: > -DenableDummyFileCreation > -DdisableCheckinChecks For a restore, required parameters are automatically set on the server now. Migration to a 3-tier environment For a migration from PREEvision 5.5/6.0 to a PREEvision 6.5 3-tier environment, first, carry out a 2-tier to 2-tier migration to PREEvision 6.5. Afterwards, migrate to the new 3-tier environment using backup and restore. For migration, a separate environment is required including a separate database instance. Reference: For detailed information about the migration, refer to the Operating Manual. Update of 3-tier environments to 6.5 SP8 In a 3-tier environment, the PREEvision client, the database server and the PREEvision application on the application server are only compatible within exactly the same 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. The following table shows compatible client, server application and database server script versions for specific PREEvision 6.5 versions: Client version Server application version Database server script version 6.5.0 6.5.0 6.5.0.24 6.5.1 6.5.1 6.5.1.3 6.5.2 6.5.2 6.5.1.3 6.5.3 6.5.3 6.5.1.3 6.5.4 6.5.4 6.5.1.3 © Vector Informatik GmbH Version 6.5 SP13 - 61 - PREEvision 6.5 SP8 Client version Server application version Database server script version 6.5.5 6.5.5 6.5.5.0 6.5.6 6.5.6 6.5.6.0 6.5.7 6.5.7 6.5.6.0 6.5.8 6.5.8 6.5.6.0 6.5.6.1 (update is optional; installation script for Linux fixed) For an update of an existing 3-tier environment, all components with a changed version number must be updated, which may include the: > PREEvision client > PREEvision database server script > PREEvision application on the application server Reference: For detailed instructions on how to update a 3-tier environment, refer to the Operating Manual. Execution of To apply to internal IT guidelines, the execution of LibreOffice is now managed by LibreOffice managed PREEvision only. Users are no longer able to separately start LibreOffice without by PREEvision PREEvision running. Additionally, the installation path of the LibreOffice installation integrated in PREEvision is read-only. The described changes only apply to the LibreOffice installation integrated in PREEvision, external LibreOffice installations remain unchanged. Installation of LibreOffice dictionaries LibreOffice is integrated in the PREEvision client for editing formatted texts and report templates. To enable the LibreOffice spell check, a dictionary with the corresponding language is required. The dictionaries (LibreOfficeExtensions_v403.zip) now have to be separately installed into the PREEvision installation directory after the PREEvision client installation: Reference: For detailed information, refer to the Operating Manual. - 62 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP8 5.3 Fixed issues Fixed issues in PREEvision 6.5 SP8 You will find the important fixed issues in the following table. Please note that some issues are depending on specific configurations, views or models. ID Issue 1791293758454 Formatted texts are no longer rewritten when Collaboration creating a reuse, since they already exist on the source artifact. Thus, a commit error has been fixed which occurred when creating reused Requirements via a metric. 1791293802716, 1791312958454, 1791319698454 Refactorings with delete operations as well as Collaboration diagram changes no longer cause multiple root artifacts in the internal delta model. Thus, the subsequent commit error has been fixed. 1791314689824 The Linux installation script for the database Installation has been corrected and references the script create_pv.sql now. 1791315268454 Formatted texts with an invalid file ID are now Administration correctly handled during 3-tier backup creation. 1791301229824 Dependently-versioned artifacts can now be correctly migrated. © Vector Informatik GmbH Version 6.5 SP13 Category Migration - 63 - PREEvision 6.5 SP8 5.4 Known issues Formatted text field cannot be edited Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams and tables in a report are not correctly printed (1715978292643) Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Artifacts referenced by a placeholder in a report are not automatically selected (34777, 1774840069822) For generated reports, automatic selection of artifacts in the Model View has been disabled due to an error in LibreOffice. When clicking on a placeholder in a report, the selection is not automatically updated. Software composition types cannot be changed via custom model import (1782615368223) The custom model import does not work when an existing software composition type of the target model shall be changed by the import (e.g. by adding a new software prototype). In this case, the import is aborted with an error message. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. Workaround: In the report toolbar, click the Select artifact at placeholder button to select the associated artifact in the Model View. Workaround: Perform a complete model import which creates new UUIDs for the imported artifacts. Manually merge the relevant changes from the imported data into the existing software composition type. Moving a checked-in Logical Function Type creates illegal model state (1774840030000) Moving a checked-in Logical Function Type from the Library to a Logical Function creates an illegal model state. A dependently versioned artifact is created with different revision information than its parent. "Update Reuse Unit" is only possible if latest version is contained in the model (1774844322645) The Update Reuse Unit action is aborted with an error message, if the latest version of the Reuse Unit is not contained in the current model. Backup requires increased hard disk space (1790491522658) Creating a project backup of a multi-user project requires significantly increased hard disk space. Workaround: Check out the Logical Function Type before moving it from the Library. Workaround: Add the latest version of the Reuse Unit to the current model. In addition to the backup directory, the "richtexts" directory within the PREEvision workspace allocates a lot of space. The hard disk space is allocated during backup creation only. After completing backup creation and closing the client, the allocated hard disk space is released. Workaround: Provide sufficient hard disk space. - 64 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP7 6 PREEvision 6.5 SP7 This chapter contains the following information: 6.1 Version numbers 66 6.2 Installation and compatibility information 67 6.3 Fixed issues 69 6.4 Known issues 70 © Vector Informatik GmbH Version 6.5 SP13 - 65 - PREEvision 6.5 SP7 6.1 Version numbers Version numbers Documentation - 66 - Application Version number PREEvision client 6.5.7 LibreOffice dictionaries 4.0.3 PREEvision license server 2.0.0 PREEvision database server (2-tier) 2.0.13 PREEvision database server (3-tier) 6.5.6.0 PREEvision application server (3-tier) 6.5.7 Document Version number PREEvision manual 6.5.3 PREEvision operating manual 6.5.5 PREEvision system requirements 6.5.5 Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP7 6.2 Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 6.5, refer to PREEvision 6.5 - Installation and compatibility information. Migration to PREEvision 7.0 PREEvision 6.5 SP7 is required for migrating to PREEvision 7.0. Installation of Visual C++ 2010 during client installation During PREEvision client installation, Visual C++ 2010 Redistributable is automatically installed. If Visual C++ 2010 Redistributable is already installed on the computer, a dialog will be displayed asking the user whether to reset or uninstall the existing installation. In this case, select the option to reset Visual C++ 2010 Redistributable to its original state. Database access rights The database access right QUERY REWRITE is no longer required for installing and running the PREEvision database server. Restore parameters The following client/server parameters no longer have to be set for restore/migration: > -DenableDummyFileCreation > -DdisableCheckinChecks For a restore, required parameters are automatically set on the server now. Migration to a 3-tier environment For a migration from PREEvision 5.5/6.0 to a PREEvision 6.5 3-tier environment, first, carry out a 2-tier to 2-tier migration to PREEvision 6.5. Afterwards, migrate to the new 3-tier environment using backup and restore. For migration, a separate environment is required including a separate database instance. Reference: For detailed information about the migration, refer to the Operating Manual. Update of 3-tier environments to 6.5 SP7 In a 3-tier environment, the PREEvision client, the database server and the PREEvision application on the application server are only compatible within exactly the same 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. The following table shows compatible client, server application and database server script versions for specific PREEvision 6.5 versions: Client version Server application version Database server script version 6.5.0 6.5.0 6.5.0.24 6.5.1 6.5.1 6.5.1.3 6.5.2 6.5.2 6.5.1.3 6.5.3 6.5.3 6.5.1.3 6.5.4 6.5.4 6.5.1.3 © Vector Informatik GmbH Version 6.5 SP13 - 67 - PREEvision 6.5 SP7 Client version Server application version Database server script version 6.5.5 6.5.5 6.5.5.0 6.5.6 6.5.6 6.5.6.0 6.5.7 6.5.7 6.5.6.0 For an update of an existing 3-tier environment, all components with a changed version number must be updated, which may include the: > PREEvision client > PREEvision database server script > PREEvision application on the application server Reference: For detailed instructions on how to update a 3-tier environment, refer to the Operating Manual. Execution of To apply to internal IT guidelines, the execution of LibreOffice is now managed by LibreOffice managed PREEvision only. Users are no longer able to separately start LibreOffice without by PREEvision PREEvision running. Additionally, the installation path of the LibreOffice installation integrated in PREEvision is read-only. The described changes only apply to the LibreOffice installation integrated in PREEvision, external LibreOffice installations remain unchanged. Installation of LibreOffice dictionaries LibreOffice is integrated in the PREEvision client for editing formatted texts and report templates. To enable the LibreOffice spell check, a dictionary with the corresponding language is required. The dictionaries (LibreOfficeExtensions_v403.zip) now have to be separately installed into the PREEvision installation directory after the PREEvision client installation: Reference: For detailed information, refer to the Operating Manual. - 68 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP7 6.3 Fixed issues Fixed issues in PREEvision 6.5 SP7 You will find the important fixed issues in the following table. Please note that some issues are depending on specific configurations, views or models. ID Issue Category Significant issues have been fixed regarding backup/restore and migration. Backup, Restore and Migration 1791210272647 During the AUTOSAR import, Base Type references of Implementation Values are correctly imported. AUTOSAR 1791216738454 Temporarily created artifacts, which have already been deleted before executing the commit, are now handled correctly. Collaboration © Vector Informatik GmbH Version 6.5 SP13 - 69 - PREEvision 6.5 SP7 6.4 Known issues Formatted text field cannot be edited Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams and tables in a report are not correctly printed (1715978292643) Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Artifacts referenced by a placeholder in a report are not automatically selected (34777, 1774840069822) For generated reports, automatic selection of artifacts in the Model View has been disabled due to an error in LibreOffice. When clicking on a placeholder in a report, the selection is not automatically updated. Software composition types cannot be changed via custom model import (1782615368223) The custom model import does not work when an existing software composition type of the target model shall be changed by the import (e.g. by adding a new software prototype). In this case, the import is aborted with an error message. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. Workaround: In the report toolbar, click the Select artifact at placeholder button to select the associated artifact in the Model View. Workaround: Perform a complete model import which creates new UUIDs for the imported artifacts. Manually merge the relevant changes from the imported data into the existing software composition type. Moving a checked-in Logical Function Type creates illegal model state (1774840030000) Moving a checked-in Logical Function Type from the Library to a Logical Function creates an illegal model state. A dependently versioned artifact is created with different revision information than its parent. "Update Reuse Unit" is only possible if latest version is contained in the model (1774844322645) The Update Reuse Unit action is aborted with an error message, if the latest version of the Reuse Unit is not contained in the current model. Backup requires increased hard disk space (1790491522658) Creating a project backup of a multi-user project requires significantly increased hard disk space. Workaround: Check out the Logical Function Type before moving it from the Library. Workaround: Add the latest version of the Reuse Unit to the current model. In addition to the backup directory, the "richtexts" directory within the PREEvision workspace allocates a lot of space. The hard disk space is allocated during backup creation only. After completing backup creation and closing the client, the allocated hard disk space is released. Workaround: Provide sufficient hard disk space. - 70 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP6 7 PREEvision 6.5 SP6 This chapter contains the following information: 7.1 Version numbers 72 7.2 Installation and compatibility information 73 7.3 Fixed issues 75 7.4 Known issues 77 © Vector Informatik GmbH Version 6.5 SP13 - 71 - PREEvision 6.5 SP6 7.1 Version numbers Version numbers Documentation - 72 - Application Version number PREEvision client 6.5.6 LibreOffice dictionaries 4.0.3 PREEvision license server 2.0.0 PREEvision database server (2-tier) 2.0.13 PREEvision database server (3-tier) 6.5.6.0 PREEvision application server (3-tier) 6.5.6 Document Version number PREEvision manual 6.5.3 PREEvision operating manual 6.5.5 PREEvision system requirements 6.5.5 Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP6 7.2 Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 6.5, refer to PREEvision 6.5 - Installation and compatibility information. Installation of Visual C++ 2010 during client installation During PREEvision client installation, Visual C++ 2010 Redistributable is automatically installed. If Visual C++ 2010 Redistributable is already installed on the computer, a dialog will be displayed asking the user whether to reset or uninstall the existing installation. In this case, select the option to reset Visual C++ 2010 Redistributable to its original state. Database access rights The database access right QUERY REWRITE is no longer required for installing and running the PREEvision database server. Restore parameters The following client/server parameters no longer have to be set for restore/migration: > -DenableDummyFileCreation > -DdisableCheckinChecks For a restore, required parameters are automatically set on the server now. Migration to a 3-tier environment For a migration from PREEvision 5.5/6.0 to a PREEvision 6.5 3-tier environment, first, carry out a 2-tier to 2-tier migration to PREEvision 6.5. Afterwards, migrate to the new 3-tier environment using backup and restore. For migration, a separate environment is required including a separate database instance. Reference: For detailed information about the migration, refer to the Operating Manual. Update of 3-tier environments to 6.5 SP6 In a 3-tier environment, the PREEvision client, the database server and the PREEvision application on the application server are only compatible within exactly the same 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. The following table shows compatible client, server application and database server script versions for specific PREEvision 6.5 versions: Client version Server application version Database server script version 6.5.0 6.5.0 6.5.0.24 6.5.1 6.5.1 6.5.1.3 6.5.2 6.5.2 6.5.1.3 6.5.3 6.5.3 6.5.1.3 6.5.4 6.5.4 6.5.1.3 6.5.5 6.5.5 6.5.5.0 6.5.6 6.5.6 6.5.6.0 © Vector Informatik GmbH Version 6.5 SP13 - 73 - PREEvision 6.5 SP6 For an update of an existing 3-tier environment, all components with a changed version number must be updated, which may include the: > PREEvision client > PREEvision database server script > PREEvision application on the application server Reference: For detailed instructions on how to update a 3-tier environment, refer to the Operating Manual. Execution of To apply to internal IT guidelines, the execution of LibreOffice is now managed by LibreOffice managed PREEvision only. Users are no longer able to separately start LibreOffice without by PREEvision PREEvision running. Additionally, the installation path of the LibreOffice installation integrated in PREEvision is read-only. The described changes only apply to the LibreOffice installation integrated in PREEvision, external LibreOffice installations remain unchanged. Installation of LibreOffice dictionaries LibreOffice is integrated in the PREEvision client for editing formatted texts and report templates. To enable the LibreOffice spell check, a dictionary with the corresponding language is required. The dictionaries (LibreOfficeExtensions_v403.zip) now have to be separately installed into the PREEvision installation directory after the PREEvision client installation: Reference: For detailed information, refer to the Operating Manual. - 74 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP6 7.3 Fixed issues Fixed issues in PREEvision 6.5 SP6 You will find the important fixed issues in the following table. Please note that some issues are depending on specific configurations, views or models. ID Issue 1791072938454 Re-import of requirements via the RIF import Product Goals is possible if the following topics are considered: If there are no changes in the attribute definitions and data types, they are allowed to be checked-in. The requirements must be checked-out. In the import wizard the existing (checked-in) attribute definition package and data type package has to be selected. 1791076442791 The AUTOSAR export of complex data types AUTOSAR works again. 1791085740455 During AUTOSAR export, the relation between I-SIGNAL and I-SIGNAL-GROUP is correctly exported. AUTOSAR 1791204942644 During AUTOSAR 3 import, base types are correctly imported. AUTOSAR 1791085276486 Sorting of enumeration entries works correctly for the DBC round trip. Communication 1791085286486 During DBC export, hyphens are exported and no longer replaced with underscores (even if this is not DBC compliant). Communication 1791070099822 Updating Composition Types to a newer Collaboration revision no longer causes an "OutOfBounds" exception. 1790549922687 On the middleware license server, the location of the license-db folder can be configured now. Therefore, the variable PREEvisionLS.dir has to be set, e.g. DPREEvisionLS.dir=D:/AppServer/ tomcat/licenseDB. 1791146132685 A new action has been added within the Administration Model Management view of the Administration perspective to download the server log file from the application server. 1791066608454 During migration of former Hex Types to Application Integer Types The attributes Representation and Extended Representation Format are now correctly set. Migration 1791204109824 Formatted texts are no longer lost during backup and restore. Migration 1791204119824 An SVN error is no longer reported during restore. Migration © Vector Informatik GmbH Version 6.5 SP13 Category Administration - 75 - PREEvision 6.5 SP6 - 76 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP6 7.4 Known issues Formatted text field cannot be edited Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams and tables in a report are not correctly printed (1715978292643) Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Artifacts referenced by a placeholder in a report are not automatically selected (34777, 1774840069822) For generated reports, automatic selection of artifacts in the Model View has been disabled due to an error in LibreOffice. When clicking on a placeholder in a report, the selection is not automatically updated. Software composition types cannot be changed via custom model import (1782615368223) The custom model import does not work when an existing software composition type of the target model shall be changed by the import (e.g. by adding a new software prototype). In this case, the import is aborted with an error message. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. Workaround: In the report toolbar, click the Select artifact at placeholder button to select the associated artifact in the Model View. Workaround: Perform a complete model import which creates new UUIDs for the imported artifacts. Manually merge the relevant changes from the imported data into the existing software composition type. Moving a checked-in Logical Function Type creates illegal model state (1774840030000) Moving a checked-in Logical Function Type from the Library to a Logical Function creates an illegal model state. A dependently versioned artifact is created with different revision information than its parent. "Update Reuse Unit" is only possible if latest version is contained in the model (1774844322645) The Update Reuse Unit action is aborted with an error message, if the latest version of the Reuse Unit is not contained in the current model. Backup requires increased hard disk space (1790491522658) Creating a project backup of a multi-user project requires significantly increased hard disk space. Workaround: Check out the Logical Function Type before moving it from the Library. Workaround: Add the latest version of the Reuse Unit to the current model. In addition to the backup directory, the "richtexts" directory within the PREEvision workspace allocates a lot of space. The hard disk space is allocated during backup creation only. After completing backup creation and closing the client, the allocated hard disk space is released. Workaround: Provide sufficient hard disk space. © Vector Informatik GmbH Version 6.5 SP13 - 77 - PREEvision 6.5 SP6 - 78 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP5 8 PREEvision 6.5 SP5 This chapter contains the following information: 8.1 Version numbers 80 8.2 Installation and compatibility information 81 8.3 Changes 83 8.4 Fixed issues Common Diagrams and tables Product Goals Logical Function Architecture AUTOSAR System Software Architecture Hardware Architecture Geometry Communication Product Line Management Metrics and reports Collaboration Administration, authority, license, installation and migration 84 84 84 85 85 86 87 88 88 89 90 91 91 92 8.5 Known issues 93 © Vector Informatik GmbH Version 6.5 SP13 - 79 - PREEvision 6.5 SP5 8.1 Version numbers Version numbers Documentation - 80 - Application Version number PREEvision client 6.5.5 LibreOffice dictionaries 4.0.3 PREEvision license server 2.0.0 PREEvision database server (2-tier) 2.0.13 PREEvision database server (3-tier) 6.5.5.0 PREEvision application server (3-tier) 6.5.5 Document Version number PREEvision manual 6.5.3 PREEvision operating manual 6.5.5 PREEvision system requirements 6.5.5 Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP5 8.2 Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 6.5, refer to PREEvision 6.5 - Installation and compatibility information. Database access rights The database access right QUERY REWRITE is no longer required for installing and running the PREEvision database server. Restore parameters The following client/server parameters no longer have to be set for restore/migration: > -DenableDummyFileCreation > -DdisableCheckinChecks For a restore, required parameters are automatically set on the server now. Migration to a 3-tier environment For a migration from PREEvision 5.5/6.0 to a PREEvision 6.5 3-tier environment, first, carry out a 2-tier to 2-tier migration to PREEvision 6.5. Afterwards, migrate to the new 3-tier environment using backup and restore. For migration, a separate environment is required including a separate database instance. Reference: For detailed information about the migration, refer to the Operating Manual. Update of 3-tier environments to 6.5 SP5 In a 3-tier environment, the PREEvision client, the database server and the PREEvision application on the application server are only compatible within exactly the same 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. The following table shows compatible client, server application and database server script versions for specific PREEvision 6.5 versions: Client version Server application version Database server script version 6.5.0 6.5.0 6.5.0.24 6.5.1 6.5.1 6.5.1.3 6.5.2 6.5.2 6.5.1.3 6.5.3 6.5.3 6.5.1.3 6.5.4 6.5.4 6.5.1.3 6.5.5 6.5.5 6.5.5.0 For an update of an existing 3-tier environment, all components with a changed version number must be updated, which may include the: > PREEvision client > PREEvision database server script > PREEvision application on the application server © Vector Informatik GmbH Version 6.5 SP13 - 81 - PREEvision 6.5 SP5 Reference: For detailed instructions on how to update a 3-tier environment, refer to the Operating Manual. To apply to internal IT guidelines, the execution of LibreOffice is now managed by Execution of LibreOffice managed PREEvision only. Users are no longer able to separately start LibreOffice without PREEvision running. Additionally, the installation path of the LibreOffice installation by PREEvision integrated in PREEvision is read-only. The described changes only apply to the LibreOffice installation integrated in PREEvision, external LibreOffice installations remain unchanged. Installation of LibreOffice dictionaries LibreOffice is integrated in the PREEvision client for editing formatted texts and report templates. To enable the LibreOffice spell check, a dictionary with the corresponding language is required. The dictionaries (LibreOfficeExtensions_v403.zip) now have to be separately installed into the PREEvision installation directory after the PREEvision client installation: Reference: For detailed information, refer to the Operating Manual. - 82 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP5 8.3 Changes LibreOffice documents incompatible to Microsoft Word In PREEvision an integrated LibreOffice editor is used for editing formatted texts and generating reports. If a document which was created in LibreOffice is opened in Microsoft Word, its presentation may be incorrectly changed or it might not be possible to open the document. This applies to ODT documents as well as to documents stored in DOC format via LibreOffice. To avoid possible incompatibilities, ODT files created with PREEvision shall only be opened or edited with LibreOffice. Additionally, PREEvision no longer supports to create Word documents (DOC). Therefore, the following changes have been implemented: > The menu item Save As... has been removed from the main menu of the LibreOffice editor. > The *.doc format can no longer be selected during report generation. > The file extension "doc" can no longer be set as "saveType" for the Report Executor metric block. Note: The documentation for generating reports as well as for the Report Executor block are currently outdated in the PREEvision manual and do not contain the restrictions mentioned above. © Vector Informatik GmbH Version 6.5 SP13 - 83 - PREEvision 6.5 SP5 8.4 Fixed issues Fixed issues in PREEvision 6.5 SP5 You will find the important fixed issues in the following table. Please note that some issues are depending on specific configurations, views or models. Further information > Common > Diagrams and tables > Product Goals > Logical Function Architecture > AUTOSAR > System Software Architecture > Hardware Architecture > Geometry > Communication > Product Line Management > Metrics and reports > Collaboration > Administration, authority, license, installation and migration > Changes 8.4.1 Common ID Issue Category 1788281649824 OLE objects are now correctly embedded in formatted texts (e.g. description fields). Common 1790439008454 By double clicking on an artifact the default editor is reliably opened now. Common 1790763829822 Generic attributes with special naming conventions are displayed correctly in the tables of the Property View. Common 1790764732709 Disabling query folders in the Model View no Common longer affects non-query folders. 8.4.2 Diagrams and tables - 84 - ID Issue Category 1790438602689 It is now possible to repeatedly change the object configuration of multiple selected artifacts in a diagram. Diagrams 1790438612689 When changing the object configuration of multiple selected artifacts in a diagram, the background image of the first selected block will be correctly applied to all blocks. Diagrams Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP5 ID Issue Category 1790482808454 Sorting model query based table columns works again. Tables 1790488048454 The alignment of table cells is exported to Excel. Tables ID Issue Category 1789454050000 Requirement Attribute Definitions located in Product Goals an Administration package within the Product Line can now be selected as target package for the RIF import. 8.4.3 Product Goals 8.4.4 Logical Function Architecture ID Issue Category 1790439208454 Within Logical Architecture System Diagrams, way points are set correctly when using Show Path on Required Ports. Logical Function Architecture 1790523648454 Within Logical Architecture System Diagrams, ports are now moved correctly after splitting Logical Functions. Logical Function Architecture 1790639330451 Within Logical Architecture Diagrams, delegation ports are no longer deleted when they are placed inside a section area. Logical Function Architecture 1790758369051 Mappings to empty Activity Chains are now displayed in the mapping table of the Property View. Logical Function Architecture 1790778789824 For populating provided/required ports in the Logical Architecture System Diagram, the following option has been introduced in the preferences: Populate only counterpart ports on „show contained ports". If enabled, only counterpart provided/ required ports will be populated. Logical Function Architecture 1790785758454 For connecting ports in the Logical Logical Function Architecture System Diagram, the following Architecture option has been introduced in the preferences: Create new Assembly Net when connecting ports instead of extending existing Assembly Net. If enabled, new assemblies are created when connecting ports. If disabled, existing assemblies will be extended. © Vector Informatik GmbH Version 6.5 SP13 - 85 - PREEvision 6.5 SP5 ID Issue Category 1790865088454 Moving a port of a logical function instance in Logical Function the Model View no longer updates all Architecture containing diagrams and no longer changes the relation to the assembly. 1790903328454 Within the Logical Architecture System Diagram, the correct number of assembly connectors is created now when connecting logical functions within Building Blocks. Logical Function Architecture ID Issue Category 1790755462791 AUTOSAR export: Communication elements AUTOSAR are also exported if they are in a global communication library. 1790757860000 AUTOSAR export and import: Timing information (e.g. time period of cyclic timing) are consistently handled. 1790765108354 AUTOSAR import: Implementation Data AUTOSAR Types without a category are displayed in the Information View. 1790788432791 During the AUTOSAR export of a System Description or an ECU Extract, Mode Declaration Groups are now correctly exported. 1790788992791 During the AUTOSAR export of an ECU AUTOSAR Extract hierarchical delegation port structures are now correctly handled. 1790789022791 AUTOSAR export: FIBEX-ELEMENTs are created for ISignalGroups. 1790851352791 The attribute SYMBOL of RUNNABLEAUTOSAR ENTITY is correctly imported and exported in AUTOSAR format. 1790851722791 During the AUTOSAR export of a System AUTOSAR Extract hierarchical delegation port structures are now correctly handled. 1790853980455 AUTOSAR export: Complex data types are correctly exported now. AUTOSAR 1790856752791 During the AUTOSAR export of a System Description, access from a RunnableEntity to an InterRunnableVariable is now realized with the correct role. AUTOSAR 1790909470455 AUTOSAR export: IPDUs are correctly converted. AUTOSAR 8.4.5 AUTOSAR - 86 - Version 6.5 SP13 AUTOSAR AUTOSAR AUTOSAR © Vector Informatik GmbH PREEvision 6.5 SP5 ID Issue Category 1790908250455 AUTOSAR export: All Bus Systems are exported. AUTOSAR 1790914420455 AUTOSAR import: PPort- and RPortMappings are imported. AUTOSAR 1790914759822 Differences between the AUTOSAR export in AUTOSAR PREEvision 6.5 and PREEvision 6.0 have been aligned. 1790964190455 During the AUTOSAR export of an ECU Extract it is now checked whether PDU Transmissions are assigned to a Frame Transmission. 1790964242791 AUTOSAR export: Duplicate references of I- AUTOSAR PDU-Ports are no longer created. 1790964242791 AUTOSAR import: Name and value of Application Errors are correctly imported. AUTOSAR 1791014122791 AUTOSAR export: Application Errors are correctly exported. AUTOSAR 1791062592791 AUTOSAR export: Unnecessary references to PDU ports are no longer created. AUTOSAR 1791063242644 AUTOSAR import: Sender and receiver gateway routing entries are now imported with the correct direction. AUTOSAR 1791066428454 AUTOSAR 4.0 export: Type references for inter runnable variables are exported. AUTOSAR AUTOSAR 8.4.6 System Software Architecture ID Issue 1787107139823 The Convert Block refactoring features a System Software name-based port preselection now and ports Architecture can be deleted. 1790754392647 Problems on updating software instances with a selected revision have been fixed. System Software Architecture 1790754412647 A type update is possible after reuse and check-out of a Composition Type. System Software Architecture 1790759279824, 1790759309824 Ports of Composition Types are placed correctly after creating them in the Interface Assignment Diagram. System Software Architecture 1790799582791 Whether the Connect Ports refactoring is available for Compositions can be used can be defined in the preferences under Refactorings | Software Architecture Port Connector | Connect ports of compositions. System Software Architecture © Vector Informatik GmbH Version 6.5 SP13 Category - 87 - PREEvision 6.5 SP5 ID Issue Category 1790865678454 The Create Composition refactoring available in the Software Architecture Diagram no longer causes a reuse error. System Software Architecture 1790908557721 When deleting a software component, the local prototype of this component will be deleted as well. Reuses of this prototype will no longer be deleted. System Software Architecture 1791062602791 The refactoring Integrate into new composition works correctly now. System Software Architecture 8.4.7 Hardware Architecture ID Issue Category 1790248340452 Connectors can again be resized within a grid Hardware of 20x20. Architecture 1790248370452 New connectors created in a diagram (via the Hardware palette or Model View) are placed on the grid Architecture again. 1790789030452, 1790789040452 Components and inline connectors can be Hardware resized to left or top again without moving the Architecture connectors, pins and connections. A combination of top-left, bottom-left or top-right is not supported, which means that the child components will be moved. 1790853439824 Object configuration via types works correctly Hardware now. Architecture 1790853650452 During wiring harness routing and signal routing automatic locking is now used. Hardware Architecture ID Issue Category 1790488312693 Setting the object configuration on Topology Segments is possible in all cases again. Geometry 1790785142693 It is possible again to open Geometry Geometry Diagrams which were created using existing 3D coordinates. An error in the label handling has been fixed. 1790785152693 The refactoring to merge Topology Geometry Segments has been corrected and is working again. 8.4.8 Geometry - 88 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP5 8.4.9 Communication ID Issue Category 1786571212689 The software architecture synthesis for the DBC and LDF import creates a Microprocessor instead a Process Unit now. Communication 1788281912791, 1790763926486 During the DBC import CANClusters are Communication created. Additionally, the cluster merge action has been added to the import wizard. 1790687209823 During the FIBEX import, software sender ports are only created for the actually sent signals in signal-based mode. Communication 1790687229823 During the FIBEX import, ports and software components are associated to the created mappings. Communication 1790687239823 For the FIBEX, DBC and LDF import with Communication merge option, the System Software Architecture can now be additionally selected as target package. 1790755422791 During the DBC export, the attribute GenMsgSendType will always be exported, independent of the Send Mode value. Communication 1790756126486 The calculation of the Initial Value of a Signal creates a constant of the proper type. Communication 1790757772791 During the DBC export, the length of names is no longer restricted/cut to 32 characters. Communication 1790757850000 During the DBC export, float and double values are now correctly exported. Communication 1790759272663 During the DBC import, CAN Signal Transmissions are created if the bus type is unknown or not set. Communication 1790771062709 Deleting Frame Transmission in the CAN Bus Communication Editor works correctly now using the automatic locking mechanism. 1790788462791 For LIN-ECU Interfaces, the error response can now be set on the property page Protocol Parameters. 1790790609822 The execution time for applying signal routing Communication results has been significantly reduced. The progress bar is updated and after each processing of 500 results a message is written to the log file. © Vector Informatik GmbH Version 6.5 SP13 Communication - 89 - PREEvision 6.5 SP5 ID Issue Category 1790768819822 The DBC Import is now able to handle Communication different character sets. Therefore, the option DbcFileCharSet was added to the DBC import/export properties. If a file cannot be read correctly with the default character set the character set can be set by the user. If the character set is not known there is the option to let the import „guess“ the right character set. The following values are possible for DbcFileCharSet: > default: use the default setting of the operating system > guess: try to guess the character set by file analysis > : the name of the character set that is to be used to import/export the file (for possible values see http:// en.wikipedia.org/wiki/ Category:Character_sets). 1790914430455 On the General property page of Signal PDU Communication Groups, the link to the Partial Network Cluster is displayed now. 1790963380455 Property pages have been added to define nested Signal Groups and Signal IPDU Groups. Communication 8.4.10 Product Line Management - 90 - ID Issue 1790781139822, 1790790619822 Performance improvements have been Product Line implemented for updating a Reuse Unit to the Management latest version. 1790785529822 Commit works after updating Reuse Units which results in new artifacts being added to a diagram. Product Line Management 1790802779051 If a Set is activated in the VM Set View and the options for automatically adding created or modified artifacts is enabled, mappings and logical connections are now automatically added to the Set. Product Line Management Version 6.5 SP13 Category © Vector Informatik GmbH PREEvision 6.5 SP5 ID Issue Category 1790905978454 When creating an Alternative by copying an existing Alternative in the Template View, State Values are now copied to the new Alternative. Product Line Management 1791062682716, 1791062779822 After a refresh, table settings of the Template Product Line View will be maintained (columns, filter, sort Management order). 8.4.11 Metrics and reports ID Issue Category 1790785162693 In the Metric Diagram it is possible again to delete ports of a Loop Block. Metrics 1790756239824 Placeholders can be correctly placed between text within the same line. Reports 1790764769051 Exporting Microsoft Word documents is no Reports longer supported by the report generator, see Changes. 1790777909824 Issue regarding rich text handling in report generation has been solved. Reports 1790783098454 A Metric Table Context referenced in a Report can be correctly overwritten with a Model Context / Primary Data Context. Reports ID Issue Category 1787097232693, 1788281639824 Automatic locks are now obtained for creating Collaboration and editing the object configuration. 1790521958454 An error has been fixed that prevented a Collaboration commit or an undo lock in combination with a shared lock. 1790853809824, 1790963418454 Undo all Locks no longer causes an error during the auto save. 8.4.12 Collaboration © Vector Informatik GmbH Version 6.5 SP13 Collaboration - 91 - PREEvision 6.5 SP5 8.4.13 Administration, authority, license, installation and migration - 92 - ID Issue 1790448942647 A commit error has been fixed which occurred Administration after migration of the administration part of the model and initializing with the default setup. 1790779129824 Initializing a database/server project with a file works again. Administration 1790858102693 The operation Administration | Remove locally cached formatted texts is now disabled after closing a project. Administration 1790438568454 It is now possible to initialize a 2-tier authority Authority model with a file-based model which was exported from 3-tier environment. 1751957072693 Stakeholder Packages can now be created in License the Library. Within these packages it is possible to create stakeholders (Clients and Supplier). 1790759398454 The performance has been improved for starting the client with a borrowed license. License 1774831412687 The database script for creating the required tablespaces (preevision_tablespaces.sql) has been adapted and can also be executed under Linux now. Installation 1790762427721 The web application archive for the PREEvision middletier can now be created under Linux/Unix using the BuildWebApp.sh script. Installation 1790800272687 The database access right QUERY Installation REWRITE is no longer required for installing and running the PREEvision database server. 1790489972689 Large Japanese texts are handled correctly by the model cache. Migration 1790767252987 In case that a file was replaced with another version from the history, the wrong file content was restored during backup/restore. The problem has been fixed, all files in the history are correctly restored. Migration 1790795262687 A backup/restore error has been fixed concerning missing files. Migration Version 6.5 SP13 Category © Vector Informatik GmbH PREEvision 6.5 SP5 8.5 Known issues Formatted text field cannot be edited Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams and tables in a report are not correctly printed (1715978292643) Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Artifacts referenced by a placeholder in a report are not automatically selected (34777, 1774840069822) For generated reports, automatic selection of artifacts in the Model View has been disabled due to an error in LibreOffice. When clicking on a placeholder in a report, the selection is not automatically updated. Software composition types cannot be changed via custom model import (1782615368223) The custom model import does not work when an existing software composition type of the target model shall be changed by the import (e.g. by adding a new software prototype). In this case, the import is aborted with an error message. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. Workaround: In the report toolbar, click the Select artifact at placeholder button to select the associated artifact in the Model View. Workaround: Perform a complete model import which creates new UUIDs for the imported artifacts. Manually merge the relevant changes from the imported data into the existing software composition type. Moving a checked-in Logical Function Type creates illegal model state (1774840030000) Moving a checked-in Logical Function Type from the Library to a Logical Function creates an illegal model state. A dependently versioned artifact is created with different revision information than its parent. "Update Reuse Unit" is only possible if latest version is contained in the model (1774844322645) The Update Reuse Unit action is aborted with an error message, if the latest version of the Reuse Unit is not contained in the current model. Backup requires increased hard disk space (1790491522658) Creating a project backup of a multi-user project requires significantly increased hard disk space. Workaround: Check out the Logical Function Type before moving it from the Library. Workaround: Add the latest version of the Reuse Unit to the current model. In addition to the backup directory, the "richtexts" directory within the PREEvision workspace allocates a lot of space. The hard disk space is allocated during backup creation only. After completing backup creation and closing the client, the allocated hard disk space is released. Workaround: Provide sufficient hard disk space. © Vector Informatik GmbH Version 6.5 SP13 - 93 - PREEvision 6.5 SP5 - 94 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP4 9 PREEvision 6.5 SP4 This chapter contains the following information: 9.1 Version numbers 96 9.2 Installation and compatibility information 97 9.3 Fixed issues 99 9.4 Known issues © Vector Informatik GmbH 101 Version 6.5 SP13 - 95 - PREEvision 6.5 SP4 9.1 Version numbers Version numbers Documentation - 96 - Application Version number PREEvision client 6.5.4 LibreOffice dictionaries 4.0.3 PREEvision license server 2.0.0 PREEvision database server (2-tier) 2.0.13 PREEvision database server (3-tier) 6.5.1.3 PREEvision application server (3-tier) 6.5.4 Manual Version number PREEvision manual 6.5.3 PREEvision operating manual 6.5.4 PREEvision system requirements 6.5.4 Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP4 9.2 Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 6.5, refer to PREEvision 6.5 - Installation and compatibility information. Restore parameters The following client/server parameters no longer have to be set for restore/migration: > -DenableDummyFileCreation > -DdisableCheckinChecks For a restore, required parameters are automatically set on the server now. Migration to a 3-tier environment For a migration from PREEvision 5.5/6.0 to a PREEvision 6.5 3-tier environment, first, carry out a 2-tier to 2-tier migration to PREEvision 6.5. Afterwards, migrate to the new 3-tier environment using backup and restore. For migration, a separate environment is required including a separate database instance. Reference: For detailed information about the migration, refer to the Operating Manual. Update of 3-tier environments to 6.5 SP4 In a 3-tier environment, the PREEvision client, the database server and the PREEvision application on the application server are only compatible within exactly the same 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. The following table shows compatible client, server application and database server script versions for specific PREEvision 6.5 versions: Client version Server application version Database server script version 6.5.0 6.5.0 6.5.0.24 6.5.1 6.5.1 6.5.1.3 6.5.2 6.5.2 6.5.1.3 6.5.3 6.5.3 6.5.1.3 6.5.4 6.5.4 6.5.1.3 For an update of an existing 3-tier environment, all components with a changed version number must be updated, which may include the: > PREEvision client > PREEvision database server script > PREEvision application on the application server Reference: For detailed instructions on how to update a 3-tier environment, refer to the Operating Manual. © Vector Informatik GmbH Version 6.5 SP13 - 97 - PREEvision 6.5 SP4 To apply to internal IT guidelines, the execution of LibreOffice is now managed by Execution of LibreOffice managed PREEvision only. Users are no longer able to separately start LibreOffice without PREEvision running. Additionally, the installation path of the LibreOffice installation by PREEvision integrated in PREEvision is read-only. The described changes only apply to the LibreOffice installation integrated in PREEvision, external LibreOffice installations remain unchanged. Installation of LibreOffice dictionaries LibreOffice is integrated in the PREEvision client for editing formatted texts and report templates. To enable the LibreOffice spell check, a dictionary with the corresponding language is required. The dictionaries (LibreOfficeExtensions_v403.zip) now have to be separately installed into the PREEvision installation directory after the PREEvision client installation: Reference: For detailed information, refer to the Operating Manual. - 98 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP4 9.3 Fixed issues Fixed issues in PREEvision 6.5 SP4 You will find the important fixed issues in the following table. Please note that some issues are depending on specific configurations, views or models. ID Issue 1790757452791 Selecting a port instance on the Software System Software Instance Diagram selects the correct port Architecture instance of the projected port prototype in the Model View. 1790488322693 On the Weight property page of a Wire Type, the properties for the weight of insulation per meter can be set again. 34796 On the Receiver and Sender property pages Communication of a Signal, the port prototypes are now displayed. 1788281279824 On the General property page of SW Component instances and types, the Instance ID and SW Component Type ID are now displayed. Communication 1790414028454 During the DBC import with merge option, a Duplicate Exception could occur. The problem has been fixed. Communication 1790491402791 During the AUTOSAR export, the byte order of Signal-IPDU-Mappings is converted to a byte order supported by AUTOSAR. Communication 1790687202791 During the DBC import, the attribute Communication lengthType of imported Base Types is set to "FIXED". 1790687382791 During the LDF import, the attribute Communication lengthType of imported Base Types is set to "FIXED". 1790752800455 The AUTOSAR import creates a Communication LIN Communication container for LinPhysicalChannel. The created structure is equal to the structure created by the LDF import. 1790752960455 During the AUTOSAR import, the DISPLAY- Communication NAME of UNITs is imported. 1790753192791 During the AUTOSAR export, two underscores ("__") are no longer generated within SHORT-NAMEs. Communication 1790753210455 During the AUTOSAR import, Port Prototypes are correctly merged by name (if UUIDs are missing). Communication © Vector Informatik GmbH Version 6.5 SP13 Category Hardware Architecture - 99 - PREEvision 6.5 SP4 - 100 - ID Issue 1790753220455 During the AUTOSAR export, the Communication PackingByteOrder is correctly set, so that the System Description can be opened in the AUTOSAR Network Explorer. 1790759090455 During the AUTOSAR export, the Unit of the Computation Method is exported. 1790765092791 During the AUTSAR import, LIN Connector Communication Types and associated attributes are created. Version 6.5 SP13 Category Communication © Vector Informatik GmbH PREEvision 6.5 SP4 9.4 Known issues Double click does not Sporadically, double clicking on an artifact may not open the defined standard editor. open the standard For example, instead of a table, diagram or report template, the form editor is always editor opened. Workaround: Keep pressed and double click again. Afterwards, double click again. and double click opens the form editor. Afterwards, a double click correctly opens the standard editor. Formatted text field cannot be edited Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams and tables in a report are not correctly printed (1715978292643) Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Artifacts referenced by a placeholder in a report are not automatically selected (34777, 1774840069822) For generated reports, automatic selection of artifacts in the Model View has been disabled due to an error in LibreOffice. When clicking on a placeholder in a report, the selection is not automatically updated. Software composition types cannot be changed via custom model import (1782615368223) The custom model import does not work when an existing software composition type of the target model shall be changed by the import (e.g. by adding a new software prototype). In this case, the import is aborted with an error message. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. Workaround: In the report toolbar, click the Select artifact at placeholder button to select the associated artifact in the Model View. Workaround: Perform a complete model import which creates new UUIDs for the imported artifacts. Manually merge the relevant changes from the imported data into the existing software composition type. Moving a checked-in Logical Function Type creates illegal model state (1774840030000) Moving a checked-in Logical Function Type from the Library to a Logical Function creates an illegal model state. A dependently versioned artifact is created with different revision information than its parent. "Update Reuse Unit" is only possible if latest version is contained in the model (1774844322645) The Update Reuse Unit action is aborted with an error message, if the latest version of the Reuse Unit is not contained in the current model. Backup requires increased hard disk space (1790491522658) Creating a project backup of a multi-user project requires significantly increased hard disk space. Workaround: Check out the Logical Function Type before moving it from the Library. Workaround: Add the latest version of the Reuse Unit to the current model. In addition to the backup directory, the "richtexts" directory within the PREEvision workspace allocates a lot of space. © Vector Informatik GmbH Version 6.5 SP13 - 101 - PREEvision 6.5 SP4 The hard disk space is allocated during backup creation only. After completing backup creation and closing the client, the allocated hard disk space is released. Workaround: Provide sufficient hard disk space. - 102 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP3 10 PREEvision 6.5 SP3 This chapter contains the following information: 10.1 Version numbers 104 10.2 Installation and compatibility information 105 10.3 New features 107 10.4 Fixed issues Common Tables Logical Function Architecture System Software Architecture Hardware Architecture Geometry Communication Product Line Management Rules, metrics and reports Collaboration Administration, authority and migration 108 108 109 109 109 109 110 110 111 111 112 113 10.5 Known issues 114 © Vector Informatik GmbH Version 6.5 SP13 - 103 - PREEvision 6.5 SP3 10.1 Version numbers Version numbers Documentation - 104 - Application Version number PREEvision client 6.5.3 LibreOffice dictionaries 4.0.3 PREEvision license server 2.0.0 PREEvision database server (2-tier) 2.0.13 PREEvision database server (3-tier) 6.5.1.3 PREEvision application server (3-tier) 6.5.3 Manual Version number PREEvision manual 6.5.3 PREEvision operating manual 6.5.3 PREEvision system requirements 6.5.3 Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP3 10.2 Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 6.5, refer to PREEvision 6.5 - Installation and compatibility information. Restore parameters The following client/server parameters no longer have to be set for restore/migration: > -DenableDummyFileCreation > -DdisableCheckinChecks For a restore, required parameters are automatically set on the server now. Migration to a 3-tier environment For a migration from PREEvision 5.5/6.0 to a PREEvision 6.5 3-tier environment, first, carry out a 2-tier to 2-tier migration to PREEvision 6.5. Afterwards, migrate to the new 3-tier environment using backup and restore. For migration, a separate environment is required including a separate database instance. Reference: For detailed information about the migration, refer to the Operating Manual. Update of 3-tier environments to 6.5 SP3 In a 3-tier environment, the PREEvision client, the database server and the PREEvision application on the application server are only compatible within exactly the same 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. The following table shows compatible client, server application and database server script versions for specific PREEvision 6.5 versions: Client version Server application version Database server script version 6.5.0 6.5.0 6.5.0.24 6.5.1 6.5.1 6.5.1.3 6.5.2 6.5.2 6.5.1.3 6.5.3 6.5.3 6.5.1.3 For an update of an existing 3-tier environment, all components with a changed version number must be updated, which may include the: > PREEvision client > PREEvision database server script > PREEvision application on the application server Reference: For detailed instructions on how to update a 3-tier environment, refer to the Operating Manual. © Vector Informatik GmbH Version 6.5 SP13 - 105 - PREEvision 6.5 SP3 To apply to internal IT guidelines, the execution of LibreOffice is now managed by Execution of LibreOffice managed PREEvision only. Users are no longer able to separately start LibreOffice without PREEvision running. Additionally, the installation path of the LibreOffice installation by PREEvision integrated in PREEvision is read-only. The described changes only apply to the LibreOffice installation integrated in PREEvision, external LibreOffice installations remain unchanged. Installation of LibreOffice dictionaries LibreOffice is integrated in the PREEvision client for editing formatted texts and report templates. To enable the LibreOffice spell check, a dictionary with the corresponding language is required. The dictionaries (LibreOfficeExtensions_v403.zip) now have to be separately installed into the PREEvision installation directory after the PREEvision client installation: Reference: For detailed information, refer to the Operating Manual. - 106 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP3 10.3 New features Refactorings of the System Software Architecture The following refactoring of the System Software Architecture has been adapted according to the type-prototype-instance concept which has been introduced with PREEvision 6.5 and is available again: > LIN and AUTOSAR Split Application SW Component Importing and exporting LIN busses via AUTOSAR is fully available now. Related tickets have been fixed. © Vector Informatik GmbH Version 6.5 SP13 - 107 - PREEvision 6.5 SP3 10.4 Fixed issues Fixed issues in PREEvision 6.5 SP3 You will find the important fixed issues in the following table. Please note that some issues are depending on specific configurations, views or models. Further information > Common > Tables > Logical Function Architecture > System Software Architecture > Hardware Architecture > Geometry > Communication > Product Line Management > Rules, metrics and reports > Collaboration > Administration, authority and migration 10.4.1 Common - 108 - ID Issue 1785297729823 Partly exported eea models can be opened in Common the client again. 1787095322693 An eea model containing duplicate XMIIDs can be opened again. 1787101418454 Labels can be set to invisible in the object and Common label configuration again. 1788282559823 The text color displayed in the Model View can be configured by the tag in the object and label configuration again. Common 1789453982790 The attribute External Link can now be edited in the Property View. It is now also possible to paste a URL. Common 1790414182791 Anchors are now supported within the Model Common Queries which enhance the comparison tree. 1790482832439 The Property View no longer freezes but is correctly refreshed according to the current selection. Common 1790549908454 After initializing a model with the default perspectives, all perspectives are correctly loaded and displayed in the start cockpit. Diagrams can be opened from the Model View. Common Version 6.5 SP13 Category Common © Vector Informatik GmbH PREEvision 6.5 SP3 10.4.2 Tables ID Issue Category 1779734490000, 1783784068454 Cell content in table editors is now displayed correctly after hiding and moving columns. Tables 1784087308454 Existing attribute values are now correctly displayed in table editors. Tables 10.4.3 Logical Function Architecture ID Issue Category 1789453558454 Selected packages of the refactoring Split Logical Block are now persisted when clicking [Finish] on the dialog. Logical Function Architecture 1787103458454 Selecting all blocks in a Logical Architecture Diagram by mouse and moving them in the diagram works correctly now. Logical Function Architecture 10.4.4 System Software Architecture ID Issue Category 1782613608157 Existing connections are maintained when moving components across compositions (including different hierarchies). System Software Architecture 10.4.5 Hardware Architecture ID Issue 24947, 1779772962693 The current calculation has been corrected to Hardware enable variant sensitivity. HW Devices not Architecture included in the selected variant are now ignored when calculating dependencies for current calculation. 1787106620452 Pins and Connectors are placed within the grid again during creation and moving. 1790248350452 Rotated labels within Hardware Diagrams are Hardware correctly placed on their selected docked Architecture position again. 1790487822647 Initializing the model with the default setup no Hardware longer causes errors within Electric Circuit Architecture Diagrams. © Vector Informatik GmbH Version 6.5 SP13 Category Hardware Architecture - 109 - PREEvision 6.5 SP3 10.4.6 Geometry ID Issue Category 1778053402693 Errors during opening a Geometry Diagram have been corrected, so that opening Geometry Diagrams is possible in all cases again Geometry ID Issue Category 34784 During the DBC import, initial values of a Communication Signal are now imported as Integer or Double Literals depending on the signal type. 34797 Within the message overview table, the column "Transmitter" has been renamed to "Sender". 34802, 1790438382791 Computation Methods that are referenced Communication from a Signal are exported in AUTOSAR into the NETWORK-REPRESENTATION. 1751961212687 The performance of the AUTOSAR 3.2.2 import has been improved. Communication 1779772502791 A merging import of DBC/LDF without creating the software layer, creates and modifies gateways now. Communication 1785297582791 The property page Sending/Receiving Communication Components has been adapted and displays the correct components now. 1787094052791 During the DBC import, the attribute GenSigStartValue is imported and synchronized with the constant Raw Initial Value in PREEvision. Communication 1787104609823 AUTOSAR 4.1.1 files can now be imported. Communication 1789452550455 Short names for PHYSICAL-CHANNELS have Communication been corrected for the AUTOSAR export (space is replaced with underscore). 1790248320455 Import of AUTOSAR 4 files works correctly now. 1790414182791 During the AUTOSAR 4.x export of a System Communication Description, ECUs without mapped software components (typically gateways) which are connected to a bus system are also exported. 1790438938454 During the AUTOSAR import, Base Types and Computation Methods are assigned to Signals. 10.4.7 Communication - 110 - Version 6.5 SP13 Communication Communication Communication © Vector Informatik GmbH PREEvision 6.5 SP3 ID Issue Category 1790482982791 In the AUTOSAR 4.0.3 export, the Base Communication Type of a Signal is exported as BaseType of I-SIGNAL. In the AUTOSAR 4.1.1 export, the Base Type of a Signal is exported as BaseType of SystemSignal. 1790483160455 During the AUTOSAR import, units of Computation Methods are correctly referenced. 1787095547721, 1790491282791 The Software Architecture can be updated Communication with the AUTOSAR import including a merge even if the AUTOSAR file does not contain UUIDs. The default implementation will use the artifact names for matching. If the AUTOSAR file contains no UUIDs, a warning will be displayed. 1790531332791 During the DBC import, types for initial value constants of signals are now calculated from the type of the GenSigStartValue communication attribute definition. If this definition is missing, the type is calculated from the type of the signal. 1790549942791 During the AUTOSAR export, data filters for Communication PDUs are exported into the TRANSMISSIONMODE-CONDITION. Communication Communication 10.4.8 Product Line Management ID Issue Category 1779772197721 The progress of compiling guards was optimized. Rules are generated during initial propagation only. Product Line Management 10.4.9 Rules, metrics and reports ID Issue Category 1774816190000 The consistency rule "NotMappedInstance" has been corrected in the demo model. Rules 1787103298454 The online checks for editing rules no longer cause a client freeze. Rules 34787 When generating lots of diagrams within a metric, LibreOffice should be reinitialized. Therefore, the "reinitializeLibreOffice" port has been added to the Diagram Render Block and should be set to "true" using a Parameter Block. Metrics © Vector Informatik GmbH Version 6.5 SP13 - 111 - PREEvision 6.5 SP3 ID Issue Category 1787096352689 Chart blocks are now automatically available Metrics in the Metric Diagram palette. The DenableChartInReport initialization flag no longer has to be set. 1787102772693 Displaying context artifacts within Metric Context Blocks has been corrected in terms of variant sensitivity. 34781 When generating a report via the Report Reports Executor Block, the table of contents will now be generated before exporting to PDF or ODT. 1780935832693 For generated reports, automatic selection of Reports artifacts in the Model View has been disabled due to an error in LibreOffice which caused a program crash after starting the report generator. 1790522029822 Report Modules which are included in text Reports with "Heading" format will be integrated in the same line without line feed. Metrics 10.4.10 Collaboration - 112 - ID Issue Category 1782604982693, 1787108658454 Exceptions during the autosave task are no longer presented to the user. Furthermore, these exceptions do no longer block a commit. This allows the user to commit changes even if the autosave was not executed properly. Collaboration 1783864470000 Dereferencing values of an enumeration from Collaboration within a table now also acquires the required shared locks correctly. 1786563849822 The search has been corrected to work properly in the 3-tier environment again. 1787101272647 A wrong lock behavior which locked file Collaboration artifacts in some cases directly after a commit has been corrected. 1788281649823 Reused elements could not be checked-out in some cases. Check-out is now possible again after replacing an artifact with another revision. Collaboration 1789939229823 The check for predecessor revisions has been adapted when loading the Version History to enable handling of histories with missing revisions. History and replacing versions know also works in this case. Collaboration Version 6.5 SP13 Collaboration © Vector Informatik GmbH PREEvision 6.5 SP3 10.4.11 Administration, authority and migration ID Issue Category 1779138112687 Initialize model with default setup has been fixed regarding perspectives. Perspectives can be updated by deleting the perspectives in the model and then using the Initialize current model with default setup operation. Administration 1786572998157 Initializing a project with a model containing artifacts without revision is now possible. Administration 1790438582687 The Log4J file path in the standard server configuration has been changed to catalina.base to work properly with all Tomcat instances. Administration 1785297538454 If "visible" object permissions have been Authority assigned to an artifact, check-out and checkin of its child artifacts is no longer possible. 1779724740000 The arrangement of lines within Logical Architecture Diagrams is now correctly migrated from PREEvision 6.0 to 6.5. 1784096582687 The commit checks executed during a restore Migration with migration have been changed to permit the commit of missing reuses in restore mode. 1787094562791 Initial values are now imported as Integer or Migration Double Literals depending on the signal type. 1787106319824 Extended logging can be enabled/disabled via the initialization parameter Dprofile.debug (true=enabled / false=disabled). Migration 1788281922687 Incomplete sort orders created during a restore are now recognized and handled properly. Migration 1788285648454 Initializing a migrated model with the default setup works correctly now. Migration © Vector Informatik GmbH Version 6.5 SP13 Migration - 113 - PREEvision 6.5 SP3 10.5 Known issues Double click does not Sporadically, double clicking on an artifact may not open the defined standard editor. open the standard For example, instead of a table, diagram or report template, the form editor is always editor opened. Workaround: Keep pressed and double click again. Afterwards, double click again. and double click opens the form editor. Afterwards, a double click correctly opens the standard editor. Formatted text field cannot be edited Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams and tables in a report are not correctly printed (1715978292643) Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Artifacts referenced by a placeholder in a report are not automatically selected (34777, 1774840069822) For generated reports, automatic selection of artifacts in the Model View has been disabled due to an error in LibreOffice. When clicking on a placeholder in a report, the selection is not automatically updated. Software composition types cannot be changed via custom model import (1782615368223) The custom model import does not work when an existing software composition type of the target model shall be changed by the import (e.g. by adding a new software prototype). In this case, the import is aborted with an error message. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. Workaround: In the report toolbar, click the Select artifact at placeholder button to select the associated artifact in the Model View. Workaround: Perform a complete model import which creates new UUIDs for the imported artifacts. Manually merge the relevant changes from the imported data into the existing software composition type. Moving a checked-in Logical Function Type creates illegal model state (1774840030000) Moving a checked-in Logical Function Type from the Library to a Logical Function creates an illegal model state. A dependently versioned artifact is created with different revision information than its parent. "Update Reuse Unit" is only possible if latest version is contained in the model (1774844322645) The Update Reuse Unit action is aborted with an error message, if the latest version of the Reuse Unit is not contained in the current model. Backup requires increased hard disk space (1790491522658) Creating a project backup of a multi-user project requires significantly increased hard disk space. - 114 - Workaround: Check out the Logical Function Type before moving it from the Library. Workaround: Add the latest version of the Reuse Unit to the current model. In addition to the backup directory, the "richtexts" directory within the PREEvision workspace allocates a lot of space. Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP3 The hard disk space is allocated during backup creation only. After completing backup creation and closing the client, the allocated hard disk space is released. Workaround: Provide sufficient hard disk space. © Vector Informatik GmbH Version 6.5 SP13 - 115 - PREEvision 6.5 SP3 - 116 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP2 11 PREEvision 6.5 SP2 This chapter contains the following information: 11.1 Version numbers 118 11.2 Installation and compatibility information 119 11.3 New features 120 11.4 Fixed issues Common Diagrams and tables Product Goals Logical Function Architecture System Software Architecture Hardware Architecture Geometry Communication Product line management Change management Metrics and reports Collaboration Administration, installation and migration 121 121 122 122 122 123 123 124 124 125 125 126 126 126 11.5 Known issues 128 © Vector Informatik GmbH Version 6.5 SP13 - 117 - PREEvision 6.5 SP2 11.1 Version numbers Version numbers Documentation - 118 - Application Version number PREEvision client 6.5.2 LibreOffice dictionaries 4.0.3 PREEvision license server 2.0.0 PREEvision database server (2-tier) 2.0.13 PREEvision database server (3-tier) 6.5.1.3 PREEvision application server (3-tier) 6.5.2 Manual Version number PREEvision manual 6.5.2 PREEvision operating manual 6.5.2 PREEvision system requirements 6.5.2 Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP2 11.2 Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 6.5, refer to PREEvision 6.5 - Installation and compatibility information. Update of 3-tier environments to 6.5 SP2 In a 3-tier environment, the PREEvision client, the database server and the PREEvision application on the application server are only compatible within exactly the same 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. The following table shows compatible client, server application and database server script versions for PREEvision 6.5 to 6.5 SP2: Client version Server application version Database server script version 6.5.0 6.5.0 6.5.0.24 6.5.1 6.5.1 6.5.1.3 6.5.2 6.5.2 6.5.1.3 For an update of an existing 3-tier environment, all components with a changed version number must be updated, which may include the: > PREEvision client > PREEvision database server script > PREEvision application on the application server Reference: For detailed instructions on how to update a 3-tier environment, refer to the Operating Manual. To apply to internal IT guidelines, the execution of LibreOffice is now managed by Execution of LibreOffice managed PREEvision only. Users are no longer able to separately start LibreOffice without PREEvision running. Additionally, the installation path of the LibreOffice installation by PREEvision integrated in PREEvision is read-only. The described changes only apply to the LibreOffice installation integrated in PREEvision, external LibreOffice installations remain unchanged. Installation of LibreOffice dictionaries LibreOffice is integrated in the PREEvision client for editing formatted texts and report templates. To enable the LibreOffice spell check, a dictionary with the corresponding language is required. The dictionaries (LibreOfficeExtensions_v403.zip) now have to be separately installed into the PREEvision installation directory after the PREEvision client installation: Reference: For detailed information, refer to the Operating Manual. © Vector Informatik GmbH Version 6.5 SP13 - 119 - PREEvision 6.5 SP2 11.3 New features Refactorings of the System Software Architecture The refactoring Convert SW Component of the System Software Architecture has been enhanced. The refactoring creates valid type-prototype-instance structures and considers reuses now. The following refactorings of the System Software Architecture have been adapted according to the typeprototype-instance concept which has been introduced with PREEvision 6.5: LIN and AUTOSAR - 120 - > Convert SW Component > Connect Port(s) > Update SW Component Type > Merge SW Component Types with the same name and type Designing LIN busses is now possible. LIN busses can be imported and exported via AUTOSAR 4.0.3 and 4.1.1. Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP2 11.4 Fixed issues Fixed issues in PREEvision 6.5 SP2 You will find the important fixed issues in the following table. Please note that some issues are depending on specific configurations, views or models. Further information > Common > Diagrams and tables > Product Goals > Logical Function Architecture > System Software Architecture > Hardware Architecture > Geometry > Communication > Product line management > Change management > Metrics and reports > Collaboration > Administration, installation and migration 11.4.1 Common ID Issue Category 1776954474915, 1779722248454 Selection changes are now reliably propagated to the Property View. Common 1778006402676 Tables and statistics can now be displayed in Common a Portlet View. 1779722268454, 1779722278454 Images are now correctly displayed in LibreOffice (including the LibreOffice editor and generated reports). 1779723359822 Certain circumstances could lead to duplicate Common XMIIDs. A prevention measure to solve this problem has been implemented. 1782617688454 The Config Property View is available again. Common 1783783272820 The compare functionality has been corrected. Common 1783784978214 In LibreOffice, EMF/WMF pictures are now Common displayed correctly if shapes are placed behind each other. The clipping problem has been solved. 1783832378214 During copy and paste of arrows from a PowerPoint document to LibreOffice in PREEvision, the arrowheads are filled correctly now. © Vector Informatik GmbH Version 6.5 SP13 Common Common - 121 - PREEvision 6.5 SP2 11.4.2 Diagrams and tables ID Issue Category 1773751369823 Centered labels are now correctly aligned. Diagrams 1774816848224, 1782601998224 In column metric cells, extra icons are no longer shown. Tables 1779722288454 Copy and paste of formatted text into attribute Tables columns of type Text and String works correctly now. 1779767288454 Values entered in string based table cells persist after leaving a cell with arrow keys or pressing the key. Tables ID Issue Category 1774844289822 During RIF import, the RequirementID is now correctly imported in the EPDM-ID field (if configured accordingly). Product Goals 1776955389822 If no context freezing point is set, the refactoring to recreate IDs is now also available on checked-in artifacts. Product Goals 1782622667721 For the RIF import the automatic locking Product Goals mechanism now checks which elements have to be locked. 11.4.3 Product Goals 11.4.4 Logical Function Architecture - 122 - ID Issue Category 1771712259823 The block type for Logical Domains is now shown on the General page in the Property View. Logical Function Architecture 1774828279822 Sections can be used in Logical Function Architecture diagrams now. Logical Function Architecture 1778006852647 A link named "Logical Type" was added to the Logical Function Property View of Logical Domains on Architecture property page General, which can be used to navigate to the corresponding logical type of a Logical Domain. 1779762018454 Required entries for creating logical port prototypes are now available in the Interface Assignment diagram palette and popup bar. 1779762408454 Port Communication Requirements can now Logical Function be created for logical sender and receiver port Architecture types. Version 6.5 SP13 Logical Function Architecture © Vector Informatik GmbH PREEvision 6.5 SP2 ID Issue Category 1779762418454 The shortcut menu of port types works properly now. Logical Function Architecture 1782627027721 References between ports and port Logical Function prototypes are still available after replacing a Architecture revision of a Reuse Unit. 11.4.5 System Software Architecture ID Issue Category 34771 Connect Port(s) refactorings properly run on Compositions if the preference Connect ports of compositions is set in the Preferences dialog under PREEvision | Refactoring | Software Architecture Port Connector. System Software Architecture 34783 The Pull Up refactoring has been corrected. System Software Architecture 1763642400455 The Convert SW Component refactoring is available again (see New features). System Software Architecture 1775905879822 The names of software types and prototypes System Software are only synchronized if the preference option Architecture Synchronize type name and first instance name is set in the Preferences dialog under category PREEvision | Type/Instance. 1779768837721 Port Types of Compositions are now also System Software displayed in the Property View on page Port Architecture Prototypes of Sender Receiver Interfaces. 1782606442689 The button Disable Automatic Figure System Software Completion During Drag and Drop Architecture operations is available in software diagrams again. The button can be used to avoid the creation of additional artifacts when a specific artifact is dropped (e.g. ports of a block). 11.4.6 Hardware Architecture ID Issue Category 34108 A checked-in System can be opened in the Architecture View. A transfer back to eASEE is not allowed. Hardware Architecture 1767580692647 The original Power Distribution perspective Hardware has been restored. Architecture © Vector Informatik GmbH Version 6.5 SP13 - 123 - PREEvision 6.5 SP2 ID Issue Category 1776955202693 In the Wiring Harness Diagram a new error message is shown when assigning a Schematic Connection which has no assigned Pins. Hardware Architecture 1778053202693 Moving pins in the Wiring Diagram has been Hardware improved. E.g. pins can be moved by 5 pixels Architecture if the grid size is set to 5. 1779138309823 The shortcut menu can be opened on checked-in Network Diagrams again. 1779768892693 The populate of Schematic Pins has been Hardware corrected: Schematic Pins are now correctly Architecture placed within the given slot layout. Within the 5x5 grid, a populate creates pins which partly cover each other, since pins are placed with a space of 5 pixels and the figure size of each pin is 10 pixels. 1782619952693 The attribute Min Outer Diameter is now available on the Pin Parameters property page of Pin Types. Hardware Architecture ID Issue Category 1774855790452, 1745477490452 In the Geometry Diagram and in the Wiring Diagram, the highlighting for a selected artifact remains visible when clicking on the diagram palette. Geometry 1779762270452 Geometry Diagrams are now correctly displayed again when using different zoom factors. Geometry ID Issue Category 34775, 1779431992689 DBC import with option Synthesize Software Communication Level and import alternative Automatic Import with Merging works properly now. 1774839917721 Routing entries are correctly displayed in the Communication Property View of CAN Frame Transmissions. 1774843869822 The Description field for Frames is available Communication again in the Property View. Hardware Architecture 11.4.7 Geometry 11.4.8 Communication - 124 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP2 ID Issue Category 1778006222727 When changing a sender/receiver Communication relationship in the LIN scheduling table, consistent sender/receiver relationships are automatically set for signal transmissions and frame transmissions. 1779142562791, 1779142582791 Computation methods are now correctly imported during AUTOSAR import. Communication 1779142572791 Computation methods are now correctly exported during AUTOSAR export. Communication 1779724969823 Only the necessary required ports and Communication mappings will be created during Fibex import. 1779735902791 The cell editor for communication attribute tables in the Property View has been correctly adapted to the data type. Communication 1779761928454 Descriptions for prototypes will now be imported during AUTOSAR import. Communication 1782606292791 The DBC import with enabled merge options works again. Communication 1782621267721 AUTOSAR files containing tags can now be imported. Communication 11.4.9 Product line management ID Issue Category 1782615378454 Ports are automatically created within diagrams of Building Blocks. If the Building Block itself is checked-in or its contained diagram is checked-in, the graphical representations of the ports are not created within the diagram. The same behavior has been implemented for the software architecture and composition type diagrams. Product line management 11.4.10 Change management ID Issue Category 1782604268218 Ticket attributes can be created with the [+] button on the Ticket Attributes property page. Change management © Vector Informatik GmbH Version 6.5 SP13 - 125 - PREEvision 6.5 SP2 11.4.11 Metrics and reports ID Issue Category 1782617688218 Connected Metric Executors are now Metrics displayed on the Usage property page of the Calculation Block. 34777, 1774840069822, 1782614298454 For generated reports, automatic selection of Reports artifacts in the Model View has been disabled due to an error in LibreOffice. When clicking on a placeholder in a report, the selection is not automatically updated. Workaround: In the report toolbar, click the Select artifact at placeholder button to select the associated artifact in the Model View. 11.4.12 Collaboration ID Issue Category 1771712017721 The check-out has been corrected to ensure new revisions can only be created on the latest revision. Older revisions can only be checked out as new branch. Collaboration 1774831432987 A file artifact which has been deleted and reimported again can now be successfully committed. Collaboration 1775905862680 Replacing a version with a version from its Collaboration history is now possible even if the artifact type has been changed, e.g. from ECU to Sensor. 1784092318454 Creating an assembly connection between two Logical Functions now only obtains shared locks on the parent artifacts (sender/ receiver Logical Function and parent package). Collaboration 11.4.13 Administration, installation and migration - 126 - ID Issue Category 1767561792647 The restore of project backups into a 3-tier environment has been improved to handle existing software structures from previous versions. Administration 1774831442676, 1779724959823 Initializing a specific administration package Administration with the default setup now works correctly, even if the package is not already available in the current model. For example, it is possible to individually add the Compare Configurations package to the current model. Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP2 ID Issue 1774833860451 The performance of the model export (Export Administration Model to File) has been improved. 1782619712987 The enableDummyFileCreation parameter is now also considered during restore in a 3-tier environment with SVN. Administration 1778006212711 Dialogs for the setup of Visual C++ 2010 Redistributable will no longer be displayed during PREEvision client installation. Installation 1776954442658, 1778004672658 Perspective configuration files are now correctly created during migration from PREEvision 6.0 to 6.5 SP2. Migration 1779722088353 Performance improvements have been implemented for the migration. Migration 1782624408351 References between interfaces and interface Migration assignments (located in the software instance layer) are now correctly migrated. © Vector Informatik GmbH Version 6.5 SP13 Category - 127 - PREEvision 6.5 SP2 11.5 Known issues Double click does not Sporadically, double clicking on an artifact may not open the defined standard editor. open the standard For example, instead of a table, diagram or report template, the form editor is always editor opened. Workaround: Keep pressed and double click again. Afterwards, double click again. and double click opens the form editor. Afterwards, a double click correctly opens the standard editor. Formatted text field cannot be edited Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams and tables in a report are not correctly printed (1715978292643) Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Artifacts referenced by a placeholder in a report are not automatically selected (34777, 1774840069822) For generated reports, automatic selection of artifacts in the Model View has been disabled due to an error in LibreOffice. When clicking on a placeholder in a report, the selection is not automatically updated. Software composition types cannot be changed via custom model import (1782615368223) The custom model import does not work when an existing software composition type of the target model shall be changed by the import (e.g. by adding a new software prototype). In this case, the import is aborted with an error message. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. Workaround: In the report toolbar, click the Select artifact at placeholder button to select the associated artifact in the Model View. Workaround: Perform a complete model import which creates new UUIDs for the imported artifacts. Manually merge the relevant changes from the imported data into the existing software composition type. Moving a checked-in Logical Function Type creates illegal model state (1774840030000) Moving a checked-in Logical Function Type from the Library to a Logical Function creates an illegal model state. A dependently versioned artifact is created with different revision information than its parent. "Update Reuse Unit" is only possible if latest version is contained in the model (1774844322645) The Update Reuse Unit action is aborted with an error message, if the latest version of the Reuse Unit is not contained in the current model. - 128 - Workaround: Check out the Logical Function Type before moving it from the Library. Workaround: Add the latest version of the Reuse Unit to the current model. Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP1 12 PREEvision 6.5 SP1 This chapter contains the following information: 12.1 Version numbers 130 12.2 Installation and compatibility information 131 12.3 New features 133 12.4 Fixed issues Common Diagrams and tables Product Goals Logical Function Architecture System Software Architecture Hardware Architecture Geometry Communication Product Line Management Rules, metrics and reports Collaboration Administration, authority, license, installation and migration 134 134 135 137 137 138 139 140 141 141 142 143 144 12.5 Known issues 146 © Vector Informatik GmbH Version 6.5 SP13 - 129 - PREEvision 6.5 SP1 12.1 Version numbers Version numbers Documentation - 130 - Application Version number PREEvision client 6.5.1 LibreOffice dictionaries 4.0.3 PREEvision license server 2.0.0 PREEvision database server (2-tier) 2.0.13 PREEvision database server (3-tier) 6.5.1.3 PREEvision application server (3-tier) 6.5.1 Manual Version number PREEvision manual 6.5.1 PREEvision operating manual 6.5.1 PREEvision system requirements 6.5.1 Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP1 12.2 Installation and compatibility information Reference: For detailed information about the installation and compatibility of PREEvision 6.5, refer to PREEvision 6.5 - Installation and compatibility information. Installation of Visual C++ 2010 during client installation During PREEvision client installation, Visual C++ 2010 Redistributable is automatically installed. If Visual C++ 2010 Redistributable is already installed on the computer, a dialog will be displayed asking the user whether to reset or uninstall the existing installation. In this case, select the option to reset Visual C++ 2010 Redistributable to its original state. Reinitializing the authority model For an update of a multi-user environment from PREEvision 6.5 to 6.5 SP1, the authority model must be reinitialized. Therefore, proceed just as usual for a migration: 1. Export the latest version of the existing authority model. 2. Initialize a new authority model with PREEvision 6.5 SP1. 3. Merge customer-specific changes from the PREEvision 6.5 backup into the newly initialized authority model. Reference: For detailed information about the migration of the authority model, refer to the Operating Manual. Update of 3-tier environments to 6.5 SP1 In a 3-tier environment, the PREEvision client, the database server and the PREEvision application on the application server are only compatible within exactly the same 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. The following table shows compatible client, server application and database server script versions PREEvision 6.5 and 6.5 SP1: Client version Server application version Database server script version 6.5.0 6.5.0 6.5.0.24 6.5.1 6.5.1 6.5.1.3 For an update of an existing 3-tier environment, all components with a changed version number must be updated, which may include the: > PREEvision client > PREEvision database server script > PREEvision application on the application server Reference: For detailed instructions on how to update a 3-tier environment, refer to the Operating Manual. © Vector Informatik GmbH Version 6.5 SP13 - 131 - PREEvision 6.5 SP1 To apply to internal IT guidelines, the execution of LibreOffice is now managed by Execution of LibreOffice managed PREEvision only. Users are no longer able to separately start LibreOffice without PREEvision running. Additionally, the installation path of the LibreOffice installation by PREEvision integrated in PREEvision is read-only. The described changes only apply to the LibreOffice installation integrated in PREEvision, external LibreOffice installations remain unchanged. Installation of LibreOffice dictionaries LibreOffice is integrated in the PREEvision client for editing formatted texts and report templates. To enable the LibreOffice spell check, a dictionary with the corresponding language is required. The dictionaries (LibreOfficeExtensions_v403.zip) now have to be separately installed into the PREEvision installation directory after the PREEvision client installation: Reference: For detailed information, refer to the Operating Manual. - 132 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP1 12.3 New features FlexRay busload table PREEvision now offers a preconfigured FlexRay busload table. The FlexRay busload table is an example for a configured table in the area of communication showing a set of attributes for the scheduled PDUTransmissions in a FlexRay bus. This table is available on the Schedule. FlexRay comparison configurations PREEvision now offers two preconfigured comparison configurations for FlexRay as an example for extending the comparison functionality. > The "FIBEX Elements" Compare Configuration presents the main FIBEX elements starting from a Schedule displaying them in a very similar structure as they appear in a FIBEX file. > The "FlexRay Communication Matrix" Compare Configuration prepares the data to be compared starting from a determined component (ECU, Sensor, etc.) showing only the communication aspect of it. Signal and frame overview tables PREEvision now offers two predefined tables available on a Communication Package. The "Signal Overview" table and the "Frame Overview" table display the main attributes of the Signals and Frames contained in the Communication Package. Support of J2602 The LDF import/export now supports the J2602 format. © Vector Informatik GmbH Version 6.5 SP13 - 133 - PREEvision 6.5 SP1 12.4 Fixed issues Fixed issues in PREEvision 6.5 SP1 You will find the important fixed issues in the following table. Please note that some issues are depending on specific configurations, views or models. Further information > Common > Diagrams and tables > Product Goals > Logical Function Architecture > System Software Architecture > Hardware Architecture > Geometry > Communication > Product Line Management > Rules, metrics and reports > Collaboration > Administration, authority, license, installation and migration 12.4.1 Common - 134 - ID Issue Category 27185 Sometimes it was not possible to shutdown PREEvision after a long work session. The problem has been fixed. Common 29869 Mapping dialogs can now be filtered. Common 33654 Resetting perspectives works correctly. Common 34565 Selection propagation from the Favorites to a historic version loaded in the Model View works as expected. Common 34590 The value check for the number of logged actions in the preferences now covers the range [0, maxInt]. The initial value is 0 and valid. Common 34715 A progress bar for executing the online check Common is displayed again in the status bar of the main window. 9760572727 All toolbar items can now be hidden via the Window | Customize Perspective command. Common 1756612179823 The shortcut menu item Open as second project for model comparison is now always available in the Project View. In the case that no Compare Configuration is available, a corresponding information is shown in the shortcut menu. Common Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP1 ID Issue Category 1764639112689 Formatted texts are saved after restoring their Common content. 1767565118454 Mappings can now be created between artifacts in a Logical Architecture Diagram and a Software Diagram. Common 1767565138454 Views can now be opened even if the currently loaded model contains no perspectives. Common 1773773020000 When opening a URL to another project, the project will be opened. Common 12.4.2 Diagrams and tables ID Issue Category 17445 A diagram update via will also update modified background images. Diagrams 19247 When moving an area consisting of several artifacts and connections within a diagram, the connections are now correctly moved together with the selected area. Diagrams 19856 Icons are now correctly updated according to Diagrams a rule-based object configuration. For example, if an icon is no longer valid because the associated rule does no longer match, the icon is changed to the default setting. 22867 Icons configured via the object configuration are now correctly considered and displayed in dynamic labels. 26560 Offset and relative position are considered for Diagrams embedded labels. 32862 Rectangular routing has been corrected. 34754 Diagrams are no longer scaled during export Diagrams as image. 34755 Scrollbars within labels work correctly, now. Diagrams 34756 If label texts are too long, they will be cut during diagram export as image. Diagrams 1708713112790 A diagram update via will also update Diagrams and re-evaluate the object configuration of all figures. © Vector Informatik GmbH Version 6.5 SP13 Diagrams Diagrams - 135 - PREEvision 6.5 SP1 ID Issue Category 1716390388454 While switching between Legend and Title Block the following behavior is now given: Diagrams > The Title Block is placed on the other side if a Legend is already contained and has as position the default position of the Title Block. > If the Title Block is already contained and a Legend is inserted later, the Legend has as default position the position of the Title Block and is pasted on the opposite side. This behavior is only active while as position the option Free position is not selected. - 136 - 1742440148454 For mapping boxes displayed in diagrams, scrollbars are available. 1754725652693 When dereferencing a diagram configuration Diagrams from a network diagram no invalid object exception is shown in the log file anymore. 1767565128454 Mapping boxes displayed in diagrams, are now correctly updated. Diagrams 9111, 32526 Table cells with content larger than the cell height can now be scrolled. Tables 19421 Actions on table cells now work properly even Tables if columns are hidden. 29942 The cell height is now calculated according to Tables the given font size in the columns. 29947 With , the table editor and all contained model queries are refreshed and reevaluated, now. Tables 32515 In table editors, scrollbars are now correctly represented in formatted text cells. Tables 1719778039822 If in the table configuration, the Enable Delete option has been deactivated for a table column, Delete will no longer be available in the shortcut menu of this table column. Tables 1752879462687 New columns added to the Requirement Text Tables Editor directly show content if the content is available. Additionally, the performance for opening the Add/Remove/Reorder Columns dialog has been improved. Opening the dialog now takes between one and two seconds. 1764607058454 Copy and paste from Excel into an attribute column is now possible. Version 6.5 SP13 Diagrams Tables © Vector Informatik GmbH PREEvision 6.5 SP1 ID Issue Category 1766554468454 Requirement attributes which display formatted text are now exported correctly to Excel. Tables 1768603937721 A temporarily opened table editor now shows Tables all content even if model queries with anchors are used. 12.4.3 Product Goals ID Issue Category 34562 Undo/redo works correctly for conditions created in the Customer Feature Editor. Product Goals 1754687048454 Formatting and IDs are now kept when importing requirements via the RIF import. Product Goals 1754688032716 Embedded objects (OLE objects) of Product Goals requirements can now be changed even if the requirements have been imported with the RIF import. The changes within the OLE objects are stored, now. 1762701928354 Formatting is now correctly imported during RIF import. XML tags for formatting, such as bold, italic etc., are taken into account. Product Goals 1768558112677 In case a requirement has been reused the identification number is set to "0" because reused artifacts cannot have different values for one version attribute. Product Goals 12.4.4 Logical Function Architecture ID Issue 16595 If the artifact name is defined directly on Logical Function artifact creation, e.g. in a separate dialog, the Architecture name is immediately taken over without additionally switching to name editing mode. 34757 The performance of refreshing a Logical Architecture System Diagram containing labels has been improved. 1716476308454 The creation of labels for assembly nets can Logical Function be prohibited by setting the option Do not Architecture create labels in the preferences. The option is available on the preference pages Logical Architecture System Diagram and Software Architecture System Diagram. © Vector Informatik GmbH Version 6.5 SP13 Category Logical Function Architecture - 137 - PREEvision 6.5 SP1 ID Issue Category 1716477068454 Moving ports is now possible between components of different Logical Function Packages. Logical Function Architecture 1756607149823 In Logical Architecture Diagrams, connections are now selected even if only a part of the connection is within the selection area. Logical Function Architecture 1763642168454 Commit is possible again after moving Logical Function Building Block Types from a subsystem to the Architecture library. 1764607218454 The relation to the Building Block Type will no Logical Function longer be lost if the type is moved from the Architecture block instance to the Library. 1766549580000 The Convert Block refactoring now considers the automatic locking mechanism. Missing locks are detected and reported to the user. Logical Function Architecture 1774823059822 The Create Building Block refactoring has been corrected. Logical Assembly Connectors are now correctly displayed for the newly created Building Block. Logical Function Architecture 12.4.5 System Software Architecture - 138 - ID Issue Category 12380 For compositions, icons can now be configured in the object configuration. System Software Architecture 24671 Connect port refactorings can now be executed on multiple ports. System Software Architecture 34753 In the System Software Architecture layer, ports can now be correctly populated. System Software Architecture 1764607062647, 1774826647721 Update of a software structures is now possible within a Reuse Unit. System Software Architecture 1773751309822 The Size Type attribute can now be set in the System Software Property View of data type Array. Architecture 1773751559822 The Data Source values for the label graph nodes representing a port in a Software Architecture System Diagram are now properly set. Version 6.5 SP13 System Software Architecture © Vector Informatik GmbH PREEvision 6.5 SP1 12.4.6 Hardware Architecture ID Issue 15866 The name of Splices and Inline Connectors is Hardware also configurable for the KBL export within the Architecture respective configuration file. 16276 Warning for the KBL export displayed in the Information View have been corrected. 17344 When changing the routing to rectilinear Hardware without changing the port layout in the Electric Architecture Circuit Diagram, Pin positions are no longer changed. 17530 Populate in the Wiring Harness Diagram does Hardware no longer change Pin positions. Architecture 17887 The handling of Pins of Inline Connectors during KBL import has been improved. 17888 During an KBL import the respective Hardware connector types are created and assigned to Architecture the connector. 19287 Moving free text elements within a component is possible again. Hardware Architecture 30101 Refactoring shortcut menus on ports have been aligned between diagram and Model View (as far as possible). Hardware Architecture 30633 Internal components are now version objects Hardware and reusable. Architecture 34509 Connected and unconnected connectors are now displayed in the Component Diagram in the same way as in the Network Diagram. 34761 It is now possible to link a Bus Connector with Hardware a Bus System, e.g. in Property View, even if Architecture both artifacts are not checked-out. The change is possible on both sides. 1741280588454 Wiring Connectors are now displayed Hardware correctly in the Wiring Harness Diagram after Architecture they have been created. 1743331160452 Rectangular routing in the Geometry Diagram routes inline Branch-Offs correctly, now. 1745477520452 For the circuit synthesis (without Wiring Hardware Harness) the Do not create Splices ... option Architecture is no longer available. 1751961482693 In Network Diagrams, the Power Distribution Output Connectors are displayed as triangle again. © Vector Informatik GmbH Version 6.5 SP13 Category Hardware Architecture Hardware Architecture Hardware Architecture Hardware Architecture Hardware Architecture - 139 - PREEvision 6.5 SP1 ID Issue Category 1752882842693 Internal Schematic Connections and Hardware Devices are now variant-sensitive for the current calculation. Hardware Architecture 1753783942693 If a drop operation on an existing diagram is not possible, the background color of the diagram will no longer be changed to blue. Hardware Architecture 1754724212693 Undo is now possible for operations executed Hardware before a ground spot optimization. Architecture 1767561680452 Header connectors were not migrated correctly from PREEvision 6.0 to 6.5. Header connectors are now migrated correctly when migrating from PREEvision 6.0 to 6.5.1. New Pins and Headers are placed correctly on the grid. Hardware Architecture 1767562020452 The naming definition in the KBL export properties file is now considered during the KBL export. Hardware Architecture 1774818902790 When generating a Wiring Diagram out of an Hardware Electric Circuit Diagram, pins and header Architecture connectors are now placed correctly. 12.4.7 Geometry - 140 - ID Issue Category 18690 The selection of Title Blocks in Geometry Diagrams has been enhanced. Geometry 18690 The performance has been improved when working with many Geometry Diagrams. Geometry 24217 Special characters contained in the Geometry description of Topology Inline Connectors are now correctly displayed in the refactoring Merge selected inline connectors. 32569 The progress dialog for calculating highlights Geometry is mainly avoided through performance improvements. However, the dialog will still be shown if the highlight calculations exceed two second in order to provide proper feedback. 33057 In the Geometry Diagram, tooltips are still displayed when adding a background image to an Installation Location. Version 6.5 SP13 Geometry © Vector Informatik GmbH PREEvision 6.5 SP1 12.4.8 Communication ID Issue Category 17538 In the Signal router wizard, if only one Communication element is available for a drop-down list, it will be automatically selected. 28658 During AUTOSAR import, unnecessary PDU Communication assignments will no longer be created. 32905 The AUTOSAR export now generates the correct number of SignalIPDUs and map them to corresponding PDU-TRIGGERINGS. 1758508690000 During AUTOSAR import, signal degradation Communication in AUTOSAR 3.2.2 is now correctly imported. 1759453310000 Signal degradation can now be configured in Communication the Property View. 30472252791 During DBC export, the Frame ID of the Communication Frame Transmission is used, if it is set there. Otherwise, the Frame ID of the Frame is used. 1761756199822 During DBC export, negative start positions are set to 0 to prevent DBC files with syntax errors (negative start values are not supported and cannot be read from DBC files). Communication 1761756249822 The DBC export now works correctly if the Export active variant only option is activated. Communication 1768563989822 During AUTOSAR export, the export of embedded complex data types is possible. The category TYPE_REFERENCE is set for complex data types. Communication 1774833800455 During AUTOSAR import, the signal length is Communication now correctly imported. 1774843849822 The DBC export with an active variant works correctly, now. Precondition: A Frame Layout Configuration must be contained in the variant to get the expected results from the DBC export. Communication Communication 12.4.9 Product Line Management ID Issue 17912 In the Variant Diagram, it is now possible to Product Line populate a Concept Space including Concept Management Templates (shown as arrow). 18042 The Architecture Variant can be changed in the Variant Diagram. © Vector Informatik GmbH Version 6.5 SP13 Category Product Line Management - 141 - PREEvision 6.5 SP1 ID Issue Category 18043 In the Variant Diagram, delete actions have been improved for Architecture Variants. Product Line Management 34721 Newly created EE Attributes of the variant management are only shown once in the Model View. Product Line Management 1745477580452 Show Reuse works correctly on connections. Product Line Management 1757553928454 Conditions between parent and child Product Line Customer Features are no longer lost. Reuse Management synchronization now works correctly. 1767573618454 The synchronization error during integration from a reuse-unit has been corrected. 1767573778454 For reusing and integrating a Reuse Unit in a Product Line Product Line, sufficient locks are now Management automatically obtained. Product Line Management 12.4.10 Rules, metrics and reports - 142 - ID Issue 28094 Since the rule model distribution has been re- Rules designed in PREEvision 6.0 the error „consistency check not executable“ does no longer occur. 33940 In the rule diagram, the drop-down list for selecting the role of a link pair is completely visible, now. Rules 1754725642693 Newly created model queries are now immediately visible in the object configuration. Rules 19337 Working with Metric Diagrams no longer causes delays. Metrics 22727 Accessing the SWT and JFace framework is possible within the source code of a Calculation Block. Metrics 31895 The metrics Java editor window is Metrics automatically closed when switching between perspectives. 1757553719026 The content of a Metric Context Block is now Metrics correctly updated in the Metric Diagram. 1757557988454 The version history and the commit history are accessible within the source code of a Calculation Block via the methods: > getVersionHistoryOfObject > getCommitHistoryOfObject Version 6.5 SP13 Category Metrics © Vector Informatik GmbH PREEvision 6.5 SP1 ID Issue Category 1759453938454 In the Report Result Block, it is now possible Metrics to reference a TempTable containing cells that have NULL values. 1770669052693 Undo/redo now works correctly after metric execution. Metrics 17793 For creating descriptions, formatted text is used. When generating a report, formatted description texts are thus automatically integrated in the report. Reports 32331 Numbering in reports has been corrected when inserting formatted texts with a numbered lists. Reports 32332 The behavior of numbering headlines has been corrected in the report generator. Reports 34749 Only syntactically correct placeholders can be added to report templates, now. Reports 1716219380000 With LibreOffice, a report can now be saved even if it is manually edited after generation. Reports 1774833829822 Editing report placeholders works again. Reports ID Issue Category 34759 Columns of tables are now sorted correctly after master database synchronization of a table editor. Collaboration 34760 The performance of search in history has been improved. Collaboration 1711941552790 In 3-tier environments, commit labels are set und updated correctly, now. Collaboration 1740344168454 After a commit the icon states in the Model View are refreshed. Collaboration 1757553400451 The performance of show version history has Collaboration been improved. 1757563560451 Corrected commit error caused by multiple reuses. Collaboration 1770662320451, 1766550622647 The performance of comparing two versions from the version history has been improved. The performance of drag and drop from the version history has been improved. Collaboration 12.4.11 Collaboration © Vector Informatik GmbH Version 6.5 SP13 - 143 - PREEvision 6.5 SP1 ID Issue Category 1773760132987 The problem that, sporadically, files were deleted in SVN but not in PREEvision has been solved. Collaboration 1773767822987 If an error occurs during creation an external working copy, a useful message is now displayed. Collaboration 12.4.12 Administration, authority, license, installation and migration - 144 - ID Issue Category 29715398454 The performance of importing project backups for rule models has been improved. Administration 1758501972687 The performance of project initialization in the Administration 3-tier environment has been improved. 1760920550451 The robustness of the 3-tier project restore has been improved. Administration 1760922210451 The performance of the 3-tier project restore has been improved. Administration 1766555018214 Initializing the current model with the default setup no longer results in duplicate XMIIDs. Administration 1768576520000 Initialization of database/server projects with an *.eea file works correctly, now. Administration 1723980372689 Navigating to an artifact via the quick search now works correctly in the authority model. Authority 1757558308216 Title Blocks are now displayed when changing the Diagram Configuration using a viewer license. License 1751960772687 The 3-tier database server installation script can now also be executed on Linux. Installation 27210, 1769628440000 A file-based model can be saved after Migration migration, again. The save button is enabled. 34553 The restore information (restore.ser file) Migration for a database restore with history is now located in the corresponding backup directory instead of the workspace directory. 1725649399822 The order of record implementation elements Migration is now migrated correctly. 1754725529822 A tailing space directly in front of the .eea file Migration extension is not allowed as model file name. For example. "mymodel.eea" is invalid. To correctly migrate the model, rename the *.eea file. Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP1 ID Issue 1758501982687 Perspective files are now correctly integrated Migration during the migration from PREEvision 6.0 to 6.5. 1764629430000 Backup and restore now work correctly. For Migration migration, the backup must be created with the new client version (PREEvision 6.5 SP1). 1768563987721 Diagram representations of comments, timing paths and conditions associated to an assembly instance are now correctly migrated during migration from PREEvision 6.0 to 6.5. 1771711968224 During migration, header connector positions Migration are adapted now in the same way as the pin positions. 1774807519822 Enumerations are now correctly handled during migration. © Vector Informatik GmbH Version 6.5 SP13 Category Migration Migration - 145 - PREEvision 6.5 SP1 12.5 Known issues Perspective configurations are missing/defective after migration (1776954442658, 1778004672658) When migrating a 2-tier model without files (files are excluded from the backup), perspective configuration files are not automatically added to the model during migration. When migrating with files (files are included in the backup), the perspective configuration files added during migration are partly defective. Workaround: After the migration: 1. Load the latest model version of the migrated model. 2. Delete all existing contents from the Administration | Perspective Configuration Model (if available). 3. Use Administration | Initialize current model with default setup and select the Perspective Configuration Model to be merged with the current model. Double click does not Sporadically, double clicking on an artifact may not open the defined standard editor. open the standard For example, instead of a table, diagram or report template, the form editor is always editor opened. Workaround: Keep pressed and double click again. Afterwards, double click again. and double click opens the form editor. Afterwards, a double click correctly opens the standard editor. Formatted text field cannot be edited Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams and tables in a report are not correctly printed (1715978292643) Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Initialize current model with default setup requires parent package (1774831442676) When selecting a specific package to be initialized with the default setup, the same package has to be already available in the current model. Otherwise, the contents will not be merged. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. For example, selecting only the "Compare Configurations" package to be integrated in the model does only work, if the "Compare Configurations" package is already available in the current model. Workaround: Manually create the parent packages of the items to be integrated. Moving a checked-in Logical Function Type creates illegal model state (1774840030000) - 146 - Moving a checked-in Logical Function Type from the Library to a Logical Function creates an illegal model state. A dependently versioned artifact is created with different revision information than its parent. Workaround: Check out the Logical Function Type before moving it from the Library. Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 SP1 "Update Reuse Unit" is only possible if latest version is contained in the model (1774844322645) Highlighting is lost when clicking on the diagram palette (1774855790452) Type change makes replace from history impossible (1775905862680) The Update Reuse Unit action is aborted with an error message, if the latest version of the Reuse Unit is not contained in the current model. Workaround: Add the latest version of the Reuse Unit to the current model. The highlighting for a selected artifact is lost when clicking on the diagram palette. The problem occurs in the Geometry Diagram and in the Wiring Diagram. Workaround: Select the artifact in the Model View or the Favorites and pin the view. Replacing a version with a version from its history is not possible if the artifact type has been changed, e.g. from ECU to Sensor. Workaround: Instead of a type change, create a new artifact. Diagram layout is not Copying a diagram layout into another diagram does not work correctly for rotated correctly copied for devices. rotated devices Workaround: Manually adjust the diagram layout. Viewer licenses cannot change table column widths When working with a viewer license, table column widths cannot be changed. When opening tables, the column width may not be changed either through dragging the separator with the mouse nor setting the width explicitly in the Property View. © Vector Informatik GmbH Version 6.5 SP13 - 147 - PREEvision 6.5 SP1 - 148 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 13 PREEvision 6.5 This chapter contains the following information: 13.1 Version numbers 150 13.2 Installation and compatibility information 151 13.3 New features 153 13.4 Fixed issues Common Diagrams and tables Product Goals Logical Function Architecture System Software Architecture and AUTOSAR Hardware Architecture Communication Product Line Management Rules, metrics and reports Collaboration Administration, license, installation and migration 160 160 161 162 162 163 164 164 165 166 167 168 13.5 Known issues 169 © Vector Informatik GmbH Version 6.5 SP13 - 149 - PREEvision 6.5 13.1 Version numbers Version numbers Documentation - 150 - Application Version number PREEvision client 6.5.0 PREEvision license server 2.0.0 PREEvision database server (2-tier) 2.0.13 PREEvision database server (3-tier) 6.5.0.24 PREEvision application server (3-tier) 6.5.0 Manual Version number PREEvision manual 6.5.0 PREEvision operating manual 6.5.0 PREEvision system requirements 6.5.0 Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 13.2 Installation and compatibility information Compatibility 2-tier environments: The following table shows the compatibility between the different PREEvision client and database server versions: Client version Database server Database server Database server version 5.5 version 6.0/6.5 version 6.5 (2.0.10) (2.0.13) (2.0.14) 5.0.x read-only read-only read-only 5.5.x compatible compatible compatible 6.0.x not compatible compatible compatible 6.5.0 - 6.5.8 not compatible compatible compatible from 6.5.9 not compatible not compatible compatible 3-tier environments: In a 3-tier environment, the PREEvision client, the database server and the PREEvision application on the application server are only compatible within the same PREEvision version. The following table shows compatible client, server application and database server script versions for specific PREEvision 6.5 versions: 3-tier Collaboration Platform Client version Server application version Database server script version 6.5.0 6.5.0.24 6.5.0 The PREEvision Collaboration Platform is now available as 3-tier environment. Reference: For detailed information about the installation of the 3-tier environment and for migrating from 2-tier to 3-tier, refer to the Operating Manual. Reinitializing the authority model For an update of a multi-user environment from the PREEvision 6.5 release to any PREEvision 6.5 service pack, the authority model must be reinitialized. Therefore, proceed just as usual for a migration: 1. Export the latest version of the existing authority model. 2. Initialize a new authority model with PREEvision 6.5 SP. 3. Merge customer-specific changes from the PREEvision 6.5 backup into the newly initialized authority model. Reference: For detailed information about the migration of the authority model, refer to the Operating Manual. Licenses and license For PREEvision 6.5, new licenses are required. server With PREEvision 6.5, a new version (2.0.0) of the PREEvision license server is available. It is recommended to update existing license servers to version 2.0.0. © Vector Informatik GmbH Version 6.5 SP13 - 151 - PREEvision 6.5 PREEvision database Oracle clusters (RAC) are not supported. server: Oracle clusters (RAC) are not supported PREEvision workspace and PREEvision.ini Existing workspaces from earlier PREEvision versions cannot be reused for PREEvision 6.5. Overwriting the PREEvision.ini is not allowed as well. Operating system: character set Please do use an operating system with a full character set of your language. For example, in order to support Japanese in PREEvision, the Japanese operating system has to be installed. An English operating system with Japanese character set might not support all characters. As a consequence, this may result in displaying wrong characters in PREEvision. - 152 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 13.3 New features Collaboration Platform as 3-tier environment Automatic locking PREEvision Collaboration Platform is available as 3-tier environment, now. The 3-tier platform contains all features of the current 2-tier platform and provides the following new and additional features: > Branches: Branches are available to check out a historic artifact revision to start a parallel development line. Branches can be created during check-out on the basis of any artifact version. In the Check-out dialog the user defines whether a new development line for an artifact shall be started by creating a new branch. Branches are visible in the Model View, the Version History and the Property View. > Search in history: The search option Current and historic model versions is available. In the search result view, historic artifacts are indicated by a grey font color. The column Model version provides the corresponding model version. A historic artifact version can be inserted in the current model as new artifact or as reuse. > Life cycle history: On the Lifecycle property page, an additional life cycle History table is available. The life cycle history displays all life cycle state changes an artifact has passed through during its life cycle. > Subversion integration: File handling in PREEvision’s 3-tier environment is now supported by the open source revision control system Subversion (SVN). Working copies of file structures can be created which improves the handling of large file structures and provides the base functionality for several use cases, for example test data management. > Middleware license server (optional): Server licenses can be managed in the integrated middleware license server. Alternatively, node-locked licenses can be used. With PREEvision 6.5, an automatic locking concept has been introduced. The user can now directly start editing or start an action without prior locking. This works for all actions in PREEvision including diagrams and shared locks. With the automatic lock handling, lock conflicts can be reduced, since only the minimum required locks are determined and obtained. © Vector Informatik GmbH Version 6.5 SP13 - 153 - PREEvision 6.5 AUTOSAR AUTOSAR 4 compliant data types as well as communication parameters are available in PREEvision. Additionally, the modeling of partial networking is supported. With the AUTOSAR use case, PREEvision is part of the Vector AUTOSAR Solution and the exchange workflow with DaVinci Developer and DaVinci Configurator Pro is possible. LIN bus communication LDF 2.0 import and export is now available. A schedule design for LIN communication can now be modeled. - 154 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 Use case oriented perspectives PREEvision now starts with a cockpit view on the user interface. The cockpit provides use case oriented entry points into PREEvision. With just a few clicks you reach the user interface that is available for your use case. An expert mode is also available that corresponds to the former PREEvision E/E standard perspective. With the help of Model View and Property View filters, perspectives can be customized to display only the artifacts relevant for the use case and keep the user interface clearly arranged. Electric details in wiring harness The following features have been introduces regarding hardware modeling: > © Vector Informatik GmbH Internal hardware components and electric details can also be modeled in the Electric Circuit Diagram and the Wiring Diagram, now. Version 6.5 SP13 - 155 - PREEvision 6.5 Specification of diagnostic requirements Test data management > With the Copy Layout function, completely modeled hardware components (including internal components) can be comfortably copied from one to another hardware layer. > In the Electric Circuit Diagram, the current path can now be populated. > The wiring harness synthesis can now be executed without creating splices. PREEvision supports the specification of diagnostics master-slave systems with diagnostic-specific attributes. > Use of PREEvision Network Diagram to model diagnostic relevant information as overview. > Extended modeling of diagnostic relevant information in PREEvision (diagnostic classification, DTCs, measurement signals, controls). > Export to CANdela and complementation of diagnostic specification in CANdela PREEvision can now be combined with vTESTcenter for test and test data management: Testing phases with bi-directional traceability between artifacts: > Requirements management > Test engineering > Test implementation: Automated tests and test lists for manual execution > Test execution planning > Test execution documentation import and archiving Analysis and reporting (graphical and table form) > - 156 - Metrics, requirements coverage, test progress, etc. Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 Usability improvements for diagrams Several usability improvements have been implemented in diagrams, especially for move and resize actions as well as for the alignment of labels. In the Property View, the following usability improvements have been implemented: Usability improvements for the > Recently changed property pages are now highlighted with bold font color. property view > The LibreOffice editor can now be opened by clicking on the Description label. > Usability improvements for drag and drop operations (Assistance view) A navigation bar at the top of the Property View displays the parent hierarchy of the currently selected artifact and can be used to navigate to any artifact within the hierarchy. An Assistance View is now available to support drag and drop operations. Depending on the currently selected drag and drop target, the Assistance View displays artifacts suitable for the drag and drop operation. The Assistance View is automatically loaded when clicking on a Property View table or a table editor to which artifacts can be added. © Vector Informatik GmbH Version 6.5 SP13 - 157 - PREEvision 6.5 Compare of artifacts The compare functionality has been revised and now supports to compare model parts. The compare can now be started from the shortcut menu via the following items: > Select as left side for compare > Compare with > Compare with each other (if two artifacts are selected) The shortcut menu items are available in the Model View, Version/Commit History and in tables. The compare algorithm now considers reuses, files and formatted text. Additionally, configurations for the compare function can be created to determine the artifacts, attributes and relations to be compared. The compare result is now displayed in a double-tree editor and can be exported to Excel. Software architecture The software architecture layer has been optimized and aligned with the AUTOSAR standard. Using a library-based approach according to AUTOSAR, it is now possible to work with types and prototypes in the Library. Additionally, the instance-based approach is supported as well. Therefore, it is now possible to work directly with software instances in the System Software Architecture while the associated (proto-) types are automatically synchronized in the Library. By these changes, the memory consumption of the complete software architecture layer has been reduced and the usability has been improved for AUTOSAR users. Safety features In PREEvision 6.5, malfunction mapping has been introduced, allowing EEarchitecture artifacts to be annotated (mapped) with malfunctions. Malfunctions carry safety-relevant constraints such as the failure rate which allows a quantitative safety approach on the annotated artifacts. PREEvision provides a safety characteristics library to create a catalogue of malfunctions which fit to the respective level of modeling. - 158 - Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 PREEvision tables in PREEvision tables (table editors) can now be included in a report via the new reports placeholder type PREEvision table. Charts in reports New metric blocks have been introduced which allow the generation of charts. Via the new report placeholder type Chart, the generated charts can be integrated in reports. Compile complete metric source codes All metric Source Code artifacts can now be checked for compilation errors at once. The action can be started from the shortcut menu of the Metric Model via Metrics | Compile all Sourcecodes. The result is displayed in the Information View. Product and release management integrated in Collaboration Platform Product and release management functionalities are now integrated in the PREEvision Collaboration Platform. The former product option PREEvision Product and Release Manager is no longer available. Miscellaneous > PREEvision is now based on Eclipse 4 > LibreOffice is now integrated in PREEvision for editing formatted text © Vector Informatik GmbH Version 6.5 SP13 - 159 - PREEvision 6.5 13.4 Fixed issues Fixed issues in PREEvision 6.5 You will find the important fixed issues in the following sections. Please note that some issues are depending on specific configurations, views or models. Further information > Common > Diagrams and tables > Product Goals > Logical Function Architecture > System Software Architecture and AUTOSAR > Hardware Architecture > Communication > Product Line Management > Rules, metrics and reports > Collaboration > Administration, license, installation and migration 13.4.1 Common - 160 - ID Issue Category 13071 Alphabetic sorting in the Model View now also considers the user-defined label configuration. Common 20045 The form editor now provides an own toolbar Common including the selection button. 30387 The selection in the model-merge result tree Common are no longer lost when changing filter settings. 34532, 34546 On opening the shortcut menu, the current selection is changed to the artifact on which the shortcut menu has been opened. 34533 Drag and drop of a parent artifact into one of Common its child artifacts is prevented, now. 34550 Copy and paste of Product Lines is possible, Common now. 34642 The Property View no longer freezes during Common a drag and drop operation. 9807112663 Artifacts in the Favorites will now be removed if a scope is activated which excludes these artifacts. Common 32761198454 Missing formatted texts are automatically restored during commit. Common 36243872658 Performance has been improved for selecting large sets of artifacts in the Model View. Common Version 6.5 SP13 Common © Vector Informatik GmbH PREEvision 6.5 ID Issue Category 1711955908454 LibreOffice is now integrated in PREEvision for editing formatted text. Common 1715174528454 Tables can now be created in data type packages, now. Common 1719778179822 When creating mappings for multiple Common artifacts via drag and drop, the mapping type can now be selected once for all artifacts of the same meta class. 13.4.2 Diagrams and tables ID Issue Category 32854 The Legend now provides artifacts for displaying the diagram name and the diagram configuration. Diagrams 34376 Internal labels can now be wrapped across multiple lines Diagrams 34659 The visibility of labels can now be correctly configured in the object configuration. Diagrams 1718930630000 Background images are now updated when the diagram configuration is changed. Diagrams 1731717408454 Changes within the object configuration of a Diagrams Legend can now be saved. 31465 An appropriate error message is displayed Tables when exporting a table to Excel and the target Excel file is not writable, e.g. because it is already open. 34530 After commit/lock the table column visibility does not change. 34677 Generic table editors can now be created on Tables Data Type Packages. 1715175998454 In the table editor configuration, for each Tables column can be defined whether the delete button is displayed when clicking into a table cell of this column. Therefore, on the General property page of the column, the Enable Delete option can be set. 1716219420000 The button now works for editing a regular expression within the column filter field of a table editor. © Vector Informatik GmbH Version 6.5 SP13 Tables Tables - 161 - PREEvision 6.5 ID Issue Category 1716219430000 Within the table shortcut menu, the actions Tables Show Whole Text, Show Row Number and Column Filter are now implemented as check boxes. 1719778199822 When creating a new artifact in a table its Tables name can be directly edited by pasting a text from the clipboard. 13.4.3 Product Goals ID Issue Category 32775998454, 32787892689 In the RIF import, WMF objects can now be imported as OLE objects. Product Goals 32789162689 Excel OLE objects can now be opened after Product Goals the RIF import. 1714403088454 Enumeration entries are now correctly imported during RIF import. Product Goals 1729989068454 Reused requirement attributes remain reused after an import with generating new UUIDs. Product Goals 13.4.4 Logical Function Architecture - 162 - ID Issue Category 34718 A Logical Function Package can now be created in a Logical Structure Package via the New shortcut menu. Logical Function Architecture 34719 Connections are now correctly populated during hierarchical populate in the Logical Archtecture System Diagram. Logical Function Architecture 32777278214 Renaming a port in the Logical Function Architecture requires the correct modifiable states for the port and the port prototype. A dialog will now be displayed to lock the required artifacts. Logical Function Architecture 1716477058454 The move ports refactoring has been fixed. Logical Function It is possible to move required ports to Architecture multiple target blocks again. The internationalization of the Move Ports dialog in the Logical Architecture layer was fixed. Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 ID Issue Category 1742437618454 When creating an Assembly Net in a Logical Logical Function Architecture System Diagram, the Assembly Architecture Connections are created as well and assigned to the Assemby Net. 1748207472687 Committing a change including new Logical Function connected logical functions in a building Architecture block is now possible without error message. 13.4.5 System Software Architecture and AUTOSAR ID Issue Category 19714 Diagrams of the System Software Architecture have been reworked. System Software Architecture 34674 Calibration parameters can now be defined for all software types. System Software Architecture 11418 Types, prototypes, interfaces, signals and "natural types" are now correctly imported during AUTOSAR import. AUTOSAR 33283 Required and provided port transmission mappings are now correctly created during the AUTOSAR import. AUTOSAR 34381 On the General property page of an Implementation Array, a link is now displayed to reference the Implementation Data Type. AUTOSAR 34485, 34612 Minimum delay of signal and PDU AUTOSAR transmissions is now correctly set during the AUTOSAR import. 34487 Port transmission mappings are correctly build. AUTOSAR 34586 In PREEvision 6.5, reuse is no longer used for AUTOSAR compositions. Therefore, check-out of a composition will no longer result in an inconsistent state. AUTOSAR 30473972791 During AUTOSAR import, a Computation AUTOSAR Method of category TEXTTABLE is imported as Verbal Table Conversion. During AUTOSAR export, Verbal Table Conversion and Text Table Conversion are exported as TEXTTABLE. 37044572791 The ECU extract contains only mapped SWCs, now. AUTOSAR 1718941439822 Implementation records are now exported during AUTOSAR export. AUTOSAR © Vector Informatik GmbH Version 6.5 SP13 - 163 - PREEvision 6.5 13.4.6 Hardware Architecture ID Issue Category 34372 A bus terminal resistor with 180 Ohm value has been added. Hardware Architecture 34528 Connections to component composites are Hardware now correctly considered in reused Network Architecture Diagrams. 34579 The wiring harness router works with automatic locking, now. 34626 In the Wiring Harness Diagram, labels can Hardware now be moved without positioning problems. Architecture 34645 The circuit synthesis works with automatic locking, now. 34724 Commit of Wiring Harness Diagrams is Hardware possible, even if the diagram name contains Architecture a comma. 1711114960452 Ground spot optimization does no longer create pins after being cancelled. Hardware Architecture 1713595662643 If a wire instance contains no color information the KBL export now fetches the color information from the wire type. Hardware Architecture 1733441690000 The correct grid size is now used for locating Hardware conductors in a cable. Thus, Wiring Harness Architecture Diagrams keep their layout after closing and reopening. Hardware Architecture Hardware Architecture 13.4.7 Communication - 164 - ID Issue Category 33682 During frame and PDU synthesis required locks are now correctly obtained. Communication 34425 A new column Owner has been added to the Communication property table Attribute Values of communication attribute definitions. 34655 Frame routing cardinalities have been adjusted in the meta model. Communication 34656 Cardinalities of routing entries have been adjusted in the meta model. Communication 34695 During the Fibex import, ports, port mappings and sending/receiving relations from Signal Transmissions/PDU Transmissions/Frame Transmissions to ECU Interfaces are created for multiplexed IPDUs. Communication Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 ID Issue Category 34702 The Fibex import is now possible, even if a problem with the header occurs. A warning will be displayed in this case. Communication 1755665038454 The DBC export works correctly, now. Communication 13.4.8 Product Line Management ID Issue 34281 If activated, the auto-resolver will be applied Product Line on all selected elements of a newly created Management alternative. 34288 Resolver results are now displayed Product Line compressed in one entry in the Information Management View, if multiple elements are propagated. 34335 A highlight for out-of-bounds values is now available in the VM Template View. 34527 The Reuse Unit View correctly displays the Product Line artifacts of the loaded model version, now. Management 34542 Scopes are now considered for the variant management, e.g. in the variant drop-down list. Product Line Management 1711942092790 The branch is checked on getting all predecessors for a Reuse Unit. Product Line Management 1711942622790 It is now possible to reuse a Reuse Unit directly from the Version History. Product Line Management 1723943012644 When merging two different artifacts from two Reuse Units to a single artifact in the integration Product Line, after the update, the artifact no longer needs to be reintegrated again. Product Line Management 1726489752644 Performance for updating reuse units has been improved. Product Line Management 1738590680000 Possible conflicts during the merge of to-one Product Line relations are now checked when merging an Management artifact from a Reuse Unit. 1746374772689 Replace with selected Version is now possible for all revisions of a Reuse Unit. Product Line Management 1746374782689 File artifacts are locked. Product Line Management 1751961080000 The Show/Hide Mappings function of the Variant Diagram now displays all kind of mappings in the selection dialog (e.g. also CF-X:Mappings). Product Line Management © Vector Informatik GmbH Version 6.5 SP13 Category Product Line Management - 165 - PREEvision 6.5 13.4.9 Rules, metrics and reports - 166 - ID Issue Category 30226 Distribution of rules has been improved. Once generated and committed, rules are distributed automatically with every update of the eea-model. Rule generation on each client is not necessary anymore. Rules 30534 Consistency checks work correctly, now. Rules 34317 Deleting artifacts including child artifacts is now possible from the Inconsistencies view. Rules 34534 The model query rule model is loaded during Rules connect; thus opening the shortcut menu now works as expected. 34647 Rule model files are now correctly Rules synchronized into the E/E model during master database synchronization. Commit of the model is possible. 1716000890000 To support chinese characters, Java files are Rules now written and compiled using UTF-8 encoding. 29058 The performance for metric calculation has been improved in order to support calculating metrics in tables. Metrics 33309 After adding/deleting external JAR files to/ from the model the JARs are now correctly updated. Metrics 34611 The graphical representation of artifacts in Metric Diagrams is now correct after synchronization with a master database. Metrics 1709547322687 Since the "Alienator" metric touches all artifacts, event triggered metrics have to be removed in advance to prevent excessive cycle times on large models. Metrics 1711118400452 Metric Executors are now alphabetically sorted in the Metrics shortcut menu. Metrics 1714400432689 The "BusLoad" metric has been fixed in the demo and default model. Metrics 1737665119822 If a port name is set to "source" it is handled Metrics as an anchor on the source object. 1742444518454 The content of a Metric Context Block is now Metrics correctly updated in the Metric Diagram. 34739 The table of contents in a generated report is refreshed after report generation, now. Version 6.5 SP13 Reports © Vector Informatik GmbH PREEvision 6.5 13.4.10 Collaboration ID Issue Category 32619 The 2-tier environment has been improved to avoid inconsistent lock states. Collaboration 33355 The connection data is shown in the title bar Collaboration if opening a model using File | Open Database Model. 34513 Opening the Version History on artifacts that were implicitly checked-in due to an import is now possible without error message. 34551 It is possible to commit imported reports and Collaboration metrics. 34573 Master database synchronization also removes deleted artifacts from the model. 34585 Network connection problems may cause an Collaboration inconsistent client state. 34587 The Lock operation is now available on all artifacts containing child artifacts. 1708707412790, 1708707432790, 1708707662790 With PREEvision 6.5, automatic locking has Collaboration been introduced which obtains only the minimum required locks. 1711135328454 Imported data can be committed if the required access rights are granted. Collaboration 1711942592790 Performance of loading the Version History has been improved. Collaboration 1745476808454 The operating Undo All Checkouts now Collaboration works correctly after a previous routing operation. All required locks for the routing operation are now obtained using automatic locking. 1748211132689 Using the 3-tier PREEvision Collaboration Platform including Subversion, it is now possible to set a download path, even if the artifact is checked-in. © Vector Informatik GmbH Version 6.5 SP13 Collaboration Collaboration Collaboration Collaboration - 167 - PREEvision 6.5 13.4.11 Administration, license, installation and migration - 168 - ID Issue Category 17488 Master database connection data can be modified in the master database config.xml file which is located in the Administration under Configuration File Container | Master Database Configuration Package. Administration 34646 Configuration file artifacts are now removed Administration from the model, if their folder cannot be determined due to an insufficient license. Commit of the initial default setup is possible. 1711135308454 Determining the artifact revision now works Administration correctly if a project is initialized with a file containing artifacts with relative revisions ("R +1"). 34643 Resources can also be created with a PREEvision Function Designer and Collaboration Platform license. License 1711134042687 Passwords with special characters are now accepted by the IAR-scripts. Installation 1746374888454 Relations that were external in V6.0.0 and have been changed into a type-of relation, are now migrated properly. Migration Version 6.5 SP13 © Vector Informatik GmbH PREEvision 6.5 13.5 Known issues Default perspective is After connecting to a project, sporadically the default perspective may not be not loaded automatically loaded. In this case, all perspective icons are displayed in the perspectives toolbar but no views are loaded. Workaround: In the perspectives toolbar, click on the icon of a perspective to manually load the perspective. Perspectives are not available Sporadically, no perspectives are available in the currently loaded model, for example after initializing a project with a file. Workaround: Reconnect to the project to reload the perspectives. Double click does not Sporadically, double clicking on an artifact may not open the defined standard editor. open the standard For example, instead of a table, diagram or report template, the form editor is always editor opened. Workaround: Keep pressed and double click again. Afterwards, double click again. and double click opens the form editor. Afterwards, a double click correctly opens the standard editor. Formatted text field cannot be edited Sporadically, a formatted text field will not be properly enabled for editing after clicking into it. Workaround: Click again into the formatted text field. Borders of diagrams and tables in a report are not correctly printed Borders of diagrams or tables (OLE objects) contained in a report are not correctly printed using the print function of LibreOffice. Workaround: In LibreOffice, first use Export as PDF... and print the PDF document afterwards. Diagram layout is not Copying a diagram layout into another diagram does not work correctly for rotated correctly copied for devices. rotated devices Workaround: Manually adjust the diagram layout. Viewer licenses cannot change table column widths When working with a viewer license table column widths cannot be changed. When opening tables the column width may not be changed either through dragging the separator with the mouse nor setting the width explicitly in the Property View. Viewer licenses do not show title blocks. If a Diagram Configuration references a Title Block and the Diagram Configuration is changed while working with a viewer license. the Diagram Configuration will be changed but the Title Block will not be shown. © Vector Informatik GmbH Version 6.5 SP13 - 169 - PREEvision 6.5 - 170 - Version 6.5 SP13 © Vector Informatik GmbH Get more Information! Visit our Website for: > News > Products > Demo Software > Support > Training Classes > Addresses www.vector.com