There is no unique identifier generated for the Form. Currently the path
of the form is considered as the unique identity of the form.What is the
use case that you are trying to achieve by having a unique identifier
for the form ?Thank YouVarun Dua
HiThis happens because of the CSRF prevention support that was added in
6.0. While making a post request you now need to provide a CSRF token as
well. This support was provided ootb with granite jquery.This question
provides more informationThanksVarun Dua
Hi You can write the validation script on the validation event. If you
are on 6.2 or 6.1 FP1 you can use the Rule Editor to add your validation
logic using the Visual Editor For more advance use case you can specify
that using code editor where you can write any custom JavaScript For
more information on rule editor please visit [1][1]
https://helpx.adobe.com/aem-forms/6-1/rule-editor.html
Hi Robert,Can you specify the use case you are targeting ? You are
requested not to use any methods starting with _ since the can change
without any notice. Also id is internal and we change it for repeatable
instances, fragments etc during render.
In 6.2 we have made Adaptive Form component [1] which covers the same
use case [1]
https://helpx.adobe.com/aem-forms/6-2/embed-adaptive-form-aem-sites.html
> The problem is with validation because the list of failed elements
returned from the guideBridge validation method has ID's that don't
exist on the page, you can't use the somExpression to resolve the
element,I am still not getting, maybe some code you provide can be
helpful. With SomExpression you can get hold of the HTML element like
thisvar errors = []; guideBridge.validate(errors);
errors.forEach(function (error) { var field =
guideBridge.resolveNode(error.som); var $field = $(field.cssCla...
This is a special case for fragments and hence you are seeing different
Ids. Consider the case where you drop a fragment twice in the form side
by side, as per the jsp code, the id would become the same and it would
be difficult for the runtime to differentiate between the two. So in the
case of fragments we change the id when fragment is loaded. Also this
logic is internal to Adaptive Form and can be changed anytime. It is not
recommended to depend on the id to do anything. The recommended appr...
Hi Praveen,cq-adaptiveforms-content pacakge comes with quickstart. Can
you check in the package manager what is the version of this package in
your setup ?RegardsVarun
Hi Urs,> do an ajax call during initialization of the component (using
jquery) ?You can initialize your component using a custom
widget/appearance as mentioned in [1].> use the result of the ajax call
to do DOM manipulations (using jquery) and update the value of guide
fieldsYou can achieve that by prepopulating the form fields by passing a
dataRef parameter[2]Manipulating component DOM in connect can lead to
some errors later on, because the Adaptive Form might have attached some
listeners on t...
Hi Praveen,Rule Editor Functionality [1] is available in AEM Forms 6.1
Feature Pack 1 release [2][1]
https://helpx.adobe.com/aem-forms/6-1/rule-editor.html[2]
https://helpx.adobe.com/aem-forms/6-1/whats-new-fp1.html RegardsVarun
Dua
No,importDataObject API is not supported on event.target object and the
same is true for other APIs that you have used in your code. So I regret
to say but your code will not work in HTML preview.RegardsVarun
Hi Urs,From the documentation[1]After performing the required action,
the Submit servlet forwards the request to the forward path. An action
uses the setForwardPath API to set the forward path in the Guide Submit
servlet. If the action doesn't provide a forward path, the Submit
servlet redirects the browser using the Redirect URL. The author
configures the Redirect URL using the Thank You Page configuration in
the Adaptive Form Edit dialog. You can also configure the Redirect URL
through the Sub...
Hi Darren,New Standard is followed for all the Adaptive Forms. In
addition to that for XFA based Adaptive Forms old standard is still
followed, but in that case if you have dropped some fields form the
sidekick and not from the Data Hierarchy tab, those fields will not be
pre-populated. So as an example, if in your XFA based Adaptive Form, you
have used only XFA based Fields then the following two XML structures
are equivalent for
pre-populating......But
if you have some fields that are not boun...
Instead of the html extension, you can try .pdf extension to show the
pdf file. i.e. try changing the URL
tohttp://:/content/xfaforms/profiles/default.pdf?contentRoot=crx:///content/dam/formsanddocuments/FordeForm&template=ESC101NK.xdp&dataRef=crx:///content/dam/fordeform/contractData.xml
Hi Dale,Yes it is a known issue, adding jQuery in Templates brings in
some weird problems. And FYI, we bundle jQuery 1.8.0 in our Adaptive
Form.RegardsVarun Dua
Hi Dale,Thanks for providing the information, it will be difficult to
debug this issue without reproducing the issue that you are facing .
Will it be possible for you to tell the steps that might help us
reproduce the issue at our end ?Apart from that I would like to know few
extra things from you1. Whether you have written any scripts on the
change event of radiobutton in xfa ?2. Whether there is any difference
in the properties of radio button in demo1 and radio button in demo2 ?
Mainly, Bind ...
Also you can check the logs in your browser in xfa based forms and see
if there is any error1. Navigate to
http://:/system/console/configMgr2. Search for Html
Library manager and click edit (pencil icon next to library manager)3.
Select the check box which says Debug Console4. In the next field (which
says Debug Init Script) select add the script
window.AF_log_config="a7-b7-c7-d7". 5. The final value in the field
should be
window.CQ_initial_log_level='INFO';window.AF_log_config="a7-b7-c7-d7"To
u...
The caption (as you call it, we call it panel summary) that you see in
the Repeatable Panel is actually controlled by the summary expression on
a panel. In the edit dialog of the repeatable panel you can write an
expression in the Summary Expression field (The field is highlighted in
the Image).[img]repeat.png[/img]If you don't provide any expression,
this is the expected behaviour. If you provide a summary expression, it
will be executed every time you add or remove a instance of the panel
usin...
Hi Urs,May I know how you are hiding the field ? Are you using the
Visible Expression or the Value Commit Expression. In your use case
using Value Commit Expression will give better performance.RegardsVarun
Hi You can use the validationsDisabled property of a Field to switch off
validations. In your example, you can write in the value commit
expression of the birthdate field if ( checkIsabove18 ) { // replace
checkIsAbove18 with an actual check legalRepresentation.visible = false;
// assuming the name of the legal representation field is
legalRepresentation. If not change this with the actual name
legalRepresentation.validationsDisabled = true;} else {
legalRepresentation.visible = true;
legalRepre...
Hi Alex,The feature was introduced in AEM 6.0 Feature Pack 1 and was not
present in the AEM 6.0 release. To try that feature you need to upgrade
to Feature Pack 1RegardsVarun
Hi vkeerthy,You can use the instances property of a Panel's
InstanceManager to get hold of all the instances of your address panels,
create an array of values and return that in the optionsExpression. So
in your case the code would be something likevar myPanel =
addressCollections.panel1, values = []; for (var i = 0; i <
myPanel.instanceManager.instanceCount; i++) { var panelInstance =
myPanel.instanceManager.instances[i];
values.push(panelInstance.address.value); } // this is important since
we...
Hi Afam,LC Process Locator and Invoker service searches for those
process in Livecycle which take two input parameters having names
dataxml and fileAttachmentLists by default. If your process have
different names, you can enter those in the configuration.These
processes are then listed in the Submit to Forms Workflow submit action
configuration and you can choose one among them. Note: dataxml is not a
property of your process but the name of the input variable which
accepts data xml (a document ...
Hi Scott,The approach you have mentioned is correct and will work in all
the cases.But we also provide a OOTB submit action which does the same.
The action invokes the process selected by the user in the submit action
configuration. The only limitation is that it only invokes those process
that take two input parameters. The action searches and lists all the
process that take two parameters (having specific names) and the author
can then select any of the process from the list. The name of those...
To use the Submit to Forms Workflow option you need to configure LC with
AEM. The steps for that are provided in [1]. You don't have to provide
any URL, Once you complete the configuration steps it will show you a
list of process and you can select one.I am not sure I understood your
second question completely. My initial understanding is that you have
not configured echosign service in AEM the steps for which are provided
in [2]. Can you share the link which you are talking about.[1]
http://hel...
Hi AshokCurrently we do not support Designer like Fragments in Adaptive
Forms. But there is a workaround with some known limitations to create a
composite component (which can have multiple AF Fields/Panels) which
when dropped onto an AF creates all the Fields/Panel in that Component.
You can reuse the same component across multiple AFs. I am detailing out
the steps for the sameCreate an AF (choose the survey Template provided
OOTB). Remove all the Panels/Fields except RootPanel.Add the necessar...
