The request for this came from Steve Moore of Moore Appliance Service.  At first, I did not give him much hope I'd manage to soon work it into my agenda.   Then I realized there's no need to give techs anything like the full Rolodex interface as found in SD.  They just need the info.  It's a much easier nut to crack.

For this feature to be operational, you'll need the presently released versions of both Mobile and MobileLink (or later).  There is a new button on Mobile's Login page, as follows:

Just click on the button, and your system will open a text document that contains essentially all the info (sans physical addresses) from your company's SD Rolodex.  The document is, literally, a file called Rolodex.txt.  It's created by MobileLink, uploaded to our server system, and is downloaded by Mobile and saved into your c:\sd\sdmResourceData folder.  It will open with whatever application is set in your particular Windows setup for association with the ".txt" extension.

We are uncertain whether some managers might wish to keep Rolodex information from their techs.  However, we have doubted it, and for such reason have not presently provided an option to prevent it.  If you are a manager that wants to avoid such sharing, let us know, so we can provide the option.  

What in the heck does "asynchronous" mean?

In the computer world, it means a task is performed in the background while others progress onward in the foreground.  Our major accomplishment in Generation-2 of Mobile is to make most of the data movement, between your Mobile interface and online data store, asynchronous (meaning your interface continues to interact while the data movement proceeds, absent interface disturbance, in the background).

There are a few communication functions we left as synchronous.  One of these was the communication as involved in requesting the RoboCall-based Call-Ahead.  Because we'd so left it, some of you continued getting interface freezes in connection with that particular operation.

This release solves that.  Your call-ahead requests should no longer produce any interface freezes at all.

As the advance in release numbers indicates, we've been busy.  There have not been announcements for each release, because generally each has involved a series of small fixes, none of which warrants direct entry here.  A number of the fixes, too, have involved addressing faults that already existed prior to the 2.x.x series.  A couple of significant fixes in this release are as follows:

Ticket Modifiers (choices to print as estimate, hide all prices but total, hide part numbers, etc.) were functioning correctly for within-Mobile presentation of the ticket, but were having no affect on what was emailed to customer or saved back into SD.  This fault was indeed a series-2-Mobile-introduced problem, and is fixed in this release.

If you've first done a "Save-As," the standard ticket as thereafter created ends with the same signature setup as in your "Save-As."  This was in fact a pre-series-2-Mobile fault, and is likewise addressed in this release.

The current MobileLink application (i.e., as opposed to Mobile) addresses a fault where, on entering the downloaded PVR entry to a JobRecord's narrative history, the prior Tech-Arrived entry was being removed, but not the prior Tech-Departed entry (if you check your narrative histories, you'll find those have been being left there, and should not have been).

There are many other fixes too, that we'll not bother to detail here.