Setting Up Agency-Level Options for Code Enforcement

Agency-level options for code enforcement include several settings related to the public user experience, assignment and autonumbering rules, and default settings for newly created issue types.

Agency-level options for code enforcement include settings such as:

• Whether public users can report issues anonymously.

• Whether incidents are automatically routed based on the issue type and subtype.

• The work schedule of the agency.

• The time period used for displaying recent issues on the public user map.

• Autonumbering rules for notices, citations, and inspections.

• Configuration for the public user landing page.

• Default code reference groups for issues types.

• Default time-based processing rules for issue types.

For more information about agency setup, see Setting Up Agencies

To configure agency level options for code enforcement:

1. Select Common Setup > Agency.

2. Click a row on the Agency Information tab.

3. Select the Features tab.

4. Click Options for the Code Enforcement offering.

   The Code Enforcement Options window opens.

5. Configure the General Settings.

   Page Element	Description
   Contact Information Required for Issue Reporting	Enable this switch to require contact information from users who submit issue reports. If the switch is not enabled, then the page where users supply contact information includes a Hide my contact information switch. When users hide their contact information, name and contact information is no longer required, and any data currently in those fields gets cleared. Even if you don’t require contact information, users must be registered and signed in to report an issue.
   Automatically Route Issues	Enable this switch to activate issue routing based on the issue type and subtype. When automatic routing is active, the Incoming Incidents worklist tab displays only incidents with the issue types and subtypes that are part of the user’s job function. If there’s only one code enforcement technician responsible for a particular issue type or subtype, then those issues are assigned to that technician automatically.
   Agency Work Schedule	Select an agency schedule from a list. This enables inspections to be scheduled based on the availability of the code officers. Due date calculations are based on the time rules set up and the schedule you select here. If the resulting due date is on a non-working day, then the next working day is set as the due date.
   Enable Workflow	Enable this switch to activate the workflow processes for incidents and cases in Code Enforcement.

6. Configure the settings in the Recent Cases section.

   Public users can view a map with markers identifying recent issues. These settings define which issues appear on the map.

   Page Element	Description
   Period	Choose how far back to look for issues by entering number of days or months, and then selecting Days or Months. Issues that were created within the specified time period appear on the map.
   Status	Select All to display all recent issues, regardless of status. Select Active to display only issues that haven’t been closed yet.

7. Use the Inspection section to configure inspection autoassignment.

   Page Element	Description
   Autoassignment	Indicate whether to enable automatic scheduling and assignment of incident and case inspections.
   Maximum Inspections per Day per Code Officer	Enter the maximum number of inspections per day for code officers. The autoassignment process will not assign inspections to officers who are at the maximum, but users can manually exceed this maximum. If you don’t enter a maximum, inspections will not be autoassigned.

8. Use Autonumber Rules section to select the following autonumber rules:

   Page Element	Description
   Notice Autonumber Rule	Select the autonumbering rule to increment numbers for notices.
   Citation Autonumber Rule	Select the autonumbering rule to increment numbers for citations.
   Inspection Autonumber Rule	Select the autonumbering rule to increment numbers for inspections.
   Fee Autonumber Rule	Select the autonumbering rule to increment numbers for fees.

   Note: For more information, see Setting Up Autonumbering.These fields are required if the Code Enforcement offering is enabled for your agency.

9. Use the Landing Page Message Definition section to enter these settings for the code enforcement landing page:

   Page Element	Description
   Message Title	Enter a short title or welcome statement for the code enforcement landing page. For example, Welcome or <City Name> Code Enforcement. This appears message appears as a title, in large text.
   Message Summary	Enter a subtitle for the code enforcement landing page. For example, Keeping our city safe and healthy. This text appears is medium-sized text under the larger main title for the page.
   Content URL	Enter a content URL for the Read More link that appears on the landing page next to the Message Summary text. Public users click this link to access a code enforcement information page that your agency maintains. If you leave this field blank, the Read More link opens a dialog box that displays the Landing Page Message. Note: If you want to link to a page outside of Oracle Public Sector Code Enforcement, you must enter a URL here.
   Landing Page Message	If you do not provide a Content URL that points to an agency-maintained information page, enter the text that will appear in the Read More dialog box. Rich text formatting tools are available for this message.

