- Girish Bedekar, LiveCycle Solution Evangelist @ Adobe
A common use case is to let the end user select various fragments to insert in the final PDF. The screen shot below would better explain what I mean by this. AS you can see this screen captures some user information, and allows the user to select fragments that need to be inserted in the final pdf. When the user hits the submit button it will call a LC process which will parse the parameters and build the DDX needed for XDP Stitching. The Process makes use of a custom component called xmlUtilities which allows you to insert elements in an xml document. The input parameters to the process are the name,city,address,state,zip and fragments. The fragments variable will hold a comma separated list of selected fragments.
Read the complete post at Adobe LiveCycle Blog.
- Ameeth Palla, Technical Account Manager, Adobe
A topic that has come up several times in the recent past is about testing Adobe LiveCycle Workspace. I thought it will be useful to provide some information around this for the benefit of a larger LC community.
If the objective is Load testing, in-house Adobe uses a commercial tool call Silk Performer which can capture and replay the AMF3 interactions between Workspace and the server for scalable load generation. There are other tools that work with AMF3.Some people have asked if QTP can be used for load testing – It is unlikely that QTP is a good fit, since it is not suited to scalable load generation.
Adobe recommends using Silk Performer or Neotys Neload for load testing of Workspace. Check out the links below that may provide more insight into this topic:
If the objective is Functional testing then Workspace is configured for QTP testing out of the box. If you install QTP, restart your computer, then install the Flex plug-in for QTP, restart your computer then you can start automating your Workspace tests. However for QTP automation you should use the Workspace automation URL rather than the default URL. So rather than http://server:port/Workspace/Main.html you would use http://server:port/Workspace/Main-auto.html.
Read the complete post at http://blogs.adobe.com/livecycle/2012/03/testing-livecycle-workspace.html.
- Juergen Hauser, Sr. Product Manager – LiveCycle Data Services
Read the complete post at http://blogs.adobe.com/livecycle/2011/12/livecycle-data-services-for-java-ee-4-6-now-available.html.
The Cookbook homepage is here: http://cookbooks.adobe.com/livecycle. Check out the available recipes and contribute your own.
Original article at http://blogs.adobe.com/samartha/2012/03/toggling-between-two-fields-in-a-dynamic-form.html.
Moderator’s note: Although this blog post is not specific to LiveCycle, the Adobe enterprise community will likely find it useful. We’re taking the liberty of sharing it (with due thanks to Holly Schinsky).
There have been a lot of questions about the viability and future of Flex recently, and Adobe has published an official whitepaper today detailing their support for Flex going forward. The paper also contains details regarding Flash runtime support, Flash Builder support and other Apache contributions including the Falcon compiler. I believe the paper is a must read and can be found HERE.
Original article at http://devgirl.org/2012/02/15/future-of-flex-whitepaper-from-adobe/.
Problem Scenario: LiveCycle uses Quartz scheduler. Typical use case is when “watched folder” endpoint related schedules get translated as quartz triggers. Quartz takes care of executing the trigger based on frequency and updates a table with the latest execution count. … Continue reading →