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
There are pros and cons for using both the GUID and Library URL. We should have the option of obtaining both URLs as best fits our use case.
We frequently release new versions of our dashboards. When we do this we overwrite our dashboards so if users were using the GUIDs then it wouldn't work for them. We also move our old versions of our dashboards to an archive folder. If the users are using the GUIDs they will see an old version of the dashboard. For our use case using the library URL makes more sense.
I think that the argument here is that you changed the behavior and people liked the old behavior, and there's no way to flip back.
The counter argument to the fact that file names change occasionally is that we we often see new versions of reports being saved with existing names (replacing files) - and often GUIDs will change. We heavily promote using sensible names for reports (no version numbers, for example), and maintaining Library path names is something that the report author is much more in control of - a GUID might change and they would never notice, we've seen that many times since this change happened.
I understand the security argument and I personally agree that promoting the use of GUIDs is more secure - I'm fine with changing aspects of the product that clearly improve it, but this is really just a preference and it should have been implemented as such.
Hi Ian,
One of the reasons behind this decision is that quite often the file name changes, leaving that link useless.
Another reason is that using the filename is considered a security risk, since you may not want to disclose information from the path/filename when sharing the link, and neither make easy to guess the URL for an attacker.
Most actors providing cloud services use unique IDs in form of hashes for identifying their resources that are user generated (documents, diagrams, spreadsheets,...).
I hope this clarifies why we took this decision.
Thanks
This change to use a GUID has made our work really difficult as we relied heavily on the library URL. Can we have this option to switch back please?