-
Type:
Improvement
-
Status: Closed
-
Priority:
Medium
-
Resolution: Bug Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:
-
Company:All Clients/Multiple Clients
-
Categories:Import
From Van Nguyen
Hello team,
BioRad is the 2nd client that have requested that we process the import files with encoding type UTF-8. MRTX was the 1st one that requested this in November.
Company Template Name: _Employee Data New Hires
File date: 3/16/2018
Filename: EmployeeCensus.txt
Employee: Marcella Gordon
Incorrect Address imported into Workterra: 12 O’Neil Ct.
Correct Address that should've been imported into Workterra: 12 O'Neil Ct.
When I manually opened the file using the TextPad application, I saw the address with the invalid special characters. 12 O’Neil Ct.
When I manually opened the file using the NotePad application, I saw the address without the invalid special characters, 12 O'Neil Ct.
I've requested for the client to temporarily remove the special characters for now, but they refuse to do that. They want us to be able to process the import files using encoding type UTF-8.
Note from Bio-Rad's IT department:
From: Balakrishna Reddy <balakrishna_reddy@bio-rad.com>
Date: Mon, Mar 19, 2018 at 12:10 PM
Subject: Re: FW: Bio-Rad - MHN - failure - special character in address
To: Julie Bates <julie_bates@bio-rad.com>
Cc: Maricel Chesney Edpao <maricel_chesney-edpao@bio-rad.com>, Maria Fonseca <maria_fonseca@bio-rad.com>
Hi Julie
I am not sure how WorkTerra opened the file and which tool they are using to open the file from fTP server.
Workterra needs to open the file in a tool which supports UTF-8 format.. If not, you will see the data as shown below. We use Notepad++
Also we don't have any insights on how workterra program is designed to read the data from FTP server side. We had the same issue from another vendor and they have changed their Decryption logic to read the file as UTF -8 and it resolved their issue
| Field | Original Value | New Value |
|---|---|---|
| Link | This issue relates to WB-693 [ WB-693 ] |
| Description |
From [Van Nguyen|https://jira.workterra.net/secure/ViewProfile.jspa?name=Van.Nguyen] Hello team, BioRad is the 2nd client that have requested that we process the import files with encoding type UTF-8. MRTX was the 1st one that requested this in November. Company Template Name: _Employee Data New Hires File date: 3/16/2018 Filename: EmployeeCensus.txt Employee: *Marcella Gordon* Incorrect Address imported into Workterra: *12 O*{color:#d04437}’{color}*Neil Ct.* Correct Address that should've been imported into Workterra: *12 O'Neil Ct.* When I manually opened the file using the *TextPad* application, I saw the address with the invalid special characters. *12 O*{color:#d04437}’{color}*Neil Ct.* When I manually opened the file using the *NotePad* application, I saw the address without the invalid special characters, *12 O'Neil Ct.* I've requested for the client to temporarily remove the special characters for now, but they refuse to do that. They want us to be able to process the import files using encoding type UTF-8. +Note from Bio-Rad's IT department:+ From: Balakrishna Reddy <balakrishna_reddy@bio-rad.com> Date: Mon, Mar 19, 2018 at 12:10 PM Subject: Re: FW: Bio-Rad - MHN - failure - special character in address To: Julie Bates <julie_bates@bio-rad.com> Cc: Maricel Chesney Edpao <maricel_chesney-edpao@bio-rad.com>, Maria Fonseca <maria_fonseca@bio-rad.com> Hi Julie I am not sure how WorkTerra opened the file and which tool they are using to open the file from fTP server. Workterra needs to open the file in a tool which supports UTF-8 format.. If not, you will see the data as shown below. We use Notepad++ Also we don't have any insights on how workterra program is designed to read the data from FTP server side. We had the same issue from another vendor and they have changed their Decryption logic to read the file as UTF -8 and it resolved their issue |
From [Van Nguyen|https://jira.workterra.net/secure/ViewProfile.jspa?name=Van.Nguyen] Hello team, BioRad is the 2nd client that have requested that we process the import files with encoding type UTF-8. MRTX was the 1st one that requested this in November. Company Template Name: _Employee Data New Hires File date: 3/16/2018 Filename: EmployeeCensus.txt Employee: *Marcella Gordon* Incorrect Address imported into Workterra: *12 O*{color:#d04437}’{color}*Neil Ct.* Correct Address that should've been imported into Workterra: *12 O'Neil Ct.* When I manually opened the file using the *TextPad* application, I saw the address with the invalid special characters. *12 O*{color:#d04437}’{color}*Neil Ct.* When I manually opened the file using the *NotePad* application, I saw the address without the invalid special characters, *12 O'Neil Ct.* I've requested for the client to temporarily remove the special characters for now, but they refuse to do that. They want us to be able to process the import files using encoding type UTF-8. +Note from Bio-Rad's IT department:+ From: Balakrishna Reddy <balakrishna_reddy@bio-rad.com> Date: Mon, Mar 19, 2018 at 12:10 PM Subject: Re: FW: Bio-Rad - MHN - failure - special character in address To: Julie Bates <julie_bates@bio-rad.com> Cc: Maricel Chesney Edpao <maricel_chesney-edpao@bio-rad.com>, Maria Fonseca <maria_fonseca@bio-rad.com> Hi Julie I am not sure how WorkTerra opened the file and which tool they are using to open the file from fTP server. Workterra needs to open the file in a tool which supports UTF-8 format.. If not, you will see the data as shown below. We use Notepad++ Also we don't have any insights on how workterra program is designed to read the data from FTP server side. We had the same issue from another vendor and they have changed their Decryption logic to read the file as UTF -8 and it resolved their issue [~satyap],[~Vinayak.Kulkarni],[~Prashant.samal] |
| QA | Sanjana Jadhav [ sanjana.jadhav ] | |
| QA Estimates | 16 |
-
- Time Spent:
- 1.7h
-
Analysis
Internal discussion
Test cases writing
| Remaining Estimate | 0h [ 0 ] | |
| Time Spent | 1.7h [ 6120 ] | |
| Worklog Id | 111588 [ 111588 ] |
| Status | To Do [ 10000 ] | Open [ 1 ] |
| Workflow | WD: Project Management Workflow [ 67780 ] | 0604 Issues Management Workflow [ 68446 ] |
| Attachment | WT_Sprint-46_Wd_140_Sanjanajadhav.xls [ 75972 ] |
| Attachment | Analysis - WD_130.doc [ 76038 ] |
| Attachment | Analysis - WD_130.doc [ 76038 ] |
| Attachment | Analysis - WD_140.doc [ 76039 ] |
Attached the analysis document : Analysis - WD_140.doc
| Status | Open [ 1 ] | In Analysis [ 10008 ] |
| Status | In Analysis [ 10008 ] | In Development [ 10007 ] |
| Categories | Parent values: Import(18506) | |
| Code Review Date | 13/Apr/2018 | |
| Code Reviewed By | Ganesh Sadawarte ,Vinalyak Kulkarni [ 12101, 12100 ] | |
| Original Estimate | 0h [ 0 ] |
Khandu Kshirsagar (Inactive)
made changes -
| Assignee | Suraj Sokasane [ suraj.sokasane ] | Hrishikesh Deshpande [ hrishikesh.deshpande ] |
| Status | In Development [ 10007 ] | LB Deployed [ 11600 ] |
Sachin Hingole (Inactive)
made changes -
| Assignee | Hrishikesh Deshpande [ hrishikesh.deshpande ] | Sanjana Jadhav [ sanjana.jadhav ] |
-
- Time Spent:
- 4h
-
Coding, Unit testing, Code review, LB check in
| Time Spent | 1.7h [ 6120 ] | 5.7h [ 20520 ] |
| Worklog Id | 112278 [ 112278 ] |
| Status | LB Deployed [ 11600 ] | In LB Testing [ 10200 ] |
| Attachment | WD-140.png [ 76431 ] |
Verified on LB.
For some UTF-8 character (such as Ɏ,ʂ, ɱ,ʘ) file imported successfully but ?? shown on UI instead of UTF-8 character .
PFA,
Thanks,
Sanjana Jadhav
CC: Prasad Pise Sachin Hingole Rakesh Roy Hrishikesh Deshpande
| Assignee | Sanjana Jadhav [ sanjana.jadhav ] | Satya [ ID10004 ] |
| Assignee | Satya [ ID10004 ] | Sanjana Jadhav [ sanjana.jadhav ] |
| Attachment | AffectedFiles.txt [ 76433 ] |
Hi Sanjana Jadhav,
Those are characters from other languages. For example, Ɏ is used in Lubuagan Kalinga language. As part of this enhancement, we supported the English UTF-8 char set.
Verified on LB for English UTF-8 char set.
Verified test cases attached.Works properly.
Ready for Pre production.
Thanks,
Sanjana Jadhav
CC: Prasad Pise Sachin Hingole Rakesh Roy Hrishikesh Deshpande
| Status | In LB Testing [ 10200 ] | Ready for Pre-Prod [ 11615 ] |
| Time Spent | 5.7h [ 20520 ] | 8.7h [ 31320 ] |
| Worklog Id | 112786 [ 112786 ] |
Khandu Kshirsagar (Inactive)
made changes -
| Status | Ready for Pre-Prod [ 11615 ] | Pre-Prod Deployed [ 11601 ] |
| Status | Pre-Prod Deployed [ 11601 ] | IN Pre-prod Testing [ 11500 ] |
-
- Time Spent:
- 2h
-
Testing
Execution on testlink
Verified on Pre production for English UTF-8 char set.
Verified test cases attached.Works properly.
Ready for Production.
Thanks,
Sanjana Jadhav
| Time Spent | 8.7h [ 31320 ] | 10.7h [ 38520 ] |
| Worklog Id | 112832 [ 112832 ] |
| Status | IN Pre-prod Testing [ 11500 ] | Ready for Production [ 10024 ] |
Khandu Kshirsagar (Inactive)
made changes -
| Status | Ready for Production [ 10024 ] | Production Deployed [ 10025 ] |
| Status | Production Deployed [ 10025 ] | In Production Testing [ 10202 ] |
Verified on production.
Company: COSB For HSPL
Verified all attached test cases. Working as expected.
Hence closing this issue.
Thanks,
Sanjana Jadhav
-
- Time Spent:
- 2h
-
Pre production testing
Jira update
Update in test link
| Time Spent | 10.7h [ 38520 ] | 12.7h [ 45720 ] |
| Worklog Id | 113227 [ 113227 ] |
| Resolution | Bug Fixed [ 10402 ] | |
| Status | In Production Testing [ 10202 ] | In Production Review [ 11501 ] |
| Status | In Production Review [ 11501 ] | Closed [ 6 ] |
| Link | This issue relates to WB-235 [ WB-235 ] |
| Transition | Time In Source Status | Execution Times |
|---|
|
7d 5h | 1 |
|
6d 19h 29m | 1 |
|
8s | 1 |
Khandu Kshirsagar (Inactive)
made transition
-
|
4h 13m | 1 |
|
3d 21h 46m | 1 |
|
18h 55m | 1 |
Khandu Kshirsagar (Inactive)
made transition
-
|
3h 42m | 1 |
|
1h 54m | 1 |
|
1h 59m | 1 |
Khandu Kshirsagar (Inactive)
made transition
-
|
4d 17h 50m | 1 |
|
1h 11m | 1 |
|
20m 33s | 1 |
|
13s | 1 |
Hi,
Please refer attached test cases:
WT_Sprint-46_Wd_140_Sanjanajadhav.xls
Thanks,
Sanjana Jadhav
CC: Prasad Pise Rakesh Roy Sachin Hingole