This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Product | Feature | Notes |
|---|---|---|---|
| 03 SEP 2021 | Created initial document. |
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.
Licensing and Permitting Common
Manage Contractors and Contacts in Applications After Submittal
In order to provide a record of past contacts or contractors, this feature introduces the ability for an applicant or contact to inactivate or re-activate a contact on an application or transaction after submittal
Agencies can leverage the conditions framework to manually apply conditions such as notice, hold, or lock to contractor licenses in the agency-maintained contractor list. The conditions help agencies manage licenses by restricting the use of contractors that applicants can select on intake forms.
Add Contractors as Application Contacts
When an applicant adds a contractor license to a permit or planning application in the intake form or after the application was submitted, the contractor's contact is added to the list of contacts for the application.
Extend Access to My Permits List to Contacts and Contractors
Contact users with application access, who were added to an application by the applicant or by the agency staff, can view the application detail and pay the fees. Contacts also see the applications they applied for themselves. Contractors access to My Permits List requires them to be listed as a contact on the permit.
Provide Ready-to-Use Fields for the Intake Form Designer
You can now use predefined fields on your intake forms. Predefined fields are delivered by Oracle and come preconfigured with any required formatting or validation, and they are set up to be incorporated into your fee calculations.
Allows a user to quickly access recently visited pages with the click of a button.
Consolidate Fee Notices to Applicants
Agencies can set up communication templates to list the day's new or updated fees. Additionally, agencies can automatically send one communication to applicants per day.
Agency staff can waive fees for the full or a partial amount at the fee item level in the application details.
Fee Line Item Display Permit Address
When a user selects the "Information" icon on the Payment Checkout page, the permit address is displayed in the Pricing Details window.
The public user payment process features improvements to the Payment Cart, Public User Landing Page, Transaction List, and Fees and Payments page in the Application Details.
Payer Information for Payments
The fees and payments information for applicants and agency staff reflects payer information captured from cashier session payments.
Payment Receipts in Oracle Accounts Receivables
Agencies can create payment receipts in Oracle Accounts Receivable.
The new Sync Card Payment Status ESS job enables agency staff to reconcile orphaned payments at scheduled intervals.
You can give permit access to specific types of permit contacts such as contractors and homeowners. As long as these contacts are registered users, they can pay fees for the permit from the fees and payment tab.
Scheduled Rules for Business Rule Framework
The Business Rules Framework now enables you to create scheduled rules that run through the Oracle Enterprise Scheduler Service (ESS).
Expand the Worklist to Display Indicators Representing Fees and Conditions
Icons now appear in the left hand column of worklists and transaction pages to indicate if fees are due for a transaction or if there have been any conditions applied to a transaction.
Send Communications to Contacts on Applications by Type
Agencies can create communication templates using variables for the attributes of application contacts, including phone, email, user ID, and user name.
This report shows the impact of the parcel reconciliation to permit transactions.
IVR Without PIN with Agency Configuration
Enable an agency to configure permission for public users to request inspections using IVR without entering a PIN number.
The Inspection Request page now displays when an inspection was created and the source of that creation, such as IVR or online.
Enables agency staff and public users to request multiple inspections for a permit at the same time.
The schedule cutoff time no longer applies to agency staff.
Mobile Inspector Management of Incomplete Permit Inspections
The permit inspection task list in the Oracle Inspector mobile application displays inspections scheduled for a prior day but not yet completed.
This feature expands the Inspection Console to provide the ability to assign inspections and view additional information about inspection all in one place.
Plan Review Cascading Due Dates
Administrators can now enable cascading due dates for plan reviews, permits, and planning applications at the agency level.
Notification of Upcoming Plan Review and Plan Review Cycle Due Dates
Notify plan reviewers, plan check coordinators, and other interested stakeholders of plan review due dates.
You can change the default plan review cycle name so that by default no name is shown instead of the current default behavior. You can also edit plan review cycle names that have already been set.
Support Re-Order of Conditions of Approval
During the entitlement application review process, the assigned planner will route the application and supporting documents to various departments for review. The plan reviewers will provide comments and conditions of approval. The project planner is responsible for consolidating and organizing the conditions entered by the plan reviewers. These conditions are typically attached to the staff report as an exhibit. Planner needs the flexibility to easily manage the conditions of approval. These conditions need to be placed in the right order and clearly describe to the applicant, decision-makers, agency staff and the public the actions that are required to occur and how these actions will be accomplished.
Hearing Body setup is now renamed as Hearing and Decision Making Body setup. Hearing Hierarchy setup is now part of the Hearing and Decision Making Body setup page. Agency administrators can identify whether a decision making body can be the first body. If the decision making body is identified as the first body, the Appeal Body section will appear. Agency administrators will be able to setup the Appeal Body, previously known as Hearing Hierarchy.
Additional Tabs for Code Officer Worklist
Code Technician tabs were added to the Code Officer Worklist including Notice of Violation, Notice of Citation, Hearings, and Assigned Incidents.
Ready for Inspection Prior to Comply by Date Expiration
Responsible parties and agency staff can request an inspection for their case using the Ready for Inspection action on the Responsible Party page. The case will be displayed as ready for inspection in the Municipal Code Officer mobile application as well as in the Code Officer worklist page on the desktop computer.
Multiple Inspections on a Property
Manage multiple cases related to a property using a single primary case. Code officers can group multiple violations within the same property and maintain specific time rules, due dates, workflow, inspections, and code references for individual cases. The primary case serves as an umbrella case file to facilitate the overview of a property, with multiple concurrent code enforcement activity.
Automatic Assessment of Fees for Notice of Violations
Extends the auto-assessment of fees to Notice of Violations.
Code Violation Status Tracking
Code officers can use the Code Violation Status to view and update individual code violation records. Key functionality includes tracking individual history for each code violation, and providing a visual indicator when each or all of the violations have been resolved by the corrective actions.
Support for Multiple Responsible Parties
Support for multiple responsible parties gives you the ability to associate multiple responsible parties to a code case, ability to update in different pages including the notice of violation and citation work list tabs, setup pages to create responsible party types, and the ability to update the responsible party type.