Dr Flex & Dr LiveCycle

Published by Waldo Smeets under Adobe Flex,LiveCycle Forms ES,LiveCycle Workbench,Uncategorized

The Modeler in LiveCycle ES2 ships with several built-in validation classes, which you can apply to the models properties using the Styles definition. Obviously these standard classes don’t cover all use cases, especially not validation behavior that is specific to a non-US region for example. One of the cool things about Fiber models is that you can extend them using custom ActionScript code, so that you can use your custom validation classes in your projects (I plan to write another article on working with custom methods in your model by overwriting the generated value objects).

So, you can add and apply your own validation classes to the model. You just need to refer to your custom class in the Style validation annotation of the property. First, copy the validation class itself into the correct folder of your Workbench project. That’s also the trickiest part within the LiveCycle Modeler (compared to doing this for the Flash Builder modeler). The FB modeler generates the code into your Flex project folder and you can easily find it, but Workbench doesn’t generate the code in the directory where all your other projects are located (on Vista/Win7 that is C:\Users\username\Workbench ES2\). I am not exactly sure why, but I think because the model generated classes are mostly temp files that don’t have to be checked into the server (downside is that you need to backup modifications of custom classes yourself).

That ‘temp’ folder that stores all model generated classes is much deeper on your disk drive. On my system it’s C:\Users\username\AppData\Roaming\Adobe\LiveCycle\ES2\Guides\generated\. Here you find subfolders structured per LiveCycle application. For your project, find the folder where the generated myModel.as and myModel.swf files are located. Consider this folder the ‘root’ that is used by the compiler, so this is where yoy copy your custom validator classes to.

The last step is to define the style validation annotations within the property. Basically you’d define your property like this:

<property type=”string”>
<style>
<validation>
<annotation name=”ActionScriptValidator”>
<item name=”ValidatorClass”>mx.validators.SocialSecurityValidator</item>
<item name=”allowedFormatChars”>”-()”</item>
</annotation>
</validation>
</style>
</property>

The ValidatorClass item defines the class path, and in this case the ‘allowedFormatChars’ is one of the parameters that is used by that class. Now make sure that Workbench recompiles your class (just move an entity a few pixels, save and the recompile will hapen). Now your custom validator class is compiled into the model itself and you are ready to use the related properties within your guide!

ps: Workbench will inform you on compilation errors if you made errors in your class.

Published by Marcel Van Espen under Uncategorized

On Tuesday March 16th from 13:00 to 16:00 we will be hosting an additional session on LiveCycle ES under the hood. No slides, no clickthrough demo’s… the real thing. We’ll build an application that will touch on all of the important features within LiveCycle ES. That means, we will use tool as Flash Builder, Workbench, Designer to create an application. You can sit in and watch and come with questions and remarks…. Let me know if you want to join. The session is at our office in Amsterdam.

Published by Marcel Van Espen under LiveCycle ES,LiveCycle Output ES,LiveCycle Workbench

Very soon a connector for MS Sharepoint Server will be released. This offers bi-directional integration options to either connect to Sharepoint from a LiveCycle process, or to connect to a LiveCycle service from a Sharepoint document/folder.

I have recorded a demonstration that shows you how to store the result of a forms process in LiveCycle in a Sharepoint folder. I have used a very simple holiday request form that is filled in from the LiveCycle Workspace. After filling it in a static PDF is generated using the Output service and the result is stored into Sharepoint using one of the standard services. Check out the recording on www.vimeo.com/9378807

Published by Marcel Van Espen under Adobe AIR,Adobe Flex,LiveCycle ES,LiveCycle ES Content Services,LiveCycle Output ES,LiveCycle Process Management ES,LiveCycle Workbench

Look at these videos that demonstrate how you can use LiveCycle ES to build a process and an AIR application to publish tweets to a corporate Twitter account where you have control on what’s published or not. Part 1 focuses on building the client with Flash Builder 4 with the LC Service Discovery plugin. In part 2 you will see how to archive all tweets in a PDF/A format within LiveCycle Content Services.

Part1: www.vimeo.com/8886180

Part2: www.vimeo.com/8886413

Published by Bart Vossen under LiveCycle ES

Published by Marcel Van Espen under LiveCycle ES,LiveCycle Forms ES,LiveCycle Output ES

As many people know, e-Invoicing is gaining a lot of traction these days in order to save money. In general many of the solutions use PDF as the format for the electronic invoice. But there is PDF and PDF. We have created a sample electronic Invoice in PDF format that is more then just a digital invoice, and also focuses on the experience of the recipient in addition to the ability to exchange structured data. Have a look at a video that includes a demo. If you would like to download the sample and play with it yourself, here it is.

