Getting Ajax call fail error when running Activity or DT
Getting Ajax call fail error when running Activity or Data transform on a Button click from iOS Custom mobile application built on Pega 7.2.1.
On click of a button user's calling a Data Transform (DT) which has when rules and set-values.
Requirement is to hide and show a section on caseworker portal on click of a button. User is trying to set a property value to true or false on click and based on which the section will be shown or hidden.
"Configuration for Ajax request to call pzRunActionWrapper activity is not supported in offline"
Steps to Reproduce
1. Setup a user with offline enabled in access group and point to pyCaseWorker portal.
2. On pyCaseWorker portal, place a button on work list grid and configure Run Activity or Run Data Transform on click event.
3. Build iOS Custom mobile application by enabling offline capabilities.
4. Install ipa file and login to the application in online and click on the button configured.
Offline capability is to support purely offline applications that could periodically synchronize their data to Pega app server.
And calling an activity from a click event is not supported in an offline enabled app (despite being currently online) in Pega 7.2.1. In Pega 7.2.1 the “Run DT” on button-click is also not supported.
So, neither the When rules inside DT nor the set-values doesn’t matter when the DT itself is not supported in offline.
In Pega 7.2.2 the support for “Run DT” has started.
Here’s the explanation for the reported behavior:
Offline capability is to support purely offline applications that could periodically sync their data to Pega app server.
And calling an activity from a click event is not supported in an offline enabled app (despite being currently online) in Pega 7.2.1.
Set-Value action on button click helps to set a property. For it to work in online/offline/browser/mobile the referred property should be present in DOM and so it must be referred somewhere on the screen.
The function could probably be defined at the Harness level or Userworkform.
If at all users need to update properties pre- and post- of flowactions, then they could use preJS and postJS functions instead of DT’s. Define “preFlowAction$flowActionName” and “postFlowAction$flowActionName” in scripts and these could be referred at Harness level. In the ‘scripts and styles’ tab of Harness.
Most of the functionalities have alternatives/server proxies when in Offline.
And for PegaOffline related doubts, these pages in help could be helpful:
0% found this useful