V5.0.2.0.0

APM Connect

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

Table 1. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
To improve usability, a new configurable option is added to chunk data and load data in sequence, such that there is no duplication. In the Data Loader Framework, to chunk the data in the given sheet, add a new column with following Caption and Name in the Configuration sheet:
  • Caption: Number of rows to be chunked together
  • Name: OPTION_NUMBER_ROWS_TO_CHUNK
US581687
Table 2. Resolved Issues

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

DescriptionTracking ID
Previously, in ADL, the GAA Event Data Loader folder name was spelled incorrectly, and this was causing an issue in the file upload. This issue has been resolved. Now, the folder name is corrected to GAA Events Data Loader to fix the file upload issue. DE202907
Table 3. Known Issues and Limitations

The following known issues and limitations exist.

DescriptionTracking ID
When you attempt to create and update relationships for a Health Indicator through the APM Family data loader, the data loader does not move from the Ingest stage and data is not added into APM. For additional information and work around, refer to the KBA 000044251.DE194409

Asset Hierarchy

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

Table 4. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
To enhance usability of the Asset Groups page:
  • You can now search for assets within the group.
  • A summary of the number of assets that you have selected to add or remove from the groups appears until you save the group.
DE191165

Calibration Management

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 enabled State Management functionality in Calibration Task family, the State Management component was not loaded on the Calibration Task datasheet. This issue has been resolved.DE202053

Data Loaders

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

Table 6. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
To improve usability, a new configurable option is added to chunk data and load data in sequence, such that there is no duplication. In the Data Loader Framework, to chunk the data in the given sheet, add a new column with following Caption and Name in the Configuration sheet:
  • Caption: Number of rows to be chunked together
  • Name: OPTION_NUMBER_ROWS_TO_CHUNK
US581687
Table 7. Resolved Issues

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

DescriptionTracking ID
Previously, when you attempted to load data into APM using a Batch Type Data Loader, no error message appeared if the Batch Key Field value was blank or null. This issue has been resolved. Now, an error message appears indicating that the Batch Key Field value is blank or null.DE202169
Previously, when a user, whose time zone was set to International Date Line West, loaded a null data field values into APM using the Family Data Loader, then the date value for the field was displayed as July 5, 1776. This issue has been resolved. Now, all null date field values are loaded as null values, regardless of the user’s time zone.DE201838
Table 8. Known Issues and Limitations

The following known issues and limitations exist.

DescriptionTracking ID
When you attempt to create and update relationships for a Health Indicator through the APM Family data loader, the data loader does not move from the Ingest stage and data is not added into APM. For additional information and work around, refer to the KBA 000044251.DE194409

Datasets

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

Table 9. Resolved Issues

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

DescriptionTracking ID
Previously, if you created a dataset using an Excel spreadsheet containing a period (.) in a column name, and if it was used as a header, the column name appeared blank in the preview and after saving the dataset. This issue has been resolved. Now, in this scenario, the period (.) is converted into an underscore (_).DE200615

Family Policies

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

Table 10. Resolved Issues

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

DescriptionTracking ID
Previously, when you executed a policy, the message "An unexpected error occurred when upgrading policy with key <...>" appeared in the execution log. This issue has been resolved.DE200396

Foundation

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

Table 11. Resolved Issues

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

DescriptionTracking ID
To address a known vulnerability in the third-party library, all references to JQueryUI have been removed from the APM code.DE199928

General Dashboards

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

Table 12. Resolved Issues

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

DescriptionTracking ID
Previously, when you attempted to open a query from the Query widget, if the percent (%) wildcard character was used in a query parameter, the parameter was incorrectly encoded, and the query results did not appear as expected. This issue has been resolved.DE192480

Import and Export

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, partial export of a file did not work. This issue has been resolved. You can now download partially exported files.US585598

Inspection Management

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 viewing an inspection in the APM web-client that was currently checked-out to an inspector, the state transition control on the Inspection page would allow you to still transition the state. This issue has been resolved. The state transition control will still allow management of assigned users, but you will be unable to change the current state of the inspection until it has been checked in.DE201806
Previously, when viewing images using the image gallery available in the Inspection page, if the associated reference document referenced to a URL or a UNC path, the reference document failed to load. This issue has been resolved.DE201352

