4Managing Incidents

Reviewing Incident Lists

The code technician worklist and the main incident lists display summary information about the listed incidents.

Reviewing Incidents on the Code Technician Worklist

To review incident details on the code technician worklist:

1. From the agency springboard, click the Code Technician Worklist tile.

2. Access any tab or subtab that displays incidents.

3. Review the following summary information about incidents:

   Page Element	Description
   Incident	This column displays: The incident ID that is assigned based on the agency’s autonumbering rules. The incident type and subtype, separated by a hyphen. The incident status. Unclaimed incidents have a status of Reported.
   Location	Displays the incident address and the incident’s district type and district. If district information is missing, a warning icon appears in its place.
   Issue	Displays the incident description.
   Attachments	Click the attachments icon to open a window with an carousel-style viewer for attachments. Each attachment appears as a thumbnail of an image (for pictures or videos) or a generic file type icon (such as a PDF icon).
   Reported Date	Displays the date that the incident was created.
   Due By	Displays the date by which the review and processing must be complete. (Processing can be scheduling an inspection, marking the incident as a duplicate, or closing the incident.) If processing is already overdue, a warning icon appears next to the date. The due date is calculated based on your agency’s time rules and the date that the incident was submitted.

4. Optionally click the View More Details icon to access the incident details page.

   To return to the code technician worklist, click the Back icon in the banner.

   For more information about the Incident detail page, see Working With Incident Details.

Reviewing Incidents in the Main Incident List

To review incident details on the main incident list:

1. From the agency springboard, click the Incidents tile.

2. If automatic routing is on, choose which incidents to view.

   Page Element

   Description

   Show All Incidents

   This switch is visible to code enforcement technicians and supervisors when automatic routing is enabled. When the switch is off, these users see only their assigned incidents and other incidents in their area of responsibility, as determined by the issue types and subtype attributes for their job function. When the switch is on, the users can see all incidents, regardless of their area of responsibility.

3. Review the following summary information about incidents:

   Page Element	Description
   Incident ID	This column displays: The incident ID that is assigned based on the agency’s autonumbering rules. The incident type and subtype, separated by a hyphen. The incident status. Unclaimed incidents have a status of Reported. The date the incident was reported.
   Location	Displays the incident address and the incident’s district type and district. If district information is missing, a warning icon appears in its place.
   Description	Displays the incident description.
   Assigned	Identifies the code enforcement technician and the code enforcement officer, if any, who are assigned to this incident.
   Reported Date	Displays the date that the incident was created.
   Attachments	Click the attachments icon to open a window with an carousel-style viewer for attachments. Each attachment appears as a thumbnail of an image (for pictures or videos) or a generic file type icon (such as a PDF icon).
   Actions	Displays the three-dot actions menu. This menu is not present for closed incidents. For information about the actions in the menu, see Processing Incidents.

4. Optionally click the View More Details icon to access the incident details page.

   To return to the code technician worklist, click the Back icon in the banner.

   For more information about the Incident detail page, see Working With Incident Details.

Claiming and Assigning Incidents

When an issue is reported, an incident is created. Code enforcement supervisors can assign incidents to code enforcement technicians, and technicians can claim incidents. The technician who claims an incident or is assigned to it becomes responsible for managing the incident.

The procedures in this topic describe how to assign or claim incidents from the code technician worklist. The same actions are available from the Incident Details page. For more information about the code technician worklist, see Using the Code Technician Worklist. For more information about the Incident Details page, see Working With Incident Details.

Overview of Automatic Routing

If you enable automatic incident routing on the Code Enforcement Options page, then incidents are routed to technicians who are responsible for specific issue types and subtypes.

Define a technician’s areas of responsibility using the Issue Type and Issue Subtype attributes for the Code Enforcement Technician and Code Enforcement Supervisor job functions:

• Assign a user to an issue type to make the user responsible for all related subtypes

• Assign an issue to a subtype when the user is not responsible for all of the subtypes that belong to the related issue type.

• To give a user responsibility for all types of issues, create an Issue Type attribute row, but leave the attribute value blank.

