Accessing .properties files within a Livecycle ES/ADEP DSC
0The other day Darren asked about how to access a properties file with some settings from within a Livecycle ES resp. ADEP DSC on the livecycle developers mailing list. I responded there, but I thought it’d be useful to post the solution here as well.
Essentially a Livecycle/ADEP DSC is nothing else but a .jar file that’s been crafted in a certain way. Darren wanted to have the .properties file within the DSC and needed to know how to access the file from Java code within the DSC. Here’s a working approach how this can be done:
---
Read the complete post at Blog In Black.
LiveCycle PDF Generator – Tips and Tricks
0- Saurabh Kumar Singh, Computer Scientist @ Adobe
Following are a few tips and workarounds for LiveCycle PDFG. Please note that the workaround marked as unsupported are not officially supported by Adobe.
- [Unsupported] On UNIX servers customers can use 64-bit OpenOffice to do OpenOffice based conversions. The obvious benefit from this is the performance improvement we get. To achieve this just point JAVA_HOME_32 to 64 bit version of Java. Same can achieved on widows too but you may observe immediate conversion failures for other native file formats.
- [Unsupported] Any file which can be opened by Acrobat (like a text file) can be converted to PDF using LiveCycle PDF Generator. You just need to add the comma separated file extension (for example txt for text files) in XPS to PDF file-type setting.
- A user/administrator can directly jump to PDF Generator UI by hitting http(s)://<server-name>:<port>/pdfgui. This way a user can skip couple of clicks on UI to land on PDF Generator user interface.
Extending Adobe LiveCycle through custom DSCs – some resources
0Don’t worry – this is not going to be a lengthy, complicated, super-advanced tutorial. I thought about writing a post on Adobe LC DSCs for a while, but never got round to. Today, I got kind of pushed over the edge by seeing that my friend Duane and his partner Matt from Überity have published a super-simple DSC to integrate an LC process with the Twilio SMS/TXT services.
You have no idea what I’m talking about? Ok – here’s the gist: A DSC is a Document Service Component in LiveCycle. Basically it’s a component wrapper for some custom logic or external service integration that one can write and use within the LiveCycle Process Management Engine. One of my biggest complains about and issues with LiveCycle are the lack of community contribution and the lack of good and advanced documentation around the product. So, let’s take this opportunity to compile a few interesting resources around DSCs.
If you’re ever in the need of extending LiveCycle (and most serious users I know are at some point), writing a Document Service Component is one of the easiest ways. To get started, use a tutorial Adobe provides here:
---
Read the complete post at Blog In Black.
20 reasons to upgrade to ES3 Correspondence Management solution
0
First version of LiveCycle Correspondence Management solution was delivered along with LiveCycle ES2 service pack 2.
Based on the customer feedback and requirements from various existing and prospective customers lot of new features have been added and existing features have been improved in Correspondence Management solution.
If you are an existing customer of Correspondence Management but are on LiveCycle version earlier to ES3 , Here are the 20 reasons why you should consider upgrading to LiveCycle ES3 Correspondence Management.
If you are a LiveCycle ES or LiveCycle ES2 customer and considering to buy and implement Correspondence Management as well , Here are the same 20 reasons why you should consider upgrading LiveCycle as well in order to make use of latest Correspondence Management solution.
(Please click the image to enlarge it and clearly view the content)


