- Revision History
- Overview
- Feature Summary
- Generation Asset Manager
-
- Generation Asset Manager
- Utilities Application Framework
- Product Usability
-
- About Box Information Adjusted
- Adjust Menu Sequences
- Entity Tags
- Field References
- Filter Area On Data Explorer Collapses After Search
- Inbound SOAP Web Service Debugging Improvement
- Menu Application Security Portal
- New Hot Keys for Navigation
- New User Experience
- Open API Specification Enhancements
- User Group Services Management - Filter User Groups by Entity Tag
- Batch Processing
- Implementation Tools
- To Do Management
- Data Export
- Miscellaneous
- Application Security
- System Wide
- IMPORTANT Actions and Considerations
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Product | Feature | Notes |
|---|---|---|---|
| 31 MAR 2022 | Created initial document. |
Oracle Utilities Generation Asset Manager Cloud Service is a highly scalable operational awareness tool that can organize and visualize real-time and historical data from operational technology systems. It is tightly integrated with Oracle Utilities Live Energy Connect. Generation Asset Manager Cloud Service is intuitively designed so you can view, track, and understand real-time and historical performance of your assets.
There are two basic components of the Generation Asset Manager Cloud Service: The Live Energy Connect Portal, a web-based application, and the Historian, a cloud-based time series database.
- view unit statuses.
- receive real-time notifications and alerts about each unit.
- select which metrics display in graph view for a unit.
- browse historical data for each unit.
- view market positions.
HAVE AN IDEA?
We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.
DISCLAIMER
The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.
This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.
Column Definitions:
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.
| Ready for Use by End Users Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features. |
Customer Must Take Action before Use by End Users Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing. |
|||||
|---|---|---|---|---|---|---|
| Feature |
Report |
UI or |
UI or |
|
||
User Group Services Management - Filter User Groups by Entity Tag |
||||||
New Application Service for Master Configuration Maintenance Object |
||||||
There are no major updates planned for Oracle Utilities Generation Asset Manager for 22A.
Utilities Application Framework
About Box Information Adjusted
The information displayed in the About box now shows the product version, maintenance pack number, and patch level. For example, the following is displayed if the environment has the 6th maintenance pack for 21B: 21B MP 6 patch 93849302. Previously, the build number (often referred to as the 'sched') was shown.
Your cloud implementation now views the current maintenance pack installed rather then the build number.
Steps to Enable
You don't need to do anything to enable this feature.
The system's menu configuration includes sequence numbers to allow control over the order of menu lines throughout the system. If sequence numbers of one or more entries are the same, the system orders those lines alphabetically. Unless there are special circumstances, the product standard is to use the sequence number 50 for all menu lines that are part of the Main Menu or Admin Menu configuration.
Several Oracle Utilities Application Framework-delivered menu lines have been updated to sequence 50 to align with this product standard. The My Preferences menu entry on the Main Menu has a higher sequence (80) so that its position is always last in that menu.
You can see a more standardized menu configuration to ensure proper sort order.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
This sequence number may be customized by an implementation. If your your organization prefers a different configuration, you can adjust it accordingly.
In addition, the update to the sequence number for these menu lines only occurs if the sequence in your environment for each menu line matches the value previously released by the product.
Finally, note that the menu line's sequence number is an attribute of the menu line's language table. This allows organizations finer control over the menu order depending on the language. The product update described here only applies to the English language row.
Entity tagging supports grouping of configuration, demo, and test related entities so they can better describe a logical function. Each group is represented by a "tag" and entities may be associated with multiple tags.
A Tags dashboard zone allows the user to add, remove, and review tags for an entity. The zone is secured by an application service so that it is only available to applicable user roles. The Entity Tag portal lists all entities linked to a tag and supports mass actions for associating configuration entities with a tag.
You can tag entities to provide better mechanisms for finding and maintaining information.
Steps to Enable
Make the feature accessible by assigning or updating privileges and/or job roles. Details are provided in the Role section below.
Role Information
System administrators should grant access to the following application services:
- F1-ENTYTAG application service for the Entity Tag maintenance object.
- F1ENTAG application service for the Entity Tag maintenance portal.
- F1ENTAGS application service for the Entity Tag query portal.
- F1-TAGS application service for the Tags dashboard zone.
A References tab is added to the Field portal to list application components that explicitly reference the field record.
You can review all application references of a field record.
Steps to Enable
You don't need to do anything to enable this feature.
Filter Area On Data Explorer Collapses After Search
The filter area now collapses when searching on data explorer zones in all cases. The Expand Filters button becomes visible, allowing you to adjust your search criteria, if desired.
Business Object Search
Previously, this behavior only occurred if the query resulted in more than two records. The behavior is now consistent for all results.
After searching using a data explorer zone, the filter area collapses allowing you to see more information in the results.
Steps to Enable
You don't need to do anything to enable this feature.
Inbound SOAP Web Service Debugging Improvement
If your inbound SOAP web service uses XSL transformation, the debug log now includes the details of the document before and after the XSL transformation.
You now see more information in the debug output for inbound SOAP web services that use XSL transformation.
Steps to Enable
You don't need to do anything to enable this feature.
Menu Application Security Portal
A user may require several application service grants to properly work with the application components associated with a specific menu line. A new Menu Application Security portal is provided to assist with maintaining application security for a user group and the application services associated with a specific menu line. The portal is accessible from a new Menu Links dashboard zone that is available when reviewing the Menu page.
The Application Services Linked and Application Services Unlinked zones now include a filter by entity tag, allowing you to refine the list of application services by logical function.
You can review and adjust the application security a user group has for application components associated with a menu line.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
An upgrade script updates all user groups that currently have access to the existing Menu page application service CILEMNUP to have the same access to the new portal application service F1MENU.
Key Resources
- Refer to the Improved Menu Security training.
The new hot key Alt+[ allows you to quickly move the cursor focus to the next major page component. You can use Shift+Alt+[ to reverse the navigation order. The major page components include:
-
The menu or toolbar area
Menu / Toolbar
-
The Dashboard
-
The Page Title area
Page Title
-
The main Page Area, including the tabs for the current page and the display area of the current page
The new hot key Alt+] allows you to quickly move the cursor focus to the next zone. You can use Shift+Alt+] to move the cursor to the previous zone. For portal-based pages, this key navigates through zones in the portal and through the zones in the Dashboard. For fixed pages, the key applies to navigation of zones within the Dashboard portal.
You can use this keyboard navigation to more easily navigate to different sections of the user interface with fewer keystrokes.
Steps to Enable
You don't need to do anything to enable this feature.
The product provides an updated user experience referred to as Redwood. The new experience includes a compact page header that takes up less vertical space to allow more page content to be displayed, as well as new portal tabs, buttons, background colors, borders, icons, and fonts. Previously, this user experience was only available by turning on a URL parameter. This parameter is no longer supported or necessary, and the experience has been enriched.
The following are highlights from the Redwood user experience:
-
Palette and Icons - The color palette and icons reflect a more modern and streamlined user experience.
-
Unified Search - There is a single search box to perform comprehensive searches for data relevant to your application, based on search options supplied by your specific product.
-
Dashboard Controls - The default location for the dashboard is now on the left. User preferences allow you to configure it on the right, as before. In addition, the state of the dashboard (its width and whether it is open or closed) are captured in the user preferences and remain set until changed again.
-
Portal or Zone Configuration - There is advanced configuration for portals and zone layout, including new width options and height options.
-
Domain Name Display - Installation Options allow you to define a domain name for an environment. This information is displayed in the toolbar.
You can use the Switch UI View option in the user menu to revert the user experience to the previous one for the current session. This option is only visible if the user has been granted access to the appropriate application service.
Oracle is transitioning all its products to a new consistent user experience, branded the Redwood experience. The Oracle Utilities Application Framework has implemented this experience to provide a more consistent and modern interface with new design elements including consistent color, layout, fonts, behavior and icongraphy.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Note that to view the underlying HTML for a page, you should use the Inspect option rather than View Source or View Frame Source. With the Redwood user experience, the "view source" options no longer include the underlying HTML source code.
Open API Specification Enhancements
The Open API Specification document generated for an Inbound Web Service complies with up-to-date schema definition standards.
Note that the changes do not impact the request and response schemas used by the web service at run time and therefore should not cause upgrade issues.
The following sections describe the changes introduced in this release:
Schema Reference
The primary changes is to how a schema is referenced using the $ref attribute and how its root node is defined for when XML format is used.
Previously, the $ref definition referenced the "root" element of the request and response schemas using a nested reference within the schema definition. This was needed to ensure that in XML format the same root node was included in the request and response schemas.
"$ref": "#/components/schemas/CREATEPERSON_request/properties/C1-CrePerson"
Schema Definition
"CREATEPERSON_request": {
"type": "object",
"properties": {
"C1-CrePerson": {
"type": "object",
"properties": {
"personId": {
"type": "string",
"maxLength": 10,
"description": "Person ID"
}
This type of nested schema reference is no longer supported. Instead, a designated XML attribute is added to explicitly define the root node.
In this release, the schema reference is changed as follows:
"$ref": "#/components/schemas/CREATEPERSON_request"
Schema Definition
"CREATEPERSON_request": {
"type": "object",
"properties": {
"personId": {
"type": "string",
"maxLength": 10,
"description": "Person ID"
}
}
"xml": {
"name":"C1-CrePerson"
}
Reusing the Schema Definition for the Standard Error Response
Previously, the same error response structure was repeated as a separate schema for each IWS operation. This made the file large for no reason. In this release, a single copy of the error response schema is included in the document to make it smaller and simpler.
Adjusting the "Tags" Attribute Text
The tags attribute is constructed as <Resource Category description> / <IWS description>. The IWS description part was used to include the detailed description of the service if any was defined, but tags should ideally be short and not involve detailed descriptions. In this release, the IWS description part is changed to include only the short description of the service, regardless of any detailed description that may be defined for the service.
You can use the generated Open API Specification to comply with up-to-date schema validation requirements.
Steps to Enable
You don't need to do anything to enable this feature.
User Group Services Management - Filter User Groups by Entity Tag
The User Group Services Management portal provides zones to view the application services linked or unlinked to a chosen user group and the ability to remove or add services.
The Application Services Linked and Application Services Unlinked zones now include a filter by entity tag, allowing you to refine the list of application services by logical function.
This allows you to refine the list of application services by logical function.
Steps to Enable
You don't need to do anything to enable this feature.
DBMS Scheduler Option for Defining Time Zone
If your implementation is in a time zone that is different from the database time zone, set the new DBMS Scheduler Option set_sessiontz option to true to ensure that the Start Date/Time on the Batch Job Submission record is set to the time based on installation time zone rather than the database time zone.
You may control the time zone used for submitting batch jobs from the DBMS scheduler.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Note that the Start Date/Time on the Batch Job Submission record is used as a way to delay the job's execution to a future date. It is not used as a timestamp to indicate when the job was created or executed. If the new option is not set or is set to false, there is no affect if your time zone matches the database time zone or if your time zone is after the database time zone. The setting is only relevant if your time zone is earlier than the database time zone. For those implementations, without this option set, the Batch Jobs are be created with the database time zone, which will cause a delay in the jobs being processed.
DBMS Submission Default Changed to Single Submission
The DBMS scheduler now uses the "single submission" setting as the default. This setting results in the creation of a single Batch Job Submission record for a given job regardless of the number of threads. The resulting records in the Batch Run maintenance object continue to keep track of the multiple threads using the Batch Thread and Batch Instance records. Previously, the default setting was that single submission was turned off.
This setting may be overridden globally or for a specific batch program. Turning off the "single submission" setting results in the creation of a separate Batch Job Submission record for each thread. However, there is no benefit to using this setting. For jobs with a large number of threads, this option results in an unnecessary proliferation of records to manage.
A multi-threaded batch job is submitted by the DBMS scheduler using a single batch job by default. This may provide fewer records to manage.
Steps to Enable
You don't need to do anything to enable this feature.
A new Advanced Show Log Option allows administrative users to fetch logs of other users. By default, a user can only retrieve their own user logs. The following are examples of when this capability is needed:
-
Batch and integration logs are captured by special user codes created for this type of processing. These users typically do not represent a human and therefore would not access logs using "show user log." Instead, someone else would be accessing these logs.
-
Customer administrators would like to retrieve logs for an end user for support reasons An end user might not have technical skills to gather or assess the log, or they might not have the privileges necessary to access the logs for security reasons.
An Administrative (F1SU) access mode has been added to the existing Show User Log application service (F1USERLOG). Only users with access to the administrative access mode can view the logs of other users.
To a user with administrative access, the Advanced Show Log Option is offered as a drop-down button along with the Show User Log option.
Show User Log
Clicking Show User Log in the drop-down list launches a window allowing you to select the user ID for the desired user logs. You can also adjust the number of log entries. If you realize you want your own logs after all, you can simply click the checkbox.
Advanced Show Log Option
A system administrator can view the logs of other user to, for example, provide better support or access special batch and user logs.
Steps to Enable
Make the feature accessible by assigning or updating privileges and/or job roles. Details are provided in the Role section below.
Role Information
System administrators should set/grant users/grant access to the Administrative (F1SU) access mode of the existing Show User Log application service (F1USERLOG).
Explicit Imports in Groovy Scripts
When saving a script, if the system detects that there are classes referenced in the script that are not explicitly defined, it issues a warning and automatically adds import statements for the classes. Previously, you had to opt-in to this functionality using a property. In this release, this is now the standard product behavior.
When the script is executed at run time, the system uses the explicit imports to execute the script. Previously, the system had logic to import all callable classes available to Groovy at run time, which caused issues in certain cases. Because you may have custom scripts that still do not have the explicit imports, the system continues to fall back on the previous behavior to import all callable classes for scripts that do not compile with their explicit imports.
You should review your existing custom Groovy scripts and update the scripts to explicitly declare the imports.
By defining Groovy Imports explicitly in Groovy scripts, you can eliminate ambiguous class references and improves compilation time.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
The background process F1-CAGVY that reports all scripts that required the automatic import step to successfully compile. You should run this batch program to identify and fix any scripts missing explicit imports.
Improved Portal Zone Height Control
Zone height configuration is simplified and now supports the following options:
- Content (Unlimited Height) - Allows the the height to be determined by content.
- Content (Limited Height) - Allows the height to be determined by content up to a specified maximum limit.
- Fixed Height - Sets the zone at a specific height regardless of content.
You can use height limit options to achieve a more consistent portal layout, especially when a zone is rendered on long or small devices.
When a height option is not explicitly selected, zone height is unlimited and determined by content. However, for a data explorer zone, the results grid area itself (not the entire zone) is limited by the zone parameter "height of report" (which has a default value of 50%).
The following zone height options are deprecated and replaced as follows:
-
Content - Zones configured with this option along with a maximum height limit are upgraded to reference the Content (Limited Height) option. If no limit is specified, the Content (Unlimited Height) option is used.
-
Full - Zones configured with this option are upgraded to reference the Content (Limited Height) option with a 100% height limit.
-
Half - Zones configured with this option are upgraded to reference the Content (Limited Height) option with a 50% height limit.
You can enhance the configuration of portal zones to better and more simply control zone height.
Steps to Enable
You don't need to do anything to enable this feature.
New Base Display Icon Images Supplied
You can use additional SVG icons in contextual insights, trees, and other user interface features that support SVG icons.
| Icon | ID | Description |
|---|---|---|
 |
F1ACTADD |
Activities - Add |
 |
F1ARWODL |
Arrow - Open - Down - Left |
 |
F1ARWODR |
Arrow - Open - Down - Right |
 |
F1ARWOUL |
Arrow - Open - Up - Left |
 |
F1ARWOUR |
Arrow - Open - Up - Right |
 |
F1ARWSI |
Arrows - In |
 |
F1ARWSO |
Arrows - Out |
 |
F1ASAVE |
Save - Arrows Out |
 |
F1BOX |
Cube |
 |
F1CAL |
Calendar |
 |
F1CALL |
Telephone |
 |
F1CALLA |
Telephone - Add |
 |
F1CAREA |
Area Chart |
 |
F1CBXOFF |
Checkbox - Off |
 |
F1CBXON |
Checkbox - On |
 |
F1CDWNR |
Caret - Down - Right |
 |
F1CHDOWN |
Chevron - Down |
 |
F1CHDWNR |
Chevron - Down - Right |
 |
F1CIRCLE |
Circle |
 |
F1CLEFT |
Caret - Left |
 |
F1CLINE |
Line Chart |
 |
F1CLIST |
Progress List |
 |
F1CLPBC |
Clear List |
 |
F1CONSTD |
Construction Design |
 |
F1CPYTMP |
Copy From Template |
 |
F1CRAGG |
Running Aggregate Chart |
 |
F1CRCLE7 |
Progress Circle |
 |
F1CREATE |
Site - Add |
 |
F1CRIGHT |
Caret - Right |
 |
F1CRPAGE |
Page - Add |
 |
F1DAREA |
Draw Area |
 |
F1DWNLD |
Download |
 |
F1EDIT |
Edit |
 |
F1EDITIN |
Inline Edit |
 |
F1EXACRO |
Export Acrobat |
 |
F1FHAND |
Free Hand Draw |
 |
F1HEXGN |
Polygon - Hexagon |
 |
F1HOUSE |
House |
 |
F1HRGS |
Waiting Hourglass - Start |
 |
F1LAYERS |
Layers |
 |
F1LINEI |
Line - Inclined |
 |
F1LINEST |
Line - Staggered |
 |
F1LOC |
Location |
 |
F1LOCW |
Location Pin - Work |
 |
F1LOCWA |
Location Pin - Work - Add |
 |
F1MENUE |
Expand Menu |
 |
F1MOVE |
Move |
 |
F1MSG |
Message |
 |
F1MULT |
Multiply |
 |
F1NOTIF |
Notification |
 |
F1NUMS |
Numbers |
 |
F1OVAL |
Oval |
 |
F1PINS |
Location Pin - Solid |
 |
F1RECT |
Rectangle |
 |
F1RFRSH |
Refresh |
 |
F1RUNNIG |
Running |
 |
F1SCLOSE |
Close - Circled - Solid |
 |
F1SFILE |
Work Request - File Stage |
 |
F1SHARE |
Share |
 |
F1STPED |
Close - Circled - 2 Colors |
 |
F1TAG |
Tag |
 |
F1TEXT |
Text |
 |
F1TRIUP |
Triangle |
 |
F1VIEW |
View |
 |
F1WRKOA |
Gannt Chart - Add |
 |
F1ZOOMIN |
Zoom In |
Additional icons allow for a richer user experience for displayed information.
Steps to Enable
You don't need to do anything to enable this feature.
You can stay current with the version of Groovy supported by the product.
The product is using Groovy 3.0.7.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Groovy introduced a change in behavior in this newer version. It is unknown whether this change in behavior is intentional or a defect.
Here is one example error:
[Static type checking] - Cannot find matching method com.splwg.base.api.datatypes.Date#addDays(java.math.BigInteger).
Please check if the declared type is correct and if the method exists.org.codehaus.groovy.control.MultipleCompilationErrorsException:
startup failed: C1FATYPALMSG: 47: [Static type checking] - Cannot find matching method
com.splwg.base.api.datatypes.Date#addDays(java.math.BigInteger). Please check if the declared type is correct and if the method exists.
@ line 47, column 35.
Date referenceDate = row.getDateTime("SCHED_DTTM").getDate().addDays(row.getInteger("DAYS_ALERT_NBR"));
In the cases that we have, some simple changes can be made in the groovy scripts to resolve the compile issues.
For example:
Date referenceDate = row.getDateTime("SCHED_DTTM").getDate().addDays(row.getInteger("DAYS_ALERT_NBR").intValue());
Width Option for Contextual Insights
A new CSS helper class is available to the ou-insights web component: card-full-width. Adding class="card-full-width" to the ou-insights web component ensures that the width for a card insight adjusts to the width of the zone that contains it. Card insights that do not set this parameter use a fixed width.
Additional CSS helper class to control the width of a card insight allows better layout possibilities for user interface design.
Steps to Enable
You don't need to do anything to enable this feature.
Improved User Search for Assigning To Do Entries
The search for users provided in the Forward action on the To Do Entry portal now allows you to filter the result list by the user ID and/or user name.
User ID/Name Search Filter
In addition, the results list has been enhanced to display counts of To Do Entries already assigned to this user for the same To Do Type ("Assigned - This Type") and across all To Do Types ("Total Assigned").
Search Result List with To Do Entry Counts
In addition, the To Do Management portal's Assign action has been enhanced. If you are a supervisor using this action, you are prompted to choose the User to assign to. Previously, this prompt used a drop-down. In this release, you now use the same enhanced search. This allows you to filter the search by User ID or user name, and it also provides you with information about each user's current work load.
When assigning a To Do Entry, you can now filter the list by User ID and User Name. You can also see the number of To Do Entries each user already has assigned to them.
Steps to Enable
You don't need to do anything to enable this feature.
General Data Export - File Size Control
Generalized Data Export (GDE) batch processes produce a single file per thread by default. This may result in files that are too large to manage. An optional batch parameter Records in File has been added to the GDE batch processes to limit the number of records exported in a file. When specified, the batch process closes the current file when the number of exported records reaches the specified limit and a new file is opened for exporting the next set of records. This allows for multiple export files to be created for a single thread.
The F1-GEXPI (Generalized Initial Export Initiator) batch process has this limit set to 500,000 records per file but this value may be removed or adjusted by your implementation as needed.
The F1-GEEXO (Generalized Ongoing Export) batch process has been enhanced to better manage situations where the backlog of queued changes has become too large. In this situation, the next batch takes longer to export, which delays the downstream consuming step of the export files. The import step can only start once the manifest file is ready when the batch completes. In this release, the backlog can be cleared in smaller "chunks", allowing the downstream consuming process to import them as they are made available. To support this, an optional batch parameter Thread Processing Limit has been introduced to limit the number of records exported in a single run. Instead of waiting for the next scheduled batch run to process the next set of remaining entries, a new batch process may be automatically submitted if requested by the Automatic Backlog Clearance batch parameter. The batch process has this limit set to 500,000 records and enables automatic backlog clearance. These parameters may be adjusted by your implementation as needed.
This allows you to produce smaller Generalized Data Export (GDE) files.
Steps to Enable
You don't need to do anything to enable this feature.
General Data Export - Ongoing Export Enabled On-Premise
The ongoing export feature of the Generalized Data Export functionality is enabled for on-premise installations.
This provides on-premise installations with the ability to continuously export data as it changes.
Steps to Enable
You don't need to do anything to enable this feature.
General Data Export - Thread Allocation Control
By default, each export batch submitted by the F1-GEXPI (Generalized Initial Export Initiator) batch process uses the number threads defined on the maintenance object's specific batch control record. This allows for a more optimal configuration of the number of threads to allocate to a specific batch based on the size of the corresponding maintenance object.
In this release, an optional batch parameter Override Number of Threads is introduced to override this value. When set to "Y" the default value is overridden with the number of threads the initiator batch is submitted with. This allows for a global number of threads allocation that does not require a specific value on each specific export batch control.
Note that this override capability only applies to master and transaction entities. Admin entities are of low volume and therefore should use their default value, which is typically a single thread.
You can fine tune the number of threads allocated to each initial export batch process when submitted via the F1-GEXPI (Generalized Initial Export Initiator) batch process.
Steps to Enable
You don't need to do anything to enable this feature.
Oracle Guided Learning Integration
This integration provides a mechanism for customers of the Oracle Guided Learning Cloud Service to define their application identifier (to identify their tenancy) in a configuration parameter. This will automatically enable the learning widget to appear on the screen passing in the user details and the context to allow relevant content to appear.
Oracle Guided Learning Cloud Service Widget
NOTE: This integration is to enable the definition of the application identifier and the display of the widget. No prebuilt content is available at this time. Customers using this facility are free to add their own content as necessary using the Oracle Guided Learning Cloud Service.
NOTE: This integration only allows links to procedures and processes stored within Oracle Guided Learning. It does not support active workflow integration to Oracle Utilities products in this release.
The Oracle Guided Learning cloud service allows utilities to provide access to contextual policies, business processes, and training materials from Oracle Utilities products. This integration allows customers to link their Oracle Guided Learning subscription and enables an on screen widget to enable the integration.
Steps to Enable
Work with your Service Delivery Manager to complete the required configuration.
Consolidation of Default Application Services
The product has consolidated the default application services that are required for basic application security.
-
F1-DFLTS now serves as the single 'default' application service. All user groups should have access to this application service and all its access modes.
-
F1-DFLTAPS was previously used for business services and service scripts as the default application service. Going forward, business services and service scripts should use F1-DFLTS as the default.
-
FWLZDEXP was previously used for displaying zones. It is no longer used by base zones. F1-DFLTS is the only application service needed for basic execution of zones.
This consolidation reduces the number of application services required for users to have basic application security.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
An upgrade script will proactively update any references in the metadata to F1-DFLTAPS or FWLZDEXP to F1-DFLTS. Implementations should consider if either of these application services are used directly in code and update those references to use F1-DFLTS or a different appropriate application service.
In addition, an upgrade script ensures that all user groups with access to F1-DFLTAPS now have F1EX access to F1-DFLTS.
In a future release, the application services F1-DFLTAPS and FWLZDEXP will be removed from support.
New Application Service for Master Configuration Maintenance Object
The F1-MASTERCONFIG application service is provided to allow you to secure the maintenance of master configuration records separately from the security for the portal used to view master configuration records. This follows the product's standards. Previously, the same application service applied to both the maintenance object and the portal. This prevented you from more granular security configuration.
This allows for more flexible and granular security configuration.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
An upgrade script updates all user groups that currently have access to the existing F1MSTCFG application service to have the same access to the new F1-MASTERCONFIG application service.
In addition, any business object that was referencing the F1MSTCFG application service has been updated to reference F1-MASTERCONFIG.
Note that the existing F1MSTCFG application service has been updated to reference only the Inquire access mode. The access modes for Add, Change, and Delete have been removed since they are not applicable for a portal-based application service.
See a preview of the database changes coming for 22A in the Oracle Utilities Cloud Services Database Changes Guide. This guide is also available in PDF.
This includes information about databases changes to tables, indexes, views, columns, and more.
Steps to Enable
You don't need to do anything to enable this feature.
Supported Platforms and Browsers
Oracle Utilities 22A Cloud Services support the following operating system and web browser combinations:
| Operating System |
Web Browsers |
|---|---|
| Windows 10 |
Firefox ESR 91+ Chrome for Enterprise 96+ Microsoft Edge (Chromium-based) 96+ |
| iPad2 iOS 10.x (WACS only) |
Safari (selected flows and portals only) |
Oracle recommends using only supported client platforms and browsers.
Steps to Enable
Use only supported platforms and browsers.
IMPORTANT Actions and Considerations
REPLACED OR REMOVED FEATURES
From time to time, Oracle replaces existing cloud services with new features, or removes existing features. Replaced features may be put on a path to removal. As a best practice, you should use the newer version of a replaced feature as soon as a newer version is available.
This section identifies the features in this Cloud service that have been replaced or removed.
| Product | Removed Feature | Target Removal | Replacement Feature | Replaced In | Additional Information |
|---|---|---|---|---|---|
| Oracle Utilities Application Framework | Field Legacy Page Metadata |
22A | Portal-based User Interface | 21B | Navigation Keys:
Records in the UI metadata program component tables related to the above navigation keys. |
| Oracle Utilities Application Framework | Portal Legacy Page Metadata |
22A | Portal-based User Interface |
21C | Navigation Keys:
Records in the UI metadata program component tables related to the above navigation keys. |
| Oracle Utilities Application Framework | Zone Legacy Page Metadata | 22A | Portal-based User Interface | 21C | Navigation Keys:
Records in the UI metadata program component tables related to the above navigation keys. |
Unless otherwise specified below, these notes are for informational purposes and no action is required.
PRODUCT CHANGES
BI / Analytics Publisher Changes
The name of Oracle BI Publisher has changed to Oracle Analytics Publisher.
Oracle Analytics Publisher is intended for low-volume, operational reporting. Use of Oracle Analytics Publisher for high volume reporting and extracts such as batch bill printing is not supported in Oracle Utilities Cloud Services.
PLANNED REMOVAL
Plan to Remove Switch UI View from Oracle Utilities Application Framework
The Switch UI View provides the ability to toggle between Redwood User Experience and pre-Redwood User Experience during a session. Support for pre-Redwood User Experience will be deprecated in a future release.
Plan to Remove F1-DFLTAPS and FWLZDEXP Application Services from Oracle Utilities Application Framework
With the consolidation of application services, references to the F1-DFLTAPS and FWLZDEXP application services will be removed in a future release. Secured objects referencing these application services within HTML or Schemas must use F1-DFLTS or a different application service that is appropriate for the business rule.
Plan to Remove Workflow and Notification Metadata and Database Tables from Oracle Utilities Application Framework
The Workflow and Notification function provided a configurable process to receive incoming messages (workflow) and exchange messages with an external system (notification). In the interim years, Outbound Message and Inbound Web Service manage external messages, service scripts handle simple incoming messages processing, and service tasks or business objects handle complicated incoming messages processing. The Workflow and Notification metadata and database tables will be deprecated in a future release.
NOTE: Oracle Utilities Application Framework only manages a portion of the Workflow and Notification function. Oracle Utilities Customer Care and Billing mostly supports the function.
Plan to Remove Mobile Application Framework Metadata from Oracle Utilities Application Framework
Metadata related to the Mobile Application Framework will be removed in a future release.
Plan to Remove Key Ring Validation Scripts, Algorithm Types, and Algorithms from Oracle Utilities Application Framework
The following K1-SignatureKeyRing business object validation scripts, algorithm types, and algorithms will be deprecated in a future release:
- Algorithm
- K1-KRDCKFS
- K1-KRINCKFS
- Algorithm Type
- KRDCKFS
- K1-KRINCKFS
- Message
- 11009 / 1402
- Plugin Script
- K1-KRDCKFS
- K1-KRINCKFS
- Service Script
- K1-ChkCfgExL
These objects are not applicable to the requirements to expand the use of the Signature Key Ring beyond object file storage and other planned use cases. The algorithms have been removed from the Business Object configuration.
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 these are used on other fixed pages.
| Field Maintenance | Portal Maintenance | Zone Maintenance | To Do Entry Maintenance |
|---|---|---|---|
| impFldTabMenu metaDataFieldMainPage metaDataFieldMaint metaDataFieldTableGrid metaDataFieldTablePage Any help navigation keys |
portalTabMenu portalMainPage portalMainPopup portalOptsGrid portalOptsPage Any help navigation keys |
portalZoneTabMenu portalZoneMainPage portalZoneGridPage portalZoneParameterGrid portalZonePortalGrid portalZonePortalPage Any help navigation keys |
toDoEntryCharGrid toDoEntryDrillKeyValuesListGrd toDoEntrySortKeyValuesListGrid todoentrykeyvalue todoentrymain toDoEntryMaint toDoEntryPopupAdd toDoEntryPopupForward toDoEntryPopupSendBack Any help navigation keys |
| Table Maintenance | Work Calendar Maintenance | Message Maintenance | Time Zone Maintenance |
|---|---|---|---|
| metaDataTableFieldsGrid metaDataTableMainPage metaDataTableCFldsGrid metaDataTableConstPage metaDataTableMaint metaDataTableRefByConstPage metaDataTableFieldPage Any help navigation keys |
workCalendarMaint workCalendarMainPage workCalendarHolidayGrid Any help navigation keys |
msgMaintDetailsPage msgMaintGrid msgMaintPage msgMaintTabMenu Any help navigation keys |
timeZoneMainPage timeZoneTabMenu Any help navigation keys |
Plan to Remove Miscellaneous System Data from Oracle Utilities Application Framework
The following metadata is no longer in use and will be removed in a future release:
| Object | Data | Description/Comments |
|---|---|---|
| Lookup Value |
CHAR_ENTITY_FLG / F1SE |
Characteristic Entity / Sync Request Inbound Exception |
| Script |
F1-TDMgActSS |
To Do Management - Process Actions (Deprecated) / Replaced by F1TDMgActSS |
| Script |
F1AddDebugLg |
Add Log for Monitoring Probe (Deprecated) / Replaced by a BS - F1-MONPRBLOG |
Plan to Incorporate Application Viewer to Oracle Utilities Applications
Many aspects of the Application Viewer are incorporated into the application, including the data dictionary. The user interfaces for the tables and fields have been enhanced to provide more information at a glance and a view of the links between tables. Information about algorithms, batch controls, and maintenance objects are also visible directly in the application. In a future release, Javadocs and Groovy Javadocs will be viewable within the application at which point the standalone Application Viewer will no longer be delivered.
Plan to Remove XSLT Managed Content Type from Oracle Utilities Application Framework
The Managed Content table entries related to XSL should use the XSLTC managed content type instead of the XSLT managed content type. Support for the XSLT managed content type will be deprecated in a future release.
Plan to Remove REST IWS - Original REST Servlet from Oracle Utilities Application Framework
The original URL supplied for calling Inbound Web Service-based REST services includes the Inbound Web Service name in its makeup. Support for this will continue for backward compatibility purposes, but 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 associated with the pagination's Append option. It is recommended that you defer from using 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 to Oracle Integration Cloud.
Plan to Remove Support for Batch Run Statistics Portal Functionality in Oracle Utilities Application Framework
The Batch Run Statistics portal provides additional information about batch runs, but some functionality on the portal is related to capturing additional information from an external tool. Additional information captured from the external tool is stored in a Fact record. Support for capturing additional information from an external tool will be discontinued in a future release. The captured additional information would still be available to existing customers.
Plan to Remove Configuration Migration Assistant Import Requests from Oracle Utilities Application Framework
The F1-FrameworkAdmin (Framework Admin) and F1-SchemaAdmin (Schema Admin) migration requests are no longer recommended and will not be updated with new administration or control table in a future release.
Plan to Remove Configuration Migration Assistant Import Algorithm from Oracle Utilities Application Framework
The Configuration Migration Assistant Import algorithm plug-in spot will be deprecated in a future release. It is recommended that you review any existing algorithms and create the appropriate Pre-Compare algorithms instead.
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) does not perform a Read of the business object when a pre-processing script is linked to the business object via options. When F1-MainProc does not perform a Read, the pre-processing script performs the Read of the business object.
In a subsequent release, a business object Read was added to F1-MainProc (with an existing pre-processing script) to resolve a UI Hints issue related to child business objects. Adding a business object Read to F1-MainProc introduced an issue visible only to specific scenarios and a different fix was introduced. The new fix made the business object Read unnecessary in F1-MainProc and many pre-processing scripts are properly performing the business object Read. The business object Read should have been removed from F1-MainProc to prevent multiple reads from being performed. However, pre-processing scripts may have been introduced after the addition of the business object Read to F1-MainProc that do not perform a business object Read in the pre-processing script. As such, the business object Read is still performed as part of the F1-MainProc processing.
When a pre-processing script exists, the business object Read will be removed from the F1-MainProc logic. Review your custom pre-processing scripts that are linked to business object options to ensure that the scripts properly perform reads of your business object.
Plan to Remove Support for Groovy-based Functions from Oracle Utilities Testing Accelerator
Support for Groovy-based plugin functions and upload test-based plugin functions will be deprecated in a future release. Groovy-based functions must be manually migrated to the supported JavaScript functions.