/
Syndeia 3.6 SP2 - Improvements

Syndeia 3.6 SP2 - Improvements

Intercax is excited to announce the release of Syndeia 3.6 Service Pack 2 (3.6 SP2).

In this section, the availability, downloads, and the list of improvements in Syndeia 3.6 SP2 are presented.

Availability

  1. Syndeia 3.6 SP2 is available for download starting May 6, 2025.

  2. Syndeia 3.6 SP2 includes:

    1. Syndeia Cloud 3.6 SP2, including Syndeia Web Dashboard

    2. Syndeia Cloud REST API 3.6 SP2

    3. Syndeia local clients 3.6 SP2

      1. Syndeia MagicDraw/Cameo plugin

      2. Syndeia Rhapsody plugin

      3. Syndeia Standalone

Downloads and Installation

  1. Existing Syndeia users with an active subscription can request downloads for Syndeia 3.6 SP2 by opening a request on our helpdesk.

  2. For Syndeia local clients, follow the instructions under the Installation sections.

    1. MagicDraw/Cameo plugin - Installation - Syndeia for MagicDraw | Cameo

    2. Rhapsody plugin - Installation - Syndeia for Rhapsody

    3. Standalone - Installation - Syndeia Standalone

  3. For Syndeia Cloud, follow the instructions here: Deployment & Maintenance

    1. New users, who are downloading Syndeia for the first time, should directly get started with Syndeia Cloud 3.6 SP2. Refer to: Automated Deployment

    2. Users working with Syndeia Cloud 3.5 SP2 or 3.6 or 3.6 SP1 can upgrade to 3.6 SP2. Refer to the following page for upgrade paths: Upgrades and Migration

Improvements

1. Integration Improvements

Syndeia Cloud 3.6 SP2 includes the following improvements and bug fixes for integrations.

1.1. Confluence

Syndeia Cloud 3.6 SP2 includes the following improvements for the Confluence integration.

1.1.1. Syndeia User Guides were updated with instructions to connect to Confluence Server or Data Center repositories. This was only a change in the documentation. Syndeia has always supported connecting to both Confluence Cloud and Confluence Server (Data Center). Links to the specific pages of the User Guide that were updated are listed below.

1.1.2. Syndeia Cloud REST API endpoints for Confluence search using CQL were returning artifacts with incorrect external id and key fields. This bug has been resolved.

  • Specific bug: SYN-4994

 

1.2. DOORS NG (DNG)

Syndeia Cloud 3.6 SP2 includes the following improvements for the DNG integration.

1.2.1. The GET artifact related endpoints in the Syndeia Cloud DNG microservice were returning a 404 (Not Found) error response instead of 401 (Unauthorized) error response when a session/token times out. This bug has been resolved.

  • Specific bug: SYN-4394

1.2.2. DNG Jazz services may return the list of projects on a DNG server without requiring credentials, even though the contents of the projects cannot be accessed without validated credentials. To avoid this confusion, Syndeia 3.6 SP2 includes an additional security check - if the credentials are not provided or are invalid, the list of DNG projects is not visible in Syndeia Dashboards and not returned via Syndeia Cloud DNG API.

  • Specific improvement: SYN-2764, IHD-2387

1.2.3. Custom mapping tutorials for DNG were updated to provide examples of adding artifact types specific to a component and stream in CM projects when creating custom SysML - DNG mappings. Refer to the following tutorials that were updated.

 

1.3. GENESYS

Syndeia Cloud 3.6 SP2 includes the following improvements for the GENESYS integration.

1.3.1. The operation name for GET GENESYS repository by key endpoint in the Syndeia Cloud REST API was misspelled due to which it was not showing up correctly in language-specific clients (e.g. Python, Typescript, Java, Scala) generated for Syndeia Cloud REST API (Open API spec). This issue has been resolved.

  • Specific bug: SYN-5019

 

1.4. GitHub

Syndeia Cloud 3.6 SP2 includes the following improvements for the GitHub integration.

1.4.1. In some scenarios, a paginated response for GitHub issue (artifact) search endpoint in the Syndeia Cloud GitHub API was returning a 500 (Internal Server Error). This issue has been resolved.

  • Specific bug: SYN-5207

1.4.2. Browsing GitHub issues with an empty body in the Syndeia Web Dashboard was resulting in an error notification . This issue has been resolved.

  • Specific bug: SYN-4987

 

1.5. Jama

