TM Forum Community

Hi Team,

During CTK execution, TMF651- Agreement Management API is expecting "engagedPartyRole attribute"  in response while as per swagger , there is no such attribute/field available in object. Can someone please guide which is this attribute in Agreement <Post> operation?

Currently our test cases<Response has engagedPartyRole attribute> are going failed due to missing this attribute in response even after getting engageParty object in response?

The engagedParty attribute is mandatory in POST. The value is an array of RelatedParty which includes the role attribute.

Hi Team,

During CTK execution, TMF651- Agreement Management API is expecting "engagedPartyRole attribute"  in response while as per swagger , there is no such attribute/field available in object. Can someone please guide which is this attribute in Agreement <Post> operation?

Currently our test cases<Response has engagedPartyRole attribute> are going failed due to missing this attribute in response even after getting engageParty object in response?

This is a bug.

I see now that the TMF651 Conformance Profile has incorrectly included engagedPartyRole as a mandatory attribute of the Agreement object, however no such attribute exists in the Swagger, or anywhere else.  The engaged part role would be found in the role attribute of a RelatedParty object included in the array value of the engagedParty attribute.

The engagedParty attribute is mandatory in POST. The value is an array of RelatedParty which includes the role attribute.

Hi Team,

During CTK execution, TMF651- Agreement Management API is expecting "engagedPartyRole attribute"  in response while as per swagger , there is no such attribute/field available in object. Can someone please guide which is this attribute in Agreement <Post> operation?

Currently our test cases<Response has engagedPartyRole attribute> are going failed due to missing this attribute in response even after getting engageParty object in response?

Thanks a lot Vance for update.

Can you please guide me, how can we raise such bug to TMF team?

This is a bug.

I see now that the TMF651 Conformance Profile has incorrectly included engagedPartyRole as a mandatory attribute of the Agreement object, however no such attribute exists in the Swagger, or anywhere else.  The engaged part role would be found in the role attribute of a RelatedParty object included in the array value of the engagedParty attribute.

The engagedParty attribute is mandatory in POST. The value is an array of RelatedParty which includes the role attribute.

Hi Team,

During CTK execution, TMF651- Agreement Management API is expecting "engagedPartyRole attribute"  in response while as per swagger , there is no such attribute/field available in object. Can someone please guide which is this attribute in Agreement <Post> operation?

Currently our test cases<Response has engagedPartyRole attribute> are going failed due to missing this attribute in response even after getting engageParty object in response?

Thanks Chetan and Vance

I've raised a Jira issue to the Open API team. I cannot make any commitment on when this will be fixed, but at least it's a start.

Thanks a lot Vance for update.

Can you please guide me, how can we raise such bug to TMF team?

This is a bug.

I see now that the TMF651 Conformance Profile has incorrectly included engagedPartyRole as a mandatory attribute of the Agreement object, however no such attribute exists in the Swagger, or anywhere else.  The engaged part role would be found in the role attribute of a RelatedParty object included in the array value of the engagedParty attribute.

The engagedParty attribute is mandatory in POST. The value is an array of RelatedParty which includes the role attribute.

Hi Team,

During CTK execution, TMF651- Agreement Management API is expecting "engagedPartyRole attribute"  in response while as per swagger , there is no such attribute/field available in object. Can someone please guide which is this attribute in Agreement <Post> operation?

Currently our test cases<Response has engagedPartyRole attribute> are going failed due to missing this attribute in response even after getting engageParty object in response?

Thanks a lot Jonathan for raising JIRA.

We have one more query here, This API CTK is executing two POST operation for Agreement operation only. Does it valid or its also bug?

First post will be executed with config.json payload and another POST is taking payload from ctk collection json. Second  POST payload is not passing all the CTK required attributes.

Thanks Chetan and Vance

I've raised a Jira issue to the Open API team. I cannot make any commitment on when this will be fixed, but at least it's a start.

Thanks a lot Vance for update.

Can you please guide me, how can we raise such bug to TMF team?

This is a bug.

I see now that the TMF651 Conformance Profile has incorrectly included engagedPartyRole as a mandatory attribute of the Agreement object, however no such attribute exists in the Swagger, or anywhere else.  The engaged part role would be found in the role attribute of a RelatedParty object included in the array value of the engagedParty attribute.

The engagedParty attribute is mandatory in POST. The value is an array of RelatedParty which includes the role attribute.

Hi Team,

During CTK execution, TMF651- Agreement Management API is expecting "engagedPartyRole attribute"  in response while as per swagger , there is no such attribute/field available in object. Can someone please guide which is this attribute in Agreement <Post> operation?

Currently our test cases<Response has engagedPartyRole attribute> are going failed due to missing this attribute in response even after getting engageParty object in response?