This content has been marked as final. Show 4 replies
The regexp check is susposed to be when users are entering data via the UI only. I would strongly suggest that you not use this level of validation if the data is coming from Siebel (and it could possibly be invalid).1 person found this helpful
I would suggest that you use warning events in your rulebase to do these sort of checks.
Thanks for the reply. But How can i use a warning even to check whether a person has entered an valid email address or not or the person has entered a valid telephone number or not. The scenario I am speaking is of when the same form is used in OPA to create new records in Siebel as well as Siebel may contain migrated data In case Siebel has migrated data The data that has been migrated from older application may contain invalid value. also warning events have a major drawback as the error given by such events are allways at the top of the page it does not point out clearly due to which control error has occured. as in case of regex error is shown just above the control and the control is clearly spotted even if I user BeforeSubmitEventHandler to validate the date though I may be checking for one control I cannot raise an error for this control. as there is no association of control with raise error If there would have been some raise error function which would have accepted control as a input and showed this error against that control I am much happy to use what you stated.
Unfortunately, this is a limitation of the system. When you put input validation on an attribute that validation is invoked when those attributes are loaded from Siebel.
Thanks for reply the limitaion is not that system validates the data befor picking up from Siebel. That is a good thing we need to ensure we get proper data whenevr we try to launch form but the greatest limitation is that it does not provide the public name due to which form launch is failing even in the application logs. If it would have provided the public name atleast person could have gone and rectified the data to fit in regex criteria. I am here pointing out the limitation of logging not that Why application is checking data.
I am happy that application validates it but I am not happy that application does not tell me why it is failing.
However you can generate the reprt of attributes containing regex by copying properties file changing the extention to xml opening it in excel and using filter to see what attributes have regex after that you can make corresponding SQL queries to point out which column contains incorrect data and maybe you can ven clean it using SQL.
< telephone number removed by moderator >
(that's bad form - you'll get spam calls for all Eternity)