MN008865A01 AF Enus PremierOne CAD Mobile Release Notes v4613

PremierOne™
CAD/Mobile Release Notes

System Release: 4.6.0, 4.6.1, 4.6.2, 4.6.3, 4.6.5, 4.6.6, 4.6.7, 4.6.8, 4.6.9,
4.6.10, 4.6.11, 4.6.12, 4.6.13
NOVEMBER 2023 *MN008865A01*

© 2023 Motorola Solutions, Inc. All Rights Reserved. MN008865A01-AF
MN008865A01-AF
Intellectual Property and Regulatory Notices
Intellectual Property and Regulatory

Notices
Copyrights
The Motorola Solutions products described in this document may include copyrighted Motorola Solutions
computer programs. Laws in the United States and other countries preserve for Motorola Solutions
certain exclusive rights for copyrighted computer programs. Accordingly, any copyrighted Motorola Solutions
computer programs contained in the Motorola Solutions products described in this document may not be
copied or reproduced in any manner without the express written permission of Motorola Solutions.
No part of this document may be reproduced, transmitted, stored in a retrieval system, or translated into
any language or computer language, in any form or by any means, without the prior written permission of
Motorola Solutions, Inc.
Trademarks
MOTOROLA, MOTO, MOTOROLA SOLUTIONS, and the Stylized M Logo are trademarks or registered
trademarks of Motorola Trademark Holdings, LLC and are used under license. All other trademarks are the
property of their respective owners.
License Rights
The purchase of Motorola Solutions products shall not be deemed to grant either directly or by implication,
estoppel or otherwise, any license under the copyrights, patents or patent applications of Motorola Solutions,
except for the normal non-exclusive, royalty-free license to use that arises by operation of law in the sale of a
product.
Open Source Content

This product may contain Open Source software used under license. Refer to the product installation media
for full Open Source Legal Notices and Attribution content.
European Union (EU) and United Kingdom (UK) Waste of Electrical and Electronic
Equipment (WEEE) Directive
The European Union's WEEE directive and the UK's WEEE regulation require that products sold into
EU countries and the UK must have the crossed-out wheelie bin label on the product (or the package in some
cases). As defined by the WEEE directive, this crossed-out wheelie bin label means that customers and
end-users in EU and UK countries should not dispose of electronic and electrical equipment or accessories in
household waste.
Customers or end-users in EU and UK countries should contact their local equipment supplier representative
or service centre for information about the waste collection system in their country.
Disclaimer
Please note that certain features, facilities, and capabilities described in this document may not be applicable
to or licensed for use on a specific system, or may be dependent upon the characteristics of a specific mobile
subscriber unit or configuration of certain parameters. Please refer to your Motorola Solutions contact for
further information.
© 2023 Motorola Solutions, Inc. All Rights Reserved
2
MN008865A01-AF
Contact Us
Contact Us
The Centralized Managed Support Operations (CMSO) is the primary contact for technical support included
in your organization's service agreement with Motorola Solutions.
Service agreement customers should be sure to call the CMSO in all situations listed under Customer
Responsibilities in their agreement, such as:
● To confirm troubleshooting results and analysis before taking action
Your organization received support phone numbers and other contact information appropriate for your
geographic region and service agreement. Use that contact information for the most efficient response.
However, if needed, you can also find general support contact information on the Motorola Solutions website,
by following these steps:
1. Enter motorolasolutions.com in your browser.
2. Ensure that your organization's country or region is displayed on the page. Clicking or tapping the name
of the region provides a way to change it.
3. Select "Support" on the motorolasolutions.com page.
Comments
Send questions and comments regarding user documentation to documentation@motorolasolutions.com.
Provide the following information when reporting a documentation error:
● The document title and part number
● The page number or title of the section with the error
● A description of the error
Motorola Solutions offers various courses designed to assist in learning about the system. For information, go
to https://learning.motorolasolutions.com to view the current course offerings and technology paths.
3
MN008865A01-AF
Document History
Document History
Version Description Date
MN008865A01-001 Unreleased version of the PremierOne CAD/Mobile Re- December 2021
lease Notes Version 4.6.5. There was not a 4.6.4 release.
The features that would have been in 4.6.4 have been
included in the 4.6.5 release.
MN008865A01-002 Initial release of the PremierOne CAD/Mobile Release January 2022
Notes Version 4.6.5.
MN008865A01-003 Initial release of the PremierOne CAD/Mobile Release March 2022
MN008865A01-004 First revision of the PremierOne CAD/Mobile Release March 2022
MN008865A01-005 Initial release of the PremierOne CAD/Mobile Release April 2022
MN008865A01-006 First revision of the PremierOne CAD/Mobile Release June 2022
MN008865A01-007 Second revision of the PremierOne CAD/Mobile Release July 2022
MN008865A01-008 Initial release of the PremierOne CAD/Mobile Release July 2022
MN008865A01-009 First revision of the PremierOne CAD/Mobile Release August 2022
MN008865A01-010 Second revision of the PremierOne CAD/Mobile Release September 2022
MN008865A01-011 Initial release of the PremierOne CAD/Mobile Release October 2022
MN008865A01-012 First revision of the PremierOne CAD/Mobile Release November 2022
MN008865A01-013 Initial release of the PremierOne CAD/Mobile Release January 2023
Consolidated previous release notes from 4.6.3, 4.6.2,
4.6.1, and 4.6.0 into this guide.
MN008865A01-014 First revision of the PremierOne CAD/Mobile Release April 2023

Notes Version 4.6.10. Updated to include 4.6.10a Issues
Resolved on page 107.
MN008865A01-015 Initial release of the PremierOne CAD/Mobile Release April 2023
MN008865A01-016 First revision of the PremierOne CAD/Mobile Release April 2023
Notes Version 4.6.11. Updated Software on page 21.
MN008865A01-AA Second revision to the PremierOne CAD/Mobile Release June 2023
Notes Version 4.6.11. Added Features and Functionality
in PremierOne Mobile iOS Application Version 4.6.11 on
page 83.
4
MN008865A01-AF
Document History
Version Description Date

MN008865A01-AB Initial release of the PremierOne CAD/Mobile Release July 2023
MN008865A01-AC First revision of the PremierOne CAD/Mobile Release August 2023
MN008865A01-AD Second revision of the PremierOne CAD/Mobile Release September 2023
MN008865A01-AE Third revision of the PremierOne CAD/Mobile Release October 2023
Notes Version 4.6.12. Updated to include 4.6.12b Issues
MN008865A01-AF First release of the PremierOne CAD/Mobile Release November 2023
5
MN008865A01-AF
Contents
Contents
Intellectual Property and Regulatory Notices................................................................... 2
Contact Us............................................................................................................................3
Document History................................................................................................................4
List of Figures.................................................................................................................... 13
List of Tables......................................................................................................................19
List of Procedures............................................................................................................. 20
Chapter 1: PremierOne Release Notes.............................................................................21
1.1 Technical Support............................................................................................................................ 21
1.2 Provisioning and IE.......................................................................................................................... 21
1.3 Software...........................................................................................................................................21
Chapter 2: Features and Functionality in Version 4.6.13................................................23
2.1 4.6.13 Issues Resolved....................................................................................................................23
2.2 CAD New Functionality.................................................................................................................... 27
2.2.1 Show Unit ID of Who Sent Message on CAD Client WAA From Field in Messaging
(524516).................................................................................................................................27
2.2.2 Ability to Update Location Information on Associated Incidents (526355)......................... 28
2.2.3 Database Queries Added for Radio ID, Vehicle ID and Talk Group (545060)....................30
2.3 Provisioning New Functionality........................................................................................................ 32
2.3.1 New Provisioning Field for Incident Response Factors (487893)...................................... 33
2.3.2 VerifyByLocationAndCity Setting Moved to Provisioning (494511).................................... 34
2.3.3 Refactor the Incident Management Form to Optimize Update and Dispatch (525692)..... 35
2.3.4 Support Modern Browsers (496229, 496230).................................................................... 36
2.3.5 Unsolicited Responses Mnemonics (488876)....................................................................36
2.3.6 Additional Fields Added to Personnel Import API (536044)...............................................36
2.4 Mobile New Functionality 4.6.13...................................................................................................... 36
2.4.1 iOS Message - Reply/Reply All/Forward, Including CC, BCC, and Attachments
(419541).................................................................................................................................37
2.4.2 iOS/Android - 10-21 Police Phone App Integration (522613, 522614).............................. 43
2.4.3 Mobile Windows - Disposition Enhancements - Disposition Filter (519663)...................... 46
2.4.4 Mobile Windows - Disposition Enhancements - Incident Number in Disposition Box
(519664).................................................................................................................................46
2.4.5 Mobile Windows - Disposition Enhancements - Adding Additional Reporting Fields to
the Disposition Area (519665)................................................................................................47
2.4.6 Android - Automate PR Data Upload (495415)..................................................................50
2.4.7 iOS - Automatic Application Updates................................................................................. 50
6
MN008865A01-AF
Contents
3.1 4.6.12b Issues Resolved..................................................................................................................52

3.2 4.6.12a Issues Resolved..................................................................................................................52
3.3 4.6.12 Issues Resolved....................................................................................................................52
3.4.1 Highlight Recommended Units that are In Station on Dispatch Form (476603)................ 54
3.4.2 AI for CAD Comments – Comments Parser (484465)....................................................... 56
3.4.3 Microsoft 2019 Support (467860).......................................................................................58
3.4.4 MACH Alert Add Ability to Change Tone for Move Up and Print Map Page Data
(496259).................................................................................................................................60
3.4.5 Provisioning – Support Modern Browsers 4.6.12 (500771)............................................... 64
3.5 Mobile New Functionality................................................................................................................. 64
3.5.1 Mobile Android – Logout Failed Dialog Box (470165)........................................................64
3.5.2 Optional Status Parameters (483606)................................................................................65
3.5.3 Mobile Android – Cross-Agency Radio ID Field (483614)................................................. 66
3.5.4 New Mobile Map Version (488162).................................................................................... 68
3.5.5 iOS – Barcode Scanner Library Replacement (483986)....................................................69
3.5.6 Messaging Send as Unit ID Settings Group (484172)....................................................... 72
3.5.7 Selection of Unit Capabilities on Mobile Client (484308)................................................... 73
3.5.8 iOS Message – Part 3 – Compose Messages, CC/BCC Messages, Messages with
Attachments Draft (419543) .................................................................................................. 76
3.5.9 Provisioning Audit Tool .NET and Angular Libraries (414457)........................................... 81
3.5.10 API 33 Behavior Changes (483610)................................................................................ 82
3.5.11 ArcGIS Upgrade for Android Systems (484292).............................................................. 82
3.6 Future Use Only...............................................................................................................................82
3.6.1 Device Type = Workstation 2.0 (495348)........................................................................... 82
Chapter 4: Features and Functionality in PremierOne Mobile iOS Application
Version 4.6.11 ................................................................................................................83
5.2 4.6.11 Issues Resolved....................................................................................................................87
5.3 CAD/Mobile/Admin Workstations Update........................................................................................ 90
5.3.1 ArcGIS 10.8.1 Required for CAD/Mobile/Admin Workstations (451239)........................... 90
5.4.1 Allow Auto Incident Association by IRF Instead of Just Agency (437942).........................91
5.4.2 Add Missing Incident Person Data to the ReportingDW Database (465483).....................91
5.4.3 Add Missing Incident Vehicle Data to the ReportingDW Database (442394).................... 93
5.4.4 Reduce the Permission for Adding Prem/Haz Records as a Comment to an Incident
to Read Only (440310) ..........................................................................................................93
5.4.5 Add the Field Initiate (FI) Command to the Status Monitor Right-Click Options
(451435).................................................................................................................................94
7
MN008865A01-AF
Contents
5.4.6 Manage High Priority Incidents Using the CC and SC Commands (435459) ................... 95
5.5 Mobile New Functionality................................................................................................................. 96
5.5.1 Windows Mobile – Mobile Server Proxy Migration to .NET 6 (444503)............................. 96
5.5.2 HandHeld Mobile iOS and Android – Rename Subnet IP Address Field (457662 and
457665).................................................................................................................................. 97
5.5.3 HandHeld Mobile iOS and Android – Send Error Reports While Logged On (455986)..... 98
5.5.4 HandHeld Mobile iOS – Public IP Address Setting Added (449157)................................. 99
5.5.5 HandHeld Mobile iOS – Message Improvements (449153)...............................................99
5.5.6 HandHeld Mobile iOS – Google Maps Navigation Provider Support (444569)................101
5.5.7 HandHeld Mobile Android – Cross-Agency Login (421195).............................................103
Chapter 6: Features and Functionality in Version 4.6.10..............................................107
6.1 4.6.10a Issues Resolved................................................................................................................107
6.2 4.6.10 Issues Resolved..................................................................................................................107
6.2.1 Personnel Provisioning - Personnel Search Form Incorrectly Defaults to Sound Alike
= Checked (423091).............................................................................................................109
6.2.2 Updating Location from Command Line - Update the Common Place for New
Location (351030)................................................................................................................ 110
6.3 CAD New Functionality...................................................................................................................111
6.3.1 Using Unit GPS Location for ID Command (400218)....................................................... 111
6.3.2 Contractor Beat Added to the RDW Data Dictionary (403514)........................................ 113
6.3.3 Add Radio ID identifier to ON Command line (400217)................................................... 113
6.3.4 Notification of Unit Being Dispatched Outside of Jurisdiction (412752)........................... 114
6.3.5 On-Demand Vicinity Checks (412848)............................................................................. 115
6.3.6 Allow Call for Service Updates for Local Agencies to update Associated Incidents
(423048)............................................................................................................................... 115
6.3.7 Performing Potential Duplicate Check Against CAD-to-CAD Call for Service
Requests (412831)...............................................................................................................116
6.4 Mobile New Functionality............................................................................................................... 117
6.4.1 Windows Mobile Client Launches Before Mobile Map (418824)...................................... 117
6.4.2 HandHeld Mobile – iOS Messages (419535)................................................................... 118
6.4.3 HandHeld – Meet Google Play Target API Level 31 Requirement (384552)................... 119
7.2 4.6.9 Issues Resolved....................................................................................................................120
7.3 CAD New Functionality.................................................................................................................. 122
7.3.1 Automatic Dispatch Upon Incident Initiation (355161)..................................................... 122
7.3.2 Notification of Unit Being Dispatched Outside of Jurisdiction (367823)........................... 124
7.3.3 Unit GPS Location Used for the FI Command (378509)..................................................126
7.3.4 Standard Operating Procedures (379619)....................................................................... 126
7.3.5 Automatic Status Changes Logged to Incident History (CAD) (375666)......................... 128
8
MN008865A01-AF
Contents

7.4.1 Automatic Status Changes Logged to Incident History (Mobile) (375666)...................... 129
7.4.2 CJIS Security Support Updates for the Least Privileged Access on Mobile Windows
(383893)...............................................................................................................................129
7.4.3 Google Android API 31 Support (384552)....................................................................... 130
7.4.4 Query Purpose Code for HandHeld iOS (361840)...........................................................131
7.5 Provisioning New Functionality...................................................................................................... 134
7.5.1 User ID Field Period Support (276893)............................................................................134
8.1 4.6.8b Issues Resolved..................................................................................................................135
8.3 4.6.8 Issues Resolved....................................................................................................................135
8.4 4.6.8 Known Issue......................................................................................................................... 137
8.5.1 Standard Operating Procedures (332009)....................................................................... 137
8.5.2 Ability to Add Up to 25 Report Numbers Against an Incident (345702)........................... 139
8.5.3 Manual Address Points (322751).....................................................................................140
8.5.4 Voice Dispatch API (222992)........................................................................................... 143
8.5.5 Include Images from Vigilant ALPR Hot Hit to the Incident (366289) ............................. 144
8.6.1 iOS Disposition Dropdown Filter (346709).......................................................................145
8.6.2 Mobile Windows Restrict Query Dropdown Fields to Picklist Selection (353279)............145
8.7.1 Provisioning Audit Tool (322888)..................................................................................... 146
9.2 4.6.7a Known Issue....................................................................................................................... 149
9.3 4.6.7 Issues Resolved....................................................................................................................149
9.4.1 ANI/ALI Rebid - Rebid on Incident Update (323862) ...................................................... 151
9.4.2 Manual Address Points (322751).....................................................................................154
9.4.3 RapidSOS RAD-E Integration (285094)...........................................................................156
9.5.1 Route to Incident Secondary Locations on Mobile Map (70825)..................................... 159
9.6.1 Alarms Provisioning Fields Added to RDW (309791)...................................................... 161
9.6.2 Premise Hazard Fields Added to RDW (328803)............................................................ 162
9.6.3 Premise Hazard Fields on CAD Configuration Removed (329988)................................. 162
9
MN008865A01-AF
Contents
10.1 Issues Resolved...........................................................................................................................163

10.2 CAD New Functionality................................................................................................................ 164
10.2.1 Location Services – APX and APX NEXT to PremierOne Connectivity 301489............164
10.2.2 Support Incident Type Aliases with the Field Initiate Command 309736....................... 165
10.3 Mobile New Functionality............................................................................................................. 165
11.1 4.6.5a Issues Resolved................................................................................................................167
11.2 4.6.5 Issues Resolved..................................................................................................................167
11.3.1 Immediately Take Units Off Duty Upon Receiving an Off Duty Notification 154874.......169
11.3.2 Accept a Call for Service (CFS) Acknowledgement Retry Value of Zero (0) 258544.....170
11.3.3 Query Purpose Code Added to II, IU, FI Commands and Vehicle/Person Screens
175033................................................................................................................................. 170
11.3.4 Contractor Capability Added to Incident History and RDW 248420............................... 177
11.3.5 Added Secondary Response Location to Available Fields in CAD Status Monitors
15029................................................................................................................................... 178
11.3.6 Edge Browser Support 277337...................................................................................... 182
11.3.7 Organization and Department Hierarchical Reporting Structure 274770....................... 182
11.4.1 Query Purpose Code Added to Mobile Traffic Stop Form and Person and Vehicle
Tabs 202019.........................................................................................................................184
11.4.2 Designate Riding Position During Logon 209329...........................................................187
11.4.3 Displaying ARL Unit Location History on the Mobile Map 209327................................. 190
11.4.4 Audible Alerts for Priority Fields 175283........................................................................ 192
11.4.5 Display All Assigned Units on CAD2CAD Incidents 234607.......................................... 194
11.4.6 Enhanced Barcode Scanner Support 240935................................................................195
11.4.7 Search Filter for the Disposition Field Updated in Android 263449................................199
11.4.8 Google Android API 30 Support 243357........................................................................ 200
11.4.8.1 Granting Background Location Permissions.....................................................201
11.5 Provisioning New Functionality.................................................................................................... 206
11.5.1 Query Response Format Designer Refresh 293471...................................................... 206
12.1 Issues Resolved...........................................................................................................................208
12.2.1 Status Selection for Freed Incidents (15731).................................................................209
12.2.2 Sending RapidSOS Information to the Incident Address Field (154707)....................... 209
12.2.3 Proactive Recommendations (161801)..........................................................................209
12.3.1 Zoom-In Functionality for GeoFence List Items (191416)..............................................210
10
MN008865A01-AF
Contents
12.3.2 Ability to Parse-out a Period in the User-ID [Montgomery Co., TX] (220979)................ 211
12.3.3 Automatic Synchronization of Assigned Incidents and Messages (196277).................. 211
12.3.4 Tracking Units in Emergency Mode (15283).................................................................. 211
12.3.5 GPS Improvements (111106)......................................................................................... 212
12.3.5.1 GPS Settings....................................................................................................212
12.3.5.2 Enhanced Windows Location Services Support (101735)............................... 218
12.3.5.3 GPS Precision Improvements.......................................................................... 218
12.3.6 Mobile Map Changes..................................................................................................... 218
12.4.1 Support Period (.) in the User Name Field for CAD/Mobile Sign On (175019).............. 220
12.4.2 Support Period (.) in the User Name Field for CAD/Mobile Sign On (175019).............. 220
13.1 Issues Resolved...........................................................................................................................221
13.2.1 Road Closures in Mobile Map (102207).........................................................................222
13.2.2 GeoFences in Mobile Map (102208)..............................................................................222
13.2.3 Support for URLs in Incident Comments and Messages (79567) .................................222
13.2.4 Deployment Improvements for iOS................................................................................ 222
13.3.1 Performance Improvement Initiatives 57047 .................................................................223
13.3.2 Process PURVIS Acknowledgement Messages to Update the Units Status (145117) . 223
13.3.3 ASAP2PSAP Interface (145111) ................................................................................... 223
13.3.4 [CAD-to-CAD] Foreign-to-Foreign Call for Service Monitoring (145112)........................224
13.3.5 CAD-to-CAD Improvement Initiatives (150929)............................................................. 224
13.3.6 Response Card Provisioning: Run Card Cutoff (145120).............................................. 224
13.4 ProQA Interface Updates.............................................................................................................225
13.4.1 Provisioned Non-Tandem Transfer Types (135957).......................................................225
13.4.2 VESTA Context Number Processing (126715).............................................................. 225
13.4.3 Configurable Button Display Based on Role Selection (140819)...................................226
13.4.4 SMS Transfer (78939)....................................................................................................226
14.1 Issues Resolved...........................................................................................................................227
15.1 Issues Resolved...........................................................................................................................230
15.2.1 Create Associated Incidents for Call for Service (CFS) Requests (80359)....................231
15.2.2 Phone Number Query.................................................................................................... 231
11
MN008865A01-AF
Contents

15.3.1 Customer-Specific Certificates (55153)......................................................................... 232
15.3.2 Mobile on REST (MoR) (15025) (79570)....................................................................... 232
15.3.3 Disaster Recovery Server Selection from Mobile (46828)............................................. 233
15.3.4 Mobile Map Activate Smart Status (15276)....................................................................236
15.3.5 Mobile Map Locate, Zoom, and Center on Mobile Map (15281)....................................237
15.3.6 Display First and Last Name of Crew Members within Unit Details (15287)..................237
15.3.7 Update Map Labels to Classic and Mobile Map (70818)............................................... 237
15.3.8 Remove the On-Screen Keyboard Checkbox (81399)...................................................238
Chapter 16: Hardware and Software Requirements......................................................239
Chapter 17: Using PremierOne Help.............................................................................. 243
Chapter 18: Open Source Legal Notices........................................................................246
12
MN008865A01-AF
List of Figures
List of Figures
Figure 1: Previous Originator Display in From Field......................................................................................... 27
Figure 2: New Originator Display with User ID in From Field........................................................................... 27
Figure 3: Priority Comment...............................................................................................................................28
Figure 4: Initiation Defaults - New Check Boxes.............................................................................................. 28
Figure 5: Incident Management Form - Update Associated Checkbox ........................................................... 29
Figure 6: Enable Local SQL Query and Connection String Box on Query > Suite Level Setting >
Interfaces Screen.........................................................................................................................................30
Figure 7: SQL Query String Text Box on the Query>Suite Level Setting>Query Types>Interface Fields
Screen ........................................................................................................................................................ 31
Figure 8: Vehicle ID Stored Procedure Query on Queries Page ..................................................................... 32
Figure 9: Vehicle ID Stored Procedure Query on Query Responses Page...................................................... 32
Figure 10: Description Field on Incident Response Factor Provisioning Page.................................................33
Figure 11: Outdated Location for VerifyByLocationAndCity - Configuration Tool .............................................34
Figure 12: New Location for VerifyByLocationAndCity - Provisioning.............................................................. 35
Figure 13: Personnel Import API With Organization ID Field and Department ID Field................................... 36
Figure 14: Reply, Reply All, and Forward Buttons in the Messages List.......................................................... 37
Figure 15: Reply button and Reply in the Compose Message Screen............................................................. 38
Figure 16: Reply All in the Compose Message Screen.................................................................................... 38
Figure 17: Forward in the Compose Message Screen..................................................................................... 39
Figure 18: Arrow Button and Menu...................................................................................................................40
Figure 19: Menu with Reply… Submenu.......................................................................................................... 41
Figure 20: Menu with the Reply All… Submenu............................................................................................... 42
Figure 21: Menu with Forward Button...............................................................................................................43
Figure 22: Figure: Call Default List................................................................................................................... 44
Figure 23: Phone Number Hyperlinks on the Incident Details - Comment and Incident Details - Personal
Information Screens.....................................................................................................................................44
Figure 24: Call Dialog Box................................................................................................................................ 45
Figure 25: Info Dialog Box................................................................................................................................ 45
Figure 26: Disposition Search Bar and Drop-down Results List.......................................................................46
Figure 27: Disposition not found Message....................................................................................................... 46
Figure 28: Disposition Box with Incident Number Field.................................................................................... 47
Figure 29: Incident Summary Displayed in the Active Work Area.................................................................... 47
Figure 30: Enable Disposition Reporting Fields Checkbox - Mode Selection Screen...................................... 48
Figure 31: Enable Disposition Reporting Fields Checkbox - Value Set to True................................................48
Figure 32: Configured Additional Fields on Disposition Screen........................................................................49
Figure 33: Incident History Screen - Mobile Client .......................................................................................... 49
Figure 34: Incident History Screen - CAD Client.............................................................................................. 50
13
MN008865A01-AF
List of Figures
Figure 35: Display Setting Drop Down List From the Unit Recommendation - Settings - Dispatch List
Provisioning Page........................................................................................................................................55
Figure 36: Default Setting- Unit Only Setting No Highlight or Notation of Units In or Out of Station ............... 55
Figure 37: Indicate Units That are in an In-Station Status Setting - Units That are In Station are
Highlighted in Red and have an Asterisk next to unit ID .............................................................................56
Figure 38: Display all Units in their provisioned Unit Status Monitor Colors ....................................................56
Figure 39: Incident Initiate Form - Comments Text Box ...................................................................................57
Figure 40: Incident Management Form - Persons and Vehicles created from parsed comment data. ............57
Figure 41: Provisioning - Enable/Disable Comments Parsing Option.............................................................. 58
Figure 42: RemoveOldManagementPacks Checkbox in PremierOne Server Configuration Tool Window ..... 59
Figure 43: SSIS Package Version Drop-Down List in PremierOne Reporting Configuration Tool Window...... 60
Figure 44: Edit Tab - ToningDSA > Toning Codebox for Changing Tone.......................................................... 61
Figure 45: Edit Tab - PagingToningTVRInterface Code Box.............................................................................61
Figure 46: Edit Tab - ToningDSA > Toning Codebox for Print Map Page Data.................................................62
Figure 47: Edit Tab - Toning > Toning Code Box.............................................................................................. 63
Figure 48: Logout Failed Dialog Box................................................................................................................ 65
Figure 49: Radio ID Field..................................................................................................................................66
Figure 50: Radio ID Field Entry Formats.......................................................................................................... 67
Figure 51: Basemap Not Displayed.................................................................................................................. 68
Figure 52: Unit Icons Not Displayed ................................................................................................................ 68
Figure 53: Basemap and Unit Icon Issues Resolved and Displaying Normally................................................ 69
Figure 54: Barcode Icon................................................................................................................................... 70
Figure 55: Camera Access Dialog Box.............................................................................................................71
Figure 56: Barcode Scanning Screen...............................................................................................................72
Figure 57: Unit ID in the From Field..................................................................................................................72
Figure 58: Message Options Dialog Box.......................................................................................................... 73
Figure 59: Mail Options Dialog Box and Send as Unit ID Check Box...............................................................73
Figure 60: Mobile Simple Login Screen with Capabilities.................................................................................74
Figure 61: Assigned Capabilities Edit Window................................................................................................. 75
Figure 62: Manage Assignments Form with Capabilities..................................................................................75
Figure 63: Mobile UI Customization - Login Options Window.......................................................................... 76
Figure 64: Dashboard Screen, Messages Inbox Screen, Messages Detail Screen with Compose Button
Highlighted ..................................................................................................................................................77
Figure 65: New Message Screen and Priority Dropdown Menu Highlighted....................................................78
Figure 66: Message Attachment Icons and Delete Icon................................................................................... 79
Figure 67: Send Button - Enabled.................................................................................................................... 79
Figure 68: Disabled Send Message Button...................................................................................................... 80
Figure 69: Cancel Button.................................................................................................................................. 80
Figure 70: Dismissing the New Message Screen by Dragging from Top to Bottom. ....................................... 81
Figure 71: Status List Screen........................................................................................................................... 83
14
MN008865A01-AF
List of Figures
Figure 72: Main Mobile Screen.........................................................................................................................84

