Yes, it's possible. You can use a server-side component of LiveCycle
called Assembler - it's designed for combining multiple documents into
one.http://www.adobe.com/mea/products/livecycle/assembler/If you need
assistance making this work, don't hesitate to contact
us.Howardhttp://www.avoka.com
Another option is to inject a unique number into the form within the
process itself.This component generates a sequential number with
optional prefix and suffix, and allow you to inject it into the
form.Doc:
http://avoka.dnsalias.com/confluence/display/Public/Unique+ID+Generator+DSCDownload
trial: http://www.avoka.com/avoka/escomponents.shtmlHoward
Hi SteveMy understanding is that deleteResource deletes the entire
resource, with all its versions.What Elaine wants to do is to delete old
versions of a resource, but retain the most recent version. (Elaine,
please confirm.)You can get old versions of the resource using
getHistory, but there is no way of removing old versions.Howard
Hi ElaineI had a quick look at the APIs.There is no exposed API for
removing old versions.Therefore there is no way (at the moment) that
anyone could write a utility for purging old versions.I suspect your
proposed approach (i.e. delete the entire resource before uploading a
new version) would be the best way to go.There may (probably is) a
private API for removing old versions, but similarly to directly
manipulating the database tables, it's probably not a good idea.Although
if you feel this is...
HiWe have built an extended Enquiry tool for LiveCycle.This may solve
your problem.Check it out here:
http://www.avoka.com/avoka/enquirytool.shtmlIf it doesn't do what you
need, please contact info@avoka.com - we may be able to modify it to
your requirements.Howard
We're working on a tool that allows you to copy the preferences from one
user to all other users.If you would like to beta-test this, please
contact info@avoka.comHoward
HiI haven't tried it, but I think that might
be:/path_to_xml1/root_node/node[text =
string(/path_to_xml2/root_node/node)]i.e. without the quotes.Please let
us know if either approach works.Howard
AllSounds like you're describing a really unfortunate behaviour (aka
bug) in LiveCycle.In short, when you select a User or a Group in the
assignTask step, it displays the user/group name, but internally it
actually uses the ID.Since ID's are different on different systems, your
process isn't transportable across different systems.There are two
workarounds:1. Use the xpath method instead, and assign to
'' or '' as a string (between single quotes).
assignTask will try to resolve any string it find...
You can use insertXmlData operation in our XML Utils component.Info:
http://avoka.dnsalias.com/confluence/display/Public/XML+Utilities+DSCDownload:
http://www.avoka.com/avoka/escomponents.shtmlHoward
Hi AmbikaI'm not sure about your exact scenario, but you could try
XQuery intead of XPath.Info
here:http://avoka.dnsalias.com/confluence/display/Public/Transforming+XML+Documentshttp://www.avoka.com/blog/?s=xqueryand
http://avoka.dnsalias.com/confluence/display/Public/XQuery+DSCDownload
here:http://www.avoka.com/avoka/escomponents.shtmlXQuery is quite a lot
more powerful than XSLT (in my opinion).In addition, our implementation
allows you to merge multiple XML documents together.Please contact
i...
HiThe easiest way to do this is using our CollectionUtils component.Info
here:http://avoka.dnsalias.com/confluence/display/Public/Collection+Utilities+DSCDownload
here:http://www.avoka.com/avoka/escomponents.shtmlhoward
HiA simpler way to convert a list to a map, or a map to a list, and
various other operations, is to use our CollectionUtils component.Here:
http://avoka.dnsalias.com/confluence/display/Public/Collection+Utilities+DSCDownload
here: http://www.avoka.com/avoka/escomponents.shtmlHoward
HiYou can use our XMLUtils component.Check out: Insert XML Data at:
http://avoka.dnsalias.com/confluence/display/Public/XML+Utilities+DSCYou
can download here: http://www.avoka.com/avoka/escomponents.shtmlHoward
HiIt sounds to me like one of the instances of Forms executable is dying
due to invalid font, and is then failing for subsequent renders. The
reason that it's intermittent may be that you have multiple instances of
the Forms executable, and one of them has failed, and the other(s) are
okay.One thing to try is to check your fonts in the underlying XML for
each of your forms, because sometimes it's hard to locate all the
instances of font usage. Search for:typeface="xxx"and We have some internal...
HiI had a bit more of a think about this.Actually, you can do this right
now with components that we already have.First, you'd need to set up a
custom escalation process, rather than using the built-in escalations
provided by User>assignTask.This is described
here:http://avoka.dnsalias.com/confluence/display/Public/Customize+User+Task+Escalation+After+AssignmentThen,
instead of deadlining the task, just get the custom escalation process
to complete the task, using ProcessUtils>Force Task Complet...
Thanks MarkSo a component to simply test the validity (well-formedness)
of an arbitrary XML document would be helpful?This would save you having
to write the file to the file system, and read it back again.By the way,
do be careful with writing to a file and reading back. This may work
doing one off testing, but you need to be careful under load, because
you may get multiple process instances reading and writing the same
file.Howardhttp://www.avoka.com
You can use one of our
components:http://avoka.dnsalias.com/confluence/display/Public/Task+Attachment+Utilities+DSCLook
for the operation: retrieveAttachmentFromInitialTaskYou can download a
trial version here: http://www.avoka.com/avoka/escomponents.shtmlHoward
One possible solution:You can use our Group Lookup component to get a
comma-separated list of the emails of the members of the group. Then, in
the step before the User>assignTask step, send the group an email. The
only problem is that you won't be able to embed a link directly to the
task, because the task doesn't exist yet.Doc:
http://avoka.dnsalias.com/confluence/display/Public/Lookup+DSCDownload:
http://www.avoka.com/avoka/escomponents.shtmlTo work around this
problem, you can use the techniq...
Hi JeromeI found your response very interesting...Without meaning to
query your decision, can you explain why you can't use a "non-free
solution".It seems to me that you've already spent a lot of money on
LiveCycle, so you've already commited to using a "non-free solution".Why
not spend a bit more and end up with a solution that solves all your
problems?Instead you seem to be about to spend a whole lot of time and
effort to come up with a solution for a problem that we've already
solved. Isn't y...
No problemIt also:Makes your SQL look much neater.You can type in "test"
values for the parameters, so that you can test your SQL statement and
see the results.Howardhttp://www.avoka.com
If this is critical for you, you can "roll your own" Email endpoint
using a looping process. It will contain Email>receiveEmail, a Wait
step, and a sub-process invocation.If you need more help, read this
"Patterns" paper, which describes how this used to be done in the days
before watch folders.The details are different, the principle is the
same.http://www.avoka.com/resources/resources/TheWatchFolderPattern.pdfHowardhttp://www.avoka.com
Hi NeptasThe SetValue component does not throw any exceptions, as you
indicate.If an exception does occur, the process will stall - you will
be notified of this via email, you can see the stalled process in the
Adminui, fix the process, and then retry the stalled action.I agree in
general that:It would be nice if we could handle exceptions in more
streamlined waysAll components threw exceptions. (I'd log a feature
request with support and get this logged.)However, the types of
exceptions you des...
The red clock is added so that the person who missed their deadline
KNOWS that they missed their deadline.If you don't want the red-clock to
show up, we could probably write a custom component to get rid of it.If
you want to discuss further, please email
info-at-avoka.com.Howardhttp://www.avoka.com
This may be a dumb question, but if all you're doing is writing the XML
document to the file system, then why are you bothering to map it to an
XML variable at all. Just leave it as a Document variable, and write the
document to the file system.???Howardhttp://www.avoka.com
I suspect the problem is that you need to set the same xfaForm variable
as both the input and the ouput of the User>assignTask step.If you don't
specify the output variable, what the user types doesn't get
saved.howardhttp://www.avoka.com
If you're setting up a watch folder, you don't need to use a
readDocument step - you just need to define an input variable of type
Document, and the watch folder does the rest.I suspect you're getting an
error because the WatchFolder code and your readDocument step are both
trying to read the same document.howardhttp://www.avoka.com
