About Messaging in the Web Interface

This topic describes the Messaging functions that are supported and unsupported in the Aptify web interface.

Supported Functions

The following Messaging functions are supported in the Aptify web interface, broken down by release:

Aptify 7.x

  • Selecting and Using message templates
  • Saving messages as templates
  • Inserting fields (as shown below) and message parts
  • Configuring the text font, style and color of the message body
  • Add hyperlinks to web sites and email addresses
  • Editing the HTML for the message
  • Attaching PDF copies of Reports to emails
  • Adding attachments to the Aptify Messaging record
  • Message actions, such as generating contact logs for messages sent from the system
  • Launching Aptify Messaging from a record
  •  

See Using Messaging in the Web Interface for more information.

Unsupported Functions and Limitations

The following Messaging functions are unsupported or have limited support in the Aptify web interface, broken down by release:

Aptify 7.x

  • Messages can only be sent from stand-alone views, attempting to send messages from dashboard views or a view on forms will fail to send.
  • Message From Prompted Views: You must select one or more records. If your view has multiple pages, selecting all records on the first page will only send a message against the records on the first page. You have to run the wizard against the first page, then navigate to the following pages, select all records and send the message again.
  • Opening the Bulk Messaging Dialog from a Form: In the Aptify Desktop client, an administrator can configure a service so that when there is a field on a form that is an email, it can open the Aptify Messaging Dialog rather than the user's mail application (i.e., Microsoft Outlook). This functionality is not supported in the Aptify web interface, and the user's mail application is always opened when the Email button is clicked on an Email field. In addition, the user may receive a message to leave the Aptify web interface (when user's default application is Outlook, for example). Clicking OK in this message launches the user's email application.

Aptify strongly recommends that you use an SMTP‐based messaging system, such as the SMTP‐based Dot Net Mail and Dot Net Mail SMTP Client systems, for message scheduling and for bulk messaging rather than Outlook Mail when using the Aptify Desktop client. 

If you decide to use message scheduling with Outlook Mail, note that messages will be sent from the Application Server user’s Outlook account and not from the user who originally composed the message. Also, Outlook may require that no user be logged into the Application Server in order to successfully generate and send bulk messages at the appointed time. Finally, you may need to reduce Outlook’s security settings to allow messages to be sent from Aptify without user intervention.

The Application Server user is the trusted user account who is running the asynchronous processor service. See Administering Application Servers for details. This user account must have an active Outlook account to send Outlook messages using Application Server.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.