Posts tagged security

Mobile Form Service Proxy

In the pre-release forum of ES4 and other customer forums of Mobile Form, one of the most sought after feature was to run all the Mobile Form workflows without directly exposing the LiveCycle server to the user accessing the forms in the browser. In ES4, the LC admin is required to open submission service “/lc/content/xfaforms/submission/default” to the whole internet as the Mobile Form needs to talk to it. The service url was embedded in the runtime model of the form. One way was to do URL mapping in webserver and proxy it but the restriction was one cannot change the URL path as it was in the runtime model.

To read the complete article, visit this blog post.

Passing parameters to Mobile Form

In LC ES4, we get this feedback from customers that they want to hide the parameters passed to Mobile Form profile to render a form. If you could see the There was only one way to pass parameters that is through request parameters (refer to Mobile Profile page). In ES4 SP1, we introduced couple more ways to pass parameters to Mobile Form.

Read the complete post here .

Hide template reference

In this post I will describe how one can you pass template reference without using request parameter. The default profile of Mobile Form takes all the parameters like template reference, data reference etc through HTTP request parameter. If Mobile Form is deployed to serve the forms on internet then you might not like to expose such URLs on public forums. That is probably because it would expose the internal repository structure to the end user.

Read the complete post here .

AEM document services and document security add-ons, powered by LiveCycle

Today we are announcing new AEM document services & document security add-ons, powered by LiveCycle.  These AEM add-ons let you publish & secure enterprise forms and documents on your website.  Learn more here: http://adobe.ly/14uV8lM

LiveCycle XMLForms Native Process and WebSphere Global Security

- Santosh Tatke, Sr. Support Architect @ Adobe

Debugging form rendering issues related to XMLforms native process could be challenging. In one of the earlier blogs I’ve put together a few points those could help narrow down problem areas. Blog post is available here.

We recently encountered a situation with another customer which was another manifestation of form rendering related problem and root cause was very different.

They were using LiveCycle ES2 SP2 + AIX 6.1 + WAS 7.0.0.17 + Oracle 11g.

---

Read the complete post at Adobe LiveCycle Blog.

Security misconceptions – Watermarks, Usage Rights and Rights Management

There is a confusion about what features of Acrobat and PDFs in general offer by way of securing documents. I would like to do a very cursory overview of the items that I have so far seen users consider “security.”
To be clear, by “security” I mean the ability or inability to access the contents of the PDF, thus safeguarding information from entering the wrong hands.

Read the complete post here.

Using Reader Extensions and Barcoded Forms


I’m starting a new hands on series for LiveCycle called appropriately: Hands On LiveCycle. This series will give you a complete and working sample LCA (LiveCycle Archive) file that you can import and run on your LiveCycle server. These hands on entries will attempt to solve a real world problem and will start out simple and continue to grow in complexity. If you have a suggestion for a hands on entry you would like to see feel free to let me know!

I’m kicking the series off with a problem that something that most consumers and agencies can relate to. How to handle a form that requires a wet signature, or an actual physical signature on the document.
In a perfect world everyone would accept a digital signature and all forms would be able to be submitted online. However, we don’t live in a perfect world and a good number of companies and government agencies still require a wet signature on a document or form to do business. If you wanted to fill out a form for a financial service or a government request the typical process today might go something like this:

  1. Download the document
  2. Print the document
  3. Fill out the document
  4. Sign the document
  5. Mail the document

Once the document is in the mail the process continues:

  1. Receive the document
  2. Key in the data in the document to the database
  3. Store the document on the server

There are quite a few things that can go wrong with this human centric process. The document could get lost in the mail, the user could fat finger the data, causing delays, or the document could be stored in the wrong place. There are several ways that this process can be improved, just by using LiveCycle Reader Extensions, the LiveCycle Foundation Services and the free Adobe Reader (Barcoded Forms is now included with the LiveCycle Reader Extensions service) Using LiveCycle Reader Extensions allows you to automate several pieces of this process and in some cases more, depending on how a company or agency is willing to accept the form.

For this LiveCycle Hands On, it is assumed that the document will be filled out, printed, signed and mailed in by the applicant. Once the document arrives at the agency, it will be scanned and placed in a folder that is watched by LiveCycle. Once LiveCycle sees the document in the folder it will be processed, the applicant data will be stored in a database and the document will be written to the file system.

This process could be made even faster by removing the snail mail portion if the agency was willing to accept a document by email. If so, the applicant could scan the document themselves, attach it to an email and send it to an email address that LiveCycle monitors. Also, with the use of Reader Extensions, the user can now save a copy of the completed form to their hard drive.

Download the zip file: Barcoded_Form_Demo.zip

The zip file for this hands on has a .lca file containing a form, some sample data and a process as well as a sample filled out form and a SQL script to create the demo table. The SQL Script should be run on the server that is hosting the LiveCycle Database and should use the adobe schema. The form will work either as the PDF file included, or if the form is printed out and scanned. LiveCycle is able to decode the information from the barcode either way.

The Barcoded Form Demo Process:

The process is broken down below into steps and the operations used.

  1. LiveCycle recieves a document from the watched folder to start the process
  2. LiveCycle extracts the data from the barcode and adds it to a XML variable. Operation: Decode Category: Barcoded Forms
  3. LiveCycle extracts the XML form data from the barcode data and stores it in an XML list variable. Category: Extract To XML Service: Barcoded Forms
  4. LiveCycle sets the form data to the first element of the XML list variable. Operation: Set Value Category: Foundation
  5. LiveCycle inserts the data into the database. Operation: Execute SQL Statement Category: Foundation
  6. LiveCycle writes the document to the file system. Operation: Write Document Category: Foundation

Please feel free to ask any questions in the comments and I will try to answer them as quickly as I can!

——-
Original article at http://www.underprise.com/2011/05/20/using-reader-extensions-and-barcoded-forms/.

Go to Top