10. Use the Code Reference Group section to define the default code reference groups for new issue types.

    Enter the first code reference group in the blank row that appears. Use the Add button to add additional rows. Each row has the following elements:

    Page Element	Description
    Group ID	Select a code reference group that will be added by default to all newly created issue types.
    Enabled	Turn this switch on to have the code group added by default to newly created issue types. If the switch is off, the code group is not added to newly created issue types.
    Delete	Click to remove the row from the list of default code reference groups.

11. Use the Time-Based Rules section to define the default time-based rules to be entered automatically into newly created issue types.

    This section displays rows for all of the due date types that require time rules. You can’t add or remove rows. Instead, you must supply a time rule for each due date.

    For more information about time rules, see Setting Up Time Rules.

    Page Element	Description
    Due Date Type ID	Displays the unique identifier for the type of due date.
    Due Date Type	Displays the description of the type of due date — for example, Incident review date
    Time Rule ID	Select the time rule ID that specifies how the due date is calculated. The time rule ID includes a time policy that states how many days or hours until the due date. Time rules IDs are available for selection if they have the specified due day type and they are enabled.

12. Click Save, then close the window.

Agency Features for Code Enforcement

Use the Agency Features section to optionally enable or disable specific code enforcement features.

To enable or disable specific agency features for code enforcement:

1. Select Common Setup > Agency.

2. Click a row on the Agency Information tab.

3. Select the Agency Features tab.

   Page Element	Description
   Feature Code	Enter the code for the feature to be enabled. The available feature codes are ORA_PSCR_CREATE_ADDRESS, for the User can create a new address on applications feature. ORA_PSCR_CREATE_INCIDENT, for the Guest Users Can Report Incidents feature. This feature enables public users to report issues without registering or signing in first. ORA_PSCR_ESTIMATE_FEE, for the Guest Users Can Estimate Fees. This feature enables public users to estimate fees without registering or signing in first. ORA_PSCR_RST_DIRECT_CASE, for the Restrict Direct Case Creation Without Incident feature. For details, see the next section on Restricting the Direct Creation of Incidents and Cases in Oracle Permitting and Licensing. ORA_PSCR_RST_DIRECT_INCIDENT, for the Restrict Direct Incident Creation feature. For details, see the next section on Restricting the Direct Creation of Incidents and Cases in Oracle Permitting and Licensing.
   Name	Displays the name of the selected feature code.
   Enabled	Use this switch to enable or disable the feature.
   Delete	Click this icon to remove a feature from the grid.

Restricting the Direct Creation of Incidents and Cases

Agencies can now control whether an external CRM system will exclusively handle the creation of incidents and cases. When your agency chooses this option, the direct creation of incidents and cases needs to be restricted in the Oracle Permitting and Licensing system.

To enable the agency features to restrict the direct creation of incidents and cases:

1. Select Common Setup > Agency.

2. Click a row on the Agency Information tab.

3. Select the Agency Features tab.

4. Depending on the agency feature to enable, select the switches to turn on for the corresponding feature codes:

   • To restrict the creation of incidents: Turn on the switch for the feature code ORA_PSCR_RST_DIRECT_INCIDENT.
     Caution: Before enabling this agency feature, ensure that the option to report an issue is unavailable for public users.

     Public users can report issues from both the public user landing pages and code enforcement landing page. Hence, disable the Report An Issue menu item on both the Products and Code Enforcement menus to completely hide the navigation menus from public users.

     To do so, select the Report An Issue menu items from the Products and Code Enforcement menus. Use the Edit button and set the Show On option to None. This hides the menu items from all devices. For details see, Configuring Menu Structure, "Selecting a Menu Item" and "Configuring General Menu Item Properties".

   • To restrict the creation of cases: Turn on the switch for the feature code ORA_PSCR_RST_DIRECT_CASE.
5. Click Save, then close the window.

Once this feature is completely enabled, all options for the public users to report an issue on the public landing pages and code enforcement pages will be hidden. For the agency staff, the options to report incidents and create cases using buttons on Incident and Case List pages, and worklist pages will be hidden.

Important: You must provide the following privileges to allow selected agency staff to still access and complete the corresponding restricted tasks, if required:

• PSC_CREATE_STANDALONE_INCIDENT_PRIV: Allows selected agency staff to report new incidents.

  However, users with System Administrator roles will have access to report incidents without any special privileges.

• PSC_CREATE_STANDALONE_CASE_PRIV: Allows selected agency staff to record violations or create cases without reported incidents.