What error do you get?Jasmin

That's a good assumption.Jasmin

Yes. I though it would be showing xml for the variable type but it does show Document in both cases. But they are different. One is a org.w3c.dom.Document and the other one is a com.adobe.idp.Document.So I guess try to use a title for that parameter that reflects the nature of the variable you're tr...

The xml variable (org.w3c.doc.Document) is a native xml data type. That means you can use xml functions and/or xPath expressions on the content of the variable.The document variable (com.adobe.idp.Document) is a more generic data type that can store any binary data. If you happen to store xml in tha...

You still need to create a component reference (New->Component Reference) for it to be included in your lca.Jasmin

You would have to use a random function from javascript.For examplevar ran_number=Math.random()*5;Jasmin

See http://help.adobe.com/en_US/livecycle/9.0/workbenchHelp/help.htm?content=003817.html#1991418for a description of the object.Jasmin

Now we have this new Task Result object you can use in the Output section of the User step.The Task Result object contains a bunch of information about the completed task, one of them being the user that completed it.Jasmin

You would have to use the API to dynamically decide which process you want to call.That means you could use the Execute Script service or build a custom component that takes the name of the process you want to call as an input parameter.Jasmin

You don't have an object called Page4.In the hierarchy rename the (untitled Subform) (page 4) to Page4 and the script will work.You can confirm that the object is valid by typing "Page4." and you'll get the object browser to shoe the properties of the object.Jasmin