What's New

Update 24B

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Overview

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.

GIVE US FEEDBACK

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.

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.

Optional Uptake of New Features (Opt In)

Oracle Cloud Applications delivers new updates every quarter. This means every three months you'll receive new functionality to help you efficiently and effectively manage your business. Some features are delivered Enabled meaning they are immediately available to end users. Other features are delivered Disabled meaning you have to take action to make available. Features delivered Disabled can be activated for end users by stepping through the following instructions using the following privileges:

• Review Applications Offering (ASM_REVIEW_APPLICATIONS_OFFERINGS_PRIV)
• Configure Oracle Fusion Applications Offering (ASM_CONFIGURE_OFFERING_PRIV)

Here’s how you opt in to new features:

1. Click Navigator > My Enterprise > New Features.
2. On the Features Overview page, select your offering to review new features specific to it. Or, you can leave the default selection All Enabled Offerings to review new features for all offerings.
3. On the New Features tab, review the new features and check the opt-in status of the feature in the Enabled column. If a feature has already been enabled, you will see a check mark. Otherwise, you will see an icon to enable the feature.
4. Click the icon in the Enabled column and complete the steps to enable the feature.

For more information and detailed instructions on opting in to new features for your offering, see Configure Offerings.

Opt In Expiration

Occasionally, features delivered Disabled via Opt In may be enabled automatically in a future update. This is known as an Opt In Expiration. If your cloud service has any Opt In Expirations in this update, you will see a related tab in this document. Click on that tab to see when the feature was originally delivered Disabled, and when the Opt In will expire, potentially automatically enabling the feature. You can also click here to see features with current Opt In Expirations across all Oracle Cloud Applications. Beyond the current update, the Financials forums on Cloud Customer Connect have details of Opt In Expirations upcoming in future updates.

Feature Summary

Permitting and Licensing

Permitting and Licensing Common

Enforcement of Required Documents

The system now checks for the presence of attachments with the required category or category and subcategory pair and displays an error if the required documents haven't been added to the application. The list of Required Documents appears on the application intake form and on the Attachments page in the application details after submittal. The list displays the category and application step requirements and whether the attachment has been added.

The document category or category and subcategory pair can be required at any of these 5 application steps or events:

• Application Submittal
• Application Issuance
• Application Acceptance
• Final Inspection
• Application Complete

Not all of these steps or events apply to all offerings. For example, Issuance and Final Inspection don't apply to planning applications. Only documents required at the Application Submittal step are required before the applicant can submit the application.

This example illustrates the Required Documents grid on a permit application form as viewed by agency staff with permission to override the required documents. Note that the agency staff has uploaded the documents required for application submittal.

Required Documents Grid on an Application Intake Form

For application steps that are Workflow events, the system sends a communication to the applicant to notify them that a required document is missing and needed. The Business Rules Framework events with a "Send" communication action include:

• Business License Missing Document
• Permit Missing Document
• Planning Missing Document

Agency staff with permissions can override document requirements and remove files. Public users can't delete required documents once they have been uploaded for prior application steps.

This allows agencies to control when specific documents are required throughout the application process.

Steps to Enable

Enforces that required documents are present at various application steps.  Existing setup is used to now enforce required documents. 

IMPORTANT! If setup is pre-existing, required documents will be enforced on upgrade.

In Permitting and Licensing 22D, required documents was released. You can configure required documents through Document Category and Subcategory setup. Once they are setup they are placed in a document group used on the Permit, Business License, or Planning Application Type set up pages. Once this is set up, users will get an error message if they try to submit an application or transaction that requires a document that is not present.

To set up required documents (as delivered in 22D):

1. Navigate to Common Setup > Document Category.

2. For each transaction type (Business License, Permit, Planning and Zoning) create the document category and subsequent subcategories that you need. Here you can set the "Required Document Application Step". See Implementing Your Agency, "Setting Up Documents", Setting Up Document Categories and Subcategories.

3. Once your categories and subcategories are created, add them to the document group. See Implementing Your Agency, "Setting Up Documents", Setting Up Document Groups.

4. Once added to the document group, link that document group to the permit, planning or business license types you need. See Implementing Permitting and Licensing, "Setting up Permits", Setting Up Permit Types.

5. Once documents are required by transaction type, For example, if a document is required when the user clicks Submit, an error is shown.

6. You need to update your workflow tasks that prompt for Required Documents.
   1. During application acceptance, set the workflow task custom property PSC_ACTIVITY_TYPE to "Accept Application" and PSC_FINAL_ACTIVITY to "No". See Implementing Permitting and Licensing, "Setting Up Workflow" on the Oracle Help Center.
   2. During application issue, set the workflow task custom property PSC_ACTIVITY_TYPE to "Issue" and PSC_FINAL_ACTIVITY to "No". See Implementing Permitting and

