Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Release 2024.1 is now available; it is a major release that contains new features. 


NOTE: PHP 8.1 IS REQUIRED for this upgrade.


We will begin scheduling 2024.1 updates on customer Test systems starting on January 29th, 2024.


Please review the Database Changes in 2024.1 and make any necessary changes to your AdHoc Grids, Custom Events, and API calls.

Review and Refresh Session(s)

We are planning two technical overview sessions for the new functionality. These sessions will be tailored to those with technical knowledge or experience using PCR-360 customizations, but all are welcome. The first session is scheduled for January 22, 2024, at 11:00 AM Eastern, and the second is scheduled for January 24, 2024, at 3:00 PM Eastern.

Key

Expand

Bug Fixes

bugFix.png

New Features

addFeature.png

Changed Features

changeFeature.png

Improved Performance

monitor_lightning.jpg

Removed Features

delFeature.png

Release 2024.1.3 (04-

...

16-2024)

Component

Description

Type

Documentation

API

Adds the ability to Complete Service Desk Actions via the API.

addFeature.png

https://pcr360.atlassian.net/wiki/x/vBsHAQ

Rating Group is now imported to new Remove Actions when created by API.

bugFix.png

The Service Desk Actions API now gets the rating_group and Catalog from the existing record.

bugFix.png

The Services API now allows updating a Service to a Category Catalog.

bugFix.png

The Barcode API now properly returns an “Invalid JSON” error when attempting to decode invalid JSON data.

bugFix.png

The Cable Paths API no longer requires the status field.

bugFix.png

Fixes a Gmail API Error Authenticating OAuth2 Token due to an Invalid State.

bugFix.png

Inventory

Corrects an issue where the Warehouse Action form was not updating the Asset Tag field, or Equipment ID correctly after using the Equipment picker.

bugFix.png

Reporting

Fixes an issue with Scheduled Reports that originated from tab grids. (The original issue was reported as a problem scheduling reports from the Call Details tab on Services)

bugFix.png

...