Author Topic: Pulse - Obtaining Data From External Entities  (Read 2019 times)

Offline abudwill

  • Full Member
  • ***
  • Posts: 157
  • Karma: 4
Pulse - Obtaining Data From External Entities
« on: July 09, 2020, 01:33:50 AM »
Hi everyone,

Before I get flamed for not reading documentation - I haven't referenced latest Pulse documentation yet and will be doing that shortly. I am looking to get other peoples experiences and understand what approaches other people have taken in the past.

Have you pulled in external data into a Pulse dashboard? If so, what kind of system were you pulling from and how did you achieve this?

An example of this might be wanting to show some business related data that originates from a database or results in a web service call in a widget on a dashboard.

Regards,
Andrew

Offline gen_rtfm

  • Jr. Member
  • **
  • Posts: 89
  • Karma: 1
Re: Pulse - Obtaining Data From External Entities
« Reply #1 on: July 09, 2020, 02:02:44 AM »
Hi,

Is the external data available as attached data?
In that case you could use statserver filters to count interactions where s specific action occurred where that attached data has been set, or set to a specific value. More recent versions of statserver also has a function to distinguish the tracked events based on a certain attached data, giving you subtotals based on the different values found amongst the key you're distinguishing by - I haven't used that myself though so I can't walk you through it.

If you're not attaching the data or and it is not feasible to do so I'd look in to firing userevents and counting & distinguishing them by statserver-filters.

Br


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


Offline hsujdik

  • Sr. Member
  • ****
  • Posts: 431
  • Karma: 16
Re: Pulse - Obtaining Data From External Entities
« Reply #2 on: July 09, 2020, 03:07:07 AM »
You can embed an IFrame on pulse. That IFrame could be either pointing to a server-side dynamic HTML or pull data via AJAX

Offline abudwill

  • Full Member
  • ***
  • Posts: 157
  • Karma: 4
Re: Pulse - Obtaining Data From External Entities
« Reply #3 on: July 09, 2020, 03:29:39 AM »
In this case the data is not available as attached data - truly external.

In the past I have actually developed and leveraged custom stat server java extension to pull external data in (similar to how some Genesys provided stat server java extensions work). I am trying to avoid that route in this instance. Thanks for your feedback.

Hi,

Is the external data available as attached data?
In that case you could use statserver filters to count interactions where s specific action occurred where that attached data has been set, or set to a specific value. More recent versions of statserver also has a function to distinguish the tracked events based on a certain attached data, giving you subtotals based on the different values found amongst the key you're distinguishing by - I haven't used that myself though so I can't walk you through it.

If you're not attaching the data or and it is not feasible to do so I'd look in to firing userevents and counting & distinguishing them by statserver-filters.

Br


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

Offline abudwill

  • Full Member
  • ***
  • Posts: 157
  • Karma: 4
Re: Pulse - Obtaining Data From External Entities
« Reply #4 on: July 09, 2020, 03:30:18 AM »
Definitely an interesting idea, thanks for the feedback.

You can embed an IFrame on pulse. That IFrame could be either pointing to a server-side dynamic HTML or pull data via AJAX

Offline gen_rtfm

  • Jr. Member
  • **
  • Posts: 89
  • Karma: 1
Re: Pulse - Obtaining Data From External Entities
« Reply #5 on: July 09, 2020, 03:37:49 AM »
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


Offline abudwill

  • Full Member
  • ***
  • Posts: 157
  • Karma: 4
Re: Pulse - Obtaining Data From External Entities
« Reply #6 on: July 09, 2020, 05:37:02 AM »
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.

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