Future Feature Request: Add additional Error Message fields for EACH constraint

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Future Feature Request: Add additional Error Message fields for EACH constraint

jbc2
I would like to make a request for a future version.

Currently, only one constraint field and one corresponding Error
Message field is allowed per control.   We're requesting if Form
Builder (and I guess the XForm spec) will allow for multiple
constraints with their own corrsponding error message.

For ex:

First Name field (i.e. text input).   We'd like to make it (a)
required field, (b) allow a max # of characters of 30 for example, (c)
and not allow any special characters (like '<' etc.).

Right now, we can make one long expression and put it in the one
Constraint field for that control, however, if it fails on any of the
3 above cases, it will result in displaying the same Error Message for
all 3.

We'd prefer to specify 3 separate constraints on the one control and
have a separate Error Message specific to that failed constraint
appear to the user.

Any comments or suggestions are welcome.

Thanks.


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Future Feature Request: Add additional Error Message fields for EACH constraint

David Shirk
I'm brand new to Orbeon - reading about it for 2 days, not using it yet, but I think I'm about to. If this is truely a limitation of constraint messages and an enhancement is to be made, in my opinion it would be much better to reference an error XML file that allows message reuse across multiple fields. The constraint returns the error element id and zero to many parameters. The referenced error element would be returned with parameters. Using the example below, the same constraints probably apply to the last name field as well as a spouses name, etc. The parameter might be first, last, spouse first, spouse last, etc.

jbc2 wrote
I would like to make a request for a future version.

Currently, only one constraint field and one corresponding Error
Message field is allowed per control.   We're requesting if Form
Builder (and I guess the XForm spec) will allow for multiple
constraints with their own corrsponding error message.

For ex:

First Name field (i.e. text input).   We'd like to make it (a)
required field, (b) allow a max # of characters of 30 for example, (c)
and not allow any special characters (like '<' etc.).

Right now, we can make one long expression and put it in the one
Constraint field for that control, however, if it fails on any of the
3 above cases, it will result in displaying the same Error Message for
all 3.

We'd prefer to specify 3 separate constraints on the one control and
have a separate Error Message specific to that failed constraint
appear to the user.

Any comments or suggestions are welcome.