...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
District Mapping (SC-1373)
Jira ID -
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
User location-DeviceLocation Telemetry -
Will be triggered when the user clicks submits his location.
{
"edata": {
"type": "CLICK",
"subtype": "device-profile-user-declared",
"id": "user-state-districtConfimation",
"pageid": "profile",
}
}
Possible values of fields -
...
"device-profile-user-declared" - the suggestion is based on the device profile and the user has not changed suggested location.
"device-profile-user-declared-updated" - the suggestion is based on the device profile and the user has changed location.
"device-profile-ip-location" - the suggestion is based on the IP location and the user has not changed the suggested location.
"device-profile-ip-location-updated" - the suggestion is based on the IP location and the user has changed location.
"user-profile" - the suggestion is based on the user location and the user has not changed the suggested location.
"user-profile-updated" - the suggestion is based on the user location and the user has changed the suggested location.
2. pageid - which route the popup is loaded.
example - "profile"
Impression Event -
Will be trigged when location popup is flashing up on the screen.
{
context: {
env: 'user-location',
cdata: [{id: 'user:state:districtConfimation', type: 'Feature'},
{id: 'SC-1373', type: 'Task'}
]
},
edata: {
type: 'view',
pageid: "profile",
uri: "/profile", // route from which popup is visible to user.
}
};Telemetry log event -
Will be triggered for API calls to update device or user location. For error and success, both cases these telemetries should be generated.
{
"edata": {
"type": "update-location", // Required. Type of log (system, process, api_access, api_call, j
"level": "ERROR", // Required. Level of the log. TRACE, DEBUG, INFO, WARN, ERROR, FA
"message": "Updation of device profile failed", // Required. Log message
"pageid": "profile", // Optional. Page where the log event has happened
}
}Possible values of fields -
...
- "Updation of device profile failed"
- "Updation of device profile success"
- "Updation of user profile success"
- "Updation of user profile failed"
3. pageid - which route the popup is loaded.
example - "profile"
Teacher-ID Verification (SC-1349)
Impression Event when the popup is visible