about_2_12_beta.txt

Notes re Tickets CAD V2.7 Beta:

1.  The Call Board function provides a display of current incident-unit assignments. (In effect, a Situation Management tool.)  Clicks there will provide a convenient direct link to incident and unit information.  Cleared incidents are shown with a strike-through for 24 hours in order to communicate that information to later shifts.
2.  Incident types are supported, with the few you'll see able to be extended by admin-privileged users as needed.  See note 32. below.
3.  Given a new call/incident, the next screen shows its location against existing response units, plus their straight-line distances and driving directions -  via both text and map.  Driving directions from any unit may be called up, with the closest one shown as the initial default.
4.  In writing up a new call, the automatic lookup is fairly effective for residential land-line phones, names (with city/state information), and street address.  When found, these return map locations.  (AKA geo-coding.)
5.  Any number of units may be committed to a given incident, as well as vice-versa.  A closed incident remains visible for 24 hours with a strike-through - for ready identification.
6.  The Reports function provides for day/week/month/year summaries, with pie-chart displays by location, priority, and incident-type.
7.  The EM Card function allows you access to the default one provided by Bob Austin, or yr own if you have one.
8.  There's a light-weight chat function available, which some teams find useful for in-the-center chat.

To install:
9.  Create an empty MySQL database entry.  You'll need to know its name, the host name, your user name and password.
10. Unzip the tickets_2_7_beta zip into whatever directory from which you plan to run Tickets.
11. Navigate to, say, http://localhost/tickets/install.php -- or its equivalent on your machine.
12. There, you'll be challenged for the database information used in step 9. above.
13. At some point -- maybe this one -- you'll need a valid GMaps API key.  It's free.  Obtain from Google at 
        http://www.google.com/apis/maps/signup.html

After installing but prior to use:

14. Note that the automatically-generated 'admin' account - despite its name - has privileges level of 'super'.  Only such supers can create new user accounts of this level, which shd be rarely done.
15. For security, you should create your user accounts with suitable access privileges: Configuration/Add User.  Remove the automatically-created admin/admin account as soon as you've tested your own account with 'super' priveleges.  Similar for guest/guest.
16. Also for security, you should hide the install.php file.  Unintended access can cause havoc.
17. Set a number of settings, like aprs poll, call board, chat time, login banner, host: Configuration/Edit settings. (Mouseover item to see explanation.)  
18. Set default map center:  Configuration/Set Default Map
19. Incident types: Configuration/Incident types fire, traffic
20. Unit status values: Configuration/Unit status types (available, unavailable)
21. Set map center, etc:  Configuration/Set Default Map  (the lookup city entry can help.)
22. Set GMaps API key:  Configuration/Set GMaps API key if needed.
23. Set Incident types: Configuration/Incident types/Add New In_types entry (ex: Animal, Domestic Violence, Public Nuisance)  Set Group and Sort to control the order within the dropdown list.
24. Set Settings, incl Call Board, chat time Default City, map height and width: Configuration/Settings (Again, mouseover item to see explanation) 
25. Set Response Units: Units/Add a Unit.  Mobile units will require a call sign entry, and these will receive APRS polling.  (Calls must match exactly their aprsworld entry.)
26. Set Unit status values: Config/Unit status types.
27. Set email addresses: Config/Contacts.  You'll need these if you'll be emailing incident data.
28. To apply kml files, insert these into the tickets/kml_files subdirectory.
29. To use your own EMS card file, replace the PDF in the ticket/emd_cards subdirectory. (FYI, Bob Austin will be providing updates to the one currently included.)

Odds and ends:

