A common pattern that’s used in process design is establishing ‘constant’ values that you refer to a few times in the process. To establish a constant value, you either:
LiveCycle Content Services ES is an ideal location in which to store documents created by business processes. However, Content Services ES does not expose a public API or support a public WSDL. As a result, you cannot directly invoke its operations from a client application such as a Java or a Flex client.
That is why I decided to create an article that discusses what you have to do if you want to store a document in Content Services ES using a client application. Basically, you have to first create a process using LiveCycle Workbech ES. Then you can invoke the process from the client application. For more information, check out the article that I wrote,
Programmatically accessing LiveCycle Content Services ES.
We would love to send each of you a cool plastic ring to help decipher some of the varying terms found in the LiveCycle forums and product documentation. But, since we don’t know your ring size, we’re providing this one-size-fits-all blog posting instead.
When writing the product documentation, we try to use terms consistently (you can find some of them in the Glossary). But you may run across terms on the message boards (like Adobe LiveCycle Forums and Adobe LiveCycle Developers Google Group) that leave you scratching your head. Hopefully, this table will help you decode the terminology. And, if you run across any other puzzling terminology, please add a comment to this post and we’ll try to clear it up for you.
|
Non-standard term |
Standard term (used in documentation) |
|
Acrobat PDF Form |
Acrobat form |
|
AcroForm |
Acrobat form |
|
dynamic form/dynamic XFA form |
dynamic PDF form (created in Designer) |
|
Flash, Flash-based |
based on Adobe Flash technology |
|
flat form |
non-interactive form |
|
flatten a form |
convert a form to a non-interactive form |
|
Form Server |
LiveCycle Forms |
|
form template |
form design (we do use "form template" when talking about .tds files in Designer) |
|
orchestration |
process |
|
Output Server |
LiveCycle Output |
|
pre-filled form |
prepopulated form |
|
static XFA form |
static PDF form (created in Designer) |
|
workflow |
process |
|
XFA form |
form created in LiveCycle Designer |
LiveCycle ES is an integrated server solution that provides data capture, information assurance, document output, process management, and content services using a service-oriented architecture. You can learn more about what LiveCycle ES can do by watching these fantastic episodes from LiveCycle Evangelist, Duane Nickull:
You can also learn about LiveCycle ES and what it can do by visiting these links:
“I want the documentation to tell me what to do when I don’t know what I want to do.”
- LiveCycle Customer Quote
As technical writers, we deal in information. In essence, we create and publish meaningful information about how to use software products and features for you, our customers. Or at least we like to think we create meaningful information. Every now and then we get the feedback from customers that the documentation we produce is not adequate. Often, we don’t get anything more specific than that, but sometimes, if we are lucky, we’ll get a specific complaint like: add more examples.
We think that part of the problem is that we don’t get very much direct customer feedback. We know you’re out there — somebody is buying our products after all — but how can we help you do what you do better, faster, etc?
