Known issues - Analyzer

Known issues - Analyzer

Q1: Images exported from Analyzer are not clear if they have more number of nodes

Description

The images exported from Analyzer are not clear enough if they have more number of nodes. You should be able to find the difference in the images attached below. 
  

Possible Reason

Product Team has confirmed that this is a bug in the current Prolaborate V5.2.

Reference

Prol-Bug3543

Q2: Permission Denied Error when trying to edit the nodes in Analyzer View

Description

When trying to add or remove a node in the analyzer view, the user gets a Permission Denied Error. 
Preview 

Steps to Reproduce

1. I've created a test user group with a test user in Prolaborate for my repository. (I didn't grant any permission)
 
2. I set the Access Permissions to Single Access with (Read and Collaborate) because the customer also has the same config.

3. I tried adding a node to the analyzer, and I got the Permission Denied error.
 
4. Added the Write access in access permissions, but it didn't work out. 
5. I tried changing the user group permissions, and the analyzer works only if I enable access to Modeling Languages or add the user to the Administrator group. And I get the permission denied error, if grant any access other than Modeling Languages.
 

Possible Reason


Product Team confirmed that this is a bug in Prolaborate V5.2. It is already addressed in the upcoming Prolaborate V5.3.

Workaround

As a temporary workaround, we recommend granting Modeling Languages access to the respective user group. By doing so, users will regain the ability to Add/Remove nodes in the analyzer view. To implement this workaround, please refer to the steps provided below:
1. Open your repository and navigate to Menu > User Groups.

2. Select the respective user group, enable "Modeling Languages" and select "Save". 

3. After this, the user should be able to edit the Analyzer view.

Email Response

Hi <Customer>,

Thank you for being so patient. 

We would like to inform you that our team has confirmed that the issue you experienced with the Analyzer view is a bug in the latest Prolaborate V5.2. This will be fixed in the upcoming release, we will keep you posted on any updates regarding this. 

In the meantime, as a temporary workaround, we recommend granting Modeling Languages access to the respective user group. By doing so, users will regain the ability to Add/Remove nodes in the analyzer view. To implement this workaround, please refer to the steps provided below:
1. Open your repository and navigate to Menu > User Groups.

2. Select the respective user group, enable "Modeling Languages" and select "Save". 

3. After this, the user should be able to edit the Analyzer view. We kindly request that you try this workaround and provide us with the outcome. 

If you have any questions or need further assistance regarding this, please do not hesitate to reach out.

Reference

Prol-Bug3644

Tags

analyzer issues,
analyzer images are not clear,
permission denied when editing analyzer nodes,
poor quality analyzer images,
analyzer,
analyser issues,
permission denied error,
editing nodes in analyzer view.


    • Related Articles

    • 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. ...

    • 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 ...

    • Known Issues - Browser Related Issues

      Authentication Failed Error when logging into Prolaborate Description The customer was unable to log in. Error message: Authentication Failed Possible Reason The bookmark might have captured the existing state ID. Workaround State IDs are captured at ...

    • 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 ...

    • Known Issues - EA Connection error.

      Error in Could not connect to the Sparx Systems Floating License Description: The Customer encounters an error as follows when accessing the servers from our client computers. Workaround: To conduct a browser test to ensure everything is functioning ...