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
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 Public Sector Permitting and Licensing can be found on the Oracle Help Center.
Business Rules Framework Settings Review
As you adopt the most recent update, it’s recommended to review and confirm that your settings are current for:
- Automated action retry
- Error email notification
Reviewing Automated Action Retry Settings
You can set up the Business Rules Framework to retry any actions that don't complete successfully upon the initial action run. Configuring automated action retry involves setting the:
- Action retry schedule through Enterprise Scheduler Service (ESS).
- Agency-level action retry options to set the number of times the system will retry the action.
For the detailed steps see Implementing Permitting and Licensing, “Implementing Business Rules Framework,” Scheduling Automated Action Retry.
Reviewing Error Email Notification Settings
Being able to send email notifications of errors related to business rule completion is an efficient way to bring potential issues quickly to the attention of system administrators. It is recommended to regularly confirm the email addresses being sent the error notifications.
For the detailed steps see Implementing Permitting and Licensing, “Implementing Business Rules Framework,” Viewing Business Rule Logs, Setting Up Email Notifications for Errors.
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.
For more information regarding the delivered features and opt-in options see My Oracle Support: Redwood Experience for Oracle Permitting and Licensing (Document ID: 3023318.1)
The following table outlines the delivered Redwood Experience features and the current Functional Setup Manager options available along with the release of mandatory uptake.
|
Feature Name/Pages |
Initial Release |
Optional (Default On) |
Mandatory |
|---|---|---|---|
| Redwood Experience for User Registration and Account Management | 24A | 24A | 25A |
| Redwood Experience for Code Enforcement Public Users |
24A (Resolve an Issue, Code Enforcement Payments) 24B (Track My Issue, Report an Issue) |
24C | 25A |
| Redwood Experience for Mobile Inspector |
24B |
25C | 25D |
| Redwood Experience for Agency Facing Account Management |
24C |
N/A | 25A |
| Redwood Experience for the Apply Page |
24C |
25A | 26B |
| Redwood Experience for Code Officer Mobile Application |
24C |
N/A | 26B |
|
Redwood Experience for Application Intake (Permits and PNZ) Make a Payment (Permits, PNZ, and Business Licenses) Transaction Lists (Permits, PNZ, and Business Licenses) |
24D |
25A** | 26B |
|
Redwood Experience for Permit Details |
25A | 25B | 26B |
|
Redwood Experience for Deposit Account List and Details |
25A | 25D | 26B |
**Before your environment is updated to 25A, it's important that you complete the following steps to ensure that your transaction and application lists populate properly:
- Log into the Fusion home page as an administrator/super user.
- Navigate to Tools > Schedule Processes page.
- Run the ESS job, "ESS job to create index definition and perform initial ingest to OSCS".
- Give the Index Name parameter "fa-psc-applications".
- The Transaction List and Application List pages will populate only after running this ESS job successfully.
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.
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.
Deprecated Features
On occasion, Oracle replaces existing features with new features or removes existing features altogether. When a feature is replaced, the older version may be removed immediately or in the future. As a best practice, you should use the new version of a replaced feature as soon as the newest version is available.
Currently, Oracle Permitting and Licensing offers two methods to generate accounting: Public Sector Accounting and Oracle Financials Subledger Accounting.
Starting in 25A, Public Sector Accounting will be deprecated and only Financials Subledger Accounting will be available. Customers can use Financials Subledger Accounting to generate accounting and can post transactions to Oracle Fusion General Ledger or export the data to a third-party general ledger. If you are currently using Public Sector Accounting, you will continue to have access to the accounting pages for reference and historical purposes via Functional Setup Manager but configuration and further use of Public Sector Accounting will not be available.
For information regarding the implementation of Oracle Financials Subledger Accounting, see Implementing Your Financial Framework, "Setting Up Accounting," on the Oracle Help Center.