Hi Iñigo,
To summarize (and to make sure I understand your situation correctly!):
1. Users enter data in a form, click a button which saves the data in the
database, and loads a signature page, passing a reference to the document
id.
2. On that page, users sign the data, and on confirmation are sent back to
Orbeon Forms where the form is loaded, passing the document id to load using
the technique Erik mentioned earlier.
When users sign, I imagine that you store some information about that
signature. You could also assign a "signature id" to that signature, which
you pass to the form on step 2. On load you could call a service you
implement, checking that this signature id is indeed valid, and that the
data has been signed. In a situation like this, passing the signature id
doesn't expose any information. Would this work for you?
-Alex
-----
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet