# The Match attribute

### Match=

The \<TypeData> XML element in the file is parsed, starting from the top. If there is a match, the search stops, so it is important to enter the child \<Type> element 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 supports several values for the Match attribute. These values can determine the type of download as follows:

#### Equals

When the Match attribute is set to a value of "Equals", entries attempt to exactly match the title of a BITS/DO download. The comparison string to be matched against is the content of the \<Type> XML element and is contained between the opening and closing XML tags (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 assign the Match attribute a value of "Contains" to obtain a match.

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

In this example, if the Job title includes the comparison string contained between the opening and closing XML tags (within the > < which in the case above is “Microsoft Outlook Offline Address Book”) a match will be made.

#### StartsWith

The "StartsWith" value checks if the display name of the job begins with the defined comparison string.

```
<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 \<Type> XML element rules correctly.


---

# Agent Instructions: 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/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.