FEATURES ORIGINALLY ENABLED VIA THE OPT IN USER INTERFACE
The features in the table below were originally delivered Disabled. That is, the features required you to take action in the Opt In UI to enable for end users (plus possibly take additional setup or configuration steps). Column A shows when these features were originally delivered.
Beginning in the update version specified in Column B, these features will no longer require the Opt In UI to enable for end users. However, you may still need to take additional setup or configuration steps to enable the feature, per Column C. If additonal customer action is still required to enable, click on the feature name to get more information.
Important Note: If you have already enabled these features in the Opt–In UI then NO further action is necessary.
| (A) | (B) | (C) | |||
|---|---|---|---|---|---|
| Feature | Product |
Feature *Required* the Opt In UI to Enable, Originally Delivered in: |
Feature *No Longer Requires* the Opt In UI to Enable, Beginning in: |
Action still required to enable for end users? | |
| NO, Delivered Ready to Use |
YES, Customer Action Still Required |
||||
| Update 19C | |||||
| Deactivate a Work Definition | Maintenance | 19A | 19C |  (1) | |
| Update 19B | |||||
| View and Edit Meter Reading Transaction History | Maintenance | 18C | 19B | (2) | |
| Display Additional Asset Information | Maintenance | 18C | 19B | (2) | |
| Use Resource Instances in Manufacturing and Maintenance | Maintenance | 18C | 19B | | |
| Manage Maintenance Programs Through Maintenance Interval Optimization | Maintenance | 18C | 19B | (2) | |
| Manage Maintenance Work Orders Based on IoT Events | Maintenance | 18C | 19B | (1) | |
| Manage Maintenance Programs Using Asset Meters and Events | Maintenance | 18C | 19B | (2) | |
| Update 19A | |||||
| Delete a Work Definition | Maintenance | 18B | 19A | (1) | |
(1) SMALL Scale UI or Process-Based Feature: These features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
(2) LARGER Scale UI or Process-Based Feature: These features have more complex designs. Therefore, the potential impact to users is higher, meaning these features should be the focus of customer acceptance testing.