Figure 73: Status Parameters Screen.............................................................................................................. 85
Figure 74: Unit Status Codes Screen............................................................................................................... 85
Figure 75: Create Associated Incidents Menu..................................................................................................91
Figure 76: Role Permission - Premise Hazard (Read Only)............................................................................. 93
Figure 77: Incident Management Form - Add as Cmt Button........................................................................... 94
Figure 78: Field Initiate in Right Click Menu Options Page.............................................................................. 94
Figure 79: PremierOne HandHeld Mobile – iOS and Android Filter IP Setting.................................................97
Figure 80: PremierOne HandHeld Mobile – iOS and Android Send Error Report Option................................ 98
Figure 81: Mobile iOS Public IP Setting............................................................................................................99
Figure 82: PremierOne Mobile iOS – New Messages Functionality in Version 4.6.11................................... 100
Figure 83: PremierOne Mobile iOS – Message Notifications......................................................................... 101
Figure 84: PremierOne Mobile iOS – Navigation Setting............................................................................... 101
Figure 85: Google Maps Application Navigation Screen................................................................................ 102
Figure 86: Google Maps Web Browser Navigation Screen............................................................................ 103
Figure 87: Cross-Agency Login with Unit ID...................................................................................................105
Figure 88: Cross-Agency Login with User ID..................................................................................................105
Figure 89: Sound Alike Check Box Defaulted to Unchecked..........................................................................109
Figure 90: incident with Location and Common Place Information.................................................................110
Figure 91: Update with Common Place Location on Command Line............................................................. 110
Figure 92: Updated Location and Common Place Display in the Incident Update Form................................ 111
Figure 93: ARL Identifier in Command Line....................................................................................................112
Figure 94: ARL Identifier in Provisioning.........................................................................................................112
Figure 95: Radio ID Identifier - RID.................................................................................................................113
Figure 96: Radio Identifier - RID with Multiple Values.....................................................................................114
Figure 97: Out-of-Agency Dispatch Notification Recipient Types................................................................... 114
Figure 98: Vcnty Button...................................................................................................................................115
Figure 99: CAD to CAD - Potential Duplicates Window..................................................................................115
Figure 100: Apply updates (as a comment to all associated incidents Button................................................116
Figure 101: Potential Duplicates Comment.....................................................................................................116
Figure 102: PremierOne Mobile iOS Messages..............................................................................................118
Figure 103: Updated Background Location Disclosures.................................................................................119
Figure 104: Agency Level Automatic Dispatch Activation Checkbox............................................................. 123
Figure 105: Incident Response Factors (Agency Type Level): Automatically Dispatch on Incident Initiation.123
Figure 106: Incident Response Factors (Agency Level): Automatically Dispatch on Incident Initiation......... 124
Figure 107: Unit Preassignments Window......................................................................................................124
Figure 108: ARL Identifier Used for Unit Location.......................................................................................... 126
Figure 109: New Incident - IRF with SOP.......................................................................................................127
Figure 110: Existing Incident - Changed IRF with SOP.................................................................................. 127
15
MN008865A01-AF
List of Figures
Figure 111: CAD Unit History Record............................................................................................................. 128

Figure 112: CAD Incident History Record.......................................................................................................128
Figure 113: Mobile Unit History Record.......................................................................................................... 129
Figure 114: Mobile Incident History Record....................................................................................................129
Figure 115: PremierOne Mobile Android – Updated In-App Disclosures........................................................131
Figure 116: PremierOne Mobile iOS Purpose Code Examples...................................................................... 132
Figure 117: PremierOne Mobile iOS Purpose Codes List...............................................................................133
Figure 118: PremierOne Mobile iOS Query Not Sent Message......................................................................133
Figure 119: Standard Operating Procedure Templates.................................................................................. 137
Figure 120: SOP – Incident Response Factors.............................................................................................. 138
Figure 121: Incident Summary Form – SOP Button....................................................................................... 138
Figure 122: SOP – PDF Viewer Example.......................................................................................................139
Figure 123: SOP – Incident History Details.................................................................................................... 139
Figure 124: Report Number Value Example................................................................................................... 140
Figure 125: Manual Address Points – Routable Street Centerline Location...................................................141
Figure 126: Manual Address Points – Common Place Names.......................................................................141
Figure 127: Manual Address Points – Matching Common Places..................................................................142
Figure 128: Manual Address Points – Common Place Aliases...................................................................... 142
Figure 129: Manual Address Points – Previous Location Check....................................................................143
Figure 130: Radio Console Sample ...............................................................................................................143
Figure 131: Dynamic Multiselect ....................................................................................................................144
Figure 132: iOS Disposition List Filtered by Search Criteria...........................................................................145
Figure 133: Mobile Client – Query – Invalid Drop-down Entry........................................................................146
Figure 134: Full Admin Access View.............................................................................................................. 147
Figure 135: Audit Log Changed Data............................................................................................................. 147
Figure 136: Audit Log Details......................................................................................................................... 148
Figure 137: Audit Log Details CSV File Download......................................................................................... 148
Figure 138: ANI/ALI Data and RapidSOS Features....................................................................................... 152
Figure 139: ANI/ALI Information..................................................................................................................... 153
Figure 140: ANI/ALI Add New Caller and Location.........................................................................................154
Figure 141: ANI/ALI Different Phone Location................................................................................................154
Figure 142: Manual Address Points................................................................................................................155
Figure 143: Common Place Entry...................................................................................................................155
Figure 144: Verified Common Place............................................................................................................... 156
Figure 145: GIS Data......................................................................................................................................156
Figure 146: RapidSOS Additional Data Enhanced RAD-E.............................................................................157
Figure 147: RapidSOS Swap..........................................................................................................................157
Figure 148: LegacyALI and RapidSOS Incident Comments Removed.......................................................... 158
Figure 149: Certificate Common Name Field................................................................................................. 159
16
MN008865A01-AF
List of Figures
Figure 150: Incident Summary when Dispatched to a Secondary Location................................................... 160

Figure 151: Route to Secondary Incident Location.........................................................................................161
Figure 152: Premise Hazard RDW................................................................................................................. 162
Figure 153: Premise Hazard Fields on CAD Configuration Removed............................................................162
Figure 154: Location Services Provisioning....................................................................................................165
Figure 155: Certificate Common Name Field................................................................................................. 166
Figure 156: Accept a CFS Acknowledgement Retry Value............................................................................ 170
Figure 157: Display Purpose Code Box..........................................................................................................171
Figure 158: Person Vehicle Screen................................................................................................................ 172
Figure 159: Person Vehicle Screen Purpose Code Box................................................................................. 172
Figure 160: Lists Statute Management...........................................................................................................173
Figure 161: Agency Level Setting IM Query Settings..................................................................................... 174
Figure 162: Agency Level Settings Purpose Code......................................................................................... 175
Figure 163: Purpose Code Command Line.................................................................................................... 175
Figure 164: Incident Initiation Command Line................................................................................................ 176
Figure 165: Field Initiate Command Line........................................................................................................176
Figure 166: Filter By Contractor......................................................................................................................177
Figure 167: Pending and Call Taker Type Window.........................................................................................178
Figure 168: Unit Type Window........................................................................................................................179
Figure 169: SRL Fields................................................................................................................................... 179
Figure 170: Incident SRL Fields..................................................................................................................... 180
Figure 171: Unit Type Status Monitor Filter.................................................................................................... 180
Figure 172: Incident, Pending, Call Taker Status Monitor Filter......................................................................181
Figure 173: Incident SRL Fields..................................................................................................................... 181
Figure 174: New SRL Fields...........................................................................................................................182
Figure 175: Departmental Hierarchical Structure Example............................................................................ 183
Figure 176: Display Purpose Code.................................................................................................................184
Figure 177: Purpose Code on the Traffic Stop Form...................................................................................... 185
Figure 178: Purpose Code on the Incident Persons Tab................................................................................ 185
Figure 179: Lists Statute Management...........................................................................................................186
Figure 180: Agency Level Setting IM Query Settings..................................................................................... 186
Figure 181: Unit Management - Riding Position............................................................................................. 187
Figure 182: Mobile UI Customization - Login Options.................................................................................... 188
Figure 183: Simple Login Form with Riding Position Dropdown.....................................................................188
Figure 184: Detailed Login Form with Riding Position Dropdowns.................................................................189
Figure 185: Detailed Unit Status Page........................................................................................................... 189
Figure 186: Mobile UI Customization - Status Monitor Display Field Configuration....................................... 190
Figure 187: ARL History Icon..........................................................................................................................191
Figure 188: ARL History Screen..................................................................................................................... 191
17
MN008865A01-AF
List of Figures
Figure 189: ARL History Query Results..........................................................................................................192

Figure 190: Service Settings - Priority Updates - Mobile Settings.................................................................. 193
Figure 191: Mobile/Handheld - Priority Alert - Incident Update...................................................................... 194
Figure 192: Incident Summary with All CAD-2-CAD Units Displayed.............................................................195
Figure 193: Status Bar Scanner Indicator.......................................................................................................195
Figure 194: Status Indicators..........................................................................................................................195
Figure 195: Mobile UI Customization..............................................................................................................196
Figure 196: List Statute Management.............................................................................................................196
Figure 197: Scanner Device........................................................................................................................... 197
Figure 198: Any Device Detected................................................................................................................... 197
Figure 199: POS HID Magnetic Stripe Reader............................................................................................... 198
Figure 200: Scanner HID Codes.....................................................................................................................198
Figure 201: Indicator Can Disable Scanning.................................................................................................. 199
Figure 202: Scanner Status Bar..................................................................................................................... 199
Figure 203: Full Disposition List......................................................................................................................200
Figure 204: Disposition Filtered by Search Criteria........................................................................................ 200
Figure 205: Background Location Permission................................................................................................ 201
Figure 206: Location Permission Settings...................................................................................................... 202
Figure 207: Administration Screen................................................................................................................. 203
Figure 208: File Explorer................................................................................................................................ 204
Figure 209: Confirming File............................................................................................................................ 205
Figure 210: Invalid File Import........................................................................................................................ 206
Figure 211: Suite Level Setting.......................................................................................................................207
Figure 212: Zoom Function.............................................................................................................................210
Figure 213: Unit in Emergency Message........................................................................................................211
Figure 214: Track Menu Option...................................................................................................................... 212
Figure 215: Mode Selection............................................................................................................................213
Figure 216: Zoom to Geofences..................................................................................................................... 219
Figure 217: New Route Display Modes Control..............................................................................................219
Figure 218: Simple Login Window.................................................................................................................. 234
Figure 219: Change Server Button................................................................................................................. 235
Figure 220: Simple Login Screen................................................................................................................... 235
Figure 221: System Logout Screen................................................................................................................ 236
Figure 222: Active Incident Window............................................................................................................... 236
Figure 223: Incident Summary Window..........................................................................................................237
Figure 224: Internet Options Dialog Box–Advanced Tab................................................................................244
Figure 225: Internet Options Dialog Box–Advanced Tab Security Section.....................................................245
18
MN008865A01-AF
List of Tables
List of Tables
Table 1: Days of Phased Release and Percentage of Users............................................................................51
Table 2: Fields Added to the MV_IncidentPerson Master View........................................................................ 92
Table 3: Fields Added to the MV_IncidentVehicle Master View........................................................................93
Table 4: Cross-Agency Login Rules................................................................................................................104
Table 5: Serial Settings................................................................................................................................... 216
Table 6: Ethernet Settings...............................................................................................................................217
Table 7: Common Settings for Serial or Ethernet........................................................................................... 217
Table 8: Location Services Settings................................................................................................................217
Table 9: PremierOne Records Mobile Recommended Specifications............................................................ 240
Table 10: Test environment specification for Windows Server 2016...............................................................242
Table 11: Test environment specification for Windows Server 2019...............................................................242
19
MN008865A01-AF
List of Procedures
List of Procedures
Granting Background Location Permissions ..................................................................................................201
Performance Improvement Initiatives 57047 ................................................................................................. 223
Using PremierOne Help .................................................................................................................................243
20
MN008865A01-AF
Chapter 1: PremierOne Release Notes
Chapter 1
PremierOne Release Notes

The PremierOne Suite contains CAD, Mobile, (Windows, Android, iOS), Records, and Cloud CAD
applications.
● PremierOne CAD is used by communications centers to track available resources, information, and
hazards, and to dispatch emergency personnel. It is available in on-premise and cloud deployments.
● PremierOne Mobile is an advanced solution for the public safety industry for law, fire, and emergency
medical services, providing first responders timely access to critical data on Windows, Android, or iOS
devices.
● PremierOne Records is an intranet application for storing, retrieving, and analyzing data collected by law
enforcement personnel. For details on Records, see the PremierOne Records Release Notes.
Information about PremierOne CAD, Mobile, and Records can be found in the following resources:
● PremierOne CAD and Mobile
● PremierOne Records
● Premier MDC
For additional information or updates, please visit the Learning Experience Portal (LXP) at:
https://learning.motorolasolutions.com
1.1
Technical Support
You can obtain 24/7 support by phone from Technical Support at 1-800-MSI-HELP. International customers,
call 1-302-MSI-HELP. International customers, call 1-302-444-9800.
Have the following information ready:
● Product name and version number
● Description of the problem (Exact wording of any messages appearing on your screen)
● What you were doing when the problem occurred
● Steps you took to try to solve the problem
● Hardware description
1.2
Provisioning and IE
Internet Explorer 11 is supported for the Provisioning console. Support for the Microsoft Edge browser has
been added when used in the IE Compatibility mode. Further information is located in Feature 277337: Edge
Browser Support.
1.3
Software
This release was tested on NET Framework 4.8. ArcGIS 10.8.1 is required.
21
MN008865A01-AF
Chapter 1: PremierOne Release Notes
Previous versions are no longer supported.
22
MN008865A01-AF
Chapter 2: Features and Functionality in Version 4.6.13
Chapter 2
Features and Functionality in Version

4.6.13
The 4.6.13 release includes the following enhancements and updates:
NOTE:
Following with previous releases, some features require additional configuration by your Motorola
Solutions support to be enabled in your agency's system.
2.1
4.6.13 Issues Resolved
Miscellaneous bugs were fixed in this release.
The full list of bugs addressed in this release will be provided by your support representative/Motorola contact
in a separate document.
● P1CAD - Application Exception Error on dispatch screen - Gold Image (228854)
● P1CAD - Dispatch Operation might be cancelled message received (232571)
● P1Mobile - 4.6.2.82 P1 Mobile Comments Manual Scroll not working properly (232723)
● P1CAD - Client Exception Error still Dispatches Units (234042)
● P1CAD - CAD Client Object reference not set to an instance of an object. upon dispatch (254359)
● P1CAD - GR01 Received an application error upon dispatch (288748)
● P1CAD reports- Dispositions Added After Units Cleared Not Inserted In MV_IncidentUnits (313666)
● P1MOB - Error on 2 MDTs during traffic stop (330913)
● P1MOB - Error Message:Failed to get message (340462)
● P1CAD - 2 Application Exception Errors on one console (DISP13) within 1 hour (382745)
● P1MOB - Mobile Error Report Upload notification disappearing before complete (400265)
● P1CAD - UnifiedCAD DB ST_WorkItemQueue_CTC has 13 in-use records. Supposed to have 1 (401016)
● P1MOB - Mobiles periodically freezes (401442)
● P1MOB - MOB not picking up change to LSM state code for Query screen (416975)
● P1CAD - Incident Alarm Level needs to be added to the MACH (MOSCAD) fire station alerting messaging
system (432068)
● P1CAD - P1 Paging upon Incident Dispatch was delayed by 10+ mins (441452 )
● P1MOB (Windows) - STAGING (468b) Additional Crew ID being Retained on Detailed Login Screen after
Closing P1 (442707)
● P1CAD - Sometimes Cad2CAD USU's not received at DEH (442811)
● P1CAD - When unit/apt is included in common place, the pick list does not change (461233)
● P1CAD - CAD Client Object Reference Error while dispatch and then clear before returned (462574)
● P1CAD - CryWolf alarm creation status not respecting IRF (473214)
● P1CAD - Vehicle drop downs with LSM not working in agency ST and VC (477116)
23
MN008865A01-AF
● P1CAD - Prov Unit Preassignments Notifications tab - LCFR/Dispatcher Supervisor login cannot see
values added to the Unit Preassignments Notifications tab. (483471)
● P1MOB (Windows): Defect Cosmetic display errors for role occur when switching between simple and
detailed login (484772)
● P1CAD - Unable to log in concurrent users on clients upgraded to 4.6.8b (485293)
● P1CAD - Users cannot login to CAD on multiple PCs at the same time following the recent upgrade
(485543)
● P1CAD - Active Orange County Warrant returning to unsolicited messages recipients (488876)
● P1CAD - Delay in receiving the 10-33 (emergency) notification pop-up alert in CAD from Radios (490098)
● P1CAD - Priority Notification Flags do not display on Pending and Incident Status Monitors for controlling
user as they should (490880)
● P1CAD - SCOM restarting APP Servers multiple times every day (491604)
● P1CAD - The Dispatch Operation Might Be Canceled, Please Confirm It Again (494309)
● P1MOB (Windows): When entering data in the MISC INFO field for the Vehicle or Person form
IncidentCommentKey is null in the RST_IM_Incident_Comment table (495461)
● P1CAD - Address Book error when user has comma in name when replying to message (496962)
● P1MOB (WINDOWS) - Error when attempting to click the area to open a report in RMS (498129)
● P1CAD - C2C Off duty MA unit never updated on Incident when placed On duty (501086)
● P1CAD - Concurrent Login Settings for client are not being honored. (502086)
● P1CAD - Manual Address Points Display in Matching Address column incorrectly (504112)
● P1CAD - Unhandled Exception-II form invalid unit in dispatch field (504391)
● P1MOB (Windows) - MDT marked off duty when provisioned not to after concurrent login try (505737)
● P1MOB (Windows) - Common places with apt/unit numbers missing cross streets (505812)
● P1CAD - Call icon on the mapping does not get cleared in some situations (506639)
● P1CAD - Reusing a work area will display the last dispatched unit in Dispatched Units field (506641)
● P1CAD - Unexpected manual address points appear as address validation matches when creating via
map (506642)
● P1CAD - Multiple CAD2CAD USUs sent instead on once (Prev 112561) (508526)
● P1CAD - Modified Circumstance Scrolling is choosing top entry on list regardless of user choice (509054)
● P1CAD - Unable to remove modifying circumstance from triggering criteria in provisioning (509081)
● P1CAD - Report Numbers not being Generated when Units Assigned (510609)
● P1CAD - Device KC03 errors (PSWGS.Cad.Client.IncidentManagement.IISummaryScreen -
AppendInfoToDuplicateAndAssociateIncidents) (510756)
● P1MOB - CAD query form fields w/ the mask option applied are passing asterisks and not the field value
to CSI (511116)
● P1CAD - CADS spamming pswgs.service.common.securityauthorization errors involving ActivateShift
(511787)
● P1CAD - Vehicle owner already populated in Vehicle tab (511898)
● P1CAD - Owner field populating in Vehicle tab from previous record (511903)
● P1MOB - After upgrading client drops connection to server when switching to cellular (513207)
● P1CAD - Map window not opening and logoff runs 30-90 seconds before confirmation dialog (513411)
● P1CAD - Training System (4611) Slow logout and session transfer on CAD client (513412)
24
MN008865A01-AF
● P1CAD - Invalid Persons or vehicles data come from ProQA when it should not (514067)
● P1CAD - Congruent Login Bug (517156)
● P1CAD - Query Response Summary Not Displayed (517474)
● P1CAD - Attempting to run new PR data causes app servers to crash (517767)
● P1CAD - UX command clears current incident and auto dispatches to stacked calls when it should only
exchange units. (517794)
● P1CAD - Right click status changes are not functioning for units with a secondary location suffix of (OD)
(518518)
● P1CAD - Provisioning loses connectivity to App Servers many times a day (520780)
● P1CAD - Location Name not being updated when location changed from form (521825)
● P1CAD - Application Error exception when initiating an incident (522330)
● WebClient - Users from FBP agency are not able to bookon to web client (522426)
● P1CAD - Complete Address Match Not Performed for ASAP Incident (524482)
● P1CAD - CAD slowness when importing Ani/Ali using RapidSOS (524932)
● P1CAD - Two Tone Paging Not Available 526455 [OHIOH] P1CAD: CAD appending a dash at the end of
unit number within notifications (525488)
● P1CAD - CAD4 Error object reference not set to an instance after dispatching a call (526557)
● P1CAD - 4.6.11 - Concurrent Login Not Working on CAD - Receive offline and status monitor error on first
CAD (527063)
● P1MOB (Windows) - 4.6.11 P1 Mobile Night Mode Query Form State Field Font Black Instead of Green
Causing to be Invisible (527066)
● P1MOB (Windows) - 4.6.11 Mobile - Query results do not display within incident on device that has both
CAD and Mobile client installed (527083)
● P1MOB (Windows) - Device Lock setting reverts after several sign on attempts, allowing user to sign in to
device (527233)
● P1CAD - SCOM Alerts for APP01 Recovery - PremierOne_01_CADP PrivateBytes (527340)
● P1CAD - 4.6.10 Provisioning GIS Data Points not functioning for names with an apostrophe (527418)
● P1MOB - Mobile Map Unit Status Changes. Does not bring Mobile Client to front when fields are required.
(527422)
● P1CAD - Provisioning Unit Preassignments Notifications tab. Cannot Add. - Permissions Issue. (527423)
● P1MOB (Windows) - State field in Night mode (527547)
● P1MOB (Windows) - 4.6.11 Field Initiate from Mobile Classic Map does not populate location (527975)
● P1MOB (Windows) - Mobile CAD client Night Mode Font Color issue (527997)
● P1MOB (Windows) - While in night mode within any query form the dropdown list values are not visible
after their values have been changed (528062)
● P1CAD - Status Monitors Groups disappear when logging into 2nd workstation with same user ID
(concurrent login) (528951)
● P1MOB (Windows) - Mobile - Query night mode is black text on black background (529808)
25
MN008865A01-AF
● P1MOB (Windows) - Draft Queries Return Abbreviations Instead Of Valid Value When Reopened
(530672)
● P1CAD - IR search functions not returning results (530738)
● P1CAD - Application Errors - Object reference not set to an instance of an object (531240)
● P1MOB (Windows) - ARL history showing speed of m/s instead of mph (531669)
● P1CAD - ARL element in ID command string adding Unit ID suffix causes issue with double click from
status monitor (531792)
● P1CAD - The original workstation has coverage groups removed on a successful concurrent second login
(532476)
● P1CAD - Provisioning Channel Group Configuration view/Modify issue (532759)
● P1CAD - P1 CAD person query returning results from RDW for a person even if they were deleted from
the call (534179)
● P1MOB - Users having to enter login credentials twice for NCIC connection (534456)
● CAD Clients Freezing at Clermont with RapidSOS (535485)
● P1MOB (Windows) - AIO - Unable to zip files for Mobile Maps (535647)
● P1CAD - Two Tone Paging Service Not Available Error (536082)
● P1CAD - App servers rebooting continuously - Renew expired Mobile Server certificate (539087)
● P1MOB (Windows) - Capabilities Incomplete on Login Form When Unit Off Duty (539178)
● P1MOB (Windows) - Mobile CAD 4.6.10a is saving the additional crew on detailed logon form (539188)
● P1MOB (Windows) - Additional crew are retained between login sessions (539189)
● P1MOB (Windows) - 4610a clients dropping connection frequently (539204)
● P1CAD - IR Command can be used even when blocked. (540988)
● P1CAD - KC08B received an unhandled exception for Object reference not set to an instance of an object
(541325)
● P1CAD - Unit Association Dropped from Dispo when Incident Mod Circ Updated 543323 [DOUNE]
P1CAD: PMDC Services restarting app servers (541649)
● P1CAD - CAD024 frozen for approx 34 seconds CS0272574 (544849)
● P1CAD - Fail to dispatch unique unit ID from dispatch form (544903)
● P1CAD - Popup Window Visual Alert for Messages does not display (545447)
● P1CAD - When adding an additional vehicle to an incident, the previous vehicle owner information gets
inserted. (547669)
● P1CAD - PSWGS.Common.CommandProcessor.dll is missing from the CS Services folder (549658)
● P1CAD - PSWGS.Common.CommandProcessor.dll is missing from the CS Services folder (549688)
● P1MOB - Error when attempting to Authenticate to Records from Mobile using Send to Reports Button
(550312)
● P1CAD - APX-NEXT radio interface into P1 not working (500856)
● P1CAD - Location search not finding address point, only common name (521904)
26
MN008865A01-AF
2.2
CAD New Functionality
The following new CAD features are included in this release. The Azure DevOps number is included for
reference.
2.2.1
Show Unit ID of Who Sent Message on CAD Client WAA
From Field in Messaging (524516)
This feature allows users to easily view the Unit ID of a mobile unit message sender, also called the
originator, in the Messages form.
Previously, the first name and last name of the originator displayed in the From field of the Messages form.
Users were not able to see the Unit ID of the originator unless they hovered their mouse over the From field.
Figure 1: Previous Originator Display in From Field
Now, the From field is updated to show the Unit ID of the mobile unit message originator first, followed by the
last name and first name. This allows users to quickly view the Unit ID of the message originator at a glance.
Figure 2: New Originator Display with User ID in From Field
27
MN008865A01-AF
This is now the default display setting for any message sent from a mobile client. This change does not have
to be provisioned by your Agency.
2.2.2
Ability to Update Location Information on Associated
Incidents (526355)
CAD users now have the option of updating incident location information for either a single incident or
distributing it across all associated incidents in the form of:
● An Incident Update against the associated incidents when the location information is identical to the
updated incident prior to the update.
● A priority comment against the associated incidents when the location information does not match the
updated incident prior to the update.
Figure 3: Priority Comment
Provisioning Updates
This feature is available on the PremierOne CAD Client Incident Initiation Management form and command
line. The option to set the default check box behavior has been added to the Incident Management
→ Service Settings → Initiation Defaults page in provisioning.
Figure 4: Initiation Defaults - New Check Boxes
28
MN008865A01-AF
If the Set "Update associated” for location updates to Yes in the Incident Management form check
box is checked for the user’s agency, the Update associated checkbox displayed in the Summary form of
the Incident Management form is checked by default. If this provisioning item is not checked, the Update
associated check box in the Summary form of the Incident Management form is unchecked by default.
User Updates
Figure 5: Incident Management Form - Update Associated Checkbox
When the incident's location information is updated and the Update associated check box is checked in the
Incident Management form, CAD attempts to update location information across all associated incidents and
one of the following actions occurs:
● If the location information exactly matches the updated incident’s location prior to the update, the
associated incident information updates.
● If the location does not match, a priority comment is added to that associated incident informing the user
that the location information was changed on an associated incident.
If the Update associated check box is unchecked, the updated location information is only applied to the
specified incident.
For more information, see the PremierOne CAD and Mobile Provisioning Guide and the PremierOne CAD
User Guide.
Command Line Identifier Updates

The new command line identifier LAI has been added to the Incident Update (IU) command to indicate
whether an update to the incident location information on the command line should be applied to associated
incidents (LAI;Y) or just to the specified incident (LAI;N).
For LAI;Y command line transactions, the associated incident will only be updated if the location info exactly
matches the updated incident’s location prior to the update. If the location does not match, a priority comment
is added to that associated incident informing the user that the location information was changed on an
associated incident.
For more information see the PremierOne CAD User Guide and the PremierOne CAD Commands Quick
Reference.
29
MN008865A01-AF
2.2.3
Database Queries Added for Radio ID, Vehicle ID and
Talk Group (545060)
Stored procedure queries have been added so that the following queries can be easily provisioned for use in
CAD and Mobile.
● Vehicle ID query - Queries the PremierOne Data base to indicate the unit a vehicle is assigned to.
● Radio ID query - Queries the PremierOne Data base to indicate the assignment for a specific radio.
● Talk Group query - Queries the PremierOne Data base to display the talk groups assigned to a specific
unit.
To provision these queries, the Enable Local SQL Query option must be selected on the Query → Suite
Level Setting → Interfaces screen and a SQL connection string must be entered in the Connection String
text box. For more information on connection string formats, please refer to Interface Field Additions and
Modifications for Local Database SQL Queries in the PremierOne CAD & Mobile Provisioning Guide.
Figure 6: Enable Local SQL Query and Connection String Box on Query > Suite Level Setting >
Interfaces Screen
After ensuring that the SQL connection string is entered and saved on the Interfaces page, administrators
must then navigate to the Query → Suite Level Setting → Query Types → Interface Fields screen and
enter the SQL statement in the SQL Query String text box.
30
MN008865A01-AF
Figure 7: SQL Query String Text Box on the Query>Suite Level Setting>Query Types>Interface Fields
Screen
The SQL Statement should be formatted as one of the following:

● exec GetRadioInfo_ForLocalQueryInterface {RadioId} - Query accepts a Radio ID. No
agency ID allowed as radio ids are unique across all agencies.
● exec GetTalkgroupsForUnit_ForLocalQueryInterface {UnitID}
- Query accepts a Unit ID. You can enter E1 if there is only one E1 in the system. Otherwise, you must
enter FD/E1. Shift ID is supported and may be required to make unit id unique.
● exec GetVehicleInfo_ForLocalQueryInterface {AgencyId},{VehicleId}
- Query has two fields: Agency and Vehicle ID. Agency can be in its own field, or set as default, or
Vehicle ID may contain the agency, for example FD/VEH1234, in which case the Agency ID field can be
left empty.
● exec GetVehicleInfo_ForLocalQueryInterface NULL, {VehicleId} - Alternate version of
the vehicle query where the Agency ID, if required to make the vehicle unique, has to be entered as
FD/VEH1234 in the Unit ID field. The query cannot access the working agency setting, so if the user
enters VEH1234 only that vehicle has to be unique.
For more information on the SQL Statement, see Interface Field Additions and Modifications for Local
Database SQL Queries in the PremierOne CAD & Mobile Provisioning Guide.
When provisioned, the stored procedure queries will display on the Queries page and the Queries
Responses page.
31
MN008865A01-AF
Figure 8: Vehicle ID Stored Procedure Query on Queries Page
Figure 9: Vehicle ID Stored Procedure Query on Query Responses Page
2.3
Provisioning New Functionality
The following new Provisioning features are included in this release. The Azure DevOps number is included
for reference.
32
MN008865A01-AF
2.3.1
New Provisioning Field for Incident Response Factors
(487893)
A new Description field has been added to the Incident Response Factor provisioning page.
Figure 10: Description Field on Incident Response Factor Provisioning Page
This field is only intended to be used within the new Workstation 2.0 devices.
For Incident Response Factors that are currently provisioned, the data populated in the Description field
contains the description provisioned against the incident type selected from the Inc.Type column, followed
by the description provisioned against the modifying circumstance selected from the Mod.Cir column if
applicable. If the user is on the Agency Type level, the information in the Description field can be edited.
However, on the Agency level, the information in the Description field is read-only and cannot be edited.
NOTE: A new specialized import spreadsheet that allows you to update existing Incident Response Factor description
amounts of description changes in preparation for Workstation 2.0 devices. This spreadsheet only allows you to upda
Factor's description. The spreadsheet can be found on your PremierOne CAD application servers under the following
\Motorola\PremierOne\PremierOne_01_CADP\services\PSWGS.Cad.Server.Provisioning\Business
Filename: IRF_AgencyType_IRFDescription_Import_Template.xlsx
33
MN008865A01-AF
2.3.2
VerifyByLocationAndCity Setting Moved to Provisioning
(494511)
The VerifyByLocationAndCity setting in the PremierOne Configuration Tool has been deprecated. If a user
makes a selection for this setting in the configuration tool it will not be effective.
This setting has been moved to Provisioning as of the 4.6.13 release and is now available at the Agency
level. With this move, the default setting will be True. If an Agency wants the setting to be False, they will
have to change it when they upgrade to 4.6.13.
Figure 11: Outdated Location for VerifyByLocationAndCity - Configuration Tool
34
MN008865A01-AF
Figure 12: New Location for VerifyByLocationAndCity - Provisioning
See the PremierOne CAD and Mobile Provisioning Guide for more information.
2.3.3
Refactor the Incident Management Form to Optimize
Update and Dispatch (525692)
Submitting the Incident Management form from the Dispatch tab requires the system to perform all updates
applied within the Incident Management form before performing the dispatch to ensure that the dispatch
operation contains the most current incident data.
When users cleared the Incident Management form from the CAD Client Work Area before the system
completed the transaction, they could receive a warning because of the update-first-then-dispatch
processing: The Dispatch operation might be canceled, please confirm it again.
The Incident Management form has been refactored to eliminate the above message by improving the
reliability of processing the transaction submitted from the Dispatch tab.
IMPORTANT: In the unlikely event that your CAD operator encounters this message when submitting
the Dispatch tab, please inform your support representative with the details of the transaction that
caused this message to be displayed.
35
MN008865A01-AF
2.3.4
Support Modern Browsers (496229, 496230)
The support for modern web browsers continued in 4.6.13 with the addition of the Unit Management module
and Resources module being made available in the Chrome web browser. Support for all of provisioning in
the Edge browser in Internet Explorer (IE) mode continues.
Chrome also supports Unit Recommendation from the previous release.
2.3.5
Unsolicited Responses Mnemonics (488876)
Improvements were made to query response functionality. For responses that are returned associated to
a mnemonic without a transaction ID, those responses will be returned to all devices associated with the
mnemonic. In the past this type of transaction was identified as unsolicited and this change has corrected that
behavior and prioritized the responses correctly.
There is no provisioning that needs to take place. The configuration file for this change has been updated in
this release.
2.3.6
Additional Fields Added to Personnel Import API
(536044)
The fields Organization ID and Department ID have been added to the Personnel Import API to allow third
party applications to pass this information to PremierOne provisioning.
Figure 13: Personnel Import API With Organization ID Field and Department ID Field
2.4
Mobile New Functionality 4.6.13
The following new Mobile features are included in this release. The Azure DevOps number is included for
reference.
PremierOne Mobile for IOS V 4.6.231109

● Compatible with PremierOne CAD 4.4 to 4.6.13
● Implemented Reply/Reply All/Forward/CC/BCC capabilities and attachments for IOS message
● Integrated the 10-21 application with P1 Mobile iOS to make phone calls
PremierOne Mobile for Android V 4.6.2311.8

● Integrated the 10-21 application with P1 Mobile Android to make phone calls
● Implemented PR data to upload automatically
36
MN008865A01-AF
2.4.1
iOS Message - Reply/Reply All/Forward, Including CC,
BCC, and Attachments (419541)
The PremierOne iOS Compose Message feature now provides users the ability to use the Reply, Reply All,
and Forward functions. Users can access these functions from the Messages List screen and the Message
Detail screen.
Reply/Reply All/Forward from Messages List Screen

From the Messages List, users can swipe right to reveal the Reply, Reply All, and Forward buttons.
Figure 14: Reply, Reply All, and Forward Buttons in the Messages List
NOTE: If the user continues to swipe after these buttons appear, a quick action occurs that has the
same result as pressing the Reply button.
Users can perform the following actions from the Messages list:
● Reply - When the user selects the Reply button, the Compose Message screen opens. The To field
contains the information of the sender of the original message, the Subject field contains the subject
of the original message with the prefix Re added. And the Body field contains the body of the original
message after a separator.
37
MN008865A01-AF
Figure 15: Reply button and Reply in the Compose Message Screen
If a message already contains attachments, an alert with the message Would you like to add
received attachments? displays. Users can select Yes to compose a new message and add the
original attachments, or select No to continue without them.
● Reply All - When the user selects the Reply All button, the Compose Message screen opens. The To
field contains the information of the sender of the original message, the Subject field contains the subject
of the original message with the prefix Re added, and the Body field contains the body of the original
Figure 16: Reply All in the Compose Message Screen
38
MN008865A01-AF
If a message already contains attachments, an alert with the message Would you like to add
received attachments? displays. Users can select Yes to compose a new message and add the
original attachments, or select No to continue without them.
● Forward - When a user selects the Forward button, the Compose Message screen opens. The Subject
field contains the subject of the original message with the prefix Fw added. The Body field contains the
body of the original message after a separator.
Figure 17: Forward in the Compose Message Screen
If a message contains attachments, the attachments from the original message are included in the new
message without requiring confirmation via an alert such as Reply or Reply All. Users have the ability
to remove any automatically added attachments by tapping the Trash icon on the Compose Message
screen.
For each of these actions, recipients can be added in the To, Bcc, and Cc fields. Users can also modify the
priority level of each message on the Priority dropdown list, and attachments can be added.
Currently, an address book functionality to manage contacts does not exist, but will be added in future
releases.
Reply/Reply All/Forward from Message Details Screen

Users can also use the Reply/Reply All/Forward features from the Message Details screen.
When a user taps on a message in their inbox, the Message Detail screen displays. At the bottom of the
Message Details screen, users can tap the arrow button to open the menu.
39
MN008865A01-AF
Figure 18: Arrow Button and Menu
Users can select one of the following options from the menu:
● Reply - When the user selects the Reply button, the Compose Message screen opens. The To field
contains the information of the sender of the original message, the Subject field contains the subject
of the original message with the prefix Re added. And the Body field contains the body of the original
If the original message contains attachments, the menu displays the Reply… submenu. If the user wants
to compose a new message and add the original attachments, they can select With Attachments from
the Reply… submenu. To reply without the original attachments, they can select Without Attachments.
40
MN008865A01-AF
Figure 19: Menu with Reply… Submenu
● Reply All - When the user selects the Reply All button, the Compose Message screen opens. The To
field contains the information of the sender of the original message, the Subject field contains the subject
of the original message with the prefix Re added, and the Body field contains the body of the original
If the original message contains attachments, the menu displays the Reply All… submenu. If the user
wants to compose a new message and add the original attachments, they can select With Attachments
from the Reply All… submenu. To reply without the original attachments, they can select Without
Attachments.
41
MN008865A01-AF
Figure 20: Menu with the Reply All… Submenu
● Forward - When a user selects the Forward button, the Compose Message screen opens. The Subject
field contains the subject of the original message with the prefix Fw added. The Body field contains the
body of the original message after a separator.
If the original message contains attachments, the menu displays with a Forward button. This button is not
a submenu. Tapping the Forward button automatically adds the original attachments without any alerts or
options.
42
MN008865A01-AF
Figure 21: Menu with Forward Button
For each of these actions, recipients can be added in the To, Bc, and Cc fields. Users can also modify the
priority level of each message on the Priority dropdown list, and attachments can be added.
Currently, an address book functionality to manage contacts does not exist, but will be added in future
releases.
For more information, see the PremierOne iOS User Guide.
2.4.2
iOS/Android - 10-21 Police Phone App Integration
(522613, 522614)
Users now have the option to initiate a call with the native dialer application or make an anonymous call
with the 10-21 Police Phone application from within PremierOne Android and iOS. Making a call with the
10-21 app allows for privacy when using a personal device and for audit functionality of phone calls made for
investigative purposes.
Changing Call Defaults

By default, Mobile uses the native phone dialer to make calls, but users can change the default method in two
ways:
● Before logging in to the mobile app, users can navigate to the Sync menu and tap Call Default. From the
Call Default menu, users can select Phone, 10-21, or Both as the default method.
● After logging in to the mobile app, users can navigate to the Settings page, tap Call Default, and select
Phone, 10-21 or Both as the default method.
43
MN008865A01-AF
Figure 22: Figure: Call Default List
NOTE: When Both is set as the call default, the user is prompted to choose between the native
phone dialer or 10-21 when placing a call.
Making Calls
To make a call, users can tap a phone number hyperlink on the Incident Details, Incident Details -
Comment or Incident Details - Personal Information screens.
Figure 23: Phone Number Hyperlinks on the Incident Details - Comment and Incident Details -
Personal Information Screens
When a user taps on a hyperlink phone number, the designated call default app opens and users can tap the
Call button to place the call.
If the call default is set as Both, a Call dialog box displays reading: Which application would you
like to use to make a call to (415)-xxx-xxx?
44
MN008865A01-AF
Figure 24: Call Dialog Box
Users can select one of the following options:

● Cancel - Cancel the call and return to the previous screen.
● Phone - Make the call using the native phone dialer. Tapping Phone opens the default dialer.
● 10-21 - Make the call using the 10-21 Police app. Tapping 10-21 opens the 10-21 Police app.
NOTE: If a user attempts to make a call using the 10-21 Police app but they are not logged into the
app, they are required to login. After login, you may have to return to the phone number and tap the
hyperlink again to complete the call.
If a user attempts to make a call using the 10-21 Police app but the app is not installed, an Info
dialog box displays, which reads: 10-21 app is not installed on your phone. Do you want to
download it from <App Store or Google Play>?
Users can tap Cancel to close the dialog box and return to the previous screen, or tap Download to
navigate to the App Store/Google Play to download 10-21. Users can also choose Call with Phone
to complete the call with the default phone dialer instead of the 10-21 app.
Figure 25: Info Dialog Box
Administration Settings
Administrators can configure the callDefault setting for their agency’s users using a Properties file and the
MDM tool. The values for callDefault include:
● callDefault=Phone
● callDefault=10-21
● callDefault=Both
For more information, see the PremierOne Mobile Android and iOS Administration Guide.
45
MN008865A01-AF
2.4.3
Mobile Windows - Disposition Enhancements -
Disposition Filter (519663)
The Disposition Filter on the Incident screen provides users with the ability to search through a list of
dispositions by typing the first few letters of the disposition into the search box.
The list of dispositions displayed in the search box updates with each letter entered and displays only items
that match the search input. For example, if a user types AD in the search box, it displays ADVISED and any
other dispositions that contain AD.
Figure 26: Disposition Search Bar and Drop-down Results List
This allows users to quickly narrow down the list to the related dispositions and find the disposition they need
without scrolling. If there is no disposition found that matches the search input, the message Disposition
not found displays.
Figure 27: Disposition not found Message
If a user wants to select a disposition manually without the Disposition Filter, they can manually scroll through
the disposition list to find the correct disposition.
2.4.4
Mobile Windows - Disposition Enhancements - Incident
Number in Disposition Box (519664)
The Close Incident dialog box now contains a field that displays incident numbers as a hyperlink.
When an incident number is generated, the number automatically populates in the Inc. Number field of the
Close Incident dialog box.
46
MN008865A01-AF
Figure 28: Disposition Box with Incident Number Field
The incident number displays as a hyperlink. When a user clicks the hyperlink, the incident summary displays
behind the Close Incident dialog box in the active work area.This allows the user to confirm and view the
incident information while adding dispositions and clearing their incident.
Figure 29: Incident Summary Displayed in the Active Work Area
2.4.5
Mobile Windows - Disposition Enhancements - Adding
Additional Reporting Fields to the Disposition Area
(519665)
The ability to activate an additional section called Disposition Reporting Fields (DRF) on the Disposition
screen has been added.
NOTE: Provisioning options for this configuration will be coming in a future release.
Up to six configurable checkboxes can be added to the DRF section.

These additional DRF checkboxes allow agencies to capture more information related to incidents. For
example, agencies can configure a DRF check-box to allow users to identify whether an officer was wearing
a body worn camera, whether a supervisor was present at the incident, whether there is a digital car video
for the incident, and so on. This additional information can be used for reporting, auditing, and internal affairs
investigations.
47
MN008865A01-AF
The additional DRF checkboxes are disabled by default. The fields can be enabled by using the
PremierOne Configuration Tool. Admins can select the Enable Disposition Reporting Fields checkbox
in the Production section of the Mode Selection screen.
Figure 30: Enable Disposition Reporting Fields Checkbox - Mode Selection Screen
The DRF fields must also be enabled in the All-in-One Installer (AIO). On the Configuration → Deployment
Device Configuration screen, the Production category must be set to a value of True to enable the DRF
checkboxes.
Figure 31: Enable Disposition Reporting Fields Checkbox - Value Set to True
The DRF can be customized by modifying the following file within the Configuration Tool:
C:\ProgramData\Mobile Client\config\DispositionReportingFieldsConfig.xml
48
MN008865A01-AF
Each reporting field in this configuration file is defined by the following four values:
● Description - This value displays on the dispositions screen next to the checkbox to identify what the
checkbox is used for.
● Display Order - This value determines the order in which the checkboxes are displayed on the
dispositions screen. A maximum six of six can display with three in each row.
● Checked Value - This value determines the information that is added to the incident history if the
checkbox is selected when closing an incident.
● Unchecked Value - This value determines the information that is added to the incident history if the
checkbox is not selected when closing an incident.
A customized DRF may look like the following example:
<ReportingField>
<Description><Digital in car video [DCIV]></Description>
<DisplayOrder><3></DisplayOrder>
<CheckedValue><Digital in car video present></CheckedValue>
<UncheckedValue></UncheckValue>
</ReportingField>
When enabled, a default number of three fields appear on the Disposition screen, but this number can be
increased up to six.
Figure 32: Configured Additional Fields on Disposition Screen
The information documented within the additional fields appears in the Incident History in both the Mobile
and CAD clients. If the Enable Disposition Reporting Field option is not selected in the Configuration Tool,
these additional fields do not appear in the Disposition screen.
Figure 33: Incident History Screen - Mobile Client
49
MN008865A01-AF
Figure 34: Incident History Screen - CAD Client
2.4.6
Android - Automate PR Data Upload (495415)
PR Data upload for the PremierOne Mobile Android application is now performed automatically.
Users do not need to open provisioning and manually upload PR Data in order to login to the PremierOne
Mobile Android application. Instead, they can immediately login to Mobile.
NOTE: If a user needs to create webmaps, they will still need to open provisioning before login to do so.
After the initial login, the application may take several minutes to automatically retrieve and update the PR
Data.
The option to manually update PR Data still exists for users but is not required.
For more information on deploying PremierOne Mobile for Android, please see the PremierOne Mobile
Android and iOS Administration Guide.
2.4.7
iOS - Automatic Application Updates
We are now using the phased release of PremierOne Mobile for iOS applications and recommend that you
take the following actions to prevent the application from not working in the future:
● Disable automatic updates for each P1 Mobile iOS user
● Test the new version of the application on your device before it is installed on all devices
NOTE:
A user’s Apple ID randomly determines if automatic updates are enabled for their account. You can
check the settings if you are not sure if an account has automatic updates turned on.
Users are not notified that they are in a phased release of the application and anyone can manually
download an application update that is in phased release from the App Store at any time after the new
version is released, even Day 1 of the phased release schedule
50
MN008865A01-AF
Phased release means new versions of the application are released over a 7-day period to a percentage of
our users who have automatic updates turned on. Releasing new application versions using phased release
gives us the ability to revert our update if there are any significant problems with the new version.
The follow percentage of users will have access to the new release on the following days:
Table 1: Days of Phased Release and Percentage of Users
Day of Phased Release Percentage of Users

1 1%
2 2%
3 5%
4 10%
5 20%
6 50%
7 100%
IMPORTANT: If your application stops working, contact Motorola Support immediately.
For more information about how to disable automatic updates for your account, see the Apple Support article
How to turn on or turn off automatic updates on your iPhone or iPad.
51
MN008865A01-AF
Chapter 3

4.6.12
NOTE:
3.1
4.6.12b Issues Resolved
● P1MOB - After upgrading client drops connection to server when switching to cellular (541422)
● P1CAD - Fail to dispatch unique unit ID from dispatch form (543044)
3.2
4.6.12a Issues Resolved
● P1MOB (Windows) - While in night mode within any query form the drop-down list values are not visible
● P1CAD - Map window not opening and log off runs 30-90 seconds before confirmation dialog (532781)
● CAD client is not being logged off after the force log off or lock device mechanisms (532780)
3.3
● P1CAD - Two additional PER INFO transaction type transaction time gets updated from the third PER
INFO transaction time (267063)
● P1MOB (Windows) - Incident Recall Search Agency drop down list does not default back to ALL when
clearing search criteria (297343)
● P1MOB (Windows) - Unit Icon hesitation on new Motorola Mobile Map (316021)
● MOB MAP - Universal/Mobile Map Directions Disappearing with Right Click (409464)
● P1CAD - Keyboard Control Issue in Dispatch Screen After Choosing Pre-empt Option (412289)
52
MN008865A01-AF
● SCOM- PCADAPP04 Not Being Monitored by SCOM (426093)

● P1CAD - Tear and Run shows unit but MACH Alert app does not (426636)
● P1MOB (Windows): STAGING (468b) Premise Hazard Being Read Aloud Multiple Times (438765)
● P1CAD - MapBookPage is missing from Alerting, therefore not sent to TearNRun printout (442973)
● P1CAD - New Month - Incident Number shows previous day on status monitor when month and year is
shown (456424)
● [iOS] Default dispo comments added to incident from handheld when adding a person or vehicle
(457023)
● P1CAD - Verified location showing 0.000000 latitude and longitude when address / comment updated by
another dispatcher (459854)
● P1CAD - Fire station alerting not sending tones to station on Move Up command (DV_Logging Table)
(459903)
● P1 Handheld - Incident status bar is Unresponsive (Spinning wheel) (460286)
● P1CAD - Entry in Manual Address Points with forward slash Causes All Address Verification to Fail
(460663)
● P1MOB - Mobile Map 2.14.8390.14 Unit Icon and Base Maps Icon Intermittently Not Displaying (466840)
● P1CAD - typing on a premise hazard display updates the wrong tab (470144)
● P1CAD Transaction commands taking 1 to 4 second delays in all instances (474263)
● P1CAD - Prov, Send all unit statuses every: X seconds - changes won't save (476504)
● P1 CAD - 4.6.10 CAD - Invalid Command Line Submission "invalid value" text now requires deletion prior
to resubmission (477142)
● P1MOB - Mobile user receives “This program might not have run correctly…” error while logging off the
client. (480520)
● P1MOB (Windows) - In P1 Mobile 4.6.10.74 Smart Copy from Query into Incident Person/Vehicle is no
longer working (484967)
● P1CAD - CAD Records not transferring to RMS correctly - CAD Issue (485929)
● P1CAD - Turning ON/OFF purge operations in prov not being audited (485974)
● P1CAD - Right-Click actions on Status Monitors take more than 1-2 seconds to update visually (486975)
● P1CAD - Cursor jumps to command line (487561)
● P1CAD - CAD clients go offline after server upgrade (489402)
● P1CAD - 4.6.10a CAD - Invalid Command Line Submission "invalid value" text now requires deletion prior
● P1CAD - Syntax error notification "Invalid Value" not clearing causing command line error. (490129)
● P1MOB(Windows) - Missing Environment Indicator Image (491816)
● P1CAD - 4.6.10a CAD - Invalid Value not removed from Command Line when there is an Error (492471)
● P1MOB (Windows) - Error Message Received after Logging Out of P1 - This Program might not have run
correctly (493151)
● P1CAD - CAD is sending RMS Calls for Service numbering incorrectly (494058)
● P1CAD - Incident Icon on Map Disappears after not selecting a common place (495164)
● P1CAD - Call for Service Numbers are being generated incorrectly from 12:01 am - 03:00 am every day.
(495721)
53
MN008865A01-AF
● P1CAD - NCIC returns not visible in CAD (497327)

● P1CAD - Call for Service Numbers are being generated incorrectly (497390)
● P1CAD - CS service cause PCADAPP servers to restart (498642)
● P1MOB (Windows) - 4.6.11.81 Is Not Installing MagTekServiceObject.dll Client will not initialize MAgStrip
Reader (499882)
● CryWolf Issues On New Stack with Updated CAD (501523)
● P1CAD - CAD Status Monitors not updating (502646)
● P1CAD - 4.6.11 Client Errors - The client repeatedly shows the error: The PremierOne CAD Client is
having a problem updating one or more status monitors. (505303)
● P1CAD - History Recommendation Tool does not show Units for ARL Rec (505741)
● P1CAD - AIO Deployment Portal displays incorrect OS version for mobile device (505815)
● P1CAD - Partition_RDW Job Failed - Change to system (507248)
● P1CAD - Incident CFS to RMS created after midnight are getting converted from UTC to local time
incorrectly (508420)
● P1CAD - AIO 4.6.11 Does not zip map files (510244)
● P1CAD - Status monitor update/Client notification delays caused by
procClientNotificationSelectCurrentCurrentJurisdictions_4611_1 (510543)
● P1CAD - CFS numbers for P1Records created after midnight are not getting converted from UTC to local
time correctly (511697)
● P1CAD - Query Responses Disappearing (512470)
3.4
reference.
3.4.1
Highlight Recommended Units that are In Station on
Dispatch Form (476603)
Knowing if a Unit is in Station can be essential for a Dispatcher. The ability to change how units are
displayed on the Incident Dispatch → Dispatch Units form has been added to provisioning in Unit
Recommendations → Settings → Dispatch List. This new setting has three options: Units Only, Indicate
Units that are in an In-Station Status and Display all Units in their provisioned Unit Status Colors.
54
MN008865A01-AF
Figure 35: Display Setting Drop Down List From the Unit Recommendation - Settings - Dispatch List
Provisioning Page
Administrators can choose from three visual display options for recommended units.
Units Only Option

Units Only is the default setting and leaves the behavior as it was before this feature enhancement was
added. With this option recommended units are displayed without detailing if the unit is IN or OUT of Station.
Figure 36: Default Setting- Unit Only Setting No Highlight or Notation of Units In or Out of Station
Indicate Units that are in an In-Station Status

Enabling the Indicate Units that are In an In-Station Status will display Units that are In Station in Red with
an Asterisk next to the unit.
55
MN008865A01-AF
Figure 37: Indicate Units That are in an In-Station Status Setting - Units That are In Station are
Highlighted in Red and have an Asterisk next to unit ID
Display all Units in their provisioned Unit Status Colors.

Enabling the Display All Units in their provisioned Unit Status Colors will display units in the color of the
status that corresponds to the Status Monitor display settings.
Figure 38: Display all Units in their provisioned Unit Status Monitor Colors
3.4.2
AI for CAD Comments – Comments Parser (484465)
The comments parser using AI provides the ability for person names, drivers license numbers, vehicle plates,
VIN Numbers and associated person and vehicle information to be entered once in the Incident Initiation
form or Incident Update form comments field and automatically populate person and vehicle tabs upon
submission. This allows CAD Users to enter data quickly without having to navigate to separate tabs and if
56
MN008865A01-AF
provisioned to automatically run the default vehicle and person query. The parsed data will remain viewable
in the comments of the incident.
Users still have the ability to manually enter this data directly into the Vehicles and Persons tabs.
NOTE: This does not apply to Mobile or Handheld.
Figure 39: Incident Initiate Form - Comments Text Box
Figure 40: Incident Management Form - Persons and Vehicles created from parsed comment data.
This feature can be enabled and disabled from the Role Permissions→Roles→General tab in provisioning.
57
MN008865A01-AF
Figure 41: Provisioning - Enable/Disable Comments Parsing Option
3.4.3
Microsoft 2019 Support (467860)
PremierOne is now supported on Windows Server 2019, SQL Server 2019 and SCOM 2019.
Server Configuration Tool Updates

If you were previously using a version older than 4.6.12 on the same servers, you must remove the older
management packs from the SCOM server by using the Server Configuration Tool in order to install the latest
version. This is done by using the RemoveOldManagementPacks check box.
The RemoveOldManagementPacks checkbox is enabled by default and is used in the following situations:
● If you are upgrading management packs older than version 4.6.12.2, the check box must be enabled.
After upgrading, you can uncheck the RemoveOldManagementPacks box.
● If you are a new customer installing version 4.6.12 or higher, you can uncheck the
RemoveOldManagementPacks check box because SCOM is empty and there are no files to remove.
● If you are upgrading from 4.6.12 to a higher version, you can uncheck the RemoveOldManagementPacks
checkbox. Leaving the box checked will increase the amount of time spent running the Server
Configuration Tool and may cause errors.
NOTE:
If you have custom management packs, you will need to manually export the custom packs. The
RemoveOldManagementPacks check box is not able to remove custom packs.
58
MN008865A01-AF
Figure 42: RemoveOldManagementPacks Checkbox in PremierOne Server Configuration Tool Window
After running the Server Configuration Tool, the removal of outdated management packages begins followed
by the installation of the updated management packages.
Reporting Configuration Tool Updates

A new SSIS Package Version drop-down list has been added to the PremierOne Reporting Configuration
Tool on SSIS Package Execution tab. This allows users to choose the appropriate SSIS Package Version
depending on the platform and Microsoft SQL Server version installed.
59
MN008865A01-AF
Figure 43: SSIS Package Version Drop-Down List in PremierOne Reporting Configuration Tool
Window
For Microsoft SQL Server 2017, users should choose value 2017 from the SSIS Package Version drop-
down list. For Microsoft SQL Server 2019, users should choose value 2019.
The chosen value is used to copy and execute the correct version of SSIS package dtsx files responsible for
running SQL Server jobs syncing the data between PremierOne CAD databases and reporting services
databases.
3.4.4
MACH Alert Add Ability to Change Tone for Move Up
and Print Map Page Data (496259)
Users have the ability to differentiate between sending a tone for a dispatched incident and a move up. This
tone is different from a regular incident tone. Users also have the ability to print map page data.
Change Tone for Move Up

To add the ability to change the tone for a move up, administrators must configure changes in the System
Management Tool Portal.
60
MN008865A01-AF
From the Edit tab, navigate to ToningDSA → Toning

Figure 44: Edit Tab - ToningDSA > Toning Codebox for Changing Tone
In the code box, administrators should add the following string:

<add key="MoveupAlterTone" value="<variable>" desc="Move up Alter Tone">
For the <value> variable, you can use a value between 01 and 08.
Print Map Page Data

To add the ability to print map page data, administrators must configure changes in the System Management
Tool Portal.
To configure the necessary Tear and Run data, from the Edit tab, navigate to PagingToningTnRDataFormat
→ PagingToningTVRInterface
Figure 45: Edit Tab - PagingToningTVRInterface Code Box
61
MN008865A01-AF
In the code box, administrators should add the following string:


<MapPage label="MapPage: " color="Black" font="18" bold="true"
fontfamily="arial" isNewline="true" contentcolor="Black" contentfont="24"
boldcontent="true" contentfontfamily="arial" contentsize="20" />
The following values are all configurable:

● <label color>
● <font>
● <bold>
● <fontfamily>
● <isNewline>
● <contentcolor>
● <contentfont>
● <boldcontent>
● <contentfontfamily>
● <contentsize>
NOTE: It is recommended that you add the MapPage lines within the Location grouping.
To configure the necessary Toning data, navigate to ToningDSA → Toning

Figure 46: Edit Tab - ToningDSA > Toning Codebox for Print Map Page Data
In the code box, administrators should enter the following string:

<add key="SendOpCode05" value="Y" desc="Determines whether to send
OpCode05 message (after OpCode01)"> </add> <add key="MapPage" value="Y"
desc="Determines whether to send MapPage with OpCode05 message (after
OpCode01)">
If this line is not included, the data is not sent in the Mach Alert. Additionally, If either the SendOpCode05
value or the MapPage value are set to N (No), the data is not sent in the Mach Alert. The values must both be
set to Y (Yes).
To modify the device configuration data, navigate to Toning → Toning
62
MN008865A01-AF
Figure 47: Edit Tab - Toning > Toning Code Box
The data in the code box should match the following configuration:
</QueueManagerConfiguration>
<Devices>
<DeviceConfiguration Category="Toning"
Id="MOSCAD" Key="2553071b-7f0c-40e4-9916-08de678e84b6"
ResourceAssemblyKey="EB022BDF-8C1D-4c7f-878E-1AF2E5E6405B"
HeartbeatFlags="NotSupported" Timeout="0" MessageFormat="FormattedByteArray"
AcknowledgementsRequired="true" Encoding="ASCII"
ConnectionStringKey="UnifiedCad" MaximumMessageLength="0" ListenerPort="13006"
AutoCloseConnectedSocket="false" Model="Client" LogInboundMessage="false"
LogOutboundMessage="false" InterfaceLogsFolder="C:\" LogToFile="false">
<CustomDeviceConnector AssemblyName="PSWGS.Cad.Interfaces.Toning"
TypeName="PSWGS.Cad.Interfaces.Toning.ToningDeviceConnector" />
<FormattedByteArrayConstants StartOfText="0X02" EndOfText="0X03"
ChecksumAlgorithm="XOR" ChecksumLength="2" IgnoreMostSignificantBit="true" />
<OutboundQueueConfigurationParameters Retries="3"
ProcessingTimeout="30000" EnableMonitor="true">
<Intervals />
</OutboundQueueConfigurationParameters>
<HostAddresses>
<Host Id="10.77.240.29" PrimaryPort="5008" RetryInternal="10" />


