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 |
|---|---|---|---|
| 06 OCT 2020 | Public Sector Common | Intake Form Save As Draft | Updated document. Revised Tips and Considerations. |
| 06 OCT 2020 | Public Sector Common | Intake Form Testing Within Sandbox | Updated document. Revised Tips and Considerations. |
| 06 OCT 2020 | Important Actions and Considerations | Updated document. Added Upgrade Actions section. | |
| 18 SEP 2020 | Created initial document. |
This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.
Security and New Features
The Role section of each feature identifies the security privilege and job role required to use the feature. If feature setup is required, then the Application Implementation Consultant job role is required to perform the setup, unless otherwise indicated. (If a feature doesn't include a Role section, then no security changes are required to use the feature.)
If you have created job roles, then you can use this information to add new privileges to those roles as needed.
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.
Optional Uptake of New Features (Opt In)
Oracle Applications Cloud delivers new updates every quarter, often containing new features for offerings. Some features are enabled by default and are readily available for use. Features that aren’t enabled by default require you to use the New Features work area to review and decide whether to opt in to them or not.
To do that, you need these 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:
- Click Navigator > My Enterprise > New Features.
- 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.
- On the New Features tab, review the new features and check the opt-in status of the feature in the Enabled column. For a feature already enabled, you would see a check mark. Otherwise, you would see an icon to enable the feature.
- 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 Offering Configuration.
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 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 Opt In Expirations across all Oracle Cloud Applications.
Column Definitions:
Features Delivered Enabled
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.
| Ready for Use by End Users Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features. |
Action is Needed BEFORE Use by End Users Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing. |
|||||
|---|---|---|---|---|---|---|
| Feature |
Report |
UI or |
UI or |
|
||
Intake Form Designer Enhancements for Field Attributes Panel |
||||||
Oracle Intelligent Advisor Enhancements for Registered Users |
||||||
ArcGIS Enterprise Portal Support
You can configure a map profile that references to an ArcGIS Enterprise Portal Webmap.
We have extended GIS integration to support ArcGIS Enterprise Portal Webmap.
Steps to Enable
You don't need to do anything to enable this feature.
Role Information
Agency staff can utilize this feature.
Parcel Search Through Elastic Search and Faceted Filters
This feature enables agency staff to dynamically filter parcels through the faceted filter panel. Filters can be used in combination to quickly hone into parcels based on their characteristics. Oracle Search Cloud Service provides the search engine capability to drive this functionality.
Faceted filters makes it easier and faster to search for properties. A new filter panel lets you find parcels based on key fields such as parcel status, improvement and land value.
Steps to Enable
You must enable Oracle Search Cloud Services in your Agency settings.
Role Information
Agency staff and public users can utilize this feature.
Intake Form Testing Within Sandbox
A new intake form status is provided to distinguish new or updated intake forms with the following status:
- Draft
- Intake forms ready to be tested
- Intake forms ready to move to production

Intake Form Status
Additionally, you can revert to a previous published version of an intake form.

Application Form Setup
Transaction types need to be published only when the intake form is ready for the production environment. Agency staff can now fully test intake forms while they are still in their sandbox (draft). A new intake form status is provided to identify forms that are finished with the testing phase and ready to be published and migrated to the production environment.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
The new ability to test your intake forms from end-to-end while they are still in the development sandbox requires you to update your workflow process definitions to include a Sandbox Connector. The Sandbox Connector enables intake forms in the sandbox to access and exchange data with process definitions in Oracle Integration Cloud. To access the intake form at runtime, a new role (PSC Custom Sandbox Access) needs to be applied to the user accessing the intake form.
For more information on configuring a Sandbox Connector and testing within a sandbox, see Setting Up The Sandbox Connector and Testing Intake Forms on the Oracle Help Center.
Key Resources
- See Implementing Compliance and Regulation, Creating Intake Forms, "Testing Intake Forms", on the Oracle Help Center for more information.
Role Information
Agency staff can utilize this feature.
Intake Form Designer Enhancements for Field Attributes Panel
The Field Attributes panel contains a new section named Details. The Details section displays information useful for reporting purposes, writing Groovy scripts, and managing lookup types. For example, the Details section shows the name of the business object containing the field, the name of the field at the database level, the data type, and the list ID if the field is associated with a list of values (lookup type).
During an implementation and when any intake layouts are updated, you may need to report on some of the fields in the form, add Groovy logic to some of the fields, and/or manage the list of values associated with drop-down list field data type. All of these activities require specific details about the field. By expanding the details section of the field attributes pane you will have visibility to the business object, field name, data type and the list ID, if the data type utilizes a list of values making it quicker and easier to complete the activities identified above.
Steps to Enable
You don't need to do anything to enable this feature.
Role Information
Agency staff can utilize this feature.
Applicants can save their applications as draft applications at any point in time. All their data will be retained so they can pick up where they left off and all validations are suspended until submit.
The ability to save as a draft allows applicants to retain all data that they have entered into an application in the event that they need to exit that application apply process prior to finalizing and/or submitting the application. When they save, all validations are bypassed so that if they have not filled in all required fields or they have violated any other validations, the system will save the data as-is and validate prior to submit.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Intake forms can now be saved by applicants without having to resolve all validation issues. This allows applicants to gather additional information and return to the intake form later. To take advantage of this feature, be aware of these upgrade impacts.
- Groovy. To compensate for the ability to bypass Groovy validation during a save, incorporate the "pending" status in your logic. An intake form is in "pending" status when it has been saved but not submitted. For example, add the following to the top of applicable Groovy scripts:
if (Status == "Pending") return true
- Upgrade. Intake forms from previous releases with fields set as required need to be updated to include the validation adjustments associated with the ability to ignore required fields during a save.
NOTE. If you do not incorporate these changes, Groovy validator scripts in 20D will run the same as they did in 20C.
To update existing intake forms:
- Open the intake form.
- Locate all the fields set as required, and turn off the Required switch.
- Save and publish the form.
- Locate all the fields that need to be set as required, and turn on the Required switch.
- Save and publish the form.
- For more information on intake form save behavior, see Considering User Experience.
Role Information
Agency staff and public users can utilize this feature.
Fee Calculations for Time Recording
Calculate and assess fees based on time recording of agency staff for plan reviews, meetings with planners, and inspections according to the billing rate and cost code assigned to the agency staff. Time-based fees can also result from time for external resources such as contract inspectors or plan reviewers. Calculated time-based fees that include a composite of multiple calculations, will show up as one row on the fees and payments tab and will not be shown as separate fee items.
You can directly associate the time that staff has spent reviewing plans or performing inspections with configured time-based fees to calculate and assess fees.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- See Implementing Your Agency, Setting Up Time Recording on the Oracle Help Center for more information.
Role Information
Agency staff can utilize this feature.
Fee and Payment Configuration Enhancements
Fee and payment displays and configuration have been enhanced. This includes removing the calculated zero dollar ($0) fee line items, displaying the fee schedule of currency codes, and mapping fees to the fee schedules.
Now it is even easier for your agency staff to configure fee items for each fee schedule and for public users and agency staff to view and understand assessed fees with an improved display.
Steps to Enable
You don't need to do anything to enable this feature.
Role Information
Agency staff configure fee schedules and public users can view and access the fee information.
Custom Global Tables Subject Area
The custom subject area allows for reporting and analytics to include Permits and Planning and Zoning custom or agency-configured fields.
You can now use values from custom (also known as agency-configured) fields as input for reports and analytics using Oracle Transactional Business Intelligence (OTBI) for tracking and managing operations.
Steps to Enable
Leverage new subject area(s) by adding to existing reports or using in new reports. For details about creating and editing reports, see the Creating and Administering Analytics and Reports book (available from the Oracle Help Center > your apps service area of interest > Books > Administration).
Key Resources
- See Implementing Your Agency, Setting Up Custom Subject Areas on the Oracle Help Center for more information.
Role Information
Agency staff can utilize this feature.
The conditions framework is extended to allow you to apply notice, hold, or lock conditions to an individual property address. You may apply one or more conditions to a property address.
Not all permitting activities happen at the parcel level. Agencies can apply notice, hold, or lock conditions to individual property addresses.
Steps to Enable
You don't need to do anything to enable this feature.
Role Information
Agency staff can utilize this feature.
Communications Attributes Use Across Resources
You can insert attributes from a related resource into your communication layout for new generic workflow communication events.
Communications offers more flexibility when creating templates by making attributes available across resources.
Steps to Enable
You don't need to do anything to enable this feature.
Role Information
Agency staff can utilize this feature.
Oracle Intelligent Advisor Enhancements for Registered Users
If an agency changes the Oracle Intelligent Advisor policy model, checkpoints in the model may be left orphaned which can cause checkpoint data corruption. The feature introduces a process for agency administrators to run to correct orphaned checkpoints when policy models change.
This feature introduces a process for the agency administrator to correct any data corrupted checkpoints when a policy model change is made.
Steps to Enable
You don't need to do anything to enable this feature.
Role Information
Agency staff can utilize this feature.
Public User Account Creation During Application Intake
During intake for agency assisted applications, agency staff may add a new public user as the applicant starting directly from the intake form. This feature allows the agency to register a public user starting from the intake so they don't have to use a separate browser to perform this task. Once the public user account has been created, the public user's information is automatically populated in the in-process application. Once the account has been created and the public user has completed the registration process, the public user can apply online and have their information automatically populated in future application intake forms.
Agency staff no longer needs to leave the intake form to register a new applicant. Instead, they can add a new user from the application intake.
Steps to Enable
You don't need to do anything to enable this feature.
Role Information
Agency users can utilize this feature.
Permit Certificate by Permit Type
This feature extends an agency's ability to associate a permit to multiple permit layouts. Using Business Intelligence Publisher (BIP) reports to format permit certificates, an agency now has the flexibility to continue to reuse the same layout for all permits or use a unique layout for each permit type. A new configuration option allows you to select the specific report per permit type.
This feature provides more flexibility when printing permits certificates. You can now use a certificate layout specific to a permit, in addition to reusing layouts across permit types.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Permit certificates are configured as Business Intelligence Publisher reports.
Role Information
Agency staff can utilize this feature.
Time Recording for Plan Review and Inspections
The name of agency staff and the time spent performing each plan review and inspection is automatically captured. The name and time can be edited by the agency administrator. This information is available for reporting and for fees based on time recording, introduced in the feature Fee Calculations for Time Recording. Each staff profile has a billing rate and cost or account center number that can be multiplied by time spent to determine the time-based fees.
Recorded time can be used by the agency for tracking and managing operations or to drive time-based fees.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- See Implementing Your Agency, Setting Up Time Recording in the Oracle Help Center for more information.
Role Information
Agency staff can utilize this feature.
Copy Contractor Information to New Permit
When using the copy feature for a permit application, this feature allows associated trade license information to be carried into the new permit application intake.
If a permit contains contractor trade license information and the permit is copied, the contractor trade license information is carried to the new permit application, so the application or agency staff does not have to re-enter the license information.
Steps to Enable
You don't need to do anything to enable this feature.
Role Information
Agency staff and public users can utilize this feature.
Automatic Data Download for Oracle Mobile Inspector
For agency field staff who want to perform inspections offline on the Oracle Inspector mobile application, this feature provides additional support by automatically downloading inspection-related data that might have occurred when syncing back to the server.
In the app settings, you can choose to work offline, which means that inspection-related data is initially downloaded to your device so that you can complete an inspection without internet connectivity. Once connected, this feature will automatically check on a periodic basis to detect any changes to your daily workload.
Let the Oracle Inspector check for any changes while you're in intermittently offline, such as reassigned or cancelled inspections. If detected, the app will update the data on your device so that you can continue to work in offline mode.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- See Implementing Compliance and Regulation, Managing Mobile Application Offline Settings, on the Oracle Help Center for more information.
Role Information
Agency staff can utilize this feature.
Conditions of Approval Tracking
Agency staff can now manage the conditions of approval that are applied to a planning application. Agency staff can pre-define standard conditions that are typically applied to all planning conditions. The standard conditions can be searched for and applied to a planning application. Agency staff can also apply custom or project specific conditions.
Conditions of Approval are requirements placed on discretionary projects such as use permits and development plans. This feature allows agency staff to setup and manage the conditions of approval that are applied planning applications.
Steps to Enable
You don't need to do anything to enable this feature.
Role Information
Agency staff can utilize this feature.
Planning staff can use the planner worklist to manage their assigned applications and activities. Planners can use the worklist to update activity statuses and due dates and to track time since an application was received. Those with appropriate privileges can view and assign or unassigned applications.
The planner worklist provides a central location for planning staff to assign or reassign planning applications, manage assigned applications and activities.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- See Using Community Development Planning and Zoning, Using the Agency Springboard and Worklist, "Using the Planner Worklist," on the Oracle Help Center for more information.
Role Information
Agency staff can utilize this feature.
Activity tracking provides a way for a planner to monitor a list of time-sensitive tasks that affect the process of a planning application.
There are four productized base date event triggers:
- Base Date: Anchor date for calculating the activity due date.
- Submission Date: The application is updated to the submitted status.
- Acceptance Date: The application is updated to accepted date.
- Hearing Date: The agency staff schedules a hearing for the planning application.
- Hearing Decision Date: The hearing body makes a decision and agency staff enters the date in the system.
When these events occur, the activity is automatically inserted to the tracking list.
Activity tracking helps planning department staff work through a list of time-sensitive tasks that affect the progress of a planning application. Many entitlement activities are driven by local ordinance, state law, and an agency’s internal process.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- See Using Community Development Planning and Zoning, Tracking Planning Application Activities, "Overview of Activity Tracking for Planning Applications," on the Oracle Help Center for more information.
Role Information
Agency staff can utilize this feature.
Pre-Application Meetings Using Agency Level Calendar
Pre-application meetings are an opportunity to meet with agency staff and receive valuable feedback. Agency staff can identify the type of application and related permits that may be necessary, permit processing steps and timelines, and pertinent information and technical studies that will be required to submit a complete application.
When setting up the pre-application meeting, choose the agency schedule as the meeting availability option. With this setting, pre-application meetings can be scheduled prior to assigning a planner to the application.
Agencies have the ability to schedule pre-application meetings prior to assigning a planner to the application.
Steps to Enable
You don't need to do anything to enable this feature.
Role Information
Agency staff can utilize this feature.
Schedule Ad hoc Public Meetings
Agency staff can schedule an ad hoc public meeting that occurs outside the agency's usual recurring meetings.
Your agency now has greater flexibility in scheduling public meetings. This feature allows agency staff to schedule an ad hoc meeting that occurs outside the agency usual recurring meetings.
Steps to Enable
You don't need to do anything to enable this feature.
Role Information
Agency staff can utilize this feature.
Incident Routing Based On Issue Type
When reporting an incident, a reporting party chooses the subtype for best resolving the issue. In turn, agency staff reviews incoming incidents to verify, among other things, that the subtype was correct so that it can be routed to the responsible code enforcement staff for follow-up inspections.
This feature provides agency staff the ability to re-categorize an issue as part of the incident review. The issue can be changed to another issue subtype within the same issue type, or to an entirely different issue type.
When the public reports an incident using an incorrect type the agency staff can now quickly resolve it by changing the type and automatically rerouting it based on predefined assignments. The reporting party will not need to do take any further action.
Steps to Enable
You don't need to do anything to enable this feature.
Role Information
Agency staff can utilize this feature.
Reporting parties have the option to report an incident as a registered user or guest user. Guest users can easily report an issue directly from the Code Enforcement 'Report an Issue' action on the landing page. However, they will not be required to create a profile and sign-in to do so. The guest user can provide contact information that will be associated with the incident if required by the agency.
This ability makes it easier and faster to notify code enforcement staff of potential violations.
Steps to Enable
You don't need to do anything to enable this feature.
Role Information
Public users can utilize this feature.
Online Access for Responsible Party
Responsible parties can manage their cases through self-service. When a case is created, a random access code is auto-generated and linked to the case. Responsible parties can provide access to this key through the notice of violation. A responsible party will use this access code to request access to a code case. A responsible party can request access as the principal party or as an additional contact.
This feature makes it easier for responsible parties to get into compliance. Now responsible parties can manage their cases online including the ability to request an appeal. An access code is used to ensure access is provided to the correct responsible party.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- See Using Community Development Code Enforcement, Code Enforcement Activities for Public Users, "Resolving Issues", on the Oracle Help Center for more information.
Role Information
Public users can utilize this feature.
Agencies are able to configure renewals by business license type to respect the license ordinance of the jurisdiction. Configuration includes the pending expiration, expiration dates, and the grace period before penalties apply. Renewals for each business license type can include one or more units of measure such as number of employees, estimated or actual gross receipts, or number of rental real estate units, to collect as tax related details in the renewal application.
In combination with expiration rules, this feature helps offload the notification, application, assessment and payment for license renewal.
Steps to Enable
The following steps need to be completed to implement this feature:
- Configure tax class with tax related units of measure.
- Map the tax class to the business license type.
- Set the expiration rules for the business license type.
- Identify the application form components that are required for the renewal.
Key Resources
- See Implementing Compliance and Regulation, Setting Up Business Licenses, "Setting Up Business License Amendments" on the Oracle Help Center for more information.
Role Information
Agency staff and public users can utilize this feature.
Amendments allow a business applicant to request changes to the details of their business entity and license information to reflect the current business scenario. Business applicants may make an amendment to an existing business license or business entity. The business applicant will complete an amendment intake to make the requested change. Your specific workflow dictates review and acceptance, and agency staff accepts or makes the change. You can validate conditions and then processes the amendment request. This action often requires reconciliation of the financial account to collect any outstanding fees.
Business owners, corporate representatives, or authorized agents are able to request changes to a business and the associated licenses by submitting an amendment application. Once the application is submitted, you can follow your workflow processes to review and approve or decline the amendment for the business. This feature offloads phone calls and visits to the agency to accomplish the changes to business and license information.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- See Implementing Compliance and Regulation, Setting Up Business Licenses, "Setting Up Business License Renewals" on the Oracle Help Center for more information.
Role Information
Agency staff and public users can utilize this feature.
Tax Related Details for Business Licenses
This feature allows an agency to collect tax related details and calculate fees for one or multiple units of measure for the current year. The agency may configure one or more units of measure to associate with a business license type. Such units of measure may include items such as gross receipts, number of employees, number of vehicles, number of residential rental units, commercial real estate square footage and more. The applicant populates the required information in the application intake and once submitted, role security identifies who may see this information in the tax related detail page of the business license activity page.
The mapping between this feature and the fee schedule allows the solution to dynamically assess the fee and allow the applicant to make immediate payment online.
Steps to Enable
To enable this feature, configure the business tax class with one or more units of measure. Map the tax class to the associated business license. This feature works in conjunction with the fee schedule identified for this business licenses.
Key Resources
- See Using Business Licenses, Managing Business License Applications, "Working with Tax-Related Details" on the Oracle Help Center for more information.
Intake Form Designer Enhancements for Business Licenses
An agency can design a single intake form and to show or hide data elements when the applicant is going through the origination, amendment, or renewal processes.
You have the ability to identify intake form groups as pertaining to origination, amendment and/or renewal applications.
Steps to Enable
When designing their intake form, you can select the license activity (origination, amendment and/or renewal) for which that portion of the intake form will display for the applicant.
Key Resources
- See Implementing Compliance and Regulation, Creating Intake Forms, "Configuring Activity Filtering for Business Licenses" on the Oracle Help Center.
Role Information
Agency staff can utilize this feature.
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 API UPDATES 20C TO 20D
Public Sector Compliance and Regulation 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. In the Public Sector Compliance and Regulation 20D update, there are a handful of APIs that have been altered which may impact the performance of the API. This documentation lists the changes to specific APIs so you can plan and alter your usage prior to getting the 20D update.
Documentation for all REST APIs included in Public Sector Compliance and Regulation can be found on the Oracle Help Center.
INSPECTIONS
The following REST APIs are for Inspections.
Inspections
InspectionId is no longer the object identifier. InspectionKey has been changed and is a newly added primary key field added to support future functionality.
A new primary key, INSPECTION_KEY, has been added to the psc_ins_inspection table to support future functionality. An upgrade script has been provided.
Inspection Checklists
The object identifier was a composite key comprised of: ChecklistId, InspectionId, AgencyId. The object identifier was changed to include InspectionChklistKey as a fourth field for the composite key. InspectionChklistKey was added as the primary key to support future functionality.
Added INSPECTION_CHKLIST_KEY as the Primary Key to table psc_ins_inspection_chklist. Previously, AGENCY_ID, INSPECTION_ID, and CHECKLIST_ID was the composite key. An upgrade script has been provided.
Inspection Checklist Items
The object identifier was composite key comprised of: InspectionId, ChecklistId, ChecklistItemId, AgencyId. The object identifier has been changed to include the InspectionClItemKey as a fifth field for the composite key. InspectionClItemKey was added as the primary key to the psc_ins_inspection_cl_item table to support future functionality.
Added INSPECTION_CL_ITEM_KEY as a primary key to the table psc_ins_inspection_cl_item. The previous key was a composite key consisting of: AGENCY_ID, INSPECTION_ID, CHECKLIST_ID, CHECKLIST_ITEM_ID. An upgrade script has been provided.
Inspection Mobile Checklist Items
The object identifier was a composite key comprised of seven fields: ChecklistId, ChecklistItemId, InspectionId, AgencyId, SetupAgencyId, SetupChecklistId, SetupChecklistItemId. The object identifier was changed to include InspectionClItemKey as an eighth field for the composite key. InspectionClItemKey was added as the primary key to the table psc_ins_inspection_cl_item to support future functionality.
INSPECTION_CL_ITEM_KEY was added as a primary key to the table psc_ins_inspection_cl_item. The previous key was a composite key consisting of: AGENCY_ID, INSPECTION_ID, CHECKLIST_ID, CHECKLIST_ITEM_ID. An upgrade script has been provided.
IVR Inspections
The InspectionId is no longer the object identifier. The object identifier was changed to InspectionKey which is a newly added primary key field added to support future functionality.
A new primary key, INSPECTION_KEY, was added to the table psc_ins_inspection to support future functionality. An upgrade script has been provided.
Assigned or Unassigned Inspections
InspectionId is no longer the object identifier. The object identifier has been changed to InspectionKey which is a newly added primary key field added to support future functionality.
PLAN REVIEWS
The following Plan Review REST APIs have had modifications.
Plan Review
The following updateable flags were changed:
- OriginalPlanReviewKey: “While Insert” was changed to “Never”
- Object VersionNumber: “Always” was changed to “Never”
The validation logic was modified to make it more restrictive. The API is now enforcing the only values that should have been accepted.
Plan Review Files
The following attributes are now hidden:
- LastUpdatedBy
- CreatedBy
The validation logic was modified to make it more restrictive. Validation was added to check for valid values.
Plan Review File Reviewers
The following attributes are now hidden:
- LastUpdatedBy
- CreatedBy
The validation logic was modified to make it more restrictive. Validation was added to check for valid values.
Plan Review Documents
The following attribute is now hidden:
- LastUpdatedBy
PARCELS
The following Parcel REST APIs have modifications.
Parcel Addresses
Added a check to ensure that the value of Country should not exceed 2 characters and that the value should already be set up in the main parcel.
Parcel Owners
Added a check to ensure that the value of Country should not exceed 2 characters and that the value should already be set up in the main parcel.
BUSINESS LICENSES
The following Business License REST APIs have modifications.
Business Location List Details
The following view object attributes have been renamed:
- Address1
- Address2
- Address3
- Address4
- PostalPlus4Code
- MailingPostalPlusFourCode
- MobileBusFlag
- MailingAddress1
- MailingAddress2
- MailingAddress3
- AltRawPhoneNumber
- EcontactPhoneAreaCodeOne
- EcontactPhoneAreaCodeTwo
- EcontactPhoneTypeTwo
The following new columns have been added:
- New Fields
- START_DATE
- END_DATE
- ADDRESS_TYPE
- BUILDING_TYPE
- COORDINATE_X
- COORDINATE_Y
- MUNCIPALITY_ID
- STREET_NAME
- STREET_TYPE
- STREET_SUFFIX
- UNIT_NUMBER
- ADDRESS_CODE
- CROSSROAD1
- CROSSROAD2
- LANDMARK
- SHAPE
- LATITUDE
- LONGITUDE
Business Owner List Details
A new mandatory not null field, REFERENCE_PUID, was added. An upgrade script has been provided.
The following view object attributes have been renamed:
- PersonLengthAtAddress
- ContactDmvLicNum
- ContactDmvLicSt
- ContactDmvLicExp
- Address1
- Address2
- Address3
- Address4
- PostalPlus4Code
- MailingAddress1
- MailingAddress2
- MailingAddress3
- MailingAddress4
- MailingPostalPlusFourCode
A new unique index was created on REFERENCE_PUID.
The following new columns were added:
- New fields
- REFERENCE_PUID – Not null and an upgrade script has been provided.
- AGENCY_ID – Not null and has a default value.
- STATUS
- VERIFICATION_STATUS
- VERIFICATION_DATE
- VERIFIED_BY
Business Registrations
A new mandatory not null field, REFERENCE_PUID, was added. An upgrade script has been provided.
The following view object attributes have been renamed:
- PersonLengthAtAddress
- ContactDmvLicNum
- ContactDmvLicSt
- ContactDmvLicExp
- Address1
- Address2
- Address3
- Address4
- PostalPlus4Code
- MailingAddress1
- MailingAddress2
- MailingAddress3
- MailingAddress4
- MailingPostalPlusFourCode
- Address1
- Address2
- Address3
- Address4
- PostalPlus4Code
- MailingPostalPlusFourCode
- MobileBusFlag
- MailingAddress1
- MailingAddress2
- MailingAddress3
- AltRawPhoneNumber
- EcontactPhoneAreaCodeOne
- EcontactPhoneAreaCodeTwo
- EcontactPhoneTypeTwo
A new unique index was created on REFERENCE_PUID.
The following new columns were added:
- REFERENCE_PUID – Not null and an upgrade script has been provided.
- AGENCY_ID – Not null and has a default value.
- STATUS
- VERIFICATION_STATUS
- VERIFICATION_DATE
- VERIFIED_BY
- START_DATE
- END_DATE
- ADDRESS_TYPE
- BUILDING_TYPE
- COORDINATE_X
- COORDINATE_Y
- MUNCIPALITY_ID
- STREET_NAME
- STREET_TYPE
- STREET_SUFFIX
- UNIT_NUMBER
- ADDRESS_CODE
- CROSSROAD1
- CROSSROAD2
- LANDMARK
- SHAPE
- LATITUDE
- LONGITUDE