This section describes enhancements, system data details and deprecation notices in Oracle Utilities Application Framework v26.10 including:

This section describes the new and enhanced batch processing features in this release, including:

The product supplies two base algorithm types that submit a batch job for a given batch control. The algorithms use the default parameter values and mark the batch submission with a submission type of Generated. In this release, both algorithm types have been enhanced to check first if there is a already Pending, "Generated" batch job for the batch control. If one is found, the algorithm will not add another one.

The following algorithm types were impacted:

The base product provides algorithms for the above algorithm types for several steps related to Content Migration Assistant (CMA). If you created several Migration Data Set Import records at once, you may have found that each one created a batch job submission for the Data Set Monitor batch. However, the batch framework only processes one at a time, so the extra batches queued up in Pending status. All the data sets were processed by the first batch run. As a result, subsequent batch runs did not have anything to process.

If your implementation has plugged in any of the base delivered algorithms to help orchestrate the CMA processing, you will see a change, especially when creating multiple Migration Data Sets in a short period of time. Now, the system will ensure that no more than one pending batch job is generated.

If your implementation has not used the base algorithms for CMA and has not created any custom algorithms for the above algorithm types for your own use cases, you are not affected by this change.

No steps are required to enable this feature.

An explicit indication was added to the batch control record to note whether it supports multi-threaded processing. Typically, this indication is set on the batch program itself and is displayed when available. There is no need to redundantly set this field in that case. This field may be populated when the batch program does not have such explicit annotation or when there is a need to restrict a multi-threaded batch process to be single threaded.

When submitting a batch job, an error is issued when multiple threads are requested for a batch control that indicates it does not support multi-threaded processing.

No steps are required to enable this feature.

For some monitor batch processes, the number of records to process is unpredictable and can range from zero to a few to many records. Submitting these batches with a fixed number of threads that fits the higher volumes of records means wasting threads with each run.

When there is no data to process, monitor batch process are now enhanced to not create any batch run or any of the thread level artifacts associated with a batch run. The batch job submission record is completed as usual, but it indicates that no batch run was needed.

In addition, a new optional batch parameter Minimum Records per Thread is available for monitor batch processes that allows some batch controls to indicate that the number of threads should be calculated dynamically based on the number of records to process. If it is not provided, the batch works as it currently does. There is no adjustment of the requested thread number. If the parameter is specified, the requested number of threads may be adjusted based on actual record count. The adjusted number of threads will not exceed the requested number and can only be reduced based on the new batch parameter.

For example:

There is no change to monitor processes that have data to process. Thread adjustment is only applied when explicitly requested using the new batch parameter on specific monitor batch controls.

Complete these steps:

With this enhancement, a batch run record for a monitor batch process will not be created when there is no data for the batch to process. In this situation, the batch job submission record indicates that a batch run was not needed using a new new "No Processing Needed" F1_NO_PROC_NEEDED column added to the Batch Job table.

If there are some custom procedures that rely on the batch run record to exist even when there is no data to process, then these procedures should be adjusted to rely on the new column added to the Batch Job table instead.

The plug-in driven extract batch supports a variable in the File Name for the batch control code. Previously, if the batch control code was fewer than 8 characters, the column contained trailing spaces to pad the data to the full 8 characters and the trailing spaces were included for the file name when substituting the code. For example, if the batch control was F1-ABCD and the file name parameter was defined as follows "Extract_{batchControl}_{runNumber}.txt".

The file name for run number 001 would be "Extract_F1-ABCD _001.txt".

In this release, the trailing spaces are trimmed so the file name in the above example would now be "Extract_F1-ABCD_001.txt.".

No steps are required to enable this feature.

You should confirm that if you have use cases that use the batch control variable in file names for a batch control with fewer than 8 characters, there is no downstream process that expects the trailing spaces. If there is, the downstream processes should be adjusted to no longer expect the trailing spaces.

Previously, the plug-in driven extract batch program supported a fixed-position file format (FIXD) only for single byte characters. When producing fixed-position extract files, space padding was applied based on byte length rather than character count. When the data contained multilingual characters (for example, Chinese), this resulted in fields not occupying the expected number of character positions.

The batch program now supports a new format option (FIXC) for the File Format batch parameter, which produces fixed-position extract files for multibyte characters. With this option, space padding is applied based on character count.

No steps are required to enable this feature.

