A component designed to send emails.
Send mail from queues.
You most commonly use this component as a menu item job with that runs continuously.
Statement to extract e-mail information. Each row in the first resultset corresponds to an e-mail. Each row in the remaining resultsets corresponds to an attachment, and all attachments are attached to all e-mails.
The component will make this call repeatedly until it reaches maxminutes or receives an empty resultset.
Statement that is executed after each e-mail to confirm that the email was sent (no resultset is expected), this database call is only executed if the column 'emailid' is returned in SQL (database call 2).
Call made when an e-mail failed to be sent.
|1||No recipients found.|
|2||The mail message contains invalid data such as NULL in body column.|
|3||At least one attachment wasn't generated correctly.|
Allows you to validate the parameters supplied by the user before any other SQL is run in the component. This call is only made if the component has visible parameters, the SQL is a stored procedure, and 'Validate parameters' is checked.
Use this call to restrict which entries a user is allowed to view and edit, and to log which entries a user views.
Access to a menu item is normally controlled through functions and roles alone but some entities need more fine grained control. For example, a user may have access to the View Member menu item for normal members but not for members with a protected identity.
The menu items a user visits are always logged (in ADMINLogMenuItem) but for sensitive data you may need to log exactly what entries are viewed. Do the logging in this call as the common ways of viewing data (grid and InfoSQL) are not allowed to modify the database.
If you bind a scalar function instead of a stored procedure to this call then its name must end with '_GrantAccess'.