Released January 30, 2010
Dear OA LodgeMaster Users,
The OA LodgeMaster team is happy to announce the immediate release of Version 2.0.2! We've fixed all the open bugs that users reported since the release of version 2.0.1.
Go to https://lodgemaster.oa-bsa.org/softwareupdate/ to download the update. You don't need to reinstall anything; the update is just over 1 meg in size and runs in just a couple seconds. As always, if you have questions or problems, please submit a request online (http://support.oalodgemaster.org).
Yours in Brotherhood,
The OA LodgeMaster Team
Mike (C.), Mike (G.), Mike (P.), Rob (A.), Rob (R.), and Scott (J.)
Over 60 bugs reported by users were fixed in this release. A small number of minor changes / improvements were also made:
- The newly added member flags from the 2.0 release were added to the individual history report and membership exports.
- A consistent problem for some users, label and membership cards have been updated, and hopefully the new format will no longer cause margin or 'creep' issues for some users.
- Quality lodge 2010 requirements have been added to the program.
- At the request of many users, when ordeal or brotherhood is completed in event manager, the council field is now populated with the current council.
The detail of the bugs and their related module are below:
#313 Populate Council When Completing Level
#252 Auto Center Event Manager Window
#254 Role Selection Box Can't Be Changed
#255 Event Manager Scroll Bar Always Visible
#244 Event Report Wizard Error
#202 Clan Report Missing Data
#298 Registered Names Refresh Very Slowly
#259 Attendee Details Shows #Error If No DOB
#262 Duplicate Member Registrations Showing Wrong Data
#267 Report Date Column Width Needs To Be Increased
#294 Error Selecting Member In Event Manager (Large Lodges)
#227 Dues Year Box Entry
#312 Error Editing Service Hours
#299 Duplicate Event Registration Check Missing
#265 Event Permissions Not Enforced In Membership Manager
#314 Vigil Fields Renamed
#209 Brotherhood Statistics Error And Missing Data
#321 Ordeal Statistics Blank
#228 Missing Flags In Individual History Report
#268 Individual History Report Data Missing
#270 Troop Rep. Header Incorrect
#243 Error Closing Dues Trends For Multiple Years
#242 Report Actions Not Closing
Importing & Exporting:
#238 Error Exporting Events When Selecting Different Options
#210 Add Attendee Notes To Event Export
#219 Add New Flag Fields To Export
#297 Data Import Unit Logic Error
#290 Excel Export File Extension
Labels & Membership Cards:
#311 Label & Memb. Card Sizing Issue
#287 Chapter Labels Printing Entire Lodge
#289 Dues Paid Thru On Labels Incorrect
#247 Membership Card Chapter Sorting Issue
#322 Add 2010 Requirements
#296 Quality Lodge Wizard Error
#293 Quality Lodge Including Deceased And Inactive
#234 Split Memo - All Splits For Transaction Updated
#235 Split Negative Amount
#236 Cash Flow Report - No Account Transfers
#237 Budgeting Form - Select Budget Year
#303 Finance Manager Hangs When Maximized
#305 Default Budget Year
#306 Budget Year Changes
#302 Report Date Width Needs To Be Increased
#250 Account Activity Date Range Error
#323 Category Updates Wrong - Category Tab
#295 Category Order Error
Non-January Membership Start Months:
#257 Elected Induction Count Includes New Ordeal Count
#263 Dues Paid Year in Red for Current Membership Year
#291 Youth and Adult Calculations
#246 Membership Audit Date Column Error
#320 Login Error Message Spelling
#245 Error Deleting Chapter With No Name
#310 Selecting Member In Asset Manager
For the desktop client, we are working on a couple of enhancements: local networking (which has been coded and we've begun testing on, and should be released March 1st). We're also working on releasing ceremonies manager and an updated inventory manager on April 1st.
For the online portal, we're working on a number of enhancements to the membership reporting tool, and later this year, will begin building additional modules for the portal.
We're also working on updating the support center and preparing the new documentation website.
Please submit a ticket on the help desk if you have any questions - this will allow each of the team members to respond as they have time - instead of sending all questions to one member of the development team. You can submit a ticket online (http://support.oalodgemaster.org) or via email at email@example.com.