Prior to this release, a request to reprocess a batch run, like submit a rerun batch process for a specific batch run number, was only available via the Batch Job Submission portal. In rare situations where a batch run was not submitted via a batch job submission request, there was no way to request such rerun. As of this release, a Rerun action has been added to the Batch Run portal to request a new batch job request to be submitted for the current batch run.

The ability to submit a rerun batch job request from the Batch Run portal supports situations in which the batch run was not initially submitted via a batch job request.

No steps are required to enable this feature.

When possible, the product delivers To Do Types to allow for creating To Do entries for each record error reported by the batch, rather than only writing the error to the batch run tree. It was found that several monitor batch processes delivered previously did not have an associated 'error' To Do Type.

The following monitor batch processes now have related To Do Types to use for errors:

Note that for backward compatibility upgrading clients need to opt in to using To Do entries for existing batches.

The ability to create To Do entries in these cases allows you to take advantage of the standard To Do functionality, such as prioritization, assigning users to do the investigation, and capturing comments or logs.

For upgrading clients, the To Do Types are delivered without the associated 'creation batch control' populated. Then means that when running any of the listed batch processes, individual record errors are still reported to the batch run tree only.

If you want To Do entries created for each error instead, complete these steps:

This section describes the new and enhanced configuration tools features in this release, including:

The system provides a Data collection for both Inbound Market Messages and Outbound Market Messages where you can link different types of data associated with the market message. Each entry allows you to indicate a Data Type and the base values provided are Message Data, Process Data, and Raw Data. In this release, the Data Type lookup is now customizable so that you can indicate a different desired data type, for example "CSV".

No steps are required to enable this feature.

Previously, a portal's title area included a single text as its title. Redwood templates support additional components as part of the title area, such as a subtitle and a list of content values.

Now the page title area functionality is enhanced to more closely match Redwood template specifications. While this enhancement aligns with Redwood guidelines, it is supported also in classic UI display mode. An optional new Enhanced Page Title portal option type allows a script to compose the information displayed in the title area. The option is defined for the main tab of the portal and applies to the entire page.

There is no change to existing page titles when the option is not used. This functionality is only available to portal pages and not legacy fixed style pages.

No steps are required to enable this feature.

Searching for a message sender record was moved to a standard query portal. The query portal supports additional filters by context type and value.

No steps are required to enable this feature.

Upgrade scripts ensure that users with Read access to the existing application service will have access to the new application service associated with the new portal. The table below lists the existing and new application services.

Previously, a portal's tab menu included a single label for each tab. The Redwood dashboard template supports a more robust scorecard display of each tab.

Now the display of a dashboard portal's tabs area is enhanced to more closely match the Redwood dashboard template specifications. This feature is only supported for portals set with the Dashboard role that are associated with a UI template. While this enhancement aligns with the Redwood template guidelines, it is also supported in classic UI display mode.

An optional new Scorecard portal option type is introduced to allow for a script to compose the information displayed in the portal's tab area. A mixture of scorecard and classic tab display is not supported. The option must be configured on the main portal and also on each tab portal associated with the dashboard page for the tabs to be rendered as a scorecards. There is no change to the display of existing page tabs when this option is not used.

No steps are required to enable this feature.

There is a standard query port for searching for a process flow type record. Using a separate query portal allows for a better and more intuitive organization of information on the maintenance portal.

No steps are required to enable this feature.

Upgrade scripts ensure that users with Read access to the existing application service will have access to the new application service associated with the new portal. The table below lists the existing and new application services.

When you have enabled revision control for any of your maintenance objects, you may now compare the object between two revisions or between the object and its most recent check in.

The Revision Control sidebar zone now includes a link to Compare to Previous Version. The following highlights the behavior:

The Revisions zone on the Revision History page now has multi-select action and a Compare button. It allows you to select any two revisions and compare them.

No steps are required to enable this feature.

Previously, a portal may have been designed to make use of configurable parameters defined on a corresponding master configuration record. These parameters are set up by customers and are used by the portal's user interface. For example, setting up defaults and valid values. Populating these parameters using the master configuration portal was disconnected from the corresponding portal definition record.

A new Configuration tab was added to the portal maintenance page to fully maintain the master configuration record if any is associated with the portal. A new portal option Master Configuration business object is used to associate a portal with the master configuration business objects that defines its additional parameters. The new tab appears only if such an option exists.

