1. Implementing Compliance and Regulation
  2. Setting Up Transactions

5Setting Up Code Enforcement

Setting Up Corrective Actions

Define the various corrective actions that can be applied to resolve code violations identified by an agency.

A corrective action can resolve more than one code violations. You add a corrective action using the Corrective Action page and assign the action to one or more code references on the code configuration page.

Adding Corrective Actions

  1. Select Code Enforcement Setup > Corrective Action.

  2. Click Add on the Corrective Action page to add a new corrective action.

  3. On the Corrective Action Details page, enter values for the corrective action.

    Page Element

    Description

    Corrective Action ID

    Enter a unique identifier for the corrective action.

    Summary

    Enter a summary about the action that is to be taken to resolve the violation.

    Description

    Enter longer descriptions or instructional information that can be formatted using a rich text editor.

  4. Verify that the Enabled switch is turned on. The option is active by default for a new corrective action.

  5. Click Save.

Modifying Corrective Actions

You can modify corrective actions for the code violations on the Corrective Action page.

  1. Select Code Enforcement Setup > Corrective Action.

  2. On the Corrective Action page, select the row for the corrective action that you want to modify.

  3. On the Corrective Action Details page, you can edit the summary and description. Click the Enabled switch to enable or disable the corrective action.

  4. Click Save to save the changes.

Deleting Corrective Actions

You can delete corrective actions for the code violations on the Corrective Action page.

  1. Select Code Enforcement Setup > Corrective Action.

  2. On the Corrective Action page, select the row for the corrective action that you want to delete.

  3. On the Corrective Action Details page, click the Delete button.

Setting Up Code References for Code Enforcement

Code references are pointers to the documentation for a specific code used on a violation. These references instruct readers to refer to documentation for the specific item. Set up the Public Sector Compliance and Regulation system to point the user to a specific documentation regarding that code violation.

Adding Code References

  1. Select Code Enforcement Setup > Code Reference.

  2. Click Add on the Code Reference page to add a new code reference.

  3. On the Code Reference Details page, enter values for the code reference.

    Page Element

    Description

    Code Reference ID

    Enter a unique identifier of the code reference.

    Summary

    Enter a summary about the violation that is related to the incident.

    Description

    Enter longer descriptions or instructional information that can be formatted using a rich text editor.

    Corrective Action

    Select the corrective action that can be applied to resolve the violation.

    Summary

    Displays information about the corrective action that will be taken to resolve the violation.

  4. Verify that the Enabled switch is turned on. The option is active by default for a new code reference.

  5. Click Save.

Modifying Code References

You can modify code references on the Code Reference page.

  1. Select Code Enforcement Setup > Code Reference.

  2. On the Code Reference page, select the row for the code reference that you want to modify.

  3. On the Code Reference Details page, you can:

    • Change the values for the summary, description, and corrective action fields.

    • Click the Enabled switch to enable or disable the corrective action.

  4. Click Save to save changes.

Deleting Code References

You can delete code references on the Code Reference page.

  1. Select Code Enforcement Setup > Code Reference.

  2. On the Code Reference page, select the row for the code reference that you want to delete.

  3. On the Code Reference Details page, click the Delete button.

Setting Up Code Reference Groups

A code reference group is a set of code references grouped together on the basis of the nature of violations. You set up code reference groups on the Code Reference Group page.

Adding Code Reference Groups

  1. Select Code Enforcement Setup > Code Reference Group.

  2. The Code Reference Group page lists all the code reference groups. Click Add to add a new group.

  3. On the Code Reference Group Details page, enter values for the code reference group.

    Page Element

    Description

    Code Reference Group ID

    Enter a unique identifier for the code reference group.

    Name

    Enter a name for the code reference group.

  4. Verify that the Enabled switch is turned on. The option is active by default for a new code reference group.

  5. In the Code References section, click Add to search and include one or more code references to the group. Use the Add and Delete action icons for adding and deleting code reference records.

  6. Click Save.

Modifying Code Reference Groups

You can modify code references groups on the Code Reference Group page.

  1. Select Code Enforcement Setup > Code Reference Group.

  2. On the Code Reference Group page, select the row for the code reference group that you want to modify.

  3. On the Code Reference Group Details page, you can:

    • Change the name of the group.

    • Use the Code References section to add new or delete existing code references.

    • Click the Enabled switch to enable or disable the code reference group.

  4. Click Save to save changes.

Deleting Code Reference Groups

