The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. TRM Technology, obtained from the vendor (or from the release source). The Vendor Release table provides the known releases for the For additional information or assistance regarding Section 508, please contact the Section 508 Office at Decisions Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. This technology has not been assessed by the Section 508 Office. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation. Users must ensure sensitive data is properly protected in compliance with all VA regulations. Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 61 VA Directives 6004, 6513, and 6517 and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Also, this technology shortens the time taken to process mail and electronic media. This technology gives users the ability to optimize workflow processes in a data secure manner. More information on the proper use of the TRM can be found on theĪutomail allows users to design, process, and deliver documents. In order to customize the entity or document that you wish to use with your own functionality, you can do so by extending TSS\Automailer\Model\Automailer and adding the relevant or annotation to your class.Technologies must be operated and maintained in accordance with Federal and Department security and You can easily customize the class used for the entity or document by simply configuring the class in config.yml and disabling the relevant functionality like this: tss_automailer:Ĭlass: AppBundle\Entity\Automailer # or AppBundle\Document\Automailer, your specific path to your entity or documentĭisable_default_document: true # disables the default document so that you can use your ownĭisable_default_entity: true # disables the default entity so that you can use your own Manager: doctrine_managerĬlass: TSS\AutomailerBundle\DefaultDocument\Automailer
You can also customize the entity manager: tss_automailer: This feature is activated automatically once a new email is sent through mailer, if pheanstalk is installed and if you add this inside. You can also test the spool by adding a new email with: app/console automailer:test has also a Beanstalk integration feature, which uses pheanstalk to send a job with automailer:spool:send to a queue/tube. Set a cron to execute the queue: app/console automailer:spool:send
app/config.yml:Īpp/console doctrine:schema:update -force New TSS\AutomailerBundle\TSSAutomailerBundle(),
Easiest way to install is via composer, add those lines to.Swiftmailer Spool for Doctrine packaged into a Symfony2 Bundle