Details
-
Type:
Task
-
Status:
To Do
(View Workflow)
-
Priority:
Normal
-
Resolution: Unresolved
-
Labels:
-
Customer:Zain 2.X
-
Product:NEP
-
REQUESTER:INTERNAL
Description
Add a new REST API ProcessDecommissionedNodes
- the new API to be triggered by the integration on daily basis after XML import
- the API will have the following parameters:
- operation:ChangeStatus or Delete
- Threshold: number of days
- Status: the new NE status if the operation is ChangeStatus
- version: version name
- The API shall loop over all NEs, check the update date, if the delta between update date and current date is bigger than the threshold, either change NE status or delete the NE based on operation.
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
Patch has been deployed .
@diana as discussed we are getting error while triggering API. kindly check and suggest.
Dear @Basant,
As discussed via teams, i fixed the bug happening while executing this API and changes will be available in release: 3.7.1.615
However, Considering this API having the following url:
http://127.0.0.1:2919/NEP_SERVER/services/zain/decom/deleteRanNodesAndData?versionName=NAZ_TEST&operation=ChangeStatus&threshold=0&status=Closed&key=y@8j-bZHqp@teHvVB3-@w?K!R5M?YX
Pleas find the following:
VersionName: should be filled with the name of version where action must be proceeded (in the url shared it is one of the versions used)
Operation: can be either
Delete: delete all outdated nodes (based on threshold)
ChangeStatus: change status of outdated nodes to another status...
Threshold: Number of days
Status:
Can be one of NEP Statuses and should be filled as needed (desired status to be changed too)
Filled only when operation is "ChangeStatus"
Can be(based on the new needed status): Active,Planned,Closed,...
hello team,
mentioned patch has been deployed and API triggered succesfully.
Navneet Kaur this is not related to AI .. it is delivery
Hi Basant,
Thank you for the update.
Hi Ahad,
Please add these API in the internal test cases and confirm if they are fulfilling the intended purpose as mentioned below.
1. First API: to decommission the nodes that not coming in XML for a certain amount of time (2 weeks).
2. Second API: to move the asset to asset tracking table if serial number has been shifted to another site or node.
Regards,
Navneet.
From: Basant Kumar <Basant.Kumar@nuiva.com>
Sent: 03 December 2024 14:54
To: Navneet Kaur <Navneet.Kaur@mobinets.com>
Cc: Tarun Verma <Tarun.Verma@mobinets.com>; Bassem Sabbagh <bassem.sabbagh@mobinets.com>; Sanju Yadav <Sanju.Yadav@mobinets.com>
Subject: RE: APIs to be considered in 3.x
Dear Team,
We have successfully triggered both APIs provided by @Diana Hamdouche on the .14 server. Additionally, I would like to inform you that both APIs will be add to the cronjob on the .14 server.
If there is a requirement to trigger the APIs, please let us know, and we will execute them accordingly.
Regards,
Basant
WL: 3 days