V5.1.1.0.0

360-View

This topic provides a list of product changes released for this module in this version.

Table 1. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, you could mark any asset group as a personal group, and you were able to view personal asset groups of other users. These issues have been resolved. Now:
  • You can mark only the asset groups that you create in Asset Hierarchy or 360 View as personal groups.
  • Unless you are a super user, you cannot view the personal groups of other users.
Note: Groups created automatically in other product workflows cannot be marked as personal groups.
US605289
Previously, if you configured an Advanced Visualization as the content of a 360 View, the visualization was displayed in a very small frame. This issue has been resolved.DE208317
Previously, if you were a super user with no assigned roles, when you selected an asset or group, no 360 Views were displayed. This issue has been resolved. Now, if you have no assigned roles, the default asset or group view is displayed.DE207956
Previously, if the asset ID was very long, the asset ID wrapped, and the asset type was displayed over the 360 View tabs. This issue has been resolved. Now, the asset ID is truncated.DE207840
Previously, in the Group Filter window, if you selected multiple relationships, duplicate records appeared in the search results. This issue has been resolved.DE206980

APM Connect

This topic provides a list of product changes released for this module in this version.

Table 2. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, when loading data into APM using the APM Family Data Loader where rules, policy, or any other application tried to reference the records or links that were just created as part of the current session (but no saved to the database), the consuming application was not able to reference the new records or links. This issue has been resolved.DE208952

Asset Health Manager

This topic provides a list of product changes released for this module in this version.

Table 3. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, if you implemented an action as Health Indicator for an Asset Strategy that was controlled by a master template, the Health Indicator was linked to all the assets using the template. This issue has been resolved. Now, the Health Indicator is linked only to the asset associated with the Asset Strategy.DE203310

Asset Strategy Management

This topic provides a list of product changes released for this module in this version.

Table 4. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, if you were an administrative user, and if you changed the Action family to use VB Rules instead of Policy in Family Management, an error appeared when you attempted to delete a Secondary Action. This issue has been resolved. Now, administrators can set the Action family to use VB Rules without any error appearing.DE208453
Previously, when you exported an Asset Strategy, the decimal values were not formatted based on the user culture setting. This issue has been resolved.DE207988
Previously, when you attempted to unlink an implemented Strategy as an Asset Strategy Management user, an error occurred, stating that the family was not found. This issue has been resolved.DE207641
Previously, in an AHM workflow in Asset Strategy, incorrect or duplicate general recommendation IDs were generated. This issue has been resolved. The recommendation IDs are now generated in sequence.DE207587

Asset Strategy Optimization

This topic provides a list of product changes released for this module in this version.

Table 5. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, when you modified and saved a Qualitative Consequence for a Risk, the Qualitative Consequence subsection for the selected Risk did not change back to view mode. This issue has been resolved.DE136779

Calibration Management

This topic provides a list of product changes released for this module in this version.

Table 6. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, when you performed a manual calibration from the Calibration Queue section, sometimes, the Asset, Template, or the Task field in the Calibration Event datasheet was not populated. This issue has been resolved.DE209347

Data Loaders

This topic provides a list of product changes released for this module in this version.

Table 7. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, when running multiple Ingestor Services that pointed to the same ActiveMQ and Redis instances, in some scenarios, two Ingestor Services tried to access the same log file at the same time. Because of this, an error occurred, which disrupted the bundle ingestion. This issue has been resolved.DE208871

Failure Modes and Effects Analysis

This topic provides a list of product changes released for this module in this version.

Table 8. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, the Asset Description field was not updated via the FMEA Asset Template Data loader. This issue has been resolved.DE209365
Previously, applying an asset template to multiple assets in bulk was inadvertently removed. This issue has been resolved. Now, the feature is available.DE209119
Previously, when you searched for RCM or FMEA records using global search and attempted to open the record, an error appeared. This issue has been resolved.DE208336
Previously, when you uploaded an FMEA Analysis Template through the data loader, the Asset Description was not updated. This issue has been resolved.DE206436

Family Policies

