We are planning two Review and Refresh sessions for 2024.2. The first session is scheduled for November 24th, 2024, at 11:00 AM Eastern, and the second is scheduled for November 26th, 2023, at 3:00 PM Eastern.
Key
Click here to expand...
Bug Fixes
New Features
Changed Features
Improved Performance
Removed Features
Release 2024.2 (11-24-2024)
Component
Description
Type
Documentation
Billing
Corrects a spelling mistake (Quantity) on the Invoice.
Catalogs
Cable
Fixes an issue preventing Ports/Pins/Lens (PPL) from being added to Service Desk Cabling when using Auto Assign.
Adds a check for Move To Location when populating the Auto Assign Location.
Fixes an issue that prevented the Origination, Destination Equipment, and Locationsfrom grouping on the Cable Maintenance Grid.
CustomerCenter
Resolves issues with searching Call Details by Authcode in CustomerCenter.
Improvs error reporting in CustomerCenter.
General
Adds PHP 8.3 Support
Introduced more cell copy options in the grid context menu.
Right-click → Copy Row
Right-click → Copy Column
Adds the following Copy Formats for the Copy Row and Copy Column options:
JSON
CSV
TSV (Excel)
Adds required PHP Extensions to Composer config so that Composer will validate the required extensions.
Removed “Error Log Explorer” (System Log table).
Imports & Exports
Inventory
People
Services
Added a MAC Address column to the Phone Services Grid.
Service Desk
Adds Service Order and Action Numbers to the Service Deskprompt when notifying users of existing Actions on a Service.
Service Remarks now display timestamps when viewed from a Service Desk Action.
Labor from Voided workflows no longer appear in the Time Entry grid
Prevents creating more than a single Remove or Service ID Action for a Service at a time. Returns a message when attempting to create a second Service ID Action or Remove Action on the Service.
Resolves issues with the Service Desk Action printout.
Switch Interfaces
* Indicates external documentation not written by PCR.
Database Changes in 2024.2
Default Schema
Table Name
Change
Table Changes
Metadata Schema
Table Name
Change
Table Changes
No changes
Archive Schema
Table Name
Change
Table Changes
No changes
Supported Versions
PCR will patch the last two versions of the application and the current LTS Release. Customers will continue to receive Help Desk Support for releases outside of the support period for a given release. Bug fixes are only released for versions that are actively supported.
Key
Active support
A release that is actively supported.
Critical Fixes Only
A release that is supported for critical security issues only. Releases are only made on an as-needed basis.
End of life
A release that is no longer supported and will not receive bug fixes. Customers using one of these releases should upgrade as soon as possible.
Version History
Release Types
LTS Release
An LTS Release is a Major Release that PCR will support for at least 12+ months. All other releases are supported for two release cycles. LTS Releases will be patched (as a hotfix) for any Critical or High-Impact bugs applied after a release. These include (but are not limited to): service-impacting issues, billing issues, or charge-related bugs. These issues have no workaround, or the workaround is cumbersome. LTS Releases are intended to relieve “Upgrade Fatigue” for Customers who may not need all of the latest features but need critical bugs fixed. Once the LTS time period has elapsed, PCR will work with customers to move them to the next LTS release. Once an LTS reaches the last few months of support, it will receive only critical fixes and security patches.
Major Release
Major releases consist of new features and some bug fixes. These features have a relatively large scope with a greater impact on development and testing, e.g. Accounts Receivable, Service Desk Archiving, Work Order, etc.
Minor Release
Minor releases consist mostly of bug fixes and occasionally minor enhancements to the application. Minor enhancements are relatively small changes with a low impact on development and testing, e.g. adding a column to a grid, a new field, or tweaking the API. The specification process will occur in at least the month prior to being assigned.
The specification process will occur in tandem with the traditional development and testing cycle.
