Update 22C

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.

Permitting and Licensing

Permitting and Licensing Common

Load Contractor Contacts From File

You can import contractor contacts in a batch upload, including contractor contact information and authorization agent contact information. This allows agencies to load contact's business information and other pertinent attributes into contractor management. 

Contractor License Validation in Applications

This feature provides agency staff the ability and flexibility to define contractor validation requirements at the permit type level. These validation requirements include license type, classification, expiration, and insurance attributes. Agency staff can optionally prevent application submittal when validation fails on the intake form.

Parcel and Address Conditions in Import Tool

This feature extends the existing import tool to support parcel and address conditions through a separate import file. Once imported, the conditions will update the conditions tables with links to the reference parcel and address detail pages.

Support Sketch Widget

The sketch widget provides agency staff and public users the ability to draw a sketch on various map pages. When a sketch is drawn and saved on an application intake page, the sketch is stored and saved as part of the application.

Support Print Widget

The print widget provides agency staff and public users with the ability to generate a printer-ready version of the map. Users can specify the print output file formats that can be selected based on the options available from the print service.

Primary Contact Selection

The applicant information is copied to the contact grid and set as the primary contact. The applicant or agency can select another contact as the primary. Only one primary is supported. If an applicant is not the primary, a flag is displayed on the contact grid row to represent the applicant and the applicant continues to have access to the application. 

Attach Documents to an Ad Hoc Message

Agencies can attach a document from their local device to an ad hoc message.

Final Document Check Box for Attachments

Agency staff can manually identify a permit attachment as a final document. For example, plan coordinators can mark an attachment as the final plan document when there are multiple attachments.

Display or Hide Inspection Functionality

Agencies will use Functional Setup Manager to either enable or disable inspection functionality. When an agency opts out of using inspections, the navigation to inspection setup and transaction pages are hidden from both agency staff and public users. 

Grid Personalization Additional Pages

This transitions from stacked grids to flat grids to support agency and user personalization for additional pages including Code Enforcement Incident and Cases, Code Officer, Code Technician, and Planner Worklists. 

Intake Form Grids

The intake form grids allow you to capture and display intake form data with a tabular page control. When creating intake forms for Permits or Planning and Zoning, you can now add grids to your pages. Drag the grid element onto your form design just as you would a group box or a field, and drag fields into the grid element to create grid columns.

Display Options for Intake Form Grids

When adding grids to an intake form design, you can set runtime display options. This includes the initial sorting column, whether to wrap data entered into columns, and others.

Intake Form Versioning and Effective Dating

You can now use the Intake Form Designer to manage multiple versions of intake forms and apply effective dating. This enables you to make changes to form designs to address current and future business needs while maintaining the integrity of historical and in-process transactions.

Intake Form Designer Groovy Icon

When adding Groovy to your intake forms, the Intake Form Designer now displays an icon to indicate which elements have Groovy business logic. If the Groovy is written at the object level, the icon appears next to the Add Logic button for the intake form. If the Groovy is written at the field level, the icon appears next to the individual fields. The Groovy icon lets you find your business logic quickly to assist development and troubleshooting efforts.

Default Group Box Display

When you design your intake forms, you can set the default display of group boxes to be either expanded or collapsed to improve user experience. Having group boxes collapsed, streamlines the initial display of the intake form.

Legacy Permit and Planning Transaction Deletion and Updates

Agency administrators can delete and update migrated permits and related objects for supporting data migration iterations. This allows a hard delete of imported transactions for each test run prior to converting to a production environment.

Financial Framework

Deposit Account Creation, Ownership, Payments, and Deposits

You can establish deposit accounts (also known as trust or escrow accounts) based on the potential for exceptional or unusual costs being incurred by the city. You can also assign transactions and projects to these deposit accounts. 

Fee Calculation Based on Reusable Custom Field Value

The calculation of fees uses the values entered in reusable custom fields.

Permit Contacts to Make Fee Payments

Permit contacts can pay fees using the Make a Payment page. 

System Administration

