If Workspace is used to work with tasks, then a task would have status "Process Draft" once a Workspace User has saved the task (via Save button, see image) but not yet completed the task.

You could customize Workspace to treat a chosen character as a delimiter and build a hierarchy from that, i.e. in your example the slash is the delimiter.

While those queries may work for users who have logged in at least once to Workspace, users who haven't yet logged in to Workspace will get the default hardcoded properties.

Waqas,Reverse proxies are not supported in LiveCycle Workspace ES 8.0.1.x. You said you use "Livcycle 8.0 SP2", which translates to LiveCycle 8.0.1.2.Try contacting Adobe Support.

What happens if you try that URL in a web browser?http://192.168.121.58:1521/adobe-bootstrapper/bootstrap?fetchTasks=true&responseLocale=enIt's very odd that you have TCP port 1521 as an HTTP port. That's the standard Oracle database port number. Recheck the values you entered in LCM.

I believe Adobe's recommended practice is to turn off these warnings. See the first link below. This link explains how to prevent WebSphere from reporting this particular warning at all:http://groups.google.com/group/ibm.software.websphere.usergroup/browse_thread/thread/cb92058dd83ea955/67abb0232396...

Hmmm ... the patch would only apply to documents pulled out from the Repository. If you -- as you say -- are pulling attachments (Documents) out from PDF-1, it is possible (likely) that the patch can't help you out there.To confirm, you experience the same type of error, but at a different point in ...

Hi Jerome,The host port only requires the hostname. Protocol prefixes are not required. Have you tried just the IP address? Java sometimes can't resolve hostnames.Also, is host sw0052 different than the host on which LCM is running? If not, you could try 'localhost' too.

The patches are ready but not yet posted to adobe.com.In the meantime, you could inquire with Adobe Support about: - Quick Fix 0.3 if you're running LiveCycle 8.2.1, - Quick Fix 2.57 if you're running LiveCycle 8.0.1.2 (8.0 with SP2).

I believe we've resolved the issue. To wrap up this thread:"org.apache.xmlbeans.XmlException: error: Invalid byte 2 of 3-byte UTF-8 sequence" This error occurs while importing an LCA (during the preview phase) and is caused by the presence of extended characters (such as é,à,...) in a process templa...