What's new

Release notes for the core platform and the modules, newest first.

Notification Manager

Notification Manager 1.5

Using WhatsApp or Msg91? Save the Meta App Secret and paste Msg91's new report address, or delivery reports are refused.

New

  • Add-ons can attach files to the emails they send, such as a PDF. Only email carries them, through SMTP or AWS SES: up to 10 files and 7 MB per message, of document, spreadsheet, image and text types. A file that is really a program is refused. See How Notification Manager sends notifications.
  • WhatsApp Settings has a new field, App Secret. See Notification Manager settings.
  • The ? Help link on Notification Manager's screens opens the Help Center article for that screen, not the Help Center home. See Open the Help Center.

Changed

  • Needs Laramin 12.7 or later. Upgrade Laramin first.
  • After you upgrade, do these steps for the providers you use. See Check what was sent.
    1. WhatsApp: in your Meta app, open App settings › Basic and copy the App Secret. Paste it in WhatsApp Settings › App Secret and save. Until you do, every delivery report from Meta is refused, and Webhook Center shows a warning.
    2. Msg91: open Notification Manager › Settings › Webhook Center, copy the Msg91 DLR Webhook URL, and paste it in your Msg91 account again. The address now ends in a secret for your Laramin, and the old address is refused. In Msg91's Webhook (New), you can send the secret in an X-Webhook-Token header instead.
    3. Twilio: check that the Auth Token is saved in SMS Settings. Without it, Twilio's delivery reports are refused, and Webhook Center shows a warning.
    4. Meta verify token: your Laramin now has its own, shown on Webhook Center. You only need it if you subscribe the webhook in Meta again.
    5. Server: ask whoever runs your server to run php artisan nm:purge-attachments once a day. It deletes copies of email attachments left behind when a send was stopped, after 48 hours.

Fixed

  • A notification sent to a person in Laramin, as Property CRM sends its team alerts, reaches their email address, phone or device. Before, only the in-app copy arrived, and email, SMS, WhatsApp and push failed. See A notification wasn't sent or didn't arrive.

Security

  • Delivery reports from Twilio, Meta and Msg91 are checked before they change a delivery log. A report that fails the check is refused and changes nothing. Before, anyone who had the address could mark a message delivered, read or failed. Sending isn't affected. See Connect an email, SMS, WhatsApp or push provider.
  • The verify token for Meta is unique to your Laramin, instead of the same for every installation.

Notification Manager

Notification Manager 1.4.2

Notification tab counts match what each tab lists, and an event with no template no longer shows its internal key.

Changed

  • Needs Laramin 12.2.0 or later. Upgrade Laramin first.

Fixed

  • The channel tabs in your notifications count only the messages they list. A message that failed to send was counted but not listed, so a tab could show 1 over an empty list. See Read your notifications.
  • When an event happens that has no template yet, the person no longer sees its internal key. The stand-in message names the event in a plain sentence, and the module's own template replaces it later. A template you've edited is never replaced. See How Notification Manager sends notifications.
  • Stand-in templates written before this release keep their old text, "A system event was triggered: …", and aren't replaced. Find them and write their message yourself. See Edit a message template and send a test.
  • The dashboard's 7-Day Dispatch Trend counts each day in your workspace's time zone, not in UTC. See Check what was sent.
  • The template builder no longer reloads, and shows an error in place of your template, when you go to another screen while it stays open.