Widgets

Unable to view the information in the dashboard for widgets configured using query

When creating a widget using a query, retrieving the result may exceed the configured time limit for executing a query in Prolaborate. This can cause errors in the Prolaborate log files, specifically noting “HttpClient. Timeout of 30 seconds elapsing.” To extend the query execution time and view the result, modify the “PCS Request Timeout” setting in Prolaborate Management using the following steps: 

1. Navigate to Prolaborate Management. 

2. Under “Manage Configuration” in the “WebApp” tab, locate the PCS Request Timeout field. 

3. Adjust the timeout duration based on your query’s execution time. 

4. Save your changes. 

5. Restart all Prolaborate services to apply the new setting. 

This update ensures that your queries can run for the designated duration without triggering a timeout

Why the card widget result preview shows more decimal numbers than the final output in the Prolaborate cards widget?

The cards widget is designed to display numbers with two decimal places when the query is formatted correctly. However, during the preview, you may see more decimal places because of how raw data is processed. Once the query is executed, the final output will display numbers with the correct two decimal places.

Why am I seeing an “Added Widget Not Implemented” error on the dashboard after upgrading to Prolaborate V5? 

This error appears because certain widgets from Prolaborate Legacy Version (V3) are not supported in the latest version (V5.x). After the upgrade, previously used V3 widgets may no longer function or appear correctly on dashboards. 

Currently Unsupported V3 Widgets in V5: 

• Discussion Summary 
• Discussions 
• Review Summary Chart 
• Impact Analysis View 
• Dashboard Collaboration 
• Feeds – Quick Links 
• General Feeds 
• Matrix Chart 

Note:

• These widgets may be reintroduced in future releases based on demand and roadmap planning. 

Why Does Data Disappear from Roadmap or Lifecycle Charts After Editing Date Fields?

When users edit date fields for elements displayed in Roadmap or Lifecycle charts in Prolaborate, the chart data may appear to vanish. This typically happens due to inconsistencies in date format handling between Prolaborate and Enterprise Architect (EA).

When users modify the date in a supported stereotype from Prolaborate, there will be no impact on the roadmap.

When users modify the roadmap from EA, the date format will be picked up from your local machine, which impacts the roadmap.

Workaround

1. Set the date format to dd/mm/yyyy in Prolaborate’s general settings.
2. Always update the date properties only from Prolaborate.
3. Update all existing date properties to dd/mm/yyyy using a script in EA.

Can I view a group of Dashboards together in Prolaborate Dashboard? 

Prolaborate supports viewing multiple dashboards in a single, unified layout using the Dashboard of Dashboards widget. This feature allows you to group several dashboards into one consolidated view without the need for manual links or Text Widgets. Click here to refer to the official guide for step-by-step instructions. 

How to display the count of elements with empty Tagged Values in a Prolaborate Card widget? 

Prolaborate’s Card widget allows you to display metrics based on specific property values. However, when you want to count the number of elements where a particular Tagged Value is empty or not set, this cannot be achieved using the default Designer configuration. 

To accomplish this, you must use a custom SQL query that filters elements with empty or null values for the desired Tagged Value when creating a cards widget. 

How can I customize the order or names of the columns in a report created using designer? 

To customize the column order, visibility, or labels in a report created using the Designer, you need to update the Form Designer configuration for the relevant stereotype in the MDG profile. 

• Navigate to form designer and select the relevant stereotype. Reorder, rename, or hide the required fields as needed and save the changes. 
• To hide, reorder or rename the columns for a report created using a designer, it needs be done in the Form Designer of that specific stereotype in the MDG profile. 
• Open the form designer of the said stereotype, adjust the columns based on your need and save the changes. It will reflect in the report in all the places where this stereotype is present. These updates will be reflected in all reports and widgets where the stereotype is used. 

To apply changes only for a specific report, disable the “MDG-Based Report” option and use a custom SQL query to define only the specific columns you want to display when creating the report. Using a custom SQL query gives you full control over the columns without affecting other reports using the same MDG configuration.