Known Issues - Modeling Language
Q1: Issues with SysML 1.4 and 1.5 MDG file in Prolaborate
Description
The customer was facing issue with SysML stereotype in Prolaborate. Some tagged values are not displayed for particular SysML stereotypes properly.
Issue
Issues with SysML MDG file:
DesignConstraint ---- Stereotype Not Available for Prolaborate SysML1.5
FunctionalRequirement ---- Stereotype Available but Tagged Values Not Available for Prolaborate SysML1.5
InterfaceRequirement ---- Stereotype Available but Tagged Values Not Available for Prolaborate SysML1.5
Possible reasons
If the customer is using the previous version of SysML MDG file then the above issue could happen.
Initial Example Draft
Hi [Customer Name]:
Thank you for reaching out to Prolaborate Support.
1. Share us the SysML MDG file that you are currently using in your Prolaborate environment.
2. Share us the screenshots of the issue you are encountering.
Thank you for your cooperation.
Steps to be Taken
Compare the customer shared SysML with our latest SysML file. If you found any issue (as mentioned above) with their file, please use the below example draft and ask them to use the attached latest SysML file in this article.
Example Draft after the analysis
Hi [Customer Name],
Thank you for your patience.
Please find the updated SysML MDG file attached to this email. Kindly update this SysML file on the SysML MDG you already have in your Prolaborate environment, check on the issue you had with the element (information is not displayed correctly in the element overview page and in the property window, designConstraint: The element is not part of the modelling), and let us know the outcome.
Click "Edit", choose the SysML file we provided and click the Update button.
Note:
We have updated the MDG file with the missing tag values. If the new MDG is updated on top of the existing one, you can manually drag and drop the tagged values to add them to the form designer in the existing profiles. To overcome this:
1. Remove the existing MDG and reupload the new MDG to have the attributes grouped. [or]
2. If the new MDG was updated over the previous version, a new profile needs to be created for it to group automatically.
Thank you for your understanding.
Reference
Ticket ID: #7175
Subject: Prolaborate V4 Installer- INHECO GmbH
Department: Prolaborate Support
Related Articles
Known Issues - Jama Integration
Pick List Items are missing in EA thick client Description Picklist values are missing in EA thick client. When accessing from EA, the system integration reads picklist information as an empty string. Picklist in Jama Picklist in Enterprise Architect ...Known Issues - Attributes
Q1: Tagged Values not displayed in Color Configuration page Description The color configuration for a custom MDG is not displaying all the tagged values from the stereotypes. The customer is using Prolaborate V4.4.1.33. Steps Taken - The issue can be ...Known Issues - Adding Elements in Prolaborate
Q1. Adding a new element with Custom Properties does not include the Properties in EA Description The elements added in Prolaborate have custom properties in them, but they are not included as a tagged value in the model when viewing from Enterprise ...Known Issues - Charts
Q1: Roadmap Displaying EA GUID Values When Grouping by RefGUID Property Description The customer reports that when grouping the roadmap items by a property of type 'RefGUID', the roadmap shows the EA GUID values of the referenced elements. We were ...Known Issues - Migration
Q1: "Invalid License" or "License Missing" error after migrating Prolaborate to a new server Description The Prolaborate and Pro Cloud Server is migrated to a new Server setup. After logging into Prolaborate, an error message appears saying "Invalid ...