When changing the Elasticube associated with a dashboard, any Pulse alerts built off widgets from that dashboard will not be changed and will continue to be affected by the old Elasticube. This is an issue if you are replacing one Elasticube with another. There is no warning / message when changing a dashboard's Elasticube that pulses will be affected. There is no way to see the Elasticube a pulse is attached to - only the dashboard (but again, changing the dashboard's Elasticube doesn't change the pulses). There is no way to see which pulses are built on top of an Elasticube from the Elasticube screen (unlike with dashboards). I would like the ability when changing the Elasticube for a Dashboard that has Pulse alerts associated to it, give the prompt option to update to the new Elasticube for Pulses as well. This could either be done: Via some new UI Via some warning (similar to when you try and delete a cube with active dashboards / pulses) - but this would then also need the secondary ability to manually change the Elasticube associated with Pulses. ... View more

Goal Enable dynamic alerting based on history using formulas Enable reuse of conditional coloring rules for pulse threshold  Background Pulse allows you to trigger off of a threshold (e.g. > 10,000, <= 10) Conditional Coloring of widget values allows for functions (e.g. Min([Months in Date], [# of unique Transactions]) Perhaps the Automatic anomaly detection does this, but we have no visibility into what is results in an anomaly.  Also not sure if you have to wait for the anomaly detection to learn. e.g. the cube has been built every day for years and has years of data, but the widget was only created a couple weeks ago and the pulse alert was added yesterday.  Will it detect anomalies or out of bound conditions that we could write with a formula Desired Functionality Enable use of functions in Pulse thresholds similar to Conditional Coloring of widget values Ideally enable reference to the Conditional coloring options for the widget.  The dashboard designer already built it into the dashboard. The user just wants a pulse alert when the widget turns RED.  Provide means of selecting from existing conditional coloring rules (Whether they are static values or forumlas) when building/editing the Pulse tile. ... View more

Opening a dashboard which leads to a temporary error will redirect the user away from the dashboard URL to a 'dedicated' error page, e.g. 'https://xxxxxxx.sisense.com/app/main/error?status=404'. If this is a temporary error and the user refreshes this page they will never return to their intended destination - they are stuck on the error page forever. This causes confusion for our clients. Is there a way to change the way errors work so that I'm not redirected to a 'dedicated' error page and instead I can refresh the page and see my intended dashboard once the error is resolved? ... View more

I've been trailing the Report Manager add-on and was disappointed to see that the 'Event Based' option for triggering reports did not allow for Pulse Alerts to be used as an Event. It seems the current workaround is to use a tool like Zapier (so the pulse goes out to Zapier via webhook, which then creates the Event and goes back into Sisense, causing the report to be sent. This seems convoluted and I would have thought being able to directly integrate Pulses to trigger Reports seems like a natural fit. ... View more

Cube build alerts via webhook should receive which cube has triggered the alert. This is required especially when we configure a single alert for multiple cubes As of now, we are only receiving following info. {buildSuccess: false, name: Cloned sisense alerts, type: build} With this info, we do not understand which specific cube has failed. ... View more

We have a custom webhook mechanism to alert us for cube build failures. We created a single alert selecting all our cubes and adding the webhook link Given build alerts are owned only by a single person.  Ownership transfer of these is helpful when people move out of the team and new person comes in, If not,the alerts created for team will need to be re-created. Also, every time we want to add a new cube to the build alert, the owner of the common build alert should be available else we cannot add alert or will be forced to create a build alert for the absence period of the owner ... View more

Currently you only provide a direct link to a dashboard.  Allow the ability to have the ID of the dashboard. That way customers embedding the dashboard into their main app can load it natively into their app instead of directing the user directly to the Sisense instance. ... View more

We have some ideas for enhancing Pulse: Once a Pulse alert has been created, have the ability to edit the filter from the Pulse page. Have the ability to create Pulse as an option from the entire dashboard.  Users would select a measure for the pulse and set filter conditions from the model in question directly. Make the Pulse input pop-up available within the application for developers (e.g. 3rd Party) to exploit from plugins they have developed. Add ability to configure Pulse to trigger on a schedule (once per day, once per week, etc.), e.g. when a build is done, the alert gets sent according to the schedule. Option to set Pulse to trigger when value changes in any direction rather than having to set up a specific calculation. ... View more