Known Issue - Confluence
Q1. Failed connection in Confluence and Jira Integration
Description
Customer reported that they are unable to establish connection in both Confluence and Jira with Prolaborate. Customer shared the below screenshots of the configurations,
Resolution
The customer was using Prolaborate over an HTTP connection. So, the following response can be used in this scenario.
Please be advised that if the Confluence and Jira site is running on an HTTPS connection, Prolaborate must also be running over HTTPS. So, we would like to suggest that you consider hosting your Prolaborate over an HTTPS connection
You can refer to the below documentation to know more about updating the protocol in Prolaborate.
https://prolaborate.sparxsystems.com/resources/v4/documentation/upgrade-installation?=#protocolupdate
https://prolaborate.sparxsystems.com/resources/v4/documentation/upgrade-installation?=#protocolupdate
Reference Ticket
Ticket ID: #4790
Subject: Confluence & Jira Integration
Department: Prolaborate Support
URL: https://desk.zoho.com/agent/sixthforcesolutions/prolaborate-support/tickets/details/759413000017950236
Q2. Prolaborate Macro not working after the domain change in Confluence Cloud
Description
After changing the Confluence Page's Domain, the Prolaborate Macro doesn't work as expected.
Users see a blank page in the published pages.
When the admin tries to reconfigure the Prolaborate Macro, they'll get a blank screen on the Manage Apps page too.
Possible Reason
The possible Reason is obviously the domain change, but we might want to confirm how exactly the domain change was implemented in Confluence Cloud. Confirm whether the customer has migrated to a different Atlassian account. If not, get the detailed steps on how the domain was change was implemented.
The documentation [here] shows the typical way of changing the subdomain in Atlassian.
Remediation
[When the domain change was implemented as mentioned in the above document, the following actions can resolve the issue.]
Uninstall the existing Prolaborate Macro.
Reinstall the Prolaborate Macro from the Atlassian Marketplace.
Make sure the configurations are retrieved automatically and navigate to your Confluence Space to check if the diagrams appear again.
If the diagrams are not visible, please try the following steps to Regenerate the Security Token.
Navigate to Portal Settings > Integrated Applications - Access Management in Prolaborate.
Locate the Confluence application and click on Regenerate Security Token.
Once the security token is regenerated, navigate to the Manage Apps page in Confluence.
Click on the Edit option to replace the updated Client ID/Secret and click on Connect.
Email Response
[Requesting additional information on the Domain Change in Confluence Cloud]
Hi <Customer>
Thank you for being so patient.
We are currently investigating the issue you've encountered with the Confluence Macro and would greatly appreciate your cooperation in providing further details. This will help us to better understand the situation and provide you with prompt assistance.
Kindly provide us with the following information:
Regarding your previous correspondence, you mentioned a domain change from <Domain 1> to <Domain 2>. Could you please confirm whether this indicates a migration to a different Atlassian account?
If the domain change does not indicate a migration, we would appreciate any additional information you can provide regarding how the domain change was implemented. If possible, please provide detailed steps or any relevant procedures followed.
If you require any clarification or assistance in providing the requested details, please feel free to reach out to us.
[Providing Remediation to the customer]
Hi <Customer>
Thank you for being so patient.
We have investigated the scenario on our end and we suspect that the issue is due to the domain change. We kindly request that you try reinstalling the Prolaborate Macro in Confluence as mentioned below and provide us with the outcome.
<Remediation Steps as mentioned above>
Please try the troubleshooting steps as mentioned above and let us know if the issue persists. If you have any questions or need additional assistance regarding this, please feel free to reach out.
Escalation Contact
Product Team - Nabil Saleem, Syed Ansari
Reference Ticket
Ticket ID: #9975
Subject: RE: Prolaborate 4 in Confluence cloud
Department: Sparx Platform Support
URL: https://desk.zoho.com/agent/sixthforcesolutions/sparx-platform-support/tickets/details/759413000036834194
Change a product URL subdomain | Atlassian Support
Troubleshooting - Confluence Integration Issues
Q3. Repository is not displayed when using the plugin
Description
The customer reported that the Confluence plugin is not displaying their production repository. They are able to view their Demo Model but the production model is not there.
Resolution
Asked the customer to check if the “Include in Repository List” option is enabled in the Prolaborate Macro configuration page in Confluence.
But the customer replied that they failed to update the Client Secret in the Macro configuration page. After getting the latest Client Secret from Prolaborate, they entered it in confluence and the issue was resolved after that.
Response Sent
Hi <Customer>
Thank you for reaching out to Sparx Platform Support.
We are investigating the issue, and we will get back to you with an update at the earliest. In the meantime, could you please provide us with the below information to understand better and assist you promptly,
Please let us know if you are using Confluence Cloud/Server.
Share a screenshot or a short video of the issue you are experiencing.
Share the screenshot of the Prolaborate Macro configuration page like the one below,
4. Please make sure that the "Include in Repository List" option is enabled, if not please enable it and let us know the outcome.
5. Kindly follow the below steps to regenerate the security token from Prolaborate and update it in the Prolaborate Macro Configuration page in Confluence.
a. Navigate to Menu->Integrated Applications – Access Management
b. Click on the Regenerate Security Token option of your respective confluence application.
d. Now, navigate to your Prolaborate Macro Configuration page in Confluence, paste it in the Client Secret field and click Save.
Reference Ticket
Ticket ID: #5552
Subject: Question regarding Prolaborate/Confluence plug-in
Department: Sparx Platform Support
URL: https://desk.zoho.com/agent/sixthforcesolutions/sparx-platform-support/tickets/details/759413000020276602
Q4. Permission Denied in Confluence after upgrading Prolaborate
Description
The customer reported that he got a permission denied error when accessing public share links in Confluence and the iFrame links are not rendered after upgrading prolaborate to the latest version V4.4.2.11 and sometimes when used the widget URL the confluence show refused to connect.
Resolution
Scenario 1
- Asked the customer to check if the Domain Access Restrictions are enabled in Prolaborate. Customer replied that they were disabled.
- So, we requested the customer to share the logs, and the Prolaborate.json file.
- We found that the "AllowedFrameHost" and "AllowedExternalSource" fields were not updated as per the documentation. So asked the customer to update the following and revert to us.
"AllowedFrameHost": ["*"]
"AllowedExternalSource": ["*"]
- Customer confirmed that the Iframe links are rendered now but the permission denied errors with public share links persisted.
- The Customer later reported that the permission denied error was fixed after clearing the cache.
Scenario 2
1. In prolaborate Enabling the "public share" option in the repository settings allowed access to the Confluence share link without any issues.
2. Sometime the permission denied error is caused due to a cache issue This can be fixed by clearing the cache in the browser. This can be done by pressing (F12) on the prolaborate login page, this will open the Developer options. Now right-click on the reload page and click Empty Cache and Hard Reload. This will clear the stored State ID and resolves the issue.
Scenario 3
Refused to connect show in confluence is bug in prolaborate 4.4.2.11 when we use the widget URL in confluence it will show the refused to connect.
Initial Response
Scenario 1
Response 1
Hi <Customer>
Thanks for the update.
We would like to let you know that access to the Prolaborate application is blocked. This issue may arise when domain access restrictions are enabled, which restricts access to shared URLs from other applications.
Could you please navigate to Menu -> Manage Application Restrictions and provide us with a screenshot of the page?
Response 2
Hi <Customer>
Thank you for sharing the files with us.
As mentioned previously, access to the Prolaborate application has been restricted as per our investigation. We kindly request you update the "AllowedFrameHost" and "AllowedExternalSource" fields in the "Prolaborate.json" file as provided below:
"AllowedFrameHost": ["*"]
"AllowedExternalSource": ["*"]
Please make these changes and inform us of the outcome.
If you have any questions or concerns, please do not hesitate to let us know.
Basic Troubleshooting question Draft
Hi <Customer>
We have reviewed the provided link you shared and it seems to be functioning correctly on our end. However, in order to better understand and assist you with the issue you're experiencing, we kindly request the following information:
1. Could you please let us know the version of the Confluence server you are currently using?
2. Additionally, share the version of the Prolaborate macro that you have installed.
3. And share the Confluence log files. You can follow these steps to retrieve the log files:
Locate the log file location in C:\Program Files\Atlassian\Confluence\logs.
Compress the log file into a zip format and share it with us.
Please don't hesitate to reach out if you have any further questions or concerns. We're here to help!
Scenario 2
Hi <Customer>
Thank you for your patience.
Our team has identified the issue with the Diagram widget in Embed links as a bug and it will be addressed in the upcoming release. We will keep you posted on the updates.
As a workaround for this issue, we kindly request you try publishing the embed links directly from your diagram. You can refer to the video here describing steps on how to publish your diagram as an Embed link.
Please check and let us know if you have any questions.
Please check and let us know if you have any questions.
Reference Ticket
Ticket ID: #4372
Subject: Prolaborate V4 Installer - Rijk Zwaan
Department: Prolaborate Support
URL: https://desk.zoho.com/agent/sixthforcesolutions/prolaborate-support/tickets/details/759413000016016456
Ticket ID: #4546
Subject: FW: BNC Sparx Platform Upgrade Complete.
Department: Sparx Platform Support
URL: https://desk.zoho.com/agent/sixthforcesolutions/sparx-platform-support/tickets/details/759413000017004459
Ticket ID: #5683
Subject: Karthick here is the HAR file you asked about
Department: Sparx Platform Support
URL: https://desk.zoho.com/agent/sixthforcesolutions/sparx-platform-support/tickets/details/759413000020888090
Q5. Unable to find a diagram in the Insert menu of confluence Macro
Description
When searching a diagram to publish in Confluence, unable find it through the Insert Prolaborate macro screen
Possible reason
If the diagram is on or above 10th level of package in Prolaborate. It cannot be fetched using the Prolaborate search functionality. This issue extends to confluence macro and the diagram is unable to fetch.
The Bug ticket can be tracked in #9998
Response
Hi <Customer>
Thank you for reaching out to Prolaborate support.
We would like to clarify you that the Confluence search functionality is very similar to that of Prolaborate. However, we observed that artifacts on or above the 10th level cannot be searched within Prolaborate, leading to this issue.
Rest assured, we have made a note of this and It has been added to our product backlog and will be addressed in the near future.
Please feel free to reach out if you have any additional questions.
Reference Ticket
Ticket ID: #2931
Subject: RE: Unable to search of child artifact at 10th Level and above (in PL) impacts Confluence Macro
Department: Sparx Platform Support
URL: https://desk.zoho.com/agent/sixthforcesolutions/sparx-platform-support/tickets/details/759413000010755244
Ticket ID: #9164
Subject: Problems with Prolaborate Macro in Confluence
Department: Prolaborate Support
URL: https://desk.zoho.com/agent/sixthforcesolutions/prolaborate-support/tickets/details/759413000034366606
Q6 In the shared diagram on Confluence, class attributes and operations are not being displayed.
Description
Customers have reported that in Confluence, the shared class elements fail to display class attributes and class operations on the Confluence page. While these elements show class attributes and basic properties in Prolaborate, the same elements hosted in Confluence lack this functionality.
Possible Reason
This issue appears to be a known issue within Confluence Cloud. Our product team has confirmed that it relates to a problem with the Macro, which has been addressed in the latest version of the Prolaborate macro.
This is only issue in Confluence cloud the data center are working as expected.
Workaround
In case customers encounter the issue of class attributes not being displayed on Confluence Cloud pages, we recommend advising them to uninstall the existing macro and reinstall the latest cloud macro. This action should resolve the issue.
Email Draft
Hi [Customer name],
Thank you for your patience.
We are pleased to inform you that we have released an updated version of the Prolaborate macro for Confluence Cloud. This update addresses the issue you previously encountered, where the Class attribute and Class operation properties were not displaying correctly.
You can access the updated Prolaborate macro on the Atlassian Marketplace: https://marketplace.atlassian.com/apps/1228352/prolaborate-4?hosting=cloud&tab=overview
Once the macro is installed, refer to the documentation here for step-by-step instructions on reconfiguring the macro.
After completing the configuration, you should now be able to see the Class attribute and Class operation properties correctly displayed on your Confluence Cloud pages.
Please review the above information and let us know if you have any further questions or concerns.
Reference Ticket
Ticket ID: #8100
Subject: Prolaborate - profile configuration - class attributes
Department: Sparx Platform Support
Tags
access denied for the projectconfluence integration
Related Articles
Known Issue - JIRA
Q1. "Not able to connect with Jira!" Error in Prolaborate Description Jira Items are not able to connect with Prolaborate elements and getting the below error. Possible Reason -1 The project may have been deleted on the Jira side after you configured ...Known issue: Access denied error when clicking SSO in Prolaborate(Autoscaling environment)
"Access denied" error when clicking SSO in Prolaborate. Description: The customer reported being unable to access Prolaborate. When clicking the SSO, they encountered an "access denied" error in Prolaborate. Possible Reason: As confirmed by the Dev ...FAQs - JIRA
Q1. Links generated from Jira Items are exposing the entire repository when accessed Answer This behaviour is intentional, as Jira provides only essential information, and users typically access Prolaborate to access comprehensive data. If you wish ...Troubleshooting - Sections and Access Permissions
Q1. Unable to access elements in a diagram located in a different package Description The customer was unable to access elements in a diagram that are located in a different package. Troubleshooting steps The error message "No access to the Artifact" ...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 ...