This topic provides a list of product changes released for this module in this version.

Table 9. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
To improve usability, the following enhancements have been made in the Reference Document generated through Email Contact node with attachment:
  • The ID is generated in the following format: Email Attachment for Policy -<Name>
  • The description field is updated in the following format: Policy: <policy name>; Instance: <instance ID>; Email sent to:<email address list>; Execution time (UTC):<timestamp of the email node execution in ISO format>
  • To keep a file name unique and to avoid renaming an attachment while saving it to your local system, the attachment name is updated in the following format: ExecutionOutput_<policy name>_<instance id>_<timestamp MMDDYYYY-hhmmss>.csv
US593664
To improve usability, the policy execution history background clean up job has been improved. To facilitate this enhancement, additional options have been added to control the job start time, end time, and selection of timezone.US541496
Table 10. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, in an After Insert relationship family policy, a Query node did not return the predecessor and successor entities linked by the inserted relationship. This issue has been resolved.DE208954
Previously, is Null node was converting input string value to the unreadable date format. This issue has been resolved.DE207778
Previously, the Export Instances and Policy Instance Data Loader did not recognize the Measurement step node and all values were considered as Point value nodes. This issue has been resolved.DE207705
Previously, when JSON Parser node configured with more than one Name and JSON path value then in return value node will have only one value available. This issue has been resolved.DE207345
Previously, State Transition node execution log messages and execution history was showing Family id instead of Entity Key. This issue has been resolved.DE207344
Previously, with State Transition Mode option, when a Record was already in the target state, Policy execution was showing success for state transition. This issue has been resolved.DE206836

Foundation

This topic provides a list of product changes released for this module in this version.

Table 11. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
To improve product security, now, when the Your session has expired window is displayed, the current APM page content is hidden. Further, you can no longer cancel the dialog to return to APM; you may only proceed directly to the login page.US607466
Table 12. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, when you accessed some APM pages, an error message appeared, stating that the feature was not accessible, although the device met the recommended screen width for APM. This issue occurred only if you accessed APM in an Edge browser because of a change in the Edge browser. This issue has been resolved. Now, the error message appears only if the browser window width is less than 768 pixels.
Note: The recommended minimum screen width for desktop devices remains 1024 pixels.
DE210143

Generation Availability Analytics

This topic provides a list of product changes released for this module in this version.

Table 13. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, you could not add or import inactive related events that spanned multiple years. This issue has been resolved.US598363

Hazards Analysis

This topic provides a list of product changes released for this module in this version.

Table 14. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, when you clicked on the LOPA ID linked to a consequence, an incorrect screen appeared. This issue has been resolved. Now, the hyperlink on the LOPA ID has been removed. DE206197
Previously, when you deleted a Hazards Analysis, the following records were not deleted:
  • Hazards Analysis Revision
  • Hazards Analysis System/Node Revision
  • HAZOP Deviation Revision
  • What If Revision
  • Hazards Analysis Cause Revision
  • Hazards Analysis Consequence Revision
  • Hazards Analysis Safeguard Revision
This issue has been resolved.
DE198596

Import and Export

This topic provides a list of product changes released for this module in this version.

Table 15. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, importing and exporting fields that satisfy the following conditions was not supported:
  • Fields that were set to Required
  • Fields with the Security Group Query condition
  • Fields with a query containing a prompt
This issue has been resolved.
DE207775

Inspection Management

This topic provides a list of product changes released for this module in this version.

Table 16. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, when you transitioned the state of an Inspection to the Draft state, the Inspection was not unlocked. This issue has been resolved. Now, when you transition from any state to the Draft state, the Inspection is unlocked.US601217

Previously, in the Inspection Confidence section of Full Inspection, if you added a new record in the bulk data form, then navigated to a different APM tab without saving the record, and then returned to the Inspection tab, the unsaved record was displayed twice in the bulk data form. This issue has been resolved.

DE209154

Previously, when you attempted to create an inspection and an error occurred from rules, the error message did not appear. This issue has been resolved.