30: Tickets DOES use popups for certain functions.  These will need to be unblocked.
31. On a Win32 platform, whether IIS or Apache, the mail function is problematic; it may or may not work correctly.
32. The map height and width are user-settable, via item 16 above.
33. In the 'incident types' and 'unit status' drop-down lists, you can set background colors by suitable css settings for the option 'group'.  See the ones already set in default.css .
34. We make extensive use of mouseover hints in a number of places, esp where we need to truncate the data shown.
35. Lots more corrections and improvements to the Units and Call Board  operations.
36. Some performance improvements made.
37. KML file useage is now a settable option. (0/1 for no/yes)
38. New privilege level 'super' added, with potentally dangerous database maintenance options restricted to that level.

Changes from Tickets V2.7 (the immediate predecessor version)

35. LOTS more corrections and improvements to the Units, Call Board, and report features.  Fixed units are now referred to as 'stations', and may have a call sign.
36. APRS functions notably cleaned up.  We now keep the most recent seven days' tracks.
37. Tracks improved, and  allows each mobile unit track to occupy its own window - as many as you have mobile units.
38. On tracked units, the as-of time obtained via APRS data is so identified.
39. The Configuration summary now shows who's logged on, or failed to log off.
40. The Units Edit form now shows the number of active dispatches, if any.  Such would make the unit non-removeable.
41. Reports changed to accommodate gracefully references to deleted units and incidents.
42. Login revised to allow reports to show station login data correctly.

Changes for Tickets V2.7 e
43. The Configuration menu now has a 'Test Callsign' function which allows testing a given callsign for APRS validity.
44. Incident infowindows now provide a direct link to allow a unit to be dispatched.
45. If a given Unit is dispatched, its infowindow now identify the incident being dispatched to, with an active link, and also a link to the dispatch/routes page.  N.B. Units without location information cannot be dispatched.

Changes for Tickets V2.8
46. USNG coordinates are now shown for incidents and unit locations.
47. You now have your choice of display format for coordinates; choice is set in Configuration/Settings (no surprise here). Apply (0) for DDD.ddddd, (1) for DDD MMM SS.ss, (2) for DDD MM.mm .
48. Tracks handling has had a significant cleanup, and now includes a graph of altitudes.
49. The top frame now shows the revised value when a 'setting' is revised and affects the display.
50. Graphics in Incident Reports now display correctly.

Changes for Tickets V2.8 b
51. Tables module was corrected to address reported problems in POST variable handling.
52. Minor corrections to filename includes in the help module.
53. Corrections to ticket EDIT and to APRS functions; 

Changes for Tickets V2.9
54. APRS data handling significantly corrected and improved. Repeated zero-speed posreps are not retained.
55. Dispatch to a unit that has its 'contact via' setting an email address - including one for cellphone texting - generates mail to that address.
56. Cellphones/texting messages will be automatically 'chunked' to reflect the size limit per message.
57. Operator-level users may now perform all needed ticket, unit and dispatch data updates.
59. The database schema was expanded to accommodate expected growth in Tickets capabilities.  Teams and members - with attributes of titles, skills, courses taken, certificates gained, plus document management and photos - are now schema elements, although without any code in this version.
60. 'Notifies' was expanded to accommodate automatic notification via email/texting whenever ANY ticket is edited or written, with a filter for severity.

Changes for Tickets V 2.9 A
61. Primarily a bug correction release.  Lots of odds and ends, including the install process, several in the Call Board operation and in the Zoom mini-map display.

