This topic provides a list of product changes included in this patch.
APM Connect
| Description | Tracking ID |
|---|
| Previously, when multiple jobs of the same type were running simultaneously, there could be a scheduling collision causing one job to get stuck in Staging Complete. This issue with resource contention has been resolved. | DE128658 |
| Previously, in APM 4.3.1, when running data loaders for non-English users (for example, German), numeric values for that culture were not being formatted correctly. This issue has been resolved. | DE127334 |
Dataloader
| Description | Tracking ID |
|---|
| Previously, if the APM Relationship for a link is defined as a Foreign Key Relationship, the APM Family Data Loader did not support the ability to update a link from one record to another. This issue has been resolved. | DE128737 |
Family Policies
| Description | Tracking ID |
|---|
| Previously, in the Math node, when you modified an equation containing an indexed variable name conflicting with an input variable name, an error occurred. This issue has been resolved. | DE128545 |
Policy designer
| Description | Tracking ID |
|---|
| Previously, in the Math node, when you modified an equation containing an indexed variable name conflicting with an input variable name, an error occurred. This issue has been resolved. | DE128545 |
RBI 581
| Description | Tracking ID |
|---|
Previously, when calculating the mitigated risk on the plan date for External Cracking Degradation Mechanism Evaluation on an RBI 581 Risk Analysis, the age calculation did not consider the target inspection date. As a result, the Total Damage Factor With Plan field (RBI Degradation Mechanisms) contained incorrect values for the following damage mechanisms:- 581-Austenitic Component Atmospheric Cracking
- 581-Austenitic Component Cracking Under Insulation
This issue has been resolved. | DE128738 |
System Requirements
| Description | Tracking ID |
|---|
| Previously, if you accessed GE Digital APM using Chrome browser version 80 or higher, you may have experienced some issues. These issues have been resolved. | DE128739 |
Thickness Monitoring
| Description | Tracking ID |
|---|
| Previously, in the TM Dataloggers page, in the Send To and Receive From sections, the Thickness Measurement Locations (TMLs) were not sorted. This issue has been resolved. Now, the TMLs are sorted in alphanumerical order of the corresponding TML IDs. | DE128020 |
Queries
| Description | Tracking ID |
|---|
| Previously, older queries that included a date/time format without the time parameter would not return any data. This issue has been resolved. | DE127899 |