If you are using workflow communications, in 24B you need to set up communication templates for the following Business Rules Framework events:

• Business License Missing Document
• Permit Missing Document
• Planning Missing Document

To set up workflow communications:

1. Navigate to Common Setup > Business Rules Framework.

2. Select the offering you want to set up, for example Permits.

3. Select Permit Missing Document event.

4. Set up the business rule event details with a Communication action. See Implementing Permitting and Licensing, "Implementing the Business Rules Framework".

5. Complete the steps for the other Business Rules Framework events: Business License Missing Document and Planning Missing Document.

Tips And Considerations

This feature was partially delivered in 22D, including setup on the Document Categories and Document Subcategories pages and application types for business licenses, permits, and planning applications. Required documents have been displayed since 22D on the application intake form and application details. Now, in 24B, you can set up Business Rules Framework events for missing document communications.

Required documents can be required at multiple application steps. However, Oracle recommends that you require a document at only one application step at the earliest that it is needed. Registered public users cannot delete a document once it has been used in a step. Requiring the same document at multiple steps will over complicate the application process. Agency staff can delete a required document once it's been used, but it is expected that once a required document has been uploaded that it will be present for the life of the transaction.

Key Resources

• See Implementing Permitting and Licensing, "Setting Up Permit Types" on the Oracle Help Center.

• See Implementing Your Agency, "Setting Up Documents", Setting Up Document Categories and Subcategories; Setting Up Document Groups; and Setting Up Required Documents on the Oracle Help Center.

• See Using Community Development Permits, "Completing an Application" Attachments on the Oracle Help Center.

Inspections with Unannounced Inspector Arrival

Agencies can now configure inspection types to be hidden from public user view in the application until the inspector has submitted the inspection results.

For example, if a Health and Safety inspection is set up as an unannounced or surprise inspection, the inspector arrives to perform the inspection without any prior communications or visibility to the applicant or contacts. Once the inspector provides the inspection results, the applicant or other contacts with application access can see the inspection details and results. If the inspection fails, agency staff can schedule the reinspection, which is also unannounced.  Public users can't request unannounced inspections or reinspections.

This example illustrates the switch used to make an inspection type unannounced.

Inspection Type Details Page

The Unannounced field that indicates whether an inspection is viewable by the applicant or not, is available only to agency staff on the inspection request, inspection details, and inspections list in the application details. This example illustrates the Unannounced field on the agency's view of the inspections list page for a business license transaction.

Agency View of the Inspections List Page in the Application Details

Public users can only see the unannounced inspections after the inspector submits the inspection results. The system prevents inspection communications for unannounced inspections from being sent to public users so they are not made aware that an unannounced inspection is about to take place. These communications include:

• Permit Inspection Canceled
• Permit Inspection ETA Updated
• Permit Inspection Postponed
• Permit Inspection Requested
• Permit Inspection Rescheduled
• Permit Inspection Scheduled

This feature allows an agency to hide internally scheduled inspections to prevent public users from preparing.

Steps to Enable

To enable this feature you must select the "Unannounced" switch on the Inspection Type Setup page.

1. Navigate to Inspection Setup > Inspection Type.
2. Select the inspection type you want to modify.
3. Turn on the Unannounced switch.

Once the switch is enabled, you'll see the Unannounced column on the Inspection Group Setup page. Only agency staff will be able to select unannounced inspection types when creating inspections.

Tips And Considerations

This will only happen for newly scheduled internal inspections once implemented. Any inspections that are already scheduled will continue to show scheduling information to the public.

Only agency staff will see unannounced inspections until the inspection has a result.

Business Rules Framework can't be configured to send a particular template/communication based on the value in the Unannounced field.

Key Resources

• See Implementing Permitting and Licensing, "Setting Up Inspections," Setting Up Inspection Types, Setting Up Inspection Dependencies, and Setting Up Inspection Groups on the Oracle Help Center.

• See Using Community Development Permits, "Working with Permit Inspections," Managing Inspections for a Permit and Requesting Inspections on the Oracle Help Center.

• See Using Business Licenses, "Working with Business License Inspections," Managing Inspections for a Business License Application and Requesting Inspections on the Oracle Help Center.

Financial Framework

Fee Due Date in Communication Events

Applicants receiving fee related notifications will now see the payment due date along with the assessed fee amount.

This alerts applicant not only of the fees but when they are due.

Steps to Enable

To enable this feature, you need to update your communication templates to include the fee due date in the message body grid, as needed.

