sayaliparab
|
be008a5ea9
|
alarmAlert
|
2025-04-01 12:31:47 +05:30 |
|
sayaliparab
|
6f5131f5b9
|
alarmAlert
|
2025-04-01 12:14:03 +05:30 |
|
kshitige
|
e01728c38d
|
changes in alarm changes in telemetry data device
|
2025-03-31 19:18:36 +05:30 |
|
kshitige
|
2bcfaa1eca
|
no conflicts
|
2025-03-28 19:42:25 +05:30 |
|
kshitige
|
2051212afa
|
CustomerInfoalertCount
|
2025-03-28 19:40:39 +05:30 |
|
sayliraut
|
fbf31e976c
|
conflict solve
|
2025-03-28 13:52:02 +05:30 |
|
sayliraut
|
3dbef32bbe
|
modify code
|
2025-03-28 13:35:40 +05:30 |
|
kshitige
|
e6affd36e9
|
changes in delete and users
|
2025-03-27 18:54:06 +05:30 |
|
sayaliparab
|
d5055fa42e
|
telementary conflcit resloved
|
2025-03-27 11:47:53 +05:30 |
|
sayaliparab
|
e5f60bc0a8
|
sneha DOne
|
2025-03-27 11:43:12 +05:30 |
|
sayliraut
|
70ab842358
|
pass starTs and EndTs
|
2025-03-26 17:36:30 +05:30 |
|
sayliraut
|
5d1121d2f3
|
conflict solve
|
2025-03-26 16:54:51 +05:30 |
|
sayliraut
|
befe84d338
|
changes in route method
|
2025-03-26 16:53:02 +05:30 |
|
sayaliparab
|
fee5bb4e8a
|
conflicts solved routes
|
2025-03-26 12:21:22 +05:30 |
|
sayaliparab
|
f741450bec
|
telemetry data device validation
|
2025-03-26 12:18:45 +05:30 |
|
sayliraut
|
c37eec7b19
|
conflict solve route method change for telementry data
|
2025-03-26 12:04:23 +05:30 |
|
sayliraut
|
0d7103ebbe
|
device user list based on customer, login, create alarm
|
2025-03-26 11:37:58 +05:30 |
|
sayaliparab
|
6cdc2552c7
|
telemetry diagnostic and device
|
2025-03-26 11:21:24 +05:30 |
|
sayaliparab
|
93953de7d3
|
userAssetlink
|
2025-03-25 12:19:43 +05:30 |
|
kshitige
|
cef3df82cf
|
TelemetryData
|
2025-03-25 11:34:55 +05:30 |
|
kshitige
|
575d23884f
|
UserAssetLinkLatest
|
2025-03-24 13:31:06 +05:30 |
|