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

TSR Integration->Field Validations->Can we make API field validations in sync with application.

    XMLWordPrintable

    Details

    • Type: Change Request
    • Status: Closed
    • Priority: High
    • 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
    • Sprint:
      TSR OnBoard - 28 Mar - 12 May
    • Severity:
      Medium
    • Code Reviewed By:
      Ramya Tantry

      Description

      At present the API field validations are not in sync with application.

      e.g. Postal code is not validated against country in API, but in application we are validating it against the mentioned country, in such scenarios when employee is added through API such fields are showing validation error on respective pages and employee needs to correct these fields.

      Above is just an example, there are many more fields. We have listed some of the validations inconsistencies in Jira NF-673.

      It will be better if we sync the validations for API fields with application, to avoid any future issue due to validations.

      Cc: Prasad Pise

        Attachments

        1. API_FieldValidationsChanges.xls
          10 kB
          Seema Gaikwad
        2. FieldInApi.xls
          7 kB
          Seema Gaikwad
        3. FieldValidationRegex_comparison.ods
          13 kB
          Seema Gaikwad

          Activity

            People

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

              Dates

              Created:
              Updated:
              Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 24h
                24h
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 18.5h Time Not Required
                18.5h