Archive for March, 2009

Visible (Print Only) presence option may not work on button objects when target version is Acrobat and Adobe Reader 7.0.5 or later

The Visible (Print Only) option is available in the Presence list on the Object palette. When you apply the Visible (Print Only) option to an object, the object appears only when the form is printed, and does not appear when the form is viewed on-screen.

However, when you select Acrobat and Adobe Reader 7.0.5 or later as the target version for a form, and apply the Visible (Print Only) presence option to a button object, the option may not work on the following versions of LiveCycle Designer:

– LiveCycle Designer 7.0 and 7.1
With dynamic PDF forms that are migrated to LiveCycle Designer 9.0 and then opened in Acrobat or Adobe Reader 8.0 or later, the Button object may be invisible when the form is printed.

– LiveCycle Designer 9.0
With static and dynamic PDF forms, the Button object may still be visible on the screen when you view the form by using the Preview PDF tab in LiveCycle Designer 9.0 or open it in Adobe Acrobat 7.0.5 or later.

Note: This issue does not occur in Adobe Acrobat 8.0 with dynamic PDF forms.

To resolve these issues, you must carry out these four steps for each Button object that you want to show or hide in Acrobat and Adobe Reader 7.0.5 or later:

1. Click the Button object, and in the Language list in the Script Editor, select JavaScript.
2. In the Presence list on the Object palette, select Invisible.
3. Copy and paste the following script into the prePrint event in the Script Editor.
this.presence = “visible”;
4. Copy and paste the following script into the postPrint event in the Script Editor.
this.presence = “invisible”;

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 10.0/10 (1 vote cast)

Tech Notes since November

It’s been a while since we gave an update on tech notes. Here’s the list of Knowledge Base tech notes that the LiveCycle ES documentation team has published since November:

• Upgrade process for LiveCycle Business Activity Monitoring ES, version 8.2.1
• LiveCycle Content Services ES Service Pack 1 turnkey requires default directory configured
Column names in a database used for supplying form object values should not differ by case only
• How to create a custom dictionary for use in LiveCycle Designer ES
• Visible (Print Only) presence option may not work on button objects when target version is Acrobat and Adobe Reader 7.0.5 or later
• Modifying sourceSet in XFA 2.5+Forms
Compiling custom form guide components with more recent versions of Flex SDK (LiveCycle ES)
Kerberos authentication between multiple domains may fail on LiveCycle Rights Management ES 8.2.1
• Unable to stop clustered LiveCycle ES server from WebSphere Administration Console
•Out of Memory errors with LiveCycle ES (8.2.1.2) installation on JBoss and MySQL
• LGPL library, JCIFS modified for LiveCycle ES Update 1 Quick Fix
• Clarification of XPath XML usage changes introduced in LiveCycle ES 8.0.1.1
• LiveCycle Workbench ES installation issues a false warning that Adobe Flash Player is not installed
• LiveCycle Designer ES 8.2 conflicts with Microsoft SQL Server 2008 when installed on the same computer
• Out of Memory errors with LiveCycle ES JBoss turnkey installation
• Using the proper Workspace ES source code for patched versions of LiveCycle ES

Other LiveCycle ES teams (like Adobe Support) also publish tech notes. You can search the Knowledge Base for a complete list of tech notes that were published within the last few months.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

A simple script that lets you calculate an amount based on a user’s input

It’s getting close to tax time here in Canada and I’m thinking about my retirement plan contributions. While looking at the Federal tax form online, I thought about how nice it would be if the form could calculate an amount based on my input. So I created a little script in LiveCycle Designer ES that calculates how much I can deduct based on my Registered Retirement Savings Plan (RRSP) contributions. Of course, the percentage I used for the calculation is purely fictional and the Canadian Government would never let me send in my own version of the form!

I used the response method to create the dialog box that contains the question and entry field. The following message box appears when I tab to the field.

RRSP_Message_Box2.gif

Here is the calculated field:
RRSP_Result2.gif

To create the calculation in this example:
1. In Designer ES, drag a Decimal Field object onto the form design.
2. In the Field tab, select a pattern for the field. In this example I selected a predefined display pattern (num{($z,zz9.99)}).
3. In the Script Editor, select the Enter event, JavaScript language, and run the script at the Client.
4. Copy and paste the following script into the Script Editor.
var RRSPResponse = xfa.host.response("What is your total RRSP contribution for the year ?", "RRSP Contribution", "", false);
$.rawValue = RRSPResponse * 0.536;

5. Save the form as a PDF file.

Now you try it and have fun!

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

Dymystifying application configuration for LiveCycle Workspace ES

Creating human-centric processes for LiveCycle Workspace ES can be tricky when you want to include operations from Signatures, Encryption, Rights Management, and Reader Extensions services in your process. There are a few technology nuances that can make it seem more difficult to configure human-centric applications than it should be. New to our LiveCycle ES 8.2 documentation set, is a guide on helping experienced developers understand recommended techniques for creating human-centric processes. These techniques include best practices, tips, and references to existing LiveCycle ES documentation. This new guide, Techniques for Configuring Applications for LiveCycle Workspace ES, can help you to design processes to meet your business requirements and provide an optimal experience for your Workspace ES users.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

Using web services to search for Rights Management events

The Rights Management service tracks specific actions as they occur, such as when a policy is used to protect a PDF document or when a policy-protected document is opened. You can develop client applications that are able to search for Rights Management events. Because the Rights Management service exposes a public WSDL, you can create a proxy library that consumes the WSDL and use the proxy library in client applications built with development environments that support web services such as Microsoft Visual Studio.

When creating a proxy library that consumes that Rights Management WSDL, the proxy library has access to data types exposed by the Rights Management WSDL. These data types include EventSpec and AuditSpec. For more information, see Searching for Events.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

Displaying process data in Flex controls

LiveCycle ES enables you to invoke processes created in Workbench ES using a client application built with Flex. A benefit of creating a client application with Flex and using it to invoke a process is that you have access to a rich set of Flex controls. That is, you can display process data in controls such as a pie chart or bar graph.

The Displaying LiveCycle ES process data in Flex graphs article discusses how to display process data in a client application built with Flex. Basically, you have to first create a process using Workbech ES. Then you can invoke the process from the client application and retrieve the process data. You can then use the process data to populate a control. For more information, check out Displaying LiveCycle ES process data in Flex graphs.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)