SendAs Tutorial

Required background

This tutorial assumes that you have a good understanding of SendAs.

Introduction

The SendAs Server maintains all SendAs entries and controls the access to a message store. It allows client applications to create messages in the Drafts folder of the message store. The SendAs API allows a client application to launch an appropriate message editor for a given message type. There are two methods of sending messages: confirmed and unconfirmed send. Confirmed send requires confirmation by the UI MTM which typically asks the phone user. Unconfirmed send does not require confirmation by the UI MTM.

The main client-side classes of SendAs are RSendAs and RSendAsMessage . RSendAs is used to establish a session with the SendAs Server and to find the available message types and services. RSendAsMessage is used to create, set and send messages.

Client applications do not require any capabilities to use the RSendAs and RSendAsMessage classes. However, if an application does not have the necessary security capabilities to send a message, the SendAs Server ensures that a message is only sent with the user's authorization. See SendAs Overview for more information.

Procedure

1. Create a session with the SendAs Server.

2. Select from a list of available MTMs and accounts.

3. Create and populate a message.

4. Send the message.