OPT IN FEATURES WITH FUTURE EXPIRATION
The features in the table below were originally delivered as Opt In but will, in a future update, no longer require Opt In to enable. You may still need to do some additional setup or configuration, as indicated in Column C. This advance notice of upcoming Opt In Expiration will help you plan for these changes. Once the Opt In has expired the feature will be included in the table above.
Important Note: If you have already enabled these features then NO further action is necessary.
| (A) | (B) | (C) | |||
|---|---|---|---|---|---|
| Feature | Module |
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 24C | |||||
| Track Affected Object Redlines and Other Updates on Changes | Product Lifecycle Management Common | 24C | 25A |  | |
| Update 24B | |||||
| Process Child Organization Item Changes and Master Organization Item Approvals Concurrently | Product Hub | 24B | 24D | (1) | |
| Add or Remove Approver Roles During Approvals | Product Lifecycle Management Common | 24B | 24D | (1) | |
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.
(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.