DE208219
Previously, after accessing the Inspection Confidence Evaluation section in the Inspection Overview page, if you switched between multiple tabs, and then generated Inspection Confidence Evaluation records, the generated records did not appear in the list. This issue has been resolved.DE207112
Previously, while viewing an image which was referenced as an URL, an “Invalid URL” error appeared. This has been resolved. Now, you can view images which are referenced as URLs.DE205167

Previously, Inspection Health Evaluation was displayed as a configurable family in the Event Configurations page, This issue has been resolved.

DE175261

Previously, the Generate Report button was enabled in the Inspection Tasks section for the MI Inspection Viewer Group. This issue has been resolved.

DE170865

Integrity Mobile Application

This topic provides a list of product changes released for this module in this version.

Table 17. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
To enhance usabilty, you can now refresh the My Inspections and All Tasks views with a new pull-to-refresh functionality.US600710
Table 18. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, photos or documents of size greater than 16 MB could not be saved to the internal app database. This issue has been resolved.DE208311
Previously, in some scenarios, Inspection Scoping documents failed to download before the Inspection appeared to complete checkout. This issue has been resolved.DE207491

Management of Change

This topic provides a list of product changes released for this module in this version.

Table 19. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, when you accessed the MOC Change Project summary record, the Project Status was showing state Id instead of state caption. This issue has been resolved.DE208462

Metrics and Scorecards

This topic provides a list of product changes released for this module in this version.

Table 20. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
To enhance functionality, a Super User, MI Metrics Admin, and MI Metrics User will override MI Metrics Viewer. To facilatate this enhancement, sequential permission check is introduced so that MI Metrics Viewer does not override Super User, MI Metrics Administrator, and MI Metrics Users, as per the earlier functionality.US609247
Table 21. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, when there were multiple measurements in a single day, the key performance indicator (KPI) did not show the latest measurement. This issue has been resolved.US606508
Previously, when you reopened a Key Performance Indicator (KPI), the scheduler summary of the KPI contained incorrect start or end date and time. This issue has been resolved.DE208993
Previously, when Worst, Critical, Target, Stretch and Best values of a KPI were retrieved from an APM Query, and you updated the measures, the Updated actual values/scores section did not display any values or limits. This issue has been resolved.DE208399

OT Connect

This topic provides a list of product changes released for this module in this version.

Table 22. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
To enhance usability, you can now configure the OT Connect HDA Adaptor to use Raw reading values from the Historian for Tag Subscriptions or to use the End Aggregate reading values from the Historian.
Note: This can be configured in appsettings.json file at Adapter level.
DE208017
Table 23. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, when performing a Tag Sync, if you encountered a system exception, the error message only stated that one or more errors occurred. This issue has been resolved. Now, in this scenario, the underlying error and the associated details appear.DE209438
Previously, when you attempted to run the OT Connect Adapter Compatibility Checker utility, an error occurred. This issue has been resolved.DE208017
Previously, the OT Connect HDA Adapter only supported a Historian Aggregate named OPCHDA_END. This issue has been resolved. Now, the OT Connect HDA Adapter supports any Historian Aggregate whose name ends with END.DE205217

Policy Designer

This topic provides a list of product changes released for this module in this version.

Table 24. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
To improve usability, the following enhancements have been made in the Reference Document generated through Email Contact node with attachment:
  • The ID is now generated as "Email Attachment for Policy -<Name>"
  • The description field is now updated as "Policy: <policy name>; Instance: <instance ID>; Email sent to:<email address list>; Execution time (UTC):<timestamp of the email node execution in ISO format>".
  • To keep the filename unique and to avoid renaming the file while saving attachment the file to your local system, the attachment file name is updated as "ExecutionOutput_<policy name>_<instance id>_<timestamp MMDDYYYY-hhmmss>.csv".
