Hi Kinshuk,
We have these 6 notifications defined for this API
Notifications related to ServiceTest:
- ServiceTestCreateEvent
- ServiceTestAttributeValueChangeEvent
- ServiceTestDeleteEvent
Notifications related to ServiceTestSpecification:
- ServiceTestSpecificationCreateEvent
- ServiceTestSpecificationAttributeValueChangeEvent
- ServiceTestSpecificationDeleteEvent
Why can't you use the ServiceTestAttributeValueChangeEvent for the state change?
In v4.1 I have also added the suggested list of states in the state definition to align with the list of states used in the 7xx test APIs but could not make it an enumeration due to backward compatibility.
see
state
|
A string. The actual state the service test is in. Recommended states are found in ExecutionStateType schema possible values include acknowledged, rejected, pending, inProgress, cancelled, completed and failed.
|
Note that our Open API table is still pointing to the 4.0 version for the user guide rather than the 4.1 but I have reported the issue and it should get fixed shortly.
@Alan Pope to let us know when the table is updated.
------------------------------
Johanne Mayer
MayerConsult Inc
------------------------------
Original Message:
Sent: Aug 05, 2021 09:48
From: Kinshuk Kulshreshtha
Subject: [TMF653] Bug/Feature that ServiceTest.validFor is writeable
Hi Johanne,
Great to know that you are working on enhancements to TMF653. Currently it does not have a StateChange Event, which is needed to notify when the state of the Test is changed (like In-Progress, Complete etc.) Is it already being taken care of in your planned enhancements or I should create a new Enhancement request for this?
------------------------------
Kinshuk Kulshreshtha
Oracle Corporation
My views posted on this forum are personal, and do not reflect the position of my employer or TM Forum.
Original Message:
Sent: Mar 09, 2021 06:40
From: Johanne Mayer
Subject: [TMF653] Bug/Feature that ServiceTest.validFor is writeable
Hi, I am working on some enhancements on TMF653 so I will look into it.
Regards.... Johanne
------------------------------
Johanne Mayer
MayerConsult Inc
Original Message:
Sent: Mar 09, 2021 01:55
From: Jan Lemmermann
Subject: [TMF653] Bug/Feature that ServiceTest.validFor is writeable
Thanks @Jonathan Goldberg makes sense if this is a general pattern.
Maybe @Johanne Mayer or @Ernie Bayha can confirm that this is intentional.
Regards,
Jan
------------------------------
Jan Lemmermann
OSS Lead Architect
EWE TEL GmbH
Original Message:
Sent: Mar 05, 2021 08:28
From: Jonathan Goldberg
Subject: [TMF653] Bug/Feature that ServiceTest.validFor is writeable
Service Test is led by @Johanne Mayer and @Ernie Bayha - they might be able to provide additional insights.
As a general rule, however, I would advocate having as few restrictions as possible in an API model, the obvious ones such as that href and id are not patchable.
The ability or not to update a specific field would be restricted using role-based access control.
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 05, 2021 01:53
From: Jan Lemmermann
Subject: [TMF653] Bug/Feature that ServiceTest.validFor is writeable
Hi Folks,
I noticed that within the current TMF653-ServiceTest-v4.0.0.swagger.json the ServiceTest.validFor attribute is writeable thru ServiceTest_Create.validFor and ServiceTest_Update.validFor.
The description states:
The validity time for the test results
Does that make sense? I would assume an API-Consumer should only read this attribute after the Service Test has been completed. Is this simply a minor error or is there a backstory to it?
Cheers,
Jan
------------------------------
Jan Lemmermann
OSS Lead Architect
EWE TEL GmbH
------------------------------