BlueTeam Release Notes:

Transcription

1 BlueTeam Release Notes: BlueTeam version Incidents routed form IAPro to BlueTeam will carry the sender notes to the yellow sticky note available when the BT user opens the incident. 2. Added back the ability to see a Read Only tabbed view of incidents instead of just the printer friendly report. 3. Corrected a situation where additional citizens could not be linked after the initial entry of an incident. 4. Added the ability to turn on the capture of findings and finding date on allegations. There is a new Enhanced Investigations Features setting accessed by the BT Admin to turn this on/off. 5. Added a Filter selection for the EI Dashboard that will allow for only showing employees in a purview that have at least one yellow or red incident status on incident thresholds. 6. Corrected the situation where a deleted incident was retaining Userlog entries and therefore attaching to newly created incidents. BlueTeam version On a password change, the end user was allowed to key more than 12 bytes for the new password. This caused issues since the database only stored 12 and the application would not error indicating that only 12 bytes were stored. The result was that the users would then not be able to get back into BlueTeam with their new password. A limit of 12 was placed on the change password screen to match the database and to prevent this issue from occurring. 2. The default Web.Config file has been changed to show details of BlueTeam errors. 3. Date Expected back causing the DBNull error Two changes have been made to gracefully handle this issue without crashing BlueTeam. The IAPro client also was modified to help with this. This error was caused by Null values in the Date Expected back column on the Incidents table. 4. Corrected a bug related to certain incident types when you click on Involved People you get an error.

2 BlueTeam version Enhancements/Fixes 1. Add hyperlinks in addition to having Drop Down menus for adding the Citizen and Officer linked items. i.e. Allegations, Force types used 2. Cancel" option now available on Vehicle Accidents - Citizen Search. This is now consistent with Vehicle Pursuits. 3. Add signature line on incident report for the originating Officer when chain routing history is suppressed. 4. Added Active Directory support for nested groups. 5. On the printable report - widen sender instructions and routing comments. 6. Show current assignment of Officers on the BlueTeam report. 7. EI Dashboard - Add column headers for each page worth of rows. 8. Fixed error currently affecting the "Assign" option under the IMD. Add Citizen to the IMD display. 9. On Vehicle Pursuit incidents, the Beginning Location and Ending Location drop down fields should also allow entry of free text. This would make the entry consistent with how this is handled for Pursuits entered in IAPro. 10. Change login to support Windows Authentication. 11. Change BlueTeam login process to show better error messages to assist technical support. Instead of just Invalid login/password. 12. Remove "Complainant" and change to "Involved Citizen" for non-investigative incident types. 13. Added password reset feature. 14. Implemented downloadable error.txt (stack trace + current url) when errors occur in BlueTeam. This will give the user a more descriptive error message that can also be saved or sent to CI Technologies. 15. Added the ability to configure a static notification sender host name to work with Office 365.

3 BlueTeam version Enhancements/Fixes 1. Fix the problem where there are orphan ASSOC_INC_CHAIN entries pointing to a delete BlueTeam group causing error. 2. Fix application authentication to check for inactive employee before allowing user to login for the first time. 3. Fixes error with same AD_USER_NAME in the Officer Table will not crash the program now. 4. Fixed LDAP where non-fully qualified username cannot login. 5. Fixed LDAP timeout session crash. 6. Fixed session error if LDAP is enabled and AD_USER_NAME is not equal to UDTEXT24G. 7. Linking citizen now correctly displays "Witness" when adding a witness. 8. Implemented logging of routings from BlueTeam to IAPro. 9. Identifies if LDAP server is unreachable or did not fine use account in the database. 10. Fix issue where pressing Cancel on a forward would result in a Resource Not Found error. 11. Fix an issue related to Active Directory authentication where an apostrophe in the AD USERNAME would fail on the database lookup. 12. Fix an issue where the password reset was incompatible with Oracle due to date formatting. 13. Fix an issue where forwarding back into IAPro would have an incident's field status incorrectly set to "To IA". 14. Change duplicate incident link so that it is always visible to all users who can view the incident. 15. Change Incident Details to show Mark Complete and Re-assign options on main page. 16. Fix issue where a new Citizen entered after a new Incident would replace the actual Incident's address data. 17. Add ordering by date ascending (newest at the bottom) for linked files. 18. A change was made to the sort on the file attachments web form.

