Question

18
Replies
374
Views
Murthy.1303 Member since 2015 12 posts
Capgemini
Posted: 1 year ago
Last activity: 1 year 2 months ago
Closed

pzTransactionId not updated after pega.u.d.asyncRequest which calls DoSave activity

We are trying to achieve auto safe feature, which would be responsible to Save user in progress data every few mins if the page is stale.

Below is the code I am using. MyActivity calls DoSave activity. Which means a commit is performed and new transaction id is generated.

The first call is successful, however subsequent calls are not. Because the new transaction id is not update on client UI.

This is a high priority client requirement. Any advise on how to resolve this would be greatly appreciated!!


setInterval(function(){ 
   InitiateAutoSave();       
}, 60000);
  
 
  function InitiateAutoSave()
  {
    if(window.parent.ValStudioDirtyCheck==true)
    {
      var callback = {success: SuccessSave, failure: FailureSave};
      var oSafeUrl = null;
      var postData = "";
          
      oSafeUrl = SafeURL_createFromURL("pyActivity=MyActivity&pzPrimaryPageName=pyWorkPage");

      pega.u.d.asyncRequest('POST',oSafeUrl,callback,postData); 
    }
    
  }

***Edited by Moderator Marissa to update platform capability tags; update SR Details****

Data Integration Java and Activities User Interface SR Exists
Moderation Team has archived post
Share this page LinkedIn