Version 2 (Beta 1.7) Campaign Busy!
With the upcoming March 2010 Memorial campaign, we have been busy having our territory up-and-ready in time for the campaign. We have an average 160 territories and we needed a simple way to print all of them. This is why we came up with the Version 2.0 (Beta 1.6.)
However, after we printed our territories, all 160, our very helpful territory servant found it hard to distribute these among our 10 field service groups. Our servant wanted to distribute these by Territory Number per field service group. For example: Assign Territory 1A, 1B, 1C and so-on to Field Service group 1. And then assign Territory 2A, 2B, 2C and so-on to Field service group 2.
Nonetheless, because Beta 1.6’s new “Print All’ feature does not separate these by Territory number, we had to device a way to group our Territory by number. Which brings us now to Beta 1.7 which features the new “Group by Territory Number.”
In addition, we have not forgotten about the Territory Administration aspect of it either. We’ve added a default value when ‘checking-out’ territories, thanks to one our users who included that suggestion here on this site.
BETA 1.7
===========================
HOUSE-TO-HOUSE Control Panel
——————
- View and Print by Territory Sets. For example, select the ‘Group by Number’, choose Territory Number 1. Then you can view/Print all Territories nested under #1 (e.g. 1A, 1B, 1C.)
- Corrected all House-Record symbol translations (e.g NH – Not at home, W – Woman, M-Man). This is now integrated with the MultiLanguage Form. In other words, you can custom translate this using the included Translation form.
- Optimized queries. Should see improved performance.
- Better S-8-S PDF Print layout.
- Fixed Alphabetized Phone Card.
- Fixed Last Name, First Name and Middle Initial columns for list views.
ARCHIVE
—————–
- We now included a default value of ‘House-to-House’ when adding records to the Territory Archives.
TRANSLATION FORM
—————————
- Fixed and improved Translation Value Fields. Added more reset buttons incase a user breaks the value code.
Note: New users will still need the back-end database. See T2K Beta considerations for more information.