4 BlueTeam version Enhancements/Fixes 1. Fix issue with ORACLE installations where the BT Report Url would break due to forced upper casing 2. Added feature in BT Admin page to regenerate all BT Report Urls for appropriate incidents (Those which should have the Urls) 3. Fix issue where a Drug Test incident type would break the application due to a null date field. 4. Fix issue with the download report button not working on the custom error page. This usually only happens with customers running BT on Internet Explorer (Legacy versions). Reduced the amount of information provided by the report (More specifically, removed the SETUP table dump) for security reasons. BlueTeam version Enhancements/Fixes 1. Add running sheet functionality. 2. Fix issue with BT Report URL generation on the admin screen throwing errors. BlueTeam version Enhancements/Fixes 1. Add support for linking a URL address in BlueTeam. (Cloud stored video) 2. Fix some issues where empty date fields on certain screens would cause errors. 3. Fix an issue in file attachment page that was causing compile errors. 4. Add support for enhanced allegations. 5. Fix the take action page where deleting records would cause the page to refresh and cause the area to go back to pg. 1. The area now stays on the same page as what the user was on when the delete button was pressed. 6. Fix an issue with how the version control system reads a configuration file 7. Fix issues with enhanced allegations where not choosing a class would result in no allegations showing. 8. Change the allegation dropdown box to remove the allegations that are already linked.

5 9. Fix issues with text formatting in the summary/narrative page and the Sender s Instructions text areas. It should now retain any formatting if the contents were copied and pasted from an editor such as MS Word. 10. Change the address that BlueTeam uses to send out notifications to be the same one that is configured for IAPro. The web config defaultsenderaddress value is no longer relevant. 11. Add an administrator area in the Notifications configuration area to configure the address. 12. Fix an issue with the body image delete functionality where the business logic would incorrectly use a SQL data command even if the customer is running an Oracle environment. 13. Fix an issue where remnants of the old code would cause an issue when trying to compile the program. BlueTeam version Enhancements/Fixes 1. Changed the login label field to use a different user defined label then what the IAPro client uses for the unique identifier of an employee record, this allows you to set a login label for AD authentication like Network ID that does not change the unique identifier in IAPro on an employee record. Because this new field being used is an existing one it might have old data that will show up on the BlueTeam login screen after upgrading, you can delete this from the BlueTeam administrator login which if empty will use the original field name. 2. Changed the way Active Directory authentication is being handled to fix an issue with groups being used not finding a user. 3. Added a new test module under the Active Directory authentication settings to verify LDAP record search for a user account. 4. Fixed an issue on the password reset screen allowing more than 12 digits causing a truncation error. 5. Added an enhanced embedded SQL connection password for the database connections also backward compatible to the old embedded password.

6 BlueTeam version Enhancements/Fixes 1. The enhanced investigative features option on the administrator screen was incorrectly using an old database column which is now being used for the login screen's username label. Prior to , if an agency was using the enhanced investigative feature, changing the login label would cause issues. 2. The hyperlinks on the Involved People tab was incorrectly displaying links to all linkable 'items' (e.g Citizen/Officer injuries) regardless of incident type. This has been fixed. 3. Duplicate primary key errors when using BlueTeam should finally be addressed. The application will now attempt inserts 200 times (Up from 20) before throwing errors. 4. Creating and updating tasks in BlueTeam (Including the new Running Sheets) are now logged. The exact update details (i.e Summary changed from X to Y) are not logged but dates and the BlueTeam user are. 5. Sending test s and resetting passwords will throw an error about the sender or recipient address being empty for customers that have been upgraded to use the configured sender address on the BlueTeam administrator side. BlueTeam version Enhancements/Fixes 1. Bug fix on the ReviewForward page where reviewers (Chain of Command forwards) would not be able to attach files because the link was hidden. 2. Bug Fix related to enhanced investigations being enabled showing the wrong drop down list. BlueTeam version Enhancements/Fixes 1. Adds a sort feature on the attachments/linked files page. The default sort is done on the attached date but the user can now click on the other columns ("Attachment Description", "Attachment Type", "Folder") to sort by those values as well. 2. Removes the max length restriction on the password field if the agency is running in Active Directory enabled mode. 3. Addresses an issue in LDAP (Active Directory Mode) where BlueTeam will throw a COM exception if the user signing in is not part of any group and a required group is configured.

