Open APIs

------------------------------
Rajesh pundru
Verizon Communications
------------------------------

Hi Rajesh
This is a delicate issue. On the one hand, if the API conformance defines attributes as optional, it means that a consumer expecting to meet a conforming implementation will "know" that it doesn't need to send those attributes. And then when it encounters your implementation with these attributes as mandatory it will fail.
On the other hand, vendors and other API implementers may want the freedom to define additional mandatory attributes for the proper functioning of their business.
It's best taken up with the CTK focal @Henrique Rodrigues, who can hopefully explain how to adjust the CTK to support additional mandatory attributes and yet still achieve a positive conformance result.
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.
------------------------------

Original Message:
Sent: Mar 28, 2022 10:00
From: Rajesh pundru
Subject: Payloads in CTK

1. Payloads in CTK have only minimum/mandatory attributes as per specification.
   What if our implementation has other mandatory attributes ?
   Can the postman collection be modified to add extra mandatory fields ?

2. Our understanding is, we can give payloads in config.json to add our mandatory fields.

    But the QuoteManagement API(TMF-648) CTK doesn't have config.json. 

3. In the ProductOrdering API(TMF-622), even after adding custom payload to the config.json, pmtest.json is NOT getting updated with that payload.

How do we add extra mandatory fields in the payloads?

  

------------------------------
Rajesh pundru
Verizon Communications
------------------------------

Thanks for the reply Jonathan..
I am new to this forum.. not sure if I can expect a reply from @Henrique Rodrigues in here or I would have to follow up officially through email or any request page ?​​
Any idea, Jonathan ? 
Thanks in advance :)

------------------------------
Rajesh pundru
Verizon Communications
------------------------------

Original Message:
Sent: Mar 28, 2022 14:24
From: Jonathan Goldberg
Subject: Payloads in CTK

Hi Rajesh
This is a delicate issue. On the one hand, if the API conformance defines attributes as optional, it means that a consumer expecting to meet a conforming implementation will "know" that it doesn't need to send those attributes. And then when it encounters your implementation with these attributes as mandatory it will fail.
On the other hand, vendors and other API implementers may want the freedom to define additional mandatory attributes for the proper functioning of their business.
It's best taken up with the CTK focal @Henrique Rodrigues, who can hopefully explain how to adjust the CTK to support additional mandatory attributes and yet still achieve a positive conformance result.
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.

Original Message:
Sent: Mar 28, 2022 10:00
From: Rajesh pundru
Subject: Payloads in CTK

1. Payloads in CTK have only minimum/mandatory attributes as per specification.
   What if our implementation has other mandatory attributes ?
   Can the postman collection be modified to add extra mandatory fields ?

2. Our understanding is, we can give payloads in config.json to add our mandatory fields.

    But the QuoteManagement API(TMF-648) CTK doesn't have config.json. 

3. In the ProductOrdering API(TMF-622), even after adding custom payload to the config.json, pmtest.json is NOT getting updated with that payload.

How do we add extra mandatory fields in the payloads?

  

------------------------------
Rajesh pundru
Verizon Communications
------------------------------

I have emailed him directly with this message thread, so hopefully he will see it.

------------------------------
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.
------------------------------

Original Message:
Sent: Mar 28, 2022 17:08
From: Rajesh pundru
Subject: Payloads in CTK

Thanks for the reply Jonathan..
I am new to this forum.. not sure if I can expect a reply from @Henrique Rodrigues in here or I would have to follow up officially through email or any request page ?​​
Any idea, Jonathan ?
Thanks in advance :)

------------------------------
Rajesh pundru
Verizon Communications

Original Message:
Sent: Mar 28, 2022 14:24
From: Jonathan Goldberg
Subject: Payloads in CTK

Hi Rajesh
This is a delicate issue. On the one hand, if the API conformance defines attributes as optional, it means that a consumer expecting to meet a conforming implementation will "know" that it doesn't need to send those attributes. And then when it encounters your implementation with these attributes as mandatory it will fail.
On the other hand, vendors and other API implementers may want the freedom to define additional mandatory attributes for the proper functioning of their business.
It's best taken up with the CTK focal @Henrique Rodrigues, who can hopefully explain how to adjust the CTK to support additional mandatory attributes and yet still achieve a positive conformance result.
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.

Original Message:
Sent: Mar 28, 2022 10:00
From: Rajesh pundru
Subject: Payloads in CTK

1. Payloads in CTK have only minimum/mandatory attributes as per specification.
   What if our implementation has other mandatory attributes ?
   Can the postman collection be modified to add extra mandatory fields ?

