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
There are several possible approaches to this that you can apply:
Use data from external source Instead of using embedded data.
Automate pruning based on your custom policies:
Use Spotfire CLI to automate library pruning based on your custom policies. You can do that from Spotfire 12.0 LTS.
Use LibraryService (as suggested above by Gerko). Note this has been deprecated recently.
Use REST API to automate library pruning based on your custom policies. You can do that from Spotfire 14.0 LTS. See: https://community.tibco.com/s/article/What-s-New-in-Spotfire-14-0-LTS
Use library version history settings to opt-out for that specific library item. You can do that from Spotfire 14.0 LTS. See: https://community.tibco.com/s/article/What-s-New-in-Spotfire-14-0-LTS
Note: When we introduced the Library version history, we discussed within UX about adding pre-defined pruning policies We understood early that there would be many different opinionated policies, and too many possible ways to configure them for different people (by date, name, directory, creator, version name, etc). Therefore, we decided to start the path by opening configuration and APIs, so everybody fully customize the pruning policy (as opposed to providing a few of default pruning behaviors).
This is an interesting idea that is somehow related: https://tibco.aha.io/ideas/SPF-I-5156 "Add Python scripting modules as a standard Add-in in the Automation services capabilities". What do you think about adding a "custom automation job task" where you could run custom CLI/Python/REST?
Thanks