Spotfire Analyst - Add more options for opening Spotfire Analyst from protocol call

Opening Spotfire from Spotfire.Dxp.exe or tibcospotfire:server:* does not provide the same functionalities.

Referring to the following articles:

https://community.tibco.com/wiki/tibco-spotfire-analyst-command-line-parameter-reference

https://docs.tibco.com/pub/sfire-analyst/latest/doc/html/en-US/TIB_sfire-analyst_UsersGuide/index.htm#t=save%2Fsave_links_to_analyses_in_the_library.htm&rhsearch=links%20to%20analyses&rhsyns=%20

Spotfire.Dxp.exe is dependent on knowing the Spotfire Analyst initial installation path.

tibcospotfire:server:* does not need to have any input on the full path to the executable file.

Both methods do not support the same options.

For users which are not familiar / do not feel comfortable with editing a batch file to create a shortcut, calling the Spotfire.Dxp.exe should be avoided, and a batch file is overkill for a shortcut to a file.

tibcospotfire:server:* is providing best portability between machines and does not require any maintenance based on the initial Spotfire Analyst version installed. Unfortunately, switches for Spotfire.Dxp.exe, like /username, are not supported when using the protocol call.

Could TIBCO make the switches for Spotfire.Dxp.exe available for the protocol method as well? The /username switch would be the most common use, but the other switches could be more beneficial to administrators.

Eventually add the path to Spotfire.Dxp.exe to a separate environment variable or %PATH%?

For TIBCO staff, please see case #01876712.

Thank you for your consideration.

Kind regards,

Xavier