- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2020 05:31 AM
Hi,
This is something strange, You could approach to ServiceNow regarding this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2020 06:13 AM
I replicated this on my PDI and same thing exactly. So I don't think it's my instance. Although both are on Orlando version.
How would I approach ServiceNow? what are the channels?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2020 06:19 AM
Hi,
Above provided solution is also from Orlando.
To approach ServiceNow,
Create HI ticket.
https://hi.service-now.com/hisp
If it is ok for you can you share the PDI details on dhananjay.pawar1111@gmail.com I will check.
If possible share
Catalog item name and access details.
Thanks,
Dhananjay.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2021 01:56 PM
Dear All,
I had the same issue (I am on Paris).
I logged a ticket with ServiceNow and they confirmed it is a bug.
The regex works with the catalog item in the backend, but it doesn't work in the service portal.
They logged a problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-01-2021 03:46 AM
Feedback from support.
The PRB: PRB1460322 attached on the Case, has been reviewed by DEV team and they have closed it as "Working as Expected" for the following reason:
"The behavior: "Variable validation for Regex is not showing error in SP": is due to the form control input in Angular, which by default trims if the value contains any leading or trailing spaces as per the design of the Platform.
The only difference is it does not show any error."
