Message systems are systems which process and send the messages created as part of the bulk messaging functionality. Aptify includes three default message systems: Dot Net Mail SMTP Client, Dot Net Mail, and Microsoft Outlook.
The Attachments tab lists any files relevant to the Message Systems record.
The Attributes tab lists any parameters that an administrator can configure to modify the behavior of the Message System. Note that the Dot Net Mail and the Dot Net SMTP Client systems have several attributes that an administrator must configure before an organization can use the Message System. See Configuring Dot Net Mail Attributes and Configuring Dot Net SMTP Client Attributes for details.
The name of the message source is stored in the Name field.
A description of the message source is stored in the Description field.
Create Audit List (Required)
If the Create Audit List option is selected, the system automatically creates an audit list as it processes each message. Otherwise no audit list is created.
Audit lists may increase performance time and could require significant storage space. Thus, audit lists should be created only when needed. See Creating Audit Lists.
The Object field lists the location in the Aptify Object Repository of the object that implements IAptifyMessageSystem.
The Class field lists the class that implements IAptifyMessageSystem, which is contained within the object specified in the Object field.
The .NET assembly name of the object specified in the Object field.
Auto Text Footer
The Auto Text Footer is a special footer that can be automatically appended to text email messages. This field is not supported in this release of Aptify.
Auto HTML Footer
The Auto HTML Footer is a special footer that can be automatically appended to HTMLformatted email messages. This field is not supported in this release of Aptify.
Footer Rule (Required)
The value selected in the Footer Rule field determines how to apply the footer for messages using this system. This field is reserved for future use. Standard options are:
- User Footer: Selected by default. The auto footer defined in the user's Message User Profile is used instead of the system footer.
- System Footer: The auto footer defined in this message system record is used instead of any footers defined in the user's Message User Profile.
- Both: A user footer is applied first, if available, and then the system footer is applied. If both user and system footers are defined, then messages may contain two footers.
Allow From (Required)
If the Allow From option is selected, the user may designate a From address. This field is reserved for future use; by default, a user can specify a From address for Dot Net Mailand Dot Net SMTP Client regardless of this setting. However, Microsoft Outlook does not support this option.
Allow Reply To (Required)
If the Allow Reply To option is selected, the user may designate a Reply To address. This field is reserved for future use; by default, a user can specify a Reply To address regardless of this setting.
Requires Approval (Required)
If the Requires Approval option is selected, messages from this system require approval prior to being sent. Approval of messages requires the approver to manually update Message Runs records to transmit messages.
When selected, this Message System is available for use. When cleared, the Message System is disabled.
Supports HTML (Required)
When selected, this indicates that the Message System can send messages in HTML format. The system sends all messages in HTML format and uses the text version of the message (if specified) as a fall-back option; recipients whose email program does not support HTML receive the text version instead. When cleared, the Message System does not support HTML and all messages are sent in Plain Text.
Address Separator (Required)
This field specifies the character used by the message system to separate multiple email addresses when sending an email message to multiple recipients. This information is used by the View Scheduling functionality.
This tab contains the fields that must be configured to support sending messages at a future date and time. See Scheduling Messages for Future Delivery for more information.
The name of the Application Server that will execute message runs at the specified date and time in the future. This field links to the Application Servers service.
Scheduled Task Service
The service that will create the Scheduled Task that determines when to send the messages in a message run. This field links to the Scheduled Task Services service. Organizations that want all users to be able to schedule messages for future delivery should use the Remote Scheduler service.
Scheduled Task Category
The category that is assigned to Scheduled Tasks records that are created for future delivery message runs that use this message system. This field links to the Scheduled Task Categories service.
Job Account Name
The Aptify user account that the Scheduled Task uses to create a Process Flow Runs record.
Job Account Password
The password for the specified Job Account user. Note that this password is encrypted. Therefore, any user who will use the delayed message delivery feature needs access to the security key that encrypts this password (as well as the access to the security key that encrypts the Scheduled Tasks entity's Job Account Password field, if a different key). See Scheduling Messages for Future Delivery for details.