The Spotler MailPro release 11.13 includes many new updates and bug fixes. Within the Automation module, you now have the ability to automatically archive flows and develop templates. In addition, more features have been released and several bugs have been resolved. Read on for the full release notes.
Automation Updates
MailPro's Automations has multiple new functionalities. These will be explained below.
Automation Layout
When you click on Automations, you'll find three tabs at the top of the page: In Use, Archived, and Templates. In the In Use tab, you'll see all flows that are currently active or inactive. In the Archived tab, you'll find all flows that have been archived. In the Templates tab, you'll find all flows saved as templates for future use.
Templates in Automations
You can now easily create a template from an existing flow. This allows you to use an existing flow as the basis for a new one. Click on More and select Copy as Template; the copy of the flow will then be saved in the Templates tab.
Good to know:
- Templates cannot be published or archived directly, and they are not automatically deleted. This can only be done manually.
- Templates can be saved with all settings from the original flow, including the trigger, steps, and any filters.
Automatically deactivate flows
A feature has been added that ensures flows in MailPro are automatically deactivated. This resolves the issue of flows staying live for a long time, even when they are no longer in use.
When creating a new flow, you can choose between two options:
- Deactivate the flow after a period of inactivity
- Deactivate the flow after a specific date
Good to know
- Flow deactivation after inactivity can be set with various periods. The standard minimum is 3 months after the last activity, and the maximum is 2 years after the last activity.
- You must always choose a deactivation option when creating a new flow.
- The options are mutually exclusive, so you can only choose one of the two.
- You can adjust the deactivation period yourself by selecting the flow options and modifying the period through the menu.
Automatically archive inactive flows
When a flow in the In Use overview has been inactive for 6 months, it will automatically be moved to the new Archived tab. This provides a clearer overview of the different flows. Flows that have been in the archive for 2 months will be automatically and permanently deleted.
Good to know:
- Archived flows can be manually restored or deleted.
- A restored flow will appear back in the In Use tab as a deactivated flow.
- Deactivated flows will be automatically archived after 6 months.
- Archived flows will be permanently deleted after 2 months.
- These time periods cannot be adjusted manually. If you have questions, contact your account manager.
Full release notes
Feature optimizations
- Optimized resource distribution between running Flows
- Increased the speed of the Flow Builder by preventing sending unnecessary requests to the backend and queue
- Increased the speed for loading contacts in groups in Overall campaigns
- Implemented cleanups for AB Test, Batch sendout and Notsent statistics
- Removed the Transfer Encoding and Charset options in the advanced section of the mailing
Bug fixes
- Ensured the calculation of the remaining recipients message when using the restart URL displays the correct amount of recipients
- Removed the broken email client integrations in the mail-a-friend plugin
- Fixed saving numeric values in Flow Builder multicheckbox fields
- Ensured the MX record check on the license local domain validates against the correct records
- Prevented expired licenses attempting to send flow and webhook messages
- Ensured cache of previous license version is deleted while updating license to new version
- Ensured every license uses the same code for processing bounces
- Fixed a bug in the code editor for blocks/templates/layouts using duplicate input group names
- Prevent creating a Landing Page template with an unknown language
- Ensured all Webhooks return date fields in the same timezone
- Prevented showing the “there are no (SMS)mailings defined” message while there are SMS mailings defined
- Fixed Javascript error in the event pages when the decline option isn’t shown
- Prevented text injection via invalid plugin urls