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.
Replace and Remove Features
| Product | Removed Feature | Target Removal | Replacement Feature | Replaced In | Additional Information |
|---|---|---|---|---|---|
| Cloud Service Foundation | User K1IPROC is no longer provided for new customers | 27.4 | None | N/A |
K1IPROC user for existing customers will change ownership to CM. |
| Oracle Utilities Application Framework | Print Zone option | 26.10 | Standard screen print functionality | N/A |
Previously, zones in the system included a menu in the zone header that included a "Print Zone" option. This feature is no longer supported. In some zone types, for example Map zone types, the print option was the only option in the menu. For these zone types, the zone menu is no longer displayed at all. For data explorer zone types, the menu is still visible to access other options that continue to be supported, such as Export. |
| Oracle Utilities Application Framework | Business Object legacy page metadata | 26.10 | Portal-based user interface | 23B / 4.5.0.1.2 |
Navigation keys removed: businessObjectAccordionPage, businessObjectAccordionPrtPage, businessObjectAlgorithmsGrid, businessObjectAlgorithmsPage, businessObjectAlgorithmsPage_H, businessObjectLifecyclePage, businessObjectLifecyclePage_H, businessObjectMainPage, businessObjectMainPage_H, businessObjectOptTypeGrid, businessObjectSchemaPage, businessObjectSchemaPage_H, businessObjectStatAlgGrid, businessObjectStatTRRuleGrid, businessObjectStatusOptionGrid, businessObjectSummaryOptTree, businessObjectSummaryPage, businessObjectSummaryPage_H, businessObjectSummaryUseTree, businessObjectTabMenu Records in the UI metadata program component tables related to the above navigation keys were removed. In addition, the following fields were removed: F1_BO_OPTIONS_TREE_NAME, F1_BO_STAT_ALG_SUMM, F1_BO_STAT_OPT_SUMM, F1_BO_STAT_TR_RULE_SUMM, F1_BO_SUMMARY_TREE_NAME, F1_BOPT_SUMM, F1_BUS_OBJ_ALG_SUMM, SNAME_FWPTBOJPTM, SUBSYS_FWPTBOJPTM |
| Oracle Utilities Application Framework | Lookup legacy page metadata | 26.10 | Portal-based user interface | 23A / 4.5.0.1.1 |
Navigation keys removed: ctLookUpMaintListGrid, ctLookUpMaintMainPage, ctLookUpMaintMainPage_H, utilLookUpTabMenu Records in the UI metadata program component tables related to the above navigation keys were removed. In addition, the following field was removed: SNAME_CIPTLKFPTB |
| Work and Asset Cloud Service, Work and Asset Management | Legacy GIS Integration | Not applicable | Oracle Utilities OIC-based GIS Integration | 26.4 |
The ArcMap/ArcGIS Desktop-based legacy integration is deprecated in 26.10. Existing ArcMap-published GIS services can continue to operate during the deprecation period. File-based inbound synchronization and asset outbound synchronization were introduced in earlier releases; work location synchronization through messaging was added in 26.4, completing the supported replacement path. |
PLANNED REMOVAL
The list of functionality/system data that we plan to change/deprecate in a future release
Plan to Remove Support for 'Print Zone' Option
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 Support for Several Legacy Pages
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. This is because the feature is no longer actively supported, or 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.
Pages Expected to Be Deprecated
| Page Name | Comment about support for the page's functionality |
|---|---|
| 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. 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.
Pages Changing to Display Only in Upcoming Release
| Page Name | Comment about support for the page's functionality |
|---|---|
| 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 for Stricter Validation for String Concatenation in Groovy 'Create Prepared Statement'
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 online help topic "Using Groovy Within Scripts" for information on the valid syntax to use for Groovy scripts going forward.
Plan to Remove Support for LegacyCryptographyInstance
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 to implement INSERT, UPDATE and DELETE
!!! Tech writers, please only include this in cloud release information. It won't apply to on prem.
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
Currently, all base delivered zone types support a parameter called Zone Header Map, which can be used to override the zone's header area. This may be used 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 Support for DBMS Scheduler
With the introduction of the next generation cloud scheduler, specialist objects used to support the original DBMS scheduler on the cloud will be removed from the product.
The following inbound web services related to DBMS Scheduler functionality will no longer be supported in a future release:
- F1-DBMSChain
- F1-DBMSGeneral
- F1-DBMSJob
- F1-DBMSThread
The following business services related to DBMS Scheduler functionality will no longer 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
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 is 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
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 Metadata & Java Related to Mobile 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. The metadata and Java packages will be removed in a future release.
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 below 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 it is used on other fixed pages.
To Do Type Metadata Planned for Removal
| To Do Type |
|---|
| toDoTypeAlgorithmsGrid |
| toDoTypeAlgorithmsPage |
| toDoTypeCharacteristicsGrid |
| toDoTypeCharacteristicsPage |
| toDoTypeCharGrid |
| toDoTypeDrillKeysListGrid |
| toDoTypeDrillKeysPage |
| toDoTypeExclListGrid |
| toDoTypeExclListPage |
| toDoTypeMainPage |
| toDoTypeRolesListGrid |
| toDoTypeRolesPage |
| toDoTypeSortKeysListGrid |
| toDoTypeSortKeysPage |
| toDoTypeTabMenu |
Algorithm Type Metadata Planned for Removal
| Algorithm Type |
|---|
| algTypeMainPage |
| algTypeMaint |
| algTypeParamGrid |
FK Reference Portal Metadata Planned for Removal
| FK Reference Portal |
|---|
| fkReferenceMaint |
| fkReferenceTabMenu |
Service Program Metadata Planned for Removal
| Service Program |
|---|
| serviceGrid |
| serviceMainPage |
| serviceTabMenu |
| serviceTree |
Feature Configuration Metadata Planned for Removal
| Feature Configuration |
|---|
| wfmSysMainPage |
| wfmSysMessageGrid |
| wfmSysMsgPage |
| wfmSysOptionsGrid |
| wfmSysTabMenu |
UI Map Metadata Planned for Removal
| UI Map |
|---|
| uiMapMainPage |
| uiMapSchemaPage |
| uiMapTabMenu |
Data Area Metadata Planned for Removal
| Data Area |
|---|
| dataAreaMaintenanceTabPage |
| dataAreaSchemaPage |
| dataAreaTabMenu |
Batch Control Metadata Planned for Removal
| Batch Control |
|---|
| batchContrAlgorithmGrid |
| batchContrAlgorithmPage |
| batchContrMainPage |
| batchControlMenu |
| batchCtrParmGrid |
Menu Metadata Planned for Removal
| Menu |
|---|
| menuCtxt |
| menuIModsGrid |
| menuLineItemsPage |
| menuLinesGrid |
| menuMain |
| menuMaintMainPage |
| menuMaintTabMenu |
| menuModFlagsGrid |
| menuModFlagsPage |
| menuSub |
Script Metadata Planned for Removal
| Script |
|---|
| scriptMaintenanceMainPage |
| scriptMaintenanceStepPage |
| scriptMaintenanceStepAccordion |
| scriptStepSendFieldsGrid |
| scriptStepPromptsGrid |
| scriptStepReceiveFieldsGrid |
| scriptMaintenanceCopyStepPopup |
| scriptDataArea |
| scriptDataAreaGrid |
| scriptSchemaPage |
| scriptMaintenanceEligPage |
| scriptMaintenanceEligCritGrid |
| scriptTree |
| scriptMaintenanceTabMenu |
Maintenance Object Metadata Planned for Removal
| Maintenance Object |
|---|
| maintenanceObjectAlgorithmsGrid |
| maintenanceObjectAlgorithmsPage |
| maintenanceObjectGrid |
| maintenanceObjectTabMenu |
| maintenanceObjectOptionsGrid |
| maintenanceObjectOptionsPage |
|
maintenanceObjectMainPage |
Business Services Metadata Planned for Removal
| Business Service |
|---|
| businessServiceMainPage |
| businessServiceSchemaPage |
| businessServiceTabMenu |
Batch Run Portal Metadata Planned for Removal
| Batch Run Portal |
|---|
| batchRunTreeMaint |
| batchRunTree |
| batchRunTreePage |
| batchRunMaintPage |
| batchRunTabMenu |
Batch Job Submission Portal Metadata Planned for Removal
| Batch Job Submission Portal |
|---|
| batchSubmitMainPage |
| batchSubmitTabMenu |
| batchJobParmGrid |
Outbound Message Type Portal Metadata Planned for Removal
| Outbound Message Type Portal |
|---|
| outboundMessageTypeMainPage |
| outboundMessageTypeTabMenu |
| outboundMessageProfileTree |
Currency Portal Metadata Planned for Removal
| Currency Portal |
|---|
| currencyGrid |
| currencyMain |
| currencyMainPage |
| currencyTab |
Geographic Type Portal Metadata Planned for Removal
| Geographic Type Portal |
|---|
| geoTypeData |
| geoTypeMainPage |
| geoTypeMaint |
Language Portal Metadata Planned for Removal
| Language Portal |
|---|
| languageLANGGrid |
| languageMainPage |
| languageMaintenance |
Phone Type Portal Metadata Planned for Removal
| Phone Type Portal |
|---|
| phoneMainGrid |
| phoneMainPage |
| phoneTypeMaint |
Plan to Remove Managed Content Support for XSLT 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 In Pagination from 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.
Metadata No Longer in Use
| Object | Data | Description / Comments |
|---|---|---|
| Lookup Value | CHAR_ENTITY_FLG / F1SE | Characteristic Entity / Sync Request Inbound Exception |
Plan to Remove Business Object (BO) Read in 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, which required a different fix that made the BO Read unnecessary in F1-MainProc. Since 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.
Fields and Columns Planned for Removal
| Product | Removed Feature | Target Removal | Replacement Feature | Replaced In | Additional Information |
|---|---|---|---|---|---|
| Work and Asset Cloud Service, Work and Asset Management | Field 'SEQ_NUM' on table 'W1_BC_LINE' | Next Release 27.4 | 26.10 | As part of this release, a new field 'BC_LINE_SEQ_NUM', which supports value up to 99,999, was added to the table 'W1_BC_LINE' and values from the existing field 'SEQ_NUM' on that same table, which supports value up to 999, was copied into the new field. However, moving forward, the field 'SEQ_NUM' on the table 'W1_BC_LINE' will not be maintained anymore and will be deprecated in the next release. If you have any customized SQLs referring to the field 'SEQ_NUM' on the table 'W1_BC_LINE', you must update them to refer to the new field. |