We have migrated our application from 6.1 to 7.2. We are using custom control to reload the section based on certain conditions using below code. The code is working fine in 6.1 but in 7.2 environment preactivity is called after the section load and because of that the updated data is not displayed in screen.
I've tried using the api pega.u.d.reloadSection as you mentioned in Pega 7.2.x. For my case, Pre-activity called first and then reloadSection activity. This confirms that the pega.u.d.reloadSection api call structure remains same. I've verified the call stack in Tracer.
I suspect that the custom control which you have used might cause the behaviour. Would you be able to attach the custom control code ?
Please feel free to reply your thoughts on this.
Posted: 5 years ago
Posted: 26 May 2017 14:36 EDT
Neeraj Drolia (NEERAJ DROLIA)
The reloadSection API is present in pzpega_ui_doc_engine.js. Why not put a debugger there and check what's happening?
And the ReloadSection calls reload API, then from there, strUrlSF.put("pyActivity", "ReloadSection"); i.e., ReloadSection activity with params PreActivity = "your activity".
Now you could probably check the Tracer, why ReloadSection activity missed to call its Pre-Activity.
In the Tracer anyway, you see a call to ReloadSection is made first and only then the ReloadSection calls the Preactivity. Are you confused with this order!? If yes, then enable the Stream Rules in Tracer which gives you a more clarity.