Spotfire Ideas Portal
ADD A NEW IDEA

All ideas

Showing 4309

Provides a license monitor that monitors, aggregates, and displays user login and logout times

Session viewer of version 14.1 only shows who is connecting at the moment. Especially when using concurrent licenses, if an administrator can see which departments are using the software frequently, including past history, they may consider adding...
about 1 year ago in Spotfire Statistica 1 Already exists

Re-implement of Software-enforced licenesing management function for concurrent user license

Since end users cannot know who is connecting, they cannot control the number of simultaneous connections. Regarding concurrent user licenses, it is necessary to re-implement the function to limit the maximum number of concurrent connections.
about 1 year ago in Spotfire Statistica 1 Will not implement

Library Recommended Visualizations & Custom Expressions Associated with Information Link or Library Data

Allow the sharing of visualization configurations to the library presented through the recommended visualization dialogue. So when a user adds a data resource from the library it would present visualizations other users have created using that dat...
about 8 years ago in Spotfire / Visualization 0 Future Consideration

Allow "Update service" through the Spotfire Server CLI

After deploying a package for a Spotfire service, such as the TERR or Python service, that service needs to be updated through the Administration Console. When the deployment is done using the "update-deployment" function in the CLI, it would be u...
about 4 years ago in Spotfire / System Administration 0 Future Consideration

Keep formatting in cross table when display name of column changes

When the display name of a column (cell value) in a cross table changes, the formatting settings are reset. This is highly annoying, especially when column names include a document property which is changed by a user. After each change, the format...
about 6 years ago in Spotfire / Visualization 0 Future Consideration

API to register a data function

An API to register a data function would make it possible to have a custom extension dynamically add a data function to the analysis document. Similar to how you can import a .data function (from a -sdf file) in the Register Data Functions dialog.
about 1 year ago in Spotfire / API 0 Future Consideration

Impact Analysis in Calculated Colomns

hello Sometime we need to do some clean up in the calculated colomn, or delete an import colomn. Today, we must look at every calculated colomn to know where it is used. Could we have (like in Information link) a right click button to ask "Where i...
about 7 years ago in Spotfire / Data Management 0 Future Consideration

API: Add option to obtain guid for the sbdf file of a SbdfLibraryDataSource in case its name is not uniqe

I've confirmed the following with support: There's currently no way to obtain the guid of the sbdf in the library which is used as data source in case its name is not unique in the library. My request is to add an option to obtain the guid easily ...
about 5 years ago in Spotfire / API 0 Future Consideration

API: Set starting folder for LibraryBrowserDialog

I've confirmed the following with the support team: There is currently no way to set the starting folder when opening the LibraryBrowserDialog via python. I can set the SelectedItem property, but if I set this to a folder in the library, that fold...
about 5 years ago in Spotfire / Scripting 0 Future Consideration

Annotations in Client and Web Player

Currently When Annotations are added in the client in a specific position on a visualization , it appears scattered in web player and does not resize according to the monitor, on bigger monitors it appears way scattered.
about 7 years ago in Spotfire / Visualization 1 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