> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/command-centre-client/examples-of-regular-expression-syntax.md).

# Examples of Regular Expression Syntax

The following table provides a number of regular expression examples that have been tested and can be used to validate text-type PDF data.

<table><thead><tr><th width="142">Category</th><th width="166">Regular Expression</th><th width="185"></th><th>Description</th></tr></thead><tbody><tr><td>Email Address</td><td colspan="2"><code>^[A-Za-z0-9._%+-]+@(?:[A-Za-z0-9-]+\.)+[A-Za-z]{2,4}$</code></td><td>Case insensitive, must include an @ symbol and optional email characters such as dots and dashes with maximum 4 characters in the generic top-level domain.</td></tr><tr><td>Phone Number<br>(example)</td><td colspan="2"><code>^0[1-9]\s\d{3,4}\s\d{4}$</code></td><td>Requires an STD prefix 01..09 followed by a compulsory space then seven or eight digits with a compulsory space separating the last four digits,<br>(e.g. 07 3482 7520 or 07 386 4902)</td></tr><tr><td>Phone Number, international format (example)</td><td colspan="2"><code>^[+]\d{7,18}$</code></td><td>Forces a '+' character at the start of the string followed by 7 to 18 integers (no spaces).</td></tr><tr><td>License Number/ID<br>(example)</td><td colspan="2"><code>^(?:CNS|BNE|TNS)\d{4,6}(?:-(?:[1-9]|1[0-5]))?$</code></td><td>Three upper case letters CNS, BNE, or TNS, immediately followed by 4-6 integers, optionally followed by a dash and an integer of 1-15, (e.g. CNS15425-13 or BNE928362).</td></tr><tr><td>Numeric ID (example)</td><td colspan="2"><code>^\d{4,8}$</code></td><td>Only integers but must consist of a minimum of 4 digits and a maximum of 8.</td></tr><tr><td>Car Registration (example)</td><td colspan="2"><code>^[A-Z]{3}\d{3}$</code></td><td>Three upper case letters immediately followed by three integers, (e.g. KMO512).</td></tr><tr><td>Single limited numeric value (example)</td><td colspan="2"><code>^[0-4]$</code></td><td>Numeric value 0, 1, 2, 3 or 4</td></tr><tr><td>Alpha characters only</td><td colspan="2"><code>^[A-Za-z]+$</code></td><td>Any uppercase or lowercase characters only, no spaces.</td></tr><tr><td rowspan="2">Upper case</td><td><code>^[A-Z]+$</code></td><td>(continuous string)</td><td rowspan="2">All upper case characters.</td></tr><tr><td><code>^(?:[A-Z]\s?)+$</code></td><td>(single spaces allowed, e.g. ASD BD GHJ)</td></tr><tr><td rowspan="2">Lower case</td><td><code>^[a-z]+$</code></td><td>(continuous string)</td><td rowspan="2">All lower case characters.</td></tr><tr><td><code>^(?:[a-z]\s?)+$</code></td><td>(single spaces allowed, e.g. rgag dhgdh afg)</td></tr><tr><td>Proper case</td><td colspan="2"><code>^(?:[A-Z]\w*\s?)+$</code></td><td>First Letter Of Each Word Must Be Upper Case.</td></tr><tr><td>Boolean</td><td colspan="2"><code>^[01]$</code></td><td>A simple on/off by using only the values 0 or 1.</td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/command-centre-client/examples-of-regular-expression-syntax.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