US593664
To improve usability, the policy execution history background clean up job has been improved. To facilitate this enhancement, additional options have been added to control the job start time, end time, and selection of time zone.US541496
Table 25. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, is Null node converted the input string value to an unreadable date format. This issue has been resolved.DE207778
Previously, when JSON Parser node configured with more than one Name and JSON path value then in return value node will have only one value available. This issue has been resolved.DE207345
Previously, State Transition node execution log messages and execution history was showing Family Id instead of Entity Key. This issue has been resolved.DE207344
Previously, with State Transition Mode option, when a Record was already in the target state, Policy execution was showing success for state transition. This issue has been resolved.DE206836

Production Loss Analysis

This topic provides a list of product changes released for this module in this version.

Table 26. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, when you selected the Causing Asset field in a Production Event datasheet, you could not view every site's asset hierarchy in the Asset Finder window. This issue has been resolved. Now, the Causing Asset field uses the Search Finder window to display the asset hierarchy.US611328

Queries

This topic provides a list of product changes released for this module in this version.

Table 27. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
To enhance usabilty, you can now specify the page size to be used by query engine during export of a query result. To facilitate this enhancement, a new field Use page size has been added to the Export to a File section that enables you to specify the page size.US610218
Table 28. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, if a query column was an expression column and was of type numeric, then on filtering, an error appeared. This issue has been resolved.DE207321

Record Manager

This topic provides a list of product changes released for this module in this version.

Table 29. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, in a text or character field, certain valid characters, for example the € symbol, were removed from the value that was saved to the database. This issue has been resolved.DE209625
Previously, if you configured a field to use a picklist with numeric values, and your user culture used a comma as the decimal separator, when you edited the records in the Bulk Data Form, fractional values were overwritten with integer values. This issue has been resolved.DE209551
Previously, if you specified canEdit=true in the !datasheet- dialog URL, the datasheet was displayed in read-only mode. This issue has been resolved.DE209281
Previously, if picklist field behavior contained input as date field from family, an error appeared when the datasheet was loading. This issue has been resolved.DE208769
Previously, when you opened the Bulk Data Form from Global Search, Advanced Search, or using a hyperlink, made changes, and then switched to a different APM tab:
  • If you had unsaved changes, the changes were lost.
  • If you added and saved new records, when you returned to the Bulk Data Form, the newly added records were no longer displayed.
These issues have been resolved.
DE208319
Previously, when a record was locked for editing, you could not copy the text in the fields. This issue has been resolved.DE208307
Previously, in a date field that was configured to use the short date format using a field behavior, a time picker was displayed in the date selection window, which resulted in the field value set to the wrong value. This issue has been resolved. Now, in this scenario, the time picker is not displayed in the date selection window.DE207248
Previously, if custom behavior and a non-standard format were set for a date field, an error occurred when you accessed the corresponding record using Record Manager. This issue has been resolved. DE205005
Previously, when you used the Microsoft Edge browser, the drop-down selection list in a multi-value field closed unexpectedly when you selected a value, resulting in incorrect values saved to the field. This issue has been resolved.DE201466

Reliability Analytics

This topic provides a list of product changes released for this module in this version.

Table 30. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, in Production Analysis, when you changed the Subdivided Region colors, the cancel option did not cancel when changing the color via text code. This issue has been resolved. DE207687
Previously, when you clicked the Production Analysis full screen button to expand, and then clicked the button again to reduce the screen size, the Production Analysis window closed completely, functioning similar to the Collapse button. This issue has been resolved. DE207683

Reliability Centered Maintenance

This topic provides a list of product changes released for this module in this version.

Table 31. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, while creating a new RCM analysis from an RCM template, the Functions, Functional Failures, Failure Modes, Failure Effects, and Recommendations were not transferred to the new analysis. This issue has been resolved.DE209533
Previously, when you searched for RCM or FMEA records using global search and attempted to open the record, an error appeared. This issue has been resolved. You can now access RCM and FMEA records successfully using global search.DE208336
Previously, when you uploaded a RCM Template through the data loader, the Asset Description was not updated. This issue has been resolved.DE206436

Reports

This topic provides a list of product changes released for this module in this version.

Table 32. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
You can now redeploy to Report Server only when there are changes in a report (instead of redeploying every time the report is accessed). To facilitate this enhancement, a new box named Web App Name has been added to the SQL Server Reporting Services workspace. If you do not enter a value in this field, the default value of Reports is considered.US609388

