Spotfire Ideas Portal
ADD A NEW IDEA

Scheduled Updates

Showing 35

Scheduling Reports to run sequentially that are all using the same rule.

When multiple reports are assigned to the same rule they are start at the same time. At this point the CPU usage and memory spikes. If you break them up and stagger them you can still run into the same issue. It would be nice if there were paramet...
over 3 years ago in Spotfire / Scheduled Updates 0 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

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

Enable monthly scheduling withdraw: same as TS-I-7174

Currently it is only possible to schedule within a week. We have several report jobs that need to run only bi-weekly or monthly. Create a possibility to set a - repeat every x weeks - with default 1.
about 4 years ago in Spotfire / Scheduled Updates 0 Future Consideration

Node manager doesn't properly handle fail over for the scheduled updates and this needs to be updated

Currently, if the a scheduled update rules fails on a rule is will keep trying to use that node to re-run the rule regardless of the reason it fails. It should go to the next node in this scenario instead since the next node could be able to handl...
about 4 years ago in Spotfire / Scheduled Updates 1 Future Consideration

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...
over 4 years ago in Spotfire / Scheduled Updates 2 Future Consideration

Withhold Scheduled reports in cache during upgrades / server restarts

When ever we restart Spotfire Server or after an upgrade of Spotfire , all the scheduled reports starts loading automatically and they take some time to finish . So it would be good if the reports are not lost and are cached when server restart or...
over 4 years ago in Spotfire / Scheduled Updates 2 Future Consideration

Create, edit, and delete scheduled update settings by Spotfire web service

We want to create, edit, and delete schedule update settings by calling Spotfire web services. By doing so we are able to prepare a dxp as a template, and auto-generate new dxp with correspoding schedule update settings by user input requirements.
over 4 years ago in Spotfire / Scheduled Updates 0 Future Consideration

Allow us to control cache expiration time

Currectly cache expires every 24 hours or less. I have over 600 reports with caché rules and the cache process take me around 6 hours. 95% of those reportes get new data every week, not every day, so I want to be able to set custom cache expiratio...
over 4 years ago in Spotfire / Scheduled Updates 2 Future Consideration

Enable schedule updates for calculated values

When a dashboard with a large data volume uses hundreds of calculated values, although scheduled updates is in place for it, calculated values are exempt from scheduled updates and they are computed on users' clients (Spotfire Analyst, Spotfire we...
about 5 years ago in Spotfire / Scheduled Updates 0 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