Syndeia Cloud 3.6 SP2 includes significant improvements for the Jama integration. Syndeia provides a comprehensive suite of digital thread capabilities for Jama, and in 3.6 SP2 this has been expanded further.

1.5.1. Diagram generation and sync - Users can now generate and sync diagrams from Cameo to Jama in the Syndeia Cameo plugin. This works for any type of diagram. A diagram is represented as a text item in Jama, and the diagram image is embedded in the description field of the text item, as shown in the screenshot below. In Syndeia, when an element is transformed from Cameo to Jama using default mappings or custom mappings, any diagram in the parent package or nested under that element or any other nested element will be generated as text items with diagram images in the description field. When a diagram is updated or new diagrams are added in Cameo and the model is synchronized from Cameo to Jama, the text items in Jama are updated or added to reflect the changes. There is a setting to turn this feature on/off based on user preference, as described in the tutorial linked below.

A new step-by-step tutorial has been added for end users to try out this capability. See here for details - Exercise 7.10 - Jama Diagram Generate & Sync.

  • Specific improvements: IHD-827, SYN-4894, SYN-4895, SYN-4073, SYN-5101

image-20250502-220949.png
image-20250503-221742.png

1.5.2. Improved delete behavior and setting - Until Syndeia 3.6 SP1, when a nested artifact was deleted in Cameo and sync to Jama was performed, or vice versa, Syndeia would not delete the artifact on the target side of the sync but instead move it to the parent artifact. This behavior was also different when using custom mappings vs default mappings. In Syndeia 3.6 SP2, this capability has been improved and users are provided a setting (as highlighted below) to control the behavior.

  • If the Allow deletion setting is checked, then Syndeia will delete nested elements on the target side (Jama/Cameo) of the sync if they have been deleted on the source side (Cameo/Jama).

  • If the Allow deletion setting is unchecked (default), then Syndeia will not delete nested elements on the target side (Jama/Cameo) of the sync if they have been deleted on the source side (Cameo/Jama).

Existing tutorials for Cameo ↔︎ Jama synchronization have been updated to demonstrate this capability.

image-20250502-222013.png

  • Specific improvements: IHD-4603, IHD-4673, IHD-4615, SYN-4889, SYN-4899, SYN-5105

1.5.3. Improved handling of HTML text - Syndeia 3.6 SP2 includes improved handling of HTML text when generating and synchronizing between SysML ↔︎ Jama artifacts bi-directionally, as shown in the screenshot below.

Tutorial on SysML <-> Jama generation and sync has been updated to demonstrate the improved handling of HTML text. See here for details - Exercise 7.5 - Using SysML-Jama Mappings.

image-20250502-230458.png

  • Specific improvements: IHD-2689, IHD-4583, IHD-4644, IHD-4417, SYN-683, SYN-4758

1.5.4. Improved synchronization of SysML elements or Jama items that were moved - If an element structure (e.g. requirement specification) in SysML was used to generate a corresponding Jama item structure, or vice versa, Syndeia establishes persistent relations/connections between each SysML element and Jama item that users can browse in the Syndeia dashboards as part of the digital thread. When one of the SysML elements or Jama items is moved in the nested hierarchy, Syndeia still recognizes that the SysML element and Jama item are connected since it tracks their ids. However, when a user syncs this change (move operation) to the other side, Syndeia would generate a new artifact during sync until 3.6 SP1. This is because Syndeia allows a single element in a SysML element to be connected with multiple Jama items, and vice versa. In Syndeia 3.6 SP2, this capability of move and sync has been improved with an added setting for users to control the behavior.

As shown in the screenshot below, Syndeia 3.6 SP2 includes a Reuse existing connections setting. If this setting is checked and a SysML element (or a Jama item) is moved in the nested hierarchy and the users sync from SysML → Jama (or Jama → SysML), Syndeia will move the artifact on the other side to match the nested hierarchies between SysML and Jama. This allows end users to maintain a packaging and element structure in SysML in sync with Jama set with folders and items, and allow them flexibility to shuffle the element/item structure and sync to the other side.

  • Specific improvements: IHD-4637, IHD-4673, SYN-4901

image-20250502-232138.png

1.5.5. New tutorial for custom mappings with mixed artifact types - Syndeia 3.6 SP2 includes a new tutorial for mapping, transforming, and synchronizing SysML packages including nested sub-packages and element structures with Jama sets including nested folders, sub-folders, and item structures. Refer to the new tutorial here: https://intercax.atlassian.net/wiki/spaces/SYN36/pages/3945889801

  • Specific improvements: IHD-4853, SYN-5100

