- EA Connector for codebeamer version 2.4.3 was released on February 7th, 2022.
- EA Connector for codebeamer version 2.4.2 was released on December 15th, 2021.
- EA Connector for codebeamer version 2.4.1 was released on December 1st, 2021.
- EA Connector for codebeamer version 2.4.0 was released on November 15th, 2021.
New required tracker field
Starting with codebeamer Connector 2.3.1, all codebeamer trackers used as an export target need to also have an additional custom field named "my_uml_type" (without the quotes).
For more info, please refer to this page: Configure a codebeamer Tracker for Export of EA Elements
codebeamer Version Restriction
The versions 2.4.x of the EA Connector for codebeamer only support codebeamer version 10 and higher. Also, codebeamer server versions 21.09 and higher are only compatible with connector versions 2.4.0 and higher.
The minimum supported version of codebeamer is version 9.5. If you want to use codebeamer version 9.5, please use the older version 2.0.5 of the EA Connector for codebeamer: Release 2.0
For more information on the compatibility of codebeamer / Retina versions and versions of the connector, please refer to the System Requirements.
|Support for codebeamer X version 4.1||The release 2.4.1. now officially supports version 4.1 of codebeamer X.||2.4.2|
|Performance improvement for API calls||Due to an optimization of REST API calls, the performance could be improved. With an active API Throttling, import / export could be sped by almost 50%.||2.4.2|
|Support for codebeamer 21.09 (codename "Emma")||Starting with codebeamer connector release 2.4.0, we officially support codebeamer 21.09 (codename "Emma"). This also includes support for active API Throttling, which unfortunately breaks previous versions of the codebeamer connector completely.||2.4.0|
|Fields with user reference breaks loading of codebeamer model||If you had a tracker with fields that reference users, groups or roles, every codebeamer operation fails (import or export) because of a faulty loading of those reference fields.||2.4.3|
|Navigation hyperlinks for exported diagrams exported do not work||The navigation hyperlinks created in codebeamer for diagrams that were exported with "Export Diagrams to codebeamer" were not created properly. With this fix it is possible to achieve a bi-directional navigability between requirements which were imported to EA and their contained diagrams that were exported to codebeamer.||2.4.2|
|Exception on export of HTML tags in the description||Further fixes were necessary to ensure HTML tags are exported correctly to codebeamer. The mechanism is now also more robust in general, and will no longer lead to failing exports. Instead, the description text will now read "Error while parsing description" in case of further errors in the conversion algorithm.||2.4.1|
|Models with duplicate GUIDs||Enterprise Architect models may contain duplicate Global Unique Identifiers (GUIDs) - which, in theory, shouldn't be possible. The handling of such models is now more robust, and they will hopefully no longer lead to bizarre and unhelpful error messages.||2.4.1|
|Open ID Connect Authentication Refresh||The Open ID connect authentication token is now also automatically refreshed during exports. This ensures that long-running exports are not aborted because of authentication issues.||2.4.0|
|Broken large exports||Exports with over 500 elements no longer break the assignment of elements to their respective parents. This also fixes the incorrect change numbers shown on such exports.||2.4.0|
|Whitespaces in server urls||Whitespaces at the beginning and the end of server URLs entered in the configuration dialog are now properly trimmed.
There's also an immediate verification of the format of the URL now.
|Immediate server configuration changes||Changes to the default server configuration are now immediately applied after saving. Previously, you needed to click "Set as default" afterwards or restart your Enterprise Architect instance.||2.4.0|
|Config file formating||The config-file in the AppData folder is now properly formatted, which makes it more easily readable.||2.4.0|
|Peformance with active API throttling||codebeamer 21.09 introduces API throttling, which is active by default (for more details, please refer to the official documentation here: https://codebeamer.com/cb/wiki/17380873#section-Default+value). This severely negatively impacts the performance when exporting data.||2.4.x|
|Colors in formatted notes of exported elements are not supported||If elements from EA with formatted notes (bullet lists, numberings, bold text, etc.) are exported, colors are not considered in the description field of the tracker items in codebeamer. This is due to a restriction in codebeamer.||2.4.x|
|Delete detection during import||When importing elements from codebeamer to EA, the connector does currently not detect elements that were removed in codebeamer. In a future release this feature will be implemented similiar as the "Obsolete Items" mechanism for exports.||2.4.x|
|Order of elements not considered during export||The current release does not replicate the order of elements from EA in codebeamer.||2.4.x|