Orbeon Forms community mailing list

validation approaches for xforms in a workflow

Classic

List

Threaded

4 messages Options

ilango_g

validation approaches for xforms in a workflow

Hi
This may seem a naive and general set of questions.I am looking for general ideas and suggestions from anybody who has used XForms in a workflow process.

So I have an XForm in a Workflow. The same form is pushed from one point of time in the process to another. Each time it is present in a different place, its state is different. For instance, when the form is initially filled in at the first point where the form starts its journey, it may have a set of data in it. For instance if I have a total of 100 different fields in my form, I do not need to fill in all 100 fields. The reason is that a different user will fill in those fields at a different point of time in the process. So these fields, say 20 of them are to be greyed out (unfilled) and passed on to the next stage in the process.
How would I need to manage the data in these 20 fields. Can I set these fields to not-required at that point of time in the process.
#Can I just validate those 80 fields before I send the form out to the process? My solution (premature) so far to this question has been to turn off validation completelyt ,which I know is not a solution.

#What are Orbeon's approaches to validation?

I have read up about the Orbeon oxf validation processor. So far, I tend to rely on client-side validation as far as possible.

#Is that enough?
I am afraid that we might need to have a different layer of validation so it leaves me thinking that in addition to having client validation (written inside the XForm) we need to have a separate button inside the XForm that perhaps sends our data to another validation processor. Does that sound normal?

If I leave off 20 fields blank and leave validation on( and I think this is where Orbeon's Validation Processor kicks in again through a button that is already pre-positioned in there at the end) the Validation processor might complain coming back with xforms-invalid messages.

Any ideas and suggestions are appreciated.

Thanks in advance for your time and consideration.

Alessandro Vernet

Re: validation approaches for xforms in a workflow

Administrator

On Fri, Mar 7, 2008 at 9:46 AM, someperson <[hidden email]> wrote:
> For instance, when the form is initially
> filled in at the first point where the form starts its journey, it may have
> a set of data in it. For instance if I have a total of 100 different fields
> in my form, I do not need to fill in all 100 fields. The reason is that a
> different user will fill in those fields at a different point of time in the
> process. So these fields, say 20 of them are to be greyed out (unfilled) and
> passed on to the next stage in the process.

One way to deal with this is to make sections of your form relevant
depending on some a condition, which in your case would be the step of
the process you are at. So the form (your XForms code) is always the
same, it is just <xforms:bind> in the form that show or hide certain
controls, and makes other fields writable or read-only. Does this make
sense?

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.com/

--
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

ilangostl

Re: Re: validation approaches for xforms in a workflow

Hi Alex

It makes sense. I do apologize for another posting that I made that might appear to be a duplicate question.

Specifically my new question (which must have been posted by now) related to the question of dynamically evaluating true or false for the readonly() attribute.

And just last night, I saw something on the internet called "yav" which is a tool for validation on some non-XForms form. As soon as I press a button called check it will bring back to the user the results of its validation like: " you entered a invalid value for date: should be mm/dd/yyyy".Is there any such mechanism that I can make use of in Xforms?

On Wed, Mar 12, 2008 at 12:20 AM, Alessandro Vernet <[hidden email]> wrote:

On Fri, Mar 7, 2008 at 9:46 AM, someperson <[hidden email]> wrote:
> For instance, when the form is initially
> filled in at the first point where the form starts its journey, it may have
> a set of data in it. For instance if I have a total of 100 different fields
> in my form, I do not need to fill in all 100 fields. The reason is that a
> different user will fill in those fields at a different point of time in the
> process. So these fields, say 20 of them are to be greyed out (unfilled) and
> passed on to the next stage in the process.

One way to deal with this is to make sections of your form relevant
depending on some a condition, which in your case would be the step of
the process you are at. So the form (your XForms code) is always the
same, it is just <xforms:bind> in the form that show or hide certain
controls, and makes other fields writable or read-only. Does this make
sense?

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.com/

--
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

--
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

Erik Bruchez

Re: Re: Re: validation approaches for xforms in a workflow

Administrator

Correct me if I am wrong, but I thought that this was what Orbeon
Forms was about: providing instant validation and the likes ;-) And
the beauty of it is that with Orbeon Forms, you don't have to press a
button at all.

But maybe I don't quite understand your question.

-Erik

On Mar 12, 2008, at 7:57 AM, XGuy wrote:

> Hi Alex
> It makes sense. I do apologize for another posting that I made that
> might appear to be a duplicate question.
> Specifically my new question (which must have been posted by now)
> related to the question of dynamically evaluating true or false for
> the readonly() attribute.
>
> And just last night, I saw something on the internet called "yav"
> which is a tool for validation on some non-XForms form. As soon as
> I press a button called check it will bring back to the user the
> results of its validation like: " you entered a invalid value for
> date: should be mm/dd/yyyy".Is there any such mechanism that I can
> make use of in Xforms?
>
>
> On Wed, Mar 12, 2008 at 12:20 AM, Alessandro Vernet <[hidden email]
> > wrote:
> On Fri, Mar 7, 2008 at 9:46 AM, someperson <[hidden email]>
> wrote:
> > For instance, when the form is initially
> > filled in at the first point where the form starts its journey,
> it may have
> > a set of data in it. For instance if I have a total of 100
> different fields
> > in my form, I do not need to fill in all 100 fields. The reason
> is that a
> > different user will fill in those fields at a different point of
> time in the
> > process. So these fields, say 20 of them are to be greyed out
> (unfilled) and
> > passed on to the next stage in the process.
>
> One way to deal with this is to make sections of your form relevant
> depending on some a condition, which in your case would be the step of
> the process you are at. So the form (your XForms code) is always the
> same, it is just <xforms:bind> in the form that show or hide certain
> controls, and makes other fields writable or read-only. Does this make
> sense?
>
> Alex
> --
> Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
> Orbeon's Blog: http://www.orbeon.com/blog/
> Personal Blog: http://avernet.blogspot.com/
>
>
> --
> 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
>
>
>
> --
> 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

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/

--
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