Spotfire Ideas Portal
ADD A NEW IDEA

All ideas

    Showing 4798

    Application-wide text areas

    Pretty much every single project we've created has followed a typical L-shape layout, that is: Custom filter panel on the left (text area with restricted filter view, grouped by accordion) Custom text area along the top, with client logo and navi...
    over 9 years ago in Spotfire / Visualization 0 Future Consideration

    Automatic alerts on system health (email warning when web player is strained for instance)

    Today we have a good monitoring status on admin console, but this is manual. As we have 24/7 teams in charge of monitoring, it would help to be able to setup automatic email alarms when the system is not performing well due to various reasons (lac...
    almost 5 years ago in Spotfire / System Administration 0 Future Consideration

    Sorting column names in a List Box

    When creating a List Box we want to change the order of the column names in the List Box. When selecting "Set property value through: Column selection" the order of the names is set, and the order cannot be changed. We would like a Sorting ...
    about 2 years ago in Spotfire / Text Area 1 Future Consideration

    Expose Lists to the Spotfire API

    Currently, Spotfire lists (as seen in the Lists panel) are not accessible via the IronPython API. This limits our ability to automate workflows that rely on lists, such as creating lists from specific column values and using list comparison tools....
    3 months ago in Spotfire / API 0 Future Consideration

    The approved version of the object should remain unchanged after migration.

    When we approve an object and then migrate it to another environment, the approved version changes to 0.1. For example, if an object is approved with version 1.0, after migration its version becomes 0.1. Ideally, the version should remain the ...
    3 months ago in Spotfire Statistica 0 Likely to implement

    Separate Library from the system database

    As an administrator I would be interested in having an option to build an external database for the Library, this way keeping the actual system database slim and providing options to link multiple libraries and provide multiple storage locations. ...
    about 3 years ago in Spotfire / Library 2 Future Consideration

    Administration functions in REST API

    Background: As soon as we use Configuration Management tools to manage our multiple Spotfire environments constellation, we need to be able to perform whole Spotfire configuration via automation scripting. Issue: During our development we spend a ...
    over 4 years ago in Spotfire / System Administration 0 Likely to implement

    Import changed/modified Spotfire elements alone

    Hi Team, In day-to-day deployment(Export,import) of Spotfire elements between multiple environments, we also migrate the elements even though it is not changed(especially, when we import/export whole folder). It is also hectic job to export/impo...
    almost 7 years ago in Spotfire / Library 1 Future Consideration

    Ability to manage permissions for exporting data to file

    Add the ability to manage permissions independently for exporting data from visualizations (yellow highlight) and from Data tables (Red Highlight). The ability to export data table can sometimes override default filtering, including some row level...
    over 1 year ago in Spotfire / Export 0 Future Consideration

    Support for timestamp with timezone data type

    Datasets from sources that use a timestamp with timezone field are read incorrectly in Spotfire. See: https://support.tibco.com/s/article/Values-in-a-column-of-type-Timestamp-with-timezone-are-different-from-original-values-when-imported-through-I...
    almost 2 years ago in Spotfire / Data Access 1 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