Spotfire Ideas Portal
We are testing v12 and are hesitant to set up the Library versioning feature, as we don't know how much space this will take in the database. I found the pruning command but remembering to run this manually by the admin team on a regular basis will be time consuming. We need to have automatic pruning, by limiting the number of versions each dxp can have.
| Implemented in | 15.0 |
Hi,
I'm happy to announce that automatic library pruning has been implemented in Spotfire 15.0.
Spotfire administrators can define now the maximum number of unnamed versions retained for each library item. Older unnamed versions are automatically removed when the configured limit is exceeded, helping organizations manage storage growth and reduce administrative overhead.
Named versions are preserved and excluded from automatic pruning, ensuring that important milestones and releases remain available for future reference.
For advanced version management scenarios, administrators can continue to use existing library version management tools and commands.
On addition to that, Spotfire 15.0 introduces also more granular control over library version history. Now administrators can override the previous default global setting and custom default settings per library type, and enable or disable version history for individual library items directly from the web administration interface or from the installed client.
This flexibility makes it easier to align version history policies with organizational requirements and specific usage scenarios, such as project workspaces, shared resources, or automated processes.
For more information, see the What's New in Spotfire and the release notes and product documentation.
Thanks!!
0
Implemented
Moreover, one of our customers wants to configure automatic pruning per library folders.
Several of our customers are asking for this as well.
Preferably, pruning by number of versions(only keep last N versions) , or by created time (only keep versions created after YYYYMMDD).