Hi Jim,
We use a variable to get short URLs when a given feature is used, so PIN code entry page should be opened with a given code when i=2 is used.
Thanks Ash - so it is basically saying
This is a link with a RescueCode ?
So what are ID=1 and ID=3 used for ?
Anyway to store the Applet on a customer's computer to skip that step EACH time ?
Those IDs are mainly for internal implementation. May I ask what the main concerns are ?
Calling card, Unattended MSI or Connect On Lan features can work as a way to not send a link every time.
ASH
We are wasting a lot of time with each RESCUE connection trying to get the customer staff to pick our custom link (in our app) or a shortcut on the desktop. Then 'Download or Run ?'; Wait for the OK button); etc.
Sending a direct email link helps a bit on the front end but doesn't eliminate the back end steps (above)
We typically have to call to walk them throiugh that step or create an email wrapper to send out the link.
Since you don't offer a ZOOM-like invitation we have to create that - and fume each time. I was hoping that the ID=X might offer a solution.
I have looked at Calling Cards as a solution but have never found a good example video of their use.
We are really looking for a way to have the Rescue client stored on the PC and then no matter who logs on can be prompted to "OK" a connection. A cross between RESCUE and CENTRAL basically. I have been told :Never going to happen !"
Thanks - JIM
Take look at this Calling Card demo on YouTube: https://www.youtube.com/watch?v=J3BIYrDDfuM
There will be more options available around Rescue and GoToAssist later on this year I believe.
