3Setting Up Planning Applications
Setting Up Agency-Level Options
You set up the Oracle Intelligent Advisor for Permits and Planning and Zoning on the Permit Options page during agency setup. You can also configure the summary title and text for the Anonymous User Landing Page and the Registered User Landing page.
Select .
Click a row on the Agency Information tab.
Select the Features tab.
Oracle delivers the list of offerings on the Features tab. The Permits offering encompasses both Permits and Planning and Zoning.
Disregard the Enabled column for the Permit offering. The offering is enabled in the Functional Setup Manager (FSM).Click Options for the Permits offering.
On the Permit Options page, you can update values for the following fields:
Page Elements
Definition
Oracle Policy Automation ID
Enter the unique identifier for the Oracle Policy Automation policy model to be used for this offering.
The offering-specific policy model that you specify here takes priority over any agency-wide policy definition that you enter on the main Agency Information page.
Message Title
Enter a short text version of the landing page message in a title format. If you leave this field blank, the value in the Label field on the Link Details page for the menu navigation link Online Permits is displayed.
Message Summary
Enter a longer version of the landing page message title in a sentence format. If you leave this field blank, the value in the Description field on the Link Details page for the menu navigation link Online Permits is displayed.
Button Content URL
Enter a content URL for the Read More button. Public users click this button to access the agency’s own permit information page, outside of Oracle Public Sector Permits. If you leave this field blank, the Read More button opens a dialog box that displays the Landing Page Message.
Note: If you want to link to a page outside of Oracle Public Sector Permits, you must enter a URL here.Landing Page Message
Enter a welcome message in rich text to appear in a dialog box on the landing page, if a URL to access the agency’s page is not defined.
For more information on Oracle Intelligent Advisor, see Overview of Oracle Intelligent Advisor Configuration.
For more information on the Landing Page Message Definition, see Defining Summary Details.
Setting Up Planning Application Types
Define the types of planning applications supported by an agency, including pre-applications. You add a planning application type and associate workflow process definitions on the Planning Application Type definition page.
Before you can create an application form, you must first create a planning application or pre-application type on the Planning Application Type definition page. The type defines attributes that will be available for the planning application or pre-application.
Adding Planning Application Type Definitions
Select .
On the Transaction Type – Planning Applications page, click the Add button.
On the Planning Type Applications page, enter values for the following fields:
Page Element
Description
Classification
Displays the type of application. The classification for this page indicates this is a planning application.
Subclassification
Displays the subclassification of the application type.
If you would like to create a pre-application type, select Pre-Application from the drop-down list. The default value is Not Applicable, which indicates a standard planning application.
Planning Application Type
Enter a name for the type of planning application.
Planning Application Type ID
Enter a unique alphanumeric code or short name for the planning application type. Do not use special characters, including symbols or punctuation, or spaces.
Status
Select from the following to indicate the planning application type status:
Preliminary: The planning application type is being defined but is not available for use.
Ready: The planning application type is ready to be accessed from the landing page for testing or production use, depending on the environment.
Void: The transaction type is no longer available.
Note: The form design can be in published status or draft status and be set to Ready. In draft status, the form can be accessed from outside the form designer—such as the Apply page—for testing purposes in the development or test environment.Form Design Status
A read-only field indicating whether the form design is published or currently being developed.
Draft: The form design is currently being created or modified. Form designs in draft status are not migrated to other environments and can’t be cloned.
Published: The form design is complete. Form designs in published status can be migrated to other environments and can be cloned.
Autonumber Rule
Select the autonumbering rule to increment numbers for planning applications.
You can delete the autonumbering rule when it isn’t being used by any transaction types.
For more information, see Setting Up Autonumbering.
Valid from Date and Valid to Date
Enter a range of dates when this planning application type is valid. The default from date is the current date. The default end date is Open. You can update these dates as needed.
Public User Enabled
Select from the following to indicate whether the intake form can be accessed and by which user types:
Enabled for all users: Only registered public users and agency users can access the intake form.
Enabled for registered users: Only registered public users and agency users can access the intake form.
Not enabled for public users (default): Only agency users can access the intake form.
Note: Currently, Enabled for all users and Enabled for registered users have equivalent access.Hearing
Select whether public hearings are applicable or not applicable to this planning application type.
For more information, see Setting Up Hearing Bodies, Setting Up Hearing Hierarchies, and Setting Up Hearing Decisions.
Application Group
Select an application transaction group that you want to associate with the planning application type.
For more information, see Setting Up Transaction Groups.
Category
Select a transaction category that you want to associate with the planning application type.
For more information, see Setting Up Transaction Categories.
Subcategory
Select a transaction subcategory that you want to associate with the planning application type.
For more information, see Setting Up Transaction Subcategories.
Activity Group
Select an activity group with the activities that you want to use for tracking planning application task due dates. Whenever an application of this application type is submitted, activities set up and mapped to the transaction type are added to the planning application’s activity tracking page.
For more information, see Setting Up Activity Tracking.
Document Group
Select a document group to manage attachments for the planning application type.
When you specify a document group, document attachments can be classified into categories and subcategories during the application process and when you upload files. Then you can see the category for a document on the attachments page in the application details.
For more information, see Setting Up Document Groups.
Fee Schedule
Select a fee schedule that you want to associate with the planning application type. A department is required when you enter a fee schedule ID.
For more information, see Setting Up Fee Schedules.
Bill Type
Select a bill type to associate with the planning application type.
The billing type identifies the type of invoice that can be generated from the record. The bill type is required.
For more information, see Setting Up Bill Types.
Department
Select a department that you want to associate with the planning application type. A department is required if you add a Fee Schedule ID to the planning application type.
If a department is specified on the Fee Item setup page, the fee item department overrides the department specified here on the planning application type.
For more information, see Setting Up Departments.
Terms of Use ID
Select a terms of use definition to associate with the planning application type. The available values for planning applications are determined by the usage on the terms of use ID.
For more information, see Setting Up Terms of Use.
Description
Enter a user-facing description of the planning application type. On the Apply page, this description appears under the application type name.
The description helps public users understand the purpose of the application type.
URL
Enter a URL for a web page that gives public users more information about the planning application type.
If you enter a URL, then a Learn More link appears at the end of the application type description on the Apply page. The user clicks this link to open the specified URL.
If you leave this field blank, the Learn More link is not visible on the Apply page.
Setting Up Conditions of Approval
In the Conditions of Approval section, you enter the report ID and template that associate with this planning application type. The report ID determines the type of report that should be printed to list the conditions of approval and the conditions of approval template determines the conditions of approval that will be applied to the planning application.
For more information about conditions of approval, see Setting Up Conditions of Approval Templates.
Setting Up Planning Application Expiration
In the Expiration section, you can enter the expiration group that defines the expiration rules for this planning application or pre-application type. Expiration rules determine the expiration dates that correspond to application activity. For more information about planning application and pre-application expiration, see Setting Up Planning Application Expiration Rules.
Setting Up Workflow for a Planning Application
You set up workflow using the Oracle Autonomous Integration Cloud (OIC) before associating the workflow with the planning application type.
For more information, see Setting Up Process Definitions for Workflow.
Select .
On the Transaction Type – Planning Applications page, click the Add button.
In the Workflow Setup section on Planning Application Type page, enter values for the following fields:
Page Element
Description
Space Name
Enter the space where the workflow process application is stored. You can group related applications in a space as well as enable users to collaborate when developing applications.
Application ID
Enter the name of the workflow process application in OIC. For more information, see Creating and Managing Applications.
Version
Enter the version of the workflow process application.
Process Definition
Enter the name of the workflow process definition that applies to this particular planning application.
Setting Up Plan Reviews for a Planning Application Type
Define how plan reviews are conducted for planning applications associated with the planning application type.
Select .
On the Transaction Type – Planning Applications page, click the Add button or select an existing planning application type.
In the Plan Reviews section on Planning Application Type page, enter values for the following fields:
Page Element
Description
Plan Review Type
Select the method used for reviewing plans for planning applications associated with the planning application type.
Manual: Plan reviews are tracked as part of planning application workflow, but are performed without the use of integrated electronic document review software.
Not Used: Plan reviews are not tracked as part of planning application workflow.
Electronic: Plan reviews are tracked as part of planning application workflow, and are performed through integration with electronic document review software.
For more information on plan reviews, see Managing Manual Plan Review Cycles and Managing Electronic Plan Review Cycles.
Enable Auto Assignment
Turn on this switch to enable the automatic assignment of plan reviewers for planning applications associated with this planning application type.
When this switch is on and the assigned planner gives a planning application associated with this planning application type a status of Completed - Plan Review Required, the automatic assignment process:
Adds a reviewer row to the plan review cycle for each plan reviewer department selected for the planning application type. If no plan reviewer departments are selected for the planning application type, the process creates the plan review cycle, but doesn’t add any reviewer rows.
Adds the designated department lead to the Reviewer field for each reviewer row. If a department doesn’t have a department lead selected, the process still creates a row for the department, but leaves the Reviewer field blank.
Note: This switch is available only when the Plan Review Type is Manual.Plan Reviewer Departments
Select the departments that should be included in any plan reviews associated with this planning application type. Plan coordinators should add a reviewer from each of the required departments. The Reviewers grid of the Plan Review page displays the required departments that you select here.
When Enable Auto Assignment is turned on, the process automatically adds a plan reviewer row to plan review cycles for each of the selected departments.
Note: A plan reviewer department is available to select only if the Planning and Zoning classification is selected for it on the Plan Reviewer Department page.For more information about plan reviewer departments, see Setting Up Plan Reviewer Departments.
For more information about plan reviews, see Electronic Plan Review Process Flow and Manual Plan Review Process Flow.
Cloning Planning Application Types
Click the Clone button to create a clone of the current planning application type, which you can then use to create a different planning application or to create a different version of the current planning application.
For more information on cloning permits and planning applications, see Cloning Transaction Type Definitions.
Designing Intake Forms
After you’ve entered the appropriate initial information for the planning and zoning type, you can then begin to design the intake form that end users will use to submit an online planning application. You create an intake form using the designer. You access the designer by clicking the Design Form button.
For more information on designing intake forms, see Using the Intake Form Designer.
Setting Up Planning Application Display Groups
Use the Display Group setup pages to display groups of planning applications on your agency’s landing page, where you start an application.
A display group identifies a meaningful grouping of planning application types displayed as a list on the Apply page. The list appears as the planning applications that agency staff or a guest can select to initiate the application process.
For more information about how the Apply page looks and is used, see Choosing an Application Type.
Before setting up planning application display groups, you must set up the types of planning applications that your agency offers. See Setting Up Planning Application Types.
Adding Planning Application Display Groups
Select .
On the Planning Application Display Group page, click Add to add a new grouping.
On the Planning Application Display Group Details page, enter values for the following:
Page Element
Description
Display Group ID
Enter a planning application display group name.
Display Group
Enter a name for the display group that appears on the Apply page for guests and agency staff.
Description
Enter a description of the display group that appears on the Apply page for guests and agency staff.
URL
Enter a URL that agency staff can use to access additional information. This page is the only place that the URL appears, so it is not available to guests.
Applicable Classification
Select the check box for the applications to which this display group applies. Choose from these options:
Business Licenses
Permits
Planning and Zoning
This option determines whether a display group type is shown on the Apply page for public users. A display group can be included with more than one classification.
Verify that the Enabled switch is turned on. The switch is turned on by default for new planning application display groups.
In the Display Group Lines section, click Add to set up a line on the Display Group Line Details page. The display group lines make up the list of planning application types in the new display group.
Note: A mix of different transaction types can be added to a display group. For example, you can add a permit transaction type to a planning application display group and the other way around.Page Element
Description
Display Order
Enter a numerical value in this field to specify the order in which you want the planning application type to be displayed, if desired. The default value is 0 and upon saving, the system automatically assigns the next value.
Transaction Type ID
Select an existing transaction type ID.
The description for the ID you enter here will appear in the Transaction Type field.
Transaction type information
Review the attribute information for the planning application type to verify you have selected the correct transaction type ID:
Transaction Type
Classification
Application Group
Category
Subcategory
For more information about transaction type attributes, see Setting Up Planning Application Types.
On the Planning Application Display Group Details page, click Save.
Modifying Planning Application Display Groups and Lines
You can modify planning application display groups and the planning applications in the list on the Planning Application Display Group Details and Display Group Line Details pages, respectively.
Select .
On the Planning Application Display Group page, select the row for the planning application group that you want to modify.
On the Planning Application Display Group Details page, you can:
Modify the group name and description. You can’t change the Display Group ID.
Turn the Enabled switch on or off to enable or disable the display group.
If you made any changes, click Save.
To modify the display group lines (the list of planning applications in a display group), select the row for the planning application group that you want to modify on the Planning Application Display Group page.
On the Planning Application Display Group Details page, select a display group line in the Display Group Lines grid.
On the Display Group Line Details page, you can change the values in these fields:
Update the Display Order field to change the order in which the lines appear.
Update the Transaction Type ID field with another existing planning application type ID.
If you made any changes, click Save.
Deleting Planning Application Display Groups and Lines
Select .
On the Planning Application Display Group page, select the row for the planning application group that you want to delete.
If you want to delete the display group, click Delete on the Planning Application Display Group Details page.
If you want to delete multiple display groups, you can delete them from the Planning Application Display Group page:
Click Edit.
Select the check boxes for the display groups to delete.
Click Delete.
To delete a display group line, go to the Planning Application Display Group Details page and select a display group line in the Display Group Lines grid.
On the Display Group Line Details page, click Delete.
If you want to delete multiple display group lines, you can delete them from the Planning Application Display Group Details page:
Click Edit.
Select the check boxes for the display group line rows to delete.
Click Delete.
Setting Up Planning Application Expiration Rules
You can set up expiration rules for the different phases of the planning application lifecycle.
You set up expiration rules for planning applications to define:
When an inactive pending application expires.
When the entitlement expires.
First, you define the rules in an effective-dated group. After setting up the expiration rules, you add the rules group ID to the application type definition and periodically run batch rules processing to update permit expiration statuses.
Setting Up Expiration Rule Groups
Here’s how to set up the rule group:
Select .
On the Planning Expiration Group page, enter values for these fields:
Page Element
Description
Expiration Group ID, Expiration Group Name, and Description
Enter an ID for the expiration group, a group name, and description.
Subclassification
Select Not Applicable for a planning application or Pre-Application. Use Pre-Application if you are applying this group of rules to a pre-application transaction type.
Effective Start Date and Effective End Date
Enter the range of dates when the group is effective. If you want to leave the effective dates open-ended, don’t enter a date for the end date.
To see the effective date history for an expiration group, click Show All Dates. On the History Data page, you can search history by effective start date or click Add to add new effective-dated rules for an expiration group.
Show All Dates
Click to access the effective-dated history of the rules definition. This button is available after you create the first rule.
You can also search history by effective start date. Click Add to create a new effective-dated row for an expiration group.
Verify that the Enabled switch is turned on. The option is active by default for a new expiration group.
Create expiration rules in the Expiration Rules section.
Defining Expiration Rules
Here’s how to set up the details about the expiration rules in the group:
Select .
Click Add in the Expiration Rules section.
Enter values to create each rule:
Page Element
Description
Expiration Basis
Select the type of expiration for the rule, based on the status of the application:
Pre-application expiration – Applies only to pre-applications. Users must complete the pre-application within the specified period of time.
The expiration timeframe begins when the user saves the pre-application and ends when the user starts the planning application.
Inactive pending application – When the planning application is in a pending status, the user must submit the application before the expiration date.
The expiration timeframe begins when the user saves a planning application and ends with application submission.
Entitlement expiration – Applies only to entitlements for planning applications. Users must submit a permit application after the entitlement is issued and before the expiration date.
The expiration timeframe begins when the agency issues the completed entitlement and ends when the user submits the permit application.
Note: Because start and end dates require specific statuses, workflow processes must include status update tasks for Application Accepted ( Accepted) and Certificate of Occupancy ( Certificate) or Completed ( Completed).Expiration Duration
Enter the amount of time that the user has before the expiration date.
About to Expire
Enter when you would like a notification to appear on the application that shows the user how long until the application expires. For example, you can enter 2 days to show that a pending application expires in 2 days.
Grace Period
Enter the amount of time the application is valid beyond the expiration date. For example, if a pending application expires in 30 days, you may provide a grace period of an additional 3 days.
Number of Extensions
Enter the number of allowed extensions beyond the expiration date. For example, to allow up to 2 extensions you would enter 2.
You can manually extend the expiration during the About to Expire and Grace Period timeframes, when the Extend link is available on the Overview page in the application details. This link is available only for agency staff with appropriate permissions. You can’t manually extend the expiration for applications in a pending status.
Both manual extensions and extensions that occur automatically due to inspection activity count toward the number of available extensions.
Verify that the Enabled switch is turned on for each rule. The option is active by default for a new expiration rule.
Click Save.
Setting Up Communication Rules
You can set up communication rules to send communications when the pre-application or planning application is about to expire or expired. Agency staff and the contact listed on the application receive the notifications. Click Add in the Communication column and select About to Expire, Expired, or both, and the recurrence of the communication.
Depending on the expiration communication rules you define, you must also set up communication templates for these delivered events:
About to Expire Pre-application – The communication event is triggered when the inactive pending application or pre-application is about to expire.
Expired Pre-Application – The communication event is triggered when the inactive pending application or pre-application expires.
About to Expire Planning and Zoning Application – The communication event is triggered when the inactive pending application or planning application is about to expire.
Expired Planning and Zoning Application – The communication event is triggered when the inactive pending application or planning application expires.
For more information about configuring the communication templates for the email or notification you want to send when the event occurs, see Setting Up Communication Templates.
Associating Expiration Groups with Application Types
After you create an expiration group, you associate the group of rules with a planning application type.
Select .
Click the row for the planning application type.
On the selected Planning Application Type page, enter the expiration group ID. You can look up the expiration group by expiration group name and description.
Click Save.
For more information see Setting Up Planning Application Types.
Running the Expiration Rule Process
After setting up expiration rules and adding an expiration rule group ID to the planning application type definition, you must set up expiration rule processing to periodically update the expiration statuses.
Run the process that updates permit and planning application expiration statuses on the Process Expiration Rules page, which you access by selecting . Oracle recommends that you schedule expiration rules processing to run daily.
For information about setting up expiration rules processing, see Updating Application Expiration Status.
Managing Pre-Application Meeting Configuration
Pre-applications are the initial step in the planning and zoning process, and are used to allow the property owner or developer to work with agency planners to receive feedback prior to submitting planning applications. A pre-application meeting is scheduled between the property owner or developers and agency planners to determine the necessary applications and approvals for the project.
Configuring the Pre-Application Meeting
Administrators set up and manage the pre-application meeting configuration on the Manage Pre-Application Meeting Configuration page.
Select . Or, Select Setup and Maintenance tile on the Agency Springboard > Select Public Sector Planning and Zoning > Planning Application Types functional area > Manage Pre-Application Meeting Configuration task.
On the Manage Pre-Application Meeting Configuration page, the Pre-Application Meeting section allows you to set up applicant privileges. Enter values for the following fields:
Page Element
Description
Applicant can request
Select to allow an applicant to request a pre-application meeting. Applicants can access the Pre-Application Meeting Request page and schedule a meeting based on the availability of the agency staff. See Working with Pre-Application Meetings.
Applicant can reschedule and cancel
Select to allow an applicant to reschedule or cancel their meeting.
The Meeting Availability section allows you to set up the parameters for scheduling meetings, determined by:
Planner meeting schedule or
Agency meeting schedule
Planner meeting schedule: Select to allow users to schedule meetings based on the availability of their assigned planner.
Note: You also need to ensure that all the Planners are assigned a Pre-Application meeting work schedule on the Agency Staff Profile. Enter values for the following fields:Page Element
Description
Meeting Duration in Hours
Select a value to set the maximum amount of time the meeting can be scheduled for. Users will see this value as the duration of the meeting, and they are not allowed to edit the field. See the section Scheduling a Pre-Application Meeting under Working with Pre-Application Meetings.
Schedule after Number of Days
Select a value to set the number of days from the current date, so that users can schedule a meeting on a date available after the number of days specified here. For example, if you select a value 5 on the 10th day of this month, the calendar on the Pre-Application Meeting Request page displays the dates that are available after the 15th day of the month.
Schedule up to Number of Days
Select a value to set the number of days that will be available for the users to select a date on the calendar for scheduling the meeting. For example, if you select a value of 90, the calendar on the Pre-Application Meeting Request page displays 90 calendar days starting from the date the user is making the selection.
See the section Scheduling a Pre-Application Meeting under Working with Pre-Application Meetings.
Agency meeting schedule: Select to allow users to schedule meetings based on the schedule of the agency. In addition to the fields described above, enter values for the following fields:
Note: If you select this option, then you need not assign Pre-Application meeting schedule to the planners as the Pre-Application meeting schedule will not be considered while determining the availability.Page Element
Description
Pre-Application Work Schedule
Select the Agency level work schedule that needs to be considered while determining the availability for the pre-application meeting.
Maximum Concurrent Meetings
Select a value to determine the maximum number of meetings that can be scheduled at a time.
The Meeting Agenda and Location section allows you to set up the agenda and the location for the pre-application meeting.
Page Element
Description
Include Agenda
Select the check box and enter the agenda in the Meeting Agenda field.
Include Location
Select the check box and search for the desired location of your agency using the Agency Information look up. The address of the location you select is displayed in the Meeting Location field.
Note: Users can edit the entries for the agenda and location fields while scheduling the meeting on the Pre-application Request page.
Setting Up Hearing Bodies
With Oracle Public Sector Compliance and Regulation Cloud, you will use the Public Hearing feature to configure hearing bodies and hearing hierarchies, schedule hearings, and record decisions.
Setting Up Public Hearing
A public hearing is an official meeting where members of the public, the hearing body, and the applicant of the planning and zoning application come together to discuss the facts about the application submitted by the applicants.
The following topics apply to administrators for setting up and maintaining the Public Hearing process:
Setting up Hearing Body
Setting up Hearing Hierarchy
Setting up Hearing Decision
Setting Up Hearing Body
A hearing body is a group of individuals formed to evaluate the testimony presented by applicants and to provide feedback.
Adding a Hearing Body
To add a hearing body:
Select .
Click Add on the Hearing Body page and enter values for the following fields:
Page Element
Description
Hearing Body Code
Enter a unique identifier of the hearing body.
Name
Enter a name for the hearing body.
Additional Information
Enter any text as details about the hearing body.
Enabled
Turn on the switch to make the hearing body available for use.
Appeal Period
Select the number of days after the public hearing, when an appeal is allowed.
Maximum Agenda Items
Select a value from the options. As an agency user you can configure the maximum number of agenda items that can be heard on a day.
Address fields
The agency address. The Country field displays US.
As you enter a Postal Code, the type-ahead list shows values that include appropriate state and city combinations. After you select a value, the city and state appear as read-only fields, and two address fields appear so that you can enter the rest of the address.
If you don’t know the postal code, click the Don’t know link to display a full set of address fields.
Select a pattern of recurrence of the meeting from these fields:
Page Element
Description
Recurrence Pattern
Select the pattern for the recurrence of the public hearing:
Weekly
Monthly
Select the Weekly recurrence if you want to schedule the meeting every week. Enter values for the following fields:
Page Element
Description
Weeks between Occurrences
Select the number of weeks between one meeting occurrence and the next.
Days of the Week
Select the days of the week on which you want the meeting to recur.
Recurrence Start Date Time
Select a date and time from which the meeting recurrence should be effective.
Select the Monthly recurrence if you want to schedule the meeting every month. Enter values for the following fields:
Page Element
Description
Months between Occurrences
Select the number of months between one meeting occurrence and the next.
Days of the Week
Select the check box if you want to schedule the meeting on particular days of the week. Click Add to open the Days of the Week page and select the days of the week, for example First Monday:
Occurrence: Select – First, Second, Third, Fourth, or Last the day of week
Weekday: Select the day of the week from Monday, Tuesday, and so on.
Turn on the Enable switch to make the setting available for use and click Save. Use the Add button to include multiple rows.
Note: You can modify or delete the entry. Click the row and use the Days of the Week page to make the change.Dates
Select the check box if you want to schedule the meeting on particular dates of the week. Click Add to open the Dates page and select from all the available dates.
Turn on the Enable switch to make the setting available for use and click Save. Use the Add button to include multiple rows.
Note: You can modify or delete the entry. Click the row and use the Dates page to make the change.Recurrence Start Date Time
Select a date and time from which the meeting recurrence should be effective.
Click Save to save the new hearing body and return to the Hearing Body page.
Modifying a Hearing Body
To modify a hearing body:
Select .
On the Hearing Body page, click the record of the hearing body you want to edit.
On the Hearing Body details page you can make changes to the fields and click Save.
Note: You can make changes to all the fields except the Hearing Code.The Hearing Body page now lists the updated record.
Deleting a Hearing Body
To delete a hearing body:
Select .
On the Hearing Body page, click the record of the hearing body you want to delete.
On the Hearing Body details page you can click the Delete button. Click OK on the confirmation message.
The Hearing Body page lists only the existing records.
Setting Up Hearing Hierarchies
Hearing Hierarchy defines the levels of hearing bodies that an application can be escalated through. In an agency, a planning and zoning application can be escalated to a higher body in cases of appeal, where the highest hearing body decision is considered final.
Agencies set up their hearing hierarchy to address events such as an appeal. For example, a hearing begins with the Planning Committee and then an appeal escalates the application to the Planning Commission. If appealed again, the application moves to the City Council.
Adding a Hearing Hierarchy
To add a hearing hierarchy:
Select .
Click Add on the Hearing Hierarchy page and enter values for the following fields:
Page Element
Description
Hierarchy Code
Enter a unique identifier of the hearing body.
Hierarchy
Enter a name for the hearing hierarchy.
Enabled
Turn on the switch to make the hearing hierarchy available for use.
Description
Enter any text to describe the hierarchy.
Click Add and enter values for the following fields:
Page Element
Description
Hearing Body Code
Select a hearing body code to associate with the new hearing hierarchy.
Sequence
Select a number to determine the escalation level of the selected hearing body within the hierarchy. For example, if the value 2 is selected, the selected hearing body will be the second in the hierarchy for the public hearing.
Appeal Allowed
Turn on the switch if you want to allow the agency to appeal after the hearing body places its decision. The agency will not be allowed to appeal the hearing to the next body in the hierarchy, if the switch is turned off.
Enabled
Turn on the switch if you want to allow the hearing body to be available for use.
Click to add a new row and add a new hearing body in the hierarchy.
Click to delete the row. The hearing body will be removed from the hierarchy.
Click Save to save the newly created hierarchy and return to the Hearing Hierarchy page, where the new hierarchy you created is listed.
Modifying a Hearing Hierarchy
To modify a hearing hierarchy:
Select .
On the Hearing Hierarchy page, click the hearing hierarchy row you want to edit.
On the Hearing Hierarchy details page make changes to the fields and click Save.
Note: You can make changes to all the fields except the Hierarchy Code.
Deleting a Hearing Hierarchy
To delete a hearing hierarchy:
Select
On the Hearing Hierarchy page, click the hearing hierarchy row you want to delete.
On the Hearing Hierarchy details page, click Delete and click OK on the confirmation page to delete the hearing hierarchy.
Click Save and return to the Hearing Hierarchy page. The page lists the updated hierarchy rows.
Setting Up Hearing Decisions
The outcome of a public hearing is referred to as hearing decision. Agency staff such as assigned planners update the decision from the hearing body into the system.
System-defined Public Hearing Decisions
Oracle delivers hearing decisions for use during the hearing process. System administrators can configure the decisions specific to their agency, which are mapped to one of the system-defined decisions listed below:
Approved
None
Denied
Continue
Adding a Hearing Decision
Select .
The Hearing Decision page lists all the decisions you have configured. Click Add.
One the Hearing Decision Status detail page, enter values for the following fields:
Page Element
Description
Code
Enter a unique identifier of the hearing decision.
Name
Enter a name to identify the decision. Example, Approved with Conditions, Not Result, and so on.
Description
Enter any text to describe the decision.
Applies To
Select the decision check box for which the status applies to:
Hearing Decision (This is the default selection.)
Staff Decision
Decision
Select one of the system-defined decisions to map to the new decision you are creating:
Approved
None
Denied
Continue
Enabled
Turn on the switch to make the decision available to use.
Click Save to save the new hearing decision and return to the Hearing Decision page, which lists the newly created decision.
Modify a Hearing Decision
To modify a hearing decision:
Select .
The Hearing Decision page lists all the decisions you have configured. Click the row of the decision you want to modify.
On the Hearing Decision detail page, make changes to the fields and click Save.
Note: You can make changes to all the fields except the Code.The Hearing Decision page lists the updated row.
Deleting a Hearing Decision
To delete a hearing decision:
Select .
The Hearing Decision page lists all the decisions you have configured. Click the row of the decision you want to delete.
On the Hearing Decision detail page, click Delete and confirm deletion by selecting OK.
Click Save and return to the Hearing Decision page. The page lists the updated decision rows.