Unfortunately, that doesn't really help, this is building the list, not
using an existing one, and as they are still all keying off of the
value, not display value. Radio button: rbServiceQuality1=1. Bad
service2=2. Good service My workaround is to set the value to be the
full string, and then use regex to set the slice the first value. Radio
button: rbServiceQuality1. Bad service2. Good service Number box:
numServiceCalculation, code editor to Calculatevar str =
rbServiceQuality.value;var res =...
I need to access the display value for a radio button in another field
on my adaptive webform. For example: red=Red Car I have a different
field that needs to show "Red Car". However, for some reason, on the
second field, this.value=rbCarColor.displayvalue; does not work.
Anything I'm missing, or is displayvalue not available for radio
buttons? Thanks!
To clarify my question - how do I factor the text fields to accept HTML
formatting beyond ? We want to be able to use HTML text with proper
header levels and formatting, and have that also appear on the DoR. The
below header will not show on generated DoR. However, this will.Using
does not allow screen readers on the Adaptive Form to scan by
headers. We can't even use panels to act as that as they are coded in
AEM as , not a header. We don't really care if the rich text shows
as plain text, bu...
That page is very generic, and does not state how to include formatted
text (This is a subhead). The page just seems to say that text
will go into text boxes, but doesn't address the fact that h2/h3 and
other formatted text for accessibility on the adaptive form does not
show on the generated document of record. Please give code or example.
So far, we have no correct reply.
We have a customized DoR template, but cannot find documentation on how
to make the correct fields to bring rich text or formatted text into the
DoR. If you can point some out, that would be very helpful.
Description - Currently, we cannot use h2 and h3 in forms and have them
appear on Generated Documents of Record. We have to use panel
descriptions for blocks of form inputs, and cannot use in Static Text -
they simply do not show and will block out the entire text block. To
enable accessible scanning of form, we need to do a workaround of a
panel descriptions for the DoR, but then put in the h2 and h3 for the
Adaptive Form. Why is this feature important to you - Accessibility!
Screenreaders scan...
Description - Currently, we cannot use h2 and h3 in forms and have them
appear on Generated Documents of Record. We have to use panel
descriptions for blocks of form inputs, and cannot use in Static Text -
they simply do not show and will block out the entire text block. To
enable accessible scanning of form, we need to do a workaround of a
panel descriptions for the DoR, but then put in the h2 and h3 for the
Adaptive Form. Why is this feature important to you - Accessibility!
Screenreaders scan...
We would like to modify the Generated Document of Record table cells
(AF_TABLEITEM_XFO) to be left-aligned rather than center-aligned.
However, even though my paragraph settings are for left-justified, my
results are still centered. Is there a way to set this? Thanks!
The form filler will sign, but then there are 2 other signers. We may
use scribble for the initial form-filler signature, but the others need
to go through Adobe Sign.
We need to create an adaptive form that the Document of Record is
formatted as a contract, with Adobe Sign fields. When I refer to the
documentation:
https://docs.adobe.com/content/help/en/experience-manager-65/forms/adaptive-forms-advanced-authoring/working-with-adobe-sign.html,
I get the following. "Use Adobe Sign block only for those adaptive forms
which automatically generate Document of Record. If you are using a
custom XDP for generating Document of Record or a form template based
adaptive...
