While transferring updated Call data from a Pega system to a external system, TServer expects the information to be passed from Pega using a function “RequestUpdateUserData” (part of Genesys SDK). This will allow the data to be passed with the KVP pyUserData. The function works like an API call. Is there a similar behaviour in Pega where the Call Data can be updated through API call rather than EventCall?
There are two options to attach data to call as part of a transfer using Genesys integration :
-
Attach data to the consultation call leg - this is achieved by customizing a Pega Call data transform
-
Update call data on the original call leg - this requires invoking a Pega Call Activity with the appropriate parameters.
Which option is best suited for your use case ?
Regards,
Bob