IMPORTANT Actions and Considerations
REPLACED OR REMOVED FEATURES
From time to time, Oracle replaces existing cloud services with new features, or removes existing features. Replaced features may be put on a path to removal. As a best practice, you should use the newer version of a replaced feature as soon as a newer version is available.
This section identifies the features in this Cloud service that have been replaced or removed.
Product | Removed Feature | Target Removal | Replacement Feature | Replaced In | Additional Information |
---|---|---|---|---|---|
Oracle Utilities Application Framework | Legacy User Experience (OPE) | 24B | Redwood User Experience | 23B | Turning off OPE as an alternative and removing the engine |
Oracle Utilities Application Framework | Batch Run Statistics | 24B | Batch Run Portal | 24A | Removing Batch Run Statistics zone |
Unless otherwise specified below, these notes are for informational purposes and no action is required.
PLANNED REMOVAL
Plan to Remove Cube Viewer Support from Oracle Utilities Application Framework
In the future, the product plans to remove support for the Cube Viewer.
Note that this includes support for the F1-COLOR characteristic type that is only used by Cube Viewer. The product uses the F1-Color extendable lookup going forward.
Plan to Remove Support for Previous User Experience from Oracle Utilities Application Framework
In the current release, the product provides an option to Switch UI View. This changes the current user experience for the user for that session. Assuming the user is in the latest user experience (referred to as Redwood), this action switches the user experience to the previous look-and-feel.
In the future, the product plans to remove support for the ability to switch that design that preceded Redwood.
Plan to Remove Support for Guiding Business Process Assistant (BPA) Scripts from Oracle Utilities Application Framework
In the current release, the product supports guiding BPA scripts that surf on top of one or more application pages and interact with these pages in parallel to script execution. This approach is considered legacy functionality and as such limited to fixed pages. It does not work with portal pages.
In the future, the product plans to remove support for such scripts.
Plan to Remove Workflow and Notification Metadata and Database Tables from Oracle Utilities Application Framework
Workflow and notification functionality supported exchanging messages with an external system (notification) and providing a configurable process for acting on incoming messages (workflow). More recently, the functionality for managing external messages is supported using Outbound Message and Inbound Web Service functionality. In addition, there are several features to support processing incoming messages. Service scripts can handle simple use cases. For more complicated processes, the service task or other business object driven objects are available.
The metadata and database tables related to this feature will be removed in a future release. Note that only a portion of the functionality for this feature is managed by Oracle Utilities Application Framework. Most of the functionality is supported in the Oracle Utilities Customer Care and Billing product.
Plan to Remove Mobile Application Framework Metadata from Oracle Utilities Application Framework
Removal of support for the Mobile Application Framework has already been announced in a previous release. However, there is metadata still included in the application related to this functionality.
The metadata will be removed in a future release.
Plan to Remove Key Ring Validation Scripts, Algorithm Types, and Algorithms from Oracle Utilities Application Framework
The product is removing all scripts, algorithm types, and algorithms that performed validation rules on the K1-SignatureKeyRing business object. The algorithms have been removed from the BO configuration. There are requirements to expand the use of a signature key ring beyond the current implementation for object file storage and the existing validations are not applicable to other planned use cases.
The following items will be removed in a future release.
- Algorithm
- K1-KRDCKFS
- K1-KRINCKFS
- Algorithm Type
- K1-KRDCKFS
- K1-KRINCKFS
- Message
- 11009 / 1402
- Plugin Script
- K1-KRDCKFS
- K1-KRINCKFS
- Service Script
- K1-ChkCfgExL
Plan to Remove UI Metadata Related to Converted Pages from Oracle Utilities Application Framework
The UI metadata related to fixed pages that have been converted to portals will be removed in a future release. The tables list the navigation keys related to each maintenance page. The related UI program component data will also be removed. Note that the metadata related to the search pages will not be removed at this time in case they are used on other fixed pages.
To Do Entry Maintenance | Table Maintenance | Message Maintenance | Display Icon Portal |
---|---|---|---|
toDoEntryCharGrid |
metaDataTableFieldsGrid |
msgMaintDetailsPage |
displayIconRefMaint |
toDoEntryDrillKeyValuesListGrd |
metaDataTableMainPage |
msgMaintGrid |
|
toDoEntrySortKeyValuesListGrid |
metaDataTableCFldsGrid |
msgMaintPage |
|
todoentrykeyvalue |
metaDataTableConstPage |
msgMaintTabMenu |
|
todoentrymain |
metaDataTableMaint |
Any help navigation keys |
|
toDoEntryMaint |
metaDataTableRefByConstPage |
||
toDoEntryPopupAdd |
metaDataTableFieldPage |
||
toDoEntryPopupForward |
Any help navigation keys |
||
toDoEntryPopupSendBack |
|||
Any help navigation keys |
Business Object Portal | Lookup Portal | Algorithm Portal | User Group Portal |
---|---|---|---|
businessObjectAccordionPage |
ctLookUpMaintListGrid |
algorithmMainGrid |
userGroupMainPage |
businessObjectAccordionPrtPage |
ctLookUpMaintMainPage |
algorithmMainPage |
userGroupProfileGrid |
businessObjectAlgorithmsGrid |
Any help navigation keys |
algorithmTab |
userGroupProfilePage |
businessObjectAlgorithmsPage |
Any help navigation keys |
userGroupTabMenu |
|
businessObjectLifecyclePage |
userGroupTabMenu2 |
||
businessObjectMainPage |
userGroupUserGrid |
||
businessObjectOptTypeGrid |
userGroupUserPage |
||
businessObjectSchemaPage |
Any help navigation keys |
||
businessObjectStatAlgGrid |
|||
businessObjectStatTRRuleGrid |
|||
businessObjectStatusOptionGrid |
|||
businessObjectSummaryOptTree |
|||
businessObjectSummaryPage |
|||
businessObjectSummaryUseTree |
|||
businessObjectTabMenu |
Plan to Remove Miscellaneous System Data from Oracle Utilities Application Framework
The following metadata is no longer in use and will be removed in a future release:
Object | Data | Description/Comments |
---|---|---|
Lookup Value |
CHAR_ENTITY_FLG / F1SE |
Characteristic Entity / Sync Request Inbound Exception |
Script |
F1-TDMgActSS |
To Do Management - Process Actions (Deprecated) / Replaced by F1TDMgActSS |
Script |
F1AddDebugLg |
Add Log for Monitoring Probe (Deprecated) / Replaced by a BS - F1-MONPRBLOG |
Script | F1MgOlmpMnt | Not in use by base functionality. |
Script | F1MgoSqlPks | Not in use by base functionality. |
Script | F1MgOlmpPst | Not in use by base functionality. |
UI Map | F1-MigrObjectImportMaintenance | Not in use by base functionality. |
Zone |
F1-BOMOSRCH |
Not in use by base functionality. |
Zone |
F1-CATCHSCH |
Not in use by base functionality. |
Zone |
F1-MONAVKEY |
Not in use by base functionality. |
Zone |
F1-REVCONQRY |
Not in use by base functionality. |
Plan to Remove XSLT Managed Content Type from Oracle Utilities Application Framework
Entries in the Managed Content table related to XSL should be using the XSLTC managed content type and not the XSLT managed content type. In a future release, the XSLT managed content type will no longer be supported.
Plan to Remove REST IWS - Original REST Servlet from Oracle Utilities Application Framework
The original URL supplied for invoking IWS based REST services included the IWS Service name in its makeup. Support for this will continue for backward compatibility purposes, but it will be deprecated in a future release. You should adjust your existing integrations to use the currently supported URL.
Plan to Remove Append Setting from Pagination - Oracle Utilities Application Framework
There are several known issues with the functionality of the "append" option in pagination. It is recommended that you do not use this pagination setting.
Plan to Remove Support for Master/Subordinate Servers for Web Service Catalog in Oracle Utilities Application Framework
The Service Catalog Configuration (master configuration) enables you to define subordinate servers. Defining subordinate servers is no longer applicable for the Oracle Integration Cloud.
Plan to Remove Support for Batch Run Statistics Portal / Sidebar Zone from Oracle Utilities Application Framework
The Batch Run Statistics portal provides additional information about batch runs. This portal was accessible from the original Batch Job Submission fixed page. Most functionality in the Batch Run Statistics portal is now visible in the Batch Run portal. There were additional functionality on the Batch Run Statistics portal related to capturing additional information from an external tool. This information is not supported in a future release.
Plan to Remove Business Object Read from F1-MAINPROC When Pre-processing Exists
In the original implementation of configuration tools, the main framework maintenance BPA (F1-MainProc) did not perform a Read of the BO when a pre-processing script was linked to the BO via options. The pre-processing script was responsible for the Read.
In a subsequent release, a BO Read was added in F1-MainProc (even if a pre-processing script existed) to resolve a UI Hint issue related to child business objects. This solution introduced a problem only visible for specific scenarios and a different fix has been introduced. The new fix made the BO Read unnecessary in F1-MainProc. Because there are many pre-processing scripts that are properly performing the Read of the BO, ideally the BO Read should be removed from F1-MainProc so that multiple reads are not performed. However, there may have been pre-processing scripts introduced after the BO Read was included in F1-MainProc that were coded to not perform a BO read in the pre-processing script. Due to this situation, the BO Read is still performed as part of the processing of F1-MainProc.
When a pre-processing script exists, we plan to remove the BO Read from F1-MainProc logic. You should review your custom pre-processing scripts that are linked to your BO options to ensure that they properly perform a Read of your BO.
Plan to Remove Legacy User Experience (OPE) from Oracle Utilities Application Framework
As part of the Oracle policy to move all user experiences to Redwood, the legacy user experience known as OPE (OPower Enterprise) will be disabled and replaced with Redwood from Oracle Utilities Application Framework 24.2.0.0.0 (24B) and above. As part of that change, the following will be implemented:
- The Redwood experience will be the only experience available for all customers.
- The user experience settings and switch between user experiences will be nullified.
- The existing legacy rendering engine will be removed from the product.
This change prepares the products for the implementation of the new Oracle rendering engine, which will be transparent to customers, which is optimized for the Redwood user experience to help deliver innovative and intuitive user experiences for our customers that are consistent across Oracle's portfolio of products.
Plan to Remove Batch Run Statistics Zone from Oracle Utilities Application Framework
With the introduction of the new Batch Run portal, Batch Day Dashboard and Batch Analytics, the usefulness of the Batch Run Statistics zone is limited and therefore will be removed from Oracle Utilities Application Framework 24.2.0.0.0 (24B) and above releases. Information on that zone is now available in the new portals.
Plan to Remove Miscellaneous System Data from Oracle Utilities Customer Care and Billing Cloud Service
The following metadata is no longer in use and will be removed in a future release:
Object | Data | Description/Comments |
---|---|---|
Managed Content |
C1-LeadOutcomeChart |
Not in use by base functionality. |
Managed Content |
C1-PPBBillSegmentsChart |
Not in use by base functionality. |
Managed Content |
C1-URSQIntervalChart |
Not in use by base functionality. |
Managed Content |
C1-VectorChart |
Not in use by base functionality. |
NOTE: For the succeeding Program Name data, in a prior release Oracle announced that many batch controls for Credit and Collection, and Batch Billing were enhanced to plugin-driven batches to allow customization of the Select Record logic. Each batch control references a specific Java batch program that replaced its older converted COBOL counterpart. These converted COBOLs are planned to be removed in a future release. If your implementation has any custom batch controls that still references the old converted COBOLs, these need to be updated to use the supported counterpart Java program. Refer to the delivered batch controls to know the program name, batch parameters, and Select Record algorithm necessary to use on your custom batch controls to continue using these.
Object | Data | Description/Comments |
---|---|---|
Program Name |
CIPBBILB (was used by the BILLING batch control) |
Not in use by base functionality. |
Program Name |
CIPLADMB (was used by the ADM batch control) |
Not in use by base functionality. |
Program Name |
CIPLCETB (was used by the CET batch control) |
Not in use by base functionality. |
Program Name |
CIPLCPMB (was used by the CPM batch control) |
Not in use by base functionality. |
Program Name |
CIPLSETB (was used by the SET batch control) |
Not in use by base functionality. |
Program Name |
CIPLSECB (was used by the SEC batch control) |
Not in use by base functionality. |
Program Name |
CIPLSEDB (was used by the SED batch control) |
Not in use by base functionality. |
Program Name |
CIPLWMOB (was used by the WPM batch control) |
Not in use by base functionality. |
Program Name |
CIPLWETB (was used by the WET batch control) |
Not in use by base functionality. |
Program Name |
CIPLOVMB (was used by the C1-ADMOV batch control) |
Not in use by base functionality. |