Published by Peter Schellemans under LiveCycle Designer,LiveCycle Forms ES

A while ago the Adobe Benelux presales team had the pleasure to attend a presentation by Logica, who explained the Form-O-Matic solution. This is a framework which is orginaly built as add-on for SAP Interactive Forms by Adobe, but can be used as well within the standalone LiveCycle Designer on xdp forms. With this framework, you can produce interactive forms in an instant with a minimum of technical know-how.

Logica’s Form-O-Matic is a solution which:
- is smart, because it provides a fast way of developing interactive forms which decrease the likelihood of errors and reduce costs.
- is uniforn, fast and controllable. This is thanks to a unique development method based on the inputting of standard parameters. Doing so the development time is reduced by more than 50%.
- is simple and optimised. Form-O-Matic can be adapted very rapidly to your organisation’s requirements, for example in terms of the house style and design of the form and the naming of each parameter.
- provides simple error detection. By using the debug mode in Form-O-Matic, a single parameter enables all dynamic actions to be displayed in text on a separate screen.

We have seen Form-O-Matic in action, and it can shorten the lead time for development of Interactive Forms, and provide error detection. It reduces the aftercare of the Form, and it is quickly to implement, and easy to use and maintain.

See also the following factsheet about Logica’s Form-O-Matic.

For more information you can reply on this post, or contact Logica directly through erp.nl@logica.com

Published by Waldo Smeets under Dr LiveCycle Question

Disease:
After installing a new Jboss turnkey instance of Adobe LiveCycle, some people run into an issue when the LiveCycle Configuration Manager is doing it’s work. At about 40%, the configuration manager might display the following error:

Failed on ‘Verifying JBoss for Adobe LiveCycle ES service is installed’
Windows turnkey service JBoss for Adobe LiveCycle ES does not exist

When checking in the Windows Service Panel, indeed there is no such service defined, even though the installer should have created it. I have not been able to replicate this issue, but it happened to me at a customer site and by searching Google it seems that others have run into it as well.

Prescription:
The Google search results tells us that some people forget to set the Java_Home system variable and that you should be using the right version of the JDK. However, this did not seem to be the problem in this case.

Through the install documentation you can find the steps needed to re-create the JBoss for Adobe LiveCycle ES service (page 62). You can use those to try and create the service ‘manually’. For our install, the problem seemed to be in the [LC_INSTALL_ROOT]\jboss\InstallJBossService.bat script file. Somehow the username / password did not seem to work, whatever we tried it failed. Well, sort off: strangely enought the command prompt output first mentions that there was an error, though still reports that the script was executed succesfully. Still no service created though.

The solution was too simple to come up with: just remove the username / password parameters from the script and execute it. This time the script did not fail and as expected created the service for us. Next thing to do is go into the service panel, select the ‘JBoss for Adobe LiveCycle’ service, right click to go to it’s Properties and in the Log On tab specify Log In As This Account. Then specify the username password (in my case “.\administrator” and the password), click OK and you are done.

Now run the LiveCycle Configuration Manager again and most likely it won’t fail anymore cause of the missing service. This seemed to have overcome our issue.

Tip to stay healthy:
When installing the turnkey solution, it is highly recommended to keep the right documentation at hand: Installing and Deploying LiveCycle® ES Using Turnkey.

Did you run into this issue as well? Please let us know if this worked for you or if you have additional tips for our readers.

Published by Peter Schellemans under LiveCycle Digital Signatures ES,LiveCycle Rights Management ES

Disease:
Typically LiveCycle Rights Management (a.k.a. Policy) protected documents use a userid/password mechanism for authenticating towards the policy server, and consequently open the protected document. A more secure way of authentication can be obtained by using client certificates. A real strong way of authentication can be accomplished when the authentication certificate resides on a smartcard, protected by a PIN code. The authentication certificate on the Belgian eid card is such an example. How can that be used to authenticate towards a Policy protected document?

Prescription:
To achieve this follow these steps:
1) First of all the authentication certificate must be known/registered/uploaded to the LiveCycle server. Open the adminui –> Settings –> Trust Store Management –> Certificates.
When importing the .cer file, specify that you want to trust the certificate for “Certificate Authentication”, and provide an alias.

2) Next this certificate must be mapped to an existing user in LiveCycle.
Open the adminui –> Settings –> User Management –> Configuration –> Certificate mapping.
The mapping between a certificate and a user is done for a defined alias, and is accomplished by mapping a certificate attribute (Mail, CN, DN,… ) to a user property (Full Name, Given Name, Mail, login ID, …).

