TABLEAU QUESTIONS

Should You Use a Tableau Alert or a Subscription?

The manager wants to know when late orders need attention. The team chasing those orders needs the details it can work through.

A Tableau alert or subscription may cover the warning or regular snapshot. Advanced Tableau Report Scheduler (ATRS) can prepare the Excel worklist that helps the team follow up.

THE PROBLEM AND ANSWER Does the manager need a warning or a report?
YOUR OPTIONS Choose what helps the team take action
SET IT UP Turn the late-order rule into a useful worklist
FOR DEVELOPERS Let your application request the worklist
YOUR NEXT STEP Give the team what it needs to follow up

THE PROBLEM AND ANSWER Does the manager need a warning or a report?

The operations manager wants to know when late orders exceed ten. A Tableau data-driven alert can draw attention to that threshold, giving the manager a reason to open the dashboard and investigate.

The Monday meeting has a different need. The manager wants the backlog report in advance, whether the count is high or low. A Tableau subscription can send a PNG image, a PDF snapshot or both on the chosen schedule.

Now consider the people chasing the orders. They need order numbers, promised dates and the customers to contact. A warning tells them there is a problem; an Excel worklist gives them something to act on. ATRS adds that report preparation and delivery when the team needs more than the native notification or snapshot.

Tableau’s alert dialog lets you set the comparison, threshold, recipients and notification frequency. The pictured example uses a different measure.

Keep the native alert when a notification completes the task. In the late-order example, the manager can use it to spot a growing backlog and decide whether to intervene. There is no need to build a file-delivery workflow just to draw attention to a number.

Use a subscription when a regular view of the figures is enough. The Monday backlog PDF can help the manager prepare for the meeting. Tableau also offers Don’t send if view is empty for a view that contains data only when an exception needs attention.

ATRS is useful when the team needs the next step prepared as well. A data-driven schedule can use a database query to select the regions that meet the late-order rule, then use the returned values to choose report parameters, recipients, formats and destinations. One manager might receive a PDF by email while the follow-up team receives its Excel worklist.

The important connection is between the rule and the file. The count that qualifies a region and the orders in its workbook should refer to the same business date and region. A recipient’s email address identifies where to send the report; it does not, by itself, select that person’s data.

Native alert and subscription requirements

For a data-driven alert, select a supported continuous numeric axis and choose Create in the Alerts panel. Set the comparison, threshold, recipients and notification frequency. Gantt charts, maps, numeric bins, discrete numeric axes and story points are not supported. See Tableau’s data-driven alert guide.

For a subscription, use Watch > Subscriptions and choose the view or workbook, PNG/PDF format and schedule. Recipients need View and Download Image/PDF permissions. Save a Custom View first when particular filters are required; temporary filters are not automatically retained by the subscription.

Empty-view suppression checks whether the view contains data. A displayed zero or a populated summary is not an empty view. For a threshold such as “more than ten late orders,” the report author must make the exception view genuinely empty when the rule is not met. See Tableau’s subscription guide.

Start with the workbook the follow-up team needs. Agree which orders and columns belong in it, which region it covers and who should receive it. Then open the Tableau report with those inputs and check a familiar late order.

In ATRS, create a Data-Driven Schedule using a query that returns the reporting records for regions with more than ten late orders. Select the Tableau account and report, map the returned region and date values to the report’s supported parameters, and map the recipient fields to the delivery destination.

Choose Excel output for the worklist and send the first run to a test destination. Open the received file with someone who handles the orders. Confirm that it contains the expected region, business date and order details, rather than only checking that an attachment arrived.

Run the schedule after the overnight data is ready. Agree whether an unresolved backlog should produce another worklist tomorrow or whether the team only wants the first notification. That decision keeps a continuing exception from turning into a stream of unwanted copies.

Configure and test the qualifying records

The ATRS data-driven schedule guide covers the database connection, driver query, report Item Path and parameter mapping. Configure the threshold in the query; ATRS uses the records it returns to drive the reporting work. This does not create a native Tableau alert.

For this example, test counts of nine, ten and eleven. Nine and ten should not qualify under a “greater than ten” rule; eleven should. Check the selected region and business date in the resulting workbook. A failed query needs investigation and must not be mistaken for a successful check with no qualifying work.

When data readiness varies, an ATRS event-based schedule can start an existing report schedule in response to a configured condition, such as a matching database record. Design the detection and acknowledgement behavior carefully: a record that continues to match can trigger repeated runs. A scheduled time alone does not prove that the overnight load has finished.

Choose the notification when awareness is enough, or deliver a worklist when the team needs a file to act on.

Your order-processing application may already decide when the backlog needs attention. It can request a tested ATRS worklist when that rule is met, leaving ATRS to generate and deliver the configured report.

Keep the request tied to the region and business date that caused it. If the next check finds the same backlog, use the agreed repeat policy before requesting another copy.

API example: run the configured ATRS worklist

Use an existing single-report schedule whose report, parameters, Excel output and destination are already configured and tested. Replace 101 with its actual UniqueId. The execution request runs saved settings; it does not evaluate the late-order threshold or supply new region and date values.

POST /api/Schedule/ExecuteScheduleAsync
Authorization: Bearer <ATRS-access-token>
Content-Type: application/json

{
  "ScheduleType": "report",
  "UniqueId": 101,
  "RunBy": "Operations application"
}

GET /api/Schedule/GetExecutionStatus?ExecutionId=<returned-id>
Authorization: Bearer <ATRS-access-token>

Save the returned ExecutionId, monitor the run and parse its JSON-encoded ResultJson. Completed can contain a failed result, so inspect the result and confirm the workbook reached its destination. Follow the ATRS execution and monitoring guide.

Keep tokens on the backend. After an uncertain response, check the existing execution before submitting another request; the first run may already have produced a delivery.

The operations manager needs to spot a growing backlog. The follow-up team needs the orders it can work through. A native alert or subscription may cover the first need; an ATRS workflow can prepare and route the worklist for the second.

Start with the late-order rule and one example of the file the team wants to receive. Explore how ATRS can connect the condition, report preparation and delivery so the warning leads to useful follow-up.

Explore ATRS report workflow automation

Should You Use a Tableau Alert or a Subscription?

Does the manager need a warning or a report?

Think about the next conversation

Choose what helps the team take action

Give the warning a purpose

Turn the late-order rule into a useful worklist

Follow one late order

Let your application request the worklist

Help a colleague follow the request

Give the team what it needs to follow up

Contributors:

Christian Ofori-Boateng

About ChristianSteven Software