No steps are required to enable this feature.

Redwood specifies a view details function where a side panel (drawer) opens to display related extended information. Now portals can be designed to leverage this same functionality. While this enhancement aligns with Redwood guidelines, it is also supported in classic UI display mode.

An optional list of "View Details" zones can be defined as part of a portal's zone configuration. These zones are not rendered as part of the portal's layout. They represent groups of zones to be presented as drawers upon user request. Each view details zone is associated with a "panel name" which represents a uniquely named drawer. When the panel name is launched, all zones that belong to that panel are presented in sequence order.

New syntax was added to launch a "view details" drawer from a UI map, a data explorer column, and a chart.

No steps are required to enable this feature.

A new Navigation URL extendable lookup defines named external pages for which customers can provide the actual URLs.

Registering external page URLs in a designated extendable lookup makes it easier to configure and enable such functionality.

You don't need to do anything to enable this feature.

Stricter access to the java.util.Formatter class has been implemented for Groovy scripts. Specifically, constructors that accept a File or file name and are capable of creating or writing to files on the file system are restricted.

The following constructors are allowed:

Restricting the methods and constructors for this Java class protects against vulnerabilities.

You can disable this restriction by setting the com.oracle.ouaf.groovy.formatterAllowlist.enabled property to false:

Example: com.oracle.ouaf.groovy.formatterAllowlist.enabled=false

You can use an insight action to navigate to another page, to launch a BPA script to perform some user interaction, or to invoke an algorithm to perform some action. Previously, it was the responsibility of the insight algorithm that returns the actions to check a user's access to the actions.

The system has been enhanced so that now the system can check security based on configuration, eliminating the need for the insight algorithm to perform explicit security checks.

If the insight action performs navigation or launches a BPA, the action is suppressed if the user does not have access to the underlying application service/access mode related to the navigation or the BPA.

In addition, the insight action collection now includes an optional Application Service/access mode. If an action is configured with this information, the user does not see the action if they do not have access to this application service/access mode.

Validating security from the action-button configuration simplifies how the insight algorithm returns action information.

You don't need to do anything to enable this feature.

This section describes the new and enhanced CMA features in this release, including:

Previously, the process of reviewing objects in error within a CMA import data set required you to sift through the objects as a list. When the number of objects in error was high, managing this process was inefficient and lacked the ability to distill common issues that impacted many objects.

A new Errors tab was added to the Migration Data Set Import portal that provides a high-level summary of exceptions and a better focus on common issues across many objects.

No steps are required to enable this feature.

This section describes the new and enhanced general features in this release, including:

Restrictions have been added to names and extensions for files uploaded to the system via plug-in driven upload batch as well as for attachments and bundles.

Ensuring that file names, attachment names, and extension names are following stricter validation ensures compatibility between different systems, prevents errors when sharing files across platforms, and maintains the integrity of system operations.

You should confirm that if you have any configured batch file uploads where a file name is defined, the file name conforms to the restrictions.

In addition, if your organization needs to support custom file extensions:

The following fields were increased to 100 bytes:

In order to support more business use cases, you can capture larger size strings in these fields.

No steps are required to enable this feature.

This section describes the new and enhanced implementation tools in this release, including:

Implementers could use plug-in driven batches to perform some types of one-off data corrections, but the process required many manual configurations and lacked the built-in approval step supported by the request-based data correction flows. In addition, each custom plug-in driven batch involved creating a few custom algorithms, scripts, and a batch control for just the one-off update.

This release introduces a simplified way to request, approve, and perform plug-in driven based data corrections.

The mechanism is based on a new Configurable Data Correction (F1-DataCorrectPlugIn) Request business object that includes the following components:

This business object is a subclass of the existing data correction root business object and leverages the same approval based lifecycle flow.

When a request is approved and a user submits it for processing, a batch job is created for the specific request. The batch job uses the query on the request to select the records to correct and calls the corresponding business object or script to perform the update for each record. The request remains in the Submitted status while the batch process runs.

When the batch is completed it updates the corresponding request to the Processed status, which then creates a monitoring To Do Entry for a user to review the results of the batch. The user marks the request as complete and if further corrections are needed the user can create another request with different correction details as needed.

A corresponding Data Correction via Batch (F1-DataCorrectTypeByBatch) Request Type business object is also provided to define a request type record for creating such requests. To enable this functionality, a request type should be created using this business object.

