Open APIs

Hi, I have the next question:
If I have an appoinment modified by another system (e.g. app, whatsapp, ivr) how can I identify the system who made the patch?
What structure on payload Can I use?
Apply on payload or header?

Regards
Cris

------------------------------
Cristian Medina
Telecom Argentina, S.A.
------------------------------

Hi Cris
This is a more general issue than just for appointments. You might want to store or audit any entity creation or change with this type of information.
I would suggest to add another custom field to the HTTP header, and then you can store this information on your entity persistence store (and send to audit log if needed).
Hope it helps/

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------

Thanks you Jonathan!
   It's very helpfull. Let me complete the use case:
   The information of the system who patch the entity (appointment in my case) has to be sended throght an kafka event to being consumed by the CRM. The CRM needs to identify which was the system who patched the entity

Under this header option, it still be valid? Or may be apply another option?

Thanks

------------------------------
Cristian Medina
Telecom Argentina, S.A.
------------------------------

Original Message:
Sent: Nov 30, 2022 02:51
From: Jonathan Goldberg
Subject: Identify system who patch appointment

Hi Cris
This is a more general issue than just for appointments. You might want to store or audit any entity creation or change with this type of information.
I would suggest to add another custom field to the HTTP header, and then you can store this information on your entity persistence store (and send to audit log if needed).
Hope it helps/

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------

Dear Cristian, 

For this use case, where you are using Kafka to get the information in CRM; I believe the easiest way would be to do it by using different Kafka topics for each system. To elaborate this, you could publish the information from whatsapp on topic-x and from IVR on topic-y. While subscribing the same, since you have separate topics, you would know the only authorized publisher. I would suggest you look at the cost aspect of this solution though. 

I welcome any feedback on this.

All the best!

------------------------------
Gaurav Sinha
Infosys
------------------------------

Original Message:
Sent: Nov 30, 2022 06:34
From: Cristian Medina
Subject: Identify system who patch appointment

Thanks you Jonathan!
   It's very helpfull. Let me complete the use case:
   The information of the system who patch the entity (appointment in my case) has to be sended throght an kafka event to being consumed by the CRM. The CRM needs to identify which was the system who patched the entity

Under this header option, it still be valid? Or may be apply another option?

Thanks

------------------------------
Cristian Medina
Telecom Argentina, S.A.
------------------------------


Original Message:
Sent: Nov 30, 2022 02:51
From: Jonathan Goldberg
Subject: Identify system who patch appointment

Hi Cris
This is a more general issue than just for appointments. You might want to store or audit any entity creation or change with this type of information.
I would suggest to add another custom field to the HTTP header, and then you can store this information on your entity persistence store (and send to audit log if needed).
Hope it helps/

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.

Thanks Gaurav,
   Currently we have a unique topic for appointmentEvents. The CRM consumes all those events from there. As you suscpect, this change it would be very cost.
  I think it could be identify into the body struture, if whoud be possible

Regards

------------------------------
Cristian Medina
Telecom Argentina, S.A.
------------------------------

Original Message:
Sent: Nov 30, 2022 10:58
From: Gaurav Sinha
Subject: Identify system who patch appointment

Dear Cristian,

For this use case, where you are using Kafka to get the information in CRM; I believe the easiest way would be to do it by using different Kafka topics for each system. To elaborate this, you could publish the information from whatsapp on topic-x and from IVR on topic-y. While subscribing the same, since you have separate topics, you would know the only authorized publisher. I would suggest you look at the cost aspect of this solution though.

I welcome any feedback on this.

All the best!

------------------------------
Gaurav Sinha
Infosys
------------------------------


Original Message:
Sent: Nov 30, 2022 06:34
From: Cristian Medina
Subject: Identify system who patch appointment

Thanks you Jonathan!
   It's very helpfull. Let me complete the use case:
   The information of the system who patch the entity (appointment in my case) has to be sended throght an kafka event to being consumed by the CRM. The CRM needs to identify which was the system who patched the entity

Under this header option, it still be valid? Or may be apply another option?

Thanks

------------------------------
Cristian Medina
Telecom Argentina, S.A.


Original Message:
Sent: Nov 30, 2022 02:51
From: Jonathan Goldberg
Subject: Identify system who patch appointment

Hi Cris
This is a more general issue than just for appointments. You might want to store or audit any entity creation or change with this type of information.
I would suggest to add another custom field to the HTTP header, and then you can store this information on your entity persistence store (and send to audit log if needed).
Hope it helps/

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.