V4.3.0.7.3 Release Notes
V4.3.0.7.3
This topic provides a list of product changes included in this patch.
Asset Strategy Management
| Description | Tracking ID |
|---|---|
| Previously, in the Risks and Actions page, if you attempted to consolidate RCM or FMEA actions, the process timed out. | DE108490 |
Calibration Management
| Description | Tracking ID |
|---|---|
| Previously, in a calibrator, if you entered the name of a user who was not a member of the MI Calibration Administrator or MI Calibration User Security Group, and tried to receive data from a calibrator, although you received the data, instead of an error message, a blank screen appeared. This issue has been resolved. | DE108620 |
| Previously, after receiving multiple records from a calibrator, if you did not save all the records that were received, the values for the saved records were always picked from the first record in the list. This issue has been resolved. | DE108612 |
| Previously, if you sent data to a Fluke calibrator, and performed a calibration using a Calibration Template, Analog or Calibration Template, Discrete record with the input UOM set to Degrees Celsius (DEG C), an error occurred. This issue has been resolved. | DE108500 |
Rounds Data Collection
| Description | Tracking ID |
|---|---|
| Previously, while disconnected from a network, if you created a recommendation for a Route, the time stamp of the recommendation displayed the time at which your device reconnected to a network. This issue has been resolved. Now, the time stamp of a recommendation displays the time at which you created the recommendation. | DE108482 |
| Previously, if you created an Operator Rounds Recommendation without the Create Work Request? check box selected, and selected that check box when updating the recommendation, the work request was entered into your SAP system, but the recommendation was not updated with the data of the work request in the Rounds Data Collection module. | DE108362 |
Rounds Designer
| Description | Tracking ID |
|---|---|
| Previously, if you created a Route using the Rounds Route Data Loader, the Route sequence did not load as expected. | DE108351 |