New Features 2017Project Type: software

New Features 2017

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

TSR Integration -> Check for BenAdmin Module Mapping and bypass APICall Flag

    Details

    • Type: Change Request
    • 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:
      Good To Have
    • Sprint:
      TSR OnBoard - 28 Mar - 12 May
    • Severity:
      Simple

      Description

      Check for BenAdmin Module Mapping and bypass APICall Flag
      Currently,when employee is added through API,plan allocation routines are not fired.

      Change the implementation to accommodate that if company has BenAdmin mapped,then routines will be executed.

      CC: Saurabh Sablaka

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          ramya.tantry Ramya Tantry (Inactive) added a comment -

          Files Affected:

          /App/BusinessLogic/Employee/EmployeeData.vb

          Show
          ramya.tantry Ramya Tantry (Inactive) added a comment - Files Affected: /App/BusinessLogic/Employee/EmployeeData.vb
          Hide
          Permalink
          ramya.tantry Ramya Tantry (Inactive) added a comment -

          Hi Prasad Pise,

          Please verify this enhancement.
          Scenario:
          If BenAdmin is mapped then ,plan allocation routines should get fired for employees added through API else not.

          Show
          ramya.tantry Ramya Tantry (Inactive) added a comment - Hi Prasad Pise , Please verify this enhancement. Scenario: If BenAdmin is mapped then ,plan allocation routines should get fired for employees added through API else not.
          Hide
          Permalink
          ramya.tantry Ramya Tantry (Inactive) added a comment - - edited

          Hi Kunal Kedari,

          As per our discussion,we will be reverting this enhancement as allowing plan allocation routines to get fired for employees added through API results in error in cases where age eligibility is added.
          This issue is because we are not passing DOB of EE added through API to the system.So while calculating age,it throws error.
          I have reverted my changes and checked in LB.Please verify normal flow of EE after patch deployment.

          CC: Prasad Pise,Saurabh Sablaka

          Show
          ramya.tantry Ramya Tantry (Inactive) added a comment - - edited Hi Kunal Kedari , As per our discussion,we will be reverting this enhancement as allowing plan allocation routines to get fired for employees added through API results in error in cases where age eligibility is added. This issue is because we are not passing DOB of EE added through API to the system.So while calculating age,it throws error. I have reverted my changes and checked in LB.Please verify normal flow of EE after patch deployment. CC: Prasad Pise , Saurabh Sablaka
          Hide
          Permalink
          kunal.kedari Kunal Kedari (Inactive) added a comment -

          Added QA estimations to original

          Show
          kunal.kedari Kunal Kedari (Inactive) added a comment - Added QA estimations to original
          Hide
          Permalink
          kunal.kedari Kunal Kedari (Inactive) added a comment -

          We are not implementing this change and roll back it from Local Environment. Closing the ticket.

          Cc: Saurabh Sablaka, Prasad Pise

          Show
          kunal.kedari Kunal Kedari (Inactive) added a comment - We are not implementing this change and roll back it from Local Environment. Closing the ticket. Cc: Saurabh Sablaka , Prasad Pise

            People

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

              Dates

              Created:
              Updated:
              Resolved:
              Code Review Date:

                Time Tracking

                Estimated:
                Original Estimate - 12h
                12h
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 8h 50m Time Not Required
                8h 50m