Question
Express Scripts
US
Last activity: 16 Oct 2018 12:03 EDT
preactivty is called after the section reload.
Hi,
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.
pega.u.d.reloadSection(pega.u.d.getSectionByName(Section Name','',''), 'Activity Name', '', false , true, '-1', false);
Please let me know if any one has faced similar issue and resolution for the issue.
**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.
Pegasystems Inc.
IN
Hi,
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.
Thank you,
Express Scripts
US
We are using below control:
<script>
function DltCnf(Status){
var oSafeUrl = new SafeURL("Class.Activity1");
oSafeUrl.put("Caption","Delete Data");
var callback = {
success : function(oResponse)
{
var strReturn = oResponse.responseText;
if(oResponse.responseText == "success")
{
var r= confirm("Are you sure you want to delete?");
if(r)
{
pega.u.d.reloadSection(pega.u.d.getSectionByName('Section1','',''), 'Activity2', '', false , true, '-1', false);
}
}
else {
alert(oResponse.responseText);
}
},
failure : function(oResponse) {
alert("Update Failure");
}
};
var request = pega.util.Connect.asyncRequest('GET',oSafeUrl.toURL(),callback);
}
</script>
We are using below control:
<script>
function DltCnf(Status){
var oSafeUrl = new SafeURL("Class.Activity1");
oSafeUrl.put("Caption","Delete Data");
var callback = {
success : function(oResponse)
{
var strReturn = oResponse.responseText;
if(oResponse.responseText == "success")
{
var r= confirm("Are you sure you want to delete?");
if(r)
{
pega.u.d.reloadSection(pega.u.d.getSectionByName('Section1','',''), 'Activity2', '', false , true, '-1', false);
}
}
else {
alert(oResponse.responseText);
}
},
failure : function(oResponse) {
alert("Update Failure");
}
};
var request = pega.util.Connect.asyncRequest('GET',oSafeUrl.toURL(),callback);
}
</script>
<table border="0" class="buttonMainTable" cellspacing="0" cellpadding="0" <pega:when test='param.TableId != ""'>id="<pega:reference name="$save(strTableId)"/>"</pega:when> >
<tr>
<td class="buttonTdLeft"> </td>
<td nowrap class="buttonTdMiddle">
<button class="buttonTdButton" <pega:withPage name="pyDisplayHarness"><pega:when name='DeleteVisibleWhen'>disabled </pega:when></pega:withPage> onclick="DltCnf('<pega:reference name="Param.Status"/>');" PEGA_VERSION="HTMLPROPERTY">
<pega:when test='param.Image != ""'><img style="padding-right:3px;vertical-align:middle"
<%
String strImage = tools.getSaveValue("strImage");
if(strImage.indexOf(".")!=-1)
tools.appendString("src=" + strImage);
else
tools.appendString("class=" + strImage);
%>
></img></pega:when>Delete</button>
</td>
<td class="buttonTdRight" onclick="if(typeof(pega) !='undefined' && pega.u.d) pega.u.d.fireButtonClick(this.parentNode);"> </td>
</tr>
</table>
Pegasystems Inc.
US
Hey Neeraj,
Can you try this -
Instead of specifying the pre-activity in the call to reloadSection(), try running the activity first...
var oSafeUrl = new SafeURL("<ClassName>.<ActivityName>");
var request = pega.u.d.asyncRequest('GET',oSafeUrl);
then call the reloadSection()...
if need be, do a setTimeout() to wait for a x number of milliseconds before you actually call reloadSection().
See if this approach works out for you.
Thank you,
Sunny
Northbridge
CA
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.