2030.990/995

--- Requires ---
--- .Net 4.8 or Later ---
--- Runs on any Windows Machine or Server ---
--- Report Runner supports Crystal Reports 8.5, 9, 10, XI/11, XI R2/11.5, 2008, 2011, 2013, 2016, 2020, and 2025 ---

Warning: You should NOT update during production. In general, our updates do not require rebooting the machine/server, but if anything is using our software during an update, you will get a notice to reboot the machine. You should ONLY update when no production is running and the machine can be rebooted if necessary.

DO NOT DOWNLOAD UNLESS YOU CLEARLY UNDERSTAND THE BREAKING CHANGES IN THIS RELEASE!
(This does NOT apply to new customers or 45 Day Evaluations)

There are a few BREAKING CHANGES in this release. We have taken a lot of pride in the past of always being backwards compatible and never releasing anything that would break production. This release is different. While everything is still 99% compatible, here are the new/updated features/changes to be aware of BEFORE UPDATING:

.Net 4.8 or 4.8.1 is now required. This won't be an issue for most of you, but previously we only required .Net 4.6. .Net 4.8 has been available since 2019.
If you have configured ANY kind of TOKEN PROCESSING previously to send mail (either Microsoft or Google), those tokens will NOT WORK with this release. You need to RE-CREATE your tokens, and the tokens interface now ONLY SUPPORTS Microsoft MSAL/Graph tokens.
If you have configured ANY kind of Microsoft Sharepoint Online processing with an ID and password, that will NOT WORK with this release. Those batch jobs will fail. ALL Sharepoint Online connections are now ONLY token-based, and you must CREATE a token to do the processing. We do NOT SUPPORT ID and password at all for Sharepoint Online accounts any more.
Lastly, if you do use the new Microsoft MSAL/Graph tokens for emailing or Sharepoint Online, and you SCHEDULE the batch, you MUST USE the SAME Windows ID/account to schedule as you did to create the token. You can not, for example, create a token and then schedule with the System account. Microsoft doesn't allow tokens to be renewed by a different account (tokens must be renewed by the same account that created it). We went with personal tokens vs some broader-based token, because they are much easier to manage and approve, and we've found the renewal process to be flawless if the same Windows account is running the account at the time.
If anyone NEEDS to stay on 2030.980/985 due to not being able to upgrade to .Net 4.8 and/or email/Sharepoint is working just fine... you will not be forced to update. Of course, any of the features/changes below will ONLY be available with 2030.990/995 and later (and of course there will never be any kind separate/extra update to 2030.980/985) should something stop working.