Current State: As of now Sisense supports adding of pulse alerts only for select chart types, like, Indicator, Area, Line, Bar and Column. Expected State: Sisense shall allow rest of the chart types as well to add pulse alerts. It is observed in other competitive products to be available for all the chart types. Customers like us (Blackline) have many use cases of tabular widgets and end users expect alert to be added to these widget types.  ... View more

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

Today, we can use plugins, dashboard and widget scripts to customize dashboard and widgets for scheduled emails as well as desktop. Same should be available for Pulse scripts which allow to modification of alert JAQL on the desktop, but the same script is not executed when sending alerts/notifications. This causes discrepancy between what the user sees on the desktop and what they receive in email. ... 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

It would be cool if our end users could receive a Digest Email that is sent out on a frequent basis from Sisense. This email would be most relevant if it was based on the groups a user is assigned to already. This would ensure relevant communication, as well as ensure there is control over the reports included in the digest that the user would already have access to them. We would not want the digest email to included recommended reports the user doesn't already have access to. If it was a feature the Admin could turn on/off at the group level that would be our preference. The feature would allow the Admin to select how often the digest went out (weekly, monthly, etc). The feature would allow the Admin to select what content was included: For example:  Changes, Top Used/Popular in the Users Groups (i.e. Org), and then for us I think Newly Published Reports would be ideal.  This would allow an organization to choose whether every time a new dashboard is released the user is notified, for us we would prefer a section in the digest that has these 3 dashboards were released to your group(s).  Other BI tools do already offer this-- Attached is an example of the Power BI digest, as reference. Thanks! ... 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

**Please note this idea was migrated to the Product Feedback Forum from older submission areas** For example, we have a system event type that indicates that a restaurant has modified their online ordering hours. Our clients use the indicator for that event type and set it to alert when it gets above 0, as stores aren’t supposed to modify their online ordering hours without owner consent. The problem is that the owner has several stores. They receive an alert when the first store changes their online ordering hours (# of events > 0), but not when a second store does it. The alert is sent at 1 but not 2. The workaround for now is to configure multiple Pulse Alerts, one per store, but that’s only feasible when there aren’t many stores. We have a franchise with over 300 stores! Also, if a store then changes their online hours back, the owner isn’t informed of that either. Can you please add a feature request for an option on the Pulse Alerts to notify on any increase to the value once it’s exceeded the threshold, so the user would receive an alert at 1 and additional alerts at 2, 3, etc.? This would have to be optional and off by default, as you wouldn’t want that to be activated for something that tracked a value that increases often, but the core use case here is for exceptional activity tracking, so the values should rarely increase. ... 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

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

To ensure security and compliance for HIPAA, we need to know when users export data. Specifically, we want to know how many rows were exported so we can check for malicious use.    ... 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

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

While there are some workarounds... * create a user on behalf of the recipient  * create a user that has the email address of an email distribution list * create a forwarding rule in your email  ...many of our users would like to schedule some dashboards to be sent via email with support for a pdf attachment to people who are not and will never be Sisense users in their system. Our application (we're OEM) supports this for reports in the application, and there's an expectation that dashboard emailing would exhibit the same support. As it is clients have to create an application user per external recipient, log in as the user and SSO to Sisense to the recipient available as a dashboard subscriber. In some cases, work can be reduced with an application user that represents an email distribution group instead of an account per user, but even that requires a lot of maintenance from dashboard to dashboard as their recipient lists vary so much. The best work around is using forwarding rules in users' email clients so that when they receive the dashboard subscription, it's automatically forwarded to those external recipients. However, the forwarding process is then tied to a specific user's email account which introduces risk should change need making when they're not available, or the organization.   If the variability of filters and data security is the concern, then perhaps sending in the context of the owner copy is a step toward an answer without meeting the more robust needs of defining different data security for different non-user recipients of the same dashboard.  ... View more

It would be nice to have an officially supported Events endpoint, that lists all the alerts / pulses / notifications that were sent out when an event was triggered. This allows users to create dashboards giving a quick overview of where problems occur. There already is an /events endpoint, but it is not officially supported and not listed in the APIs, so we were only able to find out about it by creating a support ticket. ... View more

I use pulse alerts to alert my clients when there is data on Sisense that needs their attention. The Pulse alert emails are accompanied by a big yellow 'Open Pulse' button. This button is the obvious thing to click on, but unhelpfully, it leads to the 'Pulses' tab of Sisense, not the actual dashboard. As a viewer, I want to jump straight to the dashboard, not be confused but this 'Pulses' tab which I most likely will not have seen before nor used. An option to have the button instead open the dashboard directly would be much better and make it much easier to engage customers with the Sisense platform.   I know there is a link to the dashboard on the pulse itself, but going via this screen this is inconvenient at best and confusing at worst. ... View more

Currently, when you share a dashboard you can have it email the dashboard out to people following a couple different schedules: Every Elasticube update (with a limit on times per day) Daily (can specify which days and a time) Monthly (can specify which months and what day of the month) The trick is that elasticube updates includes failed updates.  I would like to add an option to exclude failed builds from triggering these dashboard update deliveries. Now that we have alerting for build failures, there doesn't seem to be a reason for dashboards to deliver without new information. ... View more