With Service Pack 3 (Update to 3.3 Build 42), the following changes become effective:
End-to-End protection resynchronization flags are now supported for AUTOSAR schema 4.0.3
Data Mapping of single signal to array data types is now supported if the array is part of a complex structure
Import feature "check for differences" is now available for AUTOSAR 4 Software Component Types
Misleading general import message "Ignoring internal data constraints" is now replaced with a more specific one if the data constraints are incompatible
Starting from an existing port it is now possible to create a foreign port, including a necessary connection
Copy&Paste of Data-Element-Prototypes and Port-Prototypes is now supported from one interface/component to another
The automatic data mapping has been enhanced to match sub-strings with the biggest possible string length
The 'adapt connected port' function has been enhanced with additional options
The default package path assignment to CompuMethods and Units was wrong
The properties button in the data selection dialog didn't work for AUTOSAR 4 data types
Wrong import of indexed elements (e.g. Record-Elements) has been fixed if the elements have temporarily the same name during import process
Import of Revision-Label at the InternalBehavior element was missing
Consistency check was not correctly executed for Calibration Communication-Specifications
The item locking state was not corrected stored for packages in DCF workspaces
In ARXML export of DCF saving the generic attribute IMPORT_MODE_PRESET was missing at the ECU-SW-Composition delegation ports
When importing an updated ECU-Extract an existing LIN-cluster was deleted.
If the delegation port of an ECU software composition was inconsistent the ARXML export aborts with error message 'Internal exception occurred: The connection is missing a valid transmitter or receiver port'
The Runnable Operation Access was not imported using a AUTOSAR 4 SoftwareComponentType in "overwrite" mode
The Component Type dialog not forbids setting the 'supportsMultipleInstantiation' flag for Service SWCs.
Internal exception during ARXML import has been fixed if an application data type was resolved using a workspace element
The package import mode workspace and session setting was ignored by the ARXML import dialog. Thus it always selected the package import mode 'import from file'
The ModeDeclarationGroups dialog was not correctly updated when explicit values of a mode have been changed
The color highlighting of compatible ports was not consistent during manually drawing of a connection
For AUTOSAR 4 design the following functionality is currently not available:
Create Port Prototype from data mapping based on a given signal
Adapt Data Type for Data Element based on a given signal