</HostAddresses>
<OutboundMessages>
</OutboundMessages>
<InboundMessages>
</InboundMessages>
<Transformations>
</Transformations>
<PipelineTransformationAssemblies>
<PipelineTransformationAssembly
Prefix="xfrms" Namespace="urn:schemas.mot.com:pswgs:cad:dsa:xfrms"
AssemblyName="PSWGS.Cad.Interfaces.Common" />
</PipelineTransformationAssemblies>
</DeviceConfiguration>
The <Host Id> must match the VM or PC IP address.
63
MN008865A01-AF
After completing the configuration, users are able to send a Tear and Run report that contains map related
data. You can also send a Tear and Run report for a Move Up.
3.4.5
Provisioning – Support Modern Browsers 4.6.12
(500771)
This is a beta test of a larger feature in development to allow users the flexibility to use the Provisioning portal
in all modern browsers. Currently, this update is only available for the Provisioning web portal along with the
Unit Recommendation module in Chrome and the RDW with full functionality.
When using the Chrome provisioning web portal, there may be visual differences from the Internet Explorer
provisioning web portal. These two browsers use different rendering engines which may affect how certain
parts of the browsers display.
Additionally, keyboard input may work differently between the Chrome browser and the Internet Explorer
browser.
3.5
Mobile New Functionality
reference.
PremierOne Mobile for IOS V 4.6.230807

● Implemented Compose message functionality for IOS messages with attachments
● Ability to compose message with CC/BCC recipients

● Implemented Radio ID field in log in screen
● Ability to input Radio ID during cross agency log in
3.5.1
Mobile Android – Logout Failed Dialog Box (470165)
When using mobile Android, a Logout Failed dialog box displays if you are logging out of the app and there
is no connection with the server.
The Logout Failed dialog box appears with a message that reads: Logout attempt failed. Do you
want to close the app anyway?
64
MN008865A01-AF
Figure 48: Logout Failed Dialog Box
If there is a connection to the server but the server fails to respond to the logout request, the app closes
within 60 seconds automatically.
For more information, see the PremierOne Mobile Android User Guide.
3.5.2
Optional Status Parameters (483606)
This feature was released with the Mobile iOS 4.6.11 application in June 2023.
For more information, see Features and Functionality in PremierOne Mobile iOS Application Version 4.6.11
on page 83
65
MN008865A01-AF
3.5.3
Mobile Android – Cross-Agency Radio ID Field (483614)
This feature adds the Radio ID field to the cross-agency login screen. This allows users to use a specific
Radio ID independent from one that is preassigned to them. If a user enters a Radio ID, it must exist within a
specific agency.
Figure 49: Radio ID Field
The Radio ID field is an optional field and accepts agency designators. It requires an agency for validation.
Users must enter an agency into the Radio ID field in the following format: <agency value>/<field
value> or only <field value>. For example, DC/700001 or 700001 are both valid entry formats.
66
MN008865A01-AF
Figure 50: Radio ID Field Entry Formats
If a user enters a Radio ID as <field value>, the Agency ID is automatically taken from the Agency field.
For example, DC/700001.
The Radio ID can be utilized from the primary agency, a trusted agency, or any other independent agency
depending on which agency's Radio ID is being used. Radio IDs are available to all agencies as long as they
are provisioned within an agency.
The following login scenarios are typical when using the Radio ID field:
● The Agency ID field has a primary agency and you want to use the Radio ID from that primary agency:
You can type the provisioned Radio ID in the Radio ID field.
● The Agency ID field has a unit agency and the User ID field has an Agency ID or User ID: You can
use the Radio ID from the primary agency by entering <primary agency ID> or <radio ID> in the
Radio ID field.
● The Agency ID field has a unit agency and the User ID field has an Agency ID or User ID: You can use
the Radio ID from a trusted agency and enter the trusted agency's Radio ID into the Radio ID field.
● The Agency ID field has a user agency and the Unit ID field has an Agency ID or Unit ID: You can use
the Radio ID from a trusted agency. Enter the trusted agency ID or Radio ID into the Radio ID field.
● The Agency ID field has any other independent agencies entered: You can enter the Radio ID for that
specific independent agency in the Radio ID field.
67
MN008865A01-AF
3.5.4
New Mobile Map Version (488162)
The new Universal Map Build is recommended to be used with PremierOne Versions 4.6.10, 4.6.10a, and
4.6.11.
The new Universal Map Build fixed the following issues:
● Fixed Mobile Map sometimes not displaying the basemap and unit icons.
● Fixed disappearing Drive Directions when clicking the right mouse button on the map.
Figure 51: Basemap Not Displayed
Figure 52: Unit Icons Not Displayed
68
MN008865A01-AF
Figure 53: Basemap and Unit Icon Issues Resolved and Displaying Normally
3.5.5
iOS – Barcode Scanner Library Replacement (483986)
The Barcode Scanner Library by Manatee Works is no longer supported and has been replaced by a native
Apple solution.
Users can use the new native barcode scanner in the following circumstances:
● Scanning a driver’s license for running a query as Person by Driver's License
● Scanning a driver’s license for adding a person to an incident
● Scanning a QR code with the properties file/PRData/WebMap for filling the Settings screen fields
To use the new native Apple barcode scanner for driver's licenses and QR code scanning, users should grant
the native barcode scanner access to the device camera.
69
MN008865A01-AF
Figure 54: Barcode Icon
After logging in into PremierOne Mobile for iOS, you can click on the barcode icon in the upper right corner.
If permission to use the device camera was not granted on the first launch of the application, the Camera
Access dialog box displays a message similar to To scan barcode on driver’s license, go to
device settings and enable camera access.
70
MN008865A01-AF
Figure 55: Camera Access Dialog Box
Users can perform one of the following options:

● Tap the Cancel button to close this dialog box and return to the previous screen. No changes are made
to the camera access settings.
● Tap the Settings button to open the Device System Settings screen.
From the Device Systems Settings screen, users can click the camera toggle to grant access to the
camera. After changing this setting, the app may be forced by the system to restart to implement the change
and the user may need to login in again.
After granting access to the camera, users can access the barcode scanning screen and begin scanning a
driver’s license.
71
MN008865A01-AF
Figure 56: Barcode Scanning Screen
3.5.6
Messaging Send as Unit ID Settings Group (484172)
The Messaging Send as Unit ID Settings is a settings group that allows you to manage and configure the
default display of Unit IDs instead of User IDs in the From field for all Mobile users sending messages.
NOTE: Some of these settings in the group override the Follow Me settings in messaging and default
the From field on a system-wide level.
Figure 57: Unit ID in the From Field
To access the settings group in Provisioning, you must navigate to Messaging → Agency Settings. Within
the Agency Settings window, you must select the Mobile Settings tab, then under Messaging Send as
Unit ID Settings, you can choose from the following options:
Keep User Preferred Option
Enables Mobile users to manually choose their preferred sender display setting by changing the Send as
Unit ID check box in Message Options and Mail Options dialog boxes and in the messaging form on the
Messaging screen.
NOTE: This option is a Follow Me setting.
72
MN008865A01-AF
Figure 58: Message Options Dialog Box
Figure 59: Mail Options Dialog Box and Send as Unit ID Check Box
Override Default Setting to Send as Unit ID

Enables the default display of the Unit ID as the sender for all Mobile users system-wide, but they cannot
deselect the Send as Unit ID check box in the Message Options and Mail Options dialog boxes on the
Messaging screen. The Send as Unit ID check box is also automatically selected in the messaging form.
Override Default Setting to Send as User ID
Enables the default display of the User ID as the sender for all Mobile users system-wide, but they cannot
select the Send as Unit ID check box in the Message Options and Mail Options dialog boxes on the
Messaging screen.
3.5.7
Selection of Unit Capabilities on Mobile Client (484308)
PremierOne Mobile Client users can now edit their selected unit's provisioned capabilities at login. Depending
on how the capabilities are provisioned, the users can edit the capabilities, select/deselect options, check/
73
MN008865A01-AF
clear checkboxes, and add numerical values at login. Also, provisioning personnel can choose to make
a capability uneditable. Either the Simple Login screen, the Detailed Login screen, or both can list the
capabilities for modification.
For example, an officer can choose their equipment from a list of capabilities at the start of a shift. Specifying
the capabilities of a unit at login gives an accurate and transparent view of the officer's current readiness. As
before, the mobile client user can edit the unit capabilities during the shift.
In addition to the PremierOne Mobile Client, capability-based recommendations are also updated in
PremierOne CAD.
In the following example, the PremierOne Mobile Client Simple Login screen shows the Capabilities section
that is expanded into a set of unit capabilities. The user can select and deselect their current capabilities.
NOTE: Editable capabilities at login do not include the ability to include skills.
Figure 60: Mobile Simple Login Screen with Capabilities
In the mobile client itself, the user can continue to edit the unit id capabilities in the Unit Details window with
the Edit Capability option selected.
74
MN008865A01-AF
Figure 61: Assigned Capabilities Edit Window
With this release, the mobile client user has the option to edit the unit id capabilities by using the Manage
Assignments option in the Logged in menu. Similar to changing login credentials, the Login window
displays the current Capabilities for modification.
Figure 62: Manage Assignments Form with Capabilities
The Mobile UI Customization window in PremierOne Provisioning contains Capabilities in the Simple Login
Form Options and the Detail Login Form Options. Provisioning personnel create unit capabilities as in earlier
releases, except now the mobile client user can specify and edit them before and after login.
75
MN008865A01-AF
Figure 63: Mobile UI Customization - Login Options Window
Adding Capabilities to the mobile client login requires the replacement of the PRData file.
3.5.8
iOS Message – Part 3 – Compose Messages, CC/BCC
Messages, Messages with Attachments Draft (419543)
The Compose Message feature allows PremierOne iOS Users to compose and send email messages to
other PremierOne client users.
Users can find the Compose button on both the main iOS Dashboard, the Messages Inbox screen, and the
bottom right of the Message Detail screen.
76
MN008865A01-AF
Figure 64: Dashboard Screen, Messages Inbox Screen, Messages Detail Screen with Compose Button
Highlighted
Clicking the Compose button opens the New Message screen. On the New Message screen, users can
perform the following actions:
● Add recipients of the message in the To field and/or the CC and BCC fields. The To field is limited to 4000
characters and the CC/BCC fields are limited to 3000 characters each. When entering recipients, use the
following format:
○ For a user, use the format UserID@agency
○ For a device, such as a radio, use the format Device ID@Device.agency ID
○ For a unit, use the format UnitID@Unit.agency
○ For a group, use the format Group@DGroup.agency
NOTE: If users enter more than one recipient, they must be separated by a comma.
● Add a subject to the message in the Subject field.

● Select a priority for the message from the Priority drop down list. The priority levels include Low
(default), Medium, and High.
● Type the desired message in the message text field.
77
MN008865A01-AF
Figure 65: New Message Screen and Priority Dropdown Menu Highlighted
Users can also add attachments from the New Message screen. To add an attachment, you can perform any
of the following actions:
● You can attach images by tapping the Photo Library icon. This opens the Photo Library where you can
choose the desired image file and attach it to the message.
● You can take photos or record video with the device camera by tapping the Camera icon. This opens the
device camera so you can take a photo or record a video then attach it to the message.
● You can attach a file by tapping the File icon. This opens the Files folder and allows you to attach a file to
the message. The permitted file types include .txt, .pdf, xls, .xlsm, .xlsx, .doc, .docx, images,
and videos.
After attaching each file, the user can press Done. You can view a preview of the file before attaching it by
tapping the file.
You can remove any media attachment from the message by tapping the Delete icon next to the attachment.
78
MN008865A01-AF
Figure 66: Message Attachment Icons and Delete Icon
NOTE:
Messages have an attachment size limit set by system admins. If the file attachment is too large, an
error message window similar to the following displays: The file attachment is too large.
You can tap OK on the error message window to return to the New Message screen.
To send the message, users can tap the Send button.
Figure 67: Send Button - Enabled
The message does not automatically send in the following scenarios:

● If a user tries to send a message without a recipient in the To field, the Send button is disabled.
● If a user tries to send a message without data in the body of the message, the Send button is disabled.
79
MN008865A01-AF
Figure 68: Disabled Send Message Button
● If a user tries to send a message to a recipient with an incorrect address in the To field, an error message
similar to the following displays: Please add correct recipient.
● If a user tries to send a message without a subject in the Subject field, an error message similar to
the following displays: This message has no subject. Do you want to send it anyway?
You can tap Cancel to stop sending the message and enter a subject, or you can tap Send to send the
message without a subject.
You can also cancel sending a message. To cancel sending a message, the user can tap the Cancel button
on the top left of the New Message screen.
Figure 69: Cancel Button
After tapping the Cancel button, if any fields contain data, an error message similar to the following displays:
Are you sure you want to continue? You will lose the data. Users can perform one of the
following actions:
80
MN008865A01-AF
● To abort the cancellation, the user can tap Cancel. The user returns to the New Message screen with all
previously entered data intact.
● To continue with the cancellation and to discard all entered data, the user can tap Delete. The New
Message screen closes and the user automatically returns to the previous screen.
NOTE: A Save as Draft feature will be added in a future release.
Users can also dismiss the New Message screen by dragging the screen from the top to the bottom. After
dragging the New Message screen, the user returns to the previous screen.
Figure 70: Dismissing the New Message Screen by Dragging from Top to Bottom.
For more information, see the PremierOne Mobile iOS User Guide.
3.5.9
Provisioning Audit Tool .NET and Angular Libraries
(414457)
To improve security to the CAD Provisioning Audit Tool, the .NET and Angular development tool libraries
have been upgraded to .NET 6 and Angular version 15.
81
MN008865A01-AF
3.5.10
API 33 Behavior Changes (483610)
PremierOne Mobile for Android supports Google Play target API level requirements, mandating that all
applications target at least Android 13 (API level 33).
With API 33 requirements, in PremierOne Mobile for Android 13, users can change application permissions
for displaying notification when they install the application for the first time. To successfully login, users must
grant the application permission to display notifications.
3.5.11
ArcGIS Upgrade for Android Systems (484292)
The upgrade of the ArcGIS library to 100.15.2 enables the following advantages for Android deployments:
● Reduce APK file size - ABI (Application Binary Interface) filters can reduce file size by excluding ABIs that
do not belong to the deployed APK. For example, filtering out the x86 library in a release build reduces
the size of the application by 22.7 MB.
● New support for architecture x86_64, which the current library version does not support,
● New map features and bug fixes.
3.6
Future Use Only
3.6.1
Device Type = Workstation 2.0 (495348)
A Device Type of Workstation 2.0 has been added to the Device Types and Workstation/MDT/Handheld
Provisioning pages. This Device Type is intended for future use with the new PremierOne CAD Client that
is currently under development. Please do not attempt to use or modify this Device Type within these
Provisioning pages at this time.
82
MN008865A01-AF
Chapter 4: Features and Functionality in PremierOne Mobile iOS Application Version 4.6.11
Chapter 4
Features and Functionality in

