Spotfire Ideas Portal
ADD A NEW IDEA

Library

Showing 178

Spotfire Library - TIBCO supported views on Spotfire library metadata

Could TIBCO deliver "native views" (materialized?), developed and maintained by TIBCO that could provide real insights in the Spotfire library? I am aware of this article (https://community.tibco.com/wiki/tibco-spotfire-metadata-queries), but it i...
over 4 years ago in Spotfire / Library 3 Future Consideration

Store Library Path of a DXP file once saved first onto the library

Having the possibility to specify where a DXP is saved onto the library would avoid the dozens of clicking when saving the same DXP later on. In my organization we have at least 6-7 layers of folders before reaching the relevant one for my departm...
over 1 year ago in Spotfire / Library 0 Future Consideration

Automate library version pruning

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 wil...
about 1 year ago in Spotfire / Library 2 Future Consideration

Spotfire Analyst - Within Library Administration populate "Web client URL" for the selected folder

On the same level as having a Web Player URL for the analyses saved in the Spotfire Library, it would be very practical to be able to copy a Web Player link pointing to a folder. Could TIBCO implement this functionality? Thank you for your conside...
about 4 years ago in Spotfire / Library 2 Future Consideration

Spotfire Analyst - Make available library metadata information

I am looking for a quick and easy way to get the currently opened library analysis' metadata. Thinking about the File -> Document properties (where one would look "naturally" look I think), the Library tab or the Properties tab, none of these t...
about 4 years ago in Spotfire / Library 0 Future Consideration

From the Spotfire Library, ability to Export analysis file(s) and their Dependent elements with one click

The Spotfire Library Export functionality does not have the capability to gather all associated objects with a .dxp and promote in a single go. It would be great if users could export all the dependent elements related to an analysis file with one...
over 7 years ago in Spotfire / Library 2 Future Consideration

Improve ability to manage data connections and review dependencies.

Data connections do not provide an easy overview of all the data connection data sources or their dependencies. While search is possible using 'item_type' and 'depends_on' search terms, these are cumbersome and need to access an object, and get th...
almost 4 years ago in Spotfire / Library 0 Future Consideration

Provide the ability to compare / diff DXP files and information models

Currently, there is no way to see what has changed in a DXP file or information model. When working in a real development environment, being able to track and identify changes is critical to release reliable, accurate changes. Lacking this abilit...
about 8 years ago in Spotfire / Library 1 Future Consideration

Save any type of object in library

Ability to save any type of object in library. So if I have custom data function or for that matter any custom extension whose state I want to save in library and make it sharable it is not possible.In case of data functions things like conneciton...
over 8 years ago in Spotfire / Library 1 Future Consideration

Enable `search-query` parameter in `delete-library-versions` CLI to accept multiple values

Per reference , the delete-library-versions CLI has a parameter search-query. Currently, it doesn't support searching for multiple file types using a single command - e.g., --search-query="item_type::sbdf OR "item_type::dxp". Enabling the said par...
3 months ago in Spotfire / Library 0 Already exists
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