Spotfire Ideas Portal
ADD A NEW IDEA

Scheduled Updates

Showing 33

Timeout Setting for Long Running Reports

In Spotfire enviornments, intermittenly different reports keep loading for many hours and never completes execution. However, they are expected to complete in few mins. This issue is not analysis specific as it could happen with any report. There...
almost 4 years ago in Spotfire / Scheduled Updates 2 Future Consideration

Manual refresh to a scheduled report using Automation service job

A scheduled dashboard starts refresh from 8:30 AM and refreshes every hour until 9:30 PM and we have a dependent data flow which should end at 8:20 AM daily but every Monday its delaying due to data volume and ends between 8:40 to 9:05 AM so I had...
over 1 year ago in Spotfire / Scheduled Updates 0 Future Consideration

Data function refresh in scheduled mode

Data functions in auto refresh mode are executed righ after the full load of a dxp. But when a dxp is scheduled for execution and save of results in SBDF for instance, the scheduler does not wait for the DataFunctions to execute before going to th...
over 2 years ago in Spotfire / Scheduled Updates 0 Future Consideration

As a Spotfire administrator I want more control over Scheduled updates keep alive and start time

As a Spotfire administrator I want more control over Scheduled updates keep alive and start time, so that I can plan the runtime of the scheduled analysis as well as how long the analysis is loaded on Webplayer(s) We want to cache an analysis ...
almost 5 years ago in Spotfire / Scheduled Updates 0 Future Consideration

Public Web Service to check status Scheduled Updates (external updates)

We make use of the public web service UpdateAnalysisService to trigger scheduled updates externally after a data refresh. Sometimes the scheduled updates fail. The only way to check this, is to manually log on at the Spotfire Server, go to the Sc...
almost 6 years ago in Spotfire / Scheduled Updates 2 Future Consideration

Permissions for each individual scheduled file

Currently we have some power users that were given administration privileges in order to simply click "reload" at some Scheduled Updates entries in the admin view. We would like to reduce those permissions to a minimum. Therefore we would apprecia...
over 4 years ago in Spotfire / Scheduled Updates 0 Future Consideration

Routing to multiple web player nodes

In our production environment we have multiple web player nodes each with two instances. We have a number of critical reports that we run as a scheduled update where we select 2 in the 'number of instances' dropdown. The issue with default routing...
over 2 years ago in Spotfire / Scheduled Updates 2 Future Consideration

Disable/unload/purge/restart files from the scheduled updates page

If a scheduled updates file hangs it will occupy one slot until the Web Player has been restarted, which is a bad thing to do during production hours. Request(s): 1) Make it possible to cancel/restart a load operation for a file that is currently ...
over 8 years ago in Spotfire / Scheduled Updates 0 Future Consideration

Event Based Scheduling (Trigger from a file or schedule)

Other BI tools that we use have the concept of event based scheduling. So in addition to a schedule firing at a given time/day and frequency the schedule only fires if a designated trigger file can be found or another schedule that this schedule ...
almost 7 years ago in Spotfire / Scheduled Updates 4 Future Consideration

Command Line control for Scheduled Updates

Create methods to control Scheduled Updates via CLI. At a minimum, I would like to be able to enable or disable scheduled updates via the CLI. This would be very helpful when performing maintenance on the Spotfire installation. Right now, when I a...
almost 7 years ago in Spotfire / Scheduled Updates 3 Future Consideration
This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for Spotfire products and services. It is for informational purposes only and its contents are subject to change without notice. Planning to implement - generally 6-12 months out. Likely to Implement - generally means 12-18 months out. Copyright © 2014-2023 Cloud Software Group, Inc. All Rights Reserved. Cloud Software Group, Inc. ("Company") follows the EU Standard Contractual Clauses as per the Company's Data Processing Agreement. Terms of Use | Privacy Policy | Trademarks | Patents | Contact Us