PremierOne Mobile iOS Application
Version 4.6.11
Issues Resolved
The following bug was fixed in this release:
● P1 Handheld - Incident status bar is Unresponsive (Spinning wheel) (460286)
HandHeld Mobile iOS – Optional Status Parameters (483606)

Prior to this version, even though the location, comments, and odometer information were configured to
be Optional fields, these optional fields were not recognized in iOS and there was no way to enter those
updates. With this feature, users can now enter the Optional data within the Status Parameters window and
it allows iOS to update the location, comments, and odometer information as optional criteria.
From the action bar at the top of the main Mobile screen, users can tap the current unit status to open the
Status List screen.
Figure 71: Status List Screen
On the Status List screen, the current unit status appears with a blue check mark to the left of the text. On
the right side of each status a blue arrow appears allowing you to access the optional status parameter fields.
83
MN008865A01-AF
When a user taps on a status in the Status List screen, one of the following actions occurs:
● If the user taps the Status Line and there is no required parameter provisioned in a status, the unit status
changes and the user returns to the main Mobile screen.
Figure 72: Main Mobile Screen
● If the user taps the blue arrow on a status, the Status Parameters screen appears even if none of
the parameter fields in that status are listed as (required). This allows users the freedom to add
comments and data even if it is not required by provisioning. The user can tap Submit which changes the
unit status and takes the user to the main Mobile screen.
84
MN008865A01-AF
Figure 73: Status Parameters Screen
NOTE:
The Vehicle Odometer field only accepts numeric values.
Administrators can provision optional and required fields on the Admin Console from the Unit Status Codes
screen.
Figure 74: Unit Status Codes Screen
85
MN008865A01-AF
On the Unit Status Codes screen, you can select any status code from the Status Code table and mark
any of its corresponding options as required or optional in the Options list. Checking a box makes it required,
while unchecking a box makes it optional.
These changes automatically sync with the Mobile client.
For more information, see the PremierOne Mobile iOS User Guide and the PremierOne CAD and Mobile
Provisioning Guide.
PremierOne Mobile for iOS Version 4.6.230619

Compatible with PremierOne CAD 4.4 to 4.6.11
To avoid updating to this application version, ensure that your Auto Update setting is turned OFF.
86
MN008865A01-AF
Chapter 5

4.6.11
NOTE:
5.1
● P1 CAD - 4.6.11.81 CAD Status Monitors not updating and client going offline (517114)
● P1 CAD - 4.6.10 CAD - Invalid Command Line Submission "invalid value" text now requires deletion prior
● P1 CAD - Status monitor update/Client notification delays caused by
procClientNotificationSelectCurrentCurrentJurisdictions_4611_1 (517118)
● P1CAD - CAD Client response not displaying hot hit (517886)
5.2
● P1 for Cloud CAD - Mobile - Client Connect/Disconnect Issues (322658)
● P1CAD - Cloning personnel causes incorrect Interface credentials (437371)
● P1CAD - Original CAD console gets signed off when attempt to sign on to another- concurrent sessions
not working (455998)
● P1MOB - Can´t see, edit or update Incident Notes (unable to edit closed incidents assigned to user)
(388681)
● P1CAD - App Server Restarts Caused by System.TimeoutException (458830)
● P1MOB - Default person role entry is blank not "Involved" when importing query (456486)
● P1CAD - Two-Tone Paging Not Working After P1 Upgrade to 4.6.9 (451392)
● P1CAD - iPads are getting a time out message on incident history on PremierOne Handheld v.4.6.220929
(427445)
● P1CAD - Dispatchers getting update flag from their own updates (396098)
87
MN008865A01-AF
● P1MOB - (Mapping) Mobile Map Not Following 'Display Non-GPS Equipped Units Setting' in Provisioning
(325615)
● P1CAD - R2I2 Transaction Causing Talk Group to not Announce (453755)
● P1CAD - Repeating SCOM alerts for commonservice master service failed result (305212)
● P1CAD - Previous Location Check not showing all events (443866)
● P1CAD - When entering a BOLO, received an application exception error (420670)
● P1CAD - Repeated Incident comments in RDW (454881)
● P1MOB - GeoFence Description from CAD not in MobileMap (438733)
● P1 MOB - GPS Invalid location from NMEA (437909)
● P1MOB - Mobile screens obliterated by red X and blank background (379430)
● P1MOB - Mobile unable to launch using auto-login feature/error (374496)
● P1CAD - Concurrent Login Issue-user gets auto logged off of first session (457428)
● P1CAD - Missing attachments when sending email from CAD client to outside email addresses (454194)
● P1MOB - Users unable to update closed incidents they were previously assigned to (442609)
● P1MOB - Incident Number is Cut Off in Dispatch Screen when resolution is different than standard
(440205)
● P1CAD - Two-Tone Paging working intermittently (464697)
● P1CAD - CAD Client Application Error entering BOLO (459311)
● P1CAD - RCA for 'Automatic diagnostic for instance PremierOne_04_CS had a failed result. Application
CommonServiceMasterService is stopped during diagnostic' alert. (423763)
● P1CAD - Previous events for same phone number not displaying in SWA when running IR command
(399846)
● P1CAD - Disposition comments not searchable (440232)
● P1CAD 4.6.9.104 - CADI causing services to restart frequently (Not Live Only) (467380 )
● P1CAD 4.6.9a - APCO Intellicomm Client not launching (470802)
● P1CAD - Error with BOLOStatusForm key (479451)
● P1CAD - 4.6.9.104 App Server P1 Services Restarting Every 12 Hours (437440)
● P1CAD - NCP21I103A: Local Query Connection String Length must be increased from 128 Characters
(466807)
● P1CAD - CryWolf permit processing creates SQL exception 2812 (452637)
● P1CAD - Repeated errors on workstation when entering BOLOs (471497)
● P1CAD - Concurrent Login Issue-user gets logged off when another sign on is attempted (465235)
● P1CAD - Agency MPF - updated CODE4 incident notification does not include new units only initial units
(451894)
● P1CAD - UnifiedCAD [procGetAllIncidentsByTimestampAndAgencyIdsForRecords] sproc causes
duplicate case folders due to datetime vs datetime2 rounding issues in SQL Server 2016 and later
(450057)
● P1MOB (Windows) - Importing People to Call for service (RMS) from mobile is creating error data due to
invalid Height (446872)
● P1MOB (Windows) - Users are unable to edit closed incidents the unit was previously assigned to though
provisioned to be allowed to do so (427650)
88
MN008865A01-AF
● P1MOB - Field Initiate from Mobile Classic Map does not submit incident once submit button is pressed
(387577)
● P1CAD - Exception error when creating a BOLO (475426)
● P1CAD - Multiple/Duplicate Comments on Reports (393146)
● P1MOB 4.6.10 - Mobile Scroll Bar moves/disappears once a number of comments are added to incident -
WINDOWS CLIENTS (474928)
● P1CAD - RDW Fields not populated for InputIncidentTypeAliasKey and InputIncidentTypeAliasCode
(401992)
● P1CAD - Value for CallbackServiceEndpoint_Stg in Config Tool is ignored (112589)
● P1CAD - Concurrent Logins Not Functioning - JIRA 1844 (477089)
● P1MOB (Windows) - Comment Scroll Bar Disappears (477779)
● P1CAD - CSI stopped - PCADAPP02 did not recover - SCOM spammed every minute for 24 hours until
customer started reporting queries not returning or severely delayed. (377550)
● P1CAD - SSRS Reports from CAD opens with IE instead of Edge (418968)
● P1CAD - RDW IRFs that were deleted are remaining (448602)
● P1CAD - Status Monitor showing incorrect row spacing for out of county units (CAD2CAD). (369581)
● P1CAD - CAD ignoring Callback Endpoint setting when changed in the Config Tool (473839)
● RDW - Run Cards not Updated in RDW (452788)
● P1CAD - Multiple entries are being repeated in the Comments section of a Call in RDW reports (455817)
● P1 CAD - Information Update Flag on Status Monitor shows with Own CAD Comments (386191)
● P1CAD - Interface to APCO IntelliComm won't open in IE (474542)
● P1CAD - SCOM Alert - Application CommonServiceMasterService is stopped during diagnostic.
(LocalOAMTask.exe) (283862)
● P1 CAD - Unit Preassignments failed to export of 82,000 records (463347)
● P1CAD - Inactive CAD user can still log into Provisioning (455026)
● P1CAD RDW - Since fix for (BUG 200364) The same Person or Vehicle comments are repeated
(372266)
● P1Prov - Not able to add record when using a standard Australia format phone number (460642)
● P1MOB - Summary Comment Scrollbar disappears (463481)
● P1MOB - Acknowledge alert sound is not heard again for subsequent incidents dispatched to the same
pump (463455)
● P1CAD - SCOM Querying not working/CSIMasterService diagnostic gets a failed result (424679)
● P1MOB (Windows) - Mobile users no longer able to update closed incidents (427826)
● P1CAD - Automatic diagnostic for instance PremierOne_01_CS had a failed result. Application
CommonServiceMasterService diagnostic gets a failed result causing hundreds of SCOM alerts (1 every
minute) until services manually stopped. (338223)
● P1CAD - UNIT: R57 - Incident Dispatch Info Not Sent to USDD FSA/Hiplink (388193)
● P1CAD - BPI does not update Log-in PMDC Checkbox Issue (454963)
● P1CAD - Cannot save Hot Hit keywords in lower case (472436)
● P1MOB - Mobile client does not load the edit screen (Intermittent) (478040)
● P1CAD - RapidSOS Interface - ANI/ALI data is brought to the P1 CAD Client the UI freezes for up to 40
seconds (466590)
89
MN008865A01-AF
● P1CAD - Freezing when importing 911 ALI information (RapidSOS interface) (463651)
5.3
CAD/Mobile/Admin Workstations Update
The following required update is relevant for all CAD, Mobile, and Administrative workstations. The Azure
DevOps number is included for reference.
5.3.1
ArcGIS 10.8.1 Required for CAD/Mobile/Admin
Workstations (451239)
Esri ArcGIS 10.6.1 is at the end of its Mature Software Support period and should be upgraded to ArcGIS
10.8.1.
PremierOne 4.6.11 requires ArcGIS 10.8.1 to support mapping functionality. This is applicable to ArcGIS
Server, ArcGIS Desktop for the Data Import Tools, and ArcGIS Engine Runtime for the CAD client and
Mobile client. Along with ArcGIS Server 10.8.1 the ESRI security patch ArcGIS-1081-S-Log4j-Patch must be
installed, that addresses multiple security vulnerabilities found in log4j.
For information on installing ArcGIS Engine 10.8.1, see the PremierOne CAD Client Installation User Guide
and PremierOne Mobile Windows Client Installation Guide .
5.4
reference.
90
MN008865A01-AF
5.4.1
Allow Auto Incident Association by IRF Instead of Just
Agency (437942)
In provisioning, you have multiple options to create associated incidents by Incident Response Factors (IRF)
with the Create associated incidents menu. This menu allows you to override the Automatically Create
Associated Incidents setting provisioned at the Agency level.
Figure 75: Create Associated Incidents Menu
The Create associated incidents drop-down menu has been added on the Incident Response Factors
page under the General tab with three options to create associated incidents:
Using agency level setting
Creates an associated incident by following the provisioning set on the agency level. This is the default
setting.
Automatically
Creates an associated incident automatically regardless of agency level settings.
Always prompt
Creates an associated incident after a prompt asking if you would like to create an associated incident.
The Automatically and Always prompt options override the default Agency level setting configuration.
These options allow administrators to decide for each individual IRF whether associated incidents should be
created automatically, with user confirmation, or if the given IRF should be handled according to the global
settings for an agency.
5.4.2
Add Missing Incident Person Data to the ReportingDW
Database (465483)
The MV_IncidentPerson master view within the PremierOne ReportingDW (RDW) database contains the data
on each person added to an incident. The view has been updated to include data that is captured against a
person.
91
MN008865A01-AF
Table 2: Fields Added to the MV_IncidentPerson Master View
Field Description
AniAli
CallerAddress The address associated with the ANI/ALI data of the person.
CallerApartment The apartment associated with the ANI/ALI data of the person.
CallerBuilding The building associated with the ANI/ALI data of the person.
CallerCity The city associated with the ANI/ALI data of the person.
CallerName The name associated with the ANI/ALI data of the person.
CallerPhone The telephone number associated with the ANI/ALI data of the per-
son.
CellSiteLocation The cell site associated with the ANI/ALI data of the person.
ConfFactor The confidence factor associated with the ANI/ALI data of the person.
Esn The ESN associated with the ANI/ALI data of the person.
EthnicityType The ethnicity of the person.
IsPropertySeized Has a value of 1 if property was seized from the person.
IsSearched Has a value of 1 if the person was searched.
Latitude The latitude associated with the ANI/ALI data of the person.
Longitude The longitude associated with the ANI/ALI data of the person.
MiscInfo Any miscellaneous information comments added to the person.
Name The name associated with the ANI/ALI data of the person.
ParamountPersonIndex A unique ID added to the person when using Paramount ProQA
software.
PhoneCarrier The Local Exchange Carrier associated with the ANI/ALI data.
PhoneService The Class of Service associated with the ANI/ALI data.
ProbableCause Any probable cause information added to the person.
PurposeCode The purpose code selected for the person.
PurposeCodeDescription The description provisioned against the purpose code selected for the
person.
RaceType The race of the person.
SearchType The search type that was selected for the person.
SequenceNumber A sequential number given to each person added to the incident.
StateFedEntry The entry number associated with the person.
UncertFactor The uncertainty factor associated with the ANI/ALI data of the person.
UnitID The unit associated with the person.
For more information about the RDW database views, see the PremierOne Reporting Data Warehouse
(RDW) Data Dictionary.
92
MN008865A01-AF
5.4.3
Add Missing Incident Vehicle Data to the ReportingDW
Database (442394)
The MV_IncidentVehicle master view within the PremierOne ReportingDW (RDW) database contains the
data on each vehicle added to an incident. The view has been updated to include data that is captured
against a vehicle.
Table 3: Fields Added to the MV_IncidentVehicle Master View
Field Description
Color2 The secondary color of the vehicle.
LicenseMonth The month that the registration expires for the vehicle.
Owner The primary, or only, owner of the vehicle.
ParamountVehicleIndex A unique ID added to the vehicle when using Paramount Pro-
QA software.
SecondOwner The second owner of the vehicle.
UnitID The unit associated with the vehicle.
5.4.4
Reduce the Permission for Adding Prem/Haz Records as
a Comment to an Incident to Read Only (440310)
The requirement that a role had to be provisioned with Premise Hazard (Read/Write) permission in order to
add a Premise Hazard record as a comment to an incident is removed.
A role only needs a minimum of Premise Hazard (Read Only) permission.
Figure 76: Role Permission - Premise Hazard (Read Only)
You can enable the Add as Cmt button when viewing a Premise Hazard record within the Haz tab of the
Incident Initiation and Incident Management forms.
93
MN008865A01-AF
Figure 77: Incident Management Form - Add as Cmt Button
5.4.5
Add the Field Initiate (FI) Command to the Status
Monitor Right-Click Options (451435)
The right-click menu options within the PremierOne CAD status monitors have been updated to include the
Field Initiate (FI) command at both the Agency Level and Window Level Settings.
To provision a Field Initiate right-click menu option, you can select FieldInitiateCommand within the
Command field of the Right Click Menu Options provisioning page.
Figure 78: Field Initiate in Right Click Menu Options Page
94
MN008865A01-AF
For information about provisioning right-click menu options within the status monitors, refer to the Right-Click
Menu Options for Agency Defaults and Windows Right-Click Menu Options sections of the PremierOne CAD
and Mobile Provisioning Guide.
5.4.6
Manage High Priority Incidents Using the CC and SC
Commands (435459)
The CC (User Console Control) command now includes the I;<incident id or active unit id> identifier to allow
CAD operators to add or delete a specific incident from their coverage assignment.
This allows you to:
● Have a single incident be the only one that appears within your status monitors. This makes isolating a
major incident available to a CAD operator who is responsible for only managing a major incident until it is
under control.
● Remove a major incident within your coverage area assignments from your status monitors while another
CAD operator is responsible for managing that incident. This prevents your status monitor from showing
all of the unit assignments on that major incident while it is no longer part of your area of responsibility.
The CC command can also be used to display the Login Details dialog box by submitting a CC command line
transaction without any identifier values. This provides quicker access to the Login Details than the Console
menu option.
Modifications to the CC Command

The CC command identifiers default order is:
CC.A;<agency/area(s)>.CG;<login coverage group(s)>.AC;<action {add|delete|
reset}>.I;<incident id or active unit id>
Any combination of coverage areas and/or a single incident can be included with any action, such as add,
delete, or reset.
When only adding an incident to your coverage assignment, the incident will be included within your current
status monitor coverage regardless of the area assignments that you are currently covering. If you are not
covering the area of the incident, the specified incident is added to your current coverage assignments and
displayed within your status monitor. If the specified incident happens to be assigned to an area you are
covering, you do not see any changes to your status monitor coverage.
When only deleting an incident from your coverage assignment, the specified incident is removed from your
coverage assignments and is not displayed within your status monitor, even if that incident happens to be
assigned to an area you are covering. This allows you to remove a major incident from your coverage area
assignments while another dispatcher manages that major incident.
When resetting your coverage assignment to only an incident, that incident is the only incident displayed
within your status monitors. All other coverage assignments that were being covered are removed. This
allows you to display a major incident within your status monitors so that no other incident or unit activities
interfere with you while you manage a major incident.
When performing a CC transaction with a combination of areas, coverage groups, and an incident, the areas
and coverage groups are applied based on current functionality, and the incident is processed based on the
above description of each action against an incident.
NOTE: To revert back to your normal coverage area assignments after specifying an incident with an
action of add, delete or reset, you must perform a reset action against your set of coverage areas. This
is the only way to remove any incidents that were either added or deleted from your coverage
assignments.
95
MN008865A01-AF
5.5
reference.
PremierOne Mobile for IOS V 4.6.2304.22

● Implemented Delete and Message notification functionality for IOS message
● Ability to Open/View CC/BCC messages
● Added a "Public IP address" field for public IP address under settings menu
● View Drive Directions in Google Maps Improved Send error reports experience
● Renamed Subnet IP field to Filter IP

● Implemented CrossAgency login functionality
● Renamed Subnet IP field to Filter IP
● Improved Send error reports experience
5.5.1
Windows Mobile – Mobile Server Proxy Migration
to .NET 6 (444503)
In the 4.6.11 release, the PremierOne Windows Mobile Server Proxy (MSP) has been updated to
support .NET 6. This change helps to support the latest Microsoft .NET dependencies and replaces
existing .NET Core components reaching end of life. This change helps to support Cloud customers and
On-premise customers wishing to use REST protocol rather than WCF.
Migrating to .NET 6 moves the MSP to the LTS version of .NET, is compatible and scalable for PremierOne
Mobile customers in the Cloud, and provides a high performance server run time. MSP on .NET 6 uses WCF
Core to be able to handle backward-compatible communication through WCF.
96
MN008865A01-AF
5.5.2
HandHeld Mobile iOS and Android – Rename Subnet IP
Address Field (457662 and 457665)
The PremierOne HandHeld Mobile Legacy WCF mode Connectivity setting field formerly named Subnet IP
Address was renamed to Filter IP Address.
Figure 79: PremierOne HandHeld Mobile – iOS and Android Filter IP Setting
NOTE: The behavior and use of this setting has not changed.
The PremierOne Mobile architecture allows the Client to open TCP connections to the server to make
requests, and the server also opens TCP connections back to the Client for responses. For the server to
be able to open such a connection to a particular client, it must know the Client IP address. The Mobile
Client explicitly informs the server which IP address to use by asking the OS for a list of all of the device
IP addresses, comparing them to the Filter IP Address setting, and using one that matches (if multiple
addresses match, the behavior is undefined).
For more information about the Filter IP Address setting, see the PremierOne Mobile Android and iOS
Administration Guide.
97
MN008865A01-AF
5.5.3
HandHeld Mobile iOS and Android – Send Error Reports
While Logged On (455986)
PremierOne HandHeld Mobile Android and iOS applications each include an option for users to send error
reports manually while logged on. Previously, the Send Feedback option was only available from each
application’s Login screen, and you were required to log off from the application to submit an error report.
Now, the Send Feedback option has been renamed to Send Error Report and is also available in the
logged-on state. In the PremierOne Mobile iOS application, the Send Error Report option is available from
the Settings screen. In the PremierOne Mobile Android application, the Send error report option is available
from the Logs screen.
NOTE: Submitting an error report does not automatically create a ticket with the Support organization.
Please follow up with Support to report any issues with PremierOne HandHeld Mobile for iOS or
Android.
Figure 80: PremierOne HandHeld Mobile – iOS and Android Send Error Report Option
For more information about sending error reports manually from PremierOne Mobile iOS, see the
PremierOne Mobile iOS User Guide. For more information about sending error reports manually from
PremierOne Mobile Android, see the PremierOne Mobile Android User Guide.
98
MN008865A01-AF
5.5.4
HandHeld Mobile iOS – Public IP Address Setting Added
(449157)
The Public IP Address setting was added to PremierOne Mobile iOS.
Customers who use Network Address Translation (NAT) often operate behind multiple firewalls where their
IP address changes regularly. Because the IP address changes regularly, the client is not reachable from
the server and is not able to receive responses, which prevents the PremierOne Mobile iOS application from
working at all. Customers who use NAT must fill in the Public IP Address field in order to connect to the
server. The Filter IP Address is overwritten with the Public IP Address.
If you do not use NAT, you should leave this field blank and use the Filter IP Address setting instead.
Figure 81: Mobile iOS Public IP Setting
For more information about Connectivity settings, see the PremierOne Mobile Android and iOS
Administration Guide.
5.5.5
HandHeld Mobile iOS – Message Improvements (449153)
PremierOne Mobile iOS Messages provides the ability to receive and view incoming messages that are
traditional email-type messages. In version 4.6.11, iOS Messages includes the ability to receive message
notifications, swipe left to delete messages, multi-select and delete messages, and open and view messages
including CC and BCC recipients.
99
MN008865A01-AF
Figure 82: PremierOne Mobile iOS – New Messages Functionality in Version 4.6.11
100
MN008865A01-AF
Figure 83: PremierOne Mobile iOS – Message Notifications
NOTE: Additional functionality for Mobile iOS Messages will be added in future releases, including
Address Book functionality and the ability to compose and reply to messages. Messaging is already
available in the PremierOne HandHeld Android and PremierOne Mobile Windows Clients.
5.5.6
HandHeld Mobile iOS – Google Maps Navigation
Provider Support (444569)
You can configure PremierOne Mobile iOS to use Google Maps for navigation. If you select Google in the
Settings screen Navigation setting, Google Maps displays when you request drive directions in PremierOne
Mobile iOS.
Figure 84: PremierOne Mobile iOS – Navigation Setting
101
MN008865A01-AF
Figure 85: Google Maps Application Navigation Screen
If the Google Maps application is not installed on your device, you can view turn-by-turn text-based drive
directions from the web version of the application in your default web browser.
102
MN008865A01-AF
Figure 86: Google Maps Web Browser Navigation Screen
For more information about requesting drive directions, see the PremierOne Mobile iOS User Guide.
5.5.7
HandHeld Mobile Android – Cross-Agency Login
(421195)
The Mobile Cross-Agency Login feature enables users to sign into multiple agencies by specifying one or
more of the following login IDs:
● User ID
● Unit ID
● Vehicle ID
By doing so, users have access to resources across multiple independent agencies. Cross-agency login
allows users to specify an agency and its resource with the format AgencyId/ValueId, in which they can
deploy personnel, units, and vehicles in the PremierOne Mobile login screen.
103
MN008865A01-AF
Cross-agency login requires a primary agency and a secondary (or trusted) agency. They have the following
properties:
● Primary agency – The agency that you sign in with your User ID becomes the primary agency. The User
ID also determines
○ The roles that you can choose to log in with.
○ The permissions granted to the trusted agency by the chosen role.
NOTE: Primary agency commands take priority over trusted agency permissions. Permissions that
are granted to the trusted agency must also be granted to the primary agency, otherwise the trusted
commands do not work.
● Trusted agency – With the AgencyId prefix, a primary agency has access to the trusted agency's
resources:
○ The specified AgencyId prefix with the Unit ID provides access to jurisdictions Area, Sector, and
Beat.
○ The specified AgencyId prefix with the Vehicle ID provides access to the trusted agency's vehicles.
The cross-agency resources that users deploy depend on the explicit use of the AgencyId. Without
AgencyId, PremierOne Mobile retrieves the resource values from the default agency that is identified in
the Agency field.
The following table summarizes the rules for specifying the AgencyID for the User ID, Unit ID, and the
Vehicle ID:
Table 4: Cross-Agency Login Rules
Login ID No Agency Specified on ID Agency Specified on ID

User ID Default Agency sets Role value. Sets Role value.
Unit ID Default Agency sets the jurisdictions' Sets jurisdictions' Area, Sector, and
Area, Sector, and Beat values. Beat values.
Vehicle ID Default Agency sets Vehicle ID val- Sets Vehicle ID values.
ues. NOTE: The Vehicle ID can be
specified for any agency, not
necessarily the primary or a
trusted agency.
NOTE: If the Unit ID field is empty, the retrieved jurisdiction values are based on the user's agency: that
is, the agency that is explicitly defined in the User ID field or appears in the default Agency field.
The following login scenarios are typical when a user wants to use resources from other agencies.
● User logs in with agency-specified Unit ID – Without the Agency ID prefix specified with the User ID, the
primary agency is DC, as defined by the Agency field. The role is derived from the user agency DC. The
unit is taken from a trusted agency KCAC, which is specified by the Agency ID prefix. The jurisdiction
(Area, Beat, Sector) are derived from the unit's agency KCAC. In the example on the left, the vehicle ID is
specified for the agency DC. The Vehicle ID can be specified from any agency.
104
MN008865A01-AF
Figure 87: Cross-Agency Login with Unit ID
● User logs in with agency-specified User ID. – The user logs in DC/TESTCROSSAGENCY, where DC
becomes the primary agency. The role is derived from the user agency DC. The unit is taken from a
trusted agency KCAC, as defined in the Agency field. The jurisdiction (Area, Beat, Sector) are derived
from the unit's agency KCAC. In the example on the left, the vehicle ID is specified for the agency DC.
Figure 88: Cross-Agency Login with User ID
105
MN008865A01-AF
Cross-agency logins determine how fields are populated in other elements of the PremierOne Android Mobile
system, such as query features, field-initiated incidents, the creation of traffic stops, status monitor use,
viewing assigned incidents, viewing pending incidents, and viewing unit status monitors.
NOTE: Radio ID, mapping, messaging and address book functionality will be added in future releases.
106
MN008865A01-AF
Chapter 6

4.6.10
NOTE:
6.1
● P1 PROV - Not able to add record when using a standard Australia format phone number (476138)
● P1 CAD - Unit Preassignments failed to export of 82,000 records (476142)
● P1CAD - When entering a BOLO, received an application exception error (476135)
● P1CAD - Concurrent Login Issue: User gets auto logged off of first session (476147)
● 4.6.9a P1CAD - APCO Intellicomm Client not launching (476494)
● P1MOB (Windows) - Importing People to Call for service (RMS) from mobile is creating error data due to
invalid height (476501)
● P1CAD - Agency MPF: Updated CODE4 incident notification does not include new units only initial units
(476137)
● P1MOB - Acknowledge alert sound is not heard again for subsequent incidents dispatched to the same
pump (476143)
● P1MOB - Summary Comment Scrollbar disappears (476146)
● P1MOB - Mobile Map intermittently does not show the route to the incident upon dispatch after upgrading
to the released version of Mobile Client and Mobile Map (477130)
6.2
● P1CAD - Clearing the Primary Unit in Call Stack (281338)
● P1CAD - Coverage groups are not as provisioned following upgrade (281444)
● P1CAD - SCOM Mobile Server Certificate Expired Alert Resolution received with unsolicited query
response information (288291)
● P1CAD - SCOM alert should not include CJIS information - Mobile Server Certificate Expired (288295)
107
MN008865A01-AF
● P1CAD - Search in the person tab on the map did not return results (297225)
● P1MOB (Windows) - Cross Streets Missing when starting with Street Alias and selecting Common Place
during verification process (319251)
● P1 CAD - SCOM Alert - PremierOne Mobile Server Certificate Expired Alert (331507)
● P1 CAD - Pending screen no longer shows changes to pending incidents. (333285)
● P1MOB - On TSTOP Summary tab in P1 Mobile Inc Number is cutoff (333729)
● P1MOB - Recipient Address is not Populated in the "To" field on New Message Screen from Search
Resource Results (334362)
● P1CAD - During ARL history playback, the gps trail does not do anything (342828)
● P1CAD - ARL Replay does not display results on the map when unit data has 0's mixed in for lat/lon
(344873)
● P1CAD - Map zoomed out to 1:9999979 and turns white after searching for a vehicle (348965)
● P1CAD - Common Place gives different results when updating from form vs command line (351030)
● P1CAD - CSR receiving HTTP 500 381168 [PBFL] P1CAD: MonitorServersDisk.ps1 is not locating all
PremierOne server drives for SCOM Monitoring (378353)
● P1CAD - 4.6.5.70 Cross-staffing / minimum staffing not clearing units as expected consistently (386031)
● P1CAD - Inconsistent behavior producing/displaying Update/Priority Update (387972)
● P1CAD - Workstations randomly get logged off - "You have been logged out by system" and then the
client closes (391798)
● P1CAD - SCOM ALERT - PremierOne Motorola.PremierOne.ServiceHost PrivateBytes Monitor (405726)
● P1PROV - Error when attempting to Add an In-Station Record: Failed to add or update (406334)
● P1MOB - Equipment display in Unit Status Monitors on Mobile client is inconsistent if officer name or
equipment name shows first. (409846)
● P1CAD - CryWolf alarm creation status not respecting IRF Disposition setting (410499)
● P1CAD - AD Authentication is not documented properly for enabling LDAPS. (411397)
● P1CAD - F1 after unit In Dispatch Tab doesn't go to command line but goes to capability (411817)
● P1CAD - Unable to load purge settings within provisioning console (413969)
● P1CAD - Addresses do not verify when tabbing through IU screen until second attempt (414370)
● P1CAD - Addresses still showing on Re-Validation Report after being deleted out of provisioning (418208)
● P1CAD - Custom Pack - UIC Assembly creation fails for IMDispatchScreen (418268)
● P1CAD - MM/11205 - why E99 was recommended (427171)
● P1CAD - Update request for procClientNotificationSelectCurrentIncidentHistory_320_1 (427424)
● P1CAD - Hyperlink error from drill down query in Incident > Query Tab in WAA (428086)
● P1CAD - Unable to Install 4.6.9 when the default instance is something other than Instance_01 (428715)
● P1CAD - Importing Jurisdictions to Provisioning does not populate ResponseClass when "TH" (429478)
● P1MOB - Handhelds unit status next to unit name in Units screen doesn't update when status is changed.
(429683)
● P1CAD - Unexpected Error in CAD related to Modifying Circumstances field (430638)
● P1CAD On Prem - crashes after update to 4.6.9 (Master clone of 428374) (432020)
● P1CAD - Client Incident Status Screens Went Blank (Multi-client database Only) (Master clone of
401505) (432023)
108
MN008865A01-AF
● P1 CAD - Priority Flags and Update flags show inconsistent behavior when log off and on and transferring
sessions (437269)
● P1CAD - Orphan query received time doesn't show military time and sorts numerically (437410)
● P1CAD - Intermittent pre/post delivery expiration message with unread expiration time set in provisioning
(440956)
● P1MOB - Driver License Scans (PDF417) does not populate all available fields (382720)
● P1MOB - Cannot use location services with AVL Can only use COM port and NMEA (434933)
● P1 CAD - CAD2CAD Call for Service expecting additional parameters (429317)
6.2.1
Personnel Provisioning - Personnel Search Form
Incorrectly Defaults to Sound Alike = Checked (423091)
In PremierOne Provisioning → Resources → Personnel when searching for an existing record the Sound
Alike check box is now defaulted to unchecked.
Figure 89: Sound Alike Check Box Defaulted to Unchecked
109
MN008865A01-AF
6.2.2
Updating Location from Command Line - Update the
Common Place for New Location (351030)
When updating an incident location from the Command Line, the Common Place for the new location now
updates. Previously, updating from the Command Line would cause the old Common Place name to remain
with the new location information.
Figure 90: incident with Location and Common Place Information
Figure 91: Update with Common Place Location on Command Line
110
MN008865A01-AF
Figure 92: Updated Location and Common Place Display in the Incident Update Form
6.3
reference.
PremierOne Supports Windows 11 PremierOne