Changes for Tickets V 2.10 C
62. Unit types are now (at last!) variable. You may create any number of types, each unit associated with a type.
63. Phone no. lookup is more effective, using 'White Pages' API in place of Google's.  A default area-code setting is included.
64. The set of 500 icons has been eliminated in favor of dynamic number generation as required.  (Big reduction in zip file size.)
65. The Call Board may now be set to allow a permanent, frame-based display, as an alternative to the floating window, or none.
66. Its operation is a good bit quicker, providing dispatch status setting on-screen with no further navigation. Cleared dispatches may be hidden.
67. Whether a new Ticket goes immediately to the auto-routing function is user-settable.  You may turn that off/on.
68. Ticket serial number identification is now a settable option. The serial may be pre-pended, appended, or not - to the incident name.
69. Users may now write a log entry, of any content, as well as view log contents. Log-file housekeeping was added.
70. Unit icons are identified by letter, distinguishing these from incident icons.  A limit of 26 was raised to two alpha characters.
71. As a security measure, functions buttons are shown only upon login.
72. USNG values may be entered for incident and unit locations.
73. User information hs been significantly expanded to accommodate future team management capabilities.
74. Corrections applied to unit status entries to prevent - as well as accommodate - invalid entries.
75. Reports module now has a report on dispatch performance, plus unit and incident selections.
76. A new user category, 'Member', is available; these are disallowed login, pending team admin functions being made available.
77. Google's Streetview is now available form the add page, on map point selection.
78. Some persistence functions added, notably situation page 'hide units' and also the Call Board's cleared dispatches.
79. Dispatched units may receive email or text msg notification;  message text may be edited prior to release.
80. Terrain map display is now a settings option.

Changes for Tickets V 2.10 D and E
81.  Instamapper interface has been added to support GPS position data from a number of handhelds, notably the blackberry.
		(Which means there no Tickets 'page' for the bb;  We take position data from the Instamapper server as required.)
