> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/builder/builder-2021.1/service-matrix-screen/grouping-of-cases-in-a-service-line.md).

# Process Grouping Work Items

You can group work items in the Service Matrix by creating higher-level Process Groups into which you can nest multiple Cases/Tickets. 

{% embed url="<https://enate.cdn.spotlightr.com/watch/MTY5MDQ5OA==>" %}

In order to create a Process Group, go to the Service Lines screen and then in the Case or Ticket you want to add to the group, define the name of the Process group:

![](/files/-MWp0g9dfNDspYP2vdha)

When you switch over to the Service Matrix Screen, you will be able to see that your Cases and Tickets are now grouped. Clicking on a Process Group tab will reveal the Cases / Tickets within that Group.

![](/files/-M_QeDSmhXdv9FVD7d-O)

{% hint style="info" %}
Note that the 2 letter abbreviation for the group will come from the first two letters of the group name if the Process Group name is one word (e.g. International will be abbreviated to IN) or from the first letter of the first word and first letter or the last word if the group name is more than one word (e.g. HR International will be abbreviated to HI). &#x20;
{% endhint %}

A setting in General Setting lets you decide if you want to show or hide process group information in both Builder and Work Manager.

<figure><img src="/files/fKMflmlYgDRlnrQURQbl" alt=""><figcaption></figcaption></figure>

If the setting is off, all process group labels and fields will be hidden.

{% hint style="info" %}
Note that if a user tries to switch off the option after having added process group information, they will not be able to switch it off.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.enate.net/enate-help/builder/builder-2021.1/service-matrix-screen/grouping-of-cases-in-a-service-line.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.