Forms from Designer 6 to LiveCycle ES2 Designer (9)

[YogLC]

Hi All,

I have forms (xdp) designed in Adobe Designer 6 (and used with Adobe Form Server 6) and now want to use them with LiveCycle ES2 (Form ES2), what is best approach, e.g. may be first open and save in Designer 8.2 and then open 8.2 version in ES2 (Designer 9) and save it.

What should be testing approach?

Please help.

Thanks

YogLC.

[Niall_O_Donovan]

Hi,

I haven't done this, but I would try a sample form going straight to LC Designer ES2, as it should bring the version 6 form up to date.

After you open the form in LC DEsigner ES2, save it and then check the XML Source tab. The namespace should be updated to 2.8.

Hope that helps,

Niall

[YogLC]

Thanks a lot,

A sample before and after I tried to open in Livecycle ES2 Designer 9.0.0.1

How do I confirm that upgrade to Livecycle ES2 Designer 9.0.0.1 is successful ?

A blank xdp in ES2 9.0.0.1 shows the template version as 2.8 but the converted sample xdp shows as 2.4 see below.

Please help

Thanks

YogLC

A sample xdp opened designed in Designer 6 as is

<?xml version="1.0" encoding="UTF-8"?>

<?xfa generator="AdobeDesigner_V6.0" APIVersion="1.4.4136.0"?>

<xdp:xdp xmlns:xdp="http://ns.adobe.com/xdp/" timeStamp="2007-10-05T22:21:08Z" uuid="7653008d-397d-4745-b5d2-7d6a1c18021b">

<template xmlns:xfa="http://www.xfa.org/schema/xfa-template/2.1/" xmlns="http://www.xfa.org/schema/xfa-template/2.1/">

=======================================================================

A sample xdp opened in Livecycle ES2 9.0.0.1 (after Updating Rendering Model, Text Formatting, and Event Model)

<?xml version="1.0" encoding="UTF-8"?>

<?xfa generator="AdobeLiveCycleDesignerES_V9.0.0.1.20100329.2.659576" APIVersion="3.1.9277.0"?>

<xdp:xdp xmlns:xdp="http://ns.adobe.com/xdp/" timeStamp="2010-06-16T13:28:23Z" uuid="25f308cf-7817-4f1a-962f-0c8476fd0e97">

<template xmlns:xfa="http://www.xfa.org/schema/xfa-template/2.1/" xmlns="http://www.xfa.org/schema/xfa-template/2.4/">

<?formServer defaultPDFRenderFormat acrobat7.0.5static?>

<?formServer allowRenderCaching 0?>

<?formServer formModel both?>

========================================

A blank xdp created with Livecycle ES2 9.0.0.1

<?xml version="1.0" encoding="UTF-8"?>

<?xfa generator="AdobeLiveCycleDesignerES_V9.0.0.1.20100329.2.659576" APIVersion="3.1.9277.0"?>

<xdp:xdp xmlns:xdp="http://ns.adobe.com/xdp/" timeStamp="2010-06-16T13:31:35Z" uuid="034f712c-27a8-486d-8c23-56e05d396df1">

<template xmlns="http://www.xfa.org/schema/xfa-template/2.8/">

<?formServer defaultPDFRenderFormat acrobat9.0dynamic?>

[Niall_O_Donovan]

Hi,

I was not correct in the previous post - more haste, less speed.

If you look at the start of the source XML for the form, you will see the version number for LC Designer that generated the form. In this case v9.0.1

The XFA template relates to the target version in Acrobat/Reader (as set in the File > Form Properties > Defaults tab, Target version. In this case XFA Specification 2.8 = Acrobat/Reader v9.

Here is a table comparing XFA Specification numbers and the version of Acrobat/Reader supporting that spec:

XFA Specification	Supported in Acrobat/Reader Version
XFA 2.8	Acrobat/Reader version 9.0
XFA 2.7	Acrobat/Reader version 8.1
XFA 2.6	Acrobat/Reader version 8.1
XFA 2.5	Acrobat/Reader version 8.0
XFA 2.4	Acrobat/Reader version 7.0
XFA 2.2	Acrobat/Reader version 7.0
XFA 2.0	Acrobat/Reader version 6.0

So as you change the Target version in the Default tab, this XML line will change: <template xmlns="http://www.xfa.org/schema/xfa-template/2.5/">

From the Generator line, I can see that the form knows it is being opened in the latest version of LC Designer.

You just may want to change the Target Version, so that you are getting benefit of the newer features. Just remember to check the Warnings tab, in case you are building in features that are not supported by the Target version:

Hope that helps,

Niall

[YogLC]

Thanks Niall,

This helps to understand relationship between template version and Adobe reader version. I will modify couple of forms and let you know.

Thanks

YogLC

[YogLC]

Hi Niall,

After updating Properties>Compatibility and settings Target version on the old xdp I see following  xml  generated.

Does this sound right () ?

Thanks

YogLC

<?xml version="1.0" encoding="UTF-8"?>

<?xfa generator="AdobeLiveCycleDesignerES_V9.0.0.1.20100329.2.659576" APIVersion="3.1.9277.0"?>

<

xdp:xdp xmlns:xdp="http://ns.adobe.com/xdp/" timeStamp="2010-06-21T15:15:11Z" uuid="42e37fb9-0d21-499d-94bd-259200a97a10">

<

template xmlns:xfa="http://www.xfa.org/schema/xfa-template/2.1/" xmlns="http://www.xfa.org/schema/xfa-template/3.0/">

<?formServer defaultPDFRenderFormat acrobat9.1static?>

<?formServer allowRenderCaching 0?>

<?formServer formModel both?>

<

subform name="F" layout="tb" locale="ambient">

[Niall_O_Donovan]

Hi,

Yes that looks right.

Adobe LiveCycle Designer ES2 is v9.0.0.1, so that is correct.

The XML namespace is set to 3.0, which is Acrobat v9.

Good luck,

Niall

[YogLC]

Thank you,

Why does it has reference template 2.1?

If I create new blank xdp it does not have reference to template 2.1  but just template 3.0.

Thanks

YogLC

[Niall_O_Donovan]

Hi,

This is pure guesswork.

It is specifying two name spaces, one of which is specific to xfa. The original xfa specification was 2.1.

So:

xmlns.xfa = 2.1

xmlns = 3.0 // for Acrobat v9 as target

Both name spaces are specified. You shouldn't need to tweak these in the XML Source tab.

My grip on this is vague.

Niall

[Niall_O_Donovan]

You can get more details here: http://partners.adobe.com/public/developer/xml/index_arch.html

Niall

[YogLC]

Thank you for your all the help Niall.

YogLC