I found out that this problem was a bug (#2504275) in ES2 that has since been fixed in ES2 SP1. If you can apply the service pack that ought to fix your probelm.

Yes, be sure to chek out our series called, "Ask the Experts": http://www.adobe.com/cfusion/event/index.cfm?event=detail&id=1488432&loc=en_usGary.

A while ago we built a sample that would use both Forms and Form data integrator to merge data with a Form. Here it is:http://help.adobe.com/en_US/livecycle/9.0/samples/ServiceUsageSampleFormDataManipulation.htmlThe error that you report is implying that there is a class dependency between Form Data Integrator and a package called "com/adobe/formServer/utils" which is not installed (and I agree does sound like the Forms Service).You should be able to use the Form Data integratiion service to per...

That is odd. I did beleive that when you set Run As Invoker on a long loved process, then that will set the execution context for each of the steps that are invoked via the Work Manager (thus overriding the default behavior) but I will double check for you (maybe it was a chnage in behavior in ES2)

The reason for that (and sorry, I know this will not immediately solve your problem) is that the *parent* process probably did not have a Run As configured. Being Long-Lived it will, by default, run as "System" after its invoker has invoked it and is no longer synchronously waiting for a resoponse. So if you chnage the parent process to "Run As Invoker", then I think you may see the invokers context proagate through to the child process as well. But this difficult to manage because each of the s...

This is not a very useful answer, but might be relevant added info: You can browse services (that arise from your deployed processes) in the Admin UI and configure their "Run As" behavior. The Run As can be set to the Invoking User, a named user or System. I think you may be able to set the Run As for any long lived process to be the process invoker, which will in turn get passed through to any sub processes that get called. The downside of course is that you may not really want those processes ...

While I am not sure about Guides, here is some related infotmation that may help you towards the answer:- If your browser session is already authenticated to LC (i.e. you have an LC cookie) then a Flex application can actually invoke LC services with remoting and provide SSO with the existing logged on user identity.- There has been work done in ES2 to allow SAML to work as a means of browser based authentication to LiveCycle and this can be extended also to Flex applications. You can read about...