Regarding the change of output format make the following changes:Set the
Data pattern of your 2 date fields toand the Display pattern to the one
you wish to haveChange the calculation script (if you use mine in
FormCalc) toWhat this does is to use the data format of your fields to
get the date values for calculation which stays fixed whereas your
display format can then change because we do not use the formattedValue
properties any more.
Hi,you have a typo in your DDX roatate90="90" must be rotate90="90"I am
not sure that the tagging is the problem, the DDX works with tagged and
untagged documents here.regarding 1.: The watermark must be associated
to a set of surfaces in a PDF tag which is done in the way you have done
it. I don't think you can do it more simple than that.regarding 2.: Not
that I know of, but I also don't think that tagging is your problem.
What kind of PDF are you using? Do you have dynamic XFA?There may be
Hi,to explain why you cannot combine the XFA PDF with others:Assembling
PDFs only works with the same "type" of PDF.The most common form of PDFs
is what I call the Print-PDF. That is what the majority of PDFs out
there are.Then there are special variants such as XFA PDFs. These need a
plug-in in Adobe Reader or Acrobat to render them in their final form
while being opened.Because these two are so different, it is not
possible to combine them in Acrobat.You can "flatten" your XFA PDF (it
As Mayank says, if you still have IE11 and installed Adobe Reader with
the browser plugin activated (in Preferences of Reader look for Internet
and follow instructions if not activated). But to be clear: this use
case is deprecated and will not work for much longer. The organization
that wants you to sign PDF like that must offer alternatives (such as
download and upload) or use services like Adobe Sign.
The issue was a missing patch. We implemented the patch for AEM 6.5 and
updated it to 6.5.3 with the help from Adobe support and it resolved the
issue. Thanks all for viewing and responding to the question. Note -
6.5.3 is not directly available in the download site. Raise a SR with
support and they will help you.
The issue was with the proxy creation. The adobe documentation are not
accurate. When you create the proxies using WS Import the packages got
created correctly and resolved the issue.Thanks all for checking.
You will probably have to write a simple REStful service to do that
follow this documentation which has sample assets to get you a head
🙂 as you can see this approach is MUCH MORE complicated. I would
recommed to use a table. When you say "some line under some field" - can
you provide a scetch or a screenshot what you mean by that? When are
there lines under what fields?
If you are looking for an automated report which XDPs use a specific
fragment - that does not exist. A fragment is an individual XDP file
which is referenced in n layout XDP files. You would have to write
yourself some program which scans your layout XDPs and detect references
to specific fragments.
datum.toISOString() is a quick way to display a datetime in a text field
can cut away the time part - but I used the full string as I cannot
the same as your script. Just I have it in the initialize script and not
in ready.layout. reday.layout is not the most suitable event for this
kind of calculations. If you want the date only with the ISO string then...
For a better understanding of Masterpages and Fragments you may find
some ideas here. It is the SAP LC Designer but the same concepts may
help you. Forget about all the SAP related stuff...
Hi, I use Designer outside of SAP (LiveCycle/AEM Forms). Do none of your
objects give you the Create/Edit option? Or is it with certain objects?
For example: table fields cannot be converted into a fragment, the
variables section where you script is also not. Masterpages and Content
Areas also not. Have you been able to create a fragment library on your
HDD? I found a blog about fragments in SAP - maybe that
This is other solution for this case. Create one file with DDX
Set one process
variable type XML with file content. Update command XML Node with xpath
for the content.XPath: //PDF[@source="docLoteDeclaracoes"]/@pages Invoke
Hi there, By the look of your variable statements, I think you're trying
to change the inital array value that resolveNodes() has returned,Which
is why you are ending up with only 2 length array. //This section
extract an array of items to retrieve a value directly to the designated
object var monName =
In the script object that I provided in my previous examples? Did you
use my other approaches? If so then put it at the end of the script
object and call it in the exit event. You need to adjust things to your
form implementation - I cannot do everything....