May 09
mtSchedule 3.2
In the April MIS patch cycle, version 3.2 of mtSchedule was shipped. So far the feedback has been very positive. I’m also keeping my fingers crossed because so far there have only been 2 issues with the new version and both of them are in modules we ship the source for so they are field correctable.
For those who are interested, here are the 2 issues:
1: In very specific conditions, if you are using the Custom SAM option, the first item in the list can get corrupted in the Planned Event Editor. If you run into this, CS has a very easy 1 line code change that fixes it.
2: In order to make eCET group notes work with mtSchedule, Client Attendance was changed to always create the ISN register for new events. For users that don’t want this, they can comment out the $isncreate lines in mtClientAtt. There are 2 of them, line 253 for single items and line 989 for group members.
Now for the good stuff. Looking forward to 3.3 and beyond.
In the next version, tentatively called 3.3 and scheduled for the August / September time frame, there are 2 big things we are looking at. The first is adding a config page for Client Attendance and creating CFL hooks in it like the rest of mtSchedule so we can reduce the need for you guys to keep up with our upgrades to the Client Attendance process. There are no plans to close the source for that function, we just want to make it easier to maintain. Looking at the changes between the 3.0/3.1 version and the 3.2 version made me realize the need for that. Second, I’m talking to the mtSchedule Focus Group about the criteria for Check In and Check Out functionality. Check Out would be a extension to Client Attendance. If you want to get your wish list into that process, drop a message into the mtSchedule Focus Group’s list serve.
As always, if there is something you want to see added to mtSchedule, be sure to use the Product Suggestions page from the MIS support website.
Links:
- mtSchedule Focus Group
- Product Suggestions - It’s the next to the last item on the page.
