Question
American Express
US
Last activity: 18 Jan 2017 9:41 EST
How to stop CPM-7 portal from stealing focus
Product : CPM 7.1.3 on Pega 7.1.7
Question: We suspect the function focusDocument(module) in pzpega_ui_DynamicContainer.js is bringing the PEGA application into focus when we access the script. Is there a way to customize this or suppress this. Please review the below info and suggest if there would be better way to achieve this.
Overview:
We are planning to run legacy and PEGA applications in parallel, to achieve we are trying to create a case in PEGA application as soon as case is created in legacy application. This case creation in PEGA application should be in the background. Below is the scenario how it works:-
1.Open the legacy(.NET) application, PEGA application will also be opened in the background.
2.Card Member calls the customer support.
3. Call comes to legacy application.
4. Once authentication is cleared in legacy application, we need to create case in PEGA application as well in the background. CCP should always be viewing legacy application.
5. Also, if we end the case in legacy application, we would end the case in PEGA application.
To achieve step-4: We are calling the OOTB pega script from the legacy application as below with required parameters. Case is creating fine but the PEGA application is coming into focus always. We want this focus to be stopped.
pega.desktop.createNewWork(A,B,C,D,E,F,G,H)
Product : CPM 7.1.3 on Pega 7.1.7
Question: We suspect the function focusDocument(module) in pzpega_ui_DynamicContainer.js is bringing the PEGA application into focus when we access the script. Is there a way to customize this or suppress this. Please review the below info and suggest if there would be better way to achieve this.
Overview:
We are planning to run legacy and PEGA applications in parallel, to achieve we are trying to create a case in PEGA application as soon as case is created in legacy application. This case creation in PEGA application should be in the background. Below is the scenario how it works:-
1.Open the legacy(.NET) application, PEGA application will also be opened in the background.
2.Card Member calls the customer support.
3. Call comes to legacy application.
4. Once authentication is cleared in legacy application, we need to create case in PEGA application as well in the background. CCP should always be viewing legacy application.
5. Also, if we end the case in legacy application, we would end the case in PEGA application.
To achieve step-4: We are calling the OOTB pega script from the legacy application as below with required parameters. Case is creating fine but the PEGA application is coming into focus always. We want this focus to be stopped.
pega.desktop.createNewWork(A,B,C,D,E,F,G,H)
To achieve step-5: We are first opening the pega case as below and then performing required actions. End call is fine, but PEGA application is stealing focus. We want to avoid PEGA application stealing focus.
pega.desktop.openWorkByHandle(A,B,C,D,E);
Attempted Solution: We have placed snippet mentioned in the userworkform, that did not solve the initial focus.
Related SR's: SR-A76017
Accepted Solution
American Express
US
Thanks Srinivas (Srinivas Kakani),
We have raised an SR-A76017, which was closed because its not product defect.
So, done further analysis, identified the cause and created SR-A77173 for support, GCS team(Michael Feldhusen) assigned to it has created FDBK-15700 request, as its outside scope of GCS.
Thanks Srinivas (Srinivas Kakani),
We have raised an SR-A76017, which was closed because its not product defect.
So, done further analysis, identified the cause and created SR-A77173 for support, GCS team(Michael Feldhusen) assigned to it has created FDBK-15700 request, as its outside scope of GCS.
Yesterday GCS team has sent an email stating, they are closing SR-A77173 because it was/should be handled in FDBK-15700 request.
If possible, can you please advise on the possible solution timeline for FDBK-15700.
I am little confused as you requested to reach out to GCS again. Please advise on the reason to contact GCS again?
American Express
US
Identified 'window.focus()' present in pzpega_ui_DynamicContainer.js under the functions 'CreateNewWork' and 'OpenWorkByHandle' is causing the PEGA window to come into focus. We have done private edit, commented those steps and tested.. it made PEGA application stay in background.
As this script is part of pzpega_ui_DynamicContainer.js, we are unable to suppress it. Please suggest if there is a way we can achieve this.
Requirement:-
Need to add conditional focus logic in 'CreateNewWork' and 'OpenWorkByHandle' functions present in pzpega_ui_DynamicContainer.js, Pega-UIEngine:07-10-16.
Pegasystems Inc.
IN
I see that the SR is now resolved. I suppose SR-A77173 (resolved to FDBK-15700 ) are effectively referring to the same item
The code that you have identified is something that effects only IE browsers.
FDBK-15700 is actively being considered. We plan to provide a available when rule which can be used to toggle this focus behavior in IE.
Please reach out to GCS for further help.
Accepted Solution
American Express
US
Thanks Srinivas (Srinivas Kakani),
We have raised an SR-A76017, which was closed because its not product defect.
So, done further analysis, identified the cause and created SR-A77173 for support, GCS team(Michael Feldhusen) assigned to it has created FDBK-15700 request, as its outside scope of GCS.
Thanks Srinivas (Srinivas Kakani),
We have raised an SR-A76017, which was closed because its not product defect.
So, done further analysis, identified the cause and created SR-A77173 for support, GCS team(Michael Feldhusen) assigned to it has created FDBK-15700 request, as its outside scope of GCS.
Yesterday GCS team has sent an email stating, they are closing SR-A77173 because it was/should be handled in FDBK-15700 request.
If possible, can you please advise on the possible solution timeline for FDBK-15700.
I am little confused as you requested to reach out to GCS again. Please advise on the reason to contact GCS again?
Pegasystems Inc.
US
Hello Kiran, Srinivas,
Once an Enhancement Request has been created, it is up to Produce Management to decide on when it will be implemented. GCS has no insight into that process but the your Account Executive does, which is why we suggested you engage with her on this matter.
Thank you
- Michael
Updated: 24 Jun 2016 2:24 EDT
Pegasystems Inc.
IN
Since the existing behavior is only IE specific and involved change is marginal, can we re-open the SR and provide an SE item, so we can deliver the hot-fix early next week?
-Sree