CAD now supports the use of Windows 11 operating system. Microsoft Windows 11 Professional (64-bit
recommended) is recommended. Windows 10 Professional (64 - bit recommended) is supported as well.
6.3.1
Using Unit GPS Location for ID Command (400218)
CAD users can use the Automatic Resource Location (ARL) identifier from the Command Line to dispatch a
support unit to an incident assigned to a different unit.
CAD uses the GPS of the assigned Unit rather than the incident location of that assigned Unit to dispatch a
back-up unit. The GPS location can be used even if the assigned unit is moving. The back-up unit receives
driving directions to the GPS location of the assigned unit.
The ARL identifier automatically appears in the Command Line if Dynamic Help is turned on.
111
MN008865A01-AF
Figure 93: ARL Identifier in Command Line
To find the ARL identifier in provisioning, navigate to Command Line → Commands → View/Modify. The
ARL identifier has only Yes or No values.
Figure 94: ARL Identifier in Provisioning
The ARL identifier also appears in the Command Line → Identifier screen.
112
MN008865A01-AF
6.3.2
Contractor Beat Added to the RDW Data Dictionary
(403514)
Contractor Beats (also known as Contractor Boundaries) are Geographic Information System (GIS) features
represented geometrically by polygons. These features represent the geographic areas used to define
Contractor Rotations. Each Contractor Boundary is specific to a single agency.
NOTE: Motorola recommends that all Contractor Boundaries for a particular contractor type (such as
Tow, Taxi, Board Up, and so on) be maintained in a single GIS data source per agency type. Using
Contractor Boundaries is optional.
If your agency uses Contractor Boundaries, when a contractor (such as a towing or taxi company) is
requested to support an incident, the Contractor Beat information from the PremierOne CAD Client
or the PremierOne Mobile Client Contractor Request form is stored in the GeoBoundaryCode field
in the UnifiedCAD database CR_ContractorRotationRequest table and then is transferred to the
RST_CR_ContractorRotationRequest table in the Reporting Data Warehouse (RDW) database.
You can view the GeoBoundaryCode data in the RDW RS_CR_ContractorRotationRequest view. For
more information about the RDW database views, see the PremierOne Reporting Data Warehouse (RDW)
Data Dictionary.
6.3.3
Add Radio ID identifier to ON Command line (400217)
A new identifier has been added for the On Duty (ON) command which accepts multiples values with and
without agency prefixes.
NOTE: For more information on identifiers, see PremierOne CAD Commands Quick Reference.
The identifier for Radio ID is RID and is available for the ON command on the command line.
Figure 95: Radio ID Identifier - RID
The RID identifier can also accept multiple values with and without agency prefixes. It overrides preassigned
radios if any exist.
Radios without an agency ID prefix default to the working agency of the CAD User. All radio IDs must be
provisioned as a radio within PremierOne. If the radio ID is not provisioned the CAD User receives an error
message and the radio ID is not submitted.
113
MN008865A01-AF
Figure 96: Radio Identifier - RID with Multiple Values
Additionally, the RID identifier can override radio units that are preassigned in provisioning.
6.3.4
Notification of Unit Being Dispatched Outside of
Jurisdiction (412752)
An agency now has the option of notifying individuals through email, pagers or an MDT whenever a unit from
the agency is dispatched onto an incident outside of the jurisdiction of that agency. For fire agencies, this is
helpful in informing supervisors whenever one of their units is dispatched onto a mutual-aid or auto-aid event.
Figure 97: Out-of-Agency Dispatch Notification Recipient Types
The notification can be provisioned to be sent to:

● An email address – Either an internal PremierOne email address or an email address that is external to
PremierOne.
The subject of the email is: {AgencyID/Unit ID} was dispatched onto {AgencyID/Incident
Number}
The body of the email contains the same Incident Details as an Automated Incident Notification.
NOTE: Emails sent to internal email addresses take the form of a Notification.
● A physical pager – The pager text contains the following text:

{AgencyID/Unit ID} was dispatched onto {AgencyID/Incident Number}
● Pagers associated with a Pager Group – All pagers within a specified Pager Group are handled as
described under notifying a physical pager.
114
MN008865A01-AF
● An MDT assigned to a unit plus the pagers and email addresses provisioned as equipment against the
unit, vehicle or personnel assigned to the unit. The notification sent to the MDT of the unit is sent in the
same format as an email notification.
All email addresses and pagers assigned to as devices to either the unit, its personnel, or its vehicle are
also notified.
6.3.5
On-Demand Vicinity Checks (412848)
Whenever the location of the incident is verified within the Incident Initiation or Incident Management form,
the Verify button associated with the location of the incident is changed to a Vcnty button, allowing you to
manually check for Potential Duplicates against that location while the incident is displayed within the form:
Figure 98: Vcnty Button
Pressing the Vcnty button runs the same potential duplicate process that is performed during address
verification against the verified location of the incident.
● If any potential duplicates are returned, they display within the Potential Duplicates window in the Work
Assist Area.
Figure 99: CAD to CAD - Potential Duplicates Window
● If no potential duplicates are returned, the following status message displays: No Potential
Duplicates were found
Whenever the location of the incident is, or becomes, unverified, the Vcnty button is changed back to Verify.
NOTE:
The keyboard shortcut ALT+V can be used to perform either the address verification or vicinity check
function, depending on which function is currently active for the button.
6.3.6
Allow Call for Service Updates for Local Agencies to
update Associated Incidents (423048)
A local agency can now be provisioned to apply inbound Call for Service Update messages to all incidents
associated with the local incident receiving the update.
A check box for Apply updates (as a comment) to all associated incidents was added within the
Detailed Call for Service Transfer section of the Interface → External System → Local Agency Settings
provisioning page:
115
MN008865A01-AF
Figure 100: Apply updates (as a comment to all associated incidents Button
Checking this box allows incidents associated with the incident of a local agency receiving a Call for Service
Update to also be updated by the comment generated for the Call for Service Update.
6.3.7
Performing Potential Duplicate Check Against CAD-to-
CAD Call for Service Requests (412831)
In order to provide better situational awareness for inbound Call for Service Requests from external systems,
PremierOne performs a potential duplicate check against the request prior to creating the incident.
If any duplicates are returned, a comment is added to the incident identifying the potential duplicates.
Figure 101: Potential Duplicates Comment
116
MN008865A01-AF
The potential duplicate comment identifies the Call for Service Request location used for the potential
duplicate check. In Figure 101: Potential Duplicates Comment on page 116, 710 MAIN ST, EAST is the
Call for Service Request location. The potential duplicate comment also identifies the following information:
● Incident Number (Incident Status)
● Location, City
● Incident Type
● Modifying Circumstance
If there are many potential duplicates in the vicinity of the Call for Service Request, only the top three
duplicates that would have been displayed within the Incident Initiation form for the respective location are
returned.
When viewing the incident within the Incident Management form, the user can perform an On-Demand
Vicinity Check against the incident as described in On-Demand Vicinity Checks (412848) on page 115.
6.4
reference.
PremierOne Supports Windows 11

PremierOne Mobile Windows now supports the use of Windows 11 operating system. Microsoft Windows 11
Professional (64-bit recommended) is recommended. Windows 10 Professional (64 - bit recommended) is
supported as well.
PremierOne Mobile for IOS V4.6.2.30.111

● Compatible with PremierOne CAD 4.3.0 to 4.6.10
● Unit status changes dynamically with status change in Unit screen
● Created IOS Message functionality to View/Read message and Open attachments
PremierOne Mobile for Android V4.6.2212.03

● Compatible with PremierOne CAD 4.3.0 to 4.6.10
● Compatible with Android 12 (API 31)
● Permission flow improvements
6.4.1
Windows Mobile Client Launches Before Mobile Map
(418824)
Previously, the Mobile Map loaded in front of the Mobile CAD Client upon login, blocking visibility of the
Mobile Client and requiring an extra step to bring the Mobile Client into view. This feature changes that
behavior, displaying the Mobile Client in the foreground and the Mobile Map in the background after the
Mobile Map loads completely. The Mobile Map displays in the background upon successful login, after the
Switch to New User button is used, and when an active session is locked and unlocked.
The PremierOne Mobile Client behavior is unchanged other than displaying in the foreground when launched
together with the Mobile Map. The Mobile Map behavior is unchanged other than staying in the background
when launched together with the PremierOne Mobile Client.
117
MN008865A01-AF
6.4.2
HandHeld Mobile – iOS Messages (419535)
PremierOne Mobile iOS Messages provides the ability to receive and view incoming messages that are
traditional email-type messages. Mobile iOS users can view message summaries in the Messages screen,
open each message to view the detailed content, and download and open message attachments.
Figure 102: PremierOne Mobile iOS Messages
The unread message count appears on the Dashboard. A red flag icon displays next to the unread message
count on the Dashboard to indicate a high-priority unread message. A list of your messages appears in the
Messages screen. The sender, the subject, and the date the message was received display. If the message
is designated as High priority, the envelope icon appears in red. If the message is a Medium priority, the
envelope icon appears in orange. If the message is a Low priority, the envelope icon appears in gray. Unread
messages display a closed envelope icon. Read messages display an opened envelope icon.
If a message has an attachment, a paper clip icon appears next to the time received. When you open a
message that includes an attachment, you can download all the attachments to open and view them.
NOTE: Additional functionality for Mobile iOS Messages will be added in future releases, including the
ability to compose and reply to messages, add CC or BCC recipients, delete messages, receive
message notifications, and more. Messaging is already available in the PremierOne HandHeld Android
and PremierOne Mobile Windows Clients.
118
MN008865A01-AF
6.4.3
HandHeld – Meet Google Play Target API Level 31
Requirement (384552)
In version 4.6.10, PremierOne Mobile Android includes behavior changes to support the Android 12 operating
system and Android API level 31.
The new platform includes enhanced security, including updated in-app disclosures describing how
PremierOne Mobile Android uses background and device location information.
NOTE: The wording of the disclosures was updated to clarify the process for collecting and using this
information. The process has not changed.
The updated disclosures read as follows:
Figure 103: Updated Background Location Disclosures
For more information about the Android permissions dialogs, see the PremierOne Mobile Android and
iOS Administration Guide. For more information about allowing background location permissions, see the
PremierOne Mobile Android User Guide.
119
MN008865A01-AF
Chapter 7

4.6.9
NOTE:
7.1
● P1CAD - Client Incident Status Screens Went Blank (Multi-client database Only) (401505)
● P1CAD On Prem - crashes after update to 4.6.9 (428374)
● P1CAD - Unable to Install 4.6.9 when the default instance is something other than Instance_01 (432022)
7.2
● P1Mobile – Concurrent Login error on Mobile with previously orphaned sessions on that device (160197)
● P1CAD – Address Verification Issues for addresses containing buildings when
“GeocodeByNonExactAddressPointEnabled” is set to True, validating to centerline instead of address
point (179021)
● P1 CAD – Add AL to Locution API (179562)
● P1CAD – Multiple PageGate messages causing paging not to come through (298199)
● P1MO – Incident status monitor not updating (322109)
● P1CAD – Emergency Notification Audible Tone not playing provisioned alert sound (329833)
● P1CAD – Users unable to double click to select incident from pending – Remove ability to remove system
commands (337597)
● P1CAD – Double click on incident column not working because IU command got deleted – Remove ability
to remove system commands (341697)
● P1MOB – Delayed updates on mapping and road closures (Incorrect location and incident type on Map)
(341860)
● P1CAD – ARLDatabaseAccessManager construction failed error in logs (350677)
● P1 Cloud CAD – VIN number was queried and the response would not come back – warning when the
call back port isn't available (352923)
120
MN008865A01-AF
● P1MOB – Auto query from License not working because LSM duplicate long name gender codes
(364523)
● P1 CAD – Reporting District Not Populating on Some Calls (365203)
● P1MOB – Common field for middle name doesn't exist for use with DL scanners (369211)
● P1MOB – Barcode drivers license query scan error 201,required fields (369225)
● P1CAD – Fire Dispatch – USDD Alerting System Did Not Activate (375032)
● P1MOB – "An error occurred storing the incident information" upon update (376641)
● P1MOB – Messaging Address Book (Contacts) Scroll Bar does not work when first record at top is
selected (380891)
● PMDC – error when running unit activity report (381664)
● P1MOB – Driver License Scans (PDF417) does not populate all available fields (382720)
● P1CAD – offline mode (Incident tool) unable to save or update areas on certain incidents if XML has been
saved (383497)
● MOB – 4.6.5 Mobile crashes due to out of memory error without univeral map installation (Master clone of
329847) (385812)
● P1CAD – 4.6.5.70 Deployment Site Connection Timestamp Issue (386022)
● P1CAD – CAD Slowness on 6/30 and 7/10 – procGetIncidentUnitsHistory locked (387181)
● P1CAD – User gets failed to add unit on II form. – Error message should say "Another user updated this
unit" (387616)
● P1CAD – DISP5 received error "Unexpected Error: Object reference not set to an instance of an object"
when bringing up an incident for dispatch (388988)
● [P1CAD] – GPS Invalid data leading to excessive exception logging (389839)
● P1CAD – 4.6.5.70 – CAD Users receiving message pop-up from Detective Adams (we do not have a Det.
Adams) (390682)
● Provisioning Purge setting does not reflect purge of associated response data (390718)
● P1MOB – Mobile Unit and Incident Status Monitors Not Updating (390864)
● P1 Deployment Tool – AIO Deployment Fails to Update ParameterBackUp.xml with GPSDevice
Parameter Group (390942)
● P1MOB – When generating an incident, or self dispatching, the Incident screen does not indicate which
unit is the primary unit (391347)
● P1CAD – Address book search not finding users by alias (391828)
● P1CAD – Object reference not set to an instance of an object (Cross threading issue investigation)
(392368)
● P1CAD – Mail notifications based on unit equipment fails (395101)
● P1MOB – GPS Status Indicator Clarification of Network vs Satelite issue (400465)
● Incident Prune not working due to scheduled incidents (400968)
● P1CAD – Missing "Run Query (Barcode Registration)" from Peripherials > Mag Stripe / Barcode Reader
(409909)
● P1MOB – GPS is problematic when WLS returns NaN for coordinate accuracy (411395)
● P1CAD – Preferred ARL recommendation issues with capabilities - recommended a TRK outside of
agency BGF (404064)
● P1CAD – CADtoCAD change to temporarily store Address & Incident Type for comparison & Comments
(395507)
121
MN008865A01-AF
● P1CAD – CADtoCAD need the vendor's 'Incident incidentRefId' to be included in the ESResponse msg
for use in outbound transactions (395480)
● P1CAD – CADtoCAD interface needs the ability to retrieve the ExternalIncidentId (376955)
7.3
reference.
7.3.1
Automatic Dispatch Upon Incident Initiation (355161)
The Automatic Dispatch functionality allows the system to recommend and automatically dispatch units onto
specific incidents that are being initiated without the involvement of a dispatch action. When initiating an
incident for an Incident Response Factor (IRF) that is provisioned to enable automatic dispatch upon incident
initiation, the system will perform unit recommendations against all Recommendable and Available units that
qualify for the IRF's respective Response Card and dispatch the recommended units onto the incident. Unit
that are Recommendable but not in an Available status will be ignored as part of the automatic dispatch
process.
The incident's resulting status when performing an automatic dispatch is dependent on the outcome of the
unit recommendation. A corresponding Auto Dispatch comment is also written to the incident:
If the result of the Unit Recom- The Incident's Status will be With the following comment
mendation was... set to... written to the incident
Undefined: A Response Card The respective agency's Initial AUTO DISPATCH: RECOM-
was not provisioned for the IRF Status (Pending or Initial) MENDATIONS NOT PROVI-
SIONED.
Empty: No Recommendable The respective agency's Initial AUTO DISPATCH: NO RECOM-
and Available units could be rec- Status (Pending or Initial) MENDATIONS FOUND.
ommended for the incident MISSING: {List of Missing Capa-
bilities}
Incomplete: Only a partial set of Active <AUTO DISPATCH INCOM-

the required units were dispatch- PLETE.>
ed onto the incident AUTO DISPATCH: PREFER-
RED REC: {List of Dispatched
Units}MISSING: {List of Missing
Capabilities}
Complete: All required units Active AUTO DISPATCH: PREFER-
were dispatched onto the inci- RED REC: {List of Dispatched
dent Units}MISSING: (NONE)
The sets of Dispatched Units and Missing Units includes the same information that is displayed in the Unit
Recommendations form under Dispatch Units and Missing Caps respectively.
When an automatic dispatch returns an incomplete set of recommended units, the units that were
recommended will be dispatched onto the incident and a Priority Comment will be written to the incident,
immediately informing the appropriate CAD operators of the incomplete dispatch.
122
MN008865A01-AF
If ARL Recommendations was not used in the recommendation, the PREFERRED REC label within the Auto
Dispatch comment will be replaced with FIXED REC.
Automatic dispatch will be performed against associated incidents during the incident initiation process, if the
associated incident's IRF is provisioned for automatic dispatch.
If the incident's location was provisioned with a Secondary Response Location, units will also be
recommended, dispatched and designated for the Secondary Response Location as part of the automatic
dispatch.
To enable Automatic Dispatch, an agency must:
● Enable Automatic Dispatch for their Agency level
● Enable Automatic Dispatch against specific Incident Response Factors (IRFs) at either the Agency Type
or Agency level.
NOTE: The Enable Automatic Dispatch setting at the Agency level allows an agency to completely
enable or disable automatic dispatch for the agency without impacting the individual IRF settings.
Figure 104: Agency Level Automatic Dispatch Activation Checkbox
Figure 105: Incident Response Factors (Agency Type Level): Automatically Dispatch on Incident
Initiation
123
MN008865A01-AF
Figure 106: Incident Response Factors (Agency Level): Automatically Dispatch on Incident Initiation
7.3.2
Notification of Unit Being Dispatched Outside of
Jurisdiction (367823)
An agency now has the option of notifying specific units whenever a unit from this agency is dispatched
onto an incident outside of the agency's jurisdiction. For fire agencies, this is helpful in informing supervisors
whenever one of their units is dispatched onto a mutual-aid or auto-aid event. The notification is received
by the unit's MDT in the form of an email in the same manner as it would receive an automated incident
notification if provisioned.
The Out-of-Jurisdiction notification will be delivered to the recipient unit's mobile client as well as any email
addresses that are provisioned as Equipment Type = Email for either the personnel assigned to the unit
or directly against the unit.
For example, agency FD can provision BC110 to be notified whenever E101 is dispatched onto a mutual-aid
or auto-aid event.
Out-of-Jurisdiction notifications are provisioned within the Notifications tab under Unit Preassignments:
Figure 107: Unit Preassignments Window
1. You can select the unit you would like to have inform others whenever it is assigned to an incident
outside of its agency's jurisdiction. Within the Notification tab, select the Enable out-of-agency dispatch
notifications to the following recipients check box and enter the unit(s) you wish to notify.
2. Within the Notification tab, you can select the Enable out-of-agency dispatch notifications to the
following recipients check box and enter the unit(s) you wish to notify.
NOTE: Although a drop-down, the Recipient Type field only contains Unit as an option in Release
4.6.9. Email, Pager and Pager Groups will be added as options within the Recipient Type field in
Release 4.6.10.
124
MN008865A01-AF
The Out-of-Jurisdiction notification includes the following information:

● Subject: Out-of-Jurisdiction Incident Assignment Notification
● Comment: {Agency ID/Unit ID} was dispatched onto an Out-of-Jurisdiction Incident
● Incident Details: Provides the same Incident Details information that is contained within the automated
incident notification sent at the time of initial dispatch
Subject: Out-of-Jurisdiction Incident Assignment Notification
Notification:
---------------------------------------------
Notification Comment Entities:

---------------------------------------------
Comment: DISPATCHER17 09/07/2022 11:56:54

Comment: DC/DISPATCHER17 9/7/2022 11:56:54 AM
FD/E101 was dispatched onto an Out-of-Jurisdiction Incident
---------------------------------------------------
INCIDENT DETAILS
LOCATION:
Location: 123 MAIN ST
Loc Name:
Loc Descr:
City: ANYTOWN
Building:
Subdivision:
Floor:
Apt/Unit:
Zip Code: 12345
Cross Strs: FIRST AVE / SECOND AVE
Area: AR4
Sector: SC2A
Beat: DCS2
Map Book: ANYCOUNTY, 1, B4
---------------------------------------------------
INCIDENT:
Inc #: \\\BF2022-007
Inc #: \\\BF2022-007
Priority: 1
Inc Type: ABPAI
Descr: ABDOMINAL PAIN
Mod Circum:
Created: 12:00:00 PM 1/1/2022
Caller:
Phone:
---------------------------------------------------
UNITS DISPATCHED:
FD/E101
---------------------------------------------------
PERSONNEL DISPATCHED:
---------------------------------------------------
COMMENTS:
---------------------------------------------------
PREMISE HAZARD:
125
MN008865A01-AF
7.3.3
Unit GPS Location Used for the FI Command (378509)
CAD users can use the GPS location of a unit to create an incident by using the FI command instead of
manually entering the location. This feature only affects the Command Line and must be provisioned by an
administrator.
The GPS location of the unit can be used even if the unit is moving. The unit dispatched to the location
receives driving directions to that GPS location.
The identifier ARL is used to capture the GPS location of the unit. For example: FI.U;NUNIT3.ARL;Y
Figure 108: ARL Identifier Used for Unit Location
The user can provide more than one unit with the ARL identifier set to Yes (Y). In that situation, CAD retrieves
the GPS location of the first unit only. If the GPS of first unit results in an error, the CAD Client will provide
error message and open the form. CAD will not try to retrieve the GPS location of the other units provided.
The FI command used with the ARL identifier is affected by the following variables:
● The FI command does not require the Location (<L>) variable if the user enters the ARL identifier set to
Yes (<Y>).
● If the default value of the ARL identifier is set to Yes (<Y>) then the FI command can be executed using
only one parameter. For example FI.U;<UnitName>
● If the user enters the Location (<L>) variable and the ARL identifier set to Yes (<Y>), then the GPS
Location Unit feature is ignored. The FI command uses the provided location instead of the GPS location.
For example FI.U;UnitName.L;ProvidedLocation.ARL;Y
7.3.4
Standard Operating Procedures (379619)
The 4.6.9 update for Standard Operating Procedures allows new information to be added to the incident
history informing users about the SOP availability for a given IRF when creating an incident. This is a new
record, separate from the Incident Creation record.
All SOP-related actions that are visible in the incident history will also be visible in the RDW reports.
SOP Availability is recorded in the Incident History screen in the following circumstances:
● A new incident is created using an IRF with a SOP.
126
MN008865A01-AF
Figure 109: New Incident - IRF with SOP
● There is a change in the IRF of an existing incident and there is a SOP for the new IRF.
Figure 110: Existing Incident - Changed IRF with SOP
All SOP-related transaction data actions that are visible in the incident history will also be visible in the RDW
reports. The SOP fields available in the RDW include:
● [IncidentKey]
● [IncidentRecordSerialNo]
● [IncidentNumber]
● [AgencyId]
● [TransactionKey]
● [Timestamp]
● [TransactionType]
● [TransactionDescription]
● [TransactionDetail]
● [TransactionDetailType]
● [UserID]
● [ConsoleID_DeviceID]
127
MN008865A01-AF
● [RdwAuditTimestamp]
7.3.5
Automatic Status Changes Logged to Incident History
(CAD) (375666)
Automatic Status Changes are logged to Incident History for both CAD and Mobile.
Administrators can provision the conditions that trigger an Automatic Status Update from the Provisioning
Dashboard by selecting Unit → Unit Status Codes → Unit Status Codes. If the conditions provisioned by
the admin are met, the Automatic Status Change occurs.
When an Automatic Status Change occurs, SYSTEM is the reported user and a new Transaction Description
of Unit Status (Automatic) is applied. This indicates why SYSTEM changed the unit status.
Figure 111: CAD Unit History Record
Figure 112: CAD Incident History Record
If the provisioned criteria for an Automatic Status update are not met, then the change of unit status must be
completed manually and the User ID will be logged as the specific user making the change.
7.4
reference.
PremierOne Mobile for IOS V4.6.9.220929

● PremierOne Mobile now supports IOS 16
● Compatible with with PremierOne CAD 4.3.0 to 4.6.9
● Added CA Purpose code for query related transactions to indicate the reasons
● Added Missing Fields on Scanned DL for Hair Color, Age and Height
PremierOne Mobile for Android V4.6.2210.1

● Compatible with with PremierOne CAD 4.3.0 to 4.6.9
● Supports Remove Restart functionality
128
MN008865A01-AF
7.4.1
Automatic Status Changes Logged to Incident History
(Mobile) (375666)
Automatic Status Changes are logged to Incident History for both CAD and Mobile.
Administrators can provision the conditions that trigger an Automatic Status Update from the Provisioning
Dashboard by selecting Unit → Unit Status Codes → Unit Status Codes. If the conditions provisioned by
the admin are met, the Automatic Status Change occurs.
When an Automatic Status Change occurs, SYSTEM is the reported user and a new Transaction Description
of Unit Status (Automatic) is applied. This indicates why SYSTEM changed the unit status.
Figure 113: Mobile Unit History Record
Figure 114: Mobile Incident History Record
If the provisioned criteria for an Automatic Status update are not met, then the change of unit status must be
completed manually and the User ID will be logged as the specific user making the change.
7.4.2
CJIS Security Support Updates for the Least Privileged
Access on Mobile Windows (383893)
To meet CJIS requirements, files have been moved from the installation directory, which by default is
Program Files x86\MobileClient to ProgramData. This change allows all users to have access,
instead of a select few users.
NOTE: To access the MobileClient folder in ProgramData, users must have permissions to
perform the following:
● Modify
● Read and execute
● List folder content
● Read
● Write
These permissions can be set in the Mobile Client Properties window.
All configuration files (*.xml and *.config) from the Program Files
(x86)\Motorola\PremierOne\MobileClient\config folder have moved to the
ProgramData\Mobile Client\config folder.
129
MN008865A01-AF
The following changes affect configuration files:

● The installer (MobileClient.wxs) copies *.xml and *.config configuration files to the
ProgramData directory using the Environment CommonAppDataFolder variable.
● The Mobile Client Configuration Tool (Executor) copies from templates and modifies *.xml configuration
files in ProgramData folder using dedicated tasks, which supports the use of Special Folder access
(SF_CommonApplicationData).
● The Mobile Client application uses the CommonAppDataFolder and ALLUSERSPROFILE environment
variable, which points to the ProgramData folder, to read from and write to configuration files.
All temporary files created by the mobile application are created in \\ProgramData\\Mobile Client\
\Temp
The files in the Temp directory are cleared after the user performs one of the following actions:
● Switches or transfers a session
● Logs out
● Before the user logs on by either clicking the Login button or pressing Enter in the password box.
This ensures that all temporary files are cleared between user sessions.
7.4.3
Google Android API 31 Support (384552)
In version 4.6.9, PremierOne Mobile Android includes changes to support the Android 12 operating system
and Android API level 31.
The new platform includes enhanced security which has led to changes in the following PremierOne Mobile
restart functions and in-app disclosure.
NOTE: Additional changes to support Google Android API 31 will be included in a future release.
Remove Restart Functionality

For API 31, foreground services cannot run in the background. Because of this requirement, PremierOne
Mobile Android users will be redirected to the Login screen after completing the following actions:
● Changing or updating connectivity settings like the server IP address
● Successfully uploading PRData on the Administration screen
● Using the Property file to change connectivity settings or download additional data
● Reaching the maximum number of login attempts while attempting to unlock a PremierOne Mobile
session
Previously, these actions triggered the application to close, and you would have to restart it manually. In
version 4.6.9, the data from these changes is uploaded dynamically, without requiring the application to
restart.
Updated In-App Disclosures

Version 4.6.9 also includes an update to the existing in-app disclosures describing how PremierOne Mobile
Android uses background location information.
NOTE: The wording of the disclosures was updated to clarify the process for collecting and using this
information. The process has not changed.
The updated disclosures read as follows:
130
MN008865A01-AF
Figure 115: PremierOne Mobile Android – Updated In-App Disclosures
7.4.4
Query Purpose Code for HandHeld iOS (361840)
The state of California requires a Purpose Code to be added to a query transaction to indicate a reason
for the query. To allow for automated vehicle and person queries from vehicle/person screens, the Purpose
Code field was added.
To make the Purpose Code field visible on CAD, Mobile Windows, Mobile iOS, and Mobile Android,
the Display Purpose Code checkbox must be selected in Provisioning by navigating to Provisioning
→ Incident Management → Service Settings → Initiation Defaults. Then, select or toggle Display
Purpose Code. Checking and clearing this box controls the visibility of the Purpose Code for each agency.
Prior to implementing the Purpose Code and checking the box to display the purpose code, it is important
to upgrade your PremierOne HandHeld application to the latest version available. Failure to do so results in
errors with older application versions.
Once the Display Purpose Code checkbox is selected in service settings, the Purpose Code field is
available within the Incident Management screens for Person Information, Vehicle Information, and Create
Traffic Stop in the HandHeld Mobile iOS application.
131
MN008865A01-AF
Figure 116: PremierOne Mobile iOS Purpose Code Examples
The list of purpose codes that are used could vary depending on the specific requirements from the system
being queried. Purpose codes need to be provisioned in Lists and Statute Management. The default
Purpose Codes for the state of California are:
● C – Criminal Justice
● I – Immigration Enforcement
● U – Investigate Violations of Title 8, US sec. 1325
132
MN008865A01-AF
Figure 117: PremierOne Mobile iOS Purpose Codes List
When Purpose Code is marked as a required field for a query and automatic query is enabled for the
corresponding IM screen, Purpose Code is a required field for the user. The user is able to complete and
save their changes (i.e. adding a person or vehicle) without selecting a Purpose Code, but an error message
displays to inform the user that the automatic query cannot be executed.
Figure 118: PremierOne Mobile iOS Query Not Sent Message
133
MN008865A01-AF
7.5
for reference.
7.5.1
User ID Field Period Support (276893)
You can configure a Configuration setting in the System Management Tool Portal to allow periods in a user
ID: for example, PremierOne.Admin. User IDs are used throughout the PremierOne system for logging onto
the console, accessing the purge settings log, and reauthenticating a user.
134
MN008865A01-AF
Chapter 8

4.6.8
NOTE:
8.1
4.6.8b Issues Resolved
● P1MOB- Incident status monitor not updating (322109)
● P1MOB - Delayed updates on mapping and road closures (Incorrect location and incident type on Map)
(341860)
● P1MOB - Driver License Scans (PDF417) does not populate all available fields (382720)
● P1MOB - GPS Status Indicator Clarification of Network vs Satellite issue (400465)
● P1MOB - Mobile Unit and Incident Status Monitors Not Updating (390864)
● P1 Deployment Tool - AIO Deployment Fails to Update ParameterBackUp.xml with GPSDevice
Parameter Group (390942)
● P1CAD - Emergency Notification Audible Tone not playing provisioned alert sound (329833)
● P1MOB - "An error occurred storing the incident information" upon update (376641)
● P1CAD - Object reference not set to an instance of an object (Cross threading issue investigation)
(392368)
8.2
● MOB – 4.6.5 Mobile crashes due to out of memory error without universal map installation (329847)
● Phone icons and RapidSOS icons do not disappear when call is released (392986)
8.3
● P1CAD PremierOne_PruneAuditCS_451 job is not scheduled to run – should be removed (112577)
135
MN008865A01-AF
● P1CAD SM to External CAD System Gets Rejected with Incorrect Error Message when Message Body is
Empty (126838)
● P1CAD – When deleting query returns in orphan window, jumps to near the bottom instead of the next
return (152790)
● IR Returns 250 max results, Status Message Area does not indicate this limit (205522)
● P1CAD – Query stores a Null ReceptionTime for a Cascade Query Request. (222284)
● P1CAD – Query Forward in Incident Recall Work Assist Area – Client Exception Error (241793)
● P1CAD – OL (Online) command does not put the console back online (260699)
● P1CAD – Slow Clicking and drag and drop not working properly (276360)
● P1MOB WIN – Priority Alert Follow me settings not being honored with Cross-Agency login to client
(284453)
● CAD Client allows user to be signed into the same device twice. (289658)
● P1 CAD – Unit showing twice in recommendations when covering more than one area (300710)
● P1CAD – Incident Recall – Print Summary Report showing Alias codes not incident types (324776)
● P1 CAD – CAD Slowness (Updated sproc-
procSelectPreviousPersonVehicleByIncidentKeyWithinSpecificAgencies) (325336)
● P1 CAD – Query Info showing in the Query Tab when not associated with the current Incident (335271)
● P1CAD – 4.5.1 & 4.6.5 – COVID related notes from ProQA not always showing as a priority comment
(341639)
● P1CAD: SB Command not displaying all statuses (Other Activity) (341760)
● Status Monitor provisioning giving errors on Filters when using 'Is Between' or 'Not Is Between' (342888)
● P1MOB – Messaging to units on an incident does not send attachments (344343)
● P1CAD: TYCO/SIS Issues with Interface to P1 CAD when verifying locations with multiple address points
(348479)
● Received error "Incident Update tasks are not complete. Please resubmit" after submit ProQA (5.1.1.43)
to CAD (352072)
● P1CAD: PremierOne_03_CADS shutdown unexpectedly – TpsEventNotification endpoint (354544)
● P1CAD – PSA Service Request Emergency Reporting Interface Issue: Month End Dispatch Numbers
(356142)
● P1CAD – GIS Service Private Bytes Reaching Threshold Limits (356627)
● P1MOB – "PRP/ Is not on duty" error when trying to change status (358161)
● P1CAD: RDW SSIS job CADIncidentUnitExtendRdwFeed failing due to MERGE statement (359054)
● P1MOB – After upgrading to 4.6.7 Mobile Client in training, many commands are grayed out when default
environment is set to production (361192)
● P1CAD – 2 or More Users are unable to log into PMDC (Outage) (361630)
● P1CAD – Report Number was not Assigned When Unit was Enroute as Provisioned (362991)
● Call Control – All calls are showing as 911 regardless of whether they are emergency or nonemergency.
(364299)
● P1CAD – Prince George County is is having issues with Zetron alerting (372264)
● P1 CAD – PremierOne_CS crashing, unhandled exception in DisableExpiredActivePersonnel (380177)
● P1 Mobile CAD Clients updates are slow (380328)
136
MN008865A01-AF
8.4
4.6.8 Known Issue
The following issue will be resolved in a near-term release. The Azure DevOps number is included for
reference.
The end-date/time for scheduled road closures is not recognized, impacting the Mobile Map display and
routing directions. The work around is to manually perform road closures until this issue is resolved. (379121)
8.5
reference.
8.5.1
Standard Operating Procedures (332009)
Standard Operating Procedures (SOP) allows Administrators to provision agency defined SOP.pdf
documents to Incident Response Factors (IRF) with provisioning at the Agency Type and/or Agency Level.
Figure 119: Standard Operating Procedure Templates
Once an SOP has been provisioned at the Agency Type or Agency level, it will be available for provisioning in
the corresponding levels of IRF provisioning.
137
MN008865A01-AF
Figure 120: SOP – Incident Response Factors
On the PremierOne CAD Client, a SOP button has been added to the bottom of the Incident Summary form.
If an incident is created with an IRF that has an SOP provisioned, the button and the Summary tab area will
highlight. If the SOP button is not active, the SOP template has not been associated with an IRF.
Figure 121: Incident Summary Form – SOP Button
CAD users can use a mouse or keyboard shortcut to select the SOP button and display a .PDF document
detailing the SOP. The SOP will display in the default .PDF viewer for the workstation.
138
MN008865A01-AF
Figure 122: SOP – PDF Viewer Example
Viewing and acknowledging an SOP will be documented in the Incident History, along with the date the SOP
was uploaded in Provisioning.
Figure 123: SOP – Incident History Details
8.5.2
Ability to Add Up to 25 Report Numbers Against an
Incident (345702)
The RP command can now accept a value between 1 and 25 for the N;<number of report numbers>
identifier.
139
MN008865A01-AF
Figure 124: Report Number Value Example
8.5.3
Manual Address Points (322751)
Manual Address Points provide the ability to create common places and address points without having to wait
for the GIS data to be updated and then refreshed within PremierOne.
The feature was first released in 4.6.7 (see Manual Address Points (322751) on page 154) and has been
further enhanced in 4.6.8 to include:
● Routable Street Centerline Location
● GIS Common Place Entry
● Common Place Alias Entry
CAD Administrators will be able to provision Address Points, Common Places, Common Place Aliases that
do not exist within the current GIS Data.
140
MN008865A01-AF
Routable Street Centerline Location

Figure 125: Manual Address Points – Routable Street Centerline Location
When a CAD user provisions an address point, they can also add a routable address for that point so that
access to that address point off the street centerline can be specified. This functionality allows for more
accurate drive directions and an ETA to be calculated to that location. Adding a routable address is only
necessary when adding a new address point. For common place changes to existing addresses/address
points, adding a routable address is not necessary.
GIS Common Place Entry

Figure 126: Manual Address Points – Common Place Names
A CAD user can provision one or more common places for street addresses currently in GIS. Entering a
corresponding Place Type is optional. If specified, the corresponding Place Type will display during address
verification in the same manner that Place Types within GIS display.
141
MN008865A01-AF
Figure 127: Manual Address Points – Matching Common Places
Common Place Alias Entry

Figure 128: Manual Address Points – Common Place Aliases
Common place aliases can be provisioned for any common place that was either provisioned as a Manual
Address Point, a Manual GIS Common Place or that currently exists within the GIS data. Provisioning
common place aliases assists the CAD user in entering frequently used or difficult to spell locations. In the
example above, the common place of LAGRANGE PD has been aliased to HQ. When a CAD user enters a
location of HQ, the location verifies to the true common place name of LAGRANGE PD but allows the CAD
user to use the HQ alias.
142
MN008865A01-AF
Figure 129: Manual Address Points – Previous Location Check
8.5.4
Voice Dispatch API (222992)
The following Voice Dispatch API enhancements are included in this release:
Two-Tone Alerting/Paging
Two-Tone Alerting, previously only available via the Gold Elite Radio Console, is now available in the
MCC 7x00 Consoles via the new interface. Two-Tone Alerting reuses the Radio Console status monitor.
Figure 130: Radio Console Sample
143
MN008865A01-AF
Dynamic Multiselect
Dynamic Multiselect allows for an automatically created multiselect based upon a specific unit or incident.
PremierOne CAD tracks all radios assigned to a specific unit and all units to a specific incident, and can
adjust the multiselect to ensure regardless of what talkgroups the radios are currently affiliated with, a
multiselect exists that ensures all responders hear important information. The multiselect is updated in
near-real time as the radio users switch between talkgroups.
Figure 131: Dynamic Multiselect
Manual Multiselect
The Manual Multiselect functionality allows the dispatcher to load a set of resources to a multiselect on
the MCC Elite Dispatch software from the PremierOne CAD workstation. To save time, especially for
common multiselect groups, PremierOne allows for pre-defined sets of talkgroups the dispatcher can
load.
Selective Call Alerting
Either through manual toning functions, or through pre-defined alerting records for automation during
incident dispatch, PremierOne CAD can trigger the transmission of page resources on the MCC console
allowing responders to timely and recognizable alerts. By integrating with PremierOne CAD, custom
alerting records allows for intelligence with paging. For example, a set of Quik Call II tones used for a fire
station can be configured to not sound if PremierOne CAD knows the unit needed for dispatch is out of
the station, reducing the time to transmit tones over the radio system.
For more information see PremierOne/ASTRO MCC 7x00 Integration for PremierOne CAD.
8.5.5
Include Images from Vigilant ALPR Hot Hit to the
Incident (366289)
When creating an incident from a Vigilant Automated License Plate Reader (ALPR) hot hit, the License Plate
and Car images included in the hot hit will be attached to the incident.
8.6
reference.
144
MN008865A01-AF
8.6.1
iOS Disposition Dropdown Filter (346709)
The iOS Disposition Dropdown Filter is similar to the Android Disposition Dropdown Filter delivered in the
4.6.4 release.
The disposition dropdown filter allows users to find dispositions by typing the first few letters of a disposition
type into the search field. This allows for finding dispositions without scrolling through multiple pages. No
Provisioning is required to activate this feature.
For more information see the PremierOne Mobile iOS User Guide.
Figure 132: iOS Disposition List Filtered by Search Criteria
8.6.2
Mobile Windows Restrict Query Dropdown Fields to
Picklist Selection (353279)
Mobile Windows restricts Query drop-down fields to only allow choices from a configured list. If you enter a
value that does not match one of the pre-defined list items, your text displays in red and the Submit button
and Enter are both disabled. You must choose or type a valid option before you can submit the query.
145
MN008865A01-AF
Figure 133: Mobile Client – Query – Invalid Drop-down Entry
8.7
for reference.
8.7.1
Provisioning Audit Tool (322888)
The Provisioning Audit Tool (PAT) is a tool that is independent of a specific release. PAT has a separate
documentation guide describing its use.
PremierOne PAT provides the ability to track provisioning changes and audit provisioning information that is
added or deleted by users who have permission to access provisioning.
This tool will require an installation of the tool software on the application server. Detailed installation
instructions are located in the new Provisioning Audit tool manual. The tool can be accessed by a web
browser (Chrome or Edge).
A user who has full administrator access to Provisioning will be able to access the Provisioning Audit Tool
(PAT) with their credentials.
146
MN008865A01-AF
Figure 134: Full Admin Access View
The PAT user can search for provisioning changes by date/time, User ID and Agency. They can search all
provisioning areas or check for changes in specific areas.
The show Change Data will display data that was changed in Provisioning. It will show the old data in red and
new data in green.
Figure 135: Audit Log Changed Data
The show Details will display a more detailed view of the provisioning change.
147
MN008865A01-AF
Figure 136: Audit Log Details
Data can be exported to a .CSV file if needed.

Figure 137: Audit Log Details CSV File Download
148
MN008865A01-AF
Chapter 9

4.6.7
NOTE:
9.1
● P1MOB – After upgrading to 4.6.7 Mobile Client in training, many commands are grayed out when default
environment is set (363613)
● Received error "Incident Update tasks are not complete. Please resubmit" after submit ProQA (5.1.1.43)
to CAD (363768)
● P1CAD – PSA Service Request Emergency Reporting Interface Issue: Month End Dispatch
NumberConcept definition (363770)
● Remove excessive logging that was introduced by time-zone fix (367317)
● Windows Mobile – out of memory – red X's (379679)
● [Mobile] Exit works different than logout – Switching environments causes some function buttons to be
greyed out (376543)
● Mobile Client – greyed out buttons in 4.6.7.174 - dev1/stg cloud (381609)
● P1 Mobile CAD Clients updates are slow (384099)
● Mobile Client – Switching environments cause endless loop with exception errors (384415)
9.2
4.6.7a Known Issue
The following issue will be resolved in a near-term release. The Azure DevOps number is included for
reference.
The end-date/time for scheduled road closures is not recognized, impacting the Mobile Map display and
routing directions. The work around is to manually perform road closures until this issue is resolved. (379121)
9.3
● P1CAD - IR command not returning User ID number searches (319755)
149
MN008865A01-AF
● P1CAD - Run an SSRS report against the Premise Hazards Attachments (309780)
● P1CAD - Notifications Inbox - Message Expander Button (253779)
● P1MOB - Incident History - Several fields displayed in American Standard date format (MM/DD/YYYY)
instead of Australian Standard (DD/MM/YYYY) (277904)
● P1CAD - CADIncidentUnitExtendRDWFeed feed job is failing (303628)
● P1CAD - Failed to expire the BOLO message fills up RST_ES_Bolo_Message (To address having more
than 4000 char) (329116)
● P1 CAD - HP - Unit Association Dropped from Dispo when Incident Mod Circ Updated when display is at
125% and the inc management form has a horizontal scroll bar (88618)
● P1MOB (Windows) - Incorrect Unit ID shown in Unit Details screen when selected from Unit Status
Function Key screen (297345)
● P1CAD - LEADS query response displaying associated to wrong inc (230839)
● P1CAD - IP Incorrect Queries Show Up in IR WAA (243614)
● P1MOB (Mapping) - Mobile Map - Unit Status colors are incorrect (324358)
● P1MOB (Windows) - Unit status colors do not match provisioned status colors in mobile map unit list
(331081)
● P1CAD - Query Response populating in unrelated incidents (303095)
● P1MOB - User in agency IP was able to modify assigned capabilities for units in agency IF (312833)
● Replica copies of "LocalSQLQuery_Response" format added on each change to Interface in Provisioning
(332294)
● P1MOB - CAD not showing officer cleared from call despite clearing (219157)
● P1Mobile - Manage Assignments Button Will Not allow Area Change if Also Using Sector (4.6.2) (235135)
● P1MOB - Manage Assignments- Password Field Is Not Enabled When Performing A Role Change Until
After User Clicks Submit (293976)
● P1CAD - Operation Time Not Being Converted To Local Time in RDW for Personnel Table. (112574)
● P1CAD - Unable to export Personnel data from Provisioning. It only export 600 records there are over
3,000 (need to include inactive) (309596)
● P1MOB - Mobile Logon Banner Does Not Auto Close (280891)
● P1MOB - Unable to configure Ripon FD to use built-in GPS via Windows Location services (330893)
● P1MOB WIN - When Mobile user is signed out from CAD Client and Logging into a different device -
graying out issue (293252)
● P1CAD - Checkboxes will disappear when moving page to page in Personnel Provisioning (303097)
● A ResponseFormat display causes Provisioning display error (332293)
● P1CAD - NCIC Attach Response box not auto focusing (288263)
● P1CAD - IM_Dispatched_Unit is being updated Even Though Nothing has been Done to the Unit
(267778)
● P1CAD - Run a SSRS report against the RDW to report on the Alarms Provisioned (309791)
● Too many units are being recommended for Combine with Any - No Restrictions (342438)
● PremierONE - Mobile Map version 2.10.8096.40067 displays "stopped working" dialog box on logoff
(344178)
● P1CAD - MSG Warrants Query Getting No Results Found (344506)
● P1CAD - Status Monitor update alert not working if update comes from associated incident (333372)
150
MN008865A01-AF
● P1 CAD - Issue with copying the history tables over to the RDWs (294232)
● P1MOB - Users cannot expand premise hazards sometimes (301405)
● Unit Status Update (USU) Messages from External CAD System Rejected due to Timestamp Comparison
Issues (347691)
● P1CAD - Unit Statuses for Foreign Agency Units Not Applied (349332)
● P1CAD - Messages logged by pswgs.cad.server.cadtocad mix UTC and local time (349338)
● Received "Failed to Dispatch the Unit" Error and CAD Froze (327207)
● P1MOB (Windows) - Users cannot expand prem haz records (337594)
9.4
reference.
9.4.1
ANI/ALI Rebid - Rebid on Incident Update (323862)
The incident update functionality has been enhanced to allow a CAD operator still in contact with a 9-1-1
caller to update the caller's ANI/ALI and third-party RapidSOS data within the Incident Management form in
an attempt to obtain more precise location (latitude and longitude) information from a wireless caller. The
updated location information received from either ANI/ALI or RapidSOS can then be used to update the
incident's location if necessary.
The ANI/ALI Data section within the Persons tab of the Incident Management form has been replaced with a
9-1-1 Caller Information section. This section separates the ANI/ALI latitude and longitude values (previously
displayed as: {latitude}/{longitude}) into their own respective fields and includes a RapidSOS Data section
which displays the location information provided by RapidSOS when available.
151
MN008865A01-AF
Figure 138: ANI/ALI Data and RapidSOS Features
The CAD User can toggle between using ANI/ALI Data or RapidSOS Data. The Update Incident location
button has been added to allow the CAD User to change the incident location to a new location when new
ANI/ALI Data is received. The ANI/ALI button (Shift +F11) functionality has been added to function for an
incident that has already been created. Map It functionality is also available.
Additional 9-1-1 callers providing pertinent information for an existing incident can also have their ANI/ALI
data added to the incident, allowing their reported ANI/ALI or RapidSOS location to be used to update the
incident's location.
152
MN008865A01-AF
Figure 139: ANI/ALI Information
When a Rebid of ANI/ALI information is completed for an existing incident and is different than the Initial
Caller, a red status message will display to alert the CAD User that the AN/ALI phone numbers do not match.
The ANI/ALI Information will remain active and the CAD User can select Add New to add a new caller and
their location to the incident.
153
MN008865A01-AF
Figure 140: ANI/ALI Add New Caller and Location
ANI/ALI from a different phone number added as an additional caller can be used to update incident location
as well.
Figure 141: ANI/ALI Different Phone Location
9.4.2
Manual Address Points (322751)
Manual Address Points provides the ability to create common places and address points without having to
wait for GIS data to be updated and uploaded.
154
MN008865A01-AF
Manual Address Points feature is now available in provisioning in the Mapping area.
Figure 142: Manual Address Points
CAD Administrators will be able to provision Address Points and Common Places (AP/CP) that do not exist in
the current GIS Data.
Manual Address Points will allow for provisioning of Longitude and Latitude for an Address Point and/or
Common Places that do or do not have an address.
The provisioner can enter the manual address point/common place by first verifying a location by longitude
and latitude. With the verified location a common place can be added along with the other fields that are
displayed in form. Sometimes there is a need to add information that would describe the location in the
description field. If this field is completed it will display in the CAD Client when this location is verified.
NOTE: Mobile clients configured to UseLocalGisServiceOnly will not be able to verify or use
manually provisioned address points.
Figure 143: Common Place Entry
155
MN008865A01-AF
Figure 144: Verified Common Place
The address points/common places that are entered into provisioning can be exported to a spreadsheet. This
ability allows for the GIS Administrator to have the data that needs to be added to GIS prior to loading new
GIS data.
Figure 145: GIS Data
Once new GIS Data is uploaded to the PremierOne system, all manual address point entries must be
reconciled against the new GIS Data to remove duplicates of the same address point or common place;
otherwise, both the GIS and manual address point entries for the location will be returned during the address
verification process. It is important for GIS Administrators to check this area of provisioning to ensure that all
entries are added to new GIS Data.
In PremierOne CAD release 4.6.8, Manual Address Points will include the following functionality:
● Routable Location (Needed for Route-Solving when AP/CP is detached from the Street Centerline)
● Entry of a GIS AP/CP to be replaced (For AP/CPs that were entered incorrectly in GIS)
● Introduce a Permanent Manual AP/CP indicator for filtering purposes when reconciling against a new GIS
Dataset
● Common Place Aliases
● Street Range Aliases
9.4.3
RapidSOS RAD-E Integration (285094)
RapidSOS Additional Data - Enhanced (RAD-E) is now available for RapidSOS integration with PremierOne.
The former RapidSOS Additional Data schema is being discontinued by Rapid SOS.
156
MN008865A01-AF
Figure 146: RapidSOS Additional Data Enhanced RAD-E
The functionality on the CAD Client to switch between Legacy ALI, Manual, and RapidSOS was added in a
previous version.
Figure 147: RapidSOS Swap
Also in a previous version the availability of LegacyALI and RapidSOS was added as a comment to each
incident. That functionality has been removed.
157
MN008865A01-AF
Figure 148: LegacyALI and RapidSOS Incident Comments Removed
9.5
reference.
PremierOne Mobile for iOS 4.6.220427

● Compatible with PremierOne CAD 4.3.0 (build 4.3.0.1200) to 4.6.7
● Resolved issue with Field Initiation (users can now create incidents without modifying circumstances even
if inactive modifying circumstances are associated with the chosen Incident type)
● Improved connectivity and reconnections
PremierOne Mobile for Android 4.6.220427

● Compatible with PremierOne CAD 4.3.0 (build 4.3.0.1200) to 4.6.7
● Android 11 / API level 30 compliance with Google Play policy
Mobile Configuration Tool

Starting with version 4.6.6, the Certificate Common Name field can now be defined on each of the
environment tabs (Production, Training, Staging) and is labeled as CertificateCommonName_Pro.
158
MN008865A01-AF
Figure 149: Certificate Common Name Field
9.5.1
Route to Incident Secondary Locations on Mobile Map
(70825)
Secondary Locations may be provisioned for Incident Response Factors and specific addresses. When units
are dispatched to an incident that has a secondary location, the unit may be dispatched to either the primary
location or the secondary location. If a unit is dispatched to a secondary location, the incident management
summary will display the secondary location in bold, red font to draw attention to this location rather than the
primary incident location.
159
MN008865A01-AF
Figure 150: Incident Summary when Dispatched to a Secondary Location
In this scenario, the Mobile Map will route the Unit to the Secondary Location. The Map will display an icon at
the primary location. The secondary location will be displayed as a red pin marker at the end of the route. The
Secondary location information also appears in the CallInfo bar on the lower section of the map page.
160
MN008865A01-AF
Figure 151: Route to Secondary Incident Location
9.6
for reference.
9.6.1
Alarms Provisioning Fields Added to RDW (309791)
The CadProvisioningRDWFeed job was updated to fill provisioning tables with Alarms data:
● [RST_PR_AlarmDefinition]
● RST_PR_AlarmCompany
● RST_PR_AlarmContact
● RST_PR_AlarmIncidentDefinition
● RST_PR_AlarmPhone
● RST_PR_AlarmResetProcess
Added new tables for RST_AL_Alarm and RST_HIST_Alarm and updated CadIncidentUnitRDWFeed to be
filled with alarms data.
Updated MV_IncidentHistory view to display historical data about alarms triggered.
161
MN008865A01-AF
9.6.2
Premise Hazard Fields Added to RDW (328803)
Premise Hazard Priority Type and Premise Hazard Attachment Name are now available fields in the RDW.
Priority Type includes the Critical, High and Normal Priorities. Attachment Name will include the name of the
attachment that was saved on a Premise Hazard record.
Figure 152: Premise Hazard RDW
9.6.3
Premise Hazard Fields on CAD Configuration Removed
(329988)
As of 4.6.0 the fields listed in the figure below are no longer used for PremierOne CAD client configuration
and have been removed from the configuration tool. The purpose that these fields served is now handled by
new technology.
Figure 153: Premise Hazard Fields on CAD Configuration Removed
162
MN008865A01-AF
Chapter 10

4.6.6
NOTE:
10.1
Issues Resolved
● P1MOB (Windows) - Mobile Map Keyboard Shortcuts Not Functioning Ctrl+C and Ctrl+Z. (300810)
● P1CAD - IR Search Terms Limitation on Short Words (221688)
● Mobile config tool doesn't handle Certificate names per environment (318172)
● P1 CAD - RDW missing transactions daily (196060)
● P1 CAD - RDW missing transactions - Improvements to procGetCurrentHistTransactionKey (268267)
● P1 CAD - Missing transactions between PCADDB and PCADRDW DB (297560)
● Incident Page Non Operational on Continues arrival of comments to the page. (308886)
● P1CAD - LSM data for PersonRace still showing in drop down list after being end dated (285188)
● P1MOB- Users unable to login to Mobile through App01 "The file path is blank" (298987)
● P1CAD - KC06B status monitor missing 3 incidents that displayed on other devices (292036)
● Provisioning unable to export Response ID for Recommendation (112519)
● P1CAD - Cloned roles inherited by users have exiting roles (303085)
● P1CAD - Messages count refreshing is lagging after messages have been read when there are greater
than 500 notifications (267160)
● P1CAD - Batch Provisioning for Personnel is failing (308201)
● P1CAD - ProQA field not showing in CAD (277577)
● P1CAD - IR command not returning User ID number searches (324402)
● P1CAD - EnrouteToHospital and ArriveAtHospital times missing from MV_IncidentUnits RDW when
Dispatch and/or Enroute Times missing from unit (312930)
● P1MOB - Mobile Map not displaying incident information or routing (290135)
● P1CAD - Message error when SMTP Message is sent - Error 72620552581283874 for
Motorola.PremierOne.Platform.Logging (267727)
● P1 CAD - Issue with copying the history tables over to the RDWs (326143)
163
MN008865A01-AF
● P1CAD - Updating Default Plate Year in Query Type Form Resets Agency Command to Default Settings
(145390)
● P1CAD reports - EnrouteHospitalTime and ArriveHospitalTime intermittently not displaying in the view
MV_IncidentUnits (313664)
● P1MOB - Mobiles Receiving File Path Error "The file path is blank" (293065)
● CryWolf/DSA Adapter Not Consuming Permit File (300387)
● P1 CAD - Persons tab information being erased after form submit (214823)
● CAD -Vehicle info not passing from ProQA to P1CAD (234434)
● SB returns error message regarding Arrived time when adjusting multiple times (222751)
● P1CAD - Frequent Auto recovery due to System.TimeoutException in
LocateAddressAndTryDelayGeocodingV2 (221121)
● RST_HIST_Incident and RST_HIST_Transact - Missing (INC STAT,CLOSED) transactions (200364)
● P1MOB - Users receiving error "The file path is blank" (298891)
● P1CAD - Address book not synchronizing for Keywords (312936)
● P1CAD - EthnicityType field missing from RDW view RSV_IM_Person_Current and MV_IncidentPerson
(295355)
● P1 CAD - Persons tab information being erased after form submit (214823)
● P1 CAD - Fire MDTs are not reporting status again (320470)
● P1MOB- Mapping - Mobile Map - Unit Status colors are incorrect (324358)
● P1MOB (Windows) - MAJOR ExceptionHandling Message:The file path is blank (333363)
● P1MOB - Unable to configure Ripon FD to use built-in GPS via Windows Location services (342870)
● P1CAD - MSG Warrants Query Getting No Results Found (344506)
● E911 - CAD Client Application Exception Error Upon Populating II form with E911 message (349360)
● In a CJI database, a query would not return unless it was marked as consolidated (323250)
10.2
reference.
10.2.1
Location Services – APX and APX NEXT to PremierOne
Connectivity 301489
Customers using APX or APX NEXT devices paired with CommandCentral Aware can begin taking
advantage of broadband cellular connectivity to receive location updates more frequently from Location
Services. Functionality is similar to existing APX device location mapping and capabilities; however, there
is no ability to control the cadence of location updates. Cellular connectivity removes the constraints of
sending data over a customer ASTRO system, so there is no need to modify update frequency based on
164
MN008865A01-AF
unit status. Customers interested in this functionality should consult with their appropriate Motorola Solutions
representatives to discuss options.
NOTE: The proxy must match the serial number.
Figure 154: Location Services Provisioning
Ensure that the radio provisioning section is as accurate as possible, whether using this interface or any
other ASTRO to PremierOne interface.
10.2.2
Support Incident Type Aliases with the Field Initiate
Command 309736
The Incident Type field on the Field Initiate (FI) form and the T;<incident type> command line identifier
for the FI command now support the entry of an Incident Type Alias that is valid for the respective unit's
agency. The behaviors associated with processing an Incident Type Alias for a Field Initiate transaction will
be similar to processing an Incident Type Alias for an Incident Initiate transaction.
10.3
reference.
Mobile Configuration Tool

Starting with version 4.6.6, the Certificate Common Name field can now be defined on each of the
environment tabs (Production, Training, Staging) and is labeled as CertificateCommonName_Pro.
165
MN008865A01-AF
Figure 155: Certificate Common Name Field
166
MN008865A01-AF
Chapter 11

4.6.5
NOTE:
11.1
In a CJI database, a query would not return unless it was marked as consolidated (323250)
11.2
● Mobile map - Unit info is missing in pop up on mouse hover on incident. (239991)
● Failed to Export Personnel list on Cloud. (264296)
● RDW SSIS packages are holding transactions longer than needed and throwing LRT alerts and causing
unnecessary background load. (231663)
● P1MOB - RoutePremiseLocationstoCenterline setting does not take into account prefix directions.
(254346)
● P1CAD - CADIncidentUnitExtents RDW Feed Job failure. (243040)
● P1MOB - Unit Status Monitor became blank for a long time. (144698)
● P1MOB - Mobile users cannot view GeoGroups in their own agency unless the geofence was created by
that user. (146095)
● Cannot add AIO Package in Deployment Console - "Error occurred during the retrieving data from
external cloud services" (251091)
● CAD client Call Control with VESTA Adapter- The VESTA API services was disconnected then connected
but ICC never recovered. (267773)
● Mobile Client neither went offline nor stayed online upon NetMotion Failover with 50ms network delay -
intermittent. (270158)
● AIO - AIO failed on some machines with the error "The checksum for file PreReqsConfig.xml does not
match the expected one" (274718)
● P1MOB - Incident Summary screen starts to flicker when a lot of units are on an incident and
commenting. (239427)
● P1MOB - Not receiving pop up for unit ID already in use. (256252)
● P1CAD - App Servers Rolling. (253189)
167
MN008865A01-AF
● P1CAD - syncing the address book, the system shows that the "address books are synchronizing" but the
never receive the success message. (113582)
● P1CAD - Invalid Modifying Circumstance Error After Performing Sync Now. (233600)
● P1MOB - International Date Format - WCF/Cloud QA1 Testing - Search Result error on Incident Recall
Form. (194178)
● P1MOB - URL is not opening from the command line if Browser button is not enabled from Provisioning.
(237387)
● procGISInsertStartRecordToScheduledClosureResults Causing CAD Slowness. (112651)
● SB command unhandled exception with submitting many times in succession. (222750)
● P1CAD - Cascade query isn’t working for local query. (265477)
● Mobile Map not displaying routing after auto restart. (257413)
● TAIP LN GPS data without unit info processed as stale data. (272922)
● P1CAD - Deleted skills still display in Skill dropdown. (281438)
● If a Hot Hit field is sent to P1 Mobile incident or RMS via smart copy, the value pulled forward is incorrect.
(60266)
● P1MOB - Two out of three MoR Mobile Clients went offline and never came back online upon MSP scale
down. The third took 4 minutes to go back online. (279367)
● Mobile Map shows units that are not covered or monitored. (269263)
● Mobile Client: Unit Status stayed green (no confirmation from server) after NetMotion Failover. (270584)
● AIO - AIO failed on some machines with the error "The checksum for file PreReqsConfig.xml does not
match the expected one" (276585)
● P1MOB - The Invalid IP Pop Up does not pop up on the Mobile Client when the Mobile Session is locked.
Also, Mobile Log showed Online although the IP Address was Invalid. (289998)
● P1MOB WIN - Default roles don’t import with query response. (284430)
● P1MOB - Glendale PD Premise Hazard Audible Alert Not Sounding. (291243)
● P1 CLOUD - The incident time in the moto(external) email and notification box is incorrect. (204020)
● P1CAD - CommonServiceMasterService crashes followed by restart of services (Message Parallelization
Issue) (280956)
● P1CAD - Application exception error when closing the orphaned history window. (202850)
● P1CAD - Failed to load Assembly D:\Program Files
(x86)\Motorola\PremierOne\PremierOne_01_CNS\services\PSWGS.Cad.Server.dll (280994)
● P1CAD - Incorrect Field Visibility in Reporting Server Config Tool 4.6.3a. (280993)
● P1CAD : Address verification does not populate form when there is a single common place without
selecting (difference from 4.6.0 behavior). (294690)
● Provisioning settings to update/delete groups/geo groups are not in sync with Mobile Client. (266791)
● Concurrent Login Fails - (Error - Failed to logout previous user. - Logoff from the CAD Service failed).
(196280)
● Import Capability Group and Capability/Skill - invalid message of "Import Error on Row". (285859)
168
MN008865A01-AF
11.3
reference.
11.3.1
Immediately Take Units Off Duty Upon Receiving an Off
Duty Notification 154874
In an effort to keep the activities of units belonging to a foreign agency consistent between PremierOne
and the units' external CAD system, PremierOne will process any Off Duty CAD-to-CAD message it
receives against the foreign unit specified in the message regardless of the unit's current status or incident
assignment.
● If the foreign unit is currently in a Clear status, the unit will simply be taken off duty. There is no change to
this standard functionality.
● If the foreign unit is in a status other than Clear, the unit will be placed into the unit status provisioned
for the Clear transaction under Unit Management → Settings → Transactions provisioned either for the
unit's Agency or Agency Type level before being taken off duty.
This change in processing Off Duty notifications should have little or no impact on PremierOne CAD systems
receiving Unit Status Updates as they occur. The typical workflow for these systems would be to first receive
a Unit Status update from the external CAD system for one of their units before receiving an Off Duty
notification for that unit.
For PremierOne CAD systems receiving all Unit Status updates at particular intervals (Bulk USUs), it is
possible for the external CAD system to miss sending a Clear status for their units that were taken off duty in
between the Bulk USU interval.
Example
A101 happens to be on duty and is being managed by an external CAD system. This unit would belong to a
foreign agency on PremierOne. The last status change PremierOne received for A101 placed the unit into a
Busy status.
If A101 is cleared and immediately taken off duty on the external CAD system, it is more than likely that A101
would not be included in the next Bulk USU we receive from that external CAD system. In this case, we
would only receive an Off Duty CAD-to-CAD notification for A101.
Prior to this feature, since A101 was not in a Clear status, PremierOne would either reject the off duty
notification or place the unit into a Deferred Off Duty state, depending on how the unit's agency was
provisioned. In both cases, PremierOne would no longer be aligned with the external CAD system on the
state of A101.
With the implementation of this feature, any Off Duty CAD-to-CAD notification we receive from an external
CAD system for one of their units would take precedence over the unit's current activity. Therefore, A101
would first be placed into the Clear status provisioned for A101's Agency (or Agency Type if none is
provisioned at the Agency level) and then taken off duty.
Clearing the unit under this circumstance will be reflected in the unit's History and incident's History if the
unit is being cleared from an incident assignment.
169
MN008865A01-AF
11.3.2
Accept a Call for Service (CFS) Acknowledgement Retry
Value of Zero (0) 258544
The number of retries within the Interface → External System → System Identification provisioning page
has been modified to accept a minimum value of zero (0) instead of one (1). This allows retries to be handled
outside of PremierOne's internal CAD-to-CAD retry logic if necessary.
Figure 156: Accept a CFS Acknowledgement Retry Value
When the Number of Retries is set to zero (0), PremierOne will make no attempts to resend
the message. All outbound CAD-to-CAD messages associated with these retry settings that are not
acknowledged within the Retry Interval will cause a failure notification to be generated. It is then sent to
the recipients provisioned within the Notify on Failure field.
NOTE: The default value for the Number of Retries remains at three (3) and its maximum value
remains at 99.
11.3.3
Query Purpose Code Added to II, IU, FI Commands and
Vehicle/Person Screens 175033
Some states require a Purpose Code to be added to a query transaction to indicate a reason for the query.
To allow for automated vehicle and person queries from vehicle/person screens a Purpose Code field was
added. To allow for automated queries to occur in conjunction with the II, IU or FI commands the PUR
identifier field was added to each of those commands.
To have the Purpose Code viewable on CAD, Mobile Windows, Mobile iOS and Mobile Android the Display
Purpose Code must be selected. Navigate to Provisioning → Incident Management → Service Settings
→ Initiation Defaults. Select or toggled on Display Purpose Code. Checking and unchecking this box
controls the visibility of the Purpose Code for each agency.
170
MN008865A01-AF
Prior to implementing the Purpose Code and checking the box to display the purpose code, it is important to
upgrade all CAD and Mobile clients to release 4.6.5 or higher. Failure to do so will result in errors with older
client versions.
NOTE: Purpose Code in Mobile iOs and Mobile Android will be available in a future release.
Figure 157: Display Purpose Code Box
Once the Display Purpose Code checkbox is selected in service settings the Purpose Code field will be
available in the Person and Vehicle screens on the CAD Client.
171
MN008865A01-AF
Figure 158: Person Vehicle Screen
Figure 159: Person Vehicle Screen Purpose Code Box
172
MN008865A01-AF
The list of purpose codes that will be used could vary depending on the specific requirements from the
system being queried. Purpose codes need to be provisioned in Lists and Statue Management. The default
Purpose Codes are:
● C - Criminal Justice
● I - Immigration Enforcement
● U - Investigate Violations of Title 8, US sec. 1325
Figure 160: Lists Statute Management
Associating a query to the Person and Vehicle screens is located in provisioning Query → Agency Level
→ Settings → IM Query Settings.
The Purpose Code has been added to the list of fields from the Person and Vehicle screens that can
be selected as being needed to trigger the running of the automated query. Additionally, the query that is
provisioned in the IM Query Settings can be used to manually send the query by clicking the query button on
the person or vehicle screen.
173
MN008865A01-AF
Figure 161: Agency Level Setting IM Query Settings
174
MN008865A01-AF
Figure 162: Agency Level Settings Purpose Code
Purpose code added to Incident Update (IU) command. It is defaulted at the end of the available identifiers
and can be moved to different positions in the command order, used with the PUR; Identifier or set to not be
used on the command line.
Figure 163: Purpose Code Command Line
175
MN008865A01-AF
Purpose code added to Incident Initiation (II) command. It is defaulted at the end of the available identifiers
Figure 164: Incident Initiation Command Line
Purpose code added to Incident Update (IU) command. It is defaulted at the end of the available identifiers
Figure 165: Field Initiate Command Line
176
MN008865A01-AF
11.3.4
Contractor Capability Added to Incident History and
RDW 248420
When provisioning contractors, capabilities can be added to each contractor entry to identify the abilities of
that contractor and allow for contractor rotation(s) to be based on those capabilities. Within the RDW the
contractor capability was not available. This feature adds the contractor capability to the RDW for reporting
purposes.
The tow capability will now display in theIncident History
Figure 166: Filter By Contractor
Searching by Contractor within incident history along with the ability to view Incident History focused on
Contractors from the command line is also available and was added to the PremierOne CAD Users Guide.
IH.<Incident ID or Active Unit ID>.CONTR
Four tables were updated in RDW:
● -RST_CR_ContractorRotationRequest
● -TMP_CR_ContractorRotationRequest
● -RST_HIST_Contractor
● -TMP_HIST_Contractor
In each table a new column named "RequestedCapabilityCode", data type of column is nvarchar(50) was
added.
177
MN008865A01-AF
11.3.5
Added Secondary Response Location to Available
Fields in CAD Status Monitors 15029
PremierOne CAD has the ability to have a Secondary Response Location associated with the Incidents
(primary) location. This feature adds the ability to have the Secondary Response Location displayed on the
CAD Status Monitor.
In provisioning the following new fields will be available for Incident, Pending and Call Taker type windows in
a CAD Status Monitor display set.
● SRL City
● SRL Cross Street
● SRL Location
● SRL Location Name
● SRL Name
Figure 167: Pending and Call Taker Type Window
For Unit type windows in CAD Status Monitor Display set, the following fields will be available.
● Incident SRL City
● Incident SRL Cross Street
● Incident SRL Location
● Incident SRL Location Name
● Incident SRL Name
178
MN008865A01-AF
Figure 168: Unit Type Window
The SRL fields will also be available for sorting on the Incident, Pending, and Call Taker type windows.
Figure 169: SRL Fields
The Incident SRL fields will be available for sorting on Unit type windows.
179
MN008865A01-AF
Figure 170: Incident SRL Fields
For Status Monitor filtering the new SRL fields and Incident SRL fields will be available for Incident,
Pending, Call Taker and Unit Type windows as well.
Figure 171: Unit Type Status Monitor Filter
180
MN008865A01-AF
Figure 172: Incident, Pending, Call Taker Status Monitor Filter
The new SRL fields and Incident SRL fields will be available to create Alerts.
Figure 173: Incident SRL Fields
Additionally, the SRL fields and Incident SRL fields can be used as a field available for display within an
alert’s pop up dialog box. (For example: %%SRL Location Name%% being available for use within the Alert
dialog box when provisioned to display).
181
MN008865A01-AF
Figure 174: New SRL Fields
11.3.6
Edge Browser Support 277337
Internet Explorer (IE) 11 desktop application will end support for certain operating systems starting June
2022.
Customers are encouraged to move to Microsoft Edge with IE mode. IE mode enables backward
compatibility and will be supported through at least 2029. The PremierOne CAD provisioning portal can
be operated with Microsoft Edge with IE mode. Enabling the Internet Explorer mode is straightforward and
can be done through the Settings option within the Edge browser.
11.3.7
Organization and Department Hierarchical Reporting
Structure 274770
This feature covers organization and department hierarchical reporting structure for smaller agencies to be
combined.
PremierOne's organization and department hierarchical reporting structure allows smaller law enforcement,
fire, or medical entities to be combined under a single CAD agency for ease of operation. This reporting
structure still allows for incidents handled by these smaller entities to be distributed efficiently.
For example, a single PD agency can be provisioned within PremierOne to handle the following entities:
182
MN008865A01-AF
Figure 175: Departmental Hierarchical Structure Example
In terms of PremierOne's organization and department hierarchy, the cities of Bradford, Penshaw, and
Whitebridge are agency PD's organizations and the entities below each city represent their respective
departments.
Personnel and/or units can be optionally assigned to any one of these departments. Whenever a unit is
assigned to an incident the corresponding organization and department assignments will be captured against
the incident and sent to PremierOne's Reporting database (ReportingDW).
New Organization and Department provisioning pages and import spreadsheets have been added to allow an
agency to provision the organization and department hierarchy.
The Personnel and Unit Preassignment provisioning pages and import spreadsheets have been modified to
allow for the selection of a department against these records.
Additionally, new import spreadsheets have been created allowing an agency to update their existing
personnel and unit preassignment data with a department entry.
The department update spreadsheets can be found on the PremierOne CAD server under the following
Motorola
subfolder:Motorola\PremierOne\PremierOne_01_CADP\services\PSWGS.Cad.Server.Provisio
ning\Business\ExportImport\Template
The respective names of the department update spreadsheets for personnel and unit preassignments are:
● Personnel_Department_ExportImport_Template.xlsx
● Unit_Department_ExportImport_Template.xlsx
183
MN008865A01-AF
11.4
reference.
11.4.1
Query Purpose Code Added to Mobile Traffic Stop Form
and Person and Vehicle Tabs 202019
Some states require a Purpose Code to be added to a query transaction to indicate a reason for the query.
To allow for automated vehicle and person queries from vehicle/person screens a Purpose Code field was
added.
To have the Purpose Code viewable on CAD, Mobile Windows, Mobile iOS, and Mobile Android the Display
Purpose Code must be selected. Navigate to Provisioning → Incident Management → Service Settings
→ Initiation Defaults. Select or toggled on Display Purpose Code. Checking and unchecking this box
controls the visibility of the Purpose Code for each agency.
Before implementing the Purpose Code and checking the box to display the purpose code, it is important to
upgrade all CAD and Mobile clients to release 4.6.5 or higher. Failure to do so will result in errors with older
client versions.
NOTE: Purpose Code in Mobile iOs and Mobile Android will be available in a future release.
Figure 176: Display Purpose Code
Once the Display Purpose Code check box is selected in service settings, the Purpose Code field will be
available in the Traffic Stop form on the summary tab as well as the incident persons and vehicle tabs.
184
MN008865A01-AF
Figure 177: Purpose Code on the Traffic Stop Form
Figure 178: Purpose Code on the Incident Persons Tab
The list of purpose codes that will be used could vary depending on the specific requirements from the
system being queried. Purpose codes need to be provisioned in Lists and Statue Management. The default
Purpose Codes are:
● C - Criminal Justice
● I - Immigration Enforcement
● U - Investigate Violations of Title 8, US sec. 1325
185
MN008865A01-AF
Figure 179: Lists Statute Management
Associating a query to the Person and Vehicle screens is located in provisioning Query → Agency Level
→ Settings → IM Query Settings.
The Purpose Code has been added to the list of fields from the Person and Vehicle screens. It can be
selected as being needed to trigger the running of the automated query. Additionally, the query that is
provisioned in the IM Query Settings can be used to manually send the query by clicking the query button on
the person or vehicle screen.
Figure 180: Agency Level Setting IM Query Settings
186
MN008865A01-AF
11.4.2
Designate Riding Position During Logon 209329
Riding Position can now be entered from the Mobile Client on the simple and/or detailed logon screen.
Riding position allows in-vehicle assignments to be identified for crew members assigned to a multiple person
unit. Previously this was only available through roll call processing or entry from a CAD client.
The Riding Position is a dropdown field that contains options. These can be configured in Provisioning on the
Unit Management → Riding Position page. Selecting the check box to Use riding positions for on-duty
and roll call assignments will automatically add the riding position field option for Crew members. This
shows on the bottom portion of the Detailed Logon Page.
Figure 181: Unit Management - Riding Position
The Riding Position Field can be designated for the logged on officer. It can also be designated for each
crew member. The location of the Riding Position can be configured on the Simple and/or Detailed Logon
forms. This configuration is set in the Customization → Mobile UI Customization → Login Options page.
187
MN008865A01-AF
Figure 182: Mobile UI Customization - Login Options
Figure 183: Simple Login Form with Riding Position Dropdown
188
MN008865A01-AF
Figure 184: Detailed Login Form with Riding Position Dropdowns
The Riding Position can be viewed on the Detailed Unit Status page. This display does not require
provisioning.
Figure 185: Detailed Unit Status Page
New column choices are available for the Unit Status Summary Monitor and Detailed Unit Status
Monitors.
To add the Riding Position to one or more Monitors, from Provisioning, navigate to the Customization
→ Mobile UI Customization → Status Monitor Display → Fields tab. Then select either the Unit Status
Summary or Unit Status Detail Monitor to see the available column choices. Select the Riding Position
field and tap the arrow key to add the field to the monitor. Use the Move Up or Move Down buttons to
position the field in the desired location.
189
MN008865A01-AF
Figure 186: Mobile UI Customization - Status Monitor Display Field Configuration
11.4.3
Displaying ARL Unit Location History on the Mobile Map
209327
You can use the ARL History (Automatic Resource Locator) history feature to play back the location history
of selected units to display where each unit was during specified time periods. ARL uses GPS (Global
Positioning System) data saved on the PremierOne server for each unit or vehicle.
Two types of GPS tracking are available: Direct GPS tracking and PremierOne Mobile/Premier MDC client
tracking. If your agency uses Direct GPS tracking, data transfers from the GPS device directly to the
PremierOne server. If you do not use Direct GPS tracking, data goes through the Mobile client application to
the PremierOne server.
Display Location History on the Map Display

