Uploaded image for project: 'New Features 2017'
  1. New Features 2017
  2. NF-600

TSR Integration->Add Employee->Issues related to Country and States.

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Integrations
    • Labels:
      None
    • Module:
      TSR
    • Reported by:
      Harbinger
    • Item State:
      Production Complete - Closed
    • Issue Importance:
      Q1

      Description

      1. Launch the Postman app.
      2. Select “Post” request from dropdwon.
      3. Select authorization type as “Basic Auth”.
      4. Enter valid User ID and Password.
      5. Enter below URL:
      http://10.0.2.120/api/employee/addEmployeeTour
      6. Pass the require parameter using body.

      *Scenario 1] *
      API input is not accepting any special characters in State. (e.g. enter state as Uttar Pradesh, Taegu-Jikhalsi ) showing below validation message:
      "Parameter state can contain alphabets only"

      Scenario 2]
      It seems that when entered state value exceed beyond certain characters, then in DB StateID is get stored as 0 (e.g. select country India and State as Maharashtra, Chhattisgarh)

      Scenario 3]
      Can we re frame below description:
      {
      "status": "Error",
      "message": "Invalid Input",
      "errorLevel": "Error",
      "code": 403,
      "description": "Entered Address Either Country or State is not valid"
      }

      It should be - "Entered Country or State is not valid"

      Cc: Saurabh Sablaka, Prasad Pise

        Attachments

          Issue Links

            Activity

            Hide
            rupesh.mandal Rupesh Mandal (Inactive) added a comment -

            Given all Scenario has been resolved we can take special characters in state like -,( etc
            error message also changed and
            state value allows maximum of 50 characters only

            Show
            rupesh.mandal Rupesh Mandal (Inactive) added a comment - Given all Scenario has been resolved we can take special characters in state like -,( etc error message also changed and state value allows maximum of 50 characters only
            Hide
            kunal.kedari Kunal Kedari (Inactive) added a comment -

            Hi Rupesh Mandal,

            We have verified the fix on Local (wt-stage), however scenario 2] is still not fixed on Local, hence reopening.

            Cc: Prasad Pise, Saurabh Sablaka

            Show
            kunal.kedari Kunal Kedari (Inactive) added a comment - Hi Rupesh Mandal , We have verified the fix on Local (wt-stage), however scenario 2] is still not fixed on Local, hence reopening. Cc: Prasad Pise , Saurabh Sablaka
            Hide
            rupesh.mandal Rupesh Mandal (Inactive) added a comment -

            scenario 2 is solved now stateID is successfully saved for maximum of 50 characters

            Show
            rupesh.mandal Rupesh Mandal (Inactive) added a comment - scenario 2 is solved now stateID is successfully saved for maximum of 50 characters
            Hide
            kunal.kedari Kunal Kedari (Inactive) added a comment -

            Fix is verified on Local (wt-stage), now scenario 2] is working as expected.

            Show
            kunal.kedari Kunal Kedari (Inactive) added a comment - Fix is verified on Local (wt-stage), now scenario 2] is working as expected.
            Hide
            prasadp Prasad Pise (Inactive) added a comment -

            Fix is verified on STAGE, All scenario working as expected.

            Show
            prasadp Prasad Pise (Inactive) added a comment - Fix is verified on STAGE, All scenario working as expected.
            Hide
            kunal.kedari Kunal Kedari (Inactive) added a comment -

            Verified fix on Production environment, working as expected. Closing the issue.

            Show
            kunal.kedari Kunal Kedari (Inactive) added a comment - Verified fix on Production environment, working as expected. Closing the issue.

              People

              Assignee:
              kunal.kedari Kunal Kedari (Inactive)
              Reporter:
              kunal.kedari Kunal Kedari (Inactive)
              QA:
              Kunal Kedari (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Code Review Date: