Version 1.7.14 of Bill-O-Matic for Schools

O-matic Software is proud to announce the release of version 1.7.11 of Bill-O-Matic for Schools. This version has many, many updates, including all but one of the suggestions made by users on our UserVoice feedback site. We hope you enjoy this new version and look forward to hearing your feedback.

CHANGE LOG ---- V 1.7.11 21DEC2011
- Fixed bug "File not found" when previewing statements or receipts
- Added support for multiple attachments when sending emails
- Added option to BCC all recipients to hide emails from recipients
- Added Save As option to email templates
- Added report type of Projected Statements for SB
- Default Statements and Projected Statements "Include Recipients receiving" option to "Statements Only - no copies"
- Removed check box for Include Grid Lines on Statement, this will happen automatically by design
- Fixed bug with email template drop down not refreshing after adding/removing templates
- Added support for additional blank page formats on Statements and Projected Statements
- Reduced the need to reload the grid when making changes to settings or recipients
- Improved error handling when fetching records from query (Show Results button)
- Fixed bug: Actions were not added to recipients for RO emails when the "Get email address from relationship record(s)" option was NOT checked
- Fixed bug: Action type for SB Statements was not saving
- Added functionality to replace "AccountID=#&StudentFirst=#&StudentLast=#" with "AccountID={%ACCT%}&StudentFirst={%FIRST_NAME%}&StudentLast={%LAST_NAME%}" when entering a Payment URL, Replace occurs when leaving the field and during save
- Changed text on email template Help button to "Mail Merge"
- BillOMatic.tlb will now automatically copy to the Custom folder during the installation
- Fixed bug: loading template dropdown after the selected item was deleted in settings
- If "Create Output Query" option is selected in the report parameters it will now be ignored in BOM for all reports
- New statement and receipt background files added as defaults, improved support for custom receipt backgrounds
- Added code to suppress the printing of report criteria on RO Schedules and Infraction reports
- Added code to remove commas and colons from the name added to payment link when sending statements
- Improved performance while loading results grid for all report types
- Added password protection option for statements and projected statements
- Enhanced grid to reflect the password status when running password protected reports, it will now display red text on a grey background if a password cannot be generated.
- Added tooltips to indicated why rows are disabled in the grid (no email, or no password)
- Added mail merge fields for both RO and SB passwords
- Added new report formats to improve cleanup of temp files
- Reversed positions of the query and report format drop down lists
- Added Query Search to right click menu on Query drop down list
- Import Payments: Fixed issue with message "Default comment from deposit not showing on payment"
- Import Payments: Use payment type in DiamondMind file (cc = Credit Card or ck = Received EFT) instead of defaulting to CC
- Import Payments: Payment comment set in this order: In file, Default on Deposit record, Default from SB->Config->Biz Rules->Payment->Default statement description
- Import Payments: Use transaction date from file unless field is read only due to the GL->Config->Biz Rules->Transaction->Do not allow post dates to be different from transaction dates
- Import Payments: Added option to include payer name in the comments field
- Import Payments: Added code to disable the auto-select single match search results
- Import Payments: Added functionality to open search form if the ID in the file doesn't match a record in the database

V 1.7.14 05JAN2012
- Fixed issue with grid that caused emails to not be sent in certain environments

***PLEASE NOTE - some clients have reported that BOM does not appear in Plug-ins list after the update. If this occurs, please run setup.exe file AGAIN and select the repair option to fix the issue. ***

***PLEASE NOTE - we have resolved a separate UI issue discovered in 1.7.11 and updated the release version to 1.7.14.***
Login or Signup to post a comment