Risk Based Inspection

This topic provides a list of product changes released for this module in this version.

RBI 580 and RBI 581

Table 33. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID

When archiving an RBI Analysis with a consolidated or superseded recommendation, the RBI Analysis of the other source recommendation is no longer archived. The CREC Recommendation and master superseded recommendation will transition back to Proposed state to allow the user to decide if they want to unlink or update the recommendation before reapproving the RBI Inspection Plan.

US609814
Table 34. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, when calculating an analysis on a Piping Circuit with a Criticality Calculator External Corrosion Degradation Mechanism, the Piping Circuit Complexity was erroneously calculated when the following fields were blank:
  • Number of Terminations
  • Number of Penetrations
  • Number of Vertical Runs
This issue has been resolved. Now, when the fields are blank, the Circuit Complexity will not be calculated, and the External Age will not be adjusted.
DE209592

Previously, the RBI Calculation Screen would continue to show in-progress although the calculation was successful intermittently. This issue has been resolved. Now, the calculation screen will update to Complete after the calculation is successful.

DE209326
Previously, after accessing the Inspection Confidence Evaluation section in the Inspection Overview page, if you switched between multiple tabs, and then generated Inspection Confidence Evaluation records, the generated records did not appear in the list. This issue has been resolved.DE207112
Previously, when you selected more than 100 Analyses to Finalize Risk, an error message might have been displayed and all selected analysis might not have been moved to Risk Completed state. This issue has been resolved. Now, you can only finalize risk for 100 Analyses at a time. A warning message will be displayed when you select more than 100 Analyses to Finalize Risk on the following section/workspace:
  • RBI Overview- Assets Tile
  • Process Unit Overview
  • RBI Bulk Evergreening
  • Bulk Create What-If Analyses
DE161730

RBI 580

Table 35. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, when the Selected Corrosion Rate field was set to Average Rate on a Criticality Calculator External Corrosion Damage Mechanism Evaluation, the Estimated Wall Loss and Estimated Half Life values were calculated incorrectly. This issue has been resolved. Now, in this scenario, the Measured Corrosion Rate field is used for calculation, resulting in the correct Estimated Wall Loss and Estimated Half Life values.DE207443

Root Cause Analysis

This topic provides a list of product changes released for this module in this version.

Table 36. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, you could not create an RCA from a PLA Production Event if the Causing Asset was already associated with the Production Event. This issue has been resolved.DE209302

Rounds Data Collection

This topic provides a list of product changes released for this module in this version.

Table 37. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, in the RDC Overview page, if you attempted to open a SharePoint reference document for a Measurement Location, an error occurred. This issue has been resolved.US609053

Rounds Designer

This topic provides a list of product changes released for this module in this version.

Table 38. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, when you loaded Readings data into APM using the Rounds Readings Data Loader, an error occurred if you did not provide a value in the MI_READING0_RELAT_ML_ENTIT_KEY_N column. This issue has been resolved. Now, you can provide a value in either of these columns:
  • MI_READING0_RELAT_ML_ENTIT_KEY_N
  • MI_CHECK_PT_CHEC_ID_C
DE208967

Rounds Pro

This topic provides a list of product changes released for this module in this version.

Table 39. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
To enhance usability, the Allow Photos feature is now available in a Step Template itself, thus simplifying the process of creating steps. To facilitate this enhancement, using the Allow Photos field in the step template, you can specify whether capturing photos is allowed in the step template itself, which will be cascaded to the steps created using the template.US606011
To enhance usability, when using the Rounds Pro Step Data Loader, you can now provide the additional information to identify Equipment and Functional Location. To facilitate this enhancement, the following columns have been added to the Data Loader template:
  • REL_CMMS_SYSTEM: This column is used to enter the CMMS value of Equipment or Functional Location.
  • REL_EQUIP_TECH_NUM: This column is used to enter the technical number of Equipment.