7 BlueTeam version Enhancements/Fixes 1. Fixed Duplicate incident when there is more than one address attached to incident from IAPro 2. Moved Linked Files above Link URLs 3. Fixed issue when duplicating an incident it was showing the original entry person information instead of the person duplicating the incident. BlueTeam version Enhancements/Fixes 1. Fixed an issue where the Enhanced Investigative Features and Enhance Allegations settings were mismatched. This caused issues with the "Add Allegations" link/page where it would display the allegation class drop down if the Enhanced Investigative Features setting was enabled. 2. Fixed an issue where there was a 120 character limit on the file name when attaching a file. This would cause issues if users were copying and pasting URLs for linked URLs since the underlying storage of both files and URLs is the INC_FILES table. The FULL_NAME column of the INC_FILES table must be widened or else truncation errors will be thrown whenever the user enters a really long URL. 3. Fixed an issue where if the Session-State mode of IIS was anything other than InProc (The default), BlueTeam would throw serialization errors on certain pages due to what was being (Unsuccessfully) saved into the session. More about Session-State can be found at

8 BlueTeam version Enhancements/Fixes 1. In extremely rare cases, a reviewer OFFNUM and the BlueTeam GROUP_NUM will be NULL in an ASSOC_INC_CHAIN record which causes BlueTeam to throw errors. This should never happen in normal circumstances and it might be a data entry issue or a side effect of when we were allowing users to delete BlueTeam groups. If this is detected again, a message will be shown to the user to contact their ID but the app will not break. 2. For ORACLE customers, the EI Dashboard would break because the SQL was using a SQLServer specific function (MONTH). BlueTeam will now use the ORACLE equivalent if it is running against an ORACLE database. 3. There is an issue on the areas where users are allowed to search for officers. It is unconfirmed that this is fixed but refactoring of related areas have been done. 4. Added a 3rd check on the administrator page for file share access. The second check only checks if the location exists; I'm not entirely sure that the second check was validating proper permissions. The 3rd check tries to obtain the access control list from the file path; if this fails, it will indicate that there are permissions lacking. BlueTeam version Enhancements/Fixes 1. Fixes a 500 error when selecting the person to route and incident to. 2. Fixes an error when enhanced allegations are used. 3. Fix the issue that was reported regarding DBNull values in the ReviewForward.aspx page.. 4. Add printable running sheet feature to BlueTeam BlueTeam version Enhancements/Fixes 1. Modify running sheet query so that it identifies running sheets by the TASKS.RUNNING_SHEET column instead of TASKS.FS_TYPE 2. Add pagination to the Take Actions pages; prior to this version, it would display all incidents (This caused long load times where there were incidents assigned to a user) 3. Fix an issue introduced where PageSize instead of PageIndex was being used (Caused errors on page load) 4. Add sorting to some of the columns in the Take Action pages. 5. Fix a SQL typo on one of the TakeAction pages (Missing a space before ORDER BY). 6. Change LDAP authentication so that it uses SamAccountName throughout the process instead of switching to the CN after the initial connection. (Caused an issue with two Active Directory Accounts having the same full name) 7. Fixed an issue with Taser reporting when adding additional cartridge was defaulting to No and not letting you change it.

