03/27/2023 12:20 AM
We are using below regex on a service account endpoint and it is working fine, but the error shown to the end users is very technical and not user friendly.
Is there a way to customize the error message that is shown to the user on invalid regex?
Service account form:
The error shown to the end user:
Solved! Go to Solution.
03/27/2023 01:07 AM
Please try updating the label in :
Admin -> Settings -> User Interface Branding Configuration -> Manage labels
03/27/2023 01:47 AM
The issue we have is that we have multiple service account applications and with this approach it will change the message for all apps, but we have different regex rules for each application.
Is it possible to have this error message configured differently for each application?
03/27/2023 03:22 AM
This configuration is globally available and cannot be added specifically for each application.
03/27/2023 10:24 AM
You can add a simple message in Dynamic attribute for each endpoint about what the requirement of Regex look like since the error message is generic about regex failed.
Like the one you already have for approval, you can say the account name should be alpha numeric and between 3 - 20 character etc.
03/27/2023 10:46 AM
We do have such guidelines written as text on our PROD form, see example below:
But there are certain UI and UX issues here, first one being that the instructions regarding the "Account Name" field are written after the actual field. Most requesters tend to read and fill the form in order as they go along. Often they try to fill the account name field first, without having read the entire form first in detail. The error message pops up as soon as they leave the field (click out of it, or onto some other field) and here they see a issue too technical which they may not understand. Unfortunately we can not put any instructions above the account name field.
Anyways using Rakesh's solution, I guess we can put a more generic message in the popup that will work across all forms and will make more sense to the end users, something like below:
This will work for all service account applications and will encourage users to read the form first.
And yes apparently there are users who have infact tried putting an account name more than 20 characters long, which is something that I will never understand why. Most users complain about having a password policy requiring more than 8 characters long passwords so I really do wonder how they plan on remembering the 20+ character account name 🙂
Anyways I digress.
03/27/2023 10:57 AM
Yes. this should be better than a generic failed regex message. May be list down all regex conditions in simple statements in DA.