This section describes some of the Messaging features and their functionality in the Aptify web interface, including areas that are not supported.
See Using Messaging in the Web Interface for more information about the supported Messaging feature.
Messaging Functions Not Supported and Limitations
- In Aptify version 5.5.1 and up, 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 (Version 5.5.1 and up): 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.
- Message Actions (Version 5.5.2): Message actions are not populated automatically based on the template or message source. However, you can add them manually before sending the message.
- Message Actions (Version 5.5.1): This is not supported.
- Adding Attachments (Version 5.5.1 and up)
- Adding Reports (Version 5.5.1 and up)
- Scheduled a Message for Future Delivery (Version 5.5.1 and up)
- Message Confirmation Dialog (Version 5.5.1 and up)
- Message Status Bar (Version 5.5.1 and up)
- Specifying Message Dialog From a Form (Version 5.5.1 and up): 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., Outlook). This is not supported in this release, the user's mail application is always open when click the Email button on an Email field. In addition, the user may receive a message to leave the web application (when user's default application is Outlook, for example). Clicking OK will launch the user's email application.