Orbeon Forms community mailing list

How to extend Save button behavior in Form Runner?

Classic

List

Threaded

6 messages Options

Tom McLeod

How to extend Save button behavior in Form Runner?

I'm very new to Orbeon; I'm guessing there's somewhere to plug this in...

When an end-user saves an instance of a form, I want to know about it. I still want the form to be saved to eXist as it is out of the box. But then, I want to call a web service passing in the UID of the new instance.

In the Bookcast tutorial, where the save functionality is implemented from scratch, I can see where to start trying to expand on the submission.

But in form runner, where would logic like this go?

I'm open to other means of achieving this, like eXist itself triggering an action on an insert, but FR seemed like the likely place to start.

Thanks,
Tom

Erik Bruchez

Re: How to extend Save button behavior in Form Runner?

Administrator

Tom,

There is no hook within Form Runner, but Form Runner calls the eXist
persistence layer through REST, so you could:

* Patch your version of RESOURCES/apps/fr/persistence/exist/crud.xpl
* Or create your own version of the eXist persistence implementation
** copy over RESOURCES/apps/fr/persistence/exist to your own
directory, say "my-exist"
** Point Form Runner to that, e.g.:
<property as="xs:anyURI" name="oxf.fr.persistence.app.uri.*.*.*"
value="/fr/service/my-exist"/>

Note that unless you are working with the source from CVS, these files
are in orbeon-form-runner.jar.

-Erik

On Jun 11, 2009, at 11:46 PM, Tom McLeod wrote:

>
> I'm very new to Orbeon; I'm guessing there's somewhere to plug this
> in...
>
> When an end-user saves an instance of a form, I want to know about
> it. I
> still want the form to be saved to eXist as it is out of the box.
> But then,
> I want to call a web service passing in the UID of the new instance.
>
> In the Bookcast tutorial, where the save functionality is
> implemented from
> scratch, I can see where to start trying to expand on the submission.
>
> But in form runner, where would logic like this go?
>
> I'm open to other means of achieving this, like eXist itself
> triggering an
> action on an insert, but FR seemed like the likely place to start.
>
> Thanks,
> Tom
>
> --
> View this message in context: http://www.nabble.com/How-to-extend-Save-button-behavior-in-Form-Runner--tp23993689p23993689.html
> Sent from the ObjectWeb OPS - Users mailing list archive at
> Nabble.com.

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

bsteuhl

Re: How to extend Save button behavior in Form Runner?

So is there no way to call the save submission/function from a trigger we create in the form or even call other submissions after the save function if we use the form runner save button? Thanks.

youl

Re: How to extend Save button behavior in Form Runner?

Hi bsteuhl,
Did you find answers to this question?
thx

bsteuhl

Re: How to extend Save button behavior in Form Runner?

No - never got a response. I have always developed orbeon forms out side of form builder/runner but a client wanted me to try and use form builder. I felt handicapped in that environment and the only thing they really liked was the CSS so I use the form runner CSS in my external xForms I code by hand. This way I have complete control over everything and generate PDF using FOP and xsl-fo processor instead of that PDF printing which is like taking an image of the screen and putting it into PDF format - did not like that. I have the form data stored in embedded eXist using the same url structure as form builder (even though my suggestion down the road is not to use embedded eXist and run an external eXist db to store all data).

In my opinion form builder/runner is good for quick form development - but for something more advanced find it difficult to work within form builder and then bring code outside to add additional functionality and then put back in form builder, etc. Maybe just my lack of knowledge - but personal opinion.

If you get the answer would love to see it in nabble ops down the road. Good luck.

Brian Steuhl
website: http://BTMSoftwareSolutions.com
business email: [hidden email]
cell: 908-421-0742

home office: 732-961-3187
RSS Feed To My Blog:

From: youl [via Orbeon Forms (ops-users)] <[hidden email]>
To: bsteuhl <[hidden email]>
Sent: Tue, March 30, 2010 10:18:03 AM
Subject: Re: How to extend Save button behavior in Form Runner?

Hi bsteuhl,
Did you find answers to this question?
thx

View message @ http://n4.nabble.com/How-to-extend-Save-button-behavior-in-Form-Runner-tp43883p1745274.html
To unsubscribe from Re: How to extend Save button behavior in Form Runner?, click here.

Erik Bruchez-3

Re: Re: How to extend Save button behavior in Form Runner?

Brian,

Thanks for the feedback. We hope to make Form Runner more and more palatable as the default/standard way to run/deploy forms, so such feedback is important.

-Erik

On Tue, Mar 30, 2010 at 7:25 AM, bsteuhl <[hidden email]> wrote:

No - never got a response. I have always developed orbeon forms out side of form builder/runner but a client wanted me to try and use form builder. I felt handicapped in that environment and the only thing they really liked was the CSS so I use the form runner CSS in my external xForms I code by hand. This way I have complete control over everything and generate PDF using FOP and xsl-fo processor instead of that PDF printing which is like taking an image of the screen and putting it into PDF format - did not like that. I have the form data stored in embedded eXist using the same url structure as form builder (even though my suggestion down the road is not to use embedded eXist and run an external eXist db to store all data).

In my opinion form builder/runner is good for quick form development - but for something more advanced find it difficult to work within form builder and then bring code outside to add additional functionality and then put back in form builder, etc. Maybe just my lack of knowledge - but personal opinion.

If you get the answer would love to see it in nabble ops down the road. Good luck.

Brian Steuhl
website: http://BTMSoftwareSolutions.com
business email: [hidden email]
cell: 908-421-0742

home office: 732-961-3187
RSS Feed To My Blog:

From: youl [via Orbeon Forms (ops-users)] <[hidden email]>
To: bsteuhl <[hidden email]>
Sent: Tue, March 30, 2010 10:18:03 AM
Subject: Re: How to extend Save button behavior in Form Runner?

Hi bsteuhl,
Did you find answers to this question?
thx

View message @ http://n4.nabble.com/How-to-extend-Save-button-behavior-in-Form-Runner-tp43883p1745274.html
To unsubscribe from Re: How to extend Save button behavior in Form Runner?, click here.

View this message in context: Re: How to extend Save button behavior in Form Runner?

Sent from the Orbeon Forms (ops-users) mailing list archive at Nabble.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