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 Architect.
Steps to Reproduce
- Add an element with a Custom Property in Prolaborate
- In EA, the element will be visible but the Custom Property is not added as a Tagged Value
Workaround
Product Team's input was as follows,

- This is a known Behavior. This issue does not belong to Prolaborate it's a PCS-related issue. As of now, this is the expected behavior until we get a fix from PCS.
- Currently we cannot overcome this because of the limitation we have API (PCS).
- Hence to overcome the challenge we have made the workflow that suits the available API actions. We have already requested an API call for this specific scenario.
So, there is no workaround for this issue.

Email Response
Hello <Customer>,
We agree this is an issue. Currently we cannot overcome this because of the limitation we have API (PCS).
Hence to overcome the challenge we have made the workflow that suits the available API actions. We have already requested an API call for this specific scenario. We will keep you posted about the progress.
If you have any questions or need further assistance regarding this, please feel free to reach out.
Reference
Ticket ID: #5876
Subject: Adding elements and taggedvalues
Department: Prolaborate Support
Q2. Creating New Elements from Prolaboarte (Custom MDG)
Description
Customer was testing the creation of new Elements in Prolaborate and I note it seems to be able to create elements from custom MDGs.
When they try to create new Elements I get the following options:
Which are stereotypes defined in a custom profile in a custom MDG.
But after creating the Element, we noted that the predefined tag values in the stereotype are not created in the database, so the element looks like this in EA after creation in Prolaborate:
But if I create a new Element from EA, it looks like this:

when created from Prolaborate it creates the tag value groups but no the tag values. And there is a difference also in the stereotype definition, which you can see in the Browser:
The question is: is this an issue of Prolaborate? or is it a OSCL (PCS) bug?
First Response

From our side
To further investigate the issue with tag values of elements created In Prolaborate not being properly reflected in EA, we kindly request the following information from you:
1. Prolaborate version: Please provide the version number of the Prolaborate instance you are currently using.
2. EA version: Please provide the version number of the Enterprise Architect you are using.
3. DB version: Please provide the version number of the database you are using with Prolaborate and EA.
With this information, our technical team will be able to analyze the issue more effectively and provide you with appropriate assistance.

From Customer Side
Included the Technical Data :
- Prolaborate version: 4.5.0.186 (also happens in 4.4.2.11)
- Enterprise Architect version: 16.1.1627 64 bits
- Database: SQLServer 2019
- EA database schema version: 1558
- Pro Cloud Server 5.0.105 64 bits
Resolution
After investigating with our technical team, we have found that currently, the supported modelling frameworks for element creation in Prolaborate are UML, SysML 1.5, ArchiMate 3.1, and BPMN 2.0.
You can also refer to the documentation [here], which also mentions the supported modelling frameworks.
Given the current limitations, we would recommend creating the elements for your custom MDG directly in Enterprise Architect (EA).
Reference Ticket
Ticket ID: #5519
Subject: Creating new Elements from Prolaborate (custom MDG)
Department: Prolaborate Support
URL: https://desk.zoho.com/agent/sixthforcesolutions/prolaborate-support/tickets/details/759413000020206191