You can delete code reference groups on the Code Reference Group page.

  1. Select Code Enforcement Setup > Code Reference Group.

  2. On the Code Reference Group page, select the row for the code reference group that you want to delete.

  3. On the Code Reference Group Details page, click the Delete button.

Setting Up Notices

A notice is a document issued by a code enforcement authority to the party that has violated a code. You set up code enforcement notices that are used to generate and send reports to the concerned responsible parties.

Adding Notices

  1. Select Code Enforcement Setup > Notice.

  2. The Notice page lists all the notices. Click Add to add a new notice.

  3. On the Notice Details page, enter values for the notice.

    Page Element

    Description

    Notice ID

    Enter a unique identifier of the notice.

    Name

    Enter a name for the notice.

    Report ID

    Select a report to be sent as part of the notice. This report is set up on the Report Configuration page.

  4. Verify that the Enabled switch is turned on. The option is active by default for a new notice.

  5. Click Save.

Modifying Notices

You can modify notices on the Notice page.

  1. Select Code Enforcement Setup > Notice.

  2. On the Notice page, select the row for the notice that you want to modify.

  3. On the Notice Details page, you can:

    • Change the notice name.

    • Select a new report ID.

    • Click the Enabled switch to enable or disable the notice.

  4. Click Save to save changes.

Deleting Notices

You can delete notices on the Notice page.

  1. Select Code Enforcement Setup > Notice.

  2. On the Notice page, select the row for the notice that you want to delete.

  3. On the Notice Details page, click the Delete button.

Setting Up Notice Groups

A notice group is a set of notices grouped together on the basis of the status of the case. The notices within a group follow a sequence that you configure, to send to the concerned parties as and when required.

Adding Notice Groups

  1. Select Code Enforcement Setup > Notice Group.

  2. The Notice Group page lists all the notice groups. Click Add to add a new notice group.

  3. On the Notice Group Details page, enter values for the notice group.

    Page Element

    Description

    Notice Group ID

    Enter a unique identifier of the notice group.

    Name

    Enter a name for the notice group.

    Enabled

    Verify that the Enabled switch is turned on. The option is active by default for a new notice group.

  4. In the Notice Associations section, you can configure the notices that are to be sent for a particular case status and in a particular sequence.

    Page Element

    Description

    Case Status

    Select a case status to associate with the new notice group.

    Sequence

    Select a value to determine the sequence of the selected notice within the hierarchy. For example, if the value 2 is selected, the selected notice will be the second notice for the selected case status.

    Notice ID

    Select a notice that is specific to the case status and the sequence value.

    Enabled

    Verify that the Enabled switch is turned on. The option is active by default for a new notice.

    Use the Add and Delete action icons for adding and deleting notice association records.

    Note: You must ensure that valid notices are configured for the case status before you associate a notice group with an issue subtype.Use ORA_VIO status to create a case.Use ORA_CIT status to issue a citation.

  5. In the Ad Hoc Notice Associations section, you can configure an ad hoc notice that the agency staff can manually add to a case.

    Page Element

    Description

    Notice ID

    Select a notice that is specific to the case.

    Enabled

    Verify that the Enabled switch is turned on. This switch is off by default.

    Use the Add and Delete action icons for adding and deleting ad hoc notice association records.

  6. Click Save to save your changes.

Modifying Notice Groups

You can modify notice groups on the Notice Group page.

  1. Select Code Enforcement Setup > Notice Group.

  2. On the Notice Group page, select the row for the notice group that you want to modify.

  3. On the Notice Group Details page, you can:

    • Change the name of the notice group.

    • Delete notice associations and create new ones.

    • Click the Enabled switch to enable or disable the notice group.

  4. Click Save to save changes.

Deleting Notice Groups

You can delete notice groups on the Notice Group page.

  1. Select Code Enforcement Setup > Notice Group.

  2. On the Notice Group page, select the row for the notice group that you want to delete.

  3. On the Notice Group Details page, click the Delete button.

Setting Up Inspection Counts

Define the number of inspections that are carried out to assess code violations reported at the agency. You use the Inspection Count page to set up the inspection count value and its description.

Adding Inspection Counts

  1. Select Code Enforcement Setup > Inspection Count.

  2. Click Add on the Inspection Count page to add a new inspection count.

  3. In the new row, enter the count value in the Inspection Count field and a description in the Description field.

    Note: The inspection count values must follow an incremental sequence of numbering, such as 1, 2, 3, and so on.

  4. Verify that the Enabled switch is turned on. The option is active by default for a new inspection count.

  5. Click Save.