9 BlueTeam version Enhancements/Fixes 1. Fixed issue in a vehicle pursuit page where the beginning and ending location fields would allow more data than the database could accept they now have been sized to the database column size. 2. Fixed issue with Active Directory setting always requiring a default domain setting, now it will search the Global Catalog for the entire forest in more than one domain. 3. Fixed the way the LDAP query for Active Directory search for group membership using the full name (CN) which caused an issue when two user accounts had the same full name but different SamAccount login names. 4. Remove the pull down menus on involved people/incident links pages and changed wording of the sticky note messages to refer to the hyper link alternatives instead. Also added remove, edit, and change to known officer buttons to replace their equivalent options in the removed pull down menu. 5. Fix a small issue in address duplication where it would duplicate the first address linked for an incident regardless of the LINKSTO column. This would sometimes result in an address that was linked for a citizen to be duplicated instead of the incident address. 6. Fixed an issue when forwarding to IA Unit an error was thrown There is no row at position 0 related to groups. 7. Fixed an issue created in that caused an error when opening Take Action on incidents being routed for review. 8. Started recording the contents of a reminder in the User log. BlueTeam version Enhancements/Fixes 1. Remove the victim_race and victim_sex values being captured on the ASSOC_INC_OFF record. These values were being obtained and set based on the order of citizens and officers being linked and is not accurate. The accurate information can be obtained via the ASSOC_INC_CIT record instead. In addition, IAPro (In earlier versions) utilizes one of those columns to capture the body camera details, the updates resulting from those values being changed in BlueTeam would overwrite the body camera details. 2. Fix issues on the Review and ReviewForward pages where the sender's address was set to be "blueteamfss@..." instead of the configured via the setting in the Administrator login. 3. Also add logging for when a reminder was sent from BlueTeam's UsersUnreviewedChainItemsList page for auditing purposes. 4. Fix a bug where the pagination on UsersUnreviewedChainItemsList page was not working. 5. Add citizen ethnicity support to linking, editing, and reporting pages. 6. Fixed an issue with load balancing web servers and error when searching for a person to forward an incident to. BlueTeam version Enhancements/Fixes

10 1. Addresses an issue where a previous bug fix to address null BT group NUM errors resulted in the printable reports pages showing the BlueTeam group as the Sender/From in the chain history under certain situations. The reports now correctly display the sender officer. 2. Add the ability for users to download linked files attached to an ALERT incident from the Alert Overview (Printable Alert page). These files follow the same access rules as normal incidents (e.g. If routed from IAPro, only the files that the IAPro user selects to be view-able in the field are displayed). 3. Change all report screens to use the IAPro Employee Unique Identifier label for referring to officers. The login, password reset, change password, and administration screens use the new login label configured in the Administrator login on Custom Labels. 4. Added a DLL dependency to SQLServer.Types to address the issue that occurred when a HR process utilized the HierarchyID data type in SQL Server. 5. Added a new CSS rule for textarea elements which should address the no wrap issue some agencies were reporting. BlueTeam version Enhancements/Fixes 1. Fixed issue where on the Add Force Used page (Legacy - without body image), deleting an added force would cause the drop down list to duplicate its options. BlueTeam version Enhancements/Fixes 1. This version addresses an issue where the REVIEWER_TITLE for the ASSOC_INC_CHAIN entries was not being filled out for reviewers that were CC-ed. This version also adds the CC reviewers' assignment at the time of routing as well. 2. Fixed an issue Incidents you authored need to be routed into the chain of command' and 'Incidents that you authored are available to edit' holding ques. The problem is when they click on either one of them it states there are no pending incidents to address BlueTeam version Enhancements/Fixes 1. Large purview, the BlueTeam EI Dashboard takes a very long time to load changed to 20 records per page. 2. Using & issue it is a reserved character in HTML and BlueTeam wasn't encoding it properly before passing it to the next page which causes it to only take the portion before the & (i.e. "A & B" becomes "A ") now fixed. 3. Fixed an issue if the user reassigns (Assigner) an incident to a new assignee, the assignee gets an notification regarding the new incident assignment. If the assigner wasn't the previously assigned investigator, BlueTeam will also send an to the previous investigator regarding the un-assignment. BlueTeam was incorrectly sending the unassignment to the new assignee as well. BlueTeam version Enhancements/Fixes

11 1. Agencies not using a load balancing web servers no longer need to configure fixed URL setting this is now only required for load balancing web servers. BlueTeam version Enhancements/Fixes Fix an issue where if there is not summary for an incident, it would not appear in the listings when a user clicks on a "Take Action" link. The count and the actual number of entries would not match Add a custom Use of Force summary template for New Orleans Police Department Modified notice format adding white spacing in . BlueTeam version Enhancements/Fixes Fixed Notifications test when the.net Runtime was not set to 2.0 BlueTeam version Enhancements/Fixes Added logging for deletions in BlueTeam BlueTeam version Enhancements/Fixes This version addresses an issue with the Filtered EI Dashboard and how the sorting for the rows was missing. It will now sort from OrgLevelA-F assignment, followed by last name and first name of the officers.