Hi,
Just wondering first of all if anyone else is experiencing the following 2 bugs and if they are, do you know a workaround?
Bug 1)
You have an edit box and that has the required field computed with some code, for example adding the following code into the compute section of ‘required field’:
if (“hello” == “hello”){
return true;
}else{
return false
}
This works and if you change the condition (“hello” == “hello2”) it also reacts in the way you expect where the field then is no longer required as the required flag is now being set to ‘false’. You also have the option to put a custom ‘required field error message’ and here’s where the bug occurs. If you enter a custom message, the custom message appears when validation fails, however now your computed required field code (above) no longer works. It changes from a field which computes whether it is required or not, to a standard required field. Anyone else having this problem, and do you know how to have the field both compute the required flag AND have a custom error message?
Bug 2)
I’ve mentioned this before and I know double posting isn’t a good thing to do, but this may also be linked. With a multi-line edit box this time, custom messages don’t work (this is when it’s a standard ‘required field’ with no computed code whatsoever). If you set a custom error message the default ‘Validation Error: Value is required.’ message is only ever presented. Again, any ideas?
The client I’m using is 8.5FP1 and the domino server is 8.5.
I’ve tried launching the XPage application on both the server and my local client (so it been tried under both 8.5 and 8.5FP1) but the same occurs in both instances.
Thanks