Both the columns are used to identify an Equipment, whereas only the REL_CMMS_SYSTEM is used to identify a Functional Location.
US603642
To enhance usability, the sort and filter feature for Open Instances, Instance History, Route Masters, and Steps now contains the following additional functionalities:
  • You can now sort data in all the columns except the Last Reading and Photo Evidence columns on the Steps page.
  • You can now filter data in all the columns except the following columns:
    • Date and Entity Key columns
    • Last Reading and Photo Evidence columns in the Steps page.
US575808
Table 40. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, when you attempted to create a route, a timeout error occurred, especially for a large route master. This issue has been resolved. Now, timeout errors have been reduced significantly even for large routes.US606806
Previously, when you created Steps using a Data Loader, the order of the picklist items in the Step did not match the order provided in the Data Loader. This issue has been resolved.US587093
Previously, in the Rounds Pro Manager pages, dates were not displayed as per the user culture setting. This issues has been resolved.DE209587
Previously, if the route schedule was set to Active, the Route Master Data Loader could not upload that route. This issue has been resolved.DE207232
Previously, if you removed a limit, the corresponding warning message was also removed. This issue has been resolved. Now, limit-related messages are retained even if the limit values are modified or deleted.DE201133

Rules

This topic provides a list of product changes released for this module in this version.

Table 41. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, when you compiled VB rules with the Rule Compile Utility, the compiler failed with a library reference error. This issue has been resolved.DE209634

SAP Adapters

This topic provides a list of product changes released for this module in this version.

Table 42. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, when you created a Notification from an Inspection Task in SAP through SAP-PI, the mapping was incorrect. This issue has been resolved.DE209479

Security Manager

This topic provides a list of product changes released for this module in this version.

Table 43. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, the function used for navigation generated a blank record every time the search was performed. As a result, the Home item appeared blank in the navigation pane. This issue has been resolved. Now, the function is no longer used; the logic for navigation is added in the UI element itself.DE204567

SIS Management

This topic provides a list of product changes released for this module in this version.

Table 44. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
To improve usability, the field Automatic Channel Count is set to True and is disabled for Protective Instrument Loop logic solvers for ExSILentia V4 Loops. US601998
Table 45. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID
Previously, when you created a custom Protective Instrument Device (Sensor) in the Custom Failure Data section, the Trip State field was disabled. This issue has been resolved.DE208475
Previously, for a Protective Instrument Loop, when you attempted to link or unlink either a Protective Instrument Loop System, an error occurred. This issue has been resolved.DE207797
Previously, if the Hazards Analysis and Management of Change licenses were inactive, and if you attempted to access the Team Members section of an SIL analysis, an error occurred. This issue has been resolved.DE204885
Previously, when you printed the SRS report, the page layout of the PDF file did not appear as expected. This issue has been resolved.DE203752

Thickness Monitoring

This topic provides a list of product changes released for this module in this version.

Table 46. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
To enhance usabilty, in the Thickness Monitoring Datalogger page, when using the Olympus 38DL+ datalogger device, you can now choose to send a desired Inspector’s name when sending TMLs to the device. To facilitate this enhancement, when the Send To Device window appears, you can now select a value in the Inspector drop-down menu for each file being sent. If the current user is a TM Inspector, their name will be selected by default. The value selected in this drop-down menu will be used to populate the Measurement Taken By field of new measurement records after receiving and saving new readings in the Receive From tab.US569534
Table 47. Resolved Issues

The following issues, which existed in one or more previous versions, have been resolved.

DescriptionTracking ID

Previously, on the Measurement Data Entry page in Thickness Monitoring, it was possible to click the Save or Save and Calculate button multiple times resulting in duplicate Thickness Measurement records being created. This issue has been resolved.

DE209596
Previously, when you updated data of the Corrosion Analysis Setting of a TML, the TML Corrosion Analysis was not updated correctly during the calculation. This issue has been resolved.DE209137
Previously, the Minimum Thickness Type field was updated for TMLs that were not selected for calculation, when saved on the TMin Calculator Screen. This issue has been resolved.DE208365