About 3 years ago I wrote my first custom component for Adobe LiveCycle ES, a…
My colleagues from Adobe’s Benelux technical team have come up with another great use case for my custom LiveCycle ES Twitter Component I built some time ago.
Anyone with a corporate shared Twitter account will understand the conflict between being open and allowing anyone to post a tweet vs making sure that only correct public information is exposed. This solution built out using Adobe LiveCycle ES & Flash Builder is one way of solving this issue.
Part 1 – Build a controlled tweet solution
Building a controlled Twitter solution using Adobe LiveCycle ES (part1) from Dr LiveCycle on Vimeo. Part 1 of a video that demonstrates how you can use LiveCycle ES to build a process
After reading a couple of great articles recently I thought I’d give writing a component (or DSC – Document Service Component) for LiveCycle ES a go. For inspiration I read Mike Hodgson’s Devnet walkthrough article on how to build a component and Christoph Room’s sample for integrating LiveCycle ES with Adobe Share.
Since using the Twitter API has become the modern day “Hello World” I decided to give it a shot. After googling for 5 minutes I found the Think Tank Twitter java interface. A few lines of code and I had my class written ready for LiveCycle integration;