1. Navigate to Communication Setup > Communication Events.
2. Select the communication event you want to update.
3. Click the Add button to add a communication template or click on the communication template you want to update.
4. In the Communication Template Details, click Add Grid.
5. Select Due Date from the list, and click Insert Grid in Message.
6. On the Communication Template Details page, you'll see the message added to the body of the message.

Key Resources

• See Implementing Your Agency, "Setting Up Communications", Delivered Communication Events on the Oracle Help Center.

Open API Framework for Third-Party Payments and Cashiering

Agencies can use third-party payment providers (including cashiering systems) to process payments. They can outsource the settlement of payments (how the agency or consumer would want to pay) to a third-party payment system to offer flexibility and scalability for agencies to process OPAL payments.

The Open API Framework:

• Provides a lookup service to support requests for permits, planning and zoning applications, business licenses, citations, code violations, or hearing fees that are due.

• Provides an API to receive a payment confirmation and mark the fees as paid.• Provides an API to receive a void payment and reverse the payment and mark the fees as due.

• Enables agency staff to issue an offline refund for payments processed by the third-party payment provider.

• Enables agency staff to redirect the self-service user to an authenticated third-party payment provider page to make a payment.

Agency staff can:

• Configure Third Party Payment Options to enable payments in a third-party payment system.

• Configure contextual help to display the Third-Party Disclaimer that should be displayed before re-directing the user to the third-party payment page.

• Configure contextual help to display the Payment Method list that will be supported by the third-party payment system.

Registered public users can make payments for fees in the third-party payment system.

The Open API Framework provides agencies with the option to lookup fees, process payments and manage payment returns in a third-party payment platform, including cashiering solutions.

Steps to Enable

To enable the open API framework for Third-party payments and cashiering requires you to:

• Set up users and a new role.
• Configure third-party payment options.
• Configure contextual help to display the third-party disclaimer.
• Configure contextual help to display the payment method list.
• Configure the third-party re-direct.
• Configure the fee lookup service.
• Configure payment confirmation.

All configuration details are documented in the "Setting Up Third-Party Payment Integration (Document ID: 2987980.1) on My Oracle Support.

Tips And Considerations

Agencies can choose to implement one of the following options:

1. Engage with a third-party payment service provider and configure the system to process payments by the third-party payment service provider through open API framework.

2. Engage with a payment gateway supported by Oracle and configure the system to process online payments through the payment gateway.

Key Resources

• See Implementing Your Financials Framework, "Setting Up Payments," Setting Up Third-Party Payments on the Oracle Help Center.
• See Setting Up Third-Party Payment Integration (Document ID: 2987980.1) on My Oracle Support.

Business Rules Framework

Business Rules Framework Events to Submit Application

Agencies can now configure a Business Rules Framework event to automatically perform actions when an application is submitted successfully.

Use the following events to set up the business rule for the applicable offering:

Agencies can set up automatic actions for submitted applications.

Steps to Enable

To configure these events:

1. Navigate to Common Setup > Business Rules Framework.
2. Select the offering.
3. Select the event. 
4. Enter your business rule criteria.
5. Select an available action for the rule to trigger.

Key Resources

• See Implementing Permitting and Licensing, "Implementing the Business Rules Framework," Setting Up Business Rules on the Oracle Help Center.

Increased Object Support for Scheduled Rules

You now define scheduled rules the same way you create event-triggered rules. When you select Scheduled Rules from the Business Rules Framework landing page you first select from the events list instead of navigating directly to the Scheduled Rules list.

Scheduled Rules Page

When defining criteria for a scheduled rule you now have access to intake form objects, reusable fields, predefined fields, and GIS criteria where appropriate.

Criteria Dialog Box

Provides additional data to incorporate into business rules and brings more consistency between the development of event-triggered rules and scheduled rules.

Steps to Enable

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

Tips And Considerations

Existing scheduled rules and the events they are associated with have not changed, only the navigation to get to the Rules Details page.

Key Resources

• See Implementing Permitting and Licensing, "Implementing the Business Rules Framework," Setting Up Scheduled Rules on the Oracle Help Center.

Reporting and Analytics

Application Duration and Status Report

The Health Metrics BIP report helps customers identify potential blockages throughout their agency-defined, end-to-end application lifecycle.  There are several metrics that are tracked:

• Application In Count: the number of applications that have a particular status during the reporting time period. For example, when an application goes into Review status.

• Application Out Count: the number of applications that leave a particular status during the reporting time period. For example, when an application goes out of Review status. 