2. Our understanding is, we can give payloads in config.json to add our mandatory fields.

    But the QuoteManagement API(TMF-648) CTK doesn't have config.json. 

3. In the ProductOrdering API(TMF-622), even after adding custom payload to the config.json, pmtest.json is NOT getting updated with that payload.

How do we add extra mandatory fields in the payloads?

  

------------------------------
Rajesh pundru
Verizon Communications
------------------------------

Hello @Rajesh pundru​

1. Payloads in CTK have only minimum/mandatory attributes as per specification.
   What if our implementation has other mandatory attributes ?
   Can the postman collection be modified to add extra mandatory fields ?

It is not a problem for your implementation to have extra mandatory fields.
Any CTK published recently will have a config.json file. This file can be used to extend the headers, or the Payload that will be sent on the POST request, for APIs where POST is mandatory.

I will investigate 2 and 3 and get back to you by e-mail.

Best Regards,


------------------------------
Henrique Rodrigues
TM Forum
------------------------------

Original Message:
Sent: Mar 28, 2022 17:08
From: Rajesh pundru
Subject: Payloads in CTK

Thanks for the reply Jonathan..
I am new to this forum.. not sure if I can expect a reply from @Henrique Rodrigues in here or I would have to follow up officially through email or any request page ?​​
Any idea, Jonathan ?
Thanks in advance :)

------------------------------
Rajesh pundru
Verizon Communications

Original Message:
Sent: Mar 28, 2022 14:24
From: Jonathan Goldberg
Subject: Payloads in CTK

Hi Rajesh
This is a delicate issue. On the one hand, if the API conformance defines attributes as optional, it means that a consumer expecting to meet a conforming implementation will "know" that it doesn't need to send those attributes. And then when it encounters your implementation with these attributes as mandatory it will fail.
On the other hand, vendors and other API implementers may want the freedom to define additional mandatory attributes for the proper functioning of their business.
It's best taken up with the CTK focal @Henrique Rodrigues, who can hopefully explain how to adjust the CTK to support additional mandatory attributes and yet still achieve a positive conformance result.
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.

Original Message:
Sent: Mar 28, 2022 10:00
From: Rajesh pundru
Subject: Payloads in CTK

1. Payloads in CTK have only minimum/mandatory attributes as per specification.
   What if our implementation has other mandatory attributes ?
   Can the postman collection be modified to add extra mandatory fields ?

2. Our understanding is, we can give payloads in config.json to add our mandatory fields.

    But the QuoteManagement API(TMF-648) CTK doesn't have config.json. 

3. In the ProductOrdering API(TMF-622), even after adding custom payload to the config.json, pmtest.json is NOT getting updated with that payload.

How do we add extra mandatory fields in the payloads?

  

------------------------------
Rajesh pundru
Verizon Communications
------------------------------

Hi @Henrique Rodrigues ,

Thanks for the reply.​

Any update on below points ?

"
2. Our understanding is, we can give payloads in config.json to add our mandatory fields.



​​

------------------------------
Rajesh pundru
Verizon Communications
------------------------------

Original Message:
Sent: Mar 29, 2022 04:50
From: Henrique Rodrigues
Subject: Payloads in CTK

Hello @Rajesh pundru​

1. Payloads in CTK have only minimum/mandatory attributes as per specification.
   What if our implementation has other mandatory attributes ?
   Can the postman collection be modified to add extra mandatory fields ?

It is not a problem for your implementation to have extra mandatory fields.
Any CTK published recently will have a config.json file. This file can be used to extend the headers, or the Payload that will be sent on the POST request, for APIs where POST is mandatory.

I will investigate 2 and 3 and get back to you by e-mail.

Best Regards,


------------------------------
Henrique Rodrigues
TM Forum

Original Message:
Sent: Mar 28, 2022 17:08
From: Rajesh pundru
Subject: Payloads in CTK

Thanks for the reply Jonathan..
I am new to this forum.. not sure if I can expect a reply from @Henrique Rodrigues in here or I would have to follow up officially through email or any request page ?​​
Any idea, Jonathan ?
Thanks in advance :)

------------------------------
Rajesh pundru
Verizon Communications

Original Message:
Sent: Mar 28, 2022 14:24
From: Jonathan Goldberg
Subject: Payloads in CTK

