Skip to Main Content
Spotfire Ideas Portal
Status Future Consideration
Product Spotfire
Created by Guest
Created on Feb 22, 2017

Make Spotfire URLs more user friendly and allow for co-branding

In 7.5 and above when users open a report in Web Player they will see an URL similar to this:

server/spotfire/wp/render/C_nAons1wzreNS-mxU/analysis?file=/ReportPath/ReportName&waid=hJB-6u25O02ACz5uOtCG--211636b4deSuN9&wavid=0

The "C_nAons1wzreNS-mxU" context in the URL and the waid parameter are session values used by the Spotfire server. These are not user friendly and should be removed (session variables can be passed to the server using HTTP query/response headers). 

System administrators should also be able to customise the root level context (aka /spotfire/) to anything they like. A more user friendly URL when viewing a report could be:

server/app1/view/analysis?file=/ReportPath/ReportName

Also if a user browses the library and hover over the three dots, then click on share they will get the following link:

server/spotfire/wp/OpenAnalysis?file=2e07a85b-9479-466f-890d-3cc208935cad

This uses the File ID rather than the report name. This is non user friendly and it means that if we change the report ID the link will not work anymore. While we understand the opposite would happen when using the report name (if the name or location changes the server won't find the report) we prefer it that way.

Thanks

  • Attach files
  • Guest
    Reply
    |
    Nov 22, 2017

    This is even more messy than I thought. In Web Player users are given a very different link as well. If you go to hamburger Menu => Share => Copy link... you will get a link similar to this:

    server/spotfire/wp/ViewAnalysis.aspx?file=[Full Library Path to Report]

    so this is inconsistent with the URL you get when you open a report (server/spotfire/wp/render/C_nAons1wzreNS-mxU/analysis?file=[Full Library Path to Report]), the link you get from the Library share (server/spotfire/wp/OpenAnalysis?file=[Analysis ID]) and the link you get when you save a report from Spotfire Client (server/spotfire/wp/OpenAnalysis?file=[Full Library Path to Report]). So to recap these are all the links a user may see:

    1) server/spotfire/wp/render/C_nAons1wzreNS-mxU/analysis?file=[Full Library Path to Report]
    2) server/spotfire/wp/ViewAnalysis.aspx?file=[Full Library Path to Report]
    3) server/spotfire/wp/OpenAnalysis?file=[Analysis ID]
    4) server/spotfire/wp/OpenAnalysis?file=[Full Library Path to Report]

    1) URL displayed on user's browser while viewing a report

    2) Share from Web Player (hamburger Menu => Share => Copy link... )

    3) Share from Library Browser

    4) Link shown on Spotfire Client after publishing to the Library

    No consistency, 4 different links. This really needs to be fixed! It looks like the Spotfire server guys do not really talk to the Web Player guys.

  • Guest
    Reply
    |
    Aug 7, 2017

    interested in the following:

    System administrators should also be able to customise the root level context (aka /spotfire/) to anything they like. A more user friendly URL when viewing a report could be:

    server/app1/view/analysis?file=/ReportPath/ReportName

    we have a central URL assignment system with wsso. So when I install a product that has a URL "spotfire", it prevents anyone else at the company from installing the same product, because they will also require the use of the root level URL "spotfire". This is a very restrictive assumption that only one team within a company would be able to install something ending in "spotfire". We should be allowed to change this, during installation itself. It asks us to change port numbers if needed, so this root context name should also be allowed to be changed.