1.5.6. There was an issue noted in the Syndeia local Dashboard (Cameo and Rhapsody plugins) dialog where Jama artifact (item) types are added or updated. Switching from one artifact type to another artifact type did not refresh the table of attribute definitions (item fields). This issue has now been resolved.

  • Specific improvements: SYN-4816

1.5.7. The Jama artifact search endpoint in the Syndeia Cloud Jama API has been improved. The artifact search endpoint is POST /external/jama/{repoKey}/artifacts/search. The body of the POST request allows users to search by item ID, document key, or content. When content is selected as an option, users can also specify release, createdDate, modifiedDate, lastActivityDate, sortBy, and includeWildcard as optional filtering parameter for a comprehensive text-based search in Jama projects.

  • Specific improvements: SYN-5109

 

1.6. RESTful Integration

Syndeia Cloud 3.6 SP2 includes the following improvements for integrating RESTful repositories, i.e. any enterprise service or tool that provides a REST API.

1.6.1. There was an issue found in the Syndeia local clients (Cameo/Rhapsody plugin) when connecting with RESTful repositories that require dynamic token-based authentication. The token was not refreshing correctly after a period of inactivity. This issue has now been resolved.

  • Specific improvements: SYN-4848

1.6.2. There was an issue found in the Syndeia Web Dashboard when configuring a POST request with a JSON object as the request body. This issue has been resolved.

  • Specific improvements: SYN-4823

 

1.7. SysML v2

Syndeia Cloud 3.6 SP2 includes the following improvement for SysML v2 API (Systems Modeling API and Services 1.0) standard.

1.7.1. Support for Basic Auth from SysML v2 API Providers - Syndeia Web Dashboard, Client Dashboard, and Syndeia SysML v2 API now support basic auth when connecting to SysML v2 API provider repositories. This was verified to work with Cameo and Teamwork Cloud 2024x R2 (EEP edition with SysML v2 API support). In addition, Syndeia has been verified to work with SysML v2 API reference implementation (OMG) and SysON.

Syndeia was the first commercial tool in the market to support the SysML v2 API (since 2021). Since then, each Syndeia release has been conformant to the latest release of the SysML v2 language and API specifications as they were going through the submission and finalization phases. SysML v2 language and API are scheduled to be adopted as official OMG specifications in June 2025. Syndeia 3.6 SP2 already supports the submitted specification that will be adopted as the official standard. Syndeia 3.7 release later this year will include significant updates for building and managing digital threads with SysML v2. Syndeia’s digital thread capabilities can be used with any SysML v2 API provider.

  • Specific improvements: SYN-5157, SYN-5176, SYN-5150

For details, please refer to the following demo videos:

1.7.2. An issue was found with the Digital Thread Explorer with SysML v2 artifacts. If an artifact in another repository (e.g. Teamcenter) was expanded and an inter-model relation from/to a SysML v2 artifact was shown, then subsequently expanding the SysML v2 artifact to fetch intra-model relations (relations within SysML v2 model) was not working. This issue has now been resolved.

  • Specific improvements: SYN-4999

 

1.8. Teamcenter

Syndeia Cloud 3.6 SP2 includes the following improvement for Teamcenter.

1.8.1. Syndeia 3.6 SP2 includes improvements in mapping, transforming, and synchronizing SysML element structure with Teamcenter item structures with mixed item types, such as an Assembly item BOM including multi-nested Parts, Equipment, and Document items at multiple levels in the BOM hierarchy.

  • Specific improvements: IHD-4358, IHD-4783, SYN-4760

1.8.2. A new tutorial for custom mapping of SysML blocks with value properties to Teamcenter items and properties has been added. Refer to the new tutorial here: https://intercax.atlassian.net/wiki/spaces/SYN36/pages/3857317907.

  • Specific improvements: SYN-5085

1.8.3. The Syndeia Cloud Teamcenter integration now explicitly defines the location of the activeClients.properties file that is generated automatically by Teamcenter SOA services to keep track of all the active client connections. The file is automatically deleted by the Teamcenter SOA services when all the connections are signed out. This file is now set to be at the same location as the Syndeia Cloud Teamcenter logs, e.g. /opt/icx/syndeia-cloud-current/teamcenter-impl-<version>/logs/

  • Specific improvements: SYN-4981