82.  Support for this interface appears in unit information display.
83.  Units for which driving directions to an incident wd be inappropriate may now be identified, and directions will not be generated.
84.  Editing of generated email is now supported, for both email selected off the incident mini-menu and also upon dispatch.
85.  A 'quick' option setting has been added, which bypasses certain user notification in the interest of rapid operation.
86.  Settings are available to allow default email contents, applicable to noted email and also for 'notify' on new and edited incidents.
    (These are 'msg_text_1' for notify, 'msg_text_2' for incident mini-menu email, and 'msg_text_3' for dispatch notification.) 
    The defaults are set as character strings using the following.  (I cdn't find a more mnemonic scheme.)

			Subject		A
			Incident	B
			Priority	C
			Nature		D
			Written		E
			Updated		F
			Reporter	G
			Phone: 		H
			Status:		I
			Address		J
			Description	K
			Disposition	L
			Start/end	M
			Map coords	N
			Actions		O
			Patients	P
			Host		Q
			
	So, a setting of 'C J D H' wd generate Priority, Address, Nature and Phone no, - in that order - in the to-be-edited message. 
	NB: An empty value is the default; it will generate all of the above, and in that order.
	
87.  A new settings entry - def zoom fixed - allows you to maintain a fixed map and zoom.  Value 0 applies dynamic zoom (original), 
    value 1 fixes only the situation screen, value 2 fixes only the units screen, and value 3 fixes both these screens.

88.  A new settings entry allows you to set the time interval - in hours - during which closed incidents are visible in the 
    Situation screen and cleared dispatches are visible on the Call Board.

Changes for Tickets V 2.10 F

89.  The situation display has been improved to provide more information.  A new popup feature will open a window on the selected 
     incident, with assigned units also shown. Mobile units are distinguished from fixed ones by icon color, black/white.

90.  You may now associate a 'protocol' with each incident type.  The protocol may be whatver category of information your operation 
     finds useful.  It may be the response protocol in, say, vehicle types and manning or specialties, or else the treatment protocol.
     
91.  Mail functions have been significantly improved; 
     (a) mail to all/selected users - 'members' is now available on the Config screen.
     (b) Mail to all/selected respnse units is now available on the Units screen.
     (c) A new settings item, email from, is available.
     (d) SMTP mail connection is now supported, with a test function to assist in getting the connection parameters correct.  See 
         the new configuration/settings value of 'smtp acct'.  Once you have a satisfacory test operation, enter data in a 
         fwd-slash delimited string consisting of the smtp account, the port number, the user account (on that server), and the 
         password.  Your ISP may or may not require a fifth item, a 'from' string. (The following example does NOT show this latter item.)
         
	         outgoing.verizon.net/123/ashore999/whatever


92.  For those of you implementing the Instamapper interface, the Configuration page does have a test function available.

Changes for Tickets V 2.10 G

93.  Google Latitude, LocateA and Gtrack have been added as tracking devices/services. Setting for Gtrack URL is on the configuration page. 
     Selection of the service is added by a convenient drop down list in the page where units are defined. The url for the gtrack server is
     input on the configuration page. If no url is input here, Gtrack will not be shown as an option.

94.  There is a new entry on the units page to allow use of "Handle" IAW user convention. This is in addition to the call sign/license key
     entry which must be the same as used by the chosen tracking service - APRS call sign will often be the same entry as Handle but for services
     such as LocateA, Gtrack, Instamapper and Google Latitude the setting in call sign will in general not be of any use when calling up the
     unit as per local convention and communication type.
     
95.  Test screens have been added which allow testing of the three additional tracking services, accessible from the configuration page. They
     require a valid tracking id to work and in the case of Gtrack, a valid URL. Basic details of how to implement a Gtrack system are included
     in the file "gtrack_readme.txt". The other services are hosted and therefore require little setup besides getting an account and a user ID.

96.  Setting for default Map Type (maptype) allows you to set whether the default view for the Google Map element is standard Roadmap,
     Satellite Map, Terrain Map or Hybrid. Buttons still exist to allow changing from the default during use.

97.  Setting for locale added to configuration settings to allow for the options 0=US, 1=UK, 2=ROW. This determines whether US National Grid, 
     Ordnance Survey National Grid for the UK or UTM grid references are shown. This setting also changes date display on pulldown menu for Add and 
     Edit incident files.

98.  Hiding/showing units on situation display as well as by specific incident priorities is now provided.

99.  User-defined function buttons have now been added, with these appearing when set on the top menu screen. Setting of these function keys is 
     achieved through the configuration page. The entry follows the convention "url, Function Key Text". There is a default setting for function 
     key one of the home page for the OpneISES project. The function keys will bring up a popup window and therefore popups are required (same 
     as for use of Incident popup, Tracks and the EM Card capability). Function keys that have no url or text stored will not show therefore 
     no screen space is taken.  A possible use for this would be to server additional documents stored on the server such as local procedures 
     or training documents.

100. Per suggestion, and to add convenience in adding text to incident synopsis and disposition, we've added links to do so.  You'll see the 
     links on the incident map info-window and also the mini-menu.  Your entered text will be time-stamped.  The text volume is essentially 
     unlimited.
     
101. Incident type attributes has been expanded to allow adding a circle around the incident location.  You may specify circle radius (in miles, 
     color (using the common #rrggbb notation) and opacity (expressed as a number in the range 0-9, but start with 3 to see its effects). Try 
     using a group of these overlapped to identify an area that might be identified as 'do-not-enter', for emergency use.
     
The above may be too terse.  Let us know where further expansion wd be useful.

Changes for Tickets V 2.11 A and B

102. Added Facilities. Facilities are treated by Tickets in two ways, either to be routed to as the main incident location - possible use
     for distribution depots. Location of incident can be set by selecting the incident from a pull down menu - lat and lng are set from
     the facility details. Facilities also have additional information stored such as Security and access details. Facilities have two additonal
     tables to set status and type in a similar manner to units. Facilities have their own icon types to distinguish from incidents and units.
     Facility types and status values are set from the configuration screen.

103. Added ability to set a facility as a receiving point for people from an incident - usefull for EMS, Police or disaster scenarios where
     the facility could be a receiving station. Enhanced the unit status to now include en-route to facility and arrived at facility. Added
     Log events for future reporting against facilities.

104. Added Mail directions to a unit. An operator can either get route details for a facility and without dispatching a unit, email the route
     directions to any of the units or when dispatching a unit to an incident, as well as any other communications can email the directions.
     The directions capability has been enhanced to allow for multi point directions - i.e. current location to incident to receiving facility.

105. Facilities are hidden by default on the situation screen but the markers and sidebar can be displayed by clicking a show facilities link.
     Clicking on the sidebar or marker brings up an infowindow with details of the facility including opening hours, contact, security and
     access details.

106. There is now a "Links" button in the top menu which groups the function keys from 2_10_G under 1 button to save screen room. Clicking the
     "Links" button displays the function keys underneath the main menu buttons.

107. There is a Full Screen popup button in the main menu which opens a full screen map view of the situation map (excluding the sidebar).

108. There is now the ability to set a ticket with a status of "Scheduled". The Scheduled status is for pre-booked calls for some time in the future.
     If the status is set as Scheduled then the ticket will appear on a separate screen. An additional button now appears under the sidebar for
     Scheduled tickets in addition to the closed tickets button. Once a "Scheduled" ticket becomes due, the status can be changed to open and the
     ticket dealt with as normal. It will now appear in the main situation screen. Scheduled tickets retain the coloring by priority of other
     tickets.

109. The Unit and facility indices shown in the lists and on the markers now use a shortened version of the name. How this works is that when
     Entering a name into a unit or facility definition, follow the name with a "/" and three characters. The three characters will show up
     as the index. An example would be to define a new or edit an existing unit or facility and set the name as "Tickets User/T01". The T01
     will show up as the index in the list and on the marker and just the name "Tickets User" will appear as the name in both the lists and
     the infowindows. 

110. A frequent fliers facility has been added - this checks previous "reported by" entries in the database to check for persistent offenders.

111. In the Situation screen and full screen popup you can hide unavailable units. An field has been added to the unit status table to select
     which status types are badged as unavailable and can therfore be hidden.

112. The Scheduled and Closed Incidents buttons on the situation screen under the list of tickets and units are only shown if there are tickets
     in the database that have this status. You will not see the Scheduled Incidents button if there are no Scheduled incidents and in the same way
     the closed incidents button only appears if there are any closed incidents on the database. 

113. The call board has been upgraded to include the times for Facilities en-route and Facilities arrive evemts.  A List option has been added
	 which shows elapsed time from incident start to each call event.  In addition, the report shows color-coded values for those times 
	 exceeding certain threhold values, the latter set-able by users to meet local standards, and set by incident priority.. While dispalyed 
	 values are shown in compact form, cursor 'mouse-over' displays the full value.

Changes for Tickets V 2.11 D

114. A significantly improved multi-user capability:  Buttons in the top panel are 'lit' when an event occurs that 
	 merits user attention.  Specifically, a new incident written by another user will light up the situation button 
	 in red; A unit movement will light up that button in blue; a chat invitation will light up the chat button in red.
	 
	 Lit buttons remain so until clicked, with a red situation button taking precedence over the blue color used to
	 signify Unit movement.
	 
	 Given such notification, the screen refresh is no longer needed, and this function - which can be disruptive - has 
	 been removed.	

115. The situation screen is more informative, and has improved handling for sites with a larger number of units. 
	 The list is now fitted to the screen, with a scrollbar available to navigate the list.  In addition, email 
	 to all or selected units is supported on the situation screen, thus saving a number of steps.
	 
	 Mouseover assigned units displays target incident information, and Mouseover incidents displays incident 
	 address data.
	 
116. The full-screen operation has a revised layout, with an expanded map portion and more intuitive yet reduced 
	 overhead space.

117. This version now accommodates IPV6, the upcoming Internet addressing standard

118. The Chat function is much improved, supporting chat invites and with the above-noted button light-up as 
	 notification of an invitation you've received. You may send invitations to all or to a selected user.
	 
119. The Configuration screen adds information re users, including identification of those currently logged-in.

120. We've revised the 'new Unit' form to help ensure that for tracked units - APRS, Instamapper, etc. - the 
	 correct identification key is entered.

Changes for Tickets V 2.11 E

121. The 'excessive logins' nuisance has been corrected.

122. The Situation screen and the Units module have color-coding added for ready identification of unit type and 
     also status.

123. The Situation screen Units sidebar now sorts curently dispatched units to the top of the list.

124. Hiding Sit screen unavailable units now hides the sidebar list entries as well as their icons.

125. On the Sit screen, you may change unit status directly - no need to navigate to the Units module for that.

126. Units shown in the Routes module appear in order of their straight-line proximity to the incident.

127. Hide/Show of various system elements is now 'remembered' for the duration of your session, instead of 
	 being lost when you navigate away.

128. A 'constituents' table has been added, in which you may load known user locations and associated 
     information, such as apartment number, key location, etc.  Phone no. lookup order is first past tickets, then
     constituent entries, and then white-pages.  (If you already have such a named table, you will need to 
     re-name it for this capability to work.)

129. A 'settings' value for reports pie chart diameter was added, allowing user-specified values when the defaults 
	 require revision in order to meet operational needs. 
	 
130. The Reports module has been expanded to include a new Incident Log' report, which show all of the activities
	 associated with the selected incident.  In addition, the selection form was revised for ease of use.

Changes for Tickets V 2.11 F

131.  Chat works, along with more reliable multi-user operation, notification of new incidents, unit status change, 
	  and unit movement via 'lit-up' buttons.
      
132.  Unavailable units sort to the bottom of the units dispatch list; these may be identified to allow or 
	  disallow dispatch.

133.  Dispatching a unit no longer needs the 'multi' workaround.

134.  'Close_incident' operation has been corrected.

135.  Show/hide 'unit/facility unavailable' now persists for the session duration.

136.  A 'zoom_tight' setting pulls a close-in zoom for incident view/edit. 

137.  A time-of-day clock on the top frame.

138.  The situation screen reports the number of units assigned each incident.  Open (un-dispatched-to)
      incidents blink the count value.  Closed tickets my be selected by time frame (today, this week,
      month, etc.,) and full details are shown for these.

139.  This version includes the (minor) changes needed for operation with asterisk, the Open Source PBX. 

140.  The constituents table provides for apartment no and four phone nos .

141.  Automatic text messages (SMS) are now optimized for size by stripping data captions, possibly 
      reducing the number of tweets. 

142.  This file is now available via link on the Config screen. 

Changes for Tickets V 2.11 G

143.  An audible alarm capability has been added in order to augment the 'lit-button' signal that a new 
      incident has been written or a chat invitation is available.  The default sound files can be changed  
      via settings, and a test popup is available to help choose.  (Sound requires use of recent browsers; 
      IE is not yet supported for this.)

144.  We've added street location information plus geo-coding for both the Units and Facilities modules.

145.  Incident types now include a default priority selection.

146.  A '911 contact' information field has been added to Ticket information.  Letter code 'R' will include
      this field in mail nessages.

147.  Certain SMTP  servers - notably Google's - require a security setting in the parameter strings, which 
      was not accommodated:  Now corrected.  (Users with existing smtp setting will need to adjust these.
      per instructions to be provided separately.)  In addition, the test function use is restricted to 
      super-admin's, as is settings edit.  Thanks due to Kurt Jack for his work on this.
      
148.  Call board operation has been improved with quicker navigation; refresh is limited to the affected frame.       

Changes for Tickets V 2.12  (where to begin?)

149.  A major addition: An internet option has been added, selected via a new setting: 'internet'.  Possible 
      values are 1, 2, 3, these representing respectively yes, no, and maybe.  While the others are 
      self-explanatory, in the 'maybe' setting we test Internet connectivity dynamically at each page load, 
      and operate accordingly WRT maps usage.
      
      Note that in addition to maps not being presented, services such as geo-coding, driving directions, 
      and white pages lookup are not supported.
     
      In the case of no connectivity, new incidents may be written, but sans geo-coding.  When 
      connectivity is restored these location are identified by a red question icon located at your map's
      default center; geo-location can then be made via the edit process.
      
150.  We've added the capability for each site to apply its own terminology and language to many menu items,
      button captions and field names.  See the 'Captions' link on the Config page, which takes you to the 
      selection and edit page. (The replacement text is identical to the base text initially.)  We've 
      included a Restore option for your convenience in testing.  (This capability is partially 
      incomplete; let us know of any gotta-have's.)
      
      We're especially interested in hearing from any of you who've implemented non-English values.

151.  Unit lists now highlight the dispatch status (D R O, etc.) of committed units, as well as the 
      count for units on multiple runs.  We've also added the ability for each site to apply its own 
      terminology for the noted dispatch status display values.  (See setting 'disp stat' for this.)

152.  We've added a 'unit' login capability oriented to use in mobile terminals or smart phones. Button 
      sizes and font are oriented to use with touch-screen devices.  Other user types also have access 
      to this new 'mobile' module, via a new top-frame button.  
      
      In creating a user of type 'unit', a dropdown list of existing units is presented, one of which 
      must be selected in order to be associated with this user.        
      
      In the case of multiple current calls, these are shown in the new page for possible selection.  A 
      unit user's identification is presented on the top frame's navigation buttons.
      
      At login-time, the 'unit' user will be taken to the new 'mobile' module, which provides buttons for 
      setting dispatch and unit status.  Capabilities inappropriate to this unit's operation are restricted.      

153.  Reverse geo-coding - i.e., click a map point to locate nearby addresses where feasible - has been 
      cleaned up to place available information into the page form for facilities and fixed-position
      response units.

154.  The 'quick' mode of operation has been improved by bypassing some previously required clicks.

155.  The logout button has been relocated for improved visibilty.

156.  In order to better accommodate a wide variety of screen widths and map sizes, we've revised the 
      important routes/dispatch module to provide for dragging the group of buttons to any convenient 
      screen position.  These buttons hold position during page scrolling.
      
157.  We've added a setting value which will allow a site to implement its policy re whether an operator/
      dispatcher is allowed to revise incident details.  See setting 'Oper can edit'.

Changes for Tickets V 2.12b

158.  The situation screen has been given a significant re-do, with much flexibility added to hide/show
      the several tables and classes of incidents, units, and facilities. A setting for "group_or_dispatch"
	  allows the use of standard "Available" and "Unavailable" show and hide (determined by the hide setting
	  in the unit_status table) or to use the unit status groupings as the hide and show categories. the 
	  settings for standard are 0 (default) or 1 for status groupings.

159.  We've added the capability to maintain your own table of codes/signals, which may quickly be inserted 
      into several of the information fields used working an incident.  Use the 'Signals' link on the 
	  Config page on this.  You'll have the ability in the New and Edit forms and others.

160.  If you prefer that all outgoing mail go as blind copies:  On Config/Edit settings, append /B to 
      the 'email from' setting;  e.g., 'yrname@gmail.com/B'.   In addition, mail operations now allow using 
	  GMail smtp account.  N.B., that outgoing mail requires valid email addresses for both 'email from' 
	  and 'email reply to'  settings.

161.  You may now dispatch units by capability. On the dispatch menu, entered terms are used to identify 
      units with matching capabilities for dispatching, with 'any' and 'all' options for term matching.

162.  We've added automatic incident numbering, a widely-requested capability and which supports a number 
      of styles, including a fixed string (useful in identifying events) and the current year.  
	  Set it on Config/Incident Numbers.
	  
163.  There is an added link on the configuration screen - Add Tickets Module. This is for future use.	  

And, as always, we've applied a goodly number of corrections and have increased the number of caption 
substitution instances, notably for 'Patient'.

Jan '11
Arnie Shore
Andy Harvey, UK