> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/stifler/2.10/configuration/stiflerulez.xml-2.x-definitions/the-match-typedata.md).

# The Match – TypeData

### Match=

Next the \<TypeData> section of the file is parsed, starting from the top. If there is a match, the search stops, so therefore it is important to enter the TypeData rules in the correct order. The rules need to identify a BITS Job by a certain attribute of that job, be it title, download URL or some other marker.

The XML file contains a number of ways to determine the type of download as follows:

#### Equals

These entries attempt to exactly match the title of a BITS/DO download. The comparison string in contained within the > <

```
<Type TypeID="215" Match="Equals" CCMDTSType="0">CCMDTS Job</Type>
```

In the example above, we know that all Microsoft ConfigMgr content downloads have a BITS job title of “CCMDTS Job”. More on ConfigMgr specifics later in this document.

#### Contains

If you only know part of the Job title you can use the ‘Contains’ verb to obtain a match.

```
<Type TypeID="109" Match="Contains">Microsoft Outlook Offline Address Book</Type>
```

This means that if the Job title includes the string contained within the > < (which in the case above is “Microsoft Outlook Offline Address Book”) a match will be made.

#### StartsWith

This checks if the display name of the job starts with the defined Value.

```
<Type TypeID="6" Match="StartsWith">Microsoft Outlook</Type>
```

The above rule would match “Microsoft Outlook Offline Address Book” but could also match “Microsoft Outlook Some other download” – which is why it is important to order your TypeID rules correctly.


---

# 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:

```
GET https://documentation.2pintsoftware.com/stifler/2.10/configuration/stiflerulez.xml-2.x-definitions/the-match-typedata.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.