Spotfire Ideas Portal
ADD A NEW IDEA

web services

Showing 20 of 4770

Add A Button to Check and Uncheck All Column in TDV Web UI - Flow - Column Node / Object

In TDV Web UI, if a user creates a flow that contains a "Column" object/node, then at the bottom of the display, there is a list of columns available in the table being operated along with checkboxes for each column name. When a user works usin...
7 months ago in Spotfire Data Virtualization / web services 0 Future Consideration

Option to limit web service API invocation for specified time

This feature is to help control load on the TDV server from web service calls. Organizations with hardware limits or web services that pull large amounts of data could use this feature to keep load on their server in check without causing unintend...
8 months ago in Spotfire Data Virtualization / web services 0 Future Consideration

Sorting the Published REST Web Services page

Dear all,I would like to be able to sort the services that we publish to the Published REST Web Services web page. Currently we have a very untidy situation that looks like this (sorted by publishing date): service called Z service called A servic...
almost 2 years ago in Spotfire Data Virtualization / web services 0 Future Consideration

Improvements for OData Filters

Hello TIBCO Team! As directed by the TIBCO support team in case 02162240, I am opening this Enhancement Request (ER) on behalf of the customer Petrobras to request improvements to the functionality and OData filters, as per the described errors...
over 2 years ago in Spotfire Data Virtualization / web services 0 To be Reviewed

Able to set default settings for webservices JSON operation property and parameters and maintain after re-publish for REST

For REST webservices operation in TDV. We can select setting for our webservice in Web Services => REST => Operations => Property and Parameters Example: Default Property value are like ==== HTTP Method : GET ... Input Message ...
over 2 years ago in Spotfire Data Virtualization / web services 0 Future Consideration

Provide a way for a Published TDV web service's Schema to use Input arguments as-is

Provide a way for a Published TDV web service's Schema to use Input arguments as-is, instead of pre-pending them with the Operation name
almost 3 years ago in Spotfire Data Virtualization / web services 0 Planning to implement

link to spotfire from Data Workbench dataflow

It would be great to see a direct link from TDV workbench publish node to open the flow result in Spotfire directly (skipping the steps to select which flow you just made)
over 3 years ago in Spotfire Data Virtualization / web services 0 Future Consideration

Add the ability to include TDV descriptions in the OpenAPI specification

It is possible to generate an OpenAPI specification from the ODATA CSDL, however CSDL doesn't include the descriptions of the entities and attributes of the published objects. It would be useful if we could include the descriptions as this will al...
almost 5 years ago in Spotfire Data Virtualization / web services 0 To be Reviewed

Support Navigation Properties in OData

Navigation properties allow to represent semantical links between objects in OData. A link that is technically established as the translation of a foreign key - primary key relation could semantically mean different things. E.g. in banking the acc...
almost 5 years ago in Spotfire Data Virtualization / web services 0 To be Reviewed

Allow contract first for REST/OData

Contract first design of REST/Odata APIs is common in many enterprises. As SOAP contract first is already supported, Contract first in REST would allow us to receive Openapi 3.0 specifications and link the data virtualization to this exact contrac...
about 5 years ago in Spotfire Data Virtualization / web services 0 To be Reviewed
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