Article last updated: 5/13/2025   - changes from the previous update are in red. 

In between numbered versions of the software, we are constantly making updates - whether it is to fix a bug, enhance functionality or add new functionality. This page will be updated daily to provide an update on bugs the team is fixing and on minor enhancements that are being developed.

Please note that we are reporting on system-wide issues/enhancements only.  Issues that are happening to just a specific client are communicated directly with that client on an one-on-one basis.

Please check this frequently as it will change often. 

Click here to view the Archive of past updates.

September 28th

This is a small Command Center update focused on resolving several issues across commonly used areas of P3. This update includes fixes for Business Automation, Service Agreements, ESM, Communication Templates, Telephone, SPIFF, credit card processing, Invoicing, and payments. These fixes are intended to improve the reliability and consistency of everyday workflows in the Command Center.

Command Center Bugs

• Automations that haven’t run yet show a Last Run Date and Automation Timing is Off (17159)
• Not Authorized Invoice Option when Creating Service Agreement from Customer Record (17168)
• ESM: Material is not saving when switching between Price or Cost (17166)
• Templates: Personalization Variables are not being recognized during saving (17138)
• Telephone: Voicemails are not being saved to the Call Dashboard, and Missed Call Notifications are not being sent (17177)
• SPIFF does not appear as Payable to Tech when payment comes from the App (17181)
• Incorrect Card Number Validation prevents adding American Express cards (17250)
• Unable to Change System Name when Editing an Invoice (17212 / 17335)
• Multiple Internal Notifications are sent when an Invoice is sent to a Customer (17211)
• Payments with decimal values are not being saved correctly after payment (17215)

September 7th

Version 19.5 is focused entirely on bug fixes, with most of the updates addressing issues in the P3 Apps across iOS and Android. A major focus of this release is improving App stability, with several fixes targeting crashes that could occur while syncing calls, invoices, notes, diagnostics, equipment, files, and customer data, as well as during other common App workflows. We’ve also resolved issues affecting payments, invoice and customer information, Service Agreements, ESM Proposals, schedules, images, and syncing behavior. On the Command Center, additional fixes improve Customer Records, Invoicing, ESM Financial Summary data, and historical data displayed through QuickBooks Online Sync.

Version 19.5 Overview

Command Center

• Customer Record – Manually entered Map Coordinates are not saved and revert to Auto-Calculated values. (17129)
• Invoicing – Created Bundles are not displayed in the dropdown when adding a System Part. (17130)
• ESM Financial Summary – Custom Materials are not displayed under the correct Cost or Price section. (17149)
• QBO Sync – Historical Invoice and Service Call data now display the Total Amount. (17146)

Apps – iOS and Android

• ECRYPT – Processing an Invoice incorrectly updates it to Complete and Paid even when the payment fails. (17047)
• Invoice – An Invoice may disappear from the Customer Record when the Billing Address is changed to match the Service Location. (16993)
• Apps – Resolved intermittent crashes when syncing Calls created from the Schedule Legacy View. (16927)
• Technician Notes – Notes containing emojis may be cut off after syncing. (16931)
• Invoice Custom Labels – Changes are not reflected across all Apps after syncing. (16733)

Apps – iOS Only

• iOS Apps – Resolved crashes occurring when syncing Completed Calls. (16620/16617/16825/16823/17020)
• iOS Apps – Resolved intermittent crashes when creating Invoices and completing Calls. (17039/16975)
• iOS Apps – Resolved crashes when searching for Customers. (16669/16972)
• iPhone App – Resolved crashes when syncing Notes with longer character lengths. (16803)
• iPad App – Resolved a crash when creating a Service Agreement. (16577)
• iPad App – Resolved a crash when returning from an Invoice to the Schedule screen. (16860)
• iPhone App – Initiating a payment through the ECRYPT Card Reader immediately displays Payment Success even when no card has been used. (17123)
• iPhone App – Created Invoices may contain information from the wrong Customer when navigating between multiple Customers before syncing. (16969)
• iPad App – Duplicate Invoices are generated when accepting ESM Proposals. (16668)
• iPad App – Invoices created from a Blank Diagnostic Report may disappear from the Customer Record. (17044)
• iOS Apps – Recently synced Technician Schedules may disappear when the device goes offline. (16793)
• iOS Apps – Service Agreement Pricing is not applied to the Invoice when the Diagnostic Fee is changed. (16827)
• iPad App – Some Generic Calls associated with a Recurring Appointment are not displayed on the Calendar when the End Date is changed to an earlier date. (16490)
• iPad App – Adding Materials to an ESM Proposal displays a successful save message even when the save fails. (17002)
• iPad App – Customer Information is not displayed on ESM Proposals when ESM Custom Pricing Labels contain an apostrophe. (17043)
• iPhone App – The Customer Record Invoice Table displays an Amount Owed even when the Invoice is marked Complete and Paid. (16748)
• iPad App – Uploaded Landscape Images are resized to a square instead of retaining their original dimensions. (17052)

Apps – Android Only

• Android Tablet App – Resolved crashes when syncing Diagnostics and Equipment Data. (16617/16723)
• Android Tablet App – Resolved crashes when downloading Customer Historical Data. (16804/16741)
• Android Tablet App – Resolved a crash when syncing Files from the Customer Record. (16576)
• Android Phone App – The File Picker appears blank when attempting to upload Photos or Files. (16824)
• Android Tablet App – Multiple images uploaded when creating Equipment through ID Pro Scan result in only one image being displayed. (16846)

* Definitions

Updates Completed By Dev Team

The development team has completed their initial development.  At this point the testing team is confirming the fix was done according to the specification and that no other areas of the software were impacted as a result of the update; i.e. we didn't break something else in the process.  If there are any issues, they are fixed.  Once all issues are fixed, then the update will be slotted for the next available release.

In Progress

These are updates where an internal deadline has been set for the development team to deliver the update to the testing team.  The internal deadline can be anywhere from a couple days to a few weeks.  However, since there is a deadline it is on the schedule and the team is committed to its completion.

Design Phase

These are updates where we are writing the specification for how the system should behave.  In addition, in this step we create mockups so that the whole team has a visual representation of how the screens will look and how the interactions will work.  Please note that not all updates that enter the Design Phase will move to the In Progress status.