Hi Rajesh
This is a delicate issue. On the one hand, if the API conformance defines attributes as optional, it means that a consumer expecting to meet a conforming implementation will "know" that it doesn't need to send those attributes. And then when it encounters your implementation with these attributes as mandatory it will fail.
On the other hand, vendors and other API implementers may want the freedom to define additional mandatory attributes for the proper functioning of their business.
It's best taken up with the CTK focal @Henrique Rodrigues, who can hopefully explain how to adjust the CTK to support additional mandatory attributes and yet still achieve a positive conformance result.
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.

Original Message:
Sent: Mar 28, 2022 10:00
From: Rajesh pundru
Subject: Payloads in CTK

1. Payloads in CTK have only minimum/mandatory attributes as per specification.
   What if our implementation has other mandatory attributes ?
   Can the postman collection be modified to add extra mandatory fields ?

2. Our understanding is, we can give payloads in config.json to add our mandatory fields.

    But the QuoteManagement API(TMF-648) CTK doesn't have config.json. 

3. In the ProductOrdering API(TMF-622), even after adding custom payload to the config.json, pmtest.json is NOT getting updated with that payload.

How do we add extra mandatory fields in the payloads?

  

------------------------------
Rajesh pundru
Verizon Communications
------------------------------

Hi @Henrique Rodrigues

We are also facing the same issue #3 described above ​​​(3. CTK fails even after adding custom payload to the config.json) when running TMF638 Service Inventory API CTK.

We tried to pass a couple of internal mandatory parameters for POST operation in config.json, but they seem to be ignored once CTK runs causing failure. Is there an issue with this CTK or are we doing something wrong? 

Appreciate your help
Regards,

------------------------------
Leo Hodgson
Cerillion Technologies Limited
------------------------------

Original Message:
Sent: Apr 01, 2022 09:21
From: Rajesh pundru
Subject: Payloads in CTK

Hi @Henrique Rodrigues ,

Thanks for the reply.​

Any update on below points ?

"
2. Our understanding is, we can give payloads in config.json to add our mandatory fields.

    But the QuoteManagement API(TMF-648) CTK doesn't have config.json. 

3. In the ProductOrdering API(TMF-622), even after adding custom payload to the config.json, pmtest.json is NOT getting updated with that payload.
"

​​

------------------------------
Rajesh pundru
Verizon Communications

Original Message:
Sent: Mar 29, 2022 04:50
From: Henrique Rodrigues
Subject: Payloads in CTK

Hello @Rajesh pundru​

1. Payloads in CTK have only minimum/mandatory attributes as per specification.
   What if our implementation has other mandatory attributes ?
   Can the postman collection be modified to add extra mandatory fields ?

It is not a problem for your implementation to have extra mandatory fields.
Any CTK published recently will have a config.json file. This file can be used to extend the headers, or the Payload that will be sent on the POST request, for APIs where POST is mandatory.

I will investigate 2 and 3 and get back to you by e-mail.

Best Regards,


------------------------------
Henrique Rodrigues
TM Forum

Original Message:
Sent: Mar 28, 2022 17:08
From: Rajesh pundru
Subject: Payloads in CTK

Thanks for the reply Jonathan..
I am new to this forum.. not sure if I can expect a reply from @Henrique Rodrigues in here or I would have to follow up officially through email or any request page ?​​
Any idea, Jonathan ?
Thanks in advance :)

------------------------------
Rajesh pundru
Verizon Communications

Original Message:
Sent: Mar 28, 2022 14:24
From: Jonathan Goldberg
Subject: Payloads in CTK

Hi Rajesh
This is a delicate issue. On the one hand, if the API conformance defines attributes as optional, it means that a consumer expecting to meet a conforming implementation will "know" that it doesn't need to send those attributes. And then when it encounters your implementation with these attributes as mandatory it will fail.
On the other hand, vendors and other API implementers may want the freedom to define additional mandatory attributes for the proper functioning of their business.
It's best taken up with the CTK focal @Henrique Rodrigues, who can hopefully explain how to adjust the CTK to support additional mandatory attributes and yet still achieve a positive conformance result.
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.

Original Message:
Sent: Mar 28, 2022 10:00
From: Rajesh pundru
Subject: Payloads in CTK

1. Payloads in CTK have only minimum/mandatory attributes as per specification.
   What if our implementation has other mandatory attributes ?
   Can the postman collection be modified to add extra mandatory fields ?

2. Our understanding is, we can give payloads in config.json to add our mandatory fields.

    But the QuoteManagement API(TMF-648) CTK doesn't have config.json. 

3. In the ProductOrdering API(TMF-622), even after adding custom payload to the config.json, pmtest.json is NOT getting updated with that payload.

How do we add extra mandatory fields in the payloads?

  

------------------------------
Rajesh pundru
Verizon Communications
------------------------------