Siebel Knowledge

Recently I was working with a requirement where the field needs to be validated to accept only numeric values. This requirement looked to be a simple one. Adding a validation on the PreSetFieldValue of the Business Component solved the problem. Below is the code added ............................... ........... if(isNaN(FieldValue){            TheApplication().RaiseErrorText("Sorry, invalid number, please enter numbers alone."); } ....... Thats it.... Now when testing all looked fine until accidentally I entered 123123e. There was no error thrown and the value was accepted. How ever this is not what the code is suppose to be doing. So thought of getting in deeper, tested with 88779e no error thrown, then with 2341209d error thrown. So "e" at the end was the killer. Some how a number ending with e is considered as a infinite number (not sure if I am correct). As an alternative and get rid of this scenario changed the code as below and it...

Let me take this opportunity to share a unique issue that I faced during one small requirement development. Requirement: Contacts with a specific roles are created due a configuration miss in the EAI. As the product is live the fix can be put only after the root cause is found and change window is available. Till then these records needs to be deleted. As the number of records is huge deleting these records manually is a time consuming task and no back end deletion is allowed as the product is live. As a work around a client side BS would be developed to over come the problem. Siebel  Version : 7.7 Below is the pseudo code BusCom = "TechLabHelp" With BusCom                clear Query()                Search for Contact with Role "TECHLABS"                FirstRec = FirstRecord                Wh...