Posts in Category "Designer"

LiveCycle Designer ES2: Designer hangs after renaming the binding file

Issue

While editing an XDP in certain versions of LiveCycle Designer ES2, if the data binding file on disk is renamed, designer registers this change and offers to reload the current form.  If you then click Save, it again offers to reload the current form.  After clicking “Yes” to reload the form, you may notice that Designer hangs.

Method:
1. Download test_files.zip
2. Extract the 2 files to the same local folder
3. Open XDP in Designer
4. Rename the binding XML file in your local folder
5. You will see a dialog in Designer asking to reload the form, click Yes
6. Click Save
7. Again the dialog in Designer asking to reload the form, click Yes

Result:
Designer hangs

Solution

This is an issue in certain versions of LiveCycle Designer ES2 and has been addressed in later versions, including Designer ES3.  If you require a quickfix for this issue in LiveCycle Designer ES2 you should contact the enterprise support team.

reference: (183667516/3337854)

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

LiveCycle Designer ES2: Multiple pages imported to a single Master Page causing overlap

Issue

If you are importing a multi-page PDF into LiveCycle Designer ES2 to create a form using the “…Flowable Layout > Place Content In > Master Pages” method you may notice that the content of the pages are placed in a single Master page causing overlap.

Solution

This is an issue in LiveCycle Designer ES2 and has been addressed in later versions, including Designer ES3.  If you require a quickfix for this issue in LiveCycle Designer 9 you should contact the enterprise support team.

reference: (183629724/3337453)

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

LiveCycle Designer ES2: Corners appear unexpectedly when clicking on hidden rectangle object

Issue

If you are editing older XDP forms from LiveCycle Designer 7.1, or 8,  in Designer ES2, and you have hidden rectangle objects in the form design, you may notice that when selecting these hidden objects in the hierarchy, visible corners suddenly appear on these objects.  These hidden rectangle objects are created automatically when importing Word documents into Designer to create a form.

Reason

The problem is caused by the import from doc/PDF where the edge property for the rectangle is created and set to hidden, but no corners property is created.  When you create a new form in Designer (without importing), the edge and corner properties for a rectangle are always created together and the presence for both usually kept in synch.
It seems that when Designer finds a rectangle without a corner property it creates it automatically with visible corners.

Rectangle in XML after import from word:
               <rectangle>
                  <edge thickness=”0pt” presence=”hidden”/>
               </rectangle>

Rectangle in XML after selecting it on canvas:
               <rectangle>
                  <edge thickness=”0pt” presence=”hidden”/>
                  <corner radius=”5.08mm”/>
               </rectangle>

Rectangle in XML after manually fixing it in Designer (XML Source or Object Palette):
               <rectangle>
                  <edge thickness=”0pt” presence=”hidden”/>
                  <corner radius=”5.08mm” presence=”hidden”/>
               </rectangle>

Workaround

You can change the line style to “solid” and back to “none”, and then the corners property in XML is synchronized (presence=hidden) with the line edge property as expected.

Solution

This is an issue in LiveCycle Designer ES2 and will be fixed in Designer 10 and later versions.  If you require a quickfix for Designer 9 you should contact the enterprise support team.

The logic has now been changed, so that when Designer creates the corner property, it checks if the relevant edge is hidden, and sets the presence for the corners to match.

reference: (183589079/3322036)

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

LiveCycle Designer ES2: Unable to delete default value in rich-text fields

Issue

After updating to LiveCycle Designer ES2 QF4 (9.0.0.2.20110401.1.827986), you may notice that you are no longer able to delete the default value in rich-text fields.  It is possible to edit the value, but when you delete it, the value will re-appear in the field after refreshing.  This only happens for rich-text fields and not standard text fields.

Solution

This is an issue in LiveCycle Designer 9.5 QF4 and has been addressed in later versions, including Designer 10.  If you require a quickfix for this issue in LiveCycle Designer 9 you should contact the enterprise support team.

Workaround

You can delete the default value by opening the XML Source tab and removing the value manually.

reference: (183571067/3318438)

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

LiveCycle Designer ES2: Word (version XP or onwards) could not be found on the machine

Issue

If you are using LiveCycle Designer ES2 to import Microsoft Word documents from MS Word 2010 or later, you may receive the following error

Word (version XP or onwards) could not be found on the machine

Reason

This error occurs because LC Designer ES2 does not recognise the installation folder for Microsoft Word 2010 or later versions.  LiveCycle Designer ES2 was released before these versions existed and therefore the installation folders were not known/recognised.

Solution

This issue has been fixed in LiveCycle Designer ES3 and last cumulative QuickFixes (QF) for Designer ES2.  Ensure you are using the latest QF for Designer ES2, or request the latest from your support representative.

If you require an urgent fix for this issue you can make the following change in the registry:

Note: we cannot provide support for any problems that may arise as a result of modifying the registry.  Only an experienced user or an administrator should attempt this, and a full registry backup should be performed before making changes.

1. For 32-bit Windows:

  • Create the following path in the registry:
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\Word\InstallRoot
  • Create a new string value named Path with value C:\Program Files\Microsoft Office\Office14\

2. For 64-bit Windows

  • Create the following path in the registry:
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\12.0\Word\InstallRoot
  • Create a new string value named Path with value C:\Program Files (x86)\Microsoft Office\Office14\

You should check the installation folder used in the Path value exists and contains WINWORD.EXE.  You will need to restart LiveCycle Designer for the changes to take effect.

Additional information

This issue is also being discussed in the forums:

http://forums.adobe.com/message/3983628

reference: (183608560/2751566)

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

LiveCycle Designer ES2: Unable to save old XDPs with external data binding option

Issue

If you are attempting to save an XDP file in LiveCycle Designer ES2, created with an earlier version of Designer (i.e. 7, 7.1 or ES), then it can occur that the Save process never completes, and you must kill the Designer process manually in Task Manager.  If you analyse the files on your local disk, you will notice some tmp files with large file sizes.

Reason

This issue is related to the Data Binding option Allow binding to data not defined by the default data connection.  For some forms that contain data connections, Designer ES2 can get stuck in an endless loop while saving the XDP to an intermediary tmp file.  You will see the tmp file will contain a huge number of repeated entries related to the DataDescription similar to the following:

<DATACONNECTION xmlns:dd=”http://ns.adobe.com/data-description/” dd:additions=”$template(DATACONNECTION)”/>

Solution

This issue has been fixed in LiveCycle Designer ES3 and later cumulative QuickFixes for Designer ES2.  You should ensure you are using the latest QF for Designer ES2, or contact your support representative.

Workaround

Removing the data connection will allow the file to be saved, and also disabling the option in the form properties Allow binding to data not defined by the default data connection.  Also putting the sample XML data/schema file used to create the data connection into the same folder as the XDP, opening the XDP, refreshing the Data connection, will then allow to save properly.

reference: (183464630/3296440)

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

LiveCycle Designer: XFAImageService error importing a Photoshop JPG into an XFA form

Issue

 If you are trying to import JPEG images produced with Adobe Photoshop into an XFA-based form in LiveCycle Designer, then you may notice the following error in the warning palette:

Error reading JPeg file : JFIF supports only 1 and 3 component streams. 

XFAImageService: Image cannot be resolved for node: StaticImage1

Solutions

 1. Use Photoshop version 6 or less to produce the JPEG images

2. Re-save the JPEG images from Photoshop using the “Save for Web…” option in the File menu

3. Re-save the JPEG images using Paint in windows, or any other image editing tool which does not add the preview information described below

Additional information

 This error occurs when Photoshop 7 or greater was used to create the JPEG images.  This is due to a change in the JPEG format produced with Photoshop 7 and greater, which now includes a thumbnail preview of the JPEG image included in the JPEG profile.  Such profile information does conform to the JPEG/JFIF specification, however some applications like web browsers, or in this case, LiveCycle Designer cannot handle the preview data correctly.

Further information can be found below:

http://photo.net/ps7-problems.html

reference: (182368249)

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

LiveCycle Designer: flowed layout in header/footer subforms incorrect

Issue

When you use flowed subforms that repeat on pagination (that is, after pages break), some fields in the subform are rendered on top of other fields.  This can occur in all versions of Acrobat/Reader and LiveCycle.

Solution

You cannot use a flowed layout for subforms that are set up to repeat on pagination, as header or footers to pages.  The objects in the subform aren’t positioned correctly after the page-break and overlapping can occur.

Use a positioned layout for these subforms, rather than a flowed layout. You can change the layout of the subform in LiveCycle Designer. Select the subform, and then choose the Layout tab from the object panel on the lower right.

Additional information

Extract from the XFA Specification 3.1 (Page 277):

“Flowing Layout for Containers…

Error Condition: Inappropriate Layout Strategy:

Flowing layout applied to a subform that is a leader or trailer or is contained within a leader or trailer subform (because the leader or trailer size is fixed).”

reference: (181804954/2724676)

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

LiveCycle Designer: Render a trailing page in a form for duplex printing

When you use duplex printing (that is, printing on both sides of the paper), you can print a separate blank trailing page. To print a trailing page, the last page must always have an odd page number (that is, page 1, 3, 5, 7, and so on). When the last page is odd, it prints on a new sheet of paper separate from the rest of the form.

Render a trailing page in LiveCycle Designer 7.x

LiveCycle Designer 7.1 includes a script for rendering a trailing page.

To make sure that the last page has an odd page number, do the following:

  1. insert a blank hidden body page in the form just before the page you want to use as a trailing page.
  2. insert the following script in the layout:ready event of the form to show/hide the blank page at run-time:
var pageCount = xfa.layout.pageCount();

if(pageCount%2 == 0) {
    //even, show the blank page to shift the trailing page down to an odd page number
    form1.blank_page.presence="visible";
} else {
    //odd, hide the blank page as the trailing page is already on an odd page number
    form1.blank_page.presence="hidden";
}

Note: The layout event ensures that the trailing page always falls on an odd number, even if the end user alters the form contents. Such alterations cause the layout:ready event to run and adjust the page numbers accordingly.

Rendering a trailing page in LiveCycle Designer ES

LiveCycle Designer ES includes functionality in the Master Pages to handle duplex printing.

  1. Add Master Pages for odd/even numbers, for the last page, and for the blank page.
  2. Using the Printing option in the Master Pages page set, set up the form for duplex printing.
  3. For the odd/even Master Pages, choose the appropriate option in the Master Page >Pagination tab under Odd/Even.
  4. For the last page, choose the Last Page option in the Master Page > Pagination tab under Placement.
  5. For the blank page, choose the Blank Pages option in the Master Page > Pagination tab under Odd/Even.
  6. For the body page that occurs just before the trailing page, choose Go To Even Page in the After settings under the Pagination tab.

Sample files

Here are some sample file showing the solutions as outlined above for Designer 7.1 and ES.  I have included some test data files also to test the solutions with different page numbers.  You can import the data files into the XDP templates using Designer to test the solutions.

sample_files

reference: (181512630)

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

LiveCycle Designer 7.1: Cannot find Designer.xdc error starting client

Issue

 If you have installed Designer 7.1 and you receive an error message on starting the client that it cannot find Designer.xdc, then it looks like you have a corrupt installation.  This can occur if you attempt to install a newer patch version of Designer 7.1 on top of an existing installation.

Solution

 You must always completely uninstall an existing Designer 7.1 installation, before you attempt to install a newer version.  You should use the Add/Remove Programs option in the Windows control panel to uninstall the older version.

reference: (181304492)

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

LiveCycle Designer: Wrong type parameter supplied to a PDS procedure

Issue

 If you are using Designer to preview an XDP in the PDF Preview tab, you may receive the following error:

Wrong type parameter supplied to a PDS procedure

Reason

 This error usually appears when the XML structure is no longer valid, i.e. it has been edited manually.

Solution

 Open and save the form in Designer7.1, then it will correct any problems in the XML source, and work fine in PDF Preview.

Opening in Designer8.0 and later versions will also correct any issues.

reference: (1-33514950)

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

LiveCycle Designer: Bad value ‘#f1′ of the ‘use’ attribute of ‘font’ element

Issue

When you are working with Designer to edit form you may see the following warning in the report palette:

"Bad value '#f1' of the 'use' attribute of 'font' element - Default will be used."

Reason

You may see this error if you delete the “Referenced Objects” node in the Designer hierarchy.

Referenced Objects refer to any repeating objects in the form, fonts, images etc… You can define an object and its properties in the <proto> node in the XML and then just call it many times using its ID through the “use” attribute.

If you delete the Referenced Objects object, the <proto> tag will be deleted, and so the object definitions along with it. The “use” attributes will not be mapped to any object definition and so will result in this warning.

Solution

Refer to the XFA 2.4 specification, where, on page 194 it describes how to define these objects in the proto node.

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

Acrobat/Reader 8+: how to disable tabbing for read-only fields

Issue

If you have upgraded from Adobe Reader 7 to a later version and your forms contain read-only fields, you may have noticed that you can now tab into those fields in Reader 8+.  This was not possible in Reader 7 and earlier.

Solution

As a workaround, change the access property value for the fields you want to remove from the tabbing order from “readOnly” to “protected” in your XDP forms. Fields marked as “protected” do not participate in the tabbing order.

Alternately, write a script to change the access property from “readOnly” to “protected” in your XDP XML source code.

Additional Information

The tabbing feature has been documented for read-only fields since Designer 7.1 but has only been enforced in Acrobat/Reader since version 8. The necessity for tabbing into read-only fields comes from the Accessibility standards. Screen readers must be able to read the read only fields on the page, and screen readers work off the tabbing order.

This is the correct behaviour for read-only fields.

The “protected” option is not available in Designer 7.1 but is available in later versions. If you require this option in Designer 7.1, contact Adobe support to request a patch for Designer (you need a valid M&S contract to request this patch).

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

LiveCycle Designer: Processing Instruction <?templateDesigner StyleID aped3?> duplicated many times

Issue

You may notice your XDP files are bloating in size when you are working with Designer ES 8.2.1.  A simple XDP file of 100kb could easily bloat up to 5MB.

Reason

The StyleId processing instruction “<?templateDesigner StyleID aped3?>” is being duplicated many times in the XDP source.

Solution

This issue is fixed in Designer 8.2.1 SP2, and in Designer 9.  You can delete these duplicate processing instructions in the XML Source for your existing XDP files.

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

LiveCycle Designer7.1: field re-sizing not working for left-handed mouse users

Issue

 When switching mouse Primary and Secondary Buttons (i.e. from right-hand to left-hand setup), you will not be able to change a field size with the mouse.

1-Switch the mouse primary and secondary buttons:

Click on Windows Start Button -> Control Panel -> Select Mouse -> Tick “Switch Primary and Secondary Buttons” -> click Apply and then OK

2-Create a new form with Designer 7.1 and add a text field

3-Try to change the text field’s size with the mouse. This will not work.

It is expected that the field’s size can be changed by left handed users

Reason

This is a bug in Designer 7.1.

Solution

This has been fixed in Designer 8.0. and later.

reference: (1-28063550/1341841)

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