Discovered the issue.
The CF Validation string is saved as attribute within the CF
creation/modification. The CF’s Validation string showed the old
version of that regexp.
Thus once the CFValidation string is changed, the CF itself (using
this validation string needs) to be assigned with the new string using
the Admin/CF/Modify interface.
Peter ViskupOn Mon, Jun 13, 2016 at 11:13 AM, Peter Viskup email@example.com wrote:
just extended the CFValidations in
Unfortunately the CF input still does not accept string “8.15-1” and
report “Broken in: Input must match [Optional Version]”.
The Mason cache was cleaned prior the ticket creation.
Am I doing something wrong?