Welcome to the BrightGauge Enhancement Forums
The Enhancement Forums is one of several listening posts used to bring enhancement ideas to the ConnectWise Product Management Team. We utilize information from support tickets, information gathered from our onsite Consulting Team and our Sales Team during the sales process, as well as one-on-one or group discussions with our partners.
Do you have an enhancement you want to suggest or have you come across an enhancement you would like our Product Management Team to review? Vote and leave a comment. The more information gathered on the enhancement, the easier it is to make the case to the Product Management Team. The Product Management team automatically reviews enhancements with 250 votes or more and we will provide any updates to that enhancement as they become available.
Want to know what the statuses mean? Click here or on the "Status Legend" in the Links section.
Show your support for the ideas you like by voting and leaving a comment.
Now get out there and make your voice heard to help BrightGauge grow your company!
Custom date range on Dashboard Filters
When filtering on dates using Dashboard Filters, there is no option to specify a custom date range, despite there being an option for this in the Gauge Editor
New dataset for the list of Company Teams
It would be really fantastic to have a dataset that contains the list of all team members and their associated roles for each client.
Deep Linking to CWM Customer Portal
Currently deeplinks for CWM only go to CWM. We would like to allow them to use the CWM Customer Portal instead for gauges that are used by external customers.
Additional math & logic in calculated columns
We use calculated columns in Brightgauge table gauges, but find we occasionally need more complex logic than is available in the calculated columns - for example,
- max, min
- coalesce
- conditional logic and comparisons like equal to, greater than, lesser than (for example, if A+B > X, then display X, otherwise display A + B)
Keep Headers in non-list guages when exporting to CSV
When exporting a gauge to a CSV unless it's a list gauge the headers are lost. Please allow all headers to be kept in the format.
Cover Page and custom image
The cover page option on the report is very limited and does not allow too much for custom branding of reports. Currently i need to scale a image and try and make that fit on the cover page. Brightgauge needs an easier way to make a custom cover page.
Import custom fields on Project Tickets
I would like to recommend the feature of custom fields on Project Tickets to be implemented. I am building a gauge using project & project tickets to track client risk. As we can't get the "latest discussion" as a field - I created a free text custom field on a project ticket called "Latest update" which I wanted to use as a quick glance into the latest action for the risk.
3CX intergration
3CX is one of the biggest players in the world of IP telephony. Several call centers and MSP use it. Their (3CX) reports aren't great, so it would be very beneficial to have an integration between 3CX and BG to create reports and dashboards.
They have good doc on their Rest API: How to Use 3CX Configuration API
Dynamic Date Filter: Add After (n) Days (we already have 'Earlier than (n) Days', it should go both ways)
On past-looking data, we can use 2 filters to achieve a specific, custom range: Last (n) Days // Earlier Than (n) Days Ago
This solution works for looking at date ranges in the past.
BG has Last (N) Days, Earlier than (N) Days, within Next (N) Days, but does not seem to have After (N) Days. I would expect that to be there since it is very similar to the Earlier than (N) Days filter.
I will start with the past-looking metric to explain better:
- Past-Looking Data
- Need: Opportunities where date_became_lead is between 90 – 180 days ago
- Solution:
- Filters:
- Filters:
- Date_became_lead = Last (n) Days {180}
- Date_became_lead = Earlier Than (n) Days Ago {90}
- The combination of these filters yields a list of opportunities created between 90 – 180 days ago, which achieves the purpose.
- Forward-Looking Data
- Need: Opportunities where expected_close_date is between 90 – 180 days in the future
- Solution:
- Expected_Close_Date = Next (n) Days {180}
- Later Than = FIXED DATE
- The combination of these filters yields a list of opportunities closing within the next 180 days and which are also after a fixed date;
- We need this to be dynamic, like it is with the past-looking/”earlier than” data.
New dataset for CPQ - Quote item
The datasets associated with SELL/CPQ don't give enough information.
Could you create a new dataset that gives items in a quote.
I checked with CPQ dev documentation and the API allow to read the view: QuoteItemView.
Best regards,
Fred
Customer support service by UserEcho