Stephane_Gervai

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.

Re: Subfolder in the Workspace ES? - Adobe LiveCycle

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.

Re: setting user preferences - Adobe LiveCycle

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.

Re: LiveCycle Workspace ES over the Internet - Adobe LiveCycle

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.

Re: Bootstrap error while intializing the database - Adobe LiveCycle

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.

Re: Deprecated usage of direct JNDI lookup of resource IDP_DS - Adobe LiveCycle

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/67abb02323961288?pli=1(A restart will likely be required.)This link mentions how to filter the warning from the logs:http://www-01.ibm.com/support/docview.wss?uid=swg21220886(A restart will likely *not* be requir...

264

Re: Document is not available on the sending side - Adobe LiveCycle

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 your process?Would you mind sharing your process with me? You can send it to livecycle57 at gmail dot com.

Re: Configuration Manager - Adobe LiveCycle

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.

Re: Document is not available on the sending side - Adobe LiveCycle

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).

Re: Import LCA error - Adobe LiveCycle

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 template or the application.xml. A bug in the preview archive code prevents the import of such LCAs. If possible, avoid using extended characters in process maps on 8.0.x systems.However, should you run int...

Re: Import LCA error - Adobe LiveCycle

To answer your second question in your initial post, "if Acrobat is uninstalled, are LiveCycle and JBoss also uninstalled?", the answer is no, and vice-versa: if LC and Jboss are uninstalled, Acrobat is not uninstalled.

Re: Import LCA error - Adobe LiveCycle

You can send me your archives at livecycle57 at gmail dot com. I'll take a peek. Also, try to find out the file and system encodings used by your appserver.

138

Re: Import LCA error - Adobe LiveCycle

Going along with this ... in your new archive, what is the path of the application.xml file? Is it really in the root of the archive?

138

Re: Import LCA error - Adobe LiveCycle

If the LCA cannot be opened by your favorite zip program, I'd start to worry ... try another zip utility maybe? Rename a copy of the lca file to your-file.lca.zip and try opening that ...A few more questions: - How big is the problematic LCA file?

138

Re: Mass Import - Adobe LiveCycle

See 'Administering LiveCycle ES' on page http://www.adobe.com/support/documentation/en/livecycle/. Search for 'scripted'.

Re: Image in Task Instructions - Adobe LiveCycle

Sorry for the delay. We reproduced the error; your use case is somehow causing a flash.events.Event of type 'change' to fire, and since the 'change' type collides with mx.events.IndexChangeEvent's type, this generic Event is not expected by one of the handlers for IndexChangeEvent in the Workspace code, thus the coercion exception. If you're into rebuilding Workspace from source, you can begin to fix this yourself as I'll explain shortly. Mind you, the results are not stellar even with the fix.....

Re: Mass Import - Adobe LiveCycle

Hi James, You could use scripted LCA deployment. I believe it will do what you need.Cheers.

Re: Import LCA error - Adobe LiveCycle

Hi Jerome, I suspect the problem is not with the LCA file itself, but with one of the files contained within the LCA file (which is a zip file today, although there are no guarantees that won't change in the future).Is there more to the error you are seeing? A stack trace perhaps?I think it's probably an error in the file encoding of the application.xml file contained within the LCA. The server expects a specific encoding, but the file is really encoded with another encoding.What OS? OS locale s...

138

Re: Image in Task Instructions - Adobe LiveCycle

Never mind, a colleague has reproduced the error.

Re: Image in Task Instructions - Adobe LiveCycle

Is there more to this error? A stack trace maybe?

Re: Document is not available on the sending side - Adobe LiveCycle

We've isolated the issue and hope to have a solution (patch) for this shortly... There is no workaround, unfortunately.

Re: Documents disappear in repository (?) - Adobe LiveCycle

Further posts on this topic should be done here:http://www.adobeforums.com/webx?128@@.3c05650b

Re: Document not available - Adobe LiveCycle

Further posts on this topic should be done here:http://www.adobeforums.com/webx?128@@.3c05650b

Re: Document is not available on the sending side - Adobe LiveCycle

The only option that might work, and I stress *might* because I can't really test it conclusively, would be to increase the defaultDocumentDisposalTimeout to a value that will be longer than your longest running process. A week maybe... This would have rather negative disk space implications if your system is under heavy load. Since this is a testing environment, maybe this would be acceptable: that's up to you to decide. Remember to restart your appserver after changing that value.All this woul...

Re: Document is not available on the sending side - Adobe LiveCycle

No, I doubt making the Document Form variable as output would make a difference. Process variables of long-lived processes are persisted back to the database after each operation. (At least, that's my understanding...)

Re: Document is not available on the sending side - Adobe LiveCycle

I am 'intermittently' able to reproduce the problem, but I don't use the UserService at all. I think the problem is not tied to a specific service, but lies in the Document API itself, or an interaction between the workflow engine/process map/Document API....

Re: Document is not available on the sending side - Adobe LiveCycle

Just a quick note while I digest the new details: a) no, I do not think the error is caused because you're doing something wrong in your process. b) yes, "document not available" refers to one of the instances of com.adobe.idp.Document used somewhere in your process, be it by a process variable or by an operation input/output parameter. It does not mean that the source form cannot be found in the Repository.

Re: Document is not available on the sending side - Adobe LiveCycle

Well, yes it seems to be related to how the Document instances are handled once retrieved from the Repository cache. I still don't see where the problem is; the best guess we have is that a race condition develops between the "Document sweeper" (runs every 30 seconds by default) and the "act of retrieving a cached Document and cloning it before returning it to the orchestration engine". It's all conjecture at this point: I still have no solid leads.Perhaps the occurrencee of the problem will be ...

Re: Document is not available on the sending side - Adobe LiveCycle

Final note as I give up ... I've tried more tests on 8.0.1 (no service packs applied) and I'm still unable to reproduce the error.

Re: Document is not available on the sending side - Adobe LiveCycle

Valerio,Thanks for the steps. I was not able to reproduce the problem. Since you indicate that you have 8.0.1 without any service packs (the line numbers in the stack trace confirms it), could you try to apply SP2 and see if the problem still occurs for new process instances? Any stalled operation reporting the error "Document is not available on the sending side anymore. [...]" can never be restarted since part of the data required to 'restart' the operation has been permanently lost.

Guidelines

Cookie preferences