Spotfire Ideas Portal
Add a new idea Subscribe
Status Future Consideration
Product Spotfire
Categories Scripting
Created by Guest
Created on Sep 21, 2022

RELATED IDEAS

Download Containers for Script

Problem Statement

There have been many situations where Developers were asked to generate some kind of file dynamically(Formatted Excel, PDF from Data Function, Images generated from scripts, Word Reports etc.). Mostly it is easy to do so, but problem arises when they ask an option to download same via webplayer.

Solution Proposed

Spotfire should have a Download container, that can be bound to action controls which -

  • Receives input of type file, generated as Data Function Output (A document property)

  • Starts downloading that object bound with action control(similar to PDF extract right now)

From security perspective, file extension can be whitelisted/blacklisted. For example,

Whitelist

.jpg , .jpeg, .png, .bmp, .gif,

.mp4 , .mp3 , .wav

.pdf

.xls , .xlsx, .xlsm, .doc , .docx , .ppt, .pptx

.txt, .csv

Blacklist

.exe , .py, .cmd , .sh , .bat , .vbs

  • Attach files
  • Guest
    Reply
    |     Sep 24, 2022

    Hi Miguel,
    I am talking about the dynamically generated item only.

    Something like this :

    • Add a line of code to trigger download at client browser
      Application.DownloadFromWebplayer(fileObject)


    or

    • A script output of type Download, when changed- it will trigger a download at webplayer end.

  • Admin
    Miguel Díez
    Reply
    |     Sep 23, 2022

    Hi Vivek,

    Please, could you clarify a little bit?

    You are not talking about downloading containers but about a download menu option, right?

    And, is it about being able to download an existing library item or a dynamically generated one from the analysis or both?

    Thanks

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