Question
US Bank
US
Last activity: 17 Jul 2017 16:37 EDT
Implementation of HotKeys chrome based browser in PEGA 7.1.5 or PEGA 7.1.7
We have upgraded the application from PRPC 5.4 SP3 to PRPC 7.1.5 and PRPC 7.1.7 where the Hotkeys functionality is not working as expected in IE or Chrome browser, Where the same code/functionality working as expected in PRPC 5.4 SP3.
Hotkeys - Where we have functionality for "Serch" button insted of handling with Mouse click press "Alt+e" will do the same task.
Attached Custom button code(ButtonwithClick1) and screen shots of configuation which will provide the some other functionalities to the user like
1) Once user submitted the changes by cliking or press "Alt+e" which will change the button style to "Searching...." and
2) Make the scroll bar to top once user submit the changes to show focus on confirmation message.
***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.
Accepted Solution
PEG
IN
You are seeing this change in the behavior in Pega 7 for obvious reasons. The generation of buttons and their JS treatment has been changed in PRPC 7 versions. When I have used OOTB button and configured a hot key as below, "alt+B" perfectly works. You must consider changing your custom controls to OOTB controls since by converting to auto-generated controls, you will have a much easier UI upgrade path in future MLs.
If you want your custom controls to work you have to further customize them using scriplets tags <%%> in pega 7. For now I have updated your custom control and it is accepting the hotkeys. Upgrading them to pega 7 OOTB buttons is quiet easy and you can achieve the similar behavior as custom controls by using the OOTB events.
Pegasystems Inc.
US
While I am serving more as a moderator, I took a quick look and suspect that the upgrade to Pega 7 and usage of your control in Chrome may not be supported, as you are experiencing. I will let the community weigh in more on that particular matter.
In the meantime, given the significant jump in versions, may I suggest you look at all of the auto-generated controls now available in Pega 7? While there will be effort involved, you may want to give serious consideration to converting old custom controls to their newer auto-generated counterparts.
Thanks.
B.
Accepted Solution
PEG
IN
You are seeing this change in the behavior in Pega 7 for obvious reasons. The generation of buttons and their JS treatment has been changed in PRPC 7 versions. When I have used OOTB button and configured a hot key as below, "alt+B" perfectly works. You must consider changing your custom controls to OOTB controls since by converting to auto-generated controls, you will have a much easier UI upgrade path in future MLs.
If you want your custom controls to work you have to further customize them using scriplets tags <%%> in pega 7. For now I have updated your custom control and it is accepting the hotkeys. Upgrading them to pega 7 OOTB buttons is quiet easy and you can achieve the similar behavior as custom controls by using the OOTB events.
US Bank
US
Thanks Srikanth and Brendan for your response, your suggested code helped us to fix the issue in chrome in many places in the application and
In other places we are using the differant custom code(ButtonWithClick,ButtonWithClick2 - Attached to the original post) giving the issues.
Can you please help us to make this functionality works in remaining areas.