qSteve-WRz7fs

Re: Can't see "Enforce strict scoping rules" - Adobe LiveCycle 05-07-2012

Thanks Niall. What I'm not understanding is why your AssureDynamics form works for me when I open it in Designer and preview it but mine doesn't. The strict scoping parm in the XML is the same for both -- -- yet in your form, this.initValue takes the "1" on the mouseUp when the button is deselected, but on mine it's undefined. Could there be anything else causing this? Both forms are Dynamic XML and set to 9.1 or later.Steve

460

Re: Can't see "Enforce strict scoping rules" - Adobe LiveCycle 04-07-2012

Thanks for the work-around, Niall. Works like a charm and is a LOT simpler! I'll still be interested in your findings re the missing function.Steve

459

Can't see "Enforce strict scoping rules" - Adobe LiveCycle 04-07-2012

I have a radio button group in which I'm attempting to deselect a button. There are examples by Niall and others that I've copied, but it's not working, apparently because this.initValue is not being passed from MouseDown to MouseUp. It seems that deselecting "Enforce strict scoping rules" might solve the problem, but this parameter is missing from the application.I'm running ADEP Designer version 10, and there's nothing about scoping in either File Properties > Defaults or File Properties > Run...

3.3K

Re: Testing for validation errors - Adobe LiveCycle 22-06-2012

Does indeed. Thanks so much for your prompt response!Steve

249

Testing for validation errors - Adobe LiveCycle 22-06-2012

A simplified version of what I'm trying to do:A form contains a required input field, a standard submit button to perform some actions and trigger an email submit button, and a subform set to Hidden.If the user fills in the input field and clicks Submit, the hidden subform is displayed and the email submit is triggered.If the user clicks Submit with the input field empty, I want the error message to display but the subform to stay hidden and the email event to not trigger.What happens is that th...

813

Re: Extra, unwanted rows generated with Reader Extensions - Adobe LiveCycle 28-05-2012

Thanks a million, Niall - that was it. I'm not sure how it happened, but three of the rows had the Repeat box checked. It's working perfectly now.

212

Re: Extra, unwanted rows generated with Reader Extensions - Adobe LiveCycle 28-05-2012

Thanks for the suggestion Niall. Here's what's in those events:layout:ready - nothingdocReady - initializing a couple of buttons:Page1.sfEmpSub.SubmitToAdmin.presence = "invisible";Page1.sfEmpSub.SubmitToMgr.presence = "invisible";initialize - just the generated stuff:ColorFieldsValidation.InitializeColorFields();I can't see anything that would likely cause this problem, but I'll try to narrow it down by a process of elimination and post back.Steve

185

Extra, unwanted rows generated with Reader Extensions - Adobe LiveCycle 25-05-2012

I have a table with a header row, 4 body rows, and a footer row. When I display it in Reader, it appears exactly as created:But when I do a Save As > Reader Extended PDF > Enable Additional Features and display it again in Reader, several unwanted rows appear:Can anyone suggest what might be causing this?Thanks, Steve

1.4K

Re: How do I reset a mandatory field after it has been filled in? - Adobe LiveCycle 15-05-2012

I have the advantage of creating these forms for an Intranet site where I can dictate a target version of 9.1 or higher in Form Properties > Defaults. When you specify 9.1, you get the option to use global settings for Show Dialog Message, Color Failed Fields, Color Mandatory Fields, and Set Focus. Certain combinations of these do in fact remove the border and background fill when required fields have been filled in. (Although even selecting "Don't show any message boxes at all" still results in...

344

Re: How do I reset a mandatory field after it has been filled in? - Adobe LiveCycle 11-05-2012

Thanks Srini, but this should be happening automatically or it's way too much to have to coordinate for every field on every form. That was the gist of my second post - the other form I opened does this automatically. And when I create a new form from scratch, it also works fine automatically. So my work-around for now is to recreate all the forms that have problems. A pain, but faster in the long run than trying to get to the bottom of the issue.It seems to me that there's some flakiness in Des...

345

Likes from

User

Count

Learn

Documentation

Community

Support

Resources

Adobe account

Adobe