When a Read Contacts action (screenshot below) is added to the design, the $MT_CONTACTS page source tree is automatically added to the design. When the action is triggered, contacts from the device's address book are read and stored in the $MT_CONTACTS tree.
When defining the action, you can specify the following:
•Whether to read all contacts, or only one contact on the basis of its ID
•What fields from each contact's data to read and store. Do this by checking the fields that should be read (see screenshot).
|IDs are platform-dependent (and might even be different among versions of a single platform). So, in order to find the ID of a given contact, you will need to read out all contacts (with their IDs) and locate the required ID on the basis of other fields.
|Reading all the fields of all the contacts can consume considerable time and memory. It is recommended therefore to narrow the read-out list to only the fields and contacts that are needed. You can do this, for example, in a two-step process: (i) read names and their IDs; (ii) for the final read-out, read only the desired fields of the desired IDs.
|To simulate a device's address book (in order to run simulations), you can create and use a sample contacts file (see Contacts Sample Files for details). Alternatively, you can use the contacts of your Microsoft Outlook application by selecting the corresponding option in the Simulation tab of the Options dialog.
MobileTogether extension functions
MobileTogether provides a range of XPath extension functions that have been specifically created for use in MobileTogether designs. Some functions can be particularly useful with specific actions. For example, mt-available-languages() returns the languages in which the solution is available and could, for example, be used with the Message Box action. If a function is especially relevant to this action, it is listed below. For a full list of extension functions and their descriptions, see the topic MobileTogether Extension Functions.