Deleting Inspection Counts

  1. Select Code Enforcement Setup > Inspection Count.

  2. On the Inspection Count page, click the Delete icon for the row of the inspection count you want to delete.

    Note: You must ensure that the sequencing of numbers in the inspection count is maintained.

Setting Up Referral Bodies

Referral bodies are those departments that an agency can refer to in cases of code violations that are not in the scope of the agency. The agency can assign the issue to the referral body based on the referral type.

Adding Referral Bodies

  1. Select Code Enforcement Setup > Referral Body.

    The Referral Body page lists all the referral bodies that are configured by the agency.

  2. Click Add on the Referral Body page to add a new referral body and enter values for the following fields:

    Page Element

    Description

    Referral Code

    Enter an identifier of the referral body.

    Name

    Enter a name for the referral body.

    Description

    Enter a description about the referral body on the basis of which, an incident or case can be referred to the body.

    Referral Type

    Select the type of referral, which can be a department within the agency or an external agency:

    • Agency Department.

    • External Agency.

  3. Verify that the Enabled switch is turned on. The option is active by default for a new referral body.

  4. Click Save.

Modifying Referral Bodies

  1. Select Code Enforcement Setup > Referral Body.

  2. On the Referral Body page select the row for the corrective action that you want to modify.

  3. On the referral body details page, you can:

    • Change the name, description, and referral type values.

    • Click the Enabled switch to enable or disable the referral body.

      Note: You cannot delete a referral body.

  4. Click Save to save changes.

Setting Up Time Rules

Time rules are a set of policies that uses the input code enforcement inspection parameters – due date type, trigger date, priority, and occurrence to calculate due dates.

The following logic is used to calculate due date:

Due Date = Trigger date + Dates based on the time rule

If the number of transactions created exceed the policy count, then the time rule that is defined for the highest policy occurrence will be triggered.

Time rules are assigned to the issue subtype of the incident, the values of which are sourced from the Code Enforcement Options page. See Setting Up Agency-Level Options for Code Enforcement.

Note: Important!: Agency administrators add and modify time rules and assign them to issue subtypes so that appropriate rules are applied for each subtype. Every issue subtype must have a time rule assigned for every system-defined due date type. See Setting Up Issue Subtypes. The following table shows the various delivered due date types and their details.

Due Date Type

Description

Events that calculate the due date

Trigger Date

Usage

Policy Occurrence Count value

ORA_INC_REV_DUEDT

Incident review date

Incident creation

Incident report date

The incident in the worklist is marked with a status of Overdue when the calculated review due date is less than the current date.

1

ORA_INIT_INS_DUEDT

Initial inspection date

Initial inspection creation

Inspection schedule date

The Inspection due date is updated with this date when the initial inspection is scheduled.

1

ORA_RE_INS_DUEDT

Re-inspection date

Re-inspection creation

Inspection schedule date

The Inspection due date is updated with this date when the re-inspection is scheduled.

2 or more

ORA_VIOL_CMPL_PRD_DUEDT

Due date for compliance

Case creation

Case creation date

The date is displayed as the compliance date on the Case page.

The value for the policy occurrence count is zero (0) at the time of case creation.

0

ORA_VIOL_APPL_PRD_DUEDT

Violation appeal period

Case status change to Violation.

Case creation date

Ensures that the Request Appeal option is available only during the calculated appeal period.

1 or more

ORA_CITATN_CMPL_PRD_DUEDT

Due date for citation compliance

Citation issuance

Citation issue date

Updates the compliance date displayed on the Case detail page.

1 or more

ORA_CITATN_DUEDT

Due date for citation payment

Payment initiation

Citation issue date

Late fee is added after the citation payment due date.

1 or more

ORA_CITATN_APPL_PRD_DUEDT

Citation appeal period

Case status change to Citation.

Citation Issue Date

Ensures that the Request Appeal option is available only during the calculated appeal period.

1 or more

ORA_ABTMT_DUEDT

Abatement of violation due date

At present this due date type is not active.

Adding Time Rules

