Property description
thresholds is an ordered list on the rules block of the date component. Each entry maps a driverValue to a limit, matched by exact comparison against the driver attribute’s current value.
A limit restricts how far in the future a date can be set, expressed as a number of days or years from today.
Minimal JSON
{
"thresholds": [
{
"driverValue": "",
"limit": {
"kind": "none"
}
}
]
}The following example limits a date attribute to 3 years in the future when a regulation flag is set to YES, or 6 years when set to NO.
{
"thresholds": [
{
"driverValue": "YES",
"limit": {
"kind": "years",
"value": 3
},
"errorTranslationKey": "effective_from.error.max_3y"
},
{
"driverValue": "NO",
"limit": {
"kind": "years",
"value": 6
},
"errorTranslationKey": "effective_from.error.max_6y"
}
]
}Nested properties
| Property | Description | Values | Mandatory |
|---|---|---|---|
driverValue | The driver attribute value that activates this threshold. Exact match. Type follows the driver attribute (string, boolean, or integer). | string / boolean / integer | Yes |
limit | The max-future-date limit when this threshold is active. See limit properties. | json | Yes |
errorTranslationKey | Translation key for the inline validation error shown when the date exceeds this limit. If omitted, a generic platform error is used. | string | No |
limit properties
| Property | Description | Values | Mandatory |
|---|---|---|---|
kind | The shape of the limit. See Supported kind values. | string | Yes |
value | Number of days or years the date can be in the future. Not used when kind is none. | integer | No |
Supported kind values
| Value | Description |
|---|---|
days | Date must be at most value days after today. |
none | No restriction — picker is open for any future date. When used as the fallback limit, no validation error is ever generated. |
years | Date must be at most value years after today. |