Note: If you don’t set up any issue type or subtype attributes, and you activate the system-level setting for automatically routing incidents, incidents will never be routed to the user.

When automatic routing is active, the Incoming Incidents tab on the code technician worklists shows only the incidents in the user’s area of responsibility. Additionally, technicians can only reassign incidents to technicians who have the appropriate area of responsibility.

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, and they don’t appear on the Incoming Incidents tab unless the technician releases the incident.

Code enforcement supervisors can assign or reassign incidents to any technician. During this process, the list of available technicians is initially limited to those with the appropriate area of responsibility, but the supervisor can select a check box to open up the list to all technicians.

When automatic routing is active, incidents can only be updated by these users:

• Users with responsibility for the incident’s issue type or subtype

• Users who are assigned to the incident, regardless of the user’s areas of responsibility.

• Supervisors and super users such as a system administrator.

See Setting Up Agency-Level Options for Code Enforcement and Setting Up Agency Staff.

Claiming an Incident

Claiming is the action that code enforcement technicians take to assign incidents to themselves. Code enforcement supervisors who are also code technicians have to use the Assign action rather than the Claim action to assign issues to themselves.

To claim an incident:

1. From the agency springboard, click the Code Technician Worklist tile.

   The Incoming Incidents tab appears by default. The incidents that appear on the list depend on whether you use automatic routing:

   • If automatic routing is off, this tab displays all unclaimed incidents.

   • If automatic routing is on, this tab displays incidents with types and subtypes in the current user’s areas of responsibility.

2. Optionally select the Overdue or Priority subtab to filter the list of incoming incidents.

   To return from a subtab to the main Incoming Incidents tab, click the Back to Incoming Incidents icon next to the Search icon.

3. Click the Claim button to claim an incident.

   Claiming an incident makes you the assigned technician. As the assigned technician, you are now responsible for processing the incident.

Assigning an Incident

Code enforcement supervisors assign incidents to code enforcement technicians. Supervisors who also have the technician job function use the Assign action rather than the Claim action to assign issues to themselves.

To assign an incident:

1. From the agency springboard, click the Code Technician Worklist tile.

   The Incoming Incidents tab appears by default. The incidents that appear on the list depend on whether you use automatic routing:

   • If automatic routing is off, this tab displays all unclaimed incidents.

   • If automatic routing is on, this tab displays incidents with types and subtypes in the current user’s areas of responsibility.

2. Optionally select a subtab to further filter the list of incoming incidents:

   To return from a subtab to the main Incoming Incidents tab, click the Back to Incoming Incidents icon next to the Search icon.

3. Click the Assign button.

   The Assign a Technician window opens.

4. Use these fields to review the list of technicians:

   Page Element	Description
   Show All Technicians	This check box appears only if automatic routing is on. Select the check box to list all code enforcement technicians, regardless of whether their job function attributes match the current incident’s issue type and subtype. If automatic routing is not enabled, this check box is hidden, and the technician list always includes all technicians.
   Name	Displays the names of available technicians.
   Incidents	Displays the number of open incidents that the code technician is currently assigned to.

5. Select a technician by clicking the row with the technician’s name.

6. Click Save.

   This assignment occurs immediately, and the incident disappears from the Incoming Incidents tab.

Processing Incidents

The code enforcement technician who claims an incident has various options for processing it: scheduling an inspection, marking it as a duplicate, reassigning it to another technician, releasing it back to the pool of unclaimed incidents, rerouting it by updating the issue type or subtype, or closing it.

The following actions are available for processing incidents:

• Schedule Inspection

• Mark as Duplicate

• Reassign

• Release

• Reroute Incident

• Close

Code enforcement technicians access these processing options from an Actions menu. This menu appears on the Incidents tab of the code technician worklist, which lists incidents where the current user is the assigned technician. It’s also available on the Overview section of the Incident detail page. See Working With Incident Details.

Note: The Incidents tab of the code technician worklist displays the same incident information as the other incident-related worklist tabs. For descriptions of these fields, see Reviewing and Claiming Incidents.

Accessing Incident Actions from the Worklist

