Q1:Prolaborate Composite Diagram Feature
Opening Property Window Instead of Displaying Diagram
Description
When a diagram in EA contains an object that is itself a diagram, double-clicking on that element opens the nested diagram. However, in Prolaborate, double-clicking on the element opens the extended properties view instead. The user must then take several steps to open the nested diagram in Prolaborate.
Possible Reasons
It's crucial to verify that the EA Schema is up to date because using an outdated schema in the EA Database could lead to problems.
Additionally, it's important to recommend the customer to upgrade their PCS to the latest version, as issues may arise when using PCS 4.x.
Workaround
The issue of the open sub-model has been resolved by utilizing a repository with the most up-to-date schema, along with Prolaborate version 4.4.1 and PCS 5.1.126 (32-bit).
Note
This troubleshooting process is included here because the customer was using EA 15. After upgrading PCS, we recommended using a native connection, but the customer encountered an "XML incomplete" error. To address this issue, we advised the customer to set up an ODBC connection to their Oracle database. The following steps explain how to create an ODBC connection using an Oracle database in PCS.
Step 1:Click the Add drop-down in PCS and select the ODBC.
Step 2:Click the OBDC data source in the System DNS area using the option Add you can add a new Data Source in ODBC.
Step 3:Click the Oracle drive in the data source list.
Step 4:This will open an ODBC drive configuration dialog box. In there, fill the respective field with Oracle db information.
Step 5:After successfully adding the data source in ODBC, you can use the Microsoft OLE DB Provider for ODBC drivers.
Step 6:This will open the connection dialog box. In there, you can select the added data source in ODBC and fill in the credential details. After that, test the connection. It will pop a successful message if it can add the model as ODBC connection in PCS.
If the issue persists after follwoing the reach out to L2 for further assistance.
Reference
Ticket ID: #4713
Subject: How to open diagram rather than property window
Department: Prolaborate Support
The customer reported that they are encountering GUID values instead of the actual tag value information in the Property window.
Possible Reasons:
The issue of showing GUID values in the property window has been confirmed as a bug starting from Prolaborate version 4.4.1.38. This bug has been fixed in Prolaborate version 5.2.
The latest MDG may not be updated in the Modelling Language and may not properly configure the tag values in the MDG diagram.
Reference Tickets
First response – Troubleshooting Steps
Hi [Customer Name],
Thank you for reaching out to Prolaborate support.
To address the issue of GUID values appearing instead of tag values in the Property window, kindly follow these troubleshooting steps:
1. Update to the latest MDG in Prolaborate and let us know if this resolves the issue.
2. Please note that the GUID value issue is a bug starting from Prolaborate version 4.4.1.38. This issue has been resolved in Prolaborate version 5.2. If you are using a Prolaborate version below 5.2, kindly update to the latest version to resolve the issue.
3. If the issue persists after updating to Prolaborate version 5.2, we kindly request you to re-upload the latest MDG in the Modelling Language, as this may fix the issue.
Please perform these steps and let us know if the issue persists, along with a screenshot illustrating the problem for further investigation.
If you have any questions or concerns let us know.
1. Updating to the latest version of Prolaborate will fix the issue.
2. Re-uploading the MDG after updating to the latest version may also fix the issue.
Q3:Token limit reached within the Prolaborate repository.
Issue
The "Token limit reached" error occurs in Prolaborate repository even though the user possesses an unlimited license for the repository.
Description
The customer reported the absence of a personal project QEA file located in the directory C:\Users\ea-user\Documents\POP Internal Transfers.qea. Additionally, they reported missing files that were previously uploaded to the EA Cloud environment.
Possible Reason
- The issue you facing is indeed a bug in Prolaborate it occurs when the PCS version is 5.1.128
- When the 'Restrict access to Windows & OpenID users only' option is enabled in Global options in EA.

- In the Pro Cloud Server the option "Require a secure and authenticated connection" is enabled

If any of the two option enabled the token limit reached issue will occur in Prolaborate.
Workaround
When the 'Restrict access to Windows & OpenID users only' option is enabled in Global options in EA, please follow the bellow steps for resolve the issue.
As a temporary solution, we recommend the following steps to resolve the PCS token limit reached issue in Prolaborate if the "Restrict access to Windows & OpenID users only":
Step 1: Access EA and cloud-connect the model to check if there is a user login name "admin." If not, please create one and grant all the permissions to this user.
Step 2: Next, navigate to Prolaborate, edit the model, and use the "admin" User ID and its password to reconfigure the model.
Email Draft
Hi [Customer name],
Thank you for the email
The issue you facing is indeed a bug in Prolaborate it occurs when the PCS version is 5.1.128. It has been added to our product backlog and will be addressed in the upcoming version of Prolaborate. Rest assured, we'll keep you updated on any developments related to this matter.
The "PCS Token limit reached" error occurs in Prolaborate under the following conditions:
- When the 'Restrict access to Windows & OpenID users only' option is enabled in Global options in EA.

- In the Pro Cloud Server the option "Require a secure and authenticated connection" is enabled.
As a temporary solution, we recommend the following steps to resolve the PCS token limit reached issue in Prolaborate if the "Restrict access to Windows & OpenID users only":
Step 1: Access EA and cloud-connect the model to check if there is a user login name "admin." If not, please create one and grant all the permissions to this user.
Step 2: Next, navigate to Prolaborate, edit the model, and use the "admin" User ID and its password to reconfigure the model.
Step 3: Please follow these steps for the Toke limit-reached models and let us know the outcome.
If you have any other questions or concerns, please don't hesitate to reach out to us.
Reference
Ticket ID: #9775
Subject: Token Limit Reached
Department: Prolaborate Support