Limitations

This release has the following limitations. We are continuously improving Syndeia by adding new features and removing known limitations. If any of these limitations are show-stoppers in your use of Syndeia, please let us know. We may have already resolved it and can provide you an interim build of Syndeia plugins before the next public release.

1. The compare and sync capabilities are not available for the model transform connections between SysML blocks and MySQL / Excel tables. As a result, users cannot compare / update the structure of MySQL / Excel tables (such add / remove columns) from SysML blocks, and vice versa.
    
2. NX/Creo -> SysML sync capability only updates mass properties and not part-assembly structure, features, or other CAD model parameters that may have been brought over to SysML.
    
3. Before invoking the compare / sync operations on connections via the Connection Browser or the Connection Summary tab, users must ensure that the repositories owning the elements participating in the connections are connected. If the repositories are not connected, the compare / sync operations may not automatically connect them, and eventually fail when trying to reach the elements in those repositories. Users can verify if repositories are connected by selecting the repositories in the Repository List Panel of the Repository Manager. This is particularly relevant when users attempt the compare/sync operations just after launching the Syndeia Dashboard. Syndeia is not connected to any repositories when the Syndeia Dashboard is launched for the first time. 
    
4. The undo (redo) operations performed in the SysML modeling tool does not affect the connections created in Syndeia. When users generate SysML model elements from repository elements via drag-n-drop operations in the Syndeia Dashboard and then perform undo (redo) operations in the SysML modeling tools, the newly generated SysML elements are removed (added back) but the connections created by Syndeia between these new SysML elements and the repository elements are not affected—they are not removed (or added back). So, users need to manually remove those connections after an undo operation. Alternatively, if users do not remove them, Syndeia will flag those connections as orphaned (since the SysML element is missing) when the project and Syndeia Dashboard is launched next time. Users can then remove those orphaned connections.
    
5. For Excel and MySQL, Syndeia does not support any additional value types beyond those listed in here and here.
    
6. The SysML --> DOORS-NG module structure synchronization is not supported because the DOORS-NG API does not allow creating modules or updating module structures. This will be supported when IBM DOORS-NG releases an updated DOORS-NG API.