Using links

'mobileEcho' links

You can send 'mobilEcho' links for your files and folders to other Files Advanced users. These links cannot bypass permissions or other security measures. The users sharing a link must both be able to connect to the same server, have the same name for the server (e.g. if on one client the name is "Marketing", it must be "Marketing" for the recipient as well) and have access to the file or folder the link is pointing to. To send the link, simply e-mail it to the other user. There are also certain actions that can be used which will trigger when the user opens the link.

The syntax is as follows:

https://server:port(if not the default])/volume/path/path/file?action=action&parameter=parameter

Note: You can use https:// links only with Gateway Servers that are version 7.2.3 or newer.

Note: The old syntax mobilecho://server:port/volume/path/path/file?action=action&parameter=parameter is still valid and will work.

Note: If the file or path shared contains spaces, you may need to create it as a link in your e-mail client and/or surround the address in quotes.

The supported actions are:

edit - opens the file for editing.

e.g.: https://accessserver/Projects/plans.doc?action=edit

preview - opens the file for previewing.

e.g.: https://accessserver/Projects/plans.doc?action=preview

bookmark - bookmarks the folder.

e.g.: https://accessserver/Projects/May2015?action=bookmark

folder - opens the Add Network Folder dialog for the folder specified.

e.g.: https://accessserver/Projects/May2015/Statistics?action=folder

enroll - fills in the user's enrollment information to the specified server.

e.g.: https://accessserver/enroll?name=john&pin=UHDGSX

Microsoft SMB .lnk links

Files Advanced supports Windows .lnk shortcuts in Network Data Sources. The supported Data Source types are On another server (SMB) and On the Gateway Server.

• For SMB, the links must either point to files or folders on the same SMB share as the shortcut.
• For On the Gateway, the links must point to files or folders that reside on the Gateway.

These shortcuts will not work if the shortcut's path is in any way different than the path to the share used to create the Data Source.

e.g. The shortcut is created with a local path (C:\Users\username\smb) or with the full FQDN of the share (\\uadevs.glilabs.com\smb) and the data source on which the content resides is added with just the share path (\\uadevs\smb).