Spotfire Ideas Portal
ADD A NEW IDEA

Scheduled Updates

Showing 38

Keep old cache, while new cache is being generated.

Scheduled Updates allows reports to be cached. These can help reports that take a very long time, to open much quicker. Also the schedule can be set for various frequencies. But it seems the process deletes the old cache before starting a new cach...
4 months 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...
about 3 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 ...
almost 9 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 i...
over 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...
over 7 years ago in Spotfire / Scheduled Updates 3 Future Consideration

Scheduled updates icons in version 7.7 and later

One of best smallest features in server with 7.6 were the icones near scheduled updates rules. In version 7.7 and 7.8 they are no longer visible. There is general information at the top about files loaded, loading and failed. Click on the links sh...
almost 8 years ago in Spotfire / Scheduled Updates 8 Future Consideration

Schedule Update: add the possibility to start the update when a file is created

for exemple update is scheduled at 06h AM = > at 6 AM the schedule start and wait for the file //temp/schedule/logistic_updt_donne.txt. When this file is created by external job, the update can begin. At the end of update, the file is deleted t...
almost 4 years ago in Spotfire / Scheduled Updates 0 Future Consideration

Use parameters in Scheduled Updates

Hi, It would be very useful to be able to set document parameters in scheduled updates. This way it would be possible to schedule the very same document with different settings. Currently, one has to create as many versions of the dxp as many diff...
over 7 years ago in Spotfire / Scheduled Updates 6 Future Consideration

Disable Schedule for Scheduling & Routing Files

In "Scheduling & Routing" currently you can disable rules for files, which turns off the routing of users to a cached copy of the file. However, when troubleshooting issues with a data source, it would be helpful to be able to quickly disable ...
almost 4 years ago in Spotfire / Scheduled Updates 0 Future Consideration

More control with Scheduled Updates - Allow to Pause, Add an Option to NOT trigger them after server/application pool restarts

Every time a server is restarted (scheduled or unscheduled), it triggers the re-load of the analysis files in the Scheduled Updates. When analyses use large data tables, it takes a long time to run the updates, and when the re-start happens close ...
almost 8 years ago in Spotfire / Scheduled Updates 5 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