Prolaborate Collaboration – FAQs and Troubleshooting Guide

Prolaborate Collaboration – FAQs and Troubleshooting Guide

1. Tagging and Notifications in Prolaborate Discussions 

Q1: Why can’t Read-only users be tagged in Prolaborate discussions? 

  • Users require Collaborate access to participate in discussions (tagging, commenting). 

  • Read-only users are limited to viewing artifacts to prevent unintended modifications. 

Q2: Why don’t users receive email or push notifications when mentioned in discussions? 

  • Ensure email server configurations are correct in Prolaborate. 

  • Push notifications appear in-app and need an active session. 

Reference: Ticket ID #9677 
View Ticket 
Tags: Discussion, Tag user, Read-only access 

Shape 

2. Prerequisites for Enabling Open Community Access (OCA) 

Q: Do we need to enable Public Share to enable OCA? 

  • Yes, from Prolaborate version 5.4, Public Share must be enabled first for OCA to work. 

Reference: Ticket ID #17944 
View Ticket 
Tags: OCA, Public Share, Repository Settings 

Shape 

3. Repository Share Button Greyed Out After Upgrading to Prolaborate 5.5 

Q: Why is the Repository Share button greyed out post-upgrade? 

  • Disable and re-enable the OCA option in Repository Settings to refresh configuration. 

Reference: Ticket ID #22339 
View Ticket 
Tags: Prolaborate 5.5, Repository Share, OCA, Upgrade 

Shape 

4. Package Pages Not Showing Children Tables in Public Links 

Q: Why are children tables not displayed in Public Links? 

  • Currently, Public URLs show only package-level info. 

  • Use Private URL or Browser URL for full details until a future update addresses this. 

Reference Tickets: #14344, #15174 
View Ticket #14344 
View Ticket #15174 
Tags: Package Pages, Public Links, Children Tables 

Shape 

5. How to Enable List Edit Capability in Prolaborate 

Summary: 
Unable to edit a package due to locked root folders. 

Troubleshooting Steps: 

  1. Log in using credentials of the user/group who applied the lock in EA. 

  1. Request the locking user to remove the lock by selecting “No lock” in EA. 

  1. Once unlocked, enable the “Edit” toggle in Prolaborate. 

Reference: Ticket ID #11348 (Scottish Power Ltd) 
View Ticket 
Tags: Edit Package, Lock Root Folder 

Shape 

6. Basic Properties Not Visible When Reviewing Connected Elements 

Issue: 
Connected Elements not visible under Basic Properties. 

Resolution: 

  • Import or configure the MDG file into the modeling language. 

  • Connector names are visible in the Traceability tab. 

Reference: Ticket ID #15135 (Wesfarmers Chemicals, Energy & Fertilisers) 
View Ticket 
Tags: Connected Elements, Traceability, Connector Names 

    • Related Articles

    • FAQs - Prolaborate Installation

      Q1:Can you suggest how we may configure Prolaborate using https and port 443. Do you have any links to documentation? Answer You can configure the Protocol and Port settings from Prolaborate Management typically located in C:\Program ...
    • FAQs - Prolaborate Management

      Q1: The Prolaborate is hosted on the server, and now Prolaborate Management is not opening, which was working fine previously. Also, error messages are thrown; all the related files are present in the folder without any change to the file name. ...
    • FAQs - Discussions

      Q1: I wish to opt out of the discussion threads related to the Package 1 and be part of Package 2 only. Please share the steps to achieve the same. A:If your aim is just to be free from the notifications of discussions, you can enable the ...
    • FAQs - Microsoft Teams Integration

      Q1. We are not able to confirm if any data is collected while using MS Teams Plug-in for Proloborate. If so, what data do you collect? Answer The data stored from MS Teams do not contain Personally Identifiable Information (PII), However, MS Teams ...
    • Prolaborate Analyzer - Known Issues & Troubleshooting Guide

      Images Exported from Analyzer are not Clear Description: Images exported from Analyzer with a high number of nodes are not clear. This is a known bug in Prolaborate V5.2. Reference Ticket(s): #8374, Prol-Bug3543 Workaround: No workaround mentioned. ...