New Relay to OIC Action for Business Rules Framework

This feature extends our integration abilities by leveraging existing Business Rules Framework events to trigger outbound integrations through an ICS orchestration. 

Expand Usage of Existing Business Rules Framework Actions to All Applicable Resources

When setting up business rules in the Business Rules Framework, you will find that for most of the resources the amount of actions available to trigger by your business rules has increased.

Business Rules Framework Expands Scope of Apply Condition Action

You can now use the Business Rules Framework Apply Condition action to apply conditions to more objects. For example, you can create a business rule to apply a condition to an address, a parcel, a contractor license, a person, or an account.

Agency Default Settings for Grid Personalization

Agency administrators can set up default display personalization options for users. The setup provides consistent displays across all pages for agency users, flexibility to users for further personalizing page displays, and the ability to reset default options for administrators.

Permits and Inspections

Require Comments for Workflow, Plan Reviews, and Inspections

An agency can make comments optional, required in all cases, or required for negative statuses, including canceled inspections. Comments are collected when plan review decisions are made, plan review cycles are canceled, inspections are canceled, and inspection results are provided. This provides configurability to require a comment when certain predefined statuses occur in workflow, plan review, and inspections.

Final Inspection and Required Inspection Logic

Inspections can be marked as required at the inspection type level with the option to override the requirement when creating an inspection for a transaction. Final inspections are always required and can't be scheduled if there are any incomplete required inspections. This applies to mobile inspections as well.

Plan Review

Plan Reviewer Workload Visualization

A visual representation of a reviewer's workload data when adding a reviewer, including assigned reviewer information, in the context of the number of reviews that are due each day is now available. In addition, the Plan Review Console is expanded to include a reviewer workload page, including a list of reviewers with the total count of reviews assigned and the applications they are assigned to.

Plan Review Workload Display for Assignment and Reassignment

A count of plan reviews assigned to each reviewer across permits and planning applications on the Plan Review Console and on permits in the Plan Review Decision Details is now displayed. Viewing the workload helps to facilitate plan review assignment and reassignment.

All Permit Statuses View in Plan Review Console

Plan Review Console displays the reviews for all permit statuses. This allows agency staff quick access to plan reviews when the cycle is closed or when the application is in a status other than plan review, including terminal status.

Code Enforcement

Responsible Party Attachment Upload

A responsible party can now upload an attachment, such as photos showing evidence of compliance, in the responsible party page.

Autoassignment of Officer on Case Based on Job Attributes

Agencies can now enable the autoassignment of an officer to a newly created case in a particular district and district type. The autoassignment of officers works based on their job attribute values of District and District Type.

Automatically Apply Code Case Condition

The ability to automatically generate a condition on a parcel or address when a code case is linked to a referenced parcel or address is now available. Use the Business Rules Framework to set the criteria for triggering the conditions. This feature also provides the ability to resolve a condition automatically when a case is closed.

Notice Template Updates

This feature allows agency users to replace an existing system-generated notice with a different template without adding to the total count of notices issued.

Property Link to Code Cases

Easily navigate to a reference parcel or address when linking to a code case.

All Tasks Tab from the Worklist

An All Tasks tab has been added to Code Enforcement worklists so that staff can view and complete each others tasks as needed. This feature supports the scenario when a staff member is out of office temporarily and requires an easy way for backup staff to continue to process cases in their absence.

Workflow Task Reassignments

When a technician is reassigned to an incident and/or case, the assigned workflow tasks are also automatically reassigned to the newly assigned user.

Search, Sort, Filter, and Export for Code Enforcement Pages

This feature applies a consistent way to search, sort, and filter Inspection Lists for a Property for Code Enforcement pages including worklists, case, and incident pages.

Business Licensing

Business Licenses Subject Area

OTBI Business License subject area provides agencies with analytical information about their licensed businesses and real-time dashboards.

Business Licenses Communication Events

Communication events are available to support the notice of application submittal, acceptance, completion, issuance and configured workflow for Business Licenses.