Question
Legato Health Technologies
IN
Last activity: 16 Oct 2018 12:03 EDT
doFormSubmit on click of button replaces screen layout with perform harness
We have a functionality wherein on click of a button, run script action is triggered for doFormSubmit function. The portal consists of Header_Left screen layout and the button exists in main area of the portal of submission. On submission, the perform harness with the requisite data should load in the main harness. This isn't happening and the whole screen layout is being replaced by the perform harness. Ideally it should only load in the main area of the screen layout.
On further investigation, I could find that the data-portalharnessinsname isn't being set to portal name while in ideal case this gets set to screen layout harness name. Not sure if this is the problem out here but would need suggestions to fix the said behavior.
Note: pega.u.d.pyStreamNameForGadget is being set to Perform harness and ideally, as far as my understanding on this, the set Gadget name (harness) should load in the main area and not replace the screen layout.
Also, the said behavior occurs only when the doFormSubmit action is performed right after screen layout is loaded. If any other action such as trigger of any event from left sidebar area/header area, click of link or onchange of dropdown in right main area, etc. is performed before any doFormSubmit action then, it works perfectly fine loading the subsequent harness in the right main area as desired.
**Moderation Team has archived post**
We have a functionality wherein on click of a button, run script action is triggered for doFormSubmit function. The portal consists of Header_Left screen layout and the button exists in main area of the portal of submission. On submission, the perform harness with the requisite data should load in the main harness. This isn't happening and the whole screen layout is being replaced by the perform harness. Ideally it should only load in the main area of the screen layout.
On further investigation, I could find that the data-portalharnessinsname isn't being set to portal name while in ideal case this gets set to screen layout harness name. Not sure if this is the problem out here but would need suggestions to fix the said behavior.
Note: pega.u.d.pyStreamNameForGadget is being set to Perform harness and ideally, as far as my understanding on this, the set Gadget name (harness) should load in the main area and not replace the screen layout.
Also, the said behavior occurs only when the doFormSubmit action is performed right after screen layout is loaded. If any other action such as trigger of any event from left sidebar area/header area, click of link or onchange of dropdown in right main area, etc. is performed before any doFormSubmit action then, it works perfectly fine loading the subsequent harness in the right main area as desired.
**Moderation Team has archived 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
Pegasystems Inc.
IN
Hi All,
ROOT CAUSE
An issue in the custom application code or rules:
Issue is happening because "pyActionInfo" page is not present and Pega is expecting this page to be present while generating the side and header panel HTML.
Whenever user clicks on side panel links, "doUIAction" activity is called which will create "pyActionInfo" page, for this reason it is working fine whenever user navigates from left panel links.
Hi All,
ROOT CAUSE
An issue in the custom application code or rules:
Issue is happening because "pyActionInfo" page is not present and Pega is expecting this page to be present while generating the side and header panel HTML.
Whenever user clicks on side panel links, "doUIAction" activity is called which will create "pyActionInfo" page, for this reason it is working fine whenever user navigates from left panel links.
In addition, doFormSubmit/Finish Assignment is process-work related action and it should be configured in a flow where next screen is shown where the page is automatically created.
In this use-case, as there is no flow involved, the page need to be created manually.
RESOLUTION
Perform the following local-change:
Create "pyActionInfo" page before doing "doFormSubmit"/FinishAssignment call.
Action 1: Run Activity -> Create new step page "pyActionInfo" of class "Embed-UI-RunTime-Element"
Action 2: doFormSubmit or FinishAssignment
Accepted Solution
Pegasystems Inc.
IN
Hi All,
ROOT CAUSE
An issue in the custom application code or rules:
Issue is happening because "pyActionInfo" page is not present and Pega is expecting this page to be present while generating the side and header panel HTML.
Whenever user clicks on side panel links, "doUIAction" activity is called which will create "pyActionInfo" page, for this reason it is working fine whenever user navigates from left panel links.
Hi All,
ROOT CAUSE
An issue in the custom application code or rules:
Issue is happening because "pyActionInfo" page is not present and Pega is expecting this page to be present while generating the side and header panel HTML.
Whenever user clicks on side panel links, "doUIAction" activity is called which will create "pyActionInfo" page, for this reason it is working fine whenever user navigates from left panel links.
In addition, doFormSubmit/Finish Assignment is process-work related action and it should be configured in a flow where next screen is shown where the page is automatically created.
In this use-case, as there is no flow involved, the page need to be created manually.
RESOLUTION
Perform the following local-change:
Create "pyActionInfo" page before doing "doFormSubmit"/FinishAssignment call.
Action 1: Run Activity -> Create new step page "pyActionInfo" of class "Embed-UI-RunTime-Element"
Action 2: doFormSubmit or FinishAssignment