Integrity Mobile

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

Table 15. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
To enhance usability, when deploying Integrity Mobile as part of a corporate Mobile Device Management solution, it is now possible to pre-configure the desired Server URL and Datasource fields instead of providing the details manually. After configuration, the Server Settings screen appears momentarily but will automatically apply the settings and move on to the Login page. The ability to provide managed configurations is available for both Android and iOS apps.
  • US587439
  • US581716
To enhance usability, you can now check out multiple inspections simultaneously. To download the Inspection History Report with the inspections, you can enable the Download Inspection History Report setting on the Users Settings page.US569760
Language Localization support has been introduced in this release. All text will appear in the logged-in user’s language within the Integrity Mobile application.US527921
User Culture support has been introduced in this release. All culture-applicable fields will appear in the logged-in user’s culture within the Integrity Mobile application.
Note: This feature is supported on the APM server 5.0.2 and later. Also, the language/culture of the mobile device must match the culture of the logged-in user.
US532352
Table 16. Resolved Issues

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

DescriptionTracking ID
Previously, when logging into Integrity Mobile, if a space was to the end of the username, the login was stalled infinitely. This issue has been resolved.DE202451
Previously, when you rotated the orientation of the device on an Android device, the application would restart. This issue has been resolved.DE202440
Previously, if you were not assigned the Integrity Mobile User Security Role, or if the Integrity Mobile license was not applied, and if you attempted to log in using an on-premises SSO configuration, the correct error message did not appear. This issue has been resolved.DE200552
Previously, if you installed a self-signed certificate issued by a trusted source such as your corporate CA, the Integrity Mobile application did not trust the certificate and you could not log in. This issue has been resolved.DE200551
Previously, the full text for Inspection Task Details field was not displayed in the offline Inspection form. This issue has been resolved.DE187211

Policy Designer

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 ensure that content protection and revert to baseline features operate as expected, you can no longer modify the Name field in a baseline Policy record.
Note: If you have already modified the name of a baseline Policy, you can no longer edit the name. However, if you revert the policy to baseline, the name will be reverted to the original name.
US580861
To improve usability, the Rounds Pro module users can now access records from Measurement Step family and view information about related readings. The new Input Node is added that replicates the Measurement step node functionality. US579505
Table 18. Resolved Issues

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

DescriptionTracking ID
Previously, in the Design workspace of a policy, when you selected Execute Now, sometimes, the policy was not executed. This issue has been resolved.US588802
Previously, if the ActiveMQ server failed over or was restarted, scheduled policy executions were not executed as expected. This issue has been resolved.DE201020
Previously, when you executed a policy, the message "An unexpected error occurred when upgrading policy with key <...>" appeared in the execution log. This issue has been resolved.DE200396
Previously, email notifications for policy executions and policy execution history were in English, with numbers and dates formatted according to US culture, regardless of the language and culture settings of the policy execution service user (that is, MIJOB). This issue has been resolved.DE194065
Table 19. Known Issues

The following known issues and limitations exist.

DescriptionTracking ID
If you schedule a policy with a large number of instances, some of the policy instances are executed more than once at the same scheduled execution time.US595325

Production Loss Analysis

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

Table 20. Resolved Issues

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

DescriptionTracking ID
Previously, in the PLA Admin page, if there were a large number of Event Code records, a timeout error occurred. This issue has been resolved. Now, pagination is available, such that you can access only 10 records per page, therefore, eliminating the timeout error.US587515
Previously, for Production Data, Production Plan(s), Production Events, and Production Analyses, the PLA Overview Count took longer than expected to load. This issue has been resolved. Now, the tiles in the PLA Overview page load quickly.DE201449
Previously, in a Production Event datasheet, if you attempted to select the Production Event Code without selecting the Unit, the record failed to load. This issue has been resolved.DE200771

Queries

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

Table 21. Resolved Issues

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

DescriptionTracking ID
Previously, when you executed a delete query, an incorrect error message appeared, whenever there was an error during the execution of the delete query. This issue has been resolved.DE201345

