Question
ING
BE
Last activity: 19 May 2017 12:21 EDT
Issue facing while sending custom json payload to SendNotificationToIOS (Pega OOTB function)
Hi,
I am trying to send the custom json payload to SendNotificationToIOS (Pega OOTB function) which is specific to the app but I have tried many forms of payloads but nothing is working fine.
Any body did this earlier please let me know.
***Updated by moderator: Lochan to add Categories***
Incessant Technologies
IN
Hi Ashutosh,
You said - SendNotificationToIOS is OOTB function , but in which version ? I tried searching in 72 but could not find ?
Please share error message you are getting while using this function for better understanding of issue.
-Rajesh
ING
BE
Hi rajesh,
Yes, SendNotificationToIOS is a OOTB function and it is present in rule-set version PegaMKT-PusNotification:07-13-01. We are using Pega 7.1.9. I am not getting any error while using this function but I want to send custom JSON payload which is specific to the App(which has to receive the notification in our case).
I have tried with many formats of payloads but it has not rendered correctly on the app. So want to know what kind of json format and in which form this function supports and is there any one who used this function and passed the json payload.
I believe this helps.
Pegasystems Inc.
US
I can see the function in the PegaMKT-PushNotification ruleset, is this the same function you are trying to use? Can you elaborate how you are trying to call this function and what errors are you getting?
ING
BE
I am not getting any error while using this function but I want to send custom JSON payload which is specific to the App(which has to receive the notification in our case) as a parameter value to customfields in this function.
I have tried with many formats of payloads but it has not rendered correctly on the app. So want to know what kind of json format and in which form this function supports and is there any one who used this function and passed the json payload.
Pegasystems Inc.
US
Got it. I have asked the SMEs in this area to respond - this function has been used by Pega Marketing team for push notification - not part of the core platform.
Pegasystems Inc.
US
Hi Ashutosh,
As Kevin mentioned - this is not a Pega 7 OOTB function, but an internal function used by Pega Marketing for its Push Notification support through marketing Offers. For instructions on how to use the Push Notification functionality from within Pega Marketing, refer to the Push Notifications chapter in the Pega Marketing 7.13 User Guide. The section on "Send Additional Values" describes how custom fields can be passed as part of the notification message.
Pega 7 platform does have OOTB notification functionality as well, but I'm not sure if this is available in your version (7.1.9).
Thanks,
~Jai.
ING
BE
Hi Jai,
The section "Send Additional Values" you have mentioned is useful when we are suppose to send the push notification directly using Push notification shape in marketing offer flow but i am using this function in an activity and there we need to send the json payload as a value to Parameter Customfields(one of the parameter value of that function). So i want a sample json structure which this function supports because I have tried with different payloads structures provided on the Apple developer site but none worked for me.
I think this helps in providing an insight to the real issue.
Pegasystems Inc.
US
I wonder why is your real issue. Have you simply tried this for the customFields input parameter:
{"name1": "value1","name2": "value2"}
ING
BE
Hi kevin,
I have tried with different sets and variations of json payload. Ex: {"category":"Category_ContactAction","actions":[{"action":"Action_Contact"}]} and {"aps":{"category":"Category_ContactAction"},"actions":[{"action":"Action_Contact"}]}
These payloads are according to apple documentation and Category_ContactAction is custom action we have created for our app specific and values under action are the keycode actions but nothing getting rendered on the app.
Pegasystems Inc.
US
I will leave this to Jai and his colleagues to answer. I do not have the access to the java source code as it is not part of the platform.