IMPORTANT Actions and Considerations
Upgrade Actions
With every upgrade, make sure to complete the following steps in the Initial Set Up functional area in Functional Setup Manager. This process ensures all new security definitions, such as job roles, duty roles, privileges, and so on, are included in your implementation.
- Run Public Sector Security Setup Process
- Manage Custom Roles
Introduced in 24B, the feature Managing the Intake Form Metadata Cache for Improved Performance, was released to help manage cache problems that may arise in production after patching or updates to new releases. Please refer to the Steps to Enable for this feature to set up new process scheduler jobs to run weekly.
REST Backward Compatibility
Public Sector Permitting and Licensing updates REST APIs from release to release. Our goal is to not create APIS that are incompatible from one release to the next. However, due to circumstances and security impacts this may not be feasible.
For the most current information, see My Oracle Support Document ID: 2853758.1.
Documentation for all REST APIs included in Oracle Permitting and Licensing can be found on the Oracle Help Center.
Redwood Experience
Over the course of the next several updates, Oracle Permitting and Licensing will be transitioning to a new enhanced user experience built with the Visual Builder Studio (VBS) and the Redwood toolset. Functionality will remain the same or be enhanced, though the new experience may change how users complete certain functions.
Overall, many of the Redwood Experience updates will be delivered as opt-in features, meaning you will have the choice to continue using the classic version or uptake the equivalent new Redwood Experience pages in the first release in which they are delivered. This gives you time to plan for and test the new pages before you use them. In the next release, the classic pages will be removed and the equivalent new Redwood Experience pages must be used. By exception, there may be cases where the classic pages remain available for more than one release. Users can interact with a combination of classic and Redwood pages. While the visual design of the pages may differ, they will continue to function as one seamless system.
Our goal is a cohesive and streamlined all-Redwood Experience. This aligns with the transition underway for all Oracle Fusion Cloud applications. Additionally, with an application built entirely using Visual Builder Studio (VBS) you will have the ability to customize and enhance what we deliver, or create new capabilities using the same toolset. You can find information regarding Visual Builder Studio on the Oracle Help Center.
The following table outlines the Functional Setup Manager options for delivered Redwood Experience Features.
- Initial Release: Initial release for the new Redwood Experience feature/page.
- No Opt-In: Release in which the feature is delivered as "ON" in Functional Setup Manager (FSM). You do not have to do anything to use the new Redwood Experience feature/page. You have the option to go into FSM and turn the feature/page off. By turning the feature off, you will default to the classic page.
- Mandatory: Release in which you will no longer be able to use the classic version of the page and you must use the new Redwood Experience page.
Redwood Experience No Opt-In
| Feature Name/Page | Initial Release | No Opt-In (Default On) | Mandatory |
|---|---|---|---|
| Redwood Experience for User Registration and Account Management | 24A | 24A | 24D |
| Redwood Experience for Code Enforcement Public Users |
24A - Resolve an Issue, Code Enforcement Payments 24B - Track My Issue, Report an Issue |
24C | 24D |
Oracle Integration Cloud (OIC) Generation 2 to Generation 3 Separates Integrations and Processes Components
Starting in 24B, new customers provisioning environments will be provisioned and configured with OPA Generation 3. OIC Generation 2 or OIC Generation 3 will not be available. Existing customers will remain on OIC Generation 2 for integration, workflow, and fee decision modeling. OPA will be available in your pods, but it won't be utilized until a future release. You can find updated information regarding this migration on My Oracle Support Document ID: 3005969.1, Oracle Integration Cloud (OIC) Generation 2 to Generation 3.