v2024.01.16.1

What's Changed

Bug Fixes

• Fixed an issue with version calculation that caused errors when administrators tried to perform certain functions from the admin screen.
• Fixed some location logic regarding latitude and longitude. Users can no longer enter lat/long and may only request it via the built-in button. If current location is used it does not fill in lat/long anymore.
• Before creating a new user the API will check if the user exists. This should prevent officer IDs from changing in the case of very slow networks that drop GetUser requests.
• Validation now requires a basis for search explanation when the reason for search is "Condition of Parole" matching the error codes from the CA-DOJ.
• Version 1 stops will now load when navigating to the admin stops screen. The switch will change between version 1 and version 2 stops.

Features

• Before downloading Statute, City, and School data the application will check the "last updated" date on the API. This reduces the amount of times the application will need to download this data, which can take around 30 seconds and should improve initializing the application when logging in throughout the day.
• Expired statutes will now display if an administrator is editing the stop. This allows administrators to see if statutes require updates before resubmitting to the CA-DOJ.

v2023.12.19.2

What's Changed

Bug Fixes

• Fixed an issue with uploading the CLEW spreadsheet. Users are now be able to upload the unmodified CLEW spreadsheet to update domain data.
• Fixed an issue that prevented administrators from updating user profiles from the admin screen.
• Fixed an issue that prevented submission of stops created before the regulation updates.
• Fixed an issue with creating new users after importing legacy users.
• Fixed an issue causing stop audits to display audits not associated with the selected stop.
• Fixed an issue that prevented Beat IDs from containing letters.

v2023.12.07.1

What's Changed

Bug Fixes

• Fixed an issue when updating that app in the middle of stop by clearing local storage.
• Fixed an issue causing the application to improperly determine the browser was offline.
• Fixed an issue causing new user creation to fail if legacy officer IDs contained letters.
• Fixed an issue with importing legacy users via the import feature.
• Fixed an issue retrieving legacy stops in stop audits and submissions.

v2023.11.15.2

What's Changed

Updated AB 953 regulation

Breaking Changes

• After January 1st 2024 favorites will need to be recreated due regulation changes that change data properties of the stop.

Features

• Compliance with AB 953 amended regulations for 2024.
• Beginning January 1st, 2024 new stops will be created with additional data properties required by the amended regulations.
• Top 5 Favorites. Buttons have been added below the favorites menu items showing the top 5 favorites used for quick access.
• Favorites with expired statutes, cities, or schools are now highlighted.
• Back/Next buttons added at the top of the form in mobile view.
• Improved user experience by adding yes/no labels to switches.
• Admin: Added the ability to flag stops as "No Further Information Available".

DOJ Testing

• Contact our team to find out more about quick test templates to help with your agency's DOJ testing

v2023.05.19.1

What's Changed

Bug Fixes

• Fixed an issue that caused the user information dialog to pop up when the API was unavailable preventing overwriting of user data.

v2023.03.08.2

What's Changed

Features

• Added caching to domain data retrieval upon opening the application to improve performance.

Bug Fixes

• Fixed an issue with importing domain data from CLEW that prevented updated data from being imported correctly.

v2022.11.14.1

What's Changed

User Interface

• Stops are now submitted immediately if the user is online and a loading indicator was added. Previously, this happened in the background making the process unclear to users.
• In order to create offline stops the user must log in before going offline. After the user is logged in they will have around one hour of offline capabilities before needing to log in again.
• When stops are created offline they will be processed when the user returns online. There is now a loading indicator when offline stops are processing to prevent the users from closing the application, potentially creating errored stops.

Admin Page

• Fixed a bug regarding the pending status for submitted stops to the CA-DOJ. Once a stop is submitted to the CA-DOJ it will enter the pending status until it is processed. This prevents duplicate submissions.

v2022.07.21

What's Changed

User Interface

• The favorites table has been cleaned up to make reading it easier
• Favorites buttons have had colors updated to stand out more
• Date and time pickers have been updated for a more native feel on iOS
• Beat IDs now have leading zeros to make them a maximum of 3 digits. This allows users to search for beats such as "009" instead of searching for "9"
• Required logos and statute information buttons have had their sizes reduced
• PII detection for location should be slightly more accurate. Please continue to review free-form fields for PII.
• The stops with errors button will show more prominently alerting users there are saved stops with errors that need attention
• Multiple statute codes on form inputs will display an abbreviated code so the user can see all the data

Admin Page

• Administrators can now filter by multiple status on the admin stops page
• Stops now receive a "pending" status during submission. This prevents stops that are already submitted to the CA-DOJ from being edited, potentially creating duplicate submissions
• Filters on the admin stops page should perform more accurately and save state when switching between tabs
• Successfully submitted stops can now be viewed in read-only mode by administrators