Trying to understand this whole Reader Extension product


hello,

i'm trying handle on how whole extensions thing works. we're using lifecycle designer 7 generate forms (both , xdp , pdf). want our users able access data odbc connections , potentially wsdls. our clients (right now) use free reader 7.0.x.

it's understanding pdf in case needs 'extended' in case. purchase extension form $x. valid scenario.

pdf/xdp generated. pdf 'sent' extension server sort of encryption free reader understands , enables data access capabilities. user free use form , it's data access capabilities in perpetuity. it's 1 time fee 1 form.

if true, then...

where extension server encypts form?

does free reader have validate against or other server enable data access capability?

what happens if form changed?

this might now.

thanks,
bob

reader extensions server product, don't purchase "extending job" on specific form adobe, purchase server product adobe. there partners offer service of reader extending form on form form basis.

reader not have validate against server. reader extensions takes in pdf, , spits out extended pdf. when extended pdf opened in reader, reader knows needs provide functionality , functionality is.

if change form after reader extended need reader extend again. mean changing form design, not user entering data in fields.

chris
adobe enterprise developer support


More discussions in LiveCycle pre-ES (6.x and 7.x) discussions


adobe

Comments