Hi SteffenIt's not a dumb question at all, it's a very good one.There are two ways you can purge your LiveCycle database.1. You can use the Adobe PurgeProcessTool. This tool completely deletes all trace of processes that meet a particular criteria (usually, they must be older than a certain date).Af...

Hi RyanYou may want to preprocess the results to turn these characters into their XML "escaped" equivalents.e.g.      ' for 'See http://www.xmlnews.org/docs/xml-basics.htmlWe also have a SQPlus component that does what the Adobe component does, plus quite a bit more. We'd be happy to talk to yo...

Hi WillWe provide an enhanced Enquiry Screen within Workspace that has this capability.More info and download here: http://www.avoka.com/avoka/enquirytool.shtmlIf you have any queries, please contact info@avoka.com.Howard

Hi JeromeWe provide an enhanced Enquiry Screen within Workspace that has this capability.More info and download here: http://www.avoka.com/avoka/enquirytool.shtmlIf you have any queries, please contact info@avoka.com.Howard

Hi NelsonWe provide an enhanced Enquiry Screen within Workspace that has this capability.More info and download here: http://www.avoka.com/avoka/enquirytool.shtmlIf you have any queries, please contact info@avoka.com.Howard

Um, I don't quite get it. (And no, I haven't tested this...)Are you saying that if you:Delete the fragmentUpload a new version of the fragement Open the XDP form that refers to the fragment--> You get the old version of the fragment?   4.   But if you close workbench, then open it again, and then op...

Hi DeepakI suggest you take a closer look at the component and sample I posted earlier. Even if you decide not to purchase it, it will give you some good hints about how to implement this.Howard

Hi Elaine1. Yes, I agree, this isn't something you should need to code up yourself, it should be part of the product. My understanding is that this area is targetted for improvement in the next version, but you may want to log a feature request with Adobe to make sure it works the way you'd like it ...

In the User>assignTask step, you can save the ID of the user who completed the step into a string variable. You can then use the User Lookup step to look up this ID, and return details about the user. YOu can then use SetValue to inject the user information into the form.Howardhttp://www.avoka.com

Hi RyanIt's very difficult to respond without more details, particularly the error that you're getting, and perhaps also a simple example of both the XML and the XSLT.Also, this seems to be more a generic XSLT issue, so you may get a better response from an XSLT-specific forum.Howardhttp://www.avoka...