• Backlog: the number of applications that remain in a status during the time period. Essentially, this is the difference between applications in and out, in addition to carry-over backlog counts from previous reporting periods. The backlog count can help identify potential workflow blockages. 

• Average Duration: the average number of days that an application will take to complete for a specific status. For example, an average of 3.5 days in Review status indicates that it takes an average 3.5 days for all applications to be completed.

In addition, the embedded graphs illustrate the trends in the underlying changes in the metrics, as shown below:

Health Metrics Report 

This report surfaces the key metrics that impact the application life cycle and take early corrective actions.

Steps to Enable

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

Tips And Considerations

This report is available in the BI Catalog and should be run from the BI Portal.

You can limit the data using the prompts provided in the report. Date range for the chart data is calculated based on the report date and report period. Report period can only be 'Last 4 weeks' or 'Last 4 months'. For example, if you select 4 weeks, then From Date = Start of the week for (Report date - 4 weeks) and the To Date = End of the week for (Report date).

Key Resources

• See Implementing Your Agency, "Setting Up Analytics," Setting Up Reports on the Oracle Help Center.

Code Enforcement Hearing Agenda Report

A BIP report template is available to capture the code enforcement hearing agenda report. A sample report is also available in the Report List. Customers can enter the details for the Hearing Body, Hearing Status (either Completed or Scheduled) and the date to generate a report, which can be downloaded and edited.

Report List Page

Agency users can readily see reports regarding the Hearing Agendas for Code Enforcement hearings.

Steps to Enable

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

Tips And Considerations

This report is delivered as part of the BI catalog and can be executed directly from there. It is also available under the Report List for agency staff to access. You can either navigate to the BI catalog or provide a link to the report from an existing dashboard.

Key Resources

• See Implementing Your Agency, "Setting Up Analytics", Public Sector Compliance and Regulation Analytics on the Oracle Help Center.

System Administration

Managing the Intake Form Metadata Cache for Improved Performance

To improve performance of the initial loading of intake forms (custom objects), you can now schedule two Enterprise Scheduler Service (ESS) jobs to run on a regular basis. These jobs ensure that the latest metadata is available for your intake forms, without having to download and render any new updates not already in the cache.

To improve performance and to ensure the latest metadata is available after patching or new updates, you need to schedule these jobs to run.

Steps to Enable

To run the ESS jobs:

1. Select Setup and Maintenance from the Navigator or Page Finder.
2. On the Functional Setup Manager page, select Navigator > Tools > Scheduled Processes.
3. Click Schedule New Process.
4. In the Name field, type describe and press Enter.
5. The following jobs appear. Select these jobs to run (individually):
   1. Invalidate Intake Form Metadata Cache Job
   2. Build Intake Form Metadata Cache Job
6. On the Process Details page, click Advanced and select Using a Schedule on the Schedule tab.

NOTE: Run the Invalidate Intake Form Metadata Cache Job before the Build Intake Form Metadata Cache Job. It is recommended to run these jobs weekly, such as every Sunday night.

7. Click Submit.

Tips And Considerations

Important! If you do not set up these jobs to run, you may encounter problems in your production environment particularly after applying patches and updates to new releases.

You cannot run these jobs simultaneously. You must first run the Invalidate Intake Form Metadata Cache Job followed by the Build Intake Form Metadata Cache Job. Oracle recommends you run the Invalidate Intake Form Metadata Cache Job around midnight on Sundays. Build Intake Form Metadata Cache Job should run approximately 60 minutes after. For approximately 200 custom objects, this should take under 30 minutes. These jobs do not impact nor are impacted by any other jobs in the system.

Key Resources

• See Implementing Permitting and Licensing, “Creating Intake Forms,” Managing Intake Form Performance

Oracle Integration Cloud (OIC) Generation 2 to Generation 3 Separates Integrations and Processes Components

Currently, with Oracle Integration Cloud (OIC) Generation 2, OIC handles the following elements of the Permitting and Licensing solution:

• Integrations, which enables you to setup integrations to share data between systems.
• Processes, which enables you to configure workflow for transactions and decision modeling for fees.

Beginning with OIC Generation 3, OIC is split into two separate products:

• Oracle Cloud Infrastructure (OCI) Process Automation, which handles all workflow and decision modeling configuration.
• OIC Generation 3, which handles all integration configuration.

Going forward, OCI Process Automation will be provisioned with a limited license allowing it to be used only for workflow processing and fee processing, but OIC Generation 3 will not. When you begin using OCI Process Automation depends on when you’ve become a Permitting and Licensing customer.

For 24B:

• New customers beginning with 24B will be provisioned and configured with OPA Generation 3. OIC Generation 2 or OIC Generation 3 will not be provisioned.

