System Pages/Properties not available under app requestor context


We ran into an issue related to push notifications. Whenever a new app version is created, users using the mobile build(apk) generated previously using the previous version of the application started to have problems receiving push notifications. It was identified later by GCS that this happened due to a problem with the pysendpushnotifications activity that runs under the app requestor context. We were told that certain system pages/properties won't be available under app requestor context and hence the problem.

Do we know the list of systempages(px prefix) as well as the properties that won't be available under the app requestor context, that is typically available under a browser context? We would like to know these details to account for these gaps during the design phase itself going forward



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

Group Tags


Keep up to date on this post and subscribe to comments

February 11, 2019 - 4:26pm

Hi Sethu,

If you are invoking pySendPushNotification via an asynchronous service or a queued batch process, then you will likely need to have a wrapping activity to establish the context (clipboard pages) that you need.  Can you elaborate on your use case and how exactly you are invoking the activity?

- James

February 25, 2019 - 10:29am
Response to HALLJ


From the mobile channel, when we try to test the push notification feature to a recipient list, this invokes the pysendpushnotification activity, however this wasn't able to identify the most recent app context in preprod/prod leading to a failure.




February 26, 2019 - 6:46am

Hi Sethu,

Problem with push notifications for mentioned use case was fixed in HFix-50704 (for PRPC 7.3.1) and HFix-50447 (PRPC 7.3) and in my opinion is not connected to issue with missing pages/properties as mentioned at

Do you still have problem at your environment with receiving push notifications when using hotfix? How do you invoke pySendPushNotification activity? Is it run from REST service?

Regards, Wiesław



March 4, 2019 - 10:48am
Response to bondw


When we reported this issue, we didn't receive any hotfix(SR-C74940) and we were told that due to tightened security in production, some application level pages/properties are restricted in production leading to this behaviour. 

Please note that this activity gets called directly when we test the push notification functionality from designer studio(common separated list of operators) using the send to everyone button

In the real scenario, the REST Service gets invoked which then identifies the client and pushes the notification, however this also calls the same activity

The problem happened with both the use cases in production and we had to manually override using a wrapper activity(set necessary parameters for pysendpushnotifications) based on another clipboard page(pxThread) that has the application name.