---
title: Example: Highlighting Certain Incidents in a List
slug: neurons-for-itsm/admin-user-help/enu/latest/example-highlighting-certain-incidents-in-a-list
createdAt: 2026-07-14T19:16:29.028Z
---

This example explains how to highlight incidents in a list where the incident or a child business object has been modified by someone who is not the owner. This lets the owner quickly see where there is something they need to review.

This procedure involves several steps:

- [Creating a Quick Action for the Incident Business Object](docId\:s-s7UjcYgNneGT7EByT3s)
- [Creating the Triggered Action Business Rule on the Child Business Objects](docId\:s-s7UjcYgNneGT7EByT3s)
- [Creating a Formatting Style](docId\:s-s7UjcYgNneGT7EByT3s)
- [Creating the List Formatting Rule](docId\:s-s7UjcYgNneGT7EByT3s)

## Creating a Quick Action for the Incident Business Object

This example creates a quick action on the incident business object to update the appropriate fields (such as **LastModBy** and optionally **LastModDateTime**). See Creating a New Quick Action with [Creating a New Quick Action](docId:2Wq6ihUN2zxiR21eA3M7g) or [Using the Classic Action Designer (CAD)](docId:6UzT0q86Wu3yk3cxZJoAr).

1. Log in to Neurons for ITSM.
2. Open the **Incident** workspace.
3. From the Action Menu, choose **Edit Actions**. The application displays the Quick Action Editor.
4. Under **Create New Actions**, click **Update Object**.
5. Enter information into the fields.

| Field                    | Description                                          |
| ------------------------ | ---------------------------------------------------- |
| Enter action name        | Force Update LastModX                                |
| Enter action description | Quick action for highlighting incidents.             |
| Enter category           | Assign a category as needed.                         |
| Field Name               | From the drop-down list, select **LastModBy**.       |
| Field Value              | Enter **$(CurrentUserDisplayName())**.               |
| Field Name               | From the drop-down list, select **LastModDateTime**. |
| Field Value              | Enter **$(CurrentDateTime())**.                      |

:::hint{type="info"}
To add additional field names and values, click the **add** :inlineImage[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/-xC2rFf08JbJHTGUTd_A3_addgreen.png" alt caption size="10" width="17" height="15"} icon.
:::

6. Click **Save**.

:::Paragraph{indent="1"}
*Update LastModX Quick Action*
:::

::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/DbtIQW_4qQOUOgIcYsAtM_grid-quick-action.png" position="flex-start" size="40" initialPath="../../Resources/Images/help-images/grid quick action.png" githubPath="Content/Resources/Images/help-images/grid quick action.png" showCaption="false" width="858" height="499" darkWidth="858" darkHeight="499" indent="1"}

7. Close the Quick Action Editor and test the quick action.

## Creating the Triggered Action Business Rule on the Child Business Objects

This procedure describes how to create business rules on each of the child business objects to run the quick action on an incident when a record is created or updated.

1. From the Configuration Console, click **Build > Business Objects** to open the **Business Objects** workspace.
2. Open the business object called **Task.Assignment**.
3. Click the **Business Rules** tab.
4. Expand the **Triggered Actions** header and click **Add Trigger**.
5. Enter a unique name for the triggered action business rule, such as **IncidentTAForceUpdateLastModX**.
6. Choose events (for example, On Initialize, On Insert, On Update), add any applicable values, and click **Next**.
7. Select **Configure new action** and select **Run for Child** from the drop-down list.
8. Click **Next**.
9. In the **Child object and relationship** field, select **IncidentAssocTaskAssignment**.
10. In the **Action to run** field, select the quick action that you created previously, such as **Force Update LastModX**.
11. Click **Save**.
12. Test the business rule in all use cases.
13. Repeat these steps for each child business object to affect the row highlighting.

## Creating a Formatting Style

1. From the Configuration Console, click **Build > User Interface Styles > Highlighter Styles** to open the **Highlighter Styles** workspace.
2. Click **Add new\...**. The application displays the **New Style** workspace.
3. Enter a name and description for the style.
4. Drag and drop any styles to format. For example, drag the **border-color** property onto the **Dynamic Style Definition** area, then from the **Value** drop-down list, select light yellow (#FFFF99).

:::Paragraph{indent="1"}
*Example Highlighter Styles*
:::

::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/Yjbxk3A2LGohZpn7zqG0N_grid-highlighter.png" position="flex-start" size="40" initialPath="../../Resources/Images/help-images/grid highlighter.png" githubPath="Content/Resources/Images/help-images/grid highlighter.png" showCaption="false" width="956" height="531" darkWidth="956" darkHeight="531" indent="1"}

5. Click **Save**.

## Creating the List Formatting Rule

1. From the Configuration Console, click **Build > Business Objects** to open the **Business Objects** workspace.
2. Open the **Incident** business object.
3. Click the **Layouts** tab. The application displays a list of layouts.
4. Select the layout to apply the format to, ensuring that it is related to the appropriate role. For example, select **IncidentLayout.ServiceDesk**.
5. Click **gridView** to open the form in the List View Editor.  
6. Click **Edit** (next to **Add New List**) to modify the list.

:::Paragraph{indent="1"}
*List View Editor*
:::

::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/mDW4qlxgVjBOYcMRc78mE_grid-view-edit.png" position="flex-start" size="40" initialPath="../../Resources/Images/help-images/grid view edit.png" githubPath="Content/Resources/Images/help-images/grid view edit.png" showCaption="false" width="780" height="472" darkWidth="780" darkHeight="472" indent="1"}

7. The application only applies styles to the columns that are defined in the list, so add any additional fields as columns to the list, if they are missing.

:::Paragraph{indent="1"}
For this example, we want to highlight the **LastModBy** and **LastModDateTime** fields, so ensure that both of these fields are displayed as column headers on the list.
:::

:::Paragraph{indent="1"}
*Adding the LastModBy Field to the List Layout*
:::

::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/v8YKXaTmsbwmfIxiWon91_layout-add-field.png" position="flex-start" size="40" initialPath="../../Resources/Images/help-images/layout add field.png" githubPath="Content/Resources/Images/help-images/layout add field.png" showCaption="false" width="935" height="424" darkWidth="935" darkHeight="424" indent="1"}

8. While the column is highlighted, on the right, from the Style field, select the new style that you created in [Creating a Formatting Style](docId\:s-s7UjcYgNneGT7EByT3s).
9. Click **Save**.
10. Test the rule in your **Incident** workspace.

:::Paragraph{indent="1"}
Whenever anyone modifies an incident or an affected child business object of the incident, the application updates the **LastModBy** field of the incident. If the value of the **LastModBy** field is not the same as the value of the **Owner** field, the application highlights it.
:::

:::Paragraph{indent="1"}
*List Highlight Results*
:::

::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/kEBsBAk5ucEHYJBxCtHQM_grid-highlight-results.png" position="flex-start" size="40" initialPath="../../Resources/Images/help-images/grid highlight results.png" githubPath="Content/Resources/Images/help-images/grid highlight results.png" showCaption="false" width="778" height="240" darkWidth="778" darkHeight="240" indent="1"}