Record Manager

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

Table 22. Resolved Issues

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

DescriptionTracking ID
Previously, when you executed a Conditional Alert that used a query containing prompts, the query was not processed, and the Conditional Alert email was not sent. This issue has been resolved.US585597
Previously, when the Format behaviour for the date field was set as ShortDate then the value in the Date field was shifted backward by one day. This issue has been resolved.DE202705
Previously, if state management was enabled for a family, metadata created for the state field MI_SM_STATE_KEY_N was long. This issue has been resolved. Now, metadata for the state field MI_SM_STATE_KEY_N is created with character(50) (instead of long) and the IsKey flag.DE202418
Previously, if you accessed a record assigned to the Global site, and then added a new related record, the newly created record was assigned to your default site. This issue has been resolved. Now, in this scenario, the new record is assigned to the Global site.DE202055
Previously, when you selected External Network in the Edit Document Path window for a Reference Document, the list of folders and files appeared in random order. This issue has been resolved. Now, the folders and files are sorted alphabetically.DE200025
Previously, if you opened a record using a hyperlink with the #record-manager/<key>?datasheetid=<id> format, modified the record, and then switched to a different module or application without saving your changes, your changes were not retained. This issue has been resolved.DE198432
Previously, when you selected a detail record in a master/detail datasheet, the Unlink option was not always enabled as expected. This issue has been resolved. Now, the Unlink option is enabled if the Allow for Unlinking check box is selected in the master/detail datasheet definition and you have Delete privileges for the relationship between the master family and the detail family.DE93826

Risk Based Inspection

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

RBI 580 and RBI 581

Table 23. Resolved Issues

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

DescriptionTracking ID
Previously, while clicking on +Create Inspection Plan link an error occurred if the Asset had any inactive RBI Components and the RBI Admin Preference, Use Alternative Inspection Plan, was set to true. This issue has been resolved. Now, only active RBI Components are considered while creating an Alternative Inspection Plan.DE200602
Previously, RBI Components with Component Status field set to NULL were not considered as an active component in the following scenarios:
  • Suggest PDMs for Components option in Asset Summary and Corrosion Loop Summary page
  • Link Protected Components option for PRD Components related to Corrosion Loop
  • Component dropdown in Inspection plan Detail section in Inspection Plan page
  • RBI Component dropdown in Inspection confidence section in Inspection page
  • RBI Component dropdown in Inspection Profile datasheet

This issue has been resolved.

DE199690

RBI 581

Table 24. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID

The formula for calculating Final Corrosion Rate on RBI 581 External Damage Evaluations now adheres to API 581 3rd Edition, Addendum 2. To facilitate this enhancement, all corrosion rate adjustment factors will only be applied when the Source of Calculated Corrosion Rate field is set to Calculated. You can override this option by selecting the Use Corrosion Rate Adjustment Factors for External Corrosion Damage Mechanisms option in the RBI Application Settings.

US590532
The Age calculation on RBI 581 Cracking Damage Evaluations and RBI 581 External Cracking Damage Evaluations only considers the effective inspections now. To facilitate this enhancement, if the Highest Effective Inspection Level is Poorly Effective or Ineffective(None), the Date in Service is used instead of the Target Inspection Date in the Age and the Time Since Last Inspection calculations.US582724

Rounds Designer

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

Table 25. Resolved Issues

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

DescriptionTracking ID
Previously, if you attempted to load Readings data using the Rounds Readings Data Loader without providing a value for MI_READING0_RELAT_ML_ENTIT_KEY_N, an error occurred. This issue has been resolved. Now, you can choose between providing any of the following values:
  • MI_READING0_RELAT_ML_ENTIT_KEY_N
  • MI_CHECK_PT_CHEC_ID_C
DE194630

Rounds Pro

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

Table 26. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
To improve usability, Round Pro now supports the following User Culture settings:
  • Numeric Values: You can now enter numeric values with decimal point or comma
  • Date Values: You can now enter date values in dd/mm/yyyy or mm/dd/yyyy format
US579664
Table 27. Resolved Issues

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

