IMPORTANT Actions and Considerations

REGRESSION TESTING RECOMMENDATIONS

Refer to Regression Testing Recommendations in the Oracle Utilities Cloud Services Live Operations Guide for recommendations related to testing when upgrading to a new cloud service release.

PLANNED ADDITION

ILM Compression jobs will run internally (like the ILM Add Partition job) by Oracle starting with the 26.10 release. Customers should start running both measurement and non-measurement compression jobs in any test-sized environment, followed by Production environments. All ILM applicable table partitions MUST be compressed before upgrading to 26.10 in all Test and Production environments. Failure to do so may have performance impact to the online application following the upgrade to the 26.10 release.

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	Cube Viewer	26.4	Not applicable	N/A	This functionality is no longer supported. Metadata is no longer delivered to new customers. For upgrading customers, the metadata related to this functionality is updated to be CM owned for backward compatibility purposes.
Oracle Utilities Application Framework	Table Legacy Page Metadata	26.4	Portal-based User Interface	21A / 4.4.0.3.0	Navigation keys removed: mdTableRefByConstFieldsGrid, mdTableRefCnstFieldsGrid, metaDataTableCFldsGrid, metaDataTableConstPage, metaDataTableConstPage_H, metaDataTableFieldPage, metaDataTableFieldPage_H, metaDataTableFieldsGrid, metaDataTableMainPage, metaDataTableMainPage_H, metaDataTableMaint, metaDataTableRefByConstPage, metaDataTableRefByConstPage_H, utilTableTabMenu Records in the UI metadata program component tables related to the above navigation keys were removed. In addition, the following fields were removed: F1_CONST_FLD_SUMM, F1_CONST_FLD2_SUMM, F1_CONST_FLD3_SUMM, F1_TBF_SUMM, SNAME_CIPETBLTM
Oracle Utilities Application Framework	To Do Entry Legacy Page Metadata	26.4	Portal-based User Interface	21A / 4.4.0.3.0	Navigation keys removed: toDoEntryCharGrid, toDoEntryDrillKeyValuesListGrd, todoentrykeyvalue, todoentrykeyvalue_H, todoentrymain, todoentrymain_H, toDoEntryMaint, toDoEntryPopupAdd, toDoEntryPopupForward, toDoEntryPopupSendBack, toDoEntrySortKeyValuesListGrid, toDoLogGrid Records in the UI metadata program component tables related to the above navigation keys were removed. In addition, the following fields were removed: F1_TD_ENTRY_DRLKY_SUMM, F1_TD_ENTRY_SRTKY_SUMM, F1_TD_LOG_SUMM, SNAME_CIPQTDEPTM, TITLE_CIPQTDEPAP
Oracle Utilities Application Framework	User Group Legacy Page Metadata	26.4	Portal-based User Interface	23A / 4.5.0.1.1	Navigation keys removed: userGroupMainPage, userGroupMainPage_H, userGroupProfileGrid, userGroupProfilePage, userGroupProfilePage_H, userGroupTabMenu, userGroupTabMenu2, userGroupUserGrid, userGroupUserPage, userGroupUserPage_H, usrGrpAccessModesGrid, usrGrpSecurityGrid Records in the UI metadata program component tables related to the above navigation keys were removed. In addition, the following fields were removed: F1_ASC_SUMM, F1_UGP_SUMM, F1_UGS_SUMM, F1_UGU_SUMM, SNAME_CIPTUSGPTM
Oracle Utilities Application Framework	Algorithm Legacy Page Metadata	26.4	Portal-based User Interface	23A / 4.5.0.1.1	Navigation keys removed: algorithmMainGrid, algorithmMainPage, algorithmMainPage_H, algorithmTab Records in the UI metadata program component tables related to the above navigation keys were removed. In addition, the following fields were removed: F1_ALG_PARM_SUMM, SNAME_CIPTALGPTB
Cloud Service Foundation	User SYS_BTCH	26.10	New User SYS_BA	26.4
Cloud Service Foundation	User K1IPROC is no longer provided for new customers	26.10	None		K1IPROC user for existing customers will change ownership to CM.

Unless otherwise specified below, these notes are for informational purposes and no action is required.

PLANNED REPLACEMENT

Plan for Stricter Validation for String Concatenation in Groovy "Create Prepared Statement" in Oracle Utilities Application Framework