• 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. Existing customers, who have adopted Permitting and Licensing prior to 24B, and currently running on OIC Generation 2 will migrate design-time definitions to OPA at a future release. Runtime migration for workflow and decision models isn’t supported. More details will be available as the finalized OPA Generation 3 adoption dates for existing customers are settled.

NOTE: All customers requiring OIC Generation 3 for integration configuration will need to license that product separately.

The 24B documentation will be updated to reflect the user interface and navigation of OPA. See:

• Implementing Your Cloud Integrations, Setting Up Workflow
• Implementing Your Cloud Integrations, Setting Up Workflow for Code Enforcement
• Implementing Your Cloud Integrations, Configuring Fee Decision Models

Existing customers can refer to previous documentation in 24A for OIC Generation 2 integration, workflow, and fee modeling information.

The following My Oracle Support page is in place to provide additional information about Oracle Permitting and Licensing’s migration to OIC Generation 3 and OPA: Document ID 3005969.1.

Oracle Process Automation (OPA) will be provisioned with your standard license if you are provisioning Oracle Permitting and Licensing in 24B or beyond. Existing customers will continue to use OIC Generation 2 until a future release.

Steps to Enable

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

Key Resources

• See Implementing Your Cloud Integrations, Setting Up Workflow
• See Implementing Your Cloud Integrations, Setting Up Workflow for Code Enforcement
• See Implementing Your Cloud Integrations, Configuring Fee Decision Models

NOTE" This documentation will be updated with the releases of 24B and will target new customers provisioning their environments with 24B.

• Existing customers, should refer to the 24A online help topics as well as the Knowledge Document on My Oracle Support:
  • See Implementing Your Cloud Integrations, Setting Up Workflow (24A)
  • See Implementing Your Cloud Integrations, Setting Up Workflow for Code Enforcement (24A)
  • See Implementing Your Cloud Integrations, Configuring Fee Decision Models (24)
  • See My Oracle Support Document ID: 3005969.1

Legacy Data Migration for Bulk Delete

Agency administrators can import, review results, and now delete migrated data for Planning Hearings, NAICS, Business Tax Details, and Inactivate Requests. Administrators can run the Delete Migrated Data process iteratively as part of their legacy data migration effort until they are satisfied with the quality of the migrated data.

This allows agency administrators to delete and update migrated permits and related objects to support data migration iterations. You can delete imported transactions for each test run prior to converting to a production environment.

This extends existing functionality to enable you to delete code cases, incidents and business licenses in a test environment preparation to import legacy data.

Steps to Enable

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

Tips And Considerations

An ESS job is delivered for you to run the delete process. The process of importing, reviewing results, deleting migrated data and rerunning the import will be an iterative process executed a number of times by implementers until they are satisfied with the quality of the migrated data.

Key Resources

• See Implementing Permitting and Licensing, "Migrating Legacy Data" on the Oracle Help Center.

Legacy Data Migration for Planning Conditions of Approval

You can migrate your legacy data for planning applications, permits, code enforcement, and business licenses to Permitting and Licensing using Import Management. Import Management improves definition, error handling, and performance for importing flat files (.CSV). For example, Import Management has drag and drop mapping capabilities and validates the first ten records in your data file before you import to ensure the data meets the import constraints of the various attributes. It also provides error files and diagnostic logs for analyzing unsuccessful imports.

These are the objects delivered in this release:

• Conditions Of Approval Transaction 
• Condition Of Approval Comment 
• Condition Attachment
• Coa Condition Comply Period

This extends the legacy data migration tool to support planning conditions of approval objects.

Steps to Enable

You will need to complete the setup and configuration outlined in the technical brief "Migrating Data Using Import Management" Doc ID: 2808116.1 on My Oracle Support.

Key Resources

• See Implementing Permitting and Licensing, “Migrating Legacy Data,” Migrating Data Using Import Management on the Oracle Help Center.

• See Migrating Data to Permitting and Licensing Using Import Management (Doc ID: 2808116.1) on My Oracle Support.

Redwood Experience

Redwood Experience for Setup Pages

To enrich your user experience, various setup pages have been developed using the Visual Builder Studio (VBS) and the Redwood toolset.

These pages are only accessible through the Functional Setup Manager and will no longer be accessible via the menu navigation or the page finder.  The table below lists the pages that have been updated as well as their new navigation.

You will need to navigate to Setup and Maintenance and then select your Offering, Functional Area, and Task List as outlined below.

The new pages are built using the Redwood toolset and Visual Builder Studio and offer a more dynamic user experience across the application.

Steps to Enable

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

Key Resources