If Provisioned, the ARL History icon appears on the right side of the Mobile Map Status bar.
190
MN008865A01-AF
Figure 187: ARL History Icon
Tapping on the ARL History icon will switch the map display to an alternate map view showing the map with
the ARL History panel on the right side of the Map screen.
Figure 188: ARL History Screen
On the ARL History screen:

The ARL History tab shows Automatic Resource Location information, if available, for the criteria you select
on the tab, such as a specific incident, vehicle, or unit.
Enter as much information as you can in the fields on the ARL screen and click Search. Agency and at least
one Unit or Vehicle are required.
The results of your search appear in the area below the search form.
191
MN008865A01-AF
Figure 189: ARL History Query Results
To export the unit location, select at least one item and tap the Export button. A Save File dialog will display.
The following fields are exported to a .csv file:
● #,Unit ID
● Agency ID
● Incident ID
● TimeStamp
● Longitude
● Latitude
● Speed
● Heading
● Location
11.4.4
Audible Alerts for Priority Fields 175283
Audible alerts for priority fields available in PremierOne Mobile for Windows.
Audible alerts can now be configured for specific fields to draw attention to priority updates. In previous
versions, audible alerts could be turned on or off but the setting applied to all Incident Updates. This feature
adds the ability to select individual Incident fields to trigger an audible alert, and allows the alert sound to be
customized, adding uniqueness to the alert tone.
This feature is configured through Provisioning.
192
MN008865A01-AF
The Incident Management Service Settings Priority Updates page has been expanded. The page now
includes comments and priority comments, as well as check boxes to select individual fields for audible
alerts.
Administrators can select the audible alert box for each field where an audible alert is desired. Additionally,
on the Incident Management Mobile/Handheld Incident Update page, Administrators can select a
custom .wav file for the preferred tone associated with the Priority Fields. This feature has also added
the ability to separate audible alerts for priority comments from standard comments.
Figure 190: Service Settings - Priority Updates - Mobile Settings
193
MN008865A01-AF
Figure 191: Mobile/Handheld - Priority Alert - Incident Update
11.4.5
Display All Assigned Units on CAD2CAD Incidents
234607
New functionality was added to automatically display all responding units for CAD2CAD initiated incidents.
In previous versions, when a secondary incident was created to assist other agencies through a CAD2CAD
incident, P1 Mobile only displayed units from the assisting agency rather than all responding units. In order to
improve situational awareness and provide the full picture of responding units for Incident Command needs,
new functionality was added to automatically display all responding units for CAD2CAD initiated incidents.
No provisioning is required unless you wish to show colors indicating the Unit Status. In this case, the Unit
Status colors must be configured for all Agencies participating in the CAD2CAD arrangement. The Unit
Status colors are configured in Provisioning under Customization - Mobile UI Customization - Status Monitor
Colors - Unit Status tab.
194
MN008865A01-AF
Figure 192: Incident Summary with All CAD-2-CAD Units Displayed
11.4.6
Enhanced Barcode Scanner Support 240935
A new barcode scanner indicator was added as an option on the Mobile Client Status Bar. The indicator
identifies the connection status and has the ability to temporarily disable scanning if needed.
Figure 193: Status Bar Scanner Indicator
There are 4 barcode scanner status indicator states:

Figure 194: Status Indicators
The indicator is an option that can be turned on through Customization → Mobile UI Customization
→ Status Bar as shown in the following figure:
195
MN008865A01-AF
Figure 195: Mobile UI Customization
Improved HID Support

Prior to 4.6.5, Human Interface Device (HID) Scanners were provisioned in the Lists and Statute
Management (Global Level).
Figure 196: List Statute Management
While a provisioned HID device is still supported in 4.6.5, the new preferred method allows configuring of
multiple HID devices via the configuration tool, similar to serial scanners and magnetic stripe readers.
196
MN008865A01-AF
Figure 197: Scanner Device
Improved Peripheral Configuration

The ScannerDevice tab in the Configuration Tool includes a new Scanner Device Type setting that now
enumerates/demystifies which peripheral device type to use.
Figure 198: Any Device Detected
Configuring a specific device type improves P1 Mobile performance and reduces hardware configuration
ambiguity. The supported scanner device types include:
Any Device Detected

This setting is the default, and directs P1 Mobile to deduce which connected peripheral device to use. This
setting is not recommended, as it leads to potential problems and poor performance. Instead, choose one of
the specific peripheral types listed in the Scanner Device Type dropdown.
No Device Configured
Use this setting if there are no scanners or magnetic stripe readers connected. This will substantially improve
P1 Mobile overall performance.
Magnetic Stripe Reader (Serial)

This setting designates a serial driver license Magnetic Stripe Reader. The ScannerCOMPortId setting
indicates where this reader is physically connected.
Magnetic Stripe Reader (POS HID)

This setting designates a POS HID driver license Magnetic Stripe Reader. Unlike a serial Magnetic Stripe
Reader, this type of device will be listed in the POS HID Magnetic Stripe Reader section of Windows Device
Manager, such as this MagTek Magnetic Stripe Reader.
197
MN008865A01-AF
Figure 199: POS HID Magnetic Stripe Reader
Scanner (Serial)
This setting designates that a serial Barcode Scanner will be utilized for scanning driver licenses and vehicle
registrations. The ScannerCOMPortId setting indicates where this scanner is physically connected.
Scanner (HID)
This setting designates that an HID Barcode Scanner will be utilized for scanning driver licenses and vehicle
registrations. HID Barcode Scanners requires unique vendor and product codes to access the device. P1
Mobile allows defining up to three HID scanners that can be detected while running. A scanner name and
HID Codes are set as follows.
Figure 200: Scanner HID Codes
M260 Serial Scanner/Mag Stripe Reader

This setting designates that an E-Seek M260 device will be configured. The M260 is a serial hybrid device
that contains both a barcode scanner and magnetic stripe reader. The ScannerCOMPortId setting indicates
where the M260 is physically connected.
198
MN008865A01-AF
Disable/Re-enable HID Scanners Via Scanner Indicator

Some agencies use additional 3rd party applications for scanning documents. In order for another application
to have exclusive access to a shared scanner, P1 Mobile needs to temporarily disable scanning. When the
Indicator Can Disable Scanning configuration setting is true:
Figure 201: Indicator Can Disable Scanning
The scanner status bar indicator acts as a toggle button to enable or disable scanning on P1 Mobile:
Figure 202: Scanner Status Bar
NOTE: This functionality is only available for HID Scanners.
11.4.7
Search Filter for the Disposition Field Updated in
Android 263449
Search filter for the Disposition field updated in Android.
Disposition search capabilities are now available on the PremierOne Mobile Android client when clearing
from an incident. As the User begins typing search criteria, the disposition list is filtered to only show options
that contain the search criteria text. No Provisioning is required to activate this feature.
199
MN008865A01-AF
Figure 203: Full Disposition List Figure 204: Disposition Filtered by Search Cri-
teria
11.4.8
Google Android API 30 Support 243357
PremierOne Mobile Android now supports the Android 11 operating system and Android API level 30.
The new platform includes enhanced security which has led to changes in the following PremierOne Mobile
location permissions and installation processes.
Background Location Permissions

The new security measures will prevent access to GPS when applications are not in focus, when the device
is in sleep mode and when the device is locked. In order for PremierOne Mobile to process the GPS location
throughout the logged on session, “Access all of the time” permissions must be granted for the Android
Background Location. This setting only applies when the Mobile client has an active session.
The steps to grant the Background Location permissions and manually install PRdata and/or .WebMap files
are described below:
● Background Location permission: Users will be presented with the Background Location request. Click
Allow.
● On the Administration screen, tap the Select file field to open the File Explorer.
NOTE: This process must be repeated for each file you wish to import.
200
MN008865A01-AF
11.4.8.1
Granting Background Location Permissions
The steps to grant the Background Location permissions and manually install PRdata and/or.WebMap files
are described below.
Procedure:
1. Tap Allow.
Figure 205: Background Location Permission
2. Select Allow all the time.

This form appears after tapping the Allow button shown in step 1.
201
MN008865A01-AF
Figure 206: Location Permission Settings
NOTE: The look of the form may vary in your device.
3. Select the PRdata (.db), Properties, and/or WebMap file.

a. Tap Select File.
202
MN008865A01-AF
Figure 207: Administration Screen
b. Select the needed.webmap, .properties or .db (PR data) files.

NOTE: Only one file can be imported at a time. This process must be repeated when
importing multiple files.
4. Navigate to the folder where the file is saved.
a. Tap the filename to import it.
203
MN008865A01-AF
Figure 208: File Explorer
NOTE: Your File Explorer may look differently.
When the user selects a valid (.webmap, .properties, .db) file, its name will populate on the form.
5. Tap the Start button to process the file.
204
MN008865A01-AF
Figure 209: Confirming File
NOTE: A file cannot be processed when the extension is not recognized as

a .webmap, .properties, or .db. If that happens, an error message will appear. Tap Ok to dismiss
it. The form will show the invalid file in red. Tap Select file again to choose a valid file to import.
205
MN008865A01-AF
Figure 210: Invalid File Import
11.5
for reference.
11.5.1
Query Response Format Designer Refresh 293471
The ability to format and design query responses is part of PremierOne Provisioning. Provisioning uses
Microsoft Silverlight software to accomplish this. Since October 2021, Silverlight has since been discontinued
by Microsoft. This feature replaces Silverlight for query response formatting.
206
MN008865A01-AF
Figure 211: Suite Level Setting
See Chapter 30: Configuring Queries in PremierOne CAD and Mobile Provisioning Guide version 4.6.5 This
guide contains the complete update information for using the Query Response Format Designer.
207
MN008865A01-AF
Chapter 12

4.6.3
NOTE:
12.1
Issues Resolved
● In CAD, users experienced the "An error occurred assigning a report number" error during RP command.
(196262)
● "Get incident configuration failed" error occurred when users were making changes in Incident
Management → Service Settings in Provisioning. (235562)
● Users experienced an incorrect import error message in Provisioning → Resources → Personnel.
(174326)
● In CAD, Status Monitor alerts drew the cursor from the work are to the pop-up message box. (209829)
● Users experienced short delays in command line refresh. (235214)
● Using certain right-click commands on timed-out incidents resulted in the "Incident Does not exist" error.
(191104)
● ALI information for a call is now displayed even if the call is not yet answered. (228948)
● Incident Management → Service Settings Provisioning can now be properly accessed. (232846)
● Using right-click menu to close an incident at certain hours resulted in an error. (197924)
● In Provisioning, selecting any option related to Unit Status in the drop-down menu in Customization
→ Mobile UI Customization → Function Keys resulted in a blank screen. (173978)
● Person height imported incorrectly from ProQA. (155242)
● Exporting full personnel resulted in the "Failed to Export" error. (209293)
● Changes made and saved in Provisioning reverted back to default value. (206969)
● CAD Client crashed when a second user tried to start the application. (179259)
● In CAD, an error occurred when users executed the Status Backdating command. (202837)
● Comments independently moved between incidents. (204820)
● The "Failed to dispatch the unit" error occurred when ProQA updated an incident. (230638)
● Clicking on a response in query occasionally resulted in the "Application Exception Error" message.
(117217)
208
MN008865A01-AF
● The "Your password has expired. Please change it now" pop-up box did not display correctly for users
with expired passwords. (234418)
● In Provisioning, weight and height values were read incorrectly during personnel import. (229340)
● Drawing data from ReportingDW's MV_IncidentHistory view lasted up to 3 minutes and resulted in
interface timeout. (176568)
● The "Application Exception Error" occurred when users looked through query replies in Orphan window.
(178985)
● CAD Client switched to Offline Mode after being logged on for a short time. (235631)
● In Provisioning, an unhandled null exception occurs during PremierOne upgrade. (202732)
● Users were unable to configure the UnitStatus function key. (113717)
● Calculation failures in the CommSys interface prevented queries from working. (86544)
● Units configured in the ETA order were not sent to Locution fire station alerting in that order. (205835)
12.2
reference.
12.2.1
Status Selection for Freed Incidents (15731)
Users can now set the status Incidents return to when they are freed to either Initial or Pending in Incident
Management → Service Settings → Service Defaults → Freed Incident Status.
12.2.2
Sending RapidSOS Information to the Incident Address
Field (154707)
Administrators can now provision the RapidSOS information to be automatically sent to the Incident
Address field. If RapidSOS is provisioned but not available, the carrier location is used. This applies to
both ICC and non-ICC implementations.
You can use the Swap button to change the incident location between 9-1-1 data, RapidSOS, and the
manually entered location. The button activates if the RapidSOS is enabled and 9-1-1 data or RapidSOS data
is populated to an II form.
12.2.3
Proactive Recommendations (161801)
A new option has been added to the Unit Recommendation → Settings → General provisioning page
under Proactive Recommendations. The new minimum time savings setting allows Automatic Proactive
Recommendations and the PR.U;<unit id> command line transaction to only recommend the proactive unit as
a replacement for a unit already assigned to the incident if the time savings between the proactive unit and
the assigned unit is at least the specified value in minutes and seconds.
209
MN008865A01-AF
12.3
reference.
12.3.1
Zoom-In Functionality for GeoFence List Items (191416)
A zoom function to view GeoFence items in the Mobile Map is now available in the form of a magnifying glass
next to the GeoFence slider control.
Figure 212: Zoom Function
210
MN008865A01-AF
12.3.2
Ability to Parse-out a Period in the User-ID [Montgomery
Co., TX] (220979)
PremierOne can now ignore a ‘period’ in the UserID when logging-in from a Mobile or CAD client.
This capability was developed for Montgomery Co. TX and must be enabled to become active
in PremierOne System Management Tool Portal → Configuration → App → appConfig
"SupportPeriodInTheUserIDFieldForLogin"="true".
12.3.3
Automatic Synchronization of Assigned Incidents and
Messages (196277)
In the event of a wireless network disconnect between PremierOne Mobile and PremierOne CAD in the
Cloud, the assigned Incidents and Messages now synchronize automatically.
12.3.4
Tracking Units in Emergency Mode (15283)
The units that receive the Emergency Notification message now have access to the Track It button in the
Mobile Map or Classic Map. Operators can use this button to track the location of the Emergency Unit in
near-real time.
Figure 213: Unit in Emergency Message
NOTE: Where:
● SC/MUNIT2 = Agency ID /Unit ID
● MDT - SC/DEV2 = Agency ID / Device ID
● SC/User2 = Agency ID / User ID followed by the Last Name, First Name
211
MN008865A01-AF
Figure 214: Track Menu Option
12.3.5
GPS Improvements (111106)
IMPORTANT:
New settings have been added to the Mobile Client Configuration Tool in 4.6.3 to control the
Data Sources and mitigate Stationary Drift.
Before running the Mobile Client Configuration Tool, please review GPS Settings on page 212.
12.3.5.1
GPS Settings
Review the new settings in the the Mobile Client Configuration Tool.
1. In the Mobile Client Configuration Tool, select Mode Selection.
212
MN008865A01-AF
2. In the Mode Selection screen, select the IsUpdateGpsDeviceConfigure checkbox to dictate whether the
values specified in the tab will overwrite the current GPS configuration. If the option is unchecked, the
DeviceConfigure.xml file will not be modified.
Figure 215: Mode Selection
3. In the Gather Information screen, select the GPSDevice tab.
213
MN008865A01-AF
4. In the DataSource list , select the type of interface used to access GPS data.
● Serial: See Table 5: Serial Settings on page 216 and Table 7: Common Settings for Serial or Ethernet
on page 217.
● Ethernet: See Table 6: Ethernet Settings on page 217 and Table 7: Common Settings for Serial or
Ethernet on page 217.
● Location Services: See Table 8: Location Services Settings on page 217.
214
MN008865A01-AF
5. In the StationaryWhenMPHLessThan field, enter the specified value (in MPH). Designates the position
as stationary when the speed is less than the specified value (in MPH). The default is 1.5.
215
MN008865A01-AF
6. In the MinimumSatellitesRequired field, enter the minimum number of satellites to consider the GPS
data as valid. The default value is 5.
Table 5: Serial Settings
Serial Settings When DataSource is Serial

COMPortId Enter the COM port ID
BaudRate Enter the baud rate
Parity Enter the parity
StopBits Enter the stop bits
HandshakeMode Enabling HandshakeMode enables the hardware flow control for the
GPS serial communication. This allows the Mobile Client to continuously
stream GPS data.
PremierOne Mobile may be unable to continuously read GPS data from
a virtualized COM port. Enabling this setting resolves this issue.
If disabled, there is no flow control for the serial communication with
GPS.
216
MN008865A01-AF
Serial Settings When DataSource is Serial

UseNativeInterface If the GPS device is connected to the laptop or docking station via a
USB port, set to true. Otherwise, set to false.
DefaultToThisDevice To maintain serial port GPS settings in a deployment package, set this
field to true and populate the appropriate COM port values in the fields
that follow. When set to true, at each Mobile session startup, the COM
port settings for the device are scanned first.
If set to false, the last known good COM settings are scanned first, and
those settings are stored in a non-configuration XML file where they will
not be overwritten by a new upgrade/deployment package.
NOTE: Auto-detection of GPS devices only applies to mobile
deployments using Serial or UDP (Virtual COM) GPS devices
and are therefore only enabled when the DataSource=Serial.
AutoDetectSerialGPS If set to true, the Mobile client automatically scans available COM ports
to detect valid GPS feeds.
If set to false, the Mobile client uses only the COM port specified in the
ComPort Id setting
Table 6: Ethernet Settings
Ethernet Settings When DataSource is Ethernet

LocalIP Enter the local IP address.
LocalPort Enter the local port address.
ModemIP Enter the IP address of the modem.
ModemPort Enter the local port for the modem.
NetworkProtocol Select the network protocol, such as TCP.
Table 7: Common Settings for Serial or Ethernet
Common Settings When DataSource is Serial or Ethernet

DeviceMessageProtocol Select the message protocol, such as NMEA.
NMEAPacket Select the packet for NMEA GPS device. This allows a NMEA GPS
device to be configured to send specific messages (not all NMEA
GPS devices that are supported can be configured in this manner).
TAIPPacket Select the packet for TAIP GPS device. This allows a TAIP GPS
device to be configured to send specific messages (not all TAIP GPS
devices that are supported can be configured in this manner).
DeviceInitString Enter the initialization string for the device.
MinimumSatellitesRequired Enter the minimum number of satellites needed to constitute valid
GPS data. The value is an integer in the range between 0 and 14.
Table 8: Location Services Settings
Location Services Settings When DataSource is Location Services

LocationServicesPolicy Enter the Windows Location Source policy:
217
MN008865A01-AF
Location Services Settings When DataSource is Location Services

Satellite Only
Satellite or WiFi
Any
AccurateToWithinMeters Enter a value that designates the maximum accuracy distance radius
(in meters) for a location. For example, a value of 40 designates that
every GPS position received must be accurate to within 40 meters. If
it is not, the GPS position will be rejected and not used for mapping
applications or sent to CAD.
12.3.5.2
Enhanced Windows Location Services Support (101735)
Provides a straight-forward method for configuring sensor-based GPS devices to use Windows Location
Services, and expands the GPS status indicator to identify the Windows Location Services’ status.
● Administrators can now specify which data sources are allowed (Serial, Ethernet, or Location Services).
● When using Location Services, the mode can be Satellite Only, Satellite or WiFi or Any.
● The GPS Status Indicator will now identify special situations that are applicable to Windows Location
Services, such as when Location Services are disabled.
12.3.5.3
GPS Precision Improvements
New configuration settings allow Administrators to adjust GPS parameters to improve location accuracy.
Stationary position drift can be mitigated by:
● Designating the position as “stationary” when the speed is less than the specified value (in MPH).
● Defining the minimum number of satellites required to consider the GPS data as valid.
12.3.6
Mobile Map Changes
The following new Mobile Map features are included in this release.
● New parameter for limiting map rotation on unit heading changes MobileMapLimitRotation in
MappingConfig_Production.xml
● Ability to Zoom to Geofences (see figure below)
● Ability to Zoom to Extent
● Ability to Stop Route Recalculation when unit has Arrived (see figure below)
● Improved Road Closure Creation Controls
● Improved Route Auto-Zoom Functionality
● New controls for Route Display Modes (Entire Route, Remaining Route, Auto-Zoom, Center Unit )
● Mobile Map now closes gracefully when the connection to the Mobile Client is lost
218
MN008865A01-AF
Figure 216: Zoom to Geofences
You can restart the route recalculation using the following controls:
Figure 217: New Route Display Modes Control
Where:
219
MN008865A01-AF
12.4
for reference.
12.4.1
Support Period (.) in the User Name Field for CAD/
Mobile Sign On (175019)
Users can now include periods (.) in the User Name field during the sign in process.
12.4.2
Support Period (.) in the User Name Field for CAD/
Mobile Sign On (175019)
Users can now include periods (.) in the User Name field during the sign in process.
220
MN008865A01-AF
Chapter 13

