Page Comparison

District Mapping (SC-1373)

Jira ID - 

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 -

1.subtype

• "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.

...

District Mapping (SC-1373)

Jira ID - 

User location-DeviceLocation Telemetry - 

Will be triggered when the user clicks submits his location.

{

  "edata": {
    "type": "location-changed/location-unchanged",
    "subtype": "state_dist_changed/state_changed/dist_changed", 
    "id": "submit-clicked", 
    "pageid": "location-popup",
  }
}

Possible values of fields -

1.type

• "location-changed" - if location is changed.

• "location-unchanged" - if location is un changed.

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: "profilelocation-popup",
    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": "profilelocation-popup", // Optional. Page where the log event has happened
  }
}

Possible values of fields -

...

• "ERROR" :   When api fails.

• "SUCCESS" : When API is success.

...

• .

...

• "Updation of device profile failed"  
• "Updation of device profile success"
• "Updation of user profile success"
• "Updation of user profile failed"

...

Teacher-ID Verification (SC-1349)

...