1.8.4. An issue was noted with SysML → Teamcenter transformation with cyclic relations and structure in the SysML model. This issue has been resolved.

  • Specific improvements: SYN-4446

 

1.9. Teamwork Cloud

Syndeia Cloud 3.6 SP2 includes the following improvement for Teamwork Cloud.

1.9.1. Syndeia 3.6 SP2 improves user session management for Teamwork Cloud repositories, especially for cases where a user is simultaneously connected to multiple Teamwork Cloud repositories of the same version (e.g. dev, uat, prod) or different versions (e.g. 2021x, 2022x, and 2024x) from the Syndeia Dashboard.

  • Specific improvements: SYN-5154

1.9.2. An issue was found with the Teamwork Cloud search capability on the Syndeia Web Dashboard wherein multiple sign in calls were being made from the search tab. This issue has now been resolved.

  • Specific improvements: SYN-5204

1.9.3. An issue was found with the Teamwork Cloud search capability on the Syndeia Web Dashboard wherein the project (resource) ID was included twice in the input body of the API request. Even though the endpoint was working as expected, the extra field for resource id was not needed. This issue has been resolved.

  • Specific improvements: SYN-5184

1.9.4. An issue was found with the Swagger doc (Open API spec) for Syndeia Teamwork Cloud API endpoint to GET containers by external key. This endpoint also requires an additional query parameter type.externalKey which should be set to Resource to fetch Teamwork Cloud projects or Workspace to fetch Teamwork Cloud workspaces. The type.externalKey query parameter was missing in the Open API spec for the GET containers by external key endpoint. As a result, language SDK clients (e.g. Python, Java, Scala) did not include this argument in the mapped functions. This issue has now been resolved.

  • Specific improvements: SYN-5134

1.9.5. An issue was found with the Swagger doc (Open API spec) for Syndeia Teamwork Cloud API endpoint to GET artifact by external key. This endpoint also requires an additional query parameter container.externalKey which should be set to the id of the Teamwork Cloud project containing the artifact. The container.externalKey query parameter was missing in the Open API spec for the GET artifact by external key endpoint. As a result, language SDK clients (e.g. Python, Java, Scala) did not include this argument in the mapped functions. This issue has now been resolved.

  • Specific improvements: SYN-4995

 

1.10. VOLTA

Syndeia Cloud 3.6 SP2 includes the following improvement for VOLTA.

1.10.1. Users can now view and search for Dataset and Study artifacts in the VOLTA repository tree in the Syndeia Web Dashboard (screenshot below) and Client Dashboards.

  • Specific improvements: IHD-4310, SYN-4716, SYN-4952, SYN-4996

image-20250505-025634.png

1.10.2. An issue was found for VOLTA Dataset artifacts on the Syndeia Web Dashboard. Right clicking on the Dataset and selecting the More Details menu did not open the Dataset in VOLTA. This issue has now been resolved.

  • Specific improvements: SYN-4998

 

1.11. Windchill

Syndeia Cloud 3.6 SP2 includes the following improvement for Windchill.

1.11.1. An issue was found with the Windchill repository tree in the Syndeia Client Dashboards. If a new container (product, project, or library) was added in Windchill while the Client Dashboard was open, and the Windchill repository is refreshed in the Client Dashboard, the new container was not showing up. This issue has been resolved.

  • Specific improvements: SYN-4858

1.11.2. An issue was found in the generation of Part BOM structure in Windchill from SysML block structure for Windchill 12.1.2. In some cases, the part occurrence relationship in the BOM was not generating. This issue has been resolved.

  • Specific improvements: SYN-5017

2. Syndeia Dashboard Improvements

2.1 Syndeia Web Dashboard Improvements

Syndeia 3.6 SP2 includes the following improvements in the Syndeia Web Dashboard.

2.1.1. There was an issue found in the Syndeia Web Dashboard when viewing inter-model relations in the Relations tab for a selected artifact in the Tree View. The delete button (trash icon) next to the relation was malfunctioning for the following integrations: Teamcenter, GENESYS, DS-CR, and DS-E3. This issue has now been resolved.

  • Specific improvements: SYN-4923

2.1.2. There was an issue found in the Digital Thread Dashboard when right-clicking and opening a menu or sub-menu in a new browser tab. This issue has been resolved.

  • Specific improvements: SYN-4781