4.6.2
NOTE: Following with previous releases, some features require additional configuration by your
Motorola Solutions support to be enabled in your agency's system.
13.1
Issues Resolved
● In CAD, an error appeared when submitting Unit Summary form. (193490)
● When creating an incident in CAD, the changes were not reflected upon pressing the F12 button.
(176554)
● In CAD, users were unable to import Personnel into Provisioning. (147647)
● In CAD, Index being out of range resulted in an error. (160515)
● Processing large messages in CAD caused the system to shut down. (151815)
● LRT no longer causes APP servers to reboot every 1 to 2 hours. (150561)
● In CAD, an application exception error occurred upon requesting recommendations and clicking the
RespList button. (180009)
● In Provisioning, the default certificates that were added to the deployment config file were deleted upon
the upgrade of the Staging system. (99697)
● The Universal Mapping mobile application crashed frequently. (112543)
● In CAD, the Person tab info disappeared after the user submitted the form by pressing the F12 button.
(112747)
● In CAD, users were unable to dispatch Mutual Aid and pop-up messages appeared, incorrectly stating
that the request has been updated. (152694)
● In Provisioning, users experienced an while trying to change the Dispatcher role for Agency 13COMM.
(116123)
● In CAD, users were unable to close incidents due to an error. (151858)
● Following the latest update, the CAD client occasionally slowed down and became unresponsive.
(159147)
● CAD Application Logs generated frequent errors. (112713)
● Responder Alert pop-up messages in CAD were delayed. (147904)
● In CAD, alarm records settings could not be saved due to an error. (148806)
● In CAD, an application exception error occurred after clicking the View button in Messages form while
adding attachments. (148049)
221
MN008865A01-AF
● Installing P1 CAD on a clean Windows 10 machine was not giving correct folder permissions which
caused repeated Status Monitor Update pop-up warnings when signing on to the CAD client. (150706)
● PremierOne services were repeatedly crashing during the cloud staging update. (145990)
● In Provisioning, adding Alarm record could cause an error. (144675)
● In CAD, large numbers of records slowed down the queue performance during protests. (75963)
13.2
reference.
13.2.1
Road Closures in Mobile Map (102207)
● You can now create, edit, and delete road closures in Mobile Map for Windows and distribute them to
CAD and other Mobile Clients.
● The effective dates can also be customized and multiple barriers can be added to ensure all needed
segments are closed.
● For more details, see PremierOne Mobile Windows User Guide 4.6.2.
13.2.2
GeoFences in Mobile Map (102208)
● You can now create, edit, and delete GeoFences in the Mobile Map for Windows to send notification
alerts when mobile units enter or exit the outline of the geographical area that has special significance.
GeoFences can be defined to appear in different colors and shapes.
● For more details, see PremierOne Mobile Windows User Guide 4.6.2.
13.2.3
Support for URLs in Incident Comments and Messages
(79567)
● Starting in version 4.6.2, PremierOne Mobile for Windows will recognize URLs as hyperlinks in incident
Comments and Messages.
● When a URL is "clicked" the client will open the link within the application, or in the computer's default
browser. This can be configured as a user's preference.
13.2.4
Deployment Improvements for iOS
● Simplified configuration with file distribution by QR codes in iOS (originally implemented for Android).
● Enhanced MDM (Mobile Device Management) support in iOS (originally implemented for Android).
222
MN008865A01-AF
13.3
reference.
13.3.1
Performance Improvement Initiatives 57047
In our continuing efforts to improve performance, we are initially disabling services that monitor the system for
activities that may not be related to the PremierOne customer environment. One such service monitors the
system for Bulk Unit Status Update messages from the CAD-to-CAD interface. This service will be disabled
by default starting in 4.6.2. To enable this service for customers using Bulk Unit Status Updates, upgrade
the first Application Server to 4.6.2. Additionally, before starting services on this server, perform the following
steps:
Procedure:
1. Log onto the PremierOne Admin Console with permissions to modify PremierOne Configuration
settings.
2. Select the Configuration icon.
3. Select the Edit tab.
4. Navigate to: QueueConfiguration → CtcBulkUnitStatusUpdateQueue_CTC.
5. Change the <ThreadCount> value to 1.
6. Save the change.
Restart the services on this Application Server when ready. Then, perform the upgrade on the
remaining Application Servers which will pick up the above configuration change upon their restart.
13.3.2
Process PURVIS Acknowledgement Messages to
Update the Units Status (145117)
PURVIS Acknowledgement messages can now be accepted to place a unit in the agency’s default Dispatch
to a Non Mobile-Equipped Unit status into the default Dispatch Acknowledgement status. Only units within
the message that were in a status provisioned as In Station prior to being dispatched will be updated to the
Dispatch Acknowledgement status. The status of all other units within the message will remain unchanged.
A PURVIS CAD-to-CAD external system must be provisioned and the local agencies accepting PURVIS
Acknowledgement messages must be provisioned to receive and apply Unit Status Updates for this system.
13.3.3
ASAP2PSAP Interface (145111)
The provisioning of the ASAP2PSAP interface is fully supported in 4.6.2.
PremierOne processes an ASAP Alarm message through the Detailed Call for Service Transfer option. In
order for PremierOne to differentiate an ASAP Alarm message from an actual Detailed Call for Service, a new
Interface drop-down selection has been added to the Interface → External System → System Identification →
General.
● When provisioning a system to be used with the ASAP2PSAP Interface, select Interface = Asap Alarms.
223
MN008865A01-AF
● When provisioning a system to be used with the CAD-to-CAD Interface, select Interface = CAD-toCAD.
When upgrading to 4.6.2, this will be the default setting for all existing External Systems. Since the
ASAP2PSAP interface option was unavailable prior to 4.6.2, this value should not have to be modified for
existing External Systems.
13.3.4
[CAD-to-CAD] Foreign-to-Foreign Call for Service
Monitoring (145112)
PremierOne’s CAD-to-CAD functionality has been expanded to allow a PremierOne CAD operator to monitor
the activities of Foreign Agency units that are assigned to an incident that was submitted to them as a Call for
Service Request. By enabling the Foreign Agency to receive Unit Status Updates, PremierOne will allow you
to follow the progress of the Foreign Agency units through their unit status activities.
For example, if a private ambulance company is provisioned as a Foreign Agency that receives Call for
Service Requests from PremierOne, provisioning that agency to receive unit status updates will allow the
private ambulance system to send unit status update messages to monitor the progress of an ambulance
assigned to the Call for Service Request.
13.3.5
CAD-to-CAD Improvement Initiatives (150929)
As PremierOne continues to expand processing CAD-to-CAD Interface messages for external systems that
can either be managing foreign agencies (those not managed within PremierOne) or acting as an extension
to local agency within PremierOne (such as LiveMUM and PURVIS), we need to understand which of these
types of systems is communicating with us so we can act against incidents and/or units accordingly.
Therefore, a new System Type drop-down selection has been added to the Interface → External System →
System Identification → General.
● When provisioning a system to be used with the ASAP2PSAP interface, select Interface = ASAP Alarms.
System Type will be set to: Foreign System.
The Local Extension option will not be available within the drop-down for ASAP Alarms
● When provisioning a system to be used with the CAD-to-CAD Interface, select Interface = CAD-toCAD,
and then select whether the system is a Foreign System or Local Extension.
IMPORTANT: When upgrading to 4.6.2, the default setting for External Systems will be Foreign
System. If the External System is a Local Extension to local agencies on your system, please
update this value accordingly.
13.3.6
Response Card Provisioning: Run Card Cutoff (145120)
A new Run Card Cutoff option has been added to the Response Card provisioning pages for Incident
Response Factors and Response IDs.
This setting allows the response to truncate the respective Run Card to the specified value in its attempt to
recommend a unit for Fixed Recommendations, or when insufficient units can be recommended for Preferred
Recommendations.
For example, if the Run Card Cutoff value was set to five (5) for a Capability, and the respective Run Card
contained thirty Run Card Order elements, Unit Recommendations would only search the first five Run Card
Order elements for the specified Capability before stopping.
When the Run Card Cutoff is set to zero (0), the entire Run Card Order will be utilized when performing Unit
Recommendations. This will be the default value upon upgrading to 4.6.2.
224
MN008865A01-AF
13.4
ProQA Interface Updates
The following ProQA features were added to this release.
● The system administrator now has the ability to have the ProQA case number be written into the CAD
incident documents. (15730)
● • The system administrator now has the ability to have the information from the Police and Fire CBRN/
EIDS/COVID tools be written into the CAD incident comments. (142507)
● • For Police, the system administrator now has the ability to have Bicycle and Aircraft information written
into the CAD incident comments. For vehicles, the VIN field from ProQA was mapped into the CAD's VIN
field.
For Fire, the two new tags of Direction of Travel (DOT) and Cargo Type are now passed with Fireboat
and Watercraft in Distress. The system administrator now has the ability to have Clothing Info, Equipment
Info, Outdoor Experience, and Lost Person information written into the CAD incident comments. (142512)
13.4.1
Provisioned Non-Tandem Transfer Types (135957)
Before this feature was implemented, there were two Intelligent Transfer Types: Non-Tandem (for
NonEmergency calls) and Tandem (for Emergency calls). This feature adds two additional Transfer Types, so
we can have the following Intelligent Transfer Types:
● Non-Tandem Transfer
● Tandem Transfer
● Standard Conference
● Blind Transfer
Additionally, all four transfer types can now be Emergency or Non-Emergency.
The Non-Tandem call is equivalent to the No Hold conference.
The setup of this feature can be done in the Provisioning, under: Call Control → Intelligent Transfer →
Service Provider.
In the CAD Client, in the Call Control window, the Intelligent Transfer selection will be based on the incoming
Call Type (Emergency or Non-Emergency), as configured in the Provisioning.
13.4.2
VESTA Context Number Processing (126715)
This feature has been implemented to support the VESTA pre-processing functionality. There are two steps -
apply callback configuration and apply context. Callback configuration is related to the area codes and can be
set in the DDS. To specify the area codes configuration in the Provisioning Console, use the plus character
and brackets.
Context is for additional prefix and postfix for routing dial to the proper gateway. In the Provisioning Console,
apply the VESTA context name. Each of them can be configured in the VESTA console.
225
MN008865A01-AF
13.4.3
Configurable Button Display Based on Role Selection
(140819)
Before this feature was implemented, the Call Control Module displayed buttons based on the line groups
that were configured in VESTA. This feature allows to configure (in DDS) the lines attached to specific roles.
That allows to specify which lines can be used by which users.
Users can change the Button profile within chosen role in Call Control Window: Call Control → Console →
Change Button Profile.
13.4.4
SMS Transfer (78939)
VESTA allows classic (non-MSRP) SMS transfer functionality using URIs. When a VESTA system is properly
configured, (SMS feature enabled, Role configured with the appropriate permissions), ICC will automatically
display an Intelligent Transfer button (not provisioned in P1 CAD backend) to allow for SMS transfer
capability.
The default name of the button (SMS XFER) can be changed like other internationalized strings for UI
elements.
There are no default dial numbers for this button. The user can left-click to show additional providers and a
list of all Transfer Queues configured for a given role. Left-clicking the button will transfer the SMS to that
queue. Right-click on the additional providers to show details.
13.5
for reference.
Name Check Updates

● Publisher Name Check was added to Deployment Mobile Agent on Cloud. (155960)
● Common Name Check was removed from AIO Installer. (155959)
For more details, see PremierOne All-In-One Installer User Guide Version 4.6.2
226
MN008865A01-AF
Chapter 14

4.6.1
NOTE: Following with previous releases, some features require additional configuration by your
Motorola Solutions support to be enabled in your agency's system.
14.1
Issues Resolved
● (CallWorks Integration) Mapping freeze (124734)
● P1CAD - Failed to update the incident error when updating existing person in Incident Management form
(112190)
● P1CAD- Units cannot see incidents on their MDT’s and cannot see unit statuses.
(procselectupdatesformobiledatacache taking more than 15 secs) (73875)
● P1CAD - Slowness and error upon dispatch. (112477)
● P1 CAD - System down and site on cards due to large message being processed (112480)
● Unable to deploy CAD DAU and CAD Uninstall Package - Package gets stuck in Waiting To Install state
forever (113397)
● MAP - Mobile Map crashed upon trying to create a road closure (141172)
● P1CAD - (Outage) LRTs, High CPU usage on APPs - Consoles freezing for up to 30 seconds (114586)
● P1CAD Long Initial Sync Times for Clients on 4.4 clients because of a large amount of IRF (112513)
● P1MOB - Mobile Clients Not Receiving Updates When Multiple Are Dispatched To Same Incident
(127346)
● P1CAD - CAD client freezing when printing mail message from print preview (112548)
● P1CAD - Personnel Delete Errors (112568)
● P1CAD - Personnel Import Errors (112569)
● P1 MOBILE - MDTs are not receiving updates (132369)
● P1 CAD - CAD Client freezes when using map (106888)
● P1CAD - Received "Error occurred changing role DISPATCHER in agency 13COMM" in provisioning
(148243)
● Red X on Provisioning Console Accessing IRF - Object reference not set to an instance of an object.
(30268)
● P1CAD - AIO P1CAD error when downloading installation packages 45Cu3a (106999)
227
MN008865A01-AF
● P1MOB - Address book locks up when selecting group "All Units" - Display Message when too much data
(112630) • P1CAD - 4.5.3d contains upgrade script that fails with SQL Server Standard Edition (142699) •
P1Mobile - Incident History screen does not load data (111137)
● CAD Slowness When Entering Calls - Console Goes Offline - E911_ALI table Index (108781)
● P1CAD - Application Exception Error on CAD07 on Unit Assignment (137007)
● P1MOB - Mobile Users Unable to Change Status After Self Clearing an Incident (128053)
● Responder Alert CAD pop-up alerts are Delayed (114614)
● 4.6 CAD client - Exception immediately upon login (118836)
● Application Exception Error after clicking button View in Messages form for Attachment (146889)
● CAD Client froze after do some operations on query responses (56060)
● CAD Client Hangs at Logout Confirmation Form (114437)
● Job User Deployment fails with the error "There is already an open DataReader..." (106748)
● User is not able to close incident when Mapping is disabled (124205)
● VA CADC - Config Tool throws an exception when CADSystemUser does not exists in key vault (107243)
PremierOne Mobile for iOS & Android

● iOS 14 is now supported.
● The Android and iOS client applications close upon a user logoff so the user does not have to do a force
stop on Android or manual close on iOS. (Android or iOS devices are not typically shared so when an
officer logged off at the end of the shift it took extra steps to close the applications.)
PremierOne Cloud Suite Integration (List of Record Integrations Supported)

This release of PremierOne Cloud CAD enables PremierOne Cloud Suite capabilities with the following
integrated workflows:
● PremierOne Cloud CAD Agency and User provisioning data is synchronized with PremierOne Cloud
Records through the cloud provisioning service.
● PremierOne Cloud CAD Call For Service (CFS) records are automatically shared with PremierOne Cloud
Records when provisioned for Suite workflows.
● PremierOne Cloud CAD will generate a sequential Report Number and provide to PremierOne Records
upon request.
While based on a common code line, there are several PremierOne CAD functions that are not available in
PremierOne Cloud CAD, including:
● File attachments from the local user workstation are not available with Cloud CAD
● Network printer access is not available with Cloud CAD (local printer access is available)
● The Cloud CAD client is not customizable
● There is no online help in the current Cloud CAD client
● Error report upload uses a separate virtual app instead of executing from the client help menu
● Customers do not have direct access to the GIS databases; GIS & map updates from the customer are
provided to Motorola Solutions to be uploaded to the Cloud CAD environment
Support for State Query and Everbridge Interfaces

State Query interfaces
Enable State Query Transactions from PremierOne Cloud CAD. Where an on-premise point of contact is
required, a VPN will be used to create a secure network connection to an on-premise server, referred to
228
MN008865A01-AF
as the Anchor Server, to provide the local point of connection to the state. The PremierOne Query Service
is used to securely manage the queries and returns in the PremierOne Cloud CAD environment.
Everbridge Interfaces
Enable integration with a customer’s Everbridge notification service to send CAD incident and dispatch
updates through Everbridge. The Everbridge service is a customer provided service independent from
PremierOne CAD that is used to provide notifications via user definable methods (SMS, pager, and so on)
to specific agency users.
Virtual Client Non-Disruptive Upgrades

Enable PremierOne software incremental version updates to be made to the PremierOne Cloud CAD client
while a virtual client session is in use. The new PremierOne client version would be used the next time a
virtual client session is initiated.
229
MN008865A01-AF
Chapter 15

4.6.0
15.1
Issues Resolved
● P1 Mobile client browser does not launch initially, need to click on Home/Refresh buttons to launch
(62461)
● CAD Query- Object Reference not set to an instance of an object appears. (76474)
● P1 CAD - CAD Client randomly shutdown for Device ID: NRCADN1 (77263)
● SCOM - False Alert on Stop SQL Jobs rule (80952)
● P1Common services - Personnel Provisioning Interface Does Not Set Hire Date & Termination Date
(84220)
● P1 CAD - When exporting personnel, logged in users are not accounted for (84845)
● P1 CAD Error occurring while updating the alarm level of a call (84848)
● Reporting does not work with Default Certificates due to missing root certificate (85812)
● Inner Exception Report Number created time must have a value (89471)
● PhysicalWorkstationId cannot be changed during Mobile Client installation (89883)
● CAD with Call Control - CAD client crashed (93661)
● CAD - Unhandled exception PSWGS.GIS.CadMapping.MappingMainForm displays when after Map loads
(97160)
● System.NullReferenceException: Object reference not set to an instance of an object. at
PSWGS.GIS.CadMapping.MappingMainForm (97377)
● P1 CAD - Console gets "An unexpected error has occurred in the application" error (97566)
● P1 CAD - Cannot authenticate via AD (99695)
● RDW SSIS Feed Outage - change tracking version exceeds INT32 (100140)
● Mobile: Mobile Client froze (Not Responding) Upon Clicking My Active Incident Function Key (103778)
● CAD: System Monitor Update Warning window pop up appeared on the CAD client (103813)
● Closing the CAD Client login form by clicking 'X' on top right corner leaves the CAD Client process
(106705)
● Mobile Client Process Suddenly Disappeared upon clicking on the Mobile Client Commandline and could
not log in again due to Current User Has Been Locked (106753)
● P1CAD - AIO P1CAD error when downloading installation packages 45Cu3a (107000)
230
MN008865A01-AF
● P1CAD - Failed to update incident error when updating existing person in Incident Management form
(112140)
Android
● Create incident button occasionally remaining disabled
● Incorrectly assigning the default area when creating an incident
● A crash occurring when clicking the map when it was unavailable
● Comment word wrapping
iOS
● Incident priority being set incorrectly without a modifying circumstance
● An issue with the app unexpectedly locking
● An issue preventing update of client or server port settings on iOS 13.
● Sorting order of pick list items throughout the app.
● Removed duplicate entries in Unit Monitor.
15.2
The following CAD features are included in this release. The Azure DevOps number is included for reference.
15.2.1
Create Associated Incidents for Call for Service (CFS)
Requests (80359)
Whenever a CAD-to-CAD Call for Service Request is received by PremierOne, it will attempt to create an
incident based on the information contained within the Call for Service Request along with the associated
incidents provisioned against the Incident Response Factor (IRF) used in creating this incident. PremierOne
will only create associated incidents for agencies provisioned as Local Agencies. PremierOne will not create
any associated incidents for Foreign Agencies. It will be the responsibility of the sender of the Call for Service
Request to contact the other external systems from which assistance is needed.
15.2.2
Phone Number Query
Smart911 will push info to us (CSI probably) whenever a 911 call is answered. This info is called a ticket. We
need to associate a URL with the incident so a user (either at the time of the call, or later) can click on that
URL which will launch a window to retrieve that info.
During the call taking process, the user would accept the ANI/ALI information into the II form. At that point,
a query needs to be sent with the phone number. When this query goes to CSI, it would retrieve the ticket
associated with the phone number and return a query response to the client containing the URL. This query
response would then be tied to the incident.
231
MN008865A01-AF
15.3
reference.
15.3.1
Customer-Specific Certificates (55153)
Starting with PremierOne version 4.6, agencies can apply their own (customer-specific) SSL certificates
instead of default certificates provided by Motorola Solutions.
An SSL certificate can be purchased by each agency from a third-party Certificate Authority (CA) and must
be renewed prior to the certificate’s expiration.
If the SSL Certificate is issued by a commercial certificate authority, then certificates on the client devices are
not needed.
However, if an agency prefers to issue their own SSL certificates, a Root certificate must also be installed on
each Client device, so that the Chain of Trust validation can take place.
To configure an SSL certificate on the PremierOne Server, contact your Motorola Solutions Support
Representative.
To allow a gradual fleet upgrade, “mixed mode” is supported in PremierOne 4.6.0 and higher, so that newer
devices configured to use a customer-specific certificate as well as existing devices using the legacy default
certificate can coexist.
To configure an SSL certificate on the PremierOne Server, contact your Motorola Solutions Support
Representative.
For details on configuring an SSL certificate on the PremierOne Mobile Client, see the PremierOne Mobile
Client Installation Guide.
15.3.2
Mobile on REST (MoR) (15025) (79570)
Starting with PremierOne version 4.6, PremierOne Mobile clients can communicate with a PremierOne server
via HTTPS.
PremierOne’s WCF transactions are wrapped inside REST packages and transmitted securely over the air
via HTTPS. A Mobile Server Proxy (MSP) acts as an interface between Mobile Clients and the Mobile Server.
Mobile on REST can be used in these three cases:
● Communications with a PremierOne CAD system On-Premise.
● Communications with a PremierOne CAD system in Azure Cloud.
● Communications with PremierOne CAD systems (On-Premise or Azure Cloud) in Disaster Recovery as a
Service (DRaaS) mode.
SSL Certificate Validation for MoR (46781) (55519)

To ensure secure communications, a Certificate is attached to the responses from the F5 Load Balancer,
which is validated in the following ways:
● The certificate must verify Chain of Trust to a root certificate
● The certificate must not be expired or future-dated
● The request hostname must match
232
MN008865A01-AF
Deployment on MoR
Client deployment when using Mobile on REST features two major components:
● Mobile Deployment Service Proxy (MDSP)
The MDSP provides a REST interface to the PremierOne CAD Deployment Service (CADDS). And
imposes an authorization boundary between backend CADDS and the public Internet.
● Mobile Deployment Agent (MDA)
The MDA is an optional software module, which is deployed as a Windows service on Mobile clients. The
MDA historically ran over WCF (On premise configuration), but now can communicate over HTTPS with
the MDSP for Mobile on REST and Cloud configurations.
With the MDA, a Mobile Deployment Agent Notifier (MDAN) is deployed to the Mobile clients. Its main
function is to provide a UI that allows the end user to take deployment and provisioning actions. MDAN is
designed as a Windows desktop application (.NET and WPF).
15.3.3
Disaster Recovery Server Selection from Mobile (46828)
This feature allows users of PremierOneMobile clients communicating via REST to alternate between two
servers, when a Disaster Recovery situation occurs and one system takes over the other. This scenario is
known as Disaster Recovery as a Service (DRaaS), since the DR system is expected to operate in the Cloud.
The Mobile client can now support choosing one connection over another. This switch takes the form of a
simple toggle (Connect To list) in the login form.
Disaster Recovery as a Service (DRaaS)

Mobile on REST can be used on Disaster Recovery configurations. PremierOne Mobile 4.5.3 introduced the
ability to alternate between two servers, when a Disaster Recovery failover situation occurs and one system
takes over the other. When the system is configured to operate in Disaster Recovery as a Service (DRaaS)
mode, the backup system operates in the Cloud.
233
MN008865A01-AF
Figure 218: Simple Login Window
If the Mobile client is provisioned to communicate with a DRaaS server, the Mobile user can initiate the switch
between the servers in the middle of a session. Switching servers force-restarts the Mobile client application,
but keeps the unit on duty in CAD. If this is not desired, use the Logout button, as long as the CAD system is
still online to react to the request.
To switch to another server while logged in:
1. On the Status bar, select the Logged In button.
A list of options displays.
2. Select More and then select Change Server.
234
MN008865A01-AF
Figure 219: Change Server Button
This forces the Mobile client to restart.

The Login screen appears.
Figure 220: Simple Login Screen
235
MN008865A01-AF
3. Log into the Mobile client and select the Secondary server in the Connect To field.
4. When you have entered your login information, select the Login button at the bottom of the window, or
press Enter.
The System log out screen appears.
Figure 221: System Logout Screen
5. Select OK and when the Successful Login screen appears select OK.
This feature is enabled through the Configuration Tool and provisioning changes. For further details, see the
PremierOne Client Mobile Installation Guide and the PremierOne CAD/Mobile Provisioning User Guide.
15.3.4
Mobile Map Activate Smart Status (15276)
Prior to PremierOne 4.6.0, Unit Status could be changed by either clicking on a provisioned Mobile Client
function key, or by using the Status drop-down menu, or by having a dispatcher change the unit status in a
CAD Client. Starting with 4.6.0, if a Unit Status record has been provisioned to include a “NextStatus” value,
that NextStatus value will be displayed on the NextStatus button in the upper-right corner of Mobile Map.
When clicking on that Mobile Map NextStatus button, the Unit Status will be changed in the Mobile Client
and reflected back into the CAD server. If any popup messages have been provisioned for the NextStatus on
Mobile Map, the popup message will appear on the Mobile Client.
Figure 222: Active Incident Window
236
MN008865A01-AF
15.3.5
Mobile Map Locate, Zoom, and Center on Mobile Map
(15281)
Prior to 4.6.0, when selecting a Mobile map button (Universal map) in the Mobile Client, the Mobile Map
would be brought to the front, but would not zoom-in and center on the unit or incident. Starting with
4.6.0, when a “Locate on Mobile Map” button is provisioned on a given Mobile Client form with Mobile Map
UI Customization, when a Mobile Map button is clicked, the Mobile Map will Center on the Incident/Unit/
Location and Zoom to the provisioned zoom scale.
15.3.6
Display First and Last Name of Crew Members within
Unit Details (15287)
This feature allows to display the First and Last name of each additional crew member on the Mobile Unit
Details form. (Previously, only the User ID and Radio ID was displayed).
● The Name is now displayed in a new column inside the additional crew group box on the Unit Info Detail
screen.
● The Last name followed by a comma, then the first initial character of the First Name is shown (e.g.
"Adams, M”).
15.3.7
Update Map Labels to Classic and Mobile Map (70818)
Within the Mobile Client, the buttons referring to the Universal map are now labeled as “Mobile Map”. The
legacy map is now labeled as the “Classic Map”.
This feature changes the display UI Customization for Function Keys, Action Bar and Options Menu. “Locate
on Map” labels were changed to “Locate on Classic Map”. “Locate on Universal Map” labels were changed to
“Locate on Mobile Map”.
Figure 223: Incident Summary Window
237
MN008865A01-AF
15.3.8
Remove the On-Screen Keyboard Checkbox (81399)
In Windows 7, the Mobile Client needed an On-screen keyboard checkbox when using tablets. This has been
removed now that Windows 7 is no longer supported.
This change removes the “Enable Onscreen Keyboard” checkbox used to enable on screen keyboard.
238
MN008865A01-AF
Chapter 16: Hardware and Software Requirements
Chapter 16
Hardware and Software Requirements

The following sections describe the client hardware and software requirements.
Windows Server Support Tools are needed on the server.
Starting with the 4.6.12 release, PremierOne supports platform versions 2016/17 and 2019. Version 2019 is
recommended for fresh deployments. It is recommended to use only the 2016/17 MS tech stack OR the 2019
MS tech stack. A combination of 2016/17 and 2019 is not supported and may cause errors in operation. At
the time of release, in place upgrades of operating system, database, and system center to 2019 are not
supported and will be done at your own risk.
NOTE: These requirements assume no other software is being run on the workstations. If you are
running additional software at the same time, you need additional RAM and/or processing power.
PremierOne CAD Workstation Specifications

● 3.5 Ghz Processor Intel® Xeon® E5-1620 v4 or similar
● 16 GB+ memory
○ Although not needed for the PremierOne client, inclusion of additional memory (example, 16GB) in
new workstation purchases is common for future capacity.
● 20 GB available disk space; solid state drive (SSD) required for optimal performance
● 100 Mbit or faster (Gigabit recommended) Ethernet network adapter
○ Note that network latency will impact system performance.
● At least one 1024 x 768+ pixel, 16+ bit color display
CAD status monitor windows and maps are resizable, but to ensure consistent user experience the CAD
client workbench window has a fixed dimension of either 1024 x 768 or 1280 x 1024.
○ Three monitors is typical for a CAD position; specific monitor size, quantity, and configuration varies
by agency.
○ The CAD client workbench window has a fixed dimension of either 1024 x 768 or 1280 x 1024. The
Call Control window is resizable with a minimum size of 980x685.
NOTE: Scaling of the CAD display more than 100% is not supported.
CAUTION: In Windows 10, you can increase the font for outside applications to greater than
100%. Increasing the font to greater than 100% will distort the CAD and Mobile displays.
● QWERTY keyboard with 12 function keys
● Microsoft Windows 11 Professional (64-bit recommended) or Microsoft Windows 10 Professional (64-bit
recommended)
NOTE: Workstations used to create provisioning import/export files must run on Windows 10 or
Windows 11 and be able to natively create and edit Excel 2007/2010 .xlsx files.
● Graphics adapter with at least 512MB RAM per monitor, 24-bit capable graphics accelerator, OpenGL
v2.0 runtime or higher. Latest available drivers. Shader Model 3.0 or higher is recommended.
● .NET Framework 4.8 and above
● ArcGIS Engine 10.8.1 (included with PremierOne CAD client software)
● SQL Server Express 2017 or SQL Server Express 2019. CU level supporting TLS 1.2 is required.
239
MN008865A01-AF
● Software Prerequisites for PremierOne Server - Microsoft Access Database Engine 2016 Redistributable
32 bit.
● Software Prerequisites for PremierOne CAD Client - Visual C++ Redistributable Packages 2013 64 bit
NOTE: Workstation specifications are representative of workstations used in the testing of the latest
release of PremierOne software and do not take into account any other applications. Future releases of
PremierOne may dictate changes to the workstation specifications. Each agency should consider their
own technology replacement lifecycles and policies for specific purchase decisions.
Future versions of PremierOne will no longer support 32-bit client architecture or pre-2017 versions of
SQL Server Express.
Supported PremierOne Mobile Android/iOS Operating Systems Versions

Following are the supported operating systems for PremierOne Mobile for Android and iOS.
● Android 10–12
● iOS 13–16
Recommended Hardware Specifications for PremierOne Mobile Windows Client

Modern “business grade” or "ruggedized" Windows notebook.
● Windows 10 & 11 Professional
● Multi-core processor (i5 or higher, 4-thread, 2.6 Ghz +), Intel® Core™ or newer Intel® Series
● 8 GB + RAM (4 GB must be available for PremierOne Mobile)
● 20 GB + available disk space; SSD (Solid State Drive) recommended
● 1024x768 resolution display (minimum)
● Graphics accelerations handled by either processor integrated graphics or discrete graphics card if CPU
integrated graphic processing is not available
● Broadband Connectivity - 4G LTE or 5G recommended
● Touchscreen (optional)
NOTE: Agencies that have PremierOne Mobile running on legacy or non-expandable computers must
validate that the new software is able to run in a reliable and well-performing state. Support cases may
be closed if the cause can be attributed to insufficient resources or underpowered hardware.
Recommended Hardware Specifications for PremierOne Mobile CAD and Records

Mobile Workstation
Table 9: PremierOne Records Mobile Recommended Specifications
Component Description
Processor Intel i5, i7 2.6 GHz dual core processor
RAM Memory 16 GB memory Minimum
Available Disk Space 20 GB available disk space
Operating System Windows 10 & 11 Professional 64-bit
Display One (1) 1024 x 768+ pixel, 16+ bit color display,
11.6" or larger display. Usage on devices with alter-
native resolutions and smaller screens should be
tested and screen settings optimzed. Example: On
240
MN008865A01-AF
Component Description
a 10.1" WUXGA screen, use a resolution of 1280 x
800 and a front size of 125%
Keyboard-Mouse Standard QWERTY keyboard and Touchpad / point
stick (or equivalent mouse device) Touchscreen
Optional
Graphics Adapter The computer should have an integrated graphics
processor available with drivers for Windows 10
operating system. If not available, please ensure
the computer is equipped with a discrete graphics
processor.
Network Adapter Cellular network interface card with 4G LTE or
5G capabilities approved by carrier, wireless "WiFi"
network interface card, or ethernet cable as appro-
priate for application.
Additional Applications Adobe PDF reader (for help files) SQL Server Ex-
press 2017 or SQL Server Express 2019
Software Prerequisites for PremierOne Mobile

● .NET Framework 4.8 or higher
● Adobe PDF reader (for help files)
● Microsoft SQL Server Express 2017 or 2019
Software Prerequisites for PremierOne Classic Mobile Mapping

● ArcGIS Engine 10.8.1 for Classic Map
● Microsoft Visual C++ Redistributable for Visual Studio 2017 or Visual Studio 2019
NOTE: Microsoft issues new C++ runtime libraries periodically, which could be newer than the ones
included with your PremierOne software. To obtain the latest redistributables from Microsoft, so that you
can include them in your PC images and/or deployment packages, go to:
https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
Software Prerequisites for PremierOne New Mobile Mapping

● ArcGIS Runtime 10.8.1 for New Mobile Map
● Microsoft Visual C++ Redistributable for Visual Studio 2017 or 2019 (recommended)
PremierOne Records Workstation Specifications

For workstation specifications for PremierOne Records, see the current version of PremierOne Records
Release Notes.
Test Environment
The following table contains the version levels of third-party software and firmware that was used in the
testing of this release.
NOTE: PremierOne CAD 4.6.3+ requires SQL Server 2017 Cumulative Update 10 (CU10) or higher.
241
MN008865A01-AF
Table 10: Test environment specification for Windows Server 2016
Software/Firmware Version
Windows server version as well as latest update Windows Server 2016 with latest Security Updates
dates
nCache 4.4.0
.Net Framework version 4.8
SQL version with patch SQL Server 2016/SQL 2017
SCOM version with patch SCOM 2016
ESRI version 10.8.1
Table 11: Test environment specification for Windows Server 2019
Software/Firmware Version
Windows server version as well as latest update Windows Server 2019 with latest Security Updates
dates
nCache 4.4.0
.Net Framework version 4.8
SQL version with patch SQL Server 2019 CU8+ (recommend latest CU)
SCOM version with patch SCOM 2019
ESRI version 10.8.1
242
MN008865A01-AF
Chapter 17: Using PremierOne Help
Chapter 17
Using PremierOne Help

Sometimes, the default settings for Internet Explorer prevent a Help file from opening. When a user tries to
open the Help system, a message displays and the Help window does not open.
You can follow the instructions in the message and open the initial help screen. However, every selection you
make in the Help system will be blocked in a similar manner.
To avoid this problem, you can configure Internet Explorer to allow active content in files. Use the following
procedure.
To allow PremierOne Help files to open in Windows:
Procedure:
1. Open Internet Explorer.
2. From the Tools menu, select Internet Options.
The Internet Options dialog box appears.
3. Click the Advanced tab.

The Settings list appears.
243
MN008865A01-AF
Figure 224: Internet Options Dialog Box–Advanced Tab
4. Scroll to the Security section in the list.
244
MN008865A01-AF
Figure 225: Internet Options Dialog Box–Advanced Tab Security Section
5. Click the Allow active content to run in files on my computer check box, and then click OK.
6. Close Internet Explorer.
245
MN008865A01-AF
Chapter 18: Open Source Legal Notices
Chapter 18
Open Source Legal Notices

Open Source Legal Notices are posted on the Motorola Solutions Learning Management System:
Motorola Solutions LXP
Search for "Open Source Legal Notices" to access information on open source software used by
PremierOne.
246

MN008865A01 AF Enus PremierOne CAD Mobile Release Notes v4613

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MN008865A01 AF Enus PremierOne CAD Mobile Release Notes v4613

Uploaded by

Copyright:

Available Formats

PremierOne™

CAD/Mobile Release Notes

NOVEMBER 2023 *MN008865A01*

Intellectual Property and Regulatory

Open Source Content

MN008865A01-014 First revision of the PremierOne CAD/Mobile Release April 2023

Version Description Date

3.1 4.6.12b Issues Resolved..................................................................................................................52

7.4 Mobile New Functionality............................................................................................................... 128

10.1 Issues Resolved...........................................................................................................................163

15.3 Mobile New Functionality............................................................................................................. 232

Figure 72: Main Mobile Screen.........................................................................................................................84

Figure 111: CAD Unit History Record............................................................................................................. 128

Figure 150: Incident Summary when Dispatched to a Secondary Location................................................... 160

Figure 189: ARL History Query Results..........................................................................................................192

PremierOne Release Notes

Previous versions are no longer supported.

Features and Functionality in Version

Command Line Identifier Updates

The SQL Statement should be formatted as one of the following:

Figure 8: Vehicle ID Stored Procedure Query on Queries Page

Figure 9: Vehicle ID Stored Procedure Query on Query Responses Page

Figure 12: New Location for VerifyByLocationAndCity - Provisioning

PremierOne Mobile for IOS V 4.6.231109

PremierOne Mobile for Android V 4.6.2311.8

Reply/Reply All/Forward from Messages List Screen

Reply/Reply All/Forward from Message Details Screen

Figure 18: Arrow Button and Menu

Figure 19: Menu with Reply… Submenu

Figure 20: Menu with the Reply All… Submenu

Figure 21: Menu with Forward Button

Changing Call Defaults

Figure 22: Figure: Call Default List

Figure 24: Call Dialog Box

Users can select one of the following options:

Figure 28: Disposition Box with Incident Number Field

Up to six configurable checkboxes can be added to the DRF section.

Figure 34: Incident History Screen - CAD Client

Table 1: Days of Phased Release and Percentage of Users

Day of Phased Release Percentage of Users

IMPORTANT: If your application stops working, contact Motorola Support immediately.

Features and Functionality in Version

● SCOM- PCADAPP04 Not Being Monitored by SCOM (426093)

● P1CAD - NCIC returns not visible in CAD (497327)

Units Only Option

Indicate Units that are in an In-Station Status

Display all Units in their provisioned Unit Status Colors.

Figure 39: Incident Initiate Form - Comments Text Box

Figure 41: Provisioning - Enable/Disable Comments Parsing Option

Server Configuration Tool Updates

Figure 42: RemoveOldManagementPacks Checkbox in PremierOne Server Configuration Tool Window

Reporting Configuration Tool Updates

Change Tone for Move Up

From the Edit tab, navigate to ToningDSA → Toning

In the code box, administrators should add the following string:

Print Map Page Data

In the code box, administrators should add the following string:

The following values are all configurable:

To configure the necessary Toning data, navigate to ToningDSA → Toning

In the code box, administrators should enter the following string:

Figure 47: Edit Tab - Toning > Toning Code Box

PremierOne Mobile for IOS V 4.6.230807

PremierOne Mobile for Android V 4.6.2307.2

NOVEMBER 2023 MN008865A01