@Will Cho I’m attaching one document which detailed the steps I followed. I’m still not getting any response. I would really appreciate your help. Thanks!
ExtractAPI_POC.docx (1.37 MB)
@ParthasarathiRC i only tested with work object, but i would think data object should work, too. Can you force the data instances to resave/commit to DB (e.g. using activity rule) and verify that the real-time extraction Declare Trigger runs? You should be able to use the Tracer. There needs to be an event that cause the DB save/commit to fire the Declare Trigger while the connect api is running and polling.
@William Cho : Does real time bix extract via kafka stream supports oAuth2.0 . Without this our network security will not accept the solution. Any suggestion ?
@Arunkum@r I meant you or your account team to raise a ticket with GCS and follow up directly.
@Will Cho I tested Pega BIX real-time extraction by creating a cluster and topic in Confluent Cloud, and it worked very well. However, I noticed an issue: whenever I delete an existing real-time extract rule in Pega and create a new extract rule, the Declare Trigger rule is not created automatically. I have to create it manually and reference the trigger activity “pzQueueCaseForExtraction”.
@Arunkum@r Glad to hear that the real-time BIX extract also works well with External Kafka using Confluent Cloud!
When you get a chance, could you raise an incident ticket with Pega regarding the Declare Trigger issue and provide details? From what i read, it may be a bug. The new Declare Trigger should be automatically created after deleting old and creating a new Extract rule.
@Will Cho thanks for the response..will it not work only on data class? we dont have case data to extract
@Arunkum@r - I’m working on similar implementation on streaming case data to confluent cloud, i had issues while check-in process for the extract rule when enabled real time processing. I had to create the when rule(pyPerformRealTimeDataExtraction) manually now declare trigger got created and it is running, I had traced the QP as well and no errors in the QP. the problem is I’m not able to messages in the confluent cloud, i can see that topics are getting created but the data is not getting posted, any insights?
@Arunkum@r Glad that it got resolved. Thanks for sharing the additional piece of information about real-time BIX extraction. Very helpful!
@NavdeepK2565 If you read the threads above, i used OAuth 2.0 to call extract APIs. I would also suggest to check with your Pega account contact to confirm.
This article may provide useful information about creating OAuth 2.0 access token.
