Open APIs

Hi Team,

CTK seems validate the GET APIs for the entity created via POST API and access the input from POST response data. And even PATCH also uses the same ID.

When the object is created via POST, it is created with the initial lifecycle state say "In Design" or "In Study". But, GET api looks for "Active" state for that ID.

Since there is no option to pass the GET url or ID or "version" query param to get the "Active" entity in the "CHANGEME.json", have to relay on the same object as created via POST which is in different state than expected and most of the GET TCs fails due to this.

I understand the fact that, GET api should always return the latest version of an entity and hence expect "Active" but, entity create via POST may not be in "Active" as the same time.

Can you help to understand this validation criteria ? What can be done in API or CTK to be TMF compliant ?

What should be the default state of an entity created via POST and Expected in GET validation ?

Whether the lifecyclestatus of the entity created via POST should be auto reset from initial state to "Active" before validating GET call ?

Should there be option in CTK to send "ID" or "version" query param to get "Active" state entity ? OR if not, whether CTK should validate the GET API for the same state as that of created via POST and for this it has to allow to pass "version" query param to get the same entity ?

Thanks,

Vivek