With this approach, the data correction procedure is as follows:

This request-based data correction process does not require custom algorithms or batch controls. It only requires a custom script for more complicated updates.

To enable and configure this feature, complete these steps. You need access to the existing Request Type portal, Request Type Query portal, and to the Request Type MO application services to perform these steps.

To enable users to create configurable data correction requests, you must give them access to the application service for the Data Correction Request Root (F1-DATACORRECTIONRBO) business object and to the application service for the Request Data Correction (F1DTCREQ) batch process.

There is a 65,535 string size limit in Groovy when using createPreparedStatement. As a result, script writers have used the StringBuilder or String Buffer method to build more complex queries.

A new Groovy method is now provided: concatenateGroovyStrings(String... args). This method allows script writers to concatenate strings to build a query for createPreparedStatement that exceeds the maximum string size. The new method accepts a variable number of strings (varargs of strings) to concatenate. This method validates that the arguments are only strings. The createPreparedStatement method is enhanced to accept the new method as its first argument or to accept a variable that was created using that method. See the Tips and Considerations section for more details about what is supported.

In addition, helper methods are provided for use within the concatenateGroovyStrings method to support dynamically adding information from an array into the SQL statement you are preparing.

The following helper methods are supported:

By default, script validation is tightened to disallow concatenation unless the new method is used. Refer to the description for information about the property and steps for overriding it while you fix any scripts that do not compile.

Here are some examples of valid syntax using the new method:

The createPreparedStatement will not accept any variable that is not created directly from the new method with literal strings. Here are examples of syntax that is not allowed.

In this release, this previously supported string concatenation is not allowed by default. You should review all your scripts in this release and change them to use the new method. Here is an example:

Note that simple concatenation with "+" of literal strings directly in createPreparedStatement is supported and will continue to be supported in the future.

This is only applicable if you have custom UI maps that directly call CSVToXMLDataServlet and have a custom function to prepare the data to pass to this servlet.

The servlet was enhanced to include an extra parameter to ensure that the servlet correctly handles non-ascii characters in the file name. The framework provides the method oraFileUploadFromForm to handle preparing the information to pass to CSVToXMLDataServlet. If you have any UI map that uses this method to prepare information to call the CSVToXMLDataServlet, nothing further needs to occur.

However, if you have any custom maps that call CSVToXMLDataServlet and have custom function to prepare the data to pass to the servlet, you will need to adjust the maps.

Use the UI map query > Additional Information search option to see if you have any custom UI maps that reference csvToXMLDataServlet in the HTML definition.

If so, if the map has a 'form' element that defines action="csvToXMLDataServlet", confirm if the map has a custom function that is invoked by the onClick of the button used to upload an indicated CSV file.

If so, the map must be updated as follows in order to ensure that non-ascii file names are supported:

Users that have inquire access to the 'Portal' maintenance portal will now see an action to navigate to Portal Maintenance. When this option is available, users will see the Bookmark and e Portal Maintenance grouped in a 'General Actions' button menu.

For example, if a user is viewing a Business Object record and selected the Portal Maintenance action, it would look like the following.

You are taken to the portal configuration for the Business Object portal.

If you are using the Redwood user experience, the action is visible in the overflow actions menu.

For development users that are managing configuration for a portal, this option is a convenient way to quickly navigate from viewing the rendered portal to viewing the underlying configuration for the portal.

You don't need to do anything to enable this feature.

Previously, the Test button visible to authorized users on the Script page and the Business Service page performed the script/business service logic. If the script or business service logic included database updates, these were also performed. The Test button's logic is now enhanced to perform the script or business service logic, but to roll back the changes. This allows developers to confirm that the script or business service is performing the expected steps, without updating data. Note that if the script or business service does a web service call, this logic cannot be rolled back. Additionally, if the logic uses the technique to call a service via the save point dispatcher, logic performed in that session is also not rolled back.

The Test button adds an extra layer of security to ensure that only authorized users can use the test action.

Providing the ability to test a script or business service without committing changes ensures that data is not accidentally updated during a test and also allows developers to reuse testing data in subsequent tests.

Provide the required access before using the feature. Details are in the Access Requirements section below.

System administrators should set/grant users/grant access to the Execute access mode for the F1-GEN-SVC-EXEC application service.

This section describes the new and enhanced integration features in this release, including:

