In this article
December, 2024
Flex Platform | Flex CAD | Flex GIS | Flex Apps | Flex Records| Flex IBR
Flex Platform
View TOTP registration code
In 2024.3, we released TOTP as one of the authentication methods for Flex. In 2024.4, we’ve enhanced that experience, specifically for agencies and/or departments that do not allow cell phones in their facility. Now, rather than having to take a photo of a QR code with their authenticator app, users can view the TOTP registration code and manually enter in that code when registering a TOTP authenticator.
All you have to do is select the “View Key for Manual Entry” link under the QR code to view the code. Once you manually enter the code (which is all of the lines together), it will automatically register the TOTP application.
Failed login time window
In continuing our login updates to Flex, 2024.4 now includes a new feature for SAAs called Failed Login Time Window. This addresses a CJIS security policy requirement to ensure each user has a maximum number of failed login attempts and that, if those attempts occur within a certain time window, the user is locked out. Please remember that Flex cannot automatically unlock after a certain time period which means administrators will have to manually unlock the account per CJIS requirements.
Within syusradm, Flex SAAs will find the new Mins For Failed Login Lock field. This feature works in conjunction with the Max Failed Login Attempts field. If this new field is blank or “Off”, this feature will be turned off.
Go back to the top ↑
Flex CAD
Search name in CAD comments
We’re excited to announce this newest enhancement in Flex CAD, which is the ability to run names from the comments section in CAD. As a telecommunicator is entering a CAD incident and including information about a person in the comments field, they can now highlight that name, right click and select “Run name” from the drop down menu. This will save time by having the system automatically run the query without the user having to rekey information.
This new feature can be turned on and off via the Module.CAD.CAlltaking.RunNamesFromComments setting.
Go back to the top ↑
Flex GIS
ArcGIS server 11.3 support
Starting in 2024.4, we will begin supporting ArcGIS Server 11.3 for all GIS functions, such as mapping, address validation, routing, and zone assignment). This is one of the latest changes we’ve made to ensure we keep current with ESRI products, and we encourage all of our customers to do the same. This will enable some additional functionality with address validation. For example, it will show sub-unit range information as suggestions while the user is typing, allowing for quicker unit selections.
Please note that in order to use ArcGIS Server 11.3, you will need to first migrate to ArcGIS Pro if you haven’t already done so.
Eagle-view oblique imagery viewer
Another GIS update in 2024.4 is in regards to Pictometry. We have moved Pictometry over to the Eagle View Oblique Imagery Viewer. As a reminder, with the 2024.4 upgrade, the underlying architecture moves to .NET8. Unfortunately, Pictometry’s classic viewer is not supported on .NET8. This means that, if you use Pictometry, you will need to move to their new EagleView oblique imagery online viewer. This will become the new Mobile map starting in 2024.4. Since this is a browser-based viewer, it does not require that you have local images warehouse files loaded on the laptop.
Before you upgrade, you will need to reach out to EagleView and get some information from them so that you can use the viewer. There’s a client ID, a client secret, and a token URL that you will need to enter into the settings area before you can set it up. This will help mitigate any downtime for Eagle View imagery.
Go back to the top ↑
Flex Apps
Touch: State returns & ANI/ALI
On Flex Touch, we’ve re-introduced the ability to view state returns and ANI/ALI data that’s been attached to a CAD call by a dispatcher. This will allow officers who are using Touch to see those state returns and ANI/ALI information, increasing officer awareness and improving data flow throughout the agency. The state returns and ANI/ALI information will be displayed in the same format as they come in, keeping with a fixed width font.
To enable this, you’ll use the same sypriv as you did back in the earlier version of Touch: touchstatereturn. Simply add this with view access to the user, group or agency that you want to enable. This is not something that requires a new web app as long as your agency is within the last three versions of Flex.
Go back to the top ↑
Flex Records
Incident summary field
We’re excited to announce that we now have an Incident Summary field in law incidents within Flex. This appears in Mobile Law Incident and the Law Incident Screen for desktop. This can be used by agencies who want a one-two sentence summary that can be used to brief supervisors or be released to the media. Many agencies have found workarounds for this in the past, and we’re excited to bring officers a consistent, dedicated space for that summary.
This follows the same permissions as chkprnt, or you can use lwmsum sypriv. In Mobile Law, we’ve added a new setting in Admin Util where you can automatically add the Incident Summary at the beginning of every call, just like it does with Original Narrative. You can also turn that off so that users have to actually press the button to add the summary. You can find that setting at module.fr.AutoAddSummarytoIncident.
DL issue date
The other update we’ve made in Flex Records is we’ve added a “Drivers License Issued Date” field to the DL Info screen on Flex Mobile and desktop. Some states return a DL Issued date with state returns and there was never a place in Flex to store that data. This has been a particular pain point for our customers whose states require an Issued Date when issuing a citation. Now, patrol officers can easily utilize this new field in both the Mobile Names table as well as the DL info table on Flex desktop.
This field is optional and will be automatically activated for everyone.
Go back to the top ↑
Flex IBR
Workflow to batch
Starting in 2024.4, agencies will have the ability to manage what comes into their batch validation for incident reports. This will enable reports to go through a workflow process and be reviewed by a supervisor before they go into batch validation.
To enable this, go to the Adminutil setting module.IBR.WorkflowsAllowedForBatchValidation and set the status that you want each incident report to reach before it shows up in batch validation. If an incident report does not reach the specified status, it will not show up in batch validation.
Multiple offenses
Lastly, 2024.4 brings customers the ability to add multiple of the same offenses on the same report without having to go in and change the offense code in order to get it to pass batch validation. When an officer adds in the first offense, they will have the ability to fill out all of the IBR data like normal. When they add the second one with the same offense code, it will appear like it’s a Group B. The officer will not have to fill out the information again because it does not apply. This is solely for reporting purposes and it will not get sent to the state.
This update has been backed into 2024.2, allowing a few key states to take advantage of this. There are no settings for this change; it is automatically included.
Go back to the top ↑
October, 2024
Flex Platform | Flex CAD | Flex GIS | Flex Records
Flex Platform
New Login Screen With SSL Validation Check
The first and foremost update for 2024.3 is the one you’ll see when logging into Flex. Not only does the new login screen provide a more modern look, it also builds in the capability for an agency to utilize time-based, one-time password (TOTP). This brings Flex into alignment with CJIS requirements and prepares us for enabling agencies to use their own, existing IdM provider and other login methods in 2025!
The new login screen now requires users to pick their server first then enter in their username. Once users enter their username, they will be presented with a password prompt based upon IdM settings. If TOTP is enabled for that user’s agency, then they will be presented with a TOTP prompt once they enter in a valid password..
Additionally, Flex now performs an SSL Validation check whenever any user logs on. If the validation check is not successful, the user will be prevented from logging into Flex. This will help agencies ensure CJIS compliance and the overall security of their system.
The updated login screen will be applied across the board, for all Flex users once an agency upgrades to 2024.3. This new login screen is now the default login screen and is activated automatically. Users will have to select a server before connecting. For the SSL Validation Check, it’s important to note that this feature is not configurable and cannot be turned off. Your agency’s SAA can use the SSL CertCheckUtil to confirm validation and see where the problem is if the check is not successful.
Built-In TOTP
As mentioned, 2024.3 is the first release with built-in TOTP. This highly anticipated enhancement will allow agencies to set up multi-factor authentication (MFA) via TOTP out of the box. To better help Flex customers comply with the new CJIS mandate for all CJI systems to have MFA capabilities, there is no cost associated with this feature; this will be available to any Flex agency that needs MFA but does not want to buy PassKeys.
TOTP integration will be available in Flex desktop, Flex Mobile, Touch, Jail Scanner, and Flex Admin Manager. Integration for the Evidence Scanner will be coming later this year. To enable, simply set Module.MFA.TOTP.Enabled to “True”. This can be set all the way down to the user level, allowing you to be as granular or wide as you need with this MFA functionality.
IdM Integration
Does your agency use a third-party IdM provider such as Microsoft Entra ID, Cisco Duo, Okta or others? We’re actively working on integration to third-party IdM providers so that your users can utilize the same username and password used in other agency applications with Flex. Keep an eye out for this in 2025!
Bomgar Remote Session Link
This update includes a new, direct link to flexsupport.motorolasolutions.com on the Flex desktop, Mobile and Jail screens’ help menu. This helpful link, which is available to all Flex users, will drastically reduce the amount of time customers have historically spent with the Flex Support team just trying to get to the Bomgar Remote Support portal. Now, users can get to the right website in one, quick click.
There are no settings that need to be changed; this link is automatically activated. Just look for the “Remote Support” link under the Help menu.
.Net 8
Microsoft will be ending support of .NET 6 in November 2024. With that in mind, we are pleased to announce that Flex is now compatible with .NET 8. CertCheckerUtil has already been updated to check for .NET 8. We know that these changes are not fun for anyone, so we are currently making changes to the Launcher to automatically install .NET moving forward.
It’s important to note that .NET 8.0 must be installed on all Flex clients prior to upgrading to 2024.3+. It can be installed side -by-side with .NET 6.0, allowing your agency to prepare for .NET 8.0 while still enabling backwards compatibility with .NET 6.0 until upgrading.
Go back to the top ↑
Flex CAD
Add Multiple Vehicles in CAD Calls
We’re excited to announce this newest enhancement in Flex CAD, which has been one of the most requested features on our Ideas Portal! Starting in 2024.3, dispatchers can associate multiple vehicles to a call. The plates associated with the call are listed under a new tab called “Persons & Vehicles” in the Incident screen. There are multiple ways to associate a vehicle to a call. Dispatchers can include a license plate in the call comments, or they can manually or automatically run a query. After selecting the result they want, dispatchers can select a button called “Add to Call” and then select which call they want to associate the vehicle to.
To enable the Persons & Vehicles tab in the Incident screen, make sure Module.CAD.CAlltaking.RunNamesFromComments is set to Yes. To enable the “Add to Call” button, make sure the Module.StateLink.RemoveAddToCall setting is set to False.
Go back to the top ↑
Flex GIS
Mobile Map Enhancements
We’re excited to share a number of Mobile Map updates made in the 2024.3 release. These updates include changes to the sidebar, which can now expand or collapse by clicking on any of the icons or the close button. When the sidebar moves, the whole map and navigation shift so that it doesn’t cover any portion of the map. It’s important to note that the state of the sidebar is saved to the client.
We’ve also added the ability to show and hide both incident and unit labels and icons. This will allow Mobile users to hide some of the clutter when too many incidents or units are displayed on the map. These toggles are located in the Mobile Map settings.
Finally, we have improved the experience for Mobile users that want to select an incident or unit that is in close proximity with other icons on the map. Now, users can right click on the map to display a list of nearby incidents and units in an area of the map with multiple incident/unit icons overlapping.
Go back to the top ↑
Flex Records
Demographics Screen Changes
Frequently, NCIC, IBR, and Stop Reporting codes for race, sex, gender, ethnicity and color are not always the same. In an effort to streamline the process for Flex users and minimize errors in reporting, we have made a few changes to the Demographics screen. First, we’ve created Demographic screen-specific code tables for race, sex, gender, ethnicity, and color. We’ve also added a few new fields for Perceived Color, Perceived Ethnicity, and Perceived Gender. Lastly, a number of fields in the Demographics screen were expanded to allow the full abbreviations or descriptions of state-mandated fields.
There are no extra settings for this enhancement; the changes will automatically take effect beginning in 2024.3. No existing data will be lost; existing code tables will be copied over to the new code tables and existing rcmain data will now automatically point to these new code tables. It will be up to your agency to modify the new tbrc* code tables to conform to your requirements.
File Capture Screen Changes
We have a lot of customers utilizing the integration between Flex and CommandCentral Evidence, with some asking for the ability to set default download behavior. To preserve file authenticity, this newest enhancement will allow system administrators to set whether their users are forced to open files directly in CommandCentral Evidence rather than downloading files onto their desktop. Since not every agency will have a preference one way or the other, we have also provided the ability for the end user to make the decision themselves.
For SAA’s to set the default behavior for their agency, go to the new setting Module.FileCapture.downloadBehavior. If your agency does not have a preference and wants to enable the users to make their own defaults, no settings need to be changed.
Go back to the top ↑
For previous product updates not listed on this blog, click here.
