Users can orchestrate the automated delivery of selected Discover reports using Subscriptions which effectively exports or prints the content in a selected document format and distributes it on a scheduled basis.
Configuring a subscription involves choosing an output, defining the schedule, and setting up distribution via the bulletin board or email. This offers a way to share data discoveries on a scheduled basis, ensuring you can keep an eye on changes to your key metrics.
Note: this feature is available with the Enterprise Edition license only.
Note: when subscribing to content and distributing it to other users, the subscription runs as the initiating user. The recipient to whom the subscription is distributed receives the same data as the initiating user. This means the recipient may see unsecured data.
If you want to distribute data dynamically, sending different data from the same report to different users, this is done by configuring dynamic distribution of publications. In this case, the recipient will only see data for which they have permissions.
Subscriptions vs Alerts
Unlike Alerts, which are used to send an alert message that let's you know if a given data value has changed, subscriptions are used to share the entire report.
Accessing Discovery Subscriptions
Once your data discovery has been saved, click the Subscribe icon from the upper right corner above the canvas.
Subscriptions can also be accessed and triggered from running presentation dashboards.
- Click here to learn about Present Subscriptions
Subscribe Dialog
From the Subscribe Dialog, work through the four tabs to configure the subscription.
- General: select the required output type to which to discovery (or presentation) will be exported.
- Details: name your subscription and add a description.
- Schedule: configure the schedule for the subscription job.
- On Demand: use on demand scheduling to trigger the schedule when the underlying data model or reprocessed, or via an API call.
- Distribution: set the distribution to a list of recipients via the Bulletin Board, email, phone, or channel Webhook.
- Click here to learn how to configure Subscriptions from the Subscribe dialog.
Dynamic Interactions
The exported discovery reflects any dynamic interactions made with the query at the time the subscription job ran. For instance, if you filtered by a product, the exported discovery will be filtered accordingly. If you drill down, this action will be rendered in the exported discovery.
In the example below, we see that the slicer selection applied in Discover is reflected in the exported data discovery:
Subscription Output
Bulletin Board
When subscriptions are distributed via the Bulletin Board, recipients can access them from their own Subscriptions Feed where they can download the content.
When subscriptions are distributed via email, recipients will receive the templated email. According to how the email template was configured they may receive the content as an attachment, and/ or a link to the content in Pyramid.
Phone
Recipients of subscriptions distributed via SMS will receive a templated message configured by the user who created the subscription.
Channel
Recipients of subscriptions distributed via a channel Webhook will receive a templated message in the given channel.
- Click here to learn more about scheduled distribution.
Managing Subscriptions
Subscriptions can be edited or deleted from the Content Manager. Admins can also edit, remove, and rerun subscriptions from the Admin console.
- Click here to learn how to manage subscriptions schedules from the Content Manager.
- Click here to learn how to manage and create subscriptions schedules from the Admin console.
Data Source Authentication
If the data source used in the discovery or presentation is based on Windows Authentication, then a separate panel will be presented to the user. The user may need to supply a set of credentials to successfully submit the scheduled task.
This often occurs when the authentication method for the data source is set to "End-user" Windows Authentication. Under this model, the user running the queries is used to connect (via Kerberos token) to the data source. However, when running a batch task (offline), the user's token is not available - as such a set of their credentials is required for connectivity by the Pyramid engine.
This may not be required if the website authentication is via Basic or Forms.
Schedules can also be configured for SAP BW sources if SAP Logon Tickets is selected as the authentication method in the Admin console. In this case, you'll be prompted to enter the relevant credentials.
Note:SAP Logon Tickets are available with an Enterprise license only.