Spotfire Ideas Portal
ADD A NEW IDEA

Scheduled Updates

Showing 31

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

File Routing and/or Deny Open for Scheduled Updates Change

We like having scheduled-updates.performance.deny-open-when-not-scheduled set to true in config.bat so that users don't try to open large cached analyses outside of their scheduled window. However, we also want to be able to route a specific file ...
over 7 years ago in Spotfire / Scheduled Updates 2 Future Consideration

Manage scheduled updates within Library folder web interface

We would like to see the ability for web player users to be able to setup scheduled updates for DXP files they have the security to view. It would need a new license right in web player such as 'schedule from analytics folder'. I would also like t...
over 8 years ago in Spotfire / Scheduled Updates 1 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 8 years ago in Spotfire / Scheduled Updates 4 Future Consideration

To be able to access the last successful cache if the latest cache is failed for a report

When there are reports which are scheduled daily for caching and whenever a cache rule is failed, we see users facing issues while accessing that report as the data would be read from the source, which is a time consuming process. Instead we wante...
over 8 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 8 years ago in Spotfire / Scheduled Updates 6 Future Consideration

Option to trigger reload of Scheduled on particular instance

Currently the manual reload triggers reload on analysis on all configured instances on the resource pool. Sometimes reload may fail on one instance (could be due to some external errors) and success on other instances and in this scenario we can't...
over 8 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 9 years ago in Spotfire / Scheduled Updates 5 Future Consideration

Monthly Scheduling & Routing option.

currently, there is no option in the schedule to created monthly frequency, monthly repeat with all of its options is highly useful.
about 9 years ago in Spotfire / Scheduled Updates 6 Planning to implement

Scheduled Updates Priority Grouping

In 7.5, we can enter a Priority value for each scheduled update Rule. The list is sequential, with 0 the highest value. Let's say I have 20 analysis files prioritized from 0-19. I add a new analysis, and it's the most important analysis ever and m...
over 9 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