DescriptionTracking ID
Previously, when you scheduled route instance generation to end after n occurrences, only n-1 route instances were created (for example, if you set the schedule to end after three occurrences, only two route instances were created). This issue has been resolved.DE185702
Table 28. Known Issues and Limitations

The following known issues and limitations exist.

DescriptionTracking ID
Some users cannot create Health Indicators from Measurement Steps.
Workaround: For the Rounds Pro Security Groups, add permissions to the Analysis family as described in the following table.
Security GroupPermissions
MI Rounds-Pro Administrator
  • View
  • Insert
  • Update
  • Delete
MI Rounds-Pro Mobile UserView
For more information, refer to KBA 000068522.
US583188
When you attempt to import data into APM using Rounds Pro Data Loader, and if there is an error in the data, then the error message is not displayed row wise.
Note: Download the log file to view the errors.
DE202474

Root Cause Analysis

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 the RCA Recommendations, when you attempted to assign a target completion date that was in the past, an error message appeared that did not provide details on the error. This issue has been resolved. Now, a detailed informational error message appears.DE202039

Rules Editor

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, the Rules Editor loaded slowly while opening Microsoft Visual Studio and loading Libraries. This issue has been resolved.DE198869

SAP Adapters

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, during the Work Order generation, if the Task Details contained multiple blank lines (EOL), an error message appeared, and the Work Order was not generated. This issue has been resolved.US591545
Previously, if text fields in the Work Order and Strategy interfaces contained special xml characters, an error occurred. This issue has been resolved.DE189175

Security Manager

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

Table 33. 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 new security user by copying and saving an existing security user, an error occurred. This issue has been resolved.

DE201852
Previously, while using the APM application installed on a non-English language OS like Japanese, when a user tried to change the default language or default culture from User Defaults page, the user encountered an error and could not change the default value. This issue has been resolved. Now, the user can change the user defaults without any error.DE200206
Previously, on the LDAP page, if the LDAP Sync Domain Settings box was set to Deactivate Unsynced Users, after the LDAP synchronization was run, some of the synchronized users were incorrectly deactivated. This issue has been resolved. To facilitate this fix, the comparison between LDAP users and APM users is now case-insensitive.DE199797

SIS Management

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

Table 34. Resolved Issues

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

DescriptionTracking ID
Previously, you could update an SRS Template even if it was not in the initial state (that is, In Progress). This issue has been resolved.DE203393
Previously, when you created a Safety Instrumented System and selected an SRS Project in the SRS Project ID field, the selected SRS Project was not populated until you saved the record. This issue has been resolved.DE202905
Previously, when you tried to import an .exp file having custom devices, the import screen failed to load the list of Safety Instrumented Functions (SIFs). This issue has been resolved.DE202855
Previously, if Calculation Engine for any Protective Instrument Loop was ExSILentia V4, then SFF and Base SFF values for Protective Instrument Loop Final Element and Protective Instrument Loop Sensor were not getting populated. This issue has been resolved. Now, only the SFF value is populated; the Base SFF value is not populated as this field is not applicable for ExSILentia V4.DE202725
Previously, while printing an SRS report, you could not download the report. This issue has been resolved.DE202621
Previously, when you attempted to import from Exida, if Protective Instrument loop included more than four Protective Instrument Loop groups, the import failed without a warning or an error message. This issue has been resolved.

Now, from the selected list of loops, the loops with four or lesser number of groups is imported, and a warning message is displayed for the loops with more than four groups.

DE199672

Strategy Macros

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

Table 35. Resolved Issues

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

DescriptionTracking ID
Previously, the strategy macro job was executed with the MIJOB user instead of the user selected in the runAs box when scheduling a strategy macro job. This issue has been resolved. Now, the user selected in the runAs box is considered during the execution of the strategy macro job.DE203428

Teams

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, as a Super User, when you specified a site for a Team, then added team members, the list of available users was not limited to users with access to the specified site. This issue has been resolved.DE199660

Thickness Monitoring

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, if a TML group or an Asset contained a large number of TMLs, you could not spread the Corrosion Analysis Settings from the TML Group or Asset to the Thickness Measurement Location. This issue has now been resolved.DE199214