There are quite many things mainly around use of XDP like creating XDP
Adaptive Forms, getting document of record from Adaptive Forms, Adaptive
Document functionality, addon compnents for forms like e-sign, scribble
etc , watch folder and batch generation of documents, HTML 5 forms etc.
This is not an exhaustive list.
Also once you sign the form and submit there is no going back i.e. your
EchoSign actually submits the signed pdf for that instance of form (this
is irrespective of Adaptive Forms submit - but via wizard template it
goes hand in hand Sign - > summary ).So your form design should take
care that any mandatory fields you want user to fill should be done
before signing process.
"Same goes for esign" - For esign as well as Verify component it is
expected that these components would re-render. "Please share the
collateral" - You can package the adaptive forms via Package manager if
you are on 6.0 or via form manager itself if you are on 6.1 beta. For
using package manager use the following filters. -
c. Verify components re-renders when you will move next/back from
wizard. Same goes for Esign as well. I am not sure why should it not
re-render in your case. Please share the collateral for better
Just want to know the following - a. Which release version of forms are
you on as Forms JEE release had some fixes around this area.b. Is OOTB
advanced enrollment template working for you ?c. Did you place any
component on the same panel in which you have e-sign?
Did the text below in the email submit action not help you. Also please
have a look at
you want some context of fields/components. Using adaptive form field
names to dynamically create email contentThe field names in an adaptive
form are called placeholders that are replaced with the value of that
field after a user submits the form.In the Email action tab, you can use
placeholders that are processed when the action is perf...
I have a couple of things to ask - Did you go and read the links
provided in the configuring submit actions article which have details
about what each submit action does
---> Store content and PDF related actions
---> email submit
---> Submit to LC
is not enough, we are happy to answer your queries. Also if you want
some specifics w.r.t to any/all submit actions, we can go ahead
documenting the same.
If you mean submit actions then try
you want to pre-populate fields then have a look at