2.1.3. An issue was found in the form for creating a native/local User in Syndeia Cloud (non LDAP or SSO). The username field was allowing spaces which it should not have. This issue has been resolved.

  • Specific improvements: IHD-4626, SYN-4867

2.1.4. An issue was found in the Digital Thread Explorer where some of the artifact nodes were not showing the correct repository-specific colors if a relation was created for the first time from/to artifacts of that type. Further, expanding those artifacts was not fetching the intra-model relations correctly for some edge cases. This issue has been resolved.

  • Specific improvements: SYN-4834, SYN-4565, SYN-4580

2.2 Syndeia Client Dashboard Improvements

Syndeia 3.6 SP2 includes the following improvements in the Syndeia Client Dashboards, i.e. Syndeia Cameo / Rhapsody plugin dashboards.

2.2.1. The Settings tab in the Syndeia Client Dashboard now includes a Connection Timeout setting under Syndeia Store Settings. The default value of 30 seconds can be changed by end users. This setting is used by the Syndeia Client when communicating with Syndeia Cloud server and with any integrated repository, such as Jira, Teamcenter, Jama, GitHub, and others.

  • Specific improvements: SYN-4734, IHD-4303

image-20250504-164246.png

2.2.2. Improvements in the Syndeia Client Dashboard startup and user response were made when loading valid repositories that have gone offline and are not reachable.

  • Specific improvements: SYN-5015

3. Syndeia Cloud API & Infrastructure Improvements

Syndeia 3.6 SP2 includes the following general improvements in the Syndeia Cloud REST API, beyond the API improvements done for specific integrations, as described in section 1 above.

3.1. The Swagger doc (OpenAPI specification) was missing credential-related parameters for source and target repositories in the following endpoint: POST digital-threads/{digitalThreadKey}/relations/reference. As as result Syndeia API language SDKs (e.g. Python, Java, Scala, and Typescript) were also missing those parameters from the generated functions. This issue has been resolved.

  • Specific improvements: SYN-4957

3.2. Syndeia 3.6 SP2 includes a new Syndeia Cloud Log Aggregation Tool, a utility designed to assist in collecting and preparing log files from your Syndeia Cloud deployment for analysis or support purposes. It automatically gathers logs from various components of the SC-stack (Cassandra, Kafka, Zookeeper, JanusGraph, and Syndeia Cloud microservices), sanitizes sensitive information, and optionally compresses the logs for easier sharing. Learn more here: https://intercax.atlassian.net/wiki/spaces/SYN36/pages/3995697167.

  • Specific improvements: SYN-4656

3.3. An issue was found in the JSON schema for the User entity in the Open API specification. As a result, the JSON response from some of the endpoints that return User information did not match the JSON schema. This mismatch issue has now been resolved.

  • Specific improvements: SYN-4904

3.4. An issue was found with Syndeia Cloud service responses for integrations (e.g. Teamcenter, Jama) when sending rapid requests with invalid credentials that results in 401 (Unauthorized) or 403 (Forbidden) error codes. This issue has been resolved.

  • Specific improvements: SYN-4849

4. Syndeia Licensing

Syndeia 3.6 SP2 includes the following improvements and updates related to licensing.

4.1. Syndeia Cloud License Deployment - Syndeia 3.6 SP2 introduces a change in license deployment for Syndeia Cloud. A valid license pointer file (for floating licenses) or a node-locked license file must be included with Syndeia Cloud deployments. For more details, refer to the Pre-requisite sections for fresh deployments and upgrades at the links below.

4.2. Automated deployment of Intercax License Server (ILS) - Syndeia 3.6 SP2 includes a new, automated, and simplified deployment process for the Intercax License Server (based on RLM). Refer to the following link for details: https://intercax.atlassian.net/wiki/spaces/SYN36/pages/3330198748.

  • Specific improvements: SYN-5155

4.3. Improved license support for Apple Mac with M4 chips - An issue was noted with Syndeia Client (Cameo/Rhapsody plugins) license checkout from a floating license server for newer MacBook hardware with Apple M4 chip and Mac OS 15.x. This issue has been resolved.

  • Specific improvements: IHD-4832, SYN-5131, SYN-4751

5. Other Improvements

In addition to the specific improvements listed above, Syndeia 3.6 SP2 includes improvements related to the following.

  • Syndeia Documentation (this site)

  • Syndeia Cloud REST API Documentation - Swagger doc

  • Syndeia Cloud Deployment

  • Syndeia Web Dashboard usability

  • Syndeia Client Dashboard usability