You configure the time rules and policies using the Time Rule page.

  1. Select Code Enforcement Setup > Time Rule. The Time Rule page lists all the time rules that are configured by the agency.

  2. Click Add on the Time Rule page to add a new time rule.

  3. On the Time Rule Detail page, add values to the following fields:

    Page Element

    Description

    Time Rule

    Enter a name for the time rule.

    Description

    Enter a description about the time rule.

    Due Date Type

    Select the type of due date, which determines the time period or due date for a transaction.

  4. Verify that the Enabled switch is turned on. The option is active by default for a new time rule.

  5. In the Time Policy section, click the Add button to define a time policy.

  6. On the Time Policy Details page, select values for the time policy:

    Page Element

    Description

    Priority

    Select the priority for the time policy:

    • High

    • Normal

    Unit of Measure

    Select a unit for the measurement of time:

    • Hours

    • Days

    Note: The Hours option is not supported at present.

    Unit of Measure Value

    Select a number value for the unit of measure of time you selected above.

    Policy Occurrence Count

    Select an occurrence count value for the event, such as an inspection.

Modifying Time Rules

  1. Select Code Enforcement Setup > Time Rule.

  2. Select the time rule row you want to modify.

  3. On the Time Rule Detail page you can change the time rule description, due date type, and the time policy.

  4. Click the Enabled switch to enable or disable the time rule.

  5. Click Save to save changes.

Deleting Time Rules

  1. Select Code Enforcement Setup > Time Rule.

  2. Select the time rule row you want to delete.

  3. On the Time Rule Detail page, click the Delete button.

Modifying Time Policies

  1. Select Code Enforcement Setup > Time Rule.

  2. On the Time Rule page, select the time policy row to open the Time Policy Detail page. You can change values for priority, unit of measure, unit of measure value, and policy occurrence count.

  3. Click Save to save any changes.

Deleting Time Policies

  1. Select Code Enforcement Setup > Time Rule.

  2. On the Time Rule page, select the time rule row for which you want to change the time policy.

  3. On the Time Rule Detail page, click the time policy row to open the Time Policy Detail page.

  4. Click the Delete button.

  5. To delete multiple time policies from the Time Rule Detail page, click the Edit button in the Time Policy section and select the check boxes for the rows you want to delete.

  6. Click Delete.

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 setting in the Intake Form section.

    Page Element

    Description

    Contact Information Required

    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.

  6. Configure settings in the Issues section.

    Page Element

    Description

    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.

    Schedule ID

    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.

  7. 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.

  8. 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.

  9. 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.
    Note: For more information, see Setting Up Autonumbering.These fields are required if the Code Enforcement offering is enabled for your agency.

  10. Use the Agency Features section to optionally enable the Guest Users Can Report Incidents feature.

    Use these fields in the Agency Features grid to enable or disable specific code enforcement features:

    Page Element

    Description

    Feature Code

    Enter the code for the feature to be enabled. The only available feature code is 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.

    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.

  11. 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.

  12. 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.

  13. 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.

  14. Click Save, then close the window.

Setting Up Issue Types

Issue types are broad categories that are used to report code enforcement issues.

Adding an Issue Type

To create a new issue type:

  1. Select Code Enforcement Setup > Issue Type.

  2. On the Issue Type page, click Add.
  3. On the Issue Type Details page, enter the following general information about the issue type:

    Page Element

    Description

    Issue Type ID

    Enter a unique alphanumeric code for the issue subtype. Do not use special characters, including symbols or punctuation, or spaces.

    Issue Type

    Enter a short name for the issue type.

    Valid From Date

    Enter the first date that the issue type is available for issue reporting.

    Valid To Date

    Enter the last date that the issue type is available for issue reporting. The default value is Open, indicating that the issue type will remain available indefinitely.

    Status

    Select Active or Inactive.

    Inactive issue types are not available for issue reporting. They also are not available to add to an issue subtype definition.

    Icon

    Select an icon for the tile that public users click when reporting this type of issue .

    Description

    Enter a description of the issue type. This description appears on the back of the tile that users click when reporting this type of issue.

  4. Click Save.

    When the issue is saved, three additional sections appear: Issue Subtypes, Code Reference Group, and Time-Based Rules.

    You don’t need to enter information in the Issue Subtypes section. The relationship between issue types and issue subtypes is established when you set up the issue subtype. After you create the related subtypes, you can return to the Issue Type Details page to view a complete list of subtypes for the issue type.

  5. Configure the list in the Code Reference Group section.

    1. Expand the section and review your agency’s default values, if any.

      The default values come from the Code Enforcement Options page. For more information, see Setting Up Agency-Level Options for Code Enforcement.

      If your agency does not have default code reference groups, a blank row appears.

    2. For each code reference group, review or enter the following settings:

      Page Element

      Definition

      Group ID

      Select a code reference group that will be added by default to all newly created issue subtypes.

      Enabled

      Turn this switch on to have the code reference group added by default to new issue subtypes for this issue type.

      If the switch is off, the code group is not added to new issue subtypes for this issue type.

    3. To add additional code reference groups to this issue type, click the Add icon and enter information in the new row.

    4. To remove code reference groups from the issue type, click the Delete icon.

  6. Configure the list in the Time-Based Rules section:

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

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

    To set up time rules for the issue type:

    1. Expand the section and review your agency’s default values.

      These default values also come from the Code Enforcement Options page.

    2. For each rule, review or enter the following settings:

      Page Element

      Definition

      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 from the trigger date until the due date.

      Time rules IDs are available for selection if they have the specified due date type and they are enabled.

  7. Click Save again if you made any changes in the sections for code reference groups and time-based rules.

Viewing or Modifying an Issue Type

To view or modify an issue type:

  1. Select Code Enforcement Setup > Issue Type.

  2. Click the row for the issue type you want to view or modify.

    The Issue Type Detail page appears. Because the issue type has already been saved, the page displays all fields, including the sections for Issue Subtype Details, Code Reference Group, and Time-Based Rules.

  3. Make any necessary updates.

  4. Click Save if you made any updates.

Inactivating an Issue Type

You cannot delete issue types, but you can make them unavailable for use by changing the status to Inactive.

To inactivate an issue type:

  1. Select Code Enforcement Setup > Issue Type.

  2. Click the row for the issue type you want to modify.

    The Issue Type Detail page appears.

  3. Change the Status to Inactive.

  4. Click Save.

Setting Up Issue Subtypes

Code enforcement issue subtypes are the lowest level of categorization for code enforcement issues. When you set up an issue subtype, you also create the intake form and define processing rules for issues that are reported under this subtype.

Adding an Issue Subtype

To create a new issue subtype:

  1. Select Code Enforcement Setup > Issue Subtype.

  2. On the Issue Subtype page, click Add.

  3. On the Issue Subtype Details page, enter the following general information about the issue subtype:

    Page Element

    Description

    Issue Subtype ID

    Enter a unique alphanumeric code for the issue subtype. Do not use special characters, including symbols or punctuation, or spaces.

    Issue Subtype

    Enter a short name for the issue subtype.

    Issue Type ID

    Select the issue type that represents the broad category under which this issue subtype falls.

    Only active issue types are available for selection. If an issue type is later inactivated, the issue type and all of its associated issue subtypes become unavailable to public users.

    Status

    Select from the following to indicate the issue subtype status:

    • Preliminary: The issue subtype is being defined but is not available for use.

    • Ready: The issue subtype is ready for testing or production use, depending on the environment.

    • Void: The issue subtype is no longer available.

    Note: The issue subtype can be set to ready regardless of whether the intake form is in published status or draft status. A form in draft status can be accessed for testing purposes in the development or test environment.

    Valid From Date

    Enter the first date that the issue subtype is available.

    Valid To Date

    Enter the last date that the issue subtype is available. The default value is Open, indicating that the issue subtype will remain available indefinitely.

    Public User Enabled

    Select from the following to indicate which types of users can access the intake form outside of the form designer:

    • Enabled for all users: Both registered public users and agency users can access the intake form.

    • Enabled for registered users: Both 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.

    For more information, see Publishing Intake Forms.

    Case Autonumber Rule

    Select the autonumbering rule to increment numbers for cases based on this issue subtype.

    For information, see Setting Up Autonumbering.

    Incident Autonumber Rule

    Select the autonumbering rule to increment numbers for incidents based on this issue subtype.

    Fee Schedule

    Select the fee schedule to use for citations based on this issue subtype.

    For more information, see Creating Decision Models for Fees.

    Notice Group ID

    Select the notice group to use when generating notices for a case based on this issue subtype.

    For more information see Setting Up Notice Groups.

    District Type

    Select the code enforcement district type to be used for incidents with this issue subtype.

    For example, if issues with this subtype are handled by the fire department and inspected based on fire prevention districts, then the district type might be your fire prevention district type.

    Icon
    Select an icon for the tile that public users click when reporting issues with this subtype.

    Description

    Enter a description of the issue subtype. This description appears on the back of the tile that users click when reporting issues with this subtype.

  4. Click Save.

    When the issue is saved:

    • The Design Form button is activated and the Form Status appears at the top of the page.

    • The Code Reference Group and Time-Based Rules sections appear.

  5. Review the read-only Form Status, which indicates whether the intake form is published or in development.

    These are the status values for the intake form:

    • Draft: The form design is incomplete. 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.

  6. Configure the list in the Code Reference Group section.

    1. Expand the section and review the default values, if any.

      The default values come from the associated issue type. For more information, see Setting Up Issue Types.

      If your agency does not have default code reference groups, a blank row appears.

    2. For each code reference group, review or enter the following settings:

      Page Element

      Definition

      Group ID

      Select the code reference group with the code references to be included by default in notices of violation that are based on this issue subtype. The person who generates the notice can remove specific code references from the notice.

      Enabled

      Turn this switch on to make the code reference group available for issues with this subtype.

    3. To add additional code reference groups to this issue subtype, click the Add icon and enter information in the new row.

    4. To remove code reference groups from the issue subtype, click the Delete icon.

  7. Configure the list in the Time-Based Rules section.

    This section displays rows for all of the due date types that are defined in the issue type. 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.

    To set up time rules for the issue subtype:

    1. Expand the section and review the default values.

      The default values come from the issue type that you entered when creating the subtype. Changing the issue type does not update these values.

    2. For each rule, review or enter the following settings:

      Page Element

      Definition

      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.

  8. Click Save if you made any changes in the sections for code reference groups and time-based rules.

  9. Create the issue intake form for this issue subtype.

    Note: Oracle provides a template for code enforcement intake forms. Even if you plan to use the delivered form as-is, you still need to go through the process of creating the form based on the delivered template.

    1. Click the Design Form button.

    2. Review the default issue intake form and add any user-defined fields to the drop zone on the Just a Few More Questions page tab.

    3. Save the form, and when you’re done designing the form, publish it.

    For detailed instructions on creating the issue intake form, see Using the Intake Form Designer for Code Enforcement.

  10. To make the issue subtype available to end users:

    1. Return to the Issue Subtype Detail page.

    2. Confirm that the Public User Enabled field is either Enabled for all users or Enabled for registered users.

    3. Change the Status to Ready.

    4. Click Save.

Modifying an Issue Subtype

To modify an issue subtype:

  1. Select Code Enforcement Setup > Issue Subtype.

  2. Click the row for the issue subtype you want to modify.

    The Issue Subtype Detail page appears. Because the issue subtype has already been saved, the page displays all fields, including the sections for Code Reference Group and Time-Based Rules.

  3. Make any necessary updates to the issue subtype.

  4. Click Save.

  5. Use the Design Form button to access the form designer if you need to make changes to the intake form.

Deactivating an Issue Subtype

You cannot delete issue subtypes, but you can mark them as void.

To deactivate an issue subtype:

  1. Select Code Enforcement Setup > Issue Subtype.

  2. Click the row for the issue subtype you want to modify.

    The Issue Subtype Detail page appears.

  3. Change the Status to Void.

  4. Click Save.

Cloning Issue Subtypes

Note:

To clone an issue subtype:

  1. Select Code Enforcement Setup > Issue Subtype.

  2. Click the row for the issue subtype you want to clone.

  3. On the Issue Subtype Detail page, click the Clone button.

  4. On the Clone Issue Subtype page, review or enter the following information:

    Page Element

    Description

    Original Issue Subtype and Original Issue Subtype ID

    These fields display identifying information about the issue subtype that you’re cloning.

    New Issue Subtype and New Issue Subtype ID

    Enter a new identifier and short description for the issue subtype that you’re creating.

    Clone Code Reference Groups

    When this switch is on, the code reference groups in the original issue subtype are copied over to the newly created issue subtype.

    When this switch is off, the new issue subtype will have the default code reference groups from the issue type.

    Clone Time-Based Rules

    When this switch is on, the time-based rules in the original issue subtype are copied over to the newly created issue subtype.

    When this switch is off, the new issue subtype will have the default time–based rules from the issue type.

    Clone Form Design

    When this switch is on, the original issue subtype’s form design is copied to the new issue subtype.

    When the switch is off, the new issue subtype does not have an intake form until you design one.

  5. Click Create.

    A new issue subtype is created. The information on the Issue Subtype Details page is identical to the cloned subtype, except that the Status is always Preliminary.

  6. Make any necessary modifications to the issue subtype and save.

  7. Make any necessary changes to the intake form (or create the form if you did not copy it from the original issue subtype).

  8. Publish the intake form.

  9. Make the subtype available to end users by updating the Status and, if necessary, the Public User Enabled setting.