To access the Actions menu for an incident in the code technician worklist:

1. From the agency springboard, click the Code Technician Worklist tile.

2. Select the Incidents tab to view incidents in Reported status where you are the assigned technician.

3. Optionally select a subtab to further filter the list of incoming incidents:

   • Click the Overdue tab to display incidents with a due date before the current date.

   • Click the Priority tab to display incidents with a priority setting of Yes.

   To return from a subtab to the main Incoming Incidents tab, click the Back to Incoming Incidents icon next to the Search icon.

4. Click the Actions icon for an incident.

   A drop-down list of actions appears.

Accessing Incident Actions from the Incident Details

The Actions button on the Overview section of Incident Details page is identical to the Actions button on the code technicianworklist. Click the button to see a drop-down menu of available actions.

You have two options for accessing incident details:

To access incident details via the code technician worklist:

1. Click the Code Technician Worklist tile on the agency springboard.

2. Access a tab that displays the incident you want to access, and locate the incident in the list.

3. Click the View More Details icon for the incident.

To access incident details via the Incidents list:

1. Click the Incident List tile on the agency springboard.

2. On the Incidents list page, locate the incident and click it.

Scheduling an Inspection When Autoassignment is Active

If the technician who reviews an incident determines that it is a valid incident, the next step is to schedule an inspection. If the code enforcement autoassignment option is active, the system does the work for you.

To schedule an inspection when autoassignment is active:

1. Access the Actions menu for an incident.

2. Select Schedule Inspection from the menu.

   The system schedule an inspection for the next available date. The inspection is assigned to a code enforcement officer who is associated with the incident’s district. A confirmation message tells you the inspection date and the assigned officer, and you are done.

Note: In some situations, autoassignment can’t be completed. For example, a system-level option sets the maximum number of inspections per day code enforcement officers, so there might not be any eligible officers available on or before the inspection due date. When autoassignment isn’t possible, the Schedule an Inspection page opens, and a message explains why the inspection couldn’t be scheduled automatically. In this scenario, simply use the Schedule an Inspection page to schedule the inspection manually. When you schedule the inspection manually, you can overbook an officer or set the inspection date past the due date.

Scheduling an Inspection Manually

To schedule an inspection manually:

1. Access the Actions menu for an incident.

2. Select Schedule Inspection from the menu.

   The Schedule an Inspection window opens.

3. Review the following read-only fields for contextual information:

   Page Element	Description
   Priority	Indicates whether the incident has been marked as a priority. The incident priority can affect the due date calculation.
   Due Date	Displays the date by which the inspection should be completed. The inspection due date is determined by the time-based rules for the associated issue subtype. These rules are based on the incident submission date and whether the incident is marked as a priority.
   District Type	Displays the incident’s district type, which is inherited from the issue subtype.
   District	Displays the incident’s district, which is based on the district type and the incident location. The default list of available code officers consists of the code officers who are assigned to this district.

4. Accept the default Inspection Date, or enter a new one.

   The default inspection date is normally the inspection due date. However, if you are scheduling the inspection manually because autoassignment couldn’t find an eligible officer before the due date, the default date is the next date that an officer is available without being overbooked.

5. Review any existing comments.

   Existing comments display the date and time the comment was created, the user ID of the person who added the comment, and the first 200 characters of the comment text. If any comments are truncated, click the comment to open a window that displays the entire comment. A comments search box is available if any comments exist.

6. Optionally add additional comments:

   1. Click Add Comment.

   2. In the Add Comment window, enter your comment in the rich text field.

      Alternatively, insert a copy of an existing comment by clicking Select Comments. For more information about working with comments, see Working with Comments.

   3. Click Save to close the Add Comment window and return to the Schedule an Inspection window.

      Even if you cancel the Schedule an Inspection action, the new comment remains.

7. Select an inspector from the list in the Assign section.

   The list displays the Name of each inspector who is available on the inspection date.

   The Inspection Count for an officer indicates how many inspections that person is already scheduled to perform on the specified date. A warning icon appears next to the count if choosing the officer would overbook the officer (based on your system setting for the maximum number of inspections per officer per day).

   If no inspectors are available, change the inspection date.