The product provides characteristic mapping functionality for dimensions defined in the Analytics Table feature. The list of characteristic tables available when configuring the mapping sometimes displayed tables that were not supported by the analytics tool. In this release, characteristic tables included in the configuration are now in line with the tables supported by the analytics tool.

The list of tables is as follows:

No steps are required to enable this feature.

It is possible that you defined characteristic mappings for one of the tables that was not supported. Although the product allowed the mapping to be defined, it would not have been supported in the analytics tool. If you have any records like this they are not causing any issues, but they can be cleaned up by going to the Analytics Attribute Mapping table, search for the dimension and review the list of mapped characteristics to remove the ones that are for unsupported tables.

The system now delivers a base external system called Cross Product External System (Oracle Utilities Customer to Meter), which is available to use for any product built on the Oracle Utilities Application Framework.

Previously, this external system was only available to a subset of implementations.

No steps are required to enable this feature.

Note that this external system was already available previously to any implementation whose product configuration included the "X1" Owner flag.

Previously, customization of a base product's REST Inbound Web Service (IWS) was limited to certain types of schema extensions and allowed no custom business rules.

Now you can override the following aspects of a base REST IWS operation:

Customizing a base product service can significantly change how it works. A new Allow Customization indication is added to the IWS to explicitly indicate whether customization is allowed or not.

When an IWS allows customization, a Custom Script may be specified on an IWS operation to override its underlying base service. The custom script must adhere to the base service schema it overrides and can only extend it. For this reason, the custom script's schema must at least include the operation's base service schema and may include additional elements as needed.

With this approach, there is no change to the URL used to access the web service. If the operation is customized, then internally the custom script is called instead of the base service.

In the same way, the API specification of the operation is adjusted to use the custom script (if any). If a custom web service schema is also provided, then it is used instead of the base web service schema (if any).

The Extensions portal is enhanced to also report on this type of customization as an extension.

No steps are required to enable this feature.

When configuring a Message Sender with one of the following message classes, RTHTTPSNDR, RTJSONSNDR, SOAPSNDR, or HTTPSNDR, a warning is issued if no value is set for the HTTP Time Out context type.

Setting a reasonable time out limit ensures that you will not wait a long time for a response if there is any issue connecting to the third party.

To configure this feature, complete these steps:

The product now supports a JWT client assertion OAuth grant type, using a signed JSON Web Token to retrieve an access token from Oracle Identity Cloud Service.

In addition, the product supports a JWT user assertion OAuth grant type. This enables the use case where an online action in the application triggers an outbound message to another system and propagates the user identity and authenticates the user without requiring them to interactively sign in again.

Supporting these additional OAuth grant types increases both security and flexibility of outbound messages.

To enable and configure this feature, refer to the Message Sender - Context topic in the External Messages chapter of the Framework Administrative User Guide.

A Field Help Text collection has been added to Outbound Message Type. This allows the product to provide more information related to a delivered outbound message type to help your organization manage your base delivered integrations.

This makes it easy for the integration team to map fields to the target system.

You don't need to do anything to enable this feature.

This section describes the new and enhanced To Do features in this release, including:

There were several improvements to the To Do Management portal and the To Do Details tab on the To Do Dashboard portal:

In addition, there is a new feature related to displaying the Characteristics column in the results of various To Do Related queries. A column shows name/value pairs of characteristics linked to the To Do Entry. If a To Do Entry has many characteristics linked to it, the row takes up more vertical space to show all the values. This means that fewer To Do entries are visible in the list. A more compact way to display this information is to use a standard short summary text and a collapsed details section.

There were two fixes also are included with this enhancement:

Complete these steps to opt in for the compact display mode:

The functionality documented here was delivered in version 25.10 through Maintenance Pack ­­5.2.0 (Bug 38721796).

This section describes the new and enhanced user interfaces in this release, including:

When defining a menu, you are now required to provide a description.

Ensuring that there is a description on the menu allows the system to provide the standard query tools for searching for and displaying a menu where the description is part of the results.

No steps are required to enable this feature.

An upgrade script is provided to populate the Description field if it is not populated. The script first looks to see if there is text populated in the LABEL_LONG field, which is no longer used but may have relevant text from older releases, and uses that if it is available. If it is not available, the description is populated with the Menu Name field.

The product offers a new Redwood user experience. Highlights include the following:

This is an opt-in experience. It may be set at the application level using a feature configuration option. In addition, individual users with appropriate security access can use a Switch UI View option in the user menu drop-down.

Redwood provides a more modern user experience and these updates make the product more consistent with other Oracle applications.

To enable and configure this feature, complete these steps:

Additionally, a user may can select the Switch UI Style option visible from the user badge drop-down to switch between the Oracle Redwood and classic user experience.

Previously, an input form launched from a BPA script and targeted to the page data area, was presented as a large modal window even when the content did not call for that window size. Redwood supports more modern options for presenting an input form in either a small, medium, or a large drawer panel. Now you can design your input forms to render in various drawer panel sizes as needed. While this enhancement aligns with Redwood guidelines, it is also supported in classic UI display mode.

BPA scripting syntax is enhanced to also support a small, medium, or large drawer as target options for an input form.

The maintenance input form used to add or edit a business object entity is one of the most common types of input form. As of this release, when in Redwood UI display mode, the default display of a maintenance input form is set to a large drawer. A new Maintenance Drawer Size business object option is introduced to allow a business object to select a different drawer size.

In classic UI display mode:

The ability to enter data in a properly sized input drawer allows for a more modern user experience.

Steps to Enable

You don't need to do anything to enable this feature.

Previously, badges and cards were visualization options that were only available via the insights configuration. A new ou-visualization web component is now provided to render badges and cards using data available to the UI map schema without relying on any insight type configuration.

Additional styling classes are also available for a more precise user interface look and feel. For example, you may use a new class to display a list of characteristics or any name and value pairs as single elements. Displaying them as single elements and not as a list may simplify the user's review process.

Refer to the UI Map Attributes and Functions section in the online help documentation for more information.

While this enhancement aligns with the Redwood visualization components, it is also supported in classic UI display mode.

The additional visualization options better support Redwood-aligned user experience design.

You don't need to do anything to enable this feature.

When a list of entities are presented, a link to the entity's page is typically available allowing the user to navigate to that page for reviewing more information and navigate back to review the next entity. With the introduction of "view details" drawers in the previous release, this type of user interaction can be improved by launching a summary drawer for the entity instead of navigating to its page. The user can proceed with navigation to the entity page if they need further information.

This release supports the association of an entity with a default view details drawer zone via a View Entity Drawer maintenance or business object option.

There is no change to system wide navigation to entity pages. Specific UI lists now use the new navigation approach, which opens an entity’s default drawer, when available, instead of navigating to the entity page.

To support this functionality, the ability of launching a view details zone in a drawer no longer requires that zone to be defined as an explicit panel on the portal it is launched from. You may design to launch a view details zone either as a panel name or as a standalone zone.

Providing a quick view of an entity's details as a drawer eliminates the need to navigate to another page and back, which improves the user experience.

You don't need to do anything to enable this feature.

This opt-in feature is only available in portal based user interfaces. It is not available in legacy pages. The following details highlight the system behavior when this feature is turned on.

Drop-down fields:

For input fields that are built as a dropdown, when you click the input field, you see the values and the input area.

When you start typing, the system makes a match on your text with the values in the drop-down and narrows down your results list accordingly.

If you select a value and then subsequently click the drop-down again, the current value is highlighted and the text you previously entered is retained.

Search fields:

For input fields that have a search associated, the system now supports configuration to enable auto-filtering. Searches that are enabled to support this feature show a down arrow in the input field.

Searches that do not support this feature do not include the down arrow.

The fields with a search associated with them continue to support previous capabilities including:

New functionality was added so that if you click the down arrow, an input field is visible to show the label of the filter that has been configured to allow for auto-filtering. You can start typing to get records that match that result. For example:

Typing 'business' displays all the maintenance objects whose description starts with that text. This search has been configured to display the description and the code in the results.

When you start typing, the system uses one of the search's underlying filters that has been configured for this functionality. In contrast to the dropdown behavior, where the system looks for a match on the text anywhere in the string, for the search typeahead functionality, the system relies on the filter's definition as to whether it is 'likeable' and if so, whether it is 'likeable' on the suffix or the prefix or both.

Once a value is selected, the primary key of the chosen record is populated in the input field per existing functionality.

If after selecting a value you subsequently click the down arrow again, as with the dropdown behavior, the previous entered filter text is still visible. The selected value is highlighted and the text matching the filter value is bolded.