In Groovy, the string size limit when using createPreparedStatement is only 65,535. Many Groovy programmers need SQL statements that are more complex and exceed this limit. Some scripts have gotten around this by using a StringBuilder or StringBuffer method in createPreparedStatement to concatenate strings; or to concatenate a variable, which is itself a result of concatenation using StringBuilder or StringBuffer.

In a future release, this will no longer be allowed. You should change your scripts that use this technique to instead use the new method, which accepts varargs of strings: concatenateGroovyStrings(String... args). This method validates that the arguments are only strings. In addition, createPreparedStatement continues to support string concatenation using the plus (+), as long as all the arguments are literal strings.

Refer to the Using Groovy Within Scripts online help topic for information on the valid syntax to use for Groovy scripts going forward.

PLANNED REMOVAL

Plan to Remove Print Zone Option Support from Oracle Utilities Application Framework

Zones in the application currently support a "zone menu" where an option is Print Zone. In a future release, this feature will no longer be supported.

Plan to Remove Several Legacy Pages Support from Oracle Utilities Application Framework

When the Oracle Utilities Application Framework product was originally developed, there was a standard for developing UI pages that was used throughout the system. We now refer to these pages as "fixed pages". Subsequently, the product started using a new, more flexible and extendable standard, using portals and zones. All new pages created after that are built using the new standard. There is an ongoing effort to convert fixed pages to use the portal and zone technique.

There are some fixed pages where the product does not plan to ever convert the page. The reason is either because the feature is no longer actively supported or because it has been replaced with a different feature. Historically, the product has continued to support the legacy page for implementations that were previously using that functionality. However, as technology advances and browser support for certain feature changes, there will be a point in an upcoming release where the product will no longer be able to continue supporting these old pages and they will be deprecated.

The following is a list of pages that are expected to be deprecated in an upcoming release.

Script Merge
- This feature was built before the Edit Data step type was introduced. Prior to Edit Data, each script step was very specific and many individual steps were needed to create a script. The script merge was provided to make it easier to copy individual steps from one script to another. With the ability to use the Edit Data step type, it is much easier to copy script step logic from one script to another using simple text copies. Script Merge is not necessary going forward.
Supervisor To Do Assignment
- The functionality in this page can be done in the To Do Management portal or in the To Do Details tab of the To Do Dashboard portal.
Supervisor To Do Summary
- The functionality in this page can be done in the To Do Dashboard portal.
Supervisor User Summary
- This functionality will be covered in a future To Do Assignment Dashboard portal.
To Do List
- The functionality in this page can be done in the To Do Management portal or in the To Do Details tab of the To Do Dashboard portal.
To Do Summary
- The functionality in this page can be done in the To Do Dashboard portal.
To Do Search
- The management of searching for To Do entries that need to be and assigned and worked can be done in the To Do Management portal or in the To Do Details tab of the To Do Dashboard portal. Actions on To Dos related to a given To Do entry may be performed on the To Do entry page. Generally searching for To Dos, including completed To Do entries, by various criteria is planned for an upcoming release.

The following pages are planned to provide display only capability in an upcoming release.

Function
- Functions were implemented prior to the introduction of business services (BS), service scripts (SS) and business objects (BO). The recommendation for implementations going forward is to use one of the mentioned configuration tool objects in a script rather than defining a function.
XAI Inbound Service
- For backward compatibility, the product supports clients to use XAI Inbound Service deployed through IWS as SOAP services. New services should use IWS records directly configured with business services and service scripts.

Plan to Remove Support for LegacyCryptographyInstance from Oracle Utilities Application Framework

The product has not used LegacyCryptographyInstance.java for several releases now. The code itself will be removed in an upcoming release.

Plan to Remove Support for CM Java from Oracle Utilities Application Framework to Implement INSERT, UPDATE and DELETE

The system currently allows the use of prepared statements in custom Java code in the cloud that use INSERT, UPDATE or DELETE.

Support for this capability will be removed in an upcoming release. All inserts, updates, and deletes should be done through the standard methods provided by the product that handle the maintenance of records in the system.

Plan to Remove Support for the Zone Header Map from Oracle Utilities Application Framework

Currently all base delivered zone types support a parameter called Zone Header Map, which can be used to override the zone's header area. The reasons for using this may be to have more control over Actions in the header and to be able to suppress the header.

In a future release, we are no longer going to support defining a zone header map. Implementations should review any zones that are currently defining a custom zone header map. If the map is used to implement actions, use the existing zone action parameters to implement this functionality. If the map is used to suppress the header, an upcoming release will provide zone configuration to achieve this functionality.