8. Click Save to schedule the inspection on the selected date with the selected inspector.

   The inspection is scheduled, and the incident status changes to Inspection.

   After you schedule an inspection, the incident no longer appears on the Incidents tab of the code technician worklist. You can still access the incident from the incident list and incident details pages. See Working With Incident Details.

Checking for Duplicates and Marking an Incident as a Duplicate

To check for duplicates and mark an incident as a duplicate:

1. Access the Actions menu for an incident.

2. Select Mark as Duplicate from the menu.

   The Check for Duplicate window opens. The Selected Incident section at the top of the window displays the incident ID, issue type, issue subtype, and address for the incident that you are marking as a duplicate.

3. Click the Cases and Incidents links to view initial lists of possible duplicates

   The search that is performed when you open the page shows active incidents and cases that match the issue subtype and location of the selected incident. Cases and incidents appear in separate lists that appear when you click the corresponding links.

   The search results show the case or incident ID, the issue type and subtype, the status, the address, and the reported date.

4. Optionally enter your own search criteria and click Search to look for other cases or incidents that the selected incident duplicates.

5. Select the check box for an incident or case that the selected incident duplicates.

6. Click Mark as Duplicate, then click OK in the confirmation message window.

   The original incident status changes to Closed with a reason of Duplicate. The related issue information is saved so that the Incident detail page for the newly marked duplicate shows which incident or case was duplicated.

   After you mark an incident as a duplicate, it no longer appears on the Incidents tab of the code technician worklist. You can still access the incident from the incident list and incident details pages. See Working With Incident Details.

Reassigning an Incident to Another Technician

Note: Reassigning an incident assigns the incident to a new technician, who is then responsible for reviewing and processing the incident. Reassigning does not assign the incident to a code enforcement officer who will perform an inspection. To assign an incident for inspection, use the Schedule an Inspection option.

To reassign an incident to another technician:

1. Access the Actions menu for an incident.

2. Select Reassign from the menu.

   The Reassign Technician window opens. The Technician Assigned field displays the name of the current assignee.

3. In the Select to Change area, use these fields to review the list of technicians:

   Page Element	Description
   Show All Technicians	This check box is available to supervisors (but not to technicians) when automatic routing is on. Supervisors can select the check box to list all code enforcement technicians, regardless of whether their job function attributes match the current incident’s issue type and subtype. If automatic routing is not enabled, this check box is hidden, and the technician list always includes all technicians.
   Name	Displays the names of available technicians.
   Incidents	Displays the number of open incidents that the code technician is currently assigned to.

4. Select a technician by clicking the row with the technician’s name.

5. Click the Save button.

   After you reassign an incident, only the newly assigned technician sees the incident on Incidents tab of the code technician worklist.

Releasing an Incident

Releasing an incident clears the Technician Assigned field. This sends the incident back to the Incoming Incidents tab on the code technician worklist so that another technician can claim it.

You can only release incidents in Reported status that are assigned to you—that is, where you are the assigned code enforcement technician. If the incident has moved past Reported status, you can still reassign it, but you can’t release it.

To release an incident:

1. Access the Actions menu for an incident.

2. Select Release from the menu.

   The Technician Assigned field is immediately cleared, and the change is saved.

Rerouting an Incident

Incidents are classified based on the issue type and subtype. If automatic routing is enabled, the issue type and subtype route incidents to code technicians with the proper area of responsibility.

The Reroute Incident action enables you to correct an incident’s issue type and subtype. The action is available regardless of whether automatic routing is enabled, but automatic routing ensures that the correctly classified incident is directed to the appropriate code technicians.

Rerouting an incident closes the original incident with a reason of Rerouted and creates a new incident.

When the new incident is created:

• Information from fields that are common to all incidents gets copied to the new incident.

  This includes the location, the description, whether the issue is a public safety risk, and the name and contact information (if any) from the original incident.

• Data in the original incident’s custom fields are not copied.

