The next release of the Oracle Utilities Application Framework (4.3.0.4.0) is in its final implementation across our product lines over the next few months. This release improves the existing Oracle Utilities Application Framework with exciting new features and enhanced existing features for our cloud and non-cloud implementations. Here is a summary of the key features of the new Oracle Utilities Application Framework.
Main Features
CMA Improvements
The following highlights some improvements to CMA processing.
Ad-hoc Migration Requests
A new migration request BO has been provided to allow for building ‘ad-hoc’ migration requests using a list of specific objects. It’s called the “entity list” migration request.
A special zone is included to find records to include in the migration request. This zone allows you to choose a maintenance object that is configured for CMA and enter search criteria to get a list of objects to choose. The zone supports linking one or more objects for the same MO en masse.
Once records are linked, a zone allows you to view the existing records and remove any if needed.
Grouping Migration Requests
Migration requests may now be grouped so that you can maintain more granular migration requests that get grouped together to orchestrate a single export of data for a ‘wholesale’ migration. The framework supplies a new ‘group’ migration request that includes other migration requests that logically group migration plans. Edge products or implementations may include this migration request into their own migration request.
Mass Actions During Migration Import Approval
When importing data sets, a user may now perform mass actions on migration objects to approve or reject or mark as ‘needs review’.
Groovy Library Support
Implementers may now define a Groovy library script for common functionality that may be included in other Groovy scripts.
There’s a new script type:
Scripts of this type define a Groovy Library Interface step type to list the Groovy methods defined within the script that are available for use by other scripts.
Additional script steps using the Groovy Member step type are used to define the Groovy code that the script implements.
Groovy scripts that choose to reference the Groovy Library Script can use the createLibraryScript method provided by the system to instantiate the library interface.
Search Menu Capability
A new option in the toolbar allows a user to search for a page rather than using the menu to find the desired page.
All menu items whose label matches what the user types are shown (as you type):
Additional Features
The following is a subset of additional features that are included. Refer to the published release notes for more details.
- URI validation / substitution. Any place where a URI is configured can now use substitution variables to support transparency across environment. The fully substituted value can also be validated against a whitelist for added security.
- Minimizing the dashboard suppresses refresh. This allows a user to improve response when navigating throughout the system by delaying the refresh of zones in the dashboard while it is minimized.
- New support for UI design. Input maps may now support half width sections. Both display and input maps may support “floating” half width sections that fill in available space on the UI based on what is displayed.
- Individual batch controls may now be secured independently.
- Ad-hoc batch parameters are supplied to all batch related plug-in spots. Additionally, plug-in driven batch programs may now support ad-hoc parameters.
- Elements in a schema that include the private=true attribute will no longer appear in the WSDL of any Inbound Web Service based upon that schema.