Searches that enable this feature may also be configured to show up to three lines of supporting information for each record. In the example of Maintenance Object above, the search is configured to show both the maintenance object code and description in the results. In the base product, most searches for administrative tables which have a description have been configured to filter by the Description and to show the Description and the Code as shown in the Maintenance Object example.

For master and transaction fields, because only one filter field may be used for auto-filtering, searches are only enabled for this feature if a useful single filter was identified by the product team. For example, Person Name for the Account search.

In this case, the search was configured to include the person name, account ID, and relationship type in the output.

For drop-downs that have a lot of data, typing text to narrow down the list saves scrolling through a long list of values. For search metaphors where there is a reasonable filter value to enter, you save several clicks to get the data you are looking for.

To enable and configure this feature, complete these steps:

If you enable this capability and you have custom search zones, you may want to configure the search to support this functionality:

You can launch a Fusion Knowledge article from various locations in the application. Only HTML content articles are supported, such as 'question and answer' or 'problem and solution'.

UI locations that support the launching of a knowledge article are defined using the 'Knowledge Management Articles' extendable lookup. To enable this feature, update the entry with a corresponding Fusion article ID. When an entry is active and associated with a article, the knowledge book icon appears on the UI location.

Clicking the book icon opens the article in a drawer, where you can also search for other articles as needed.

Associating UI locations with supporting knowledge articles helps users complete their tasks.

To enable and configure this feature, complete these steps:

Redwood allows for important notes about the content to be highlighted on a page. This capability is supported for any portal. While this enhancement aligns with Redwood guidelines, it is supported also in classic UI display mode.

A new Portal Banners portal option type allows a script to compose the list of messages in various severity level to be presented on a portal. The option is defined for the main tab of the portal and applies to the entire page. For example, a customer dashboard may show a banner message alerting the agent of an existing outage along with the ability to view outage details in a drawer.

The following describe important aspects of portal banner functionality:

The product provides a generic 'Portal Banners by Insight Class - F1BannesInst' script that composes messages based on insights associated with an insight class for a given context. This allows banners to be configurable by the customer.

Highlighting important messages as banners on a portal increases visibility into these situations.

You don't need to do anything to enable this feature.

Currently, when a hint based Unified Search query is performed, there is no size limit on the entered filter value. For some searches this may cause performance issues.

You can associate a Unified Search hint filter definition, defined by the 'Search Filter Hint' extendable lookup, with an optional regular expression (regex) that qualifies the value the user enters as a valid filter value. When a hint is used and that hint is associated with such value expression, the search text is considered a valid filter value if it matches that regex. If the value does not match the regex, the search is not performed.

There is no change to hints without a value regex. Their value is used by the search without any value restriction.

Supporting a rule that qualifies the value of a hint based filter allows for performance improvement of hint-based unified search queries.

If there is a need to restrict the value entered when a unified search hint is used, complete these steps:

You can use the following new SVG icons in contextual insights, trees, and other user interface features that support SVG icons.

New 26.10 Icons

Additional icons allow for an enhanced user experience for displayed information. These updates have no impact on existing customizations.

You don't need to do anything to enable this feature.

Portal pages support defining portal-specific actions that are visible in the page title area of the application. In this release, the system supports configuring the portal-specific actions in an actions menu. This is useful when there are a large number of actions.

The ability to define portal actions in an actions menu allows you to organize a large number of actions.

You don't need to do anything to enable this feature.

See Portal Specific Page Actions in the Understanding Portals and Zones section of the Framework Administrative User Guide.

This section describes the new and enhanced data privacy and security features in this release, including:

The base product delivers many user groups that act as a type of library of system services. One of the main user groups that acts as a library of service is ALL_SERVICES. However, many of the other base delivered user groups act as a library of services, but for targeted functionality. The product strongly advises against granting users access to any of these user groups in production. Besides giving the users broad access when linked to any of these user groups, the product includes application services for new features and functions into these user groups in a new release. This means that users linked to those groups get access to the new features without having a chance to review their purpose and choose to opt into the new functionality.

The user groups may be used in a development or in a testing environment as an easy way for developers and testers to have access to features and functions for testing.

Previously, a health assessment type was delivered to report feedback when a user was found to be linked to ALL_SERVICES. The assessment type has now been expanded to check for users linked to any base delivered user group.