In the case of the Belgian eid card the CN on the authentication certificate contains also the word “Authentication”. In my case my CN = Peter Schellemans (Authentication). So in order to get a working certificate mapping towards an existing user, make sure you have a user with a similar Full Name. In my case I have a user (adminui –> Settings –> User Management –> Users and Groups) with First Name = Peter, Last Name = Schellemans (Authentication).

3) Next add this user as part of your Policy. When opening the policy protected document you will now get the choice between userid/password authentication and client certificate authentication.

Tip to stay healthy:
If you want a higher level of security when authenticating towards a policy protected document, Adobe LiveCycle allows you to map certificates towards users, used in a policy definition.

Published by Marcel Van Espen under LiveCycle ES PDF generation,LiveCycle Workbench

You probably know the case, you want to convert a file to PDF and add a fax page so you can send it to a customer using your fax-server, or you just want to add a coverpage so you can archive the file in a effective way and have all the metadata nicely grouped on that coverpage.

There are simple ways to let LiveCycle ES take care of that process for you. Below a short explanation of some of the available services that are relevant in this context.

Within LiveCycle Workbench ES, one of the services in the common category that you can use is “Export XMP“. This service will extract all the available metadata from a PDF document. If you have converted a MS-Office document to a PDF document, you will be surprised what metadata is also converted. All these properties are now accessible using the service above. Here is a screenshot of some custom properties in a Word document.

Result of the Export XMP service is an XML structure that you can query. For instance, if you want to know what’s in some of the custom metadata fields, you can check this file. Here is a sample of the result of an Export XMP service.

<?xpacket begin=”” id=”W5M0MpCehiHzreSzNTczkc9d”?>
<x:xmpmeta xmlns:x=”adobe:ns:meta/” x:xmptk=”Adobe XMP Core 4.2-jc015 52.349034, 2008 Jun 20 00:30:39-PDT (debug)”>
<rdf:RDF xmlns:rdf=”www.w3.org/1999/02/22-rdf-syntax-ns#”>
<rdf:Description rdf:about=”"
xmlns:xmp=”ns.adobe.com/xap/1.0/“>
<xmp:CreateDate>2008-12-23T09:45:28+01:00</xmp:CreateDate>
<xmp:CreatorTool>Acrobat PDFMaker 9.0 for Word</xmp:CreatorTool>
<xmp:ModifyDate>2008-12-23T09:45:28+01:00</xmp:ModifyDate>
<xmp:MetadataDate>2008-12-23T09:45:28+01:00</xmp:MetadataDate>
</rdf:Description>
<rdf:Description rdf:about=”"
xmlns:pdf=”ns.adobe.com/pdf/1.3/“>
<pdf:Producer>Acrobat Distiller 9.0.0 (Windows)</pdf:Producer>
<pdf:Keywords>”PDF, Metadata”</pdf:Keywords>
</rdf:Description>
<rdf:Description rdf:about=”"
xmlns:dc=”purl.org/dc/elements/1.1/“>
<dc:format>application/pdf</dc:format>
<dc:creator>
<rdf:Seq>
<rdf:li>Marcel van Espen</rdf:li>
</rdf:Seq>
</dc:creator>
<dc:title>
<rdf:Alt>
<rdf:li xml:lang=”x-default”>This is a test document</rdf:li>
</rdf:Alt>
</dc:title>
<dc:description>
<rdf:Alt>
<rdf:li xml:lang=”x-default”>Onderwerp</rdf:li>
</rdf:Alt>
</dc:description>
<dc:subject>
<rdf:Bag>
<rdf:li>PDF, Metadata</rdf:li>
</rdf:Bag>
</dc:subject>
</rdf:Description>
<rdf:Description rdf:about=”"
xmlns:pdfx=”ns.adobe.com/pdfx/1.3/“>
<pdfx:Company>Adobe Systems Incorporated</pdfx:Company>
<pdfx:Department>Development</pdfx:Department>
<pdfx:Language>English</pdfx:Language>
<pdfx:Office>Amsterdam</pdfx:Office>
</rdf:Description>
</rdf:RDF>
</x:xmpmeta>
<?xpacket end=”w”?>

Now, you will see some familiar tags in there. If you would like to access the custom property Office (With value Amsterdam) as highlighted in bold above, you will need to do the following:

1. Store the result data from the Export XMP service in a variable of type XML (for this example this will be xmpdocxml)
2. Create a variable of type string (In this case it will be office) to store the office location (of course you can also put it in a form template, but this is out of scope for this example)
3. Use a set value service to set /process_data/@Office = /process_data/xmpdocxml/x:xmpmeta/rdf:RDF/rdf:Description/pdfx:Office