• See Implementing Your Agency on the Oracle Help Center.
• See Implementing Permitting and Licensing on the Oracle Help Center.
• See Implementing Your Financial Framework on the Oracle Help Center.

Redwood Experience for Branding Capabilities

For public facing pages in Oracle Permitting and Licensing that are built with the new Redwood Experience, you have a limited set of capabilities for branding and themes.

The following table shows the attributes supported for the themes you apply to the currently available Redwood applications.

Branding themes and capabilities are available for new Redwood Experience pages.

Steps to Enable

To add branding themes to Redwood content, you use the same user interface as you did for the previous releases. You can apply the listed subset of theme attributes supported for Redwood content to the listed set of Redwood applications.

See Configuring the User Experience, "Branding", Branding Your Offering on the Oracle Help Center.

Tips And Considerations

As of 24B only select attributes are supported for the themes you can apply to the current Redwood applications. See Configuring the User Experience, "Branding", Branding Your Offering.

The listed attributes are not new, but are a subset of the theme attributes that are supported for the listed Redwood application. This subset of themes are the only ones that can be applied to the applications listed. Others will be available in future releases.

Key Resources

• See Configuring the User Experience, "Branding", Branding Your Offering on the Oracle Help Center.

Permits and Inspections

Redwood Experience for Oracle Inspector

Enrich the user experience of building inspectors and inspector supervisors with the Oracle Inspector mobile application developed using the Redwood toolset. The mobile app is built from the ground up using Visual Builder Studio (VBS) to give you a unique experience of Oracle applications.

These examples illustrate some of the pages in the mobile app featuring the enhanced UI, with all of the self-service features available on the original Oracle Inspector for performing permit and business license inspections.

NOTE: The Oracle Inspector web application doesn't currently support submitting inspection results for multiple inspections at once or working offline. You can only add inspections or update scheduled inspections on the desktop version of the application at this time. For information about using the previous offering of the Oracle Inspector mobile application, see the Oracle Help Center documentation for release 24A.

Inspection Tasks Page for Permit and Business License Inspections

Inspection Detail Page Including Checklists, Comments, Attachments, and Signature Panels

Checklists Page

Inspection Result Page

Conditions Page

The mobile app is built from the ground up using Visual Builder Studio (VBS) to give you a unique experience of Oracle applications.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Permits  No Longer Optional From: Update 25D

To use Redwood Experience for Oracle Inspector you will need to enable it in the Functional Setup Manager.

To enable:

1. Navigate to Setup and Maintenance.
2. Select Setup: Public Sector Permits.
3. Click on the Change Feature Opt In link.
4. Select the pencil icon for Permit Inspections.

Permit Inspections Opt In

5. Select the Enable check box for Next Generation Flow for Permit Inspections.

Next Generation Flow for Permit Inspections

NOTE: You can have both the Classic Flow for Permit Inspections and Next Generation Flow for Permit Inspections enabled. However, the navigation for both will be labeled as Mobile Inspections. You can change the menu label if you choose. See Configuring User Experience, "Configuring Navigation", Configuring Menu Structure on the Oracle Help Center.

Tips And Considerations

NOTE: The Oracle Inspector web application doesn't currently support submitting inspection results for multiple inspections at once or working offline. You can only add inspections or update scheduled inspections on the desktop version of the application at this time. For information about using the previous offering of the Oracle Inspector mobile application, see the Oracle Help Center documentation for release 24A.

Key Resources

• See Using Business Licenses and Using Community Development Permits, "Using Oracle Inspector" on the Oracle Help Center.

Code Enforcement

Code Enforcement Fee Calculations Based on User-Defined Field Values

You can now include user-defined fields in fee calculations for code enforcement.

The decision models that process the fee calculations in the Oracle Integration Cloud will include the custom values entered by the agency.

This example shows an agency-defined field that can be used in code enforcement fee calculations:

Design Code Enforcement Application Page

Fee calculations are available using user-defined fields.

Steps to Enable

You will follow the standard process to configure a DMN model and add it to the Fee Schedule. To use the user-defined fields you'll complete the following:

1. Configure a DMN model to include any required user-defined fields as inputs. See "Creating Decision Models for Fees" on the Oracle Help Center.

2. Add the DMN model to a Fee Scheduling using the Form Design fee mapping source. See "Mapping Form Fields to Decision Model Attributes" on the Oracle Help Center.

3. From the intake form designer, complete the fee mapping to map the DMN input to a user-defined field on the form. See "Mapping Form Fields to Decision Model Attributes" on the Oracle Help Center.

Tips And Considerations

A DMN service can use both custom field inputs and non-custom field (such as existing late fee) inputs can be set up in the Fee Schedule using the Form Design fee mapping source.