• You can review and edit the new incident information before submitting it.

  Use this option to add information in any custom fields for the new incident subtype.

• The agency user who reroutes the incident becomes the creator of the new incident.

  If a public user was signed in while creating the original incident, the user can see the incident using the Track Your Issues option. After rerouting, however, the new incident is not associated with the original public user account, and it’s not included in the user’s issue list. The public user can see that the original issue was closed, and the issue details provide the new issue number.

To reroute an incident:

1. Access the Actions menu for an incident.

2. Select Reroute Incident from the menu.

   The Reroute Incident window opens.

3. Enter the corrected Issue Type and Issue Subtype.

   You must change at least one value before you can continue.

4. Click Continue.

   The Review page appears.

5. Review the information for the new incident.

6. If you need to add or change information for the new incident:

   1. Click Edit on the review page to make the fields editable.

   2. Make your changes.

   3. Click Done to return to the review page.

7. Click Submit.

   The original incident is closed with the reason Rerouted, and a new incident is created. A confirmation message provides the ID of the new incident.

   If automatic routing is active, the new incident is routed to the appropriate code technicians. Otherwise, the new incident goes into the general pool of unassigned incidents.

Closing an Incident Manually

Sometimes an incident can be closed immediately, without first being inspected.

To close an incident:

1. Access the Actions menu for an incident.

2. Select Close from the menu.

   The Close Incident window opens.

3. In the Close Reason field, select one of the following reasons:

   Value	Description
   Compliance	No violation has occurred.
   Error	The incident was created in error.
   Referral	The incident has been referred to another department or agency.

   Note: Other close reasons, including Duplicate and Reroute, are assigned by the system during related processing.

4. Review any existing comments, and optionally add additional comments.

   To add new comments:

   1. Click Add Comment.

   2. In the Add Comment window, enter your comment in the rich text field.

      Alternatively, insert a copy of an existing comment by clicking Select Comments. For more information about working with comments, see Working with Comments.

   3. Click Save to close the Add Comment window and return to the Close Incident window.

      Even if you cancel the Close Incident action, the new comment remains.

5. Click Save.

   The incident status changes to Closed.

   After you close the incident, it no longer appears on the Incidents tab of the code technician worklist. You can still access the incident from the incident list and incident details pages. See Working With Incident Details.

Working With Incident Details

The Incident page includes sections for the incident overview, details, comments, attachments, and history. The page also displays a map with the incident location. Use this page to view and update incident information, to claim or assign the incident, and to perform the actions for processing the incident.

Accessing Incident Details

To access incident details from the code technician worklist:

1. Click the Code Technician Worklist tile on the agency springboard.

2. Access a tab that displays the incident you want to access, and locate the incident in the list.

3. Click the View More Details icon for the incident.

To access incident details from the Incidents list:

1. Click the Incident List tile on the agency springboard.

2. On the Incidents list page, locate the incident and click it.

Using the Incident Overview Tab

The Overview tab on the Incident page displays summary information, enables you to update assignments, and provides access to the same actions that you can perform from the code technician worklist.

To use the Overview tab:

1. Access the incident.

   The Incident page appears and displays the Overview tab by default. If you navigate away from this tab, return by clicking Overview in the left frame.

2. Review the incident Status and, if the incident is closed, review the closure Reason.

   The following table describes incidents statuses and reasons:

   Status	Description
   Reported	This incident has not been processed. The status does not indicate whether the incident has been claimed. The Claim action is available if no technician is assigned. After the incident is claimed, the actions for processing the incident become available.
   Inspection	An inspection has been scheduled, and the inspection results have not yet been recorded.
   Violation	The inspection resulted in a violation. When this happens, a case is created. The incident becomes read-only. When the case is closed, the incident status also changes to Closed.
   Closed	When in incident is closed, the Reason provides additional information: Compliance: No violation exists, or the violation has been corrected and the related case has been closed. Duplicate: The incident was closed as a duplicate of another incident or of a case. . Error: The incident was created in error, or its related case was closed with a status of Void. Referral: The incident (or it’s related case) was referred to another department or agency. Technicians who are assigned to incidents can use the Close action manually close the incident with any of these reasons except Duplicate. To close a case as a duplicate, the technician uses the Mark as Duplicate action.

