Skip to main content
All CollectionsReport SenderRelease Notes
Report Sender v1.73 - August '23 Major Release
Report Sender v1.73 - August '23 Major Release

A bunch of improvements for Report Sender users

Updated over a year ago

In this release, we're adding several of our most-requested enhancements - CC/BCC, date/time merge fields, and additional schedule options! Report Sender is also getting some bug fixes to make sure your reports get delivered exactly when and how you expect them.
​

Release Schedule

  • August 14, 2023 - Automatically pushed to all sandboxes.
    ​

  • August 21, 2023 - Automatically pushed to all production orgs.
    ​

  • August 9, 2023 - Available on the AppExchange.
    ​

Can't wait? Upgrade now: Sandbox | Production


Release Notes

Use Dates in the Email Subject and File Name

One of our most requested features is now available! You can now use a merge field to insert the current date or date/time into the email subject or file name when the email is sent.

See the Date and DateTime merge fields help article for full instructions.

New Schedule Options - Hourly, Quarterly, Annual

Want to get a report every hour during the work day - now you can! Or maybe you need a quarterly deal report delivered at the end of the quarter. How about some annual financial metrics delivered just when you need them to close out the books? Whatever your situation, we probably have a schedule that works for you.

Hourly

When setting up an hourly job, you can choose the start and end times and which days it should run. So if you really need the updates all day, every day, you can do that.

Quarterly

For quarterly schedules, we let you choose the first or last day of the quarter. Remember to set up your report properly to match whatever you choose here - if you choose the first day of the quarter, but your report says "Current FQ," that works if you're reporting on something like upcoming Campaigns but probably won't work well if you are reporting on records created or something backward-looking. Here's a quick cheat sheet:

If you want to look back in time:

Day of Quarter

Suggested Date Filter in Report

First

Previous FQ

Last

Current FQ

If you want to look forward in time:

Day of Quarter

Suggested Date Filter in Report

First

Current FQ (or Current and Next FQ)

Last

Next FQ

Annually

Annual schedules are pretty simple - choose what time of day and day of the year you want it to send. And then wait until that special day comes around again.

More Recipient Options

You can now send to any Email Address, Contact, User, or Public Group. You can even mix and match - send to a public group and some emails, send to some contacts and users - it's all up to you now.

CC and BCC Support

Now when sending emails, you have access to the standard recipient email fields - To, CC, and BCC. BCC is a great way to send to multiple recipients without sharing emails with each other or to add on a compliance email that gets a copy of every report. You can even BCC yourself to make sure the schedule was set up correctly.

Note: If you're using the Salesforce feature for compliance emails for all emails, we cannot detect this, so it is up to you to check this setting or test using the BCC first.

Report Sender Administrator Permission Set

Previously, Report Sender only came with one permission set and this was assigned to everyone. This meant that everyone could activate and deactivate Report Sender. This rarely caused a problem, but when it did, it stopped everyone's reports from sending. So this package now includes a CloudAnswers Report Sender Administrator permission set. We recommend only assigning this to the users that need to Activate and Deactivate Report Sender. We'll be adding more permissions to this permission set as we add more global settings in the future.

Improved Logging

We've been working hard on making it easier to find out what's going on with your Report Schedules on the rare occasion that they don't send as you expected. We have some more work coming, but in this version, you can now create Reports on Report Sender Logs. So, if you're trying to troubleshoot any failures and you can't find the error email we sent you, try a report on Report Sender Logs.

Note: Report Sender Logs are deleted after 30 days. To change the retention period, go to Setup > Custom Settings and click Manage next to Log Settings.

Lightning Web Security Support

Report Sender now works with Lightning Web Security. So if you disabled Lightning Web Security because of Report Sender, you can now turn it back on. We recommend testing all of your Salesforce customizations in a sandbox before enabling it, but Report Sender now supports the latest security framework from Salesforce.

Checking for Inactive Owners

We all know it happens - someone leaves the company, and you forget everything that is tied to their user. It's ok, it happens to the best of us. Before, Report Sender would email you after the report failed to send, which is good but not very proactive. Now, when you go to Report Sender, we'll notify you if there are schedules assigned to an inactive user.

Bug Fixes

We've also been busy squashing bugs. Here are the latest fixes:

  • Reports sent on the last day of the month near the end of the day are now sent with the sending user's time zone so that they do not send a day early due to server time.

  • After the free trial ends or if you downgrade to the free edition, any schedules using an org-wide email now revert to the "Scheduled As" user email. Previously they were using the Running User.

  • We fixed some formatting issues on the free trial message for new customers.

  • Now when changing the report, we don't change the file format.

  • Support for 50k report folders! Yes, some of our clients have over 50,000 report folders, and Report Sender was not set up to handle that before, but now it is.

  • Checking report availability was done by the Running User in some situations, which is now fixed always to use the Scheduled As user to confirm report availability.

  • Fixed an issue sending reports with <script> tags in the contents.

Did this answer your question?