Key Resources

• See Implementing Your Financials Framework, "Setting Up Fees", Mapping Form Fields to Decision Model Attributes on the Oracle Help Center.

• See Implementing Your Financials Framework, "Setting Up Fees", Setting Up Fee Schedules, "Adding Fee Items with Other Mapping Sources" on the Oracle Help Center.

Redwood Experience for Code Enforcement

Redwood Experience for Code Enforcement Public Users

Enhance your user experience with the Code Enforcement Public User Flow developed using the Redwood tool set and Visual Builder Studio (VBS).

We have enhanced the usability of the Code Enforcement flows for reporting and tracking issues for your public users.

Select an Issue Type Page

In the next pages, the public users can provide the location of the issue. They can either enter the address in the Search field or locate it on the map.

Provide the Location of the Issue Page

The public users can enter the details of the issue and add any photos or documents as attachments.

Tell Us What is Going On Page

Once all the details are entered and submitted, a message appears to confirm the creation of an incident, as well as provides an Issue Number for future reference.

The public users can use this Issue Number to search for and track the reported incident’s progress from the Issues page.

Issues Page

All updates made for the reported incident will be displayed in the details page.

Incident Details Page

The Redwood Experience for Permitting and Licensing gives users a clean and easy flow to report, track, and pay for citations and issues.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Code Enforcement  No Longer Optional From: Update 25A

To enable these pages, you will need to turn them on in the Functional Setup Manager.

1. Navigate to Setup and Maintenance.

2. Select the Code Enforcement offering.

3. Select Change Features Opt In.

4. Select the pencil icon under the Features column for Public Sector Code Enforcement.

5. Select the pencil icon for Next Generation Flow for Public Users.

Next Generation Flow for Public Users

6. Select the four pages listed and Click Save and Close.

7. If you prefer to use the Classic Flow for Public Users, you must first turn off the Next Generation Flow for Public Users by following steps above but clearing the checks for each page and saving.

8. Once you have disabled the Next Generation Flow, select the pencil icon under the Enable column for Classic Flow for Public Users.

9. Click Save and Close.

Classic Flow for Public Users

Tips And Considerations

The Resolve an Issue and CE Payments pages were delivered as part of Oracle Permitting and Licensing 24A. With the addition of Report an Issue and Track My Issue, you can now enable the entire Code Enforcement Public User flow with the same Redwood look and feel. This gives the public user continuity when reporting, tracking, resolving and paying for incidents and cases in Code Enforcement. These pages will default in Functional Setup Manager to "ON" in the 24C update. See Important Actions and Considerations at the end of this document for  more details regarding the Redwood Experience for Permitting and Licensing.

Key Resources

• See Using Community Development Code Enforcement, "Code Enforcement Activities for Public Users", Reporting Issues on the Oracle Help Center.

• See Using Community Development Code Enforcement, "Code Enforcement Activities for Public Users", Tracking Issues on the Oracle Help Center.

Business Licenses

Pending Inspection Creation Due to Business Location Change

When automatic creation of pending inspections is set up for business licenses, and a business location changes from outside the agency's jurisdiction to within its jurisdiction, the system automatically creates the pending inspections. The system automatically creates inspections in a Pending status for all the in-process business license transactions that are associated with the selected location.

This example illustrates the switch that agency staff turns on to indicate that the physical business location is within the agency's jurisdiction. The switch is on the Location Details page in the business record details.

Location Details Page in the Business Details

Helps to control when inspections are created based on agency jurisdiction.

Steps to Enable

The system must be set up to automatically create pending inspections in the agency-level options for business licenses and the inspection group must be identified on the business license type.

1. Navigate to Common Setup > Agency.
2. Select your agency.
3. Select the Options link for Business Licenses.
4. In the Inspections section, turn on the "Enable Automatic Creation of Pending Inspections" switch.

On the Physical Location section on the Location Details page in Business Details page, turn on the switch, Is this business physically located within the agency's jurisdiction? and select a parcel within the agency's jurisdiction for the pending inspections to be automatically created.

Tips And Considerations

Cancellation of pending inspections when a business location is moved outside of an agency's jurisdiction was released in 23C. The agency must set up the system to automatically create pending inspections for business license types.

Key Resources

• See Implementing Permitting and Licensing, "Setting Up Business Licenses," Setting Up Agency-Level Options for Business Licenses on the Oracle Help Center.

• See Using Business Licenses, "Managing the Business License," Working with Business Location Information on the Oracle Help Center.

• See Using Business Licenses, "Working with Business License Inspections," Managing Inspections for a Business License Application on the Oracle Help Center.

