Release 2025.1 is now available; it is a major release that contains new features and refinements.
NOTE: PHP 8.3 is supported and recommended for this upgrade.
We will begin scheduling 2025.1 updates on customer Test systems starting on May 2nd, 2025; however, due to staff training in May, we will schedule the upgrades for after June 1st, 2025.
Notable Changes
Please review the Database Changes in 2025.1 and make any necessary changes to your AdHoc Grids, Custom Events, and API calls.
Review and Refresh Session(s)
We are planning two Review and Refresh sessions for 2025.1. The first session is scheduled for December 3rd, 2024, at 11:00 AM Eastern, and the second is scheduled for December 4th, 2023, at 3:00 PM Eastern.
Key
Click here to expand...
Bug Fixes
New Features
Changed Features
Improved Performance
Removed Features
Release 2025.1.2 (08-14-2025)
Component
Description
Type
Documentation
CustomerCenter
Resolves an issue within CustomerCenter where (numeric) UDFs were reporting errors on Oracle Systems even though no values were assigned.
CustomerCenter Cart Requests now pull in UDF default values upon creation.
Custom Logic
The Custom Logic’s renderCustomReport function now sets the format correctly, rather than always defaulting it to JSON.
Cabling
The Auto Assign cabling grid now shows whether each item is already on a path.
General
Fixes the broken links to the PCR-360 wiki pages displayed in the “Help” slide-out.
Resolves the issue where emailed attachments were not being handled properly in some cases. Specifically, attachments received through MSGraph API Emails do not have the proper MIME type.
Resolves an issue where the Gmail API was not properly Encoding Messages to BASE64, leading to jumbled emails when they contain HTML.
Corrects a bug stopping the Gmail API interface from sending emails, specifically, but not limited to, the Bill Coordinator Email process.
Service Desk
Resolves an issue where read-only permissions for UDFs were not enforced on new Incident forms. NOTE: THIS MAY IMPACT EXISTING FORM PERMISSIONS.
Fixes a problem where specific fields still showed as “required” even though they already had a value. This occurred when you copied a form in Service Desk Actions and then changed the action type to Upgrade/Downgrade.
Release 2025.1.1 (07-22-2025)
Component
Description
Type
Documentation
Admin
Resolves an issue that prevented deleting a user after changing passwords when using native authentication.
API
Service Desk Actions can now be finalized through the API.
Resolves the Service Desk API issue, requiring an Owner to complete Actions when the order does not have an assigned Owner.
Fixes an issue where the Owner could not be changed on a Service Desk Action via the API.
CustomerCenter
Adds the ability to prevent Stand Alone Equipment requests in CustomerCenter with a new configuration option: CC_ALLOW_STANDALONE_EQUIPMENT
Adds a new configuration option “FOOTER_MESSAGE” that allows a custom message in the footer section for all pages.
The default maximum file size configuration has been increased to 50MB in the application. Some PHP configurations may need to be updated to take advantage of this: upload_max_filesize and post_max_size.
Resolves grid search errors when using certain special characters on index grids.
Cleans up warnings generated by some dashboard charts.
Inventory
Fixes an issue that causes the Purchase Order Equipment to always be set to ‘Billable’ = true.
People
Resolves an issue preventing Non-Service Desk Time from showing on the Time Entry Report.
Services
Resolves an issue with Service Charges where the Effective Date prompt was not appearing on Owner changes, and the Billing Group Pricing was not being updated.
Service Desk
Service Desk Estimates now attempt to use Purchase Order Pricing (if configured) for Equipment.
Service Desk Actions no longer require any fields when voiding, but the status will become read-only as soon as the Void option is selected.
Service Desk Equipment is no longer automatically checked as billable for Incidents.
Fixes an issue where completing a Service Order Action unchecks the Left In Cable Path Flag.
Fixes a problem where Custom Validations were not displaying the error dialog when creating new Service Desk Actions for Services that had attached Equipment.
Resolves issues where Service Desk Actions were completing even when there were errors.
Release 2025.1 (05-02-2025)
Component
Description
Type
Documentation
API
The Equipment API endpoint can now accept attachments.
The Services API endpoint can now accept attachments.
Catalogs
Removes the ability to hide Locations.
AdHoc Grids
Adds the ability to define custom parameters for AdHoc grids and enables editing of existing AdHoc grid queries and column definitions.
Adds the ability to import and export AdHoc grid definitions.
Custom Logic
This change addresses security risks by using the cURL protocol in Custom Logic. It also makes retrieving data in Custom Logic/Reports easier.
THIS IS A BREAKING CHANGE: Eliminates access to the previously allowed curl_exec() function. Adds ->curlRequest() (a wrapper to simplify curl usage) and ->curlExec() (a drop in replacement for curl_exec that restricts the allowed protocols to HTTP and HTTPS) methods for use in custom logic. EXISTING CUSTOM LOGIC USING curl_exec MUST BE UPDATED TO USE ->curlExec() INSTEAD
General
Adds additional supported HTML tags to the rich text editor used in PCR-360 to better retain formatting and styling.
Inventory
Adds the ability to access, add, and modify Remarks on closed Purchase Orders and Return Orders.
Mobile
Added a new Mobile View to PCR-360
Mobile View Features
Mobile-Friendly and Dynamic Interface
User-Customized Themes settings:
Light & Dark Mode
Font & Font Sizing
Button colors
View basic Service Desk information
Manage Workflows
Manage Labor/Time Entry
Native or SSO Login Options
“Available Custom Reports” PDF downloads are available under the Mobile View via the Custom Reports menu.
Note: This is a licensed feature. For more information, please submit a quote request to your account manager.
* Indicates external documentation not written by PCR.
Database Changes in 2025.1
Default Schema
Table Name
Change
Table Changes
ADHOC_GRIDS_PARAMETERS
Added
USER_MODULE_SESSIONS
Added
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.
