Re: Mobile forms having to be opened from different URI on mixed security classified environments

Asterion — Fri, 03 Aug 2007 00:34:45 GMT

I saw another posting that talked about onLine v offLine using, say "if(thisApplication.MachineOnlineState == XdMachineOnlineState.xdOffline)". Now if the form can programmatically fool itself about its publishing history somehow we could avoid touching the file per se. I know this (appears to) defeat the notion of the publishing option, but if we could have the form be happy to be run from two fixed and not one fixed publishing sites.

Mobile forms having to be opened from different URI on mixed security classified environments

Asterion — Thu, 02 Aug 2007 15:55:44 GMT

We have a task to build a forms based approach for a classified site.

The problem is that there is a mix of SECRET laptops and RESTRICTED network servers and clients. Material can migrate from RESTRICTED to SECRET relatively, but not the other way with major hoops.

The nuisance is then that we need to publish a report.xsn onto a USB stick. Have operators using the SECRET laptop save report.xml to the stick. Have someone move the report.xml to a CD. Nurse the data through a security check and then copy the report.xsn onto the RESTRICTED LAN.

We subsequently want to open the forms for editing again but cannot guarantee, say, having report.xsn on a similar path the the laptop. Because the RESTRICTED clients are geographically distributed we cannot distribute the forms to the RESTRICTED clients and so a server based repository of the forms seems the best option.

The problem is that the report.xml will be referencing the published report.xsn on the SECRET laptop's USB stick.

We'll have issues enough synchronizing the forms between the SECRET and RESTRICTED environments as it is.

I assume that we can do something as clunky as manually edit the report.xsn reference in the report.xml as we move the instance data onto the RESTRICTED LAN. We are funding limited so we are using eXist as a form repository so the avenue of using local (same directory) refs, even if it were available, may not solve the problem. So the reports.xml will eventually be on a web service with REST or WEBDAV access (though even this seems a problem at the moment as InfoPath isn't happy even saving into a collection).

Do we have to mangle the report.xsn reference once we get the report.xml onto the RESTRICTED LAN? Or is there something smarter we can do with the XSLT features of InfoPath? If forms are signed electronically, at they are locked by InfoPath I assume that subsequently editing the raw xml will break the file.

Any ideas welcome.

Cheers,

Rei

Newbie Questions

Re: Mobile forms having to be opened from different URI on mixed security classified environments

Mobile forms having to be opened from different URI on mixed security classified environments