Business Summary Page Contextual Help

Registered public users can amend business, location, and owner information using a business license associated with the business and location.

Business Overview Page

The contextual help information is displayed only to registered public users on the Business Entity Overview page.

The information is displayed when the business entity status is either active or inactive, but not provisional.

Tip for Registered Public Users that if they would like to update business information they should do so using an amendment on an associated business license.

Steps to Enable

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

Tips And Considerations

If the delivered contextual help does not meet the requirements set up by your agency, you can suppress the contextual help by creating your own agency-defined contextual help for this page. The agency-defined contextual help will override the system generated help delivered with this feature.

Key Resources

• See Using Business Licenses, "Managing the Business License" Managing Business Information on the Oracle Help Center

Interface to Export or Import Business License Types

The Oracle Permitting and Licensing system now offers the pre-configured Business Licenses License Types to export, import, and then apply to your agency’s test environment.

The following image illustrates the Business License Types being submitted for export:

Export Solution Package Page

Facilitate the reuse of license type configurations between testing and production environments.

Steps to Enable

Complete the steps outlined in Oracle Permitting and Licensing Solution Packages Technical Reference Paper found on the Oracle Permitting and Licensing Solution Library.

Key Resources

• See Implementing Permitting and Licensing, "Setting Up Permits," Importing Solution Packages on the Oracle Help Center.

• See Oracle Permitting and Licensing Solution Packages Technical Reference Paper on the Oracle Permitting and Licensing Solution Library.

Confidential Attachments for Business Licenses

Agencies can now provide business license applicants with the option to limit access to sensitive documents, such as tax information, by indicating they are confidential. When an applicant uploads a confidential document during application intake, only agency staff with permissions, the applicants, and contacts with application access can view confidential attachments on the application. Only agency staff with access to confidential documents can upload confidential attachments or update the confidential designation, but confidential attachments are hidden from view by other agency staff and public users.

This example illustrates the Confidential switch used to indicate whether an attachment is confidential on an intake form.

Add Attachments Modal Page with Confidential Switch

This example illustrates the list of attachments for a business license transaction as viewed by agency staff with permissions to work with confidential documents.

Business License Transaction - Attachments Page

Applicants and agency staff with permissions can add confidential attachments on business license intake forms, and agency staff with permissions can add and manage confidential attachments on business license transactions and the business record.

Allows agency to maintain privacy for sensitive documents from staff that do not require access.

Steps to Enable

To enable confidential attachments for Business Licenses:

1. Navigate to Common Setup > Agency.
2. Select the agency row.
3. Click on the Features tab.
4. Click on the Business License Options link.
5. Under General Settings, enable the "Enable Confidential Attachments" switch.

Tips And Considerations

• Public users can only attach documents from the intake form; however, agency staff with access can attach and modify confidential flag post-submit.

• Public users with full and view/pay/ print will have access to confidential attachments.

• This is only available for Business Licenses.

• Once confidential attachments functionality is enabled, any attachment can be marked as confidential.

Key Resources

• See Implementing Permitting and Licensing, "Setting Up Business Licenses," Setting Up Agency-Level Options for Business Licenses on the Oracle Help Center.

• See Using Business Licenses, "Applying for a Business License," Completing an Application on the Oracle Help Center.

• See Using Business Licenses, "Managing Business License Applications," Completing an Application, Navigating to Business License Activity Details, and Working with Attachments on the Oracle Help Center.

• See Using Business Licenses, "Managing the Business License," Managing Business Information on the Oracle Help Center.

Access Requirements

The following roles agency staff roles have access to attach and modify the confidential flag after it is submitted:

• Auditor
• Business License Administrator
• Business License Analyst
• Business License Manager
• Business License Specialist
• Treasury Supervisor
• Treasury Administrator
• System Administrator

Audit History for Businesses

A new Audit History tab has been added to the Business Details page. Use the search bar to filter the data provided and click column headers to sort. At the bottom, there are tabs for Business, Owners, and Location data, as shown below:

Audit History Tab

Provides the ability to see the audit history for a business.

Steps to Enable

You need to make sure that the data you want audited is set up to see data on the Audit History tab.

To enable auditing:

1. Navigate to Setup and Maintenance > Application Extensions > Manage Audit Policies.
2. Click Configure Business Object Attributes.
3. In the Products drop down list, select Public Sector Common Components.
4. Select the check box in the Audit column for the desired business objects.
5. Click Save and Close.

Key Resources

• See Implementing Permitting and Licensing, "Managing Audit Policies," Implementation Concepts for Audit Policies on the Oracle Help Center.

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

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.