Details

    • Type: Story Story
    • Status: Ready for Signoff
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 0.1
    • Fix Version/s: 0.1
    • Component/s: PGR, Rework
    • Labels:
      None
    • Story Points:
      3

      Description

      • Update json contracts across the system to have field in "camelCase" format
      • Update YAML file documentation to use camelCase format
      • Use implicit deserialization / serialization wherever possible using Jackson
      • Use Lombok to get rid of getters and setters.
      • Have jurisdiction Id present in all request info objects (aka tenant id)

      The expected structure for SevaRequest should be as follows:

      SevaRequest
      {
        "ResposneInfo": {
          "apiId": "string",
          "ver": "string",
          "ts": "string",
          "resMsgId": "string",
          "msgId": "string",
          "status": "string",
          "userId": "Long" //Populated by REST layer for everyone downstream for logged in user.
          "userType": "string", //Possible values are EMPLOYEE, CITIZEN and SYSTEM
          "accessToken": "string",
          "correlationId": "string" //Id injected at REST layer to trace request & spawning calls across system. Should be used while logging messages
        },
        "Seva": [
          {
            "serviceRequestId": "string",
            "status": Boolean,
            "statusNotes": "string",
            "serviceName": "string",
            "serviceCode": "string",
            "description": "string",
            "agencyResponsible": "string",
            "serviceNotice": "string",
            "requestedDatetime": "string",
            "updatedDatetime": "string",
            "expectedDatetime": "string",
            "address": "string",
            "addressId": "string",
            "zipcode": 0,
            "lat": 0,
            "lng": 0,
            "mediaUrl": "string",
            "firstName": "string",
            "lastName": "string",
            "phone": "string",
            "email": "string",
            "deviceId": "string",
            "accountId": "string",
            "values": [
              {
                //below is a list of possible keys and description of what they represent within Seva Request
                "locationId":"string", //location id based on cross hierarchy id or lat/lng
                "childLocationId":"string", //child location id based on cross hierarchy id
                "locationName":"string", //name of the location
                "assignmentId":"string", //Id of the assignee
                "stateId":"string", //workflow id
                "receivingMode":"", //Originating channel for the request. Mobile, Desktop etc..
                "userId":"string", //user id of the complainant. This can be different than logged in user
                "receivingCenter":"string", //specify receiving-center when officials/employees register complaint on behalf of citizens
                "complainantAddress":"string", //address of complainant in case of anonymous user
                "startRating":"integer", //rating given by citizens
                "complaintStatus":"string", //status of the complaint
                "escalationHours": "string", //Escalation number of hours for the complaint that will be used by indexing.
                "complainantAddress": "string", //address of the complainant
                "status":"string"//Possible values are COMPLETED, FORWARDED, REJECTED, REGISTERED, WITHDRAWN, REOPENED, PROCESSING;
              }
            ]
          }
        ]
      }
      

        Expenses

          Activity

          Hide
          Sumanth K P (Inactive) added a comment -

          We should also decide on values key for the kafka contract.

          Show
          Sumanth K P (Inactive) added a comment - We should also decide on values key for the kafka contract.
          Hide
          Priyank Gupta (Inactive) added a comment - - edited

          Tasks

          • Add missing Contract tests.
          • Includes UI changes. (PGR Rest, File Store and User service)
          Show
          Priyank Gupta (Inactive) added a comment - - edited Tasks Add missing Contract tests. Includes UI changes. (PGR Rest, File Store and User service)

            People

            • Assignee:
              Malathi R
              Reporter:
              Priyank Gupta (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:

                Agile

                  Potential Duplicates