New Features 2017Project Type: software

New Features 2017

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

TSR Integration->Add Employee->Employee get added successfully in DB, but not displaying in Search Employee list.

    Details

    • Type: Bug
    • 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

      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.
      7. Click on Send button.
      8. Employee get added and success message also get display.
      9. Search newly added employee using Search Employee page.

      Actual Result:
      Success message is displaying and employee get added in DB, but it is not listed in Search Employee page.

      Prasad Pise

        Attachments

          Issue Links

          relates to

          Enhancement - An improvement or enhancement to an existing feature or task. NF-180 TSR: API: Add Employee- generate & assign defaults

          • High - Serious problem that could block progress.
          • Closed

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            kunal.kedari Kunal Kedari (Inactive) added a comment - - edited

            This issue is related to configuration. The configuration done for Password security should consists of the parameter passed through API.

            As per dev comments in NF-508:
            *This issue is now fixed. Error was occurring due to company level customization for UserName generation policy. For candidates we accept only email, firstname & last name. So, username & password generation policies should be configured using these fields only.

            We need to consider these policies after deployment of enhancement to Stage and Production, setting should be made in advance to avoid the issue. *

            Show
            kunal.kedari Kunal Kedari (Inactive) added a comment - - edited This issue is related to configuration. The configuration done for Password security should consists of the parameter passed through API. As per dev comments in NF-508 : *This issue is now fixed. Error was occurring due to company level customization for UserName generation policy. For candidates we accept only email, firstname & last name. So, username & password generation policies should be configured using these fields only. We need to consider these policies after deployment of enhancement to Stage and Production, setting should be made in advance to avoid the issue. *
            Hide
            Permalink
            prasadp Prasad Pise (Inactive) added a comment -

            On Stage for "TSR Demo Company" Security Plolicy configuration is done using First Name, Last Name and Email.

            Working as expected on Stage with this configuration only.

            Show
            prasadp Prasad Pise (Inactive) added a comment - On Stage for "TSR Demo Company" Security Plolicy configuration is done using First Name, Last Name and Email. Working as expected on Stage with this configuration only.
            Hide
            Permalink
            kunal.kedari Kunal Kedari (Inactive) added a comment -

            This issue is related to configuration. The configuration done for Password security should consists of the parameter passed through API.

            As per dev comments in NF-508:
            *This issue is now fixed. Error was occurring due to company level customization for UserName generation policy. For candidates we accept only email, firstname & last name. So, username & password generation policies should be configured using these fields only.

            We need to consider these policies after deployment of enhancement to Stage and Production, setting should be made in advance to avoid the issue. *

            Show
            kunal.kedari Kunal Kedari (Inactive) added a comment - This issue is related to configuration. The configuration done for Password security should consists of the parameter passed through API. As per dev comments in NF-508 : *This issue is now fixed. Error was occurring due to company level customization for UserName generation policy. For candidates we accept only email, firstname & last name. So, username & password generation policies should be configured using these fields only. We need to consider these policies after deployment of enhancement to Stage and Production, setting should be made in advance to avoid 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:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: