Oracle details AI photo intake for code complaints in its permitting update
An October 19 overview describes image-based incident reporting and inspection summaries in 26D. Users can revise generated descriptions, while application checks require agency configuration.
Oracle’s Permitting and Licensing 26D update adds AI-assisted support across code enforcement, application review, inspections, and planning reports. The tools can draft incident details from photos, flag application issues, summarize inspection history, and assemble reports, but they leave decisions and finalization to staff. Oracle detailed the photo assistant on October 19; it is available to agency staff and registered public users only where enabled, and its results depend on image quality and agency-configured fields. Agencies must also configure the application-review agent before using it.
01
The image assistant maps suggested violations to agency-configured issue types and fills only fields for which the image provides required information.
02
Application Acceptance is a template, not a ready-to-run agent: agencies must configure rules and select application types before triggering checks.
03
After resubmission, Application Acceptance checks again and retains earlier results; staff decide whether to request corrections or continue processing.
Oracledetailed an AI assistant on October 19 that turns uploaded photos into draft code-enforcement incident information in its Permitting and Licensing 26D update. Available to agency staff and registered public users when enabled, it suggests potential violations and fills configured fields. Users can revise the generated description before submitting a report.
A photo starts the incident report
The Code Enforcement Incident Image Intake Assistant works inside the Report Issue workflow. It describes the scene and maps potential violations to the agency’s configured issue types. Matching fields are populated when the image contains the required information.
Users can complete the report manually at any stage. Oracle cautions that the quality and completeness of the populated information depend on the image analysis and the application’s configured issue types and fields.
Checking submissions and drafting planning reports
The update also includes an Application Acceptance agent, described in Oracle’s October 5 release documentation. It looks for missing, incomplete or inconsistent information across configured application fields, descriptions, attachments and agency-defined validation instructions, then prepares verification notes.
Editorial illustration for Oracle details AI photo intake for code complaints in its permitting update.
This is not a ready-to-run agent. Agencies must copy and configure its template and set rules that trigger it for selected application types. In the standard configuration, staff decide whether to request corrections or continue processing. Resubmission triggers another check, with earlier results retained in verification history.
For planning and zoning reports, staff run a configured generator using an application record ID. It assembles a structured draft from available details such as parcels, fees, hearings and conditions. Staff can edit it and add the planner’s analysis, rationale and recommendation before saving or publishing.
Inspection history at hand
For officers preparing for or completing an inspection, the Inspection Summary Assistant offers a read-only overview from the Inspection Tasks page. It brings together prior inspections, outcomes, violations, corrective actions, notices and comments. Authorized staff can manually refresh it to include their latest updates.
Sources
docs.oracle.comOracle Fusion Cloud Permitting and Licensing 26D What
Reader comments
Newest comments first. Replies stay oldest first.