WORKTERRAProject Type: software

WORKTERRA

Uploaded image for project: 'WORKTERRA'
  1. WORKTERRA
  2. WT-12252

Effective Date format issue for Employee Import

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: BenAdmin
    • Labels:
    • Environment:
      Others
    • Bug Type:
      Functional
    • Bug Severity:
      Medium
    • Module:
      BenAdmin - Import
    • Reported by:
      Others
    • Company:
      All Clients/Multiple Clients
    • Item State:
      Production Complete - Closed
    • Sprint:
      WT Sprint 41

      Description

      *Scenario - *
      1) On Template Settings set date format as 'YYYYMMDD'.
      2) Add Employee's effective date field in sub template and map it to 'Employee Effective Date'.
      3) Manual or Scheduled import gets failed.

      Cause -
      When system tries to convert date value string to date format, it throws an exception. Ex. ''20100101' string can not convert to Date'. Since, string value don't have any separator, CType function can not convert it to appropriate date format.

      Correction -
      Code change is needed

        Attachments

        1. ElectioneffectiveDate.txt
          0.4 kB
        2. EmpEffectiveDate.txt
          0.7 kB
        3. FinalUpdatedTestcases.xls
          28 kB
        4. FW 1211 Sprint - Development Approval.msg
          51 kB
        5. FW Hot Fix and Development Approval Request.msg
          60 kB
        6. RE Approvals.msg
          34 kB
        7. Testcases.xls
          26 kB
        8. UpdatedTestcases.xls
          28 kB
        9. WaiveDate.jpg
          WaiveDate.jpg
          195 kB
        10. WaiveDate.txt
          0.5 kB
        11. WT-12252 Data.xls
          19 kB

          Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. WT-12735 Fix Import File Failures

          • Medium - Has the potential to affect progress.
          • Closed
          is caused by

          Enhancement - An improvement or enhancement to an existing feature or task. WT-10805 User generation for failed Imports after Employee data is inserted - Implementation

          • Medium - Has the potential to affect progress.
          • Production Complete
          is duplicated by

          Support Activity - Support Activity WT-12449 CVHP - Import failure

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

          Bug - A problem which impairs or prevents the functions of the product. NF-5470 Effective Date format issue for Employee Import

          • Medium - Has the potential to affect progress.
          • Resolution Setting

            Activity

            Ascending order - Click to sort in descending order
            14 older comments
            Hide
            Permalink
            gaurav.sodani Gaurav Sodani (Inactive) added a comment -

            Hi All,

            Attaching the stage and production deployment approval email for reference: Unable to embed resource: FW Hot Fix and Development Approval Request.msg of type application/octet-stream

            Also, i have attached the email which states that we will be deploying only the Demographics import issue for now and will be taking up election import as part of Import module restructuring initiative

            Regards
            Gaurav

            Jayshree NagpureSuraj SokasaneJaideep VinchurkarSatyaSamirRakesh RoyJennifer ReedNagini IndugulaAbhay Patil

            Show
            gaurav.sodani Gaurav Sodani (Inactive) added a comment - Hi All, Attaching the stage and production deployment approval email for reference: Unable to embed resource: FW Hot Fix and Development Approval Request.msg of type application/octet-stream Also, i have attached the email which states that we will be deploying only the Demographics import issue for now and will be taking up election import as part of Import module restructuring initiative Regards Gaurav Jayshree Nagpure Suraj Sokasane Jaideep Vinchurkar Satya Samir Rakesh Roy Jennifer Reed Nagini Indugula Abhay Patil
            Hide
            Permalink
            jayshree.nagpure Jayshree Nagpure (Inactive) added a comment -

            Hi Suraj Sokasane,

            Verified on stage
            Company - ASML for hspl

            Verified only for demographics import
            PFA : FinalUpdatedTestcases.xls
            Verified for syn and async mode
            Verified with Initial load Yes/No
            Not considered any other import type.

            Working fine, Marking item state as Ready for production.

            Thanks,
            Jayshree

            cc : Rakesh Roy Prasad Pise Hrishikesh Deshpande Snehal Katkar

            Show
            jayshree.nagpure Jayshree Nagpure (Inactive) added a comment - Hi Suraj Sokasane , Verified on stage Company - ASML for hspl Verified only for demographics import PFA : FinalUpdatedTestcases.xls Verified for syn and async mode Verified with Initial load Yes/No Not considered any other import type. Working fine, Marking item state as Ready for production. Thanks, Jayshree cc : Rakesh Roy Prasad Pise Hrishikesh Deshpande Snehal Katkar
            Hide
            Permalink
            abhay.patil Abhay Patil (Inactive) added a comment -

            Question regarding comment by Suraj Sokasane - You have said the following.
            _... from election import point of view, it is failing for very specific scenario, where effective date given in file is less than hire date of employee and date format of template is YYYYMMDD.
            ... . We scanned all companies on production using YYYYMMDD date format for election import and found a very few are using it currently._

            I want to understand the following.

            • Will YYYYMMDD format always fail for election imports - or will it fail only under the specific scenario you mentioned?
            • When you say you found "a few companies using YYYYMMDD format for election import" - do you mean that those imports will fail? How many companies did you find?
              CC Cindy Wibbing Gaurav Sodani Jayshree Nagpure Jennifer Reed
            Show
            abhay.patil Abhay Patil (Inactive) added a comment - Question regarding comment by Suraj Sokasane - You have said the following. _... from election import point of view, it is failing for very specific scenario, where effective date given in file is less than hire date of employee and date format of template is YYYYMMDD. ... . We scanned all companies on production using YYYYMMDD date format for election import and found a very few are using it currently._ I want to understand the following. Will YYYYMMDD format always fail for election imports - or will it fail only under the specific scenario you mentioned? When you say you found "a few companies using YYYYMMDD format for election import" - do you mean that those imports will fail? How many companies did you find? CC Cindy Wibbing Gaurav Sodani Jayshree Nagpure Jennifer Reed
            Hide
            Permalink
            suraj.sokasane Suraj Sokasane (Inactive) added a comment - - edited

            Hi Abhay Patil,

            Below are the answers:

            • Will YYYYMMDD format always fail for election imports: No, election import won't fail always. It'll fail only in the specific scenario mentioned above.
            • When you say you found "a few companies using YYYYMMDD format for election import" - do you mean that those imports will fail? : Yes, but as per the first answer above, only for the specific scenario and not always.
            • How many companies did you find? : I'm attaching an excel sheet which contains data - Company name, Template name and number of imports on that template in 2017 till now. Here it is : WT-12252 Data.xls

            Hope this successfully answers your queries. Please let us know if you know more details on same.

            Show
            suraj.sokasane Suraj Sokasane (Inactive) added a comment - - edited Hi Abhay Patil , Below are the answers: Will YYYYMMDD format always fail for election imports : No, election import won't fail always. It'll fail only in the specific scenario mentioned above. When you say you found "a few companies using YYYYMMDD format for election import" - do you mean that those imports will fail? : Yes, but as per the first answer above, only for the specific scenario and not always. How many companies did you find? : I'm attaching an excel sheet which contains data - Company name, Template name and number of imports on that template in 2017 till now. Here it is : WT-12252 Data.xls Hope this successfully answers your queries. Please let us know if you know more details on same.
            Hide
            Permalink
            hrishikesh.deshpande Hrishikesh Deshpande (Inactive) added a comment -

            Hi All,

            This Fix is Deployed and Tested on Production. This is working as expected for all date formats.
            Closing this JIRA.

            Thanks,
            Hrishikesh.

            Show
            hrishikesh.deshpande Hrishikesh Deshpande (Inactive) added a comment - Hi All, This Fix is Deployed and Tested on Production. This is working as expected for all date formats. Closing this JIRA. Thanks, Hrishikesh.

              People

              Assignee:
              hrishikesh.deshpande Hrishikesh Deshpande (Inactive)
              Reporter:
              snehal.katkar Snehal Katkar (Inactive)
              Developer:
              Snehal Katkar (Inactive)
              QA:
              Jayshree Nagpure (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Dev Due Date:
                Pre-Prod Due Date:
                Production Due Date:
                Code Review Date:

                  Time Tracking

                  Estimated:
                  Original Estimate - 22h Original Estimate - 22h
                  22h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 60h
                  60h