> ## Documentation Index
> Fetch the complete documentation index at: https://docs.alumio.com/llms.txt
> Use this file to discover all available pages before exploring further.

# String: Matches wildcard pattern

> Checks that a string matches the supplied wildcard pattern.

export const FormField = ({property, label, required = false, diType, uiPatterns, children}) => {
  const patterns = Array.isArray(uiPatterns) ? uiPatterns : uiPatterns ? [uiPatterns] : [];
  return <div style={{
    margin: '1.5rem 0'
  }}>
      <div style={{
    display: 'flex',
    alignItems: 'baseline',
    flexWrap: 'wrap',
    gap: '0.5rem',
    marginBottom: '0.25rem'
  }}>
        <strong>{label}</strong>
        <span style={{
    fontSize: '0.7rem',
    fontWeight: 600,
    textTransform: 'uppercase',
    letterSpacing: '0.04em',
    color: required ? '#6241f5' : '#6b7280'
  }}>
          {required ? 'Required' : 'Optional'}
        </span>
      </div>

      <div>{children}</div>

      {diType || patterns.length > 0 ? <p style={{
    fontSize: '0.85rem',
    color: '#6b7280',
    marginBottom: 0
  }}>
          {diType ? <>
              See the <a href={`/references/${diType}`}>{diType}</a> reference.{' '}
            </> : null}
          {patterns.length > 0 ? <>
              Accepts a <a href={`/documentation/placeholders-and-patterns/patterns#${patterns[0]}`}>pattern</a>.
            </> : null}
        </p> : null}
    </div>;
};

Passes when the incoming text fits a wildcard pattern you supply. Use it to act only on values of a certain shape, for example product codes that start with `SKU-`, or file names that end in `.csv`.

A wildcard pattern uses two special characters: `*` stands for any run of characters, including none, and `?` stands for exactly one character. Everything else has to match literally, and the comparison is case-sensitive. So `SKU-*` covers `SKU-1001` and even a bare `SKU-`, while `image?.png` covers `image1.png` but not `image10.png`. Note that `sku-1001` would not match `SKU-*`, because the letters differ in case. This style of pattern is simpler than a full regular expression; reach for [String: Matches regular expression](/references/condition/string-regex) when you need finer control.

This documentation describes: [Schema](/schemas/condition/string-match)

## Fields

<FormField property="value" label="Value" required>
  The wildcard pattern the incoming text is checked against. The condition passes when the text fits the pattern and fails when it does not. Use `*` to stand for any run of characters and `?` for a single character. With a pattern of `SKU-*`, a code of `SKU-1001` passes while `PROD-5` fails.
</FormField>

## Sample data

With the pattern set to `SKU-*`, the condition checks whether a product code starts with `SKU-`.

| Field | Value   |
| ----- | ------- |
| Value | `SKU-*` |

| Value      | Result         |
| ---------- | -------------- |
| `SKU-1001` | Matches        |
| `PROD-5`   | Does not match |

```json Configuration theme={null}
{
  "prototype": "string-match",
  "parameters": {
    "value": "SKU-*"
  }
}
```
