Discussion

Pressing Enter Key disables Continue & Cancel btn

I noticed that when we enter in data on our profile screen, and then press the enter key to trigger the continue button to go to the next page, it actually greys out, and disables both the continue, and cancel buttons. It doesn't matter which field I am entering data in. It still disables the two buttons. Anyone have any idea on how to resolve this issue? Thanks, Eric

***Updated by moderator: Marissa to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Comments

Keep up to date on this post and subscribe to comments

May 7, 2009 - 12:44pm

re: I noticed that when we enter in data on our profile screen, and then press the enter key to trigger the continue button to go to the next page, it actually greys out, and disables both the continue, and cancel buttons. It doesn't matter which field I am entering data in. It still disables the two buttons.

Eric -- which version are you in?
In v5.3/v5.4 (I haven't looked at this in v5.5 yet), there's a JS function catchEnterKey() in harness_action_iframe.js which submits the current form upon clicking Enter except when you're in a textarea, link anchor, or button.

That might help explain what's going on.

Jon

May 8, 2009 - 11:12am

Hi,
Im actually on version 5.1 I see that js file, and i'm looking through it now, but I'm not sure what to modify here.

May 8, 2009 - 12:59pm

re: I'm actually on version 5.1 I see that js file, and i'm looking through it now, but I'm not sure what to modify here.

Yeah, that's the catch-- you can't directly modify it. I was just giving you a hint to see where the code was executing. Which HTML element are you in when you are clicking enter?

You *can* directly override catchEnterKey() in the rule-override fashion, but if you create a function afterwards in the HTML, the second function will be executed. I'm not sure if this is best practice -- I'll check -- but it can be a workaround in a pinch if you need one.

Jon

May 9, 2009 - 5:08pm

Yes, I think I could do that for the time being. Can you explain the Rule-override. I am in the Zip Code field when hitting the enter key to make it continue to the next screen, but I can hit the enter key on any area of the screen, and it still greys out the buttons

May 11, 2009 - 10:22am

re: Can you explain the Rule-override.

By "rule-override" I meant the essential PegaRULES technology of overriding rules to provide your own functionality. That doesn't apply at the javascript function level.

Jon

May 12, 2009 - 1:46pm

Thats what I thought you meant. I talked with Pega Support about this, and since it is part of the Pega-Procom ruleset which is marked final, I can not edit it, or save-as. They are looking into the issue now, and if they can correct this issue.

Thanks,
Eric

May 12, 2009 - 2:05pm

Eric wrote: I talked with Pega Support about this, and since it is part of the Pega-Procom ruleset which is marked final, I can not edit it, or save-as. They are looking into the issue now, and if they can correct this issue.

Thanks for the heads-up. I found it, SR-24799.
For future reference, if people enter support items *in addition to* posting here, can you make that known here (and posting the SR-# if possible?) We like to see developers get through your problems, and duplicating efforts on our end might frustrate that a tad.

In addition, if you've raised something with GCS from the PDN Forums, then include the link to the discussion in your submission.

Just to check on this when you said "enter in data on our profile screen" -- what do you mean? Looking at the screenshots you submitted, I think you meant flow action (as I suspected).

Also, from your original post -- did you mean to say that nothing submits at all? Sorry I neglected to clarify that at the time. I was just advising where to look to see what was going on.

Jon