Haven’t you come across a scenario, where the business wants you to
emulate the paper based version of the forms as is on web channel ? If
so, then I think the hardest part of such requests is to have an Image
Field in Adaptive Form. It is like where the person filling up the form
should be able to attach and then see or preview the passport size
photograph or may be some other photograph while within the form’s view.
Adaptive Forms only provide a hyperlink to the uploaded image. This link
when ...
experience-manager-forum :If you can tell the version of AEM & AEM
Forms which you are using, we can help you better, I suppose.To start
with, it may be that one of the Forms Servlet might be
missing/unsatisfied, due to which the call is being forwarded to default
SlingPostServlet which is unable to handle the request format.You can
also post the request headers for the failing call.Cheers,Jagjeet
SinghAEM Forms Blog
Hi Prabu,I will need the complete screenshot of your bundle page and
components page and error logs.Why don't you try and add debug pointers,
that will help you find exact problem easilyCheers,Jagjeet Singh
A few questions to identify the issue:1. Is your forms Json Model
Based?2. Is the name of field which your are trying to populate
"textbox"If answer to both the question is yes, then please try below
JSON{ "afData": { "afUnboundData": { "data": { "textbox": "testing" }
}}Hope this helps !!!Cheers,Jagjeet SinghAEM Forms Blog
Thanks,The issue which you have mentioned is due to number higher that
javascript's limit for numbers being converted to exponentional or
scientific notations ex 123.11e26.This issue is at Javascript's end and
not at AEM Forms end. You can go to browser's console, create a "var a =
1111111111111111111111111111111111111111111" and then just get alert(a),
you will get out put in exponential notation.As a solution, I will
suggest you to use text field with pattern validation for number, but
bear in...
Hi christofhed35451717,The instructions here work as is. I guess we
will need some more information to help you debug. For starters you can
compare the json you are populating your form with to the json created
when you save the form.You can get the json on form save easily via
network panel.While comparing you can have it either with or without
afdata wrapper.Cheers,Jagjeet SinghAEM Forms Blog
Really Sorry for that. I was rearranging the paragraphs to make better
sense and it got jumbled.What I wanted to write is :If the validation
fails, the hook returns the form with to the browser again, showcasing
the errors. An important point to note here is that all the validation
should be a part of Form's dependency scripts, and all other validations
will not work.Cheers,Jagjeet SinghAEM Forms Blog
Hi James R Green,When you enable server side validation, there is a
server side hook which is enabled. When you submit the form, the form is
sent to that hook, where all the Validate Rules (which are configured
using widget options & validation rules in rule editor) that have been
configured in the form are re-run. You can think of it as form being
previewed with the submitted data, on the server side, and the success
being determined on the basis of .validate() function run at
guideContainer l...
Hi James R Green ,I have tested the same on 6.3, 6.3 SP1, & 6.4 Beta
Load 20 and validations are automatically triggered for numeric box on
any value commit. I do NOT see any bug there, can you please check once
more.deepakt84913413 :What was the initial issue you were facing,1. Was
it Validations not working for numeric field on tap-out without any
value change, something like in this video AEM Forms Field Validation
Aberrant behavior - YouTube.The fix for this is the script which I gave
you....
Hi James R Green ,Sorry for being noob. The field validation is
automatically triggered when you make changes in the field values (any
widget : text or numeric). (I might be missing something, just writing
for my knowledge, please let me know what am I missing). Thus, in my
perception, the script you provided does not do anything over & above
this.The only difference between text & numeric validation is the
trigger when you haven't changed anything, and I suppose that it what
deepakt84913413 ha...
James R Green, deepakt84913413,I think I am missing something, I have
tried this solution but it does not validate on focus out when I have
NOT typed anything in the box, which was the initial requirement from
deepakt84913413. Please let me now, if there is some step which I
missed.Below are some of my suggestions : If what I found previously is
correct: Since this solution validates only after some input entry is
made (at least for me), this makes the functionality same as marking the
field ...
Hi prabuj201987,You will have still have some runtime error(s) I think.
Please clear your error.log file, restart you bundle. And please share
your logs, screenshot of your bundle details page
(/system/console/bundles/bundle-number) and components page.Its will be
able to help me debug your issue.Cheers,Jagjeet SinghAEM Forms Blog
Hi deepakt84913413The code I have shared has a comparing code already
working on mobile sites, also you can use the below piece of code on
initialize of root panel or the field to achieve what you want
(validation to trigger when you leave the
field.$(".numericbox1518941620523 input").focusout(function()
{guideBridge.resolveNode("numericbox1518941620523").validate()});//replace
numericbox1518941620523 by the name of your text fieldThis piece of code
has some hardcoding, but I will soon be able ...
Then, you can go to bundles, stop & start your bundle. Look into the
error logs and check if there are any errors during
activation.Cheers,Jagjeet SinghAEM Forms Blog
prabuj201987, you can go to /system/console and then to your specific
bundle, and then check if your service is being exported. Also, in
addition, you can go /system/console/components to check if your service
is satisfied.I can help you with next steps once you help me with the
status of these things.Cheers,Jagjeet SinghAEM Forms Blog
prabuj201987I think I had a similar problem a few days back. In my case
the bundle was getting active but the pre-fill service I created was not
getting active/satisfied, due to run-time dependencies of some class
(some class related to w3c dom document, if I remember correctly).Please
check if you are also facing something similar, where some run-time
dependencies are missing.Hope this helps !!!Cheers,Jagjeet SinghAEM
Forms Blog
deepakt1812Yes, James R Green is right.Why don't you use HTML5 number
field in your forms. I have created a blog post here with a step by step
way to achieve what you want.Numeric Box Widget Tips in Adaptive Forms
for Mobile Devices | AEM Forms Blog It works in mobile also, with all
the rules. Please go through the blog post and it will solve your
problem.Hope it helps & answers your question .Cheers,Jagjeet SinghAEM
Forms Blog
deepakt84913413 :Why don't you use HTML5 number field in your forms. I
have created a blog post here with a step by step way to achieve what
you want.Numeric Box Widget Tips in Adaptive Forms for Mobile Devices |
AEM Forms Blog It works in mobile also, with all the rules. Please go
through the blog post and it will solve your problem.Hope it helps &
answers your question .Cheers,Jagjeet SinghAEM Forms Blog
The whole point behind making a cloud services is that it is
configurable, and you can give the privilege to super-authors and reduce
dependency from server administrator.You can have a configuration
parameter for the service url or the server type, and that can be
changed as per environment. If you can see how we configure
analytics/target/dtm or any such tool using cloud services, you will get
a fair idea of what I am trying to convey.I will try and create a small
blog post in a couple of days...
rajeshs28932860 :I remember a bug in some version (not sure of the
version number though), where if you make the radio button/check box as
mandatory then all the rules used to stop working, it was fixed with an
incremental release.Can you please confirm, if you can reproduce the
bug. I mean if this thing does not work only if radio is mandatory, in
that case, I can help you find the bug fix (incremental release) for
this issue.Cheers,Jagjeet SinghAEM Forms Blog
Maruan Sahyoun : The general approach to this scenario is to create a
new cloud configuration for your service and add that cloud service to
the page where form is used/added. Now you can have different values to
these configuration in your different servers(dev, qa& prod).And in your
code you read these cloud config values rather than the OSGI Configs. I
have personally used this approach for many of my forms and it saves a
lot of development effort and is also generic as per coding
guidelines...
Hi Malarvizhi Saravanan :I would suggest you to use AEM's Content
Services to achieve what you want.I is the best solution to your
problem, giving you granular control over the data you would like to
expose via the API.Cheers,JagjeetAEM Forms Blog
I am from Adobe (not from Forms' Engineering Team), so not an official
word. But as far as I know changing the Form Model will lead to binding
errors on all the bound fields, this may be an important reason to not
allow it in first place.Cheers,Jagjeet SinghAEM Forms Blog
chandran85965395 you need to add display:none to the selector
".guideFieldDescription.long" which is the parent to the cross
button.You can do this by creating a client lib, creating a js file this
code and add it as a dependency in your Adaptive form.Hope this helps
!!!Cheers,Jagjeet SinghAEM Forms Blog
Hi James R Green, formatix,First of all that's definitely not a
recommended way.If you still wish to go ahead and change it, please
change it in the corresponding form location in
/content/forms/af/***//jcr:content/guideContainer node
also.Cheers,JagjeetAEM Forms Blog
I don't think this is a bug.There is a point we are missing here, since
that field is mapped to an XFA element, it is supposed to have values
that only XFA dropdown is mapped to.The right approach to handle your
scenario should be to have the dropdown dynamic in XFA itself. The
process remain almost similar to what you are doing in Adaptive
FormsHope this helps !!!Cheers,Jagjeet SinghAEM Forms Blog
So, I guess final correct answer should be add below mentioned code to
code editor on initialize:guideBridge.on("bridgeInitializeComplete",
function (event, data) { guideBridge.resolveNode("staticText1").value =
"Your new static text here";});I have created a blog post which delves
into details around how to dynamically change static textsmacdonald2008
: I think we should change the correct answer, as the answer which is
currently marked correct answer, will never work in this question's
use-ca...
