Scenario
There are times when we want someone not
logged into the domain to be able to edit a form which needs to be submitted to
DBXL. Let's say that "User A" is a person who works inside the domain
and therefore has access to submit to DBXL and "User B" is a person
who is working outside of the domain.
Value Proposition
Using DBXL's "URN-based solution" feature gives
us the power to use InfoPath forms to capture offline e-mailed data for
centralized DBXL upload. We can email forms back-and-forth, to and from external
users (sometimes offline/disconnected or simply not a member of the domain),
and at the same time, manage those forms in private locations such as a domain.
We need to make sure that the form data in both the public and the private
locations are in-sync.
Here's an outline of the solution we're
trying to accomplish:
1.
User A emails the form template
(XSN) file to an external user, User B (External version).
2.
User B opens the form template,
fills it out and emails back to User A.
3.
User A receives the form (XML)
and opens it with the higher version of the form template (Internal version).
4.
User A submits the form to
DBXL.
5.
User A opens the form from
DBXL, edits it and emails it back to User B.
Note that User A may receive a warning message that
the original form template cannot be found and suggests another form template
to open the form instead. Clicking Yes will open the form with the correct
version of the form template.
6.
User B receives the form,
accepts the changes, re-edits and re-emails back to User A.
Note that User B may receive a warning message that
the form template associated with the form has a higher version than the one
stored on the machine. Clicking Yes will allow user to open the form.
7.
User A receives the form and
re-submits it to DBXL.
Requirements
-
DBXL v2.4 or higher
-
InfoPath 2007 with SP2 or
InfoPath 2010 with SP2
-
Outlook 2007 or 2010 (for
domain members)