Posts tagged "workbench"

LiveCycle Workbench ES2: duplicate body tags when saving a form with floating fields

Issue

When using LiveCycle Designer 9 through LiveCycle Workbench 9 to create and modify XDP templates with static text and floating fields, you may notice that saving the form in this situation creates duplicate <body> nodes in the XML source.

There is an issue with the integration between Workbench and Designer and the auto-checkout functionality when saving changes to a file.

Solution

This issue will be addressed in a future release. Currently there is a quick fix available for LiveCycle ES2 SP2. Contact Adobe Enterprise Support to obtain this quick fix.

As a workaround you use the Save button on the Designer toolbar, rather than the File>Save menu item.

Additional information

 This issue can be reproduced using the following steps:

  1. Open Workbench 9.5.
  2. Create new application.
  3. Right-click new application and create new form in Workbench, click Finish.
  4. Add a static text object.
  5. Menu: Insert->Floating field.
  6. Save and close XDP.
  7. Checkin form in Workbench.
  8. Double-click form in WB to open in Designer.
  9. Delete some chars from static text label.
  10. Click on File menu (yes to checkout).
  11. Then view XML.

Result:

Duplicate <body> node in the static text field object.

This behaviour means that only the first node, with the old text label, will be used when the form is rendered, and shown in Designer design view.  It also produces an “Invalid append operation” error in the server log, and in Designer log.

reference: (181920824/2777586)

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

LiveCycle Workbench: which URLs are used for communication with LC server

Information

 If you are using a proxy between Workbench and the LiveCycle ES Server, you may want to limit the connection to provide a higher level of security.  For the standard installation Workbench communcates with the LiveCycle server over HTTP with servername and port number as follows:

http://<server>:<port>

Using a proxy server, you could limit the connection further to just two URLs:

http://<server>:<port>/DocumentManager
http://<server>:<port>/soap/sdk

This is subject to change, especially in later versions and must be tested thoroughly to ensure there are no conflicts or unexpected problems.  Adobe will investigate issues related to such a configuration but in some cases the only solution may be to return to the default settings, without limiting the connection to specific URLs.

reference: (181300310)

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