OSM Mobile 3​.0 release notes

New features

These features are new in AVEVA™ Operational Safety Management Mobile 3.0 application.

Sign in to mobile application with email

It's now possible to sign in to OSM mobile application with either Windows Active Directory username (domain\username) or email address.

Isolation Lists

• Search for and look at details of an isolation list.

• Add isolation lists to your My work list.

• Process the workflow of an isolation list.

• Add and view attachments.

• Work with isolation points, such as:

  • View and add signatures for a point

  • View and change comments

  • View and change locks

  • View and change the state of isolation points

Software fixes

The following software defects have been resolved in AVEVA™ Operational Safety Management Mobile 3.0.

None.

Known issues

This release of AVEVA™ Operational Safety Management Mobile contains the following known issues. Whenever possible, we will provide a workaround.

3651614 - List of "Equipment to be isolated" appears in duplicate

When a user performs a workflow for an isolation list, occasionally the list of "Equipment to be isolated" can be appear duplicated. This is just a visual error.

Workaround: To see the correct list, refresh the isolation list.

Applies to OSM Mobile Versions: 3.0

3904075 - Rendering error performing action on iOS

Sometimes, when performing an action in the OSM Mobile app on iOS platform, the screen can appear to display half of one screen and half of another screen. This is a visual error caused by .NET MAUI.

Workaround: You can correct this by moving forwards and backwards to refresh the screen.

Applies to OSM Mobile Versions: 3.0

3924873 - Incorrect radio button state for System lock on iOS

In Isolations module, it is possible to add only one System lock. However, in the iOS operating system, when adding locks, it may appear that it is possible to add a second System lock, but it is not. This is a bug of the iOS operating system that the radio button appears in the wrong state.

Workaround: None.

Applies to OSM Mobile Versions: 3.0