JohnSolomon0

Re: Fragment function "is not a function" - Adobe Experience Manager Forms 28-06-2022

It looks like the function call worked either way, but that line change did it! Well... it threw other errors, but these ones were much more useful that the previous and I know how to fix them 🙂 Thank you!

Re: Fragment function "is not a function" - Adobe Experience Manager Forms 27-06-2022

Tried embedding per your suggestion, the behavior did not change.

Re: Fragment function "is not a function" - Adobe Experience Manager Forms 27-06-2022

No, that's the issue. That call just throws an error saying that it's "not a function". I don't understand why, I call a very similar function in a similar location and don't have this issue.

Fragment function "is not a function" - Adobe Experience Manager Forms 24-06-2022

Hi All, I am making a new fragment to help with some code a want to run often. I'm at the point where it should be working but whenever I attempt to reference it in the field I get an error saying "error: TypeError: form1.variables.employeeLookup.employeeLookupMain is not a function". I have no idea what's wrong, I have a decent amount of javascript experience I can't see where I messed up the function. Can anyone help? Applicable code attached below: Code that runs in the field: form1.formPage....

Re: Making all hidden fields optional - Adobe Experience Manager Forms 17-05-2022

Just making the .mandatory= "disbaled" or "error" doesn't work. You have to first do the process I described originally where you make it visible, then modify the .mandatory property, then make it hidden again. You also can't call the fragment that does this from the validate event (where we were originally calling it. The only event you can call it from is the "preSubmit" event. On top of that, if it does succeed, you have to modify the event handler like so: if(!clientChangeScriptsHTML.validat...

Re: Making all hidden fields optional - Adobe Experience Manager Forms 17-05-2022

Hi Mayank, I have way too many hidden required fields across my implementation of Webforms for it to be reasonable to go in and do that logic on each one of them. I need a way to solve this in a fragment script. I've tried using that bitTextField1.mandatory = "error" but when I try and do that to a hidden field it doesn't work. I engaged Adobe support and we found a workaround, but I'm still confused as to why that doesn't work.

Making all hidden fields optional - Adobe Experience Manager Forms 16-05-2022

Hi all! This is related to a previous question that I've asked, but I think I narrowed things down quite a bit. I have a script (Fragment) that runs on submission that scans the form and makes all hidden-required fields optional, that way the form will submit as long as all of the visible required fields are filled. This script worked really well on PDF forms, but I'm transitioning to .xdp (HTML5 rendered) forms. I'm having 1 key issue. Whenever I try to change a hidden field to optional, the sc...

Betreff: Hidden Required fields - existing script isn't working. - Adobe Experience Manager Forms 10-05-2022

Those console.log statements weren't in there until after this started, they are just there for debugging purposes. ValidationHTML is another fragment that is attached to the form. The second code block is the "setFocusToRequired" part of it. This method just handles turning text red and setting the focus of the view window. The issue (I think) is within the first code block, as that is the section of code that handles modifying the .nulltest property on the fields. I wish I could share a form, ...

Hidden Required fields - existing script isn't working. - Adobe Experience Manager Forms 09-05-2022

Hello All!I have a script that is designed to scan through the form when the users submits it and make any hidden required fields un-required. However, recently after a change to the default profile (I think this was the inciting incident, I'm not entirely sure), the user has to press the submit button twice in order for the script to work. I have absolutely no idea what's causing this, I poured over it all day, but can't figure it out. Any help would be greatly appreciated! Relevent code linked...

112

HTML5 Form - Highlight Existing Fields by default - Adobe Experience Manager Forms 21-04-2022

Hi All! We made the decision to switch off of PDF forms to HTML5 forms as part of an upgrade to our livecycle environment. In the old PDF forms, any fields that could be edited by a user had a nice highlight around them to make it clear that they weren't protected. In HTML5, this is off by default, and the user has to click a button to highlight the fields. I checked out some older questions: Highlight fields automatically in a Form | Adobe Acrobat (acrobatusers.com) but it looks like they take ...

Likes from

User

Count

Learn

Documentation

Community

Support

Resources

Adobe account

Adobe