Plan to Remove DBMS Scheduler Support from Oracle Utilities Application Framework

With the introduction of the next generation cloud scheduler, the product plans to remove specialist objects supporting the original DBMS Scheduler on the cloud.

The following inbound web services will not be supported in a future release:

F1-DBMSChain
F1-DBMSGeneral
F1-DBMSJob
F1-DBMSThread

The following business services will not be supported in a future release:

F1-DBMSCancelJob
F1-DBMSCancelSteps
F1-DBMSChain
F1-DBMSChainAddOrChange
F1-DBMSGetJobDetails
F1-DBMSGetJobRuns
F1-DBMSGetJobs
F1-DBMSJob
F1-DBMSList
F1-DBMSProgram
F1-DBMSProgramAddOrChange
F1-DBMSRestartChain
F1-DBMSRestartThread
F1-DBMSSchedule
F1-DBMSScheduleAddOrChange
F1-DBMSSubmitJob

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 Support for Workflow and Notification Functionality 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 and Java Packages from Oracle Utilities Application Framework

Removal of support for the Mobile Application Framework has already been announced in a previous release. However, there are metadata and Java packages still included in the application related to this functionality.

CM Java code that references services or methods in the ../mobile/.. package should be reviewed.

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 Type

toDoTypeAlgorithmsGrid
toDoTypeAlgorithmsPage
toDoTypeCharacteristicsGrid
toDoTypeCharacteristicsPage
toDoTypeCharGrid
toDoTypeDrillKeysListGrid
toDoTypeDrillKeysPage
toDoTypeExclListGrid
toDoTypeExclListPage
toDoTypeMainPage
toDoTypeRolesListGrid
toDoTypeRolesPage
toDoTypeSortKeysListGrid
toDoTypeSortKeysPage
toDoTypeTabMenu

Algorithm Type

algTypeMainPage
algTypeMaint
algTypeParamGrid

Service Program

serviceGrid
serviceMainPage
serviceTabMenu
serviceTree

Feature Configuration

wfmSysMainPage
wfmSysMessageGrid
wfmSysMsgPage
wfmSysOptionsGrid
wfmSysTabMenu

UI Map

uiMapMainPage
uiMapSchemaPage
uiMapTabMenu

Data Area

dataAreaMaintenanceTabPage
dataAreaSchemaPage
dataAreaTabMenu

Batch Control

batchContrAlgorithmGrid
batchContrAlgorithmPage
batchContrMainPage
batchControlMenu
batchCtrParmGrid

menuCtxt
menuIModsGrid
menuLineItemsPage
menuLinesGrid
menuMain
menuMaintMainPage
menuMaintTabMenu
menuModFlagsGrid
menuModFlagsPage
menuSub

Script

scriptMaintenanceMainPage
scriptMaintenanceStepPage
scriptMaintenanceStepAccordion
scriptStepSendFieldsGrid
scriptStepPromptsGrid
scriptStepReceiveFieldsGrid
scriptMaintenanceCopyStepPopup
scriptDataArea
scriptDataAreaGrid
scriptSchemaPage
scriptMaintenanceEligPage
scriptMaintenanceEligCritGrid
scriptTree
scriptMaintenanceTabMenu

Maintenance Object

maintenanceObjectAlgorithmsGrid
maintenanceObjectAlgorithmsPage
maintenanceObjectGrid
maintenanceObjectTabMenu
maintenanceObjectOptionsGrid
maintenanceObjectMainPage

Business Service

businessServiceMainPage
businessServiceSchemaPage
businessServiceTabMenu

Batch Run Portal

batchRunTreeMaint
batchRunTree
batchRunTreePage
batchRunMaintPage
batchRunTabMenu

Batch Job Submission Portal

batchSubmitMainPage
batchSubmitTabMenu
batchJobParmGrid

Business Object Portal

businessObjectAccordionPage
businessObjectAccordionPrtPage
businessObjectAlgorithmsGrid
businessObjectAlgorithmsPage
businessObjectLifecyclePage
businessObjectMainPage
businessObjectOptTypeGrid
businessObjectSchemaPage
businessObjectStatAlgGrid
businessObjectStatTRRuleGrid
businessObjectStatusOptionGrid
businessObjectSummaryOptTree
businessObjectSummaryPage
businessObjectSummaryUseTree
businessObjectTabMenu

Lookup Portal

ctLookUpMaintListGrid
ctLookUpMaintMainPage
Any help navigation keys

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 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

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.