Genesys CTI User Forum > Genesys-related Development

Pulse - Obtaining Data From External Entities

<< < (2/2)

gen_rtfm:
There is an option to (as I understand it) submit external data to pulse but when I asked customer care about the details I found it rather backwards, I had assumed that pulse would poll for external data rather than be a recipient that the source submits to.

Another option is to create a custom widget; the widget is just a skeleton with JavaScript content. Use that content to fetch your external  data.

The iframe version is definitely the most straightforward approach, any development needed would be done at the target url or it's backend. The only thing to manage there is to make look and feel consistent with the rest of pulse UI.

Skickat från min Mi MIX 3 5G via Tapatalk

abudwill:
After a google search I found your post asking this question last year. Looks like the Pulse API might be what you are talking about here. Seems like a really strange use case the way it is developed. To me it looks like they expose enough methods for an account to authenticate and do things like design / create a view and then even send snapshot data to the view. The external entity would be responsible for continually pushing data to the view via the Pulse API. Definitely a long complicated approach (in my opinion).

The IFrame and integrating to a backend using something like NodeJS looks simple and interesting.

Just read the custom Widget documentation - also looks pretty promising. Might be able to reach out to those external systems to fetch the external data in the custom widget code. Still some questions around how that custom widget would get config details (ex: would it go read an ini file somewhere, use PSDK to read a transaction list).

Interested in hearing from anyone else with an approach not already mentioned here.

[quote author=gen_rtfm link=topic=11648.msg53018#msg53018 date=1594233469]
There is an option to (as I understand it) submit external data to pulse but when I asked customer care about the details I found it rather backwards, I had assumed that pulse would poll for external data rather than be a recipient that the source submits to.

Another option is to create a custom widget; the widget is just a skeleton with JavaScript content. Use that content to fetch your external  data.

The iframe version is definitely the most straightforward approach, any development needed would be done at the target url or it's backend. The only thing to manage there is to make look and feel consistent with the rest of pulse UI.

Skickat från min Mi MIX 3 5G via Tapatalk
[/quote]

Navigation

[0] Message Index

[*] Previous page