Hi,
I want to add a validation that triggers when a specific text line code is added, the text shouldn’t be longer than 240 characters.
Unfortunately I am getting above error message. Any Idea how the syntax needs to be?
Many thanks in advance!
Best regards
Jacqui
Best answer by Saranga Amaraweera
Hi
LEN() is not a valid expression function in FSM even though it’s in SQL. You can simply create a custom view for this to check whether the task_text.text length is less than or greater than the given character length with SQL LEN function (having a boolean result column in the same view). Then create custom metadata for the same view and join that view on the task_text table with a new join relationship so that you can easily have the view’s result column as a BR rule input. Finally, you can call the validation directly from that.
+12Hi
As per my understanding you cannot use LEN() function in the business rule. In the BusinessRules document following are the functions which can be used in the business rules.
If you want to restrict the number of character you have to change the metadata. Following is a thread which says the steps to configure the metadata.
Hope this answer helps.
Best Regards,
Atheeq
+22Hi
LEN() is not a valid expression function in FSM even though it’s in SQL. You can simply create a custom view for this to check whether the task_text.text length is less than or greater than the given character length with SQL LEN function (having a boolean result column in the same view). Then create custom metadata for the same view and join that view on the task_text table with a new join relationship so that you can easily have the view’s result column as a BR rule input. Finally, you can call the validation directly from that.
+22Adding more inputs, this can be done with a custom client script validation as well.
Hello,
Could anyone guide me on how to use the following regular expression inside a Validation Business Rule in IFS FSM?
^[A-Z0-9]+$ My goal is to validate product.serial_id so that it only allows uppercase alphanumeric characters (A–Z, 0–9). No symbols, spaces, or dashes should be permitted.
While I’m aware that we could use custom client scripts for this, those only validate on the UI level. I need this validation to occur at both the UI and database levels.
Any suggestions or examples would be greatly appreciated.
Thank you.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.