Expanding the health check for users linked to base delivered user groups ensures that clients are reviewing their user access and that they are linked only to custom defined user groups.

You don't need to do anything to enable this feature.

Previously, the Oracle Utilities Application Framework product delivered one base user group ALL_SERVICES and linked all the framework owned application services linked to this user group. Other products delivered as part of your full product solution may have added their own application services to this user group. However, there are use cases where additional base user groups are delivered for a specific subset of functionality and, in some cases, application services are only linked to this special, fit-for-purpose user group and not to ALL_SERVICES. In this way, the special user groups act as a catalogue of the services related to that specific functionality.

The Oracle Utilities Application Framework now delivers three new user groups to catalogue a specific subset of functionality or capabilities:

Going forward, the ALL_SERVICES user group will not include by default any of the application services/access modes that are linked to the AI or Cloud Services user groups. For application services in the Developer Services user group, ALL_SERVICES includes on the 'inquire' access mode. For backward compatibility, an upgrade script ensures that any of the services that used to belong to ALL_SERVICES in a previous release continue to be included in ALL_SERVICES (with the CM owner flag) for upgrading clients.

In addition, the Oracle Utilities Application Framework delivers a user group for the edge applications to link any application service needed for internal integration flows. Unlike the above user groups, this user group is not a catalogue of services. It is a functional user group that can be used in production for users and is created for internal integration flows.

New user groups provide a more specific catalogue of certain types of services.

You don't need to do anything to enable this feature.

This section describes the new and enhanced conversion features in this release, including:

Previously, there was no way to indicate that a entity validation rule is not applicable when the entity is added as part of conversion. Now the validate entity conversion batch process sets an indication available to validation rules, that they are being called as part of a conversion process. This allows a validation algorithm to skip some rules when called as part of conversion. Refer to online help for more information.

Allowing entity validation algorithms to skip rules that are not applicable when the entity is converted improves the quality and performance of the conversion process.

If you need to add configuration or prerequisite steps, add them below.

If a custom validation algorithm includes rules that are not applicable when the entity is converted, you can use the new indication to skip them when the algorithm is called from the entity validation batch process.

Refer to Validate Information In The Staging Tables in the Framework Administrative User Guide for more information.

This section describes the new and enhanced miscellaneous features in this release, including:

The Batch Control query portal supports a search by User ID as part of the Additional Information search option.

The ability to search for batch control configurations that reference a specific User ID allows a system administrator to review and adjust configurations more easily.

No steps are required to enable this feature.

Previously, the maintenance objects included in the ILM Managed Maintenance Objects section were only those that have an ILM Eligibility Algorithm, but this is not the only method by which a high volume maintenance object can be managed by the ILM functionality. Some maintenance objects will not have an eligibility algorithm for performance reasons. Instead, they are designed with a specific ILM crawler batch process with built-in ILM eligibility rules. There are other cases where there may not be an ILM eligibility algorithm or an ILM crawler batch control. For example, a snapshot maintenance object that is never updated and therefore its ILM_SW can be set when the entity is created.

These additional ILM managed maintenance objects are now also included in the ILM Managed Maintenance Objects list.

No steps are required to enable this feature.

This section provides information on functionality that has been removed, is no longer supported by Oracle Utilities Application Framework v26.10, or is planned for removal.

This is a list of functionality / system data that Oracle already removed from the Oracle Utilities Application Framework.

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.

Records in the UI metadata program component tables related to the following navigation keys were removed.

In addition, the following fields were removed:

Records in the UI metadata program component tables related to the following navigation keys were removed.

In addition, the following fields were removed:

Records in the UI metadata program component tables related to the following navigation keys were removed.

In addition, the following fields were removed:

Records in the UI metadata program component tables related to the above navigation keys were removed.

In addition, the following fields were removed:

This is a list of functionality / system data that Oracle plans to deprecate in a future release.

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.

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.

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

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.

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

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.

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:

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

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.

In the future, the product plans to remove support for such scripts.

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.

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.

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

The UI metadata related to fixed pages that have been converted to portals will be removed in a future release. The navigation keys listed are 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.

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.

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.

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.

The Service Catalog Configuration (master configuration) enables you to define subordinate servers. Defining subordinate servers is no longer applicable for the Oracle Integration Cloud.

The following metadata is no longer in use and will be removed in a future release:

 

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.