(v1) .Release Notes v2019.1
- David Engblom
Release 2019.1 is now available. This patch contains a number of stabilization fixes and refinements. We will begin scheduling 2019.1 updates on customer Test systems starting March 27th, 2019.
Note: All versions after 2018.1 require an upgrade to PHP 7.2, hosted customers and customers who have 2018.1 already have the php upgrade. Most updates to test systems will need to occur during non-business hours. Please send any scheduling requests to help@pcr.com.
This release contains some table changes that could cause issues with Adhocs, API calls, Grid Perspectives, or other custom processes. Please review the Release Notes#Database Changes in 2019.1 to review the changes and make the necessary changes to your customizations.
Licensed Customers will need to install PHP 7.2 before we can upgrade test to 2019.1, the instructions can be found here: PHP 7.2 Upgrade. Please consult PCR before upgrading your system.
Key
Release 2019.1.4 (06-20-2019)
Component | Description | Type | Incident(s) | Documentation |
|---|---|---|---|---|
Billing | When processing Monthly Recurring Charges that were Stopped on the Billed Through Date the billing process was incorrectly generating Bill Details transactions. The process should only flag the charge as Billing Complete and not generate any Bill Details transactions. | IN201935378 |
Release 2019.1.3 (05-23-2019)
Component | Description | Type | Incident(s) | Documentation |
|---|---|---|---|---|
API | To address a rapidly growing API Request table, full API responses will not be saved for successful SQL POST calls or GET API Calls; only error responses will be saved. |
Release 2019.1.2 (05-10-2019)
Component | Description | Type | Incident(s) | Documentation |
|---|---|---|---|---|
Escalations & Notifications | Added a process to convert the Escalation Sequences to the new format used in 2019.1. | IN201935672 |
Release 2019.1.1 (05-10-2019)
Component | Description | Type | Incident(s) | Documentation |
|---|---|---|---|---|
API | The permissions set on each API Endpoint are now obeyed when called from a Custom Endpoint. | Custom API |
Release 2019.1 (03-25-19)
Component | Description | Type | Incident(s) | Documentation |
|---|---|---|---|---|
API | Added the ability to use Authentication with API calls.
| |||
| Added the ability to Add and Update Contacts via the API. | Contact API Calls | |||
| Added the ability to specify the Source field using the Service Desk API. | Service Desk API Calls | |||
| Added an API Request Log to assist users with troubleshooting API calls. The log contains all Requests made to the PCR-360 API and the Response. | API Request Log | |||
| Added the ability to associate Equipment with a Service Desk Item via the API. | ||||
Added the ability to add or update the Rating-Group via the Services API. | Services API | |||
| Added the ability to specify an SDC with a Service Desk Action API call. | Service Desk Action API | |||
Added the ability to Stop the following types of Charges via the API:
| IN201833443 | |||
Added the Effective Flag to the following Charge APIs:
| ||||
Added the ability to create the following Action types via the API:
| Users Group | Service Desk Action API | ||
Modified the names and columns for various API tables. |
| Release Notes#Database Changes in 2019.1 | ||
| Now all POST Requests require content in the body of the request. URL String parameters are no longer supported for POST Requests. |
| API | ||
Added a check to the Services API POST to allow editing a Service with a Formatted Service ID. The API now checks for the Service, removing the requirement that Service RECID be passed via the API Request. Previously the API incorrectly created Duplicate Services. |
| Services API | ||
| Corrected the API Service Charge Error message to properly reference the Service Charge rather than Equipment Charges. |
| |||
Corrected an issue with the Service Desk API not filling in all Auth Code Service Details. Added additional fields to Service Desk API |
| Service Desk API | ||
Updated the API to send proper response codes.
|
| API Response Codes | ||
| Fixed an issue where the GLA API was not properly enforcing required GLA Components. |
| GLA API | ||
| Fixed an issue where the API did not populate Service Location on Remove Action if service is Multi-Location and only has one Location. |
| IN201834748 | ||
The Service Desk API Change and Remove Actions now allow a Location for a Multiple-Location Service only if that Location is already associated to that Service. The API now returns appropriate error messages for change actions ("The 'location' provided is not associated with the Service." and "This Service has multiple Locations and requires the 'location' parameter.") |
| IN201834748 | Service Desk Action API | |
| Fixed an issue where the Services API allowed duplicate GLA types of 100%. |
| IN201935127 | ||
Billing & Charges | The Bill process will be prevented from running if the Bill range overlaps an existing bill. |
| Bills | |
Cable | Fixed an issue where the From Equipment Location disappeared on the Cable Maintenance Grid when a pair strand was saved. |
| IN201935022 | |
Calls | Fixed an issue where Call Rating would sometimes use the wrong Service Host value for Rating. |
| IN201832461 | |
CustomerCenter | Fixed an issue where adding Stand-Alone Equipment to the cart would erroneously cause the system to report that Order Details were missing and prevent the cart from submitting. |
| ||
| Fixed an issue with the CustomerCenter Accounts Receivable Details widget where it only displayed Invoices for up to 8 accounts. |
| |||
Escalations & Notifications | Added the following verbs to Escalations Sequences:
|
| Escalations / Notifications | |
|
| Escalations / Notifications Prior to 2019.1 (for comparison) | ||
General | Added a Source column to the Authentication Log to indicate whether a user logged in using LDAP, Shibboleth, the API etc. |
| ||
Renamed some Authorization Constants:
|
| |||
| With this release, the Catalog tab and the Default Charges tab are always visible on the Equipment Catalog form. Default charges are only deleted when the category flag is checked and the record saved. Both Active and Inactive charges are deleted from the Catalog. |
| Equipment Catalog | ||
| PHP 7.2 removed support for mcrypt. All usages of mcrypt in PCR-360 have now been replaced with Openssl. |
| |||
| Fixed an issue where the Adhoc Query Builder form would fail to load for certain users. |
| IN201832648 | ||
| Fixed an issue where saving a Perspective sometimes unchecked the Auto Load Data checkbox. |
| IN201622826 | ||
Imports & Exports | Added an Equipment Catalog Import. |
| Equipment Catalog Import | |
| Added the ability to Unhide Locations using the Cable Full Path Import or the Location Import. |
| |||
| Improved the performance of the GLA Import when updating UDF values. |
| |||
| The Pair/Strand, Ports/Pins/Lens, and Full Path Imports now account for duplicate Equipment IDs. If the same Equipment ID exists on multiple Equipment records in the application and is referenced in the import file, the import will insert an error line into Imported Records instead of failing the entire file. |
| IN201833921 IN201833126 | ||
| Fixed an issue causing the GLA Import to fail when trying to populate a GLA Picker UDF on a GLA. |
| |||
| Fixed an issue where certain types of errors would cause the Cable Full Path Import to crash. |
| |||
Service Desk | Added MAC Address to the Service Desk Equipment Form and Service Desk Equipment Picker. |
| IN201622826 | |
| Fixed an issue where the duplicate Path Leg error message just displayed 'Failed to Save Record'. The error message has more detail to allow the user to correct the data. |
| IN201834772 | ||
| Fixed an issue where the Service ID was not displayed on the Service Desk Cabling Diagram for an Add Action. |
| |||
| Fixed an issue that caused odd formatting of graphical Cabling Data on print reports. |
| IN201834904 | ||
| Fixed an issue where the Location Picker on the Service Desk Wizard allowed the user to select Inactive Service Location records. |
|
Database Changes in 2019.1
| Table Name | Change | Table Changes |
|---|---|---|
APIS | Removed | |
AUTHENTICATION_LOG | Updated | Added AUTH_SOURCE VARCHAR(20) |
BILLS | Updated | Added BILL_END_DATE DATETIME NULL Changed BILL_END_DATE to not allow NULL |
API_KEYS | New | |
API_KEYS_PERMISSIONS | New | |
API_KEYS_USERS | New | |
API_KEYS_USERS_TOKENS | New | |
API_PERMISSIONS | New | |
API_REQUESTS | New |
Additional Information on Hidden Locations
Before this change, if you had a Location record that you hid using the Hide Button on the Location Grid, and you tried to get the Cable Full Path or Location Import to create that Location, you would get an error. The import would check to see if the Location already existed. The check was ignoring hidden locations, treating them like they didn't exist. So, the import tried to create a new Location record and caused an SQL Duplicate error.
After this change, these two imports will notice that the Location already exists in a hidden state. Now the import retrieves the hidden Location record and updates it, so it is no longer hidden. The process will blank out any old information on the Location (from before it was hidden), so it will seem like a fresh new record. The remaining import logic will treat it as a new record and fill in the values as normal. The Imported Records grid will display a line showing a new Location record added.
A consequence of this is that if there were any old Service Orders that referenced this Location, then any details of the Location that were displayed on the Service Order will now show the new Location values instead of the original values. This problem will eventually be solved by the Service Order archiving change.
Help Desk Portal - Email: help@pcr.com - Phone: 616.259.9242