3. Review information that is specific to how the incident has been processed:

   These fields are visible when relevant:

   Page Element	Description
   Case	If the incident was determined to be a violation, this field displays the ID of the case that was created. The ID is a link to the case.
   Related Incident or	If the incident was closed as a duplicate of another incident, this field displays the ID of the other incident. The ID is a link to the transaction.
   Related Case	If the incident was closed as a duplicate of a case, this field displays the ID of the case. The ID is a link to the case.
   Referral Type and Referral Code	If the incident was closed as a referral, these fields appear. The referral type indicates if the incident was referred to an Agency Department or to an External Agency. The referral code was selected at the time the incident was closed. For information about referral codes, see Setting Up Referral Bodies.
   Rerouted to Incident	If the incident was closed because it was rerouted (assigned a new issue type or subtype), this field displays the ID of the replacement incident. The ID is a link to the incident.
   Rerouted from Incident <incident ID>	If the incident was created as a result of rerouting another incident (by changing the issue type or subtype), this message appears next to the incident status. The incident ID is a link to the original incident.

4. Review the following general incident information:

   Page Element	Description
   Priority	Displays Yes or No to indicate whether the incident is a priority issue. The initial value corresponds to the how the person who reported the incident answered the question Does this issue pose a health hazard or public safety risk. If the incident has been claimed and it is in Reported status, the assigned technician can click the adjacent Edit link to change the incident priority.
   Issue Description	Displays a description of the problem that was reported. If the incident is in Reported status, the assigned technician can click the adjacent Edit link to open the Edit Description window and change the description. Even if the technician edits the description, the original issue description still appears on the Details tab.
   Service Request ID	Displays the identifier of the service request in the external application. This field appears only if the incident is submitted from an external system.
   Service Request Source	Displays the name of the external system from which the incident was submitted. This field appears only if the incident is submitted from an external system.
   Location	Displays the location of the incident. This can include an address and any additional location information that was provided. If the incident is in Reported status, the assigned technician can click the map marker icon next to the current location to open the Update Location window and select a new location. The technician can type the new location into the address search box or drag the map so that the location crosshairs are over the new location. When the technician closes the window, the new address replaces the old one on this page. The original address still appears on the Details tab.
   Reported Date	Displays the date that the incident was originally submitted.
   Review Due Date	Displays the due date for code technician to process the incident. Claiming an incident is not sufficient: the technician must close the incident or schedule an inspection. (The inspection does not have to be performed by the review due date—it has its own due date.) The review due date is calculated based on the issue subtype, the date the incident was reported, and the incident priority.

5. Review information about the incident district, and update the information if necessary.

   Page Element	Description
   District Type ID	Identifies the code enforcement district type for the incident. For example, incidents might be associated with a fire prevention district type. The district type is inherited from the issue subtype and is read-only. However, if the field is blank because the issue subtype doesn’t have a district type, you can manually select one. The field becomes read-only after you enter a value.
   District	Confirm or update the specific district where the incident is located. This district is based on the district type and the issue location: With GIS integration, the system finds the district using the GIS map layer that is associated with the district type.. If the agency doesn’t use GIS integration, the system looks for the code enforcement district that is associated with the parcel. If the system is unable to determine the district, you can manually enter one. The district determines the default code officers for the incident. For example, if an incident is in fire prevention district 2, then the code officers who are assigned to that district are listed when you schedule an inspection. Code officers are assigned to specific districts using the Code Enforcement Districts attribute of the Code Enforcement Officer job function. For more information about setting job function attributes, see Setting Up Agency Staff.

6. Review and, if necessary, update the incident assignments using these fields:

   Page Element	Description
   Technician Assigned	Identify the code enforcement technician who is responsible for the initial review and processing for the incident. You can update this field directly, or use the Reassign action in the Actions menu.
   Inspector Assigned	Identify the code enforcement officer who is responsible for an initial inspection. An inspector is assigned when the inspection is scheduled. This field is editable only if the incident is in Inspection status. When you change the assignment, the system does not check the new assignee’s workload. After you assign the new inspector, the assignment is also updated on the corresponding inspection record.

7. If an inspection has been scheduled, review the Inspection ID and Inspection Status fields.

   Click the inspection ID link to open the Inspection Detail page and view the details of the inspection. You view the assigned officer, the inspection outcome along with its reason, and the inspection related dates. The Comments and Attachments sections allow you to view the comments and attachments added by the inspector. You can add your own comments and attachments using the Add Comments button and the Add icon respectively.

8. Use the Actions menu to perform any of the following actions:

   Action	Description
   Schedule Inspection	Select the inspection date and the inspector for an incident.
   Mark as Duplicate	Identify another issue (an incident or a case) that this incident duplicates. Incidents that are marked as duplicates are closed, and the ID of the related transaction appears on the Overview tab.
   Reassign	Choose a new code enforcement technician. This action has the same result as directly editing the Technician Assigned field.
   Release	Clear the Technician Assigned field.
   Reroute Incident	Provide a new issue type and subtype for the incident. If automatic routing is enabled, the incident is routed based on the new values.
   Close	Close the incident and specify a reason for the closure.

   Note: These are the same actions that are available in the code technician worklist on the tabs where code enforcement technicians view their assigned incidents. For more information, see Processing Incidents.

Using the Incident Details Tab

The Detail tab on the Incident page displays read-only information from the original issue report.

Note: Because this tab displays the originally reported information, the values displayed here do not get updated when if agency staff updates the corresponding fields on the Overview tab.

To use the Details tab:

1. Access the incident.

2. Click Details in the left panel.

3. Review the following read-only information.

   Page Element	Description
   Address	Displays the original location of the incident.
   Additional Location Details	Displays any additional location information that was provided. This field appears only if there is any detail to show.
   Issue Description	Displays the original description of the problem that was reported.
   Does this issue pose a health hazard or public safety risk?	Displays Yes or No to indicate whether the issue was marked as a health hazard or public safety risk when it was originally reported. This value is also the initial value for the incident priority shown on the Overview tab.
   <User-defined fields>	Displays any user-defined fields from the intake form.
   Name, Email, and Phone	Displays contact information for the person who reported the incident. If your agency allows public users to hide their information when reporting an issue, these fields can be blank.

Working With Incident Comments

The Comments tab on the Incident page enables you to add comments using the same comments tool that you use for adding case comments. For detailed information on adding comments, see Working with Comments.

Viewing Incident Attachments

The Attachments tab lists the file attachments that were uploaded as part of the original incident report.

To view incident attachments:

1. Access the incident.

2. Click Attachments in the left panel.

3. Review information for the attachments in the list:

   Attachment information is not labeled, but it consists of the following:

   • A thumbnail showing an image (for pictures or videos) or a generic file type icon (such as a PDF icon).

   • File name

   • File size

   • File description, if one was entered when the file was uploaded.

   • Date and time that the attachment was uploaded.

4. To view additional details or update the description:

   1. Click the Actions icon for the row and select View Details from the menu.

   2. Review information in these fields: File Name, File Size, Uploaded By, and Uploaded On.

   3. Review and optionally modify the Description.

   4. Click Cancel or, if you updated the description, click Save

5. To download a local copy of the file, click the Actions icon for the row and select Download from the menu.

   The download process is based on your browser. If you’re not prompted for a file location, the file is saved to your downloads folder.

6. To remove the attachment from the incident, click the Actions icon for the row and select Delete from the menu.

Viewing Incident History

To view a history of an incident’s status change:

1. Access the incident.

2. Click History in the left panel.

3. Review the following status history information:

   Page Element	Description
   Status	Displays the new status after an incident status change.
   Updated By	Identifies the person who performed the action that updated the incident status.
   Updated Date	Displays the date that the status changed.
   Reason	Displays the reason, if any, that is associated with the status change. For example, if a code enforcement technician closes an incident without scheduling an inspection, this field displays the reason that the technician selected when closing the incident.