I would suggest you get access to the server, and try to open a Word
document using it's installed version of MS/Word.I suspect it may have
an expired license or some other issue that it is trying to present via
the UI - that PDFG has no ability to report.Just a guess.Good LuckMark
You might want to take a look at subform/field bindings, and initialize
events.If you have a binding to a repeating element, check your
scripting and initializations.It may be that you are appending to a
structure each time you initialize the form - even if it already
exists.I have reviewed forms that had subforms set to repeat based on
binding to elements, and a script that was adding an instance each time
the form initialized.Not saying that's happening here - just throwing it
out there.Sounds...
Creating Custom Component information can be found here:Adobe LiveCycle
* Creating Your First Component As far as SFTP goes, I would suggest
creating a project in Eclipse, and get the Java SFTP code working
outside of LiveCycle.Once you are confident that your code is running
right, then make the conversion into a Component - that will isolate
Component issues from SFTP issues.In the past I have found Java SFTP
routines to use as 'seed' code on the internet. Used Eclipse to make
them into what I...
I believe the information you are looking for can be found in the
Acrobat JavaScript Scripting
Reference.http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/Acro6JS.pdf
Specifically, the 'printParams' object - 'pageHandling' object.Good
LuckMark
I believe what you want to do is use the PreSign Event of the signature
field to evaluate the data condition(s), and set a True/False return
value.Look at the event documentation in Designer Scripting Reference -
If you set it one way, the signature will happen - the other way and it
will be prevented.Mark
Hello,In looking at your PDF, I get the same result of data not
persisting when Reader Extended.I can tell that the extension was
applied, because I do not get the prompt telling me I cannot save data
in the 'Extended' version.I think the issue may be in how the form is
structured. XDP forms separate the form and the data. Typically they
have a data schema that fields are bound to. If a schema is not used,
the the binding option of "use name ()" is selected to give
the form instructions on how/w...
I believe the feature you are looking for is known as "Reader
Extensions".Saving a PDF with data in it is native to a full copy of
Acrobat. The free Adobe Reader product does not have this ability out of
the box.By default, you can create PDFs that collect data, and can be
printed or submitted to a LiveCycle / AEM Forms server.In order to be
able to save the PDF locally with data ( or use a number of other
features ) in Adobe Reader - the PDF needs additional rights granted to
it.These can be ap...
Using the Admin UI on the server, locate the service definition for your
processHome>Services>Applications and Services>Service ManagementAt the
bottom of the Security Tab, add the group you want to have access using
the Add Principal button.Grant them Invoke-Perm and Read-Perm
permissionsBe sure to save your changes.Members of the group should be
the only ones to access your start point.Good LuckMark
Are you generating a new form each week?If so, this will get the date
for next Monday - you can play with the format:var d = new
Date();d.setDate(d.getDate() + (1 + 7 - d.getDay()) % 7);this.rawValue =
d;If you are using the same form for multiple weeks, then you would need
to test to see if the current field value was less that the value
generated by the script and replace in the field if needed.Good Luck,
There are a number of things going on with your form.I believe the
biggest reason for your calculation issues is that the date field you
are referencing in the Late Fee Field is below the Late Fee Field. It
does not get initialized until after the Late Fee field initializes.
Form fields are processed Top-Down/Left to Right. A way to fix this is
to either have the Late Fee field calculate its own value for Current
Date, or place a 'hidden' field in the form above the Late Fee, and have
the Date f...
Do you see any 'work policy violation' messages in the log when this
occurs?if so, this might help: Addressing Work Policy Violations in
LiveCycle ES2 | Adobe LiveCycle Blog Best of LuckMark
Kais,The most direct way is to create a MAP type variable.Add your PDF,
and the attachments to the MAP, while also composing a Document
Description XML (DDX).( More info here:
http://help.adobe.com/en_US/livecycle/9.0/ddxRef.pdf ).Then invoke the
AssemblerService/InvokeDDX and pass in the DDX and MAP.An
AssemblerResult variable is the output, and you can retrieve your
finished document from that.Hope this helps.Mark
Agustin,I have had success using a 'regular' subform as the Overflow
Leader.In the initialize event, I set the subform as hidden.This subform
is defined at the same level in the hierarchy as the flowing main
subform.In the Layout:Ready event, I test the xfa.layout.page(this)
property, and if > 1 - set presence as visible.Reference the subform as
the Overflow Leader in the Pagination Properties of your flowing
subform.I use global bindings on the fields within the overflow leader
so that the data...
One technique would be to put code in the DocReady event to evaluate the
form state.See which subform should be acted on, and determine which
fields on the form should be opened for edit.You can use the layout
ready event of a subform that contains a signature field to check if the
specific fields for that signature meet your validations - Set the
access of the appropriate signature field to 'open' - if they are
not,set it as 'protected'.You can also evaluate the signature fields to
check it the...
The way to accomplish this is with conditional routes. Optionally going
to one set-value or the other depending on your condition(s).Be sure to
set the route evaluation on the upstream service to check the
conditional route before the default route.Best practice is to always
have one un-conditional route defined, and have it listed last in the
evaluation sequence.HTHMark
Sazaed:The feature you are looking for is called a floating field.Here
is a link to some information - good
luckhttp://help.adobe.com/en_US/livecycle/9.0/designerHelp/index.htm?content=000427.html
Check what program your browser is using for PDFs.A number of browsers
have shifted to their own PDF viewer code instead of Adobe's plug
in.Some of these do not support the whole PDF standardSwitch to Adobe
Acrobat/Reader and try opening the docs again.
If you have not already gotten past this, add a BlankPage element after
each Source element with forceEven = 'true' - forceEven will only add a
page if the source has an odd number of page images.See the DDX
reference doc for all the options.HTH - Mark
This page intentionally left blank
This page intentionally
left blank
Greetings,You have a couple of options depending on whether you need to
display the number when the form is created, or saved.You will need a
'Back-end' data store - most likely a database with a table that at a
minimum keeps track of the last used number.If you are saving the data
from the form into a database, you could return the number to the user
after saving the data ( and generating the associated number )If you are
wanting to display the number when the form is first opened, you will
nee...
Your form objects have a default visibility - visible or hidden, based
on how they are defined.You can override the default behavior in a
number of different events.Initialize events fire when the form is first
loaded, and when the form recalculates. Initialize can fire many times
during a single session depending on the level of the object.There are
charts out there that show the relationship between
forms/subforms/objects, and when the various events fire.That being
said, most of those events ...
So a lot depends on the internal structure, and how you are or are not
bonding data.The short answer, is no - setting a button property to
hidden, when the default property is visible, will only persist for the
time you have the form open.Once you re-open the form, the default is
used again.This is why setting the formula to reference a data item that
is saved with the form makes it easier to control the hide-when
actions.If you do not want to add an additional field - use an existing
one.Do you...
One way to handle this is to set a hidden field in the form that
contains a 'Form State' indicator.This is a simple number value that
relates to the different stages the form goes through.'1' might be open
for entry,'2' might be submitted.'3' might be validated, etc.Then it is
a simple process to set a button ( or any other form object ) to be
shown or hidden based on the value in the form-state field.Remember to
either set a default value, or initialize the form-state field before
first use, an...
Sounds like you are using a font in your drop-down that does not exist
on your printer.Try changing the font of the drop-down to a font that is
appearing correctly on the printed copy.
Yes. if the names of your fields are correct - Your screenshot does not
show enough detail.You should be able to test it in the Preview panel,
by typing in the comb, and clicking out of the field.THe barcode value
should change to the value you entered.
