POL00029902
POL00029902
Peak Incident Management System
Call Reference PC0246997 Call Logger Deleted User -- EDSC
Release Targeted At -- HNG-X 12.88 Top Ref CTR_APP_X1288 V646
Call Type Cloned call Priority B -- Progress stopped
Contact Deleted Contact Call Status Closed -- S/W Fix Available to Call Logger
Target Date 17/10/2015 Effort (Man Days) 0
Summary 2248433 - horizon - transaction discrepancies
All References Type Value
SSCKEL KEL acha621P
Release PEAK PC0248024
Product Baseline CTR_APP_X1288_V646
DeviIntRel-Director Live Supp.Test
DevintRel-Director Live Supp.Test
Clone Master PC0246949
TRIOLE for Service A10504260
Collections Name User Date
BIFApproved Lorraine Elliott 02-Nov-2015 08:06:36
Impact :
Si ees : User Date
Unknown 15-Oct-2015 13:13:33
Branch has a discrepancy of £24000. 4 other branches have had a similar problem in the last 2 months. 3 of
these resolved by remming out the excess. Since these were all branch-to-branch rems and there is no cross-
branch accounting within Horizon, this removes the discrepancy.
Progress Narrative
bate:14-Oct-2015 15:23:24 User:Anne Chambers
CALL Pc0246997 opened
Details entered are:~
summary:2248433 - horizon - transaction discrepancies
call Type:
call Priority:¢
Target Release: HNG-X 12.11
touted to:EDSC - Anne Chambers
jbate:13-Oct-2015 14:46:37 User: Customer Call_
CALL PC0246949 opened
Details entered are:
48433 - horizon - transaction discrepancies
ffarget Release:HNG-X 12.11
Routed to:EDSC - _Unassigned_
HINCIDENT Mi
bate/Time Raised:
priority: ¢
contact Name: PostOftice. Unknown
[contact Phon GRO
riginator: XX)
riginator's r
Product Serial No:
product
Oct 12 2015 5:10PM
G¥:17991774
te: 224843
transfer Note: ****Please can PEAK investigate this discrepancy issue. NBSC has confirmed that following discussions and checks
With the user that this is not a user error issue, but an issue within the system requiring Fujitsu investigation.****:
Received the following email:
Hi Eden,
jeed to raise an incident for below issue éamp; provide Fujitsu re.. It?s been confirmed with SM.
(previous ref: 17972295)
jote: NBSC has confirmed that they following discussions and checks with the user that this is not a user error issue, but an
issue within the system requiring Fujitsu investigation
POL00029902
POL00029902
FNane: Anne Ireland
IPhone #: 01292 550 321
[caller type: Dalmellington Outreach Service
LFAD code (for branch) / PATH code (for supplier
Problem/Request:
Fuser has discrepancies when transferring cash from one branch to another (specifically between their main branch to their
outreach branch); OUTREACH BRANCH ISSUE
Fuser said instead of the system logging it as 8000 pound transaction, it recognizes it as a 32,000 pound transaction
user already contacted NBSC and was right away directed to us, POSD; reference# 1358666
IFAD code *2248433
lode id #gellar kit
User id *ATROO1
pate / Time of transaction 8th October 2015 @ 1300
session ID *1-12440-1 I 1-12441-1 I 1-12442-1 I 1-1243-1
{transaction number(s) * none
Jamounts *8000 pounds over 32000 pounds
First 6 and last 4 digits of card number (if applicable) *n/a
current TP / BP / Stock unit *TP - 6, BP - n/a, Stock Unit - AA
Key strokes *Back Officesgt; Remittances and Transferssgt; Deliveryagt; Scan your barcodeagt; type in the amountagt; confirm the
jamountégt; Enter
2248433
Regards,
IAbhishek Rane
lHinjewadi, Phase-2, Pune-411057
tos India
Femail attached and forwarded to Fujitsu
access attached
POL-SD-Horizon-Minimum Dataset for Software Calls
incident History:
2015-10-12 17:10:56 [ POA-HDI]
INIT : Create a new request/incident/problem/change/issue
2015-10-12 17:10:57 [ POA-HDI}
neut_en_poa : Transfer Notification
2015-10-12 17
zneun_en_poa
10:57 [ POA-HDI}
: Open Notification
2015-10-12 17:12:58 [ POA-HDI]
I’DIoutaDD : From ATOSSDM12: ~
lemail from Rane
2015-10-12 17:14:29 [ POA-HDI]
I2DIoutADD : From ATOSSDMI2: -
email from Katie
2015-10-12 17:15:00 [I POA-HDI}
l’DToutaDD : From ATOSSDM12: 2015/10/12 17:13:39 GMT Log Comment -received the following:
\Thank you Abhishek.
lkden ? grateful if this one can be raised today. Please let myself and Abhishek know immediately if Fujitsu reject this call.
thanks,
atie
email attached
“Attachement 2248433 Dalmellington Outreach Service - horizon transaction discrepancies .msg
Attachement RE 2248433 Dalmellington Outreach Service - horizon transaction discrepancies .msg ——
2015-10-12 17:15:31 [ POA-HDT]
JtDToutADD : From ATOSSDM12: 2015/10/12 17:14:41 GMT Status Status changed to -
Received the following emai
H Eden,
Need to raise an incident for below issue & provide Fujitsu re.. It?s been confirmed with SM.
(previous ref: 17972295)
jote: NBSC has confirmed that they following discussions and checks with the user that this is not a user error issue, but an
issue within the system requiring Fujitsu investigation
Name: Anne Ireland
[Phone #:
Caller typé? Dalmellington Outreach Service
FAD code (for branch) / PATH code (for supplier): 2248433
Problem/Request:
Fuser has discrepancies when transferring cash from one branch to another (specifically between their main branch to their
joutreach branch); OUTREACH BRANCH ISSUE
user said instead of the system logging it as 8000 pound transaction, it recognizes it as a 32,000 pound transaction
user already contacted NBSC and was right away directed to us, POSD; reference# 1358666
IFAD code #2248433
pate / Time of transaction ‘today @ 1300
session ID *1-12440-1 I 1-12441-1 I 1-12442-1 I 1-1243-1
\'ransaction number(s) * none
JAmounts “8000 pounds over 32000 pounds
jrirst 6 and last 4 digits of card number (if applicable) *n/a
urrent TP / BP / Stock unit *TP - 6, BP - n/a, Stock Unit - AA
ey strokes *Back Office> Remittances and Transfers> Delivery> Scan your barcode> type in the amount> confirm the amount> Enter
Regards,
labhishek Rane
POL00029902
POL00029902
fmeident, Management
Pi
jabhishek.rand-
limbasay Tech one,
IHinjewadi, Phase-2, Pune-411057
jAtos India
email attached and forwarded to Fujitsu
J-access attached
lboL-SD-Horizon-Minimum Dataset for Software Calls
\****START* ** *MONO0900TUEO 900WEDO 900THUO 900FRI0900SATO900SUNOG00BNKO000
(N0000TUEO0OWEDO9OOTHUOOOOFRI0000SAT0000SUN0000BNK0000
(N00 0TUE0000WEDO0OOTHUOOOOFRI0000SAT0000SUN0000BNK0000
(ONL 730TUEI 730WED1730THU1730FRI1730SAT1230SUNO000BNK0000**+**END****
2015-10-12 17:16:01 [ POA-HDI]
J]HDIoutADD : From ATOSSDM12: 2015/10/12 17:15:10 GMT Status Status changed to —
IReceived the following email:
Iki Eden,
eed to raise an incident for below issue & provide Fujitsu re.. It?s been confirmed with SM.
(previous ref: 17972295)
Note: NBSC has confirmed that they following discussions and checks with the user that this is not a user error issue, but an
issue within the system requiring Fujitsu investigation
J-Name: Anne Ireland
I-Phone #:
caller typé: Dalméiiington Outreach Service
I-FAD code (for branch) / PATH code (for supplier): 2248433
Iproblem/Reques'
Fuser has discrepancies when transferring
joutreach branch); OUTREACH BRANCH ISSUE
l-user said instead of the system logging it as 8000 pound transaction, it recognizes it as a 32,000 pound transaction
l-user already contacted NBSC and was right away directed to us, POSD; reference# 1358666
FAD code *2248433
jode id *gellar kit
User id f
[Date / Time of transaction *today @ 1300
Session ID *1-12440-1 I 1-12441-1 I 1-12442-1 { 1-1243-1
Transaction number(s) * none
lamounts *8000 pounds over 32000 pounds
[First 6 and last 4 digits of card number (if applicable) *n/a
[current TP / BP / Stock unit *TP - 6, BP - n/a, Stock Unit - AA
key strokes “Back Office> Remittances and Transfers> Delivery> Scan your barcode> type in the amount> confirm the amount> Enter
cash from one branch to another (specifically between their main branch to their
Regards,
lAbhishek Rane
liinjowadi, Phase-2, Pune-411057
lAtos India
email attached and forwarded to Fujitsu
access attached
lPOL-SD-Horizon-Minimum Dataset for Software Calls
I****START* ***MONO900TUEO 900WEDO900THUO 900FRI0900SATO900SUNO000BNK0000
(ON0000TUE0000WEDO000THUOOOOFRI0000SATOO00SUNO000BNK0000
(ON0000TUE0000WEDO000THUOOOOFRIO000SATOOOOSUND000BNKO000
(ON1730TUE1 730WED1730THU1730FR11730SAT1230SUN0000BNK0000****END****
2015-10-12 17:27:00 [ Millman, Emma }
lsDIoutsTU : Hi
sall notes it states the Date & Time of the
in regards to the above call, in the
lissue as ‘today @ 1300.’ I think you will find this is incorrect as the issue was originally raised on 8th October.
Please provide us with the correct date so we can investigate this.
Regards
[emma Millman
2015-10-12 17:45:11 [ POA-HDI]
]3DIoutADD ; From ATOSSDMI2: -
[7991774 - A10504260.maq ---
email to Rane and Katie
015-10-12 18:27:12 [ Millman, Emma }
Jzneut_en_poa : Transfer Notification
2015-10-13 04:19:29 [ POA-HDT]
lxDToutaDD : From ATOSSDM12: -
Jemail from MAC
2015-10-13 04:20:02 [ FOA-HDT]
lDIoutapp : From ATOSSDMI2: —
17991774 - A10504260.msg -—-
jomail sent to Katie Austin and Abhishek Rane
“Attachement RE 2248433 Dalmellington Outreach Service - horizon transaction discrepancies
“Attachement A1050426017991774 .msg ---
“Attachement RE 2248433 Dalmellington Outreach Service - horizon transaction discrepancies
2015-10-13 04:21:33 [ POA-HDI]
dDToutADD : From ATOSSDM12: 2015/10/13 04:19:26 GMT Log Comment - received an email from MAC asking for a correct time and date
jof the issue occurred
POL00029902
POL00029902
F forwarded email to Katie Austin and Abhishek Rane of IM
From: Post Office Service Desk
Sent: Tuesday, October 13, 2015 12:18 PM
: Austin, Katie (ext); Rane, Abhishek
2248433 I Dalmellington Outreach Service - horizon I transaction discrepancies / 17991774 - A10504260
lcood Morning,
JWe receive a new email from Fujitsu, please see belo
in regards to the above call, in the call notes it states the Date & Time of the issue as ?today @ 1300.? I think you will find
this is incorrect as the issue was originally raised on 8th October.
Please provide us with the correct date so we can investigate this.
Incident is still assigned to Fujitsu.
je will try to call the branch later to get the right information needed by them.
I will try to call the branch later if queue persist
2015-10-13 04:22:34 [ POA-HDI]
]sDIoutaDD : From ATOSSDM12: ----Attachement Automatic reply 2248433 Dalmellington Outreach Service - horizon transaction
iscrepancies 17991774 - A10504260.msq
0 email from Katie Austin
2015-10-13 04:23:04 [ POA-HDI]
iDroutaDD : From ATOSSDM12: 2015/10/13 0:
From: Austin, Katie (ext)
sent: Tuesday, October 13, 2015 1:44 AM
to: Post Office Service Desk
subject: Automatic reply: 2248433 I Dalmellington Outreach Service - horizon I transaction discrepancies / 17991774 ~ A10504260
:22:08 GMT Log Comment - 000 email from Katie Austin
[Thank you for your email.
I am travelling to offsite meetings on Tuesday 13th
For any urgent issues, please call me on my mobile
2015-10-13 08:50:22 [ POA-HDI]
ibtoutapp : From ATOSSDM12: 2015/10/13 08:49:34 GMT Log Comment email from Katie to IM:
Q¢
ober and will therefore have limited access to email.
labhishek ? Please can you correct this with Fujitsu ? I believe the issue was reported on the 8th in the morning?
Ik
2015-10-13 08:50:56 [ POA-HDI]
IDIoutADD : From ATOSSDM12: -
Ik7991774 ~ A10504260.msg —-~
email from Katie to IM
2015-10-13 13:43:00 [ Millman, Emma }
lzDIoutSTU : Abhishek from Atos IMT called for an update.
“Attachement RE 2248433 Dalmellington Outreach Service - horizon transaction discrepancies
Ii advised we are currently awaiting an update the SD regarding the correct date of when the issue occurred.
hishek advised the correct date is 8th October.
It advised I will amend the call and now I will send it over for investigation.
jpo15-10-13 13:46:11 I Millman, Bmma I
Jzneut_en poa : Transfer Notification
***Please can PEAK investigate this discrepancy issue. NBSC has confirmed that following discussions and checks with the user
that this is not a user error issue, but an issue within the system requiring Fujitsu investigation.****
IDate:13-Oct-2015 15:33:39 User:Jonathan Pegg
Jproduct, HNG-X Platforms -- HNG-X Counter App (CNT) (version unspecified) added.
jbate:13-Oct-2015 1
[Start of Response]
7:03 User:Jonathan Pegg
IPRESCAN
comments:
IKEL Reference:
ssigned User: Cheryl Card
[End of Response]
Response code to call type L as Category 40 -- Pending -- Incident Under Investigation
Response was delivered to Consumer
jate:13-Oct-2015 15:37:38 User:Jonathan Pegg
[the Call record has been assigned to the Team Member: Cheryl Card
Progress was delivered to Consumer
jDate:13-Oct-2015 15:53:44 User:Cheryl Card
[fhe Call record has been assigned to the Team Member: Anne Chambers
progress was delivered to Consumer
Jbate:13-Oct-2015 16:32:09 User: Customer Call_
Prom ATOSSDM12: 2015/10/13 15:29:41 GMT Log Comment incident raised on 8th Oct
POL00029902
POL00029902
falled Samp; updated PM the situation
spoke with Fujitsu, updated them the correct incident raised date. they are currently investigating
bate:13-Oct-2015 17:42:11 User:Anne Chambers
[Start of Response]
i can see that the clerk pressed Enter 4 times after the Delivery Receipts were printed, and each time a vem in transaction for
k8000 and its cash settlement were recorded. This should not be possible. Continuing to investigate.
[End of Response]
Response code to call type L as Category 40 -- Pending -- Incident Under Investigation
Response was delivered to Consumer
jbate:14-Oct-2015 0°
From ATOSSDM12:
10504260.msg
jemail from Abishek Rane
Customer Cali_
“Attachement RE 2248433 Dalmellington Outreach Service - horizon transaction discrepancies 17991774 -
jDate:414-Oct-2015 07:13:11 User: Customer Call_
lrrom ATOSSDM12: ----Attachement RE 2248433 Dalmellington Outreach Service - horizon transaction discrepancies 17991774 -
1a10504260.msq
lesponse to Abishek Rane
Date:14-Oct-2015 07:14:11 User: Customer Call_
lfrom ATOSSDM12: 2015/10/14 06:11:36 GMT Log Comment -email from Abishek Rane:
I" Yes, it?s for 8th Oct
Details were send with ref with 17972295
Regards,
lAbhishek Rane
embassy ‘Tech Zone,
ltinjewadi, Phase-2, Pune-411057
tos India "
I-responded to Abishek Rane
emails attached
Joate:14-Oct-2015 15:23:24 User:Anne Chambers
call cloned from original call:PC0246949 by User:Anne Chambers
jbate:14-Oct-2015 15:25:02 User:Anne Chambers
clone taken for investigation into the root cause. Original call PC0246949 will be used to make sure the financial implications
Jat the branch are resolved.
jbate:14-Oct-2015 15:35:38 User:Anne Chambers
evidence Added ~ 01_pocl51008.txt - File will be Obfuscated and made available to download soon.
Dat ¢:14-Oct-2015 15:36:33 User:Anne Chambers
nvidence Added - 01 pocl51001.txt - File will be Obfuscated and made available to download soon.
jbate:14-Oct-2015
lbvidence Added - work
6:53 User:Anne Chambers
day set 8th Oct
JDate:14-Oct-2015 15:37:05 User:Anne Chambers
Jnvidence Obfuscated File (CTRPOC) Added -
Jate:14-Oct-2015 15:37:07 User:Anne Chambers
lsvidence Obfuscated File (CTRPOC) Added - i
jpate:14-Oct-2015 1
Ievidence Added - <
7:14 User:Anne Chambers
1 di 1-8 Oct
jDate:14-Oct-2015 15:42:25 User:Anne Chambers
[Start of Response]
outing to GDC to investigate why user was able to press enter and settle the same "rem in" basket multiple times. I have not
anaged to reproduce this. non-core links 7167 and 20290 enabling Outreach and Branch to Branch Rems, which may or may not be
relevant.
[End of Response]
lkeaponse code to call type € as Category 40 -- Pending -- Incident Under Investigation
Date:44-Oct-2015 15:49:15 User:Anne Chambers
IA new Business Impact has been adde:
jBranch has a discrepancy of £24000 which they cannot resolve themselves. Only one known instance.
POL00029902
POL00029902
[Date:i4-Oct-2015 15:49:42 UscriAnne Chambers
[the Call record has been transferred to the team: xCtr_ GDC
lUser:Anne Chambers Confirmed that this Incident may be passed to the external company with the attached evidence.
Date:44-Oct-2015 16:12:51 User:Anne Chambers
Ihe call Priority has been changed from C
the call Priority is now B
[Date:14-Oct-2015 17:21:38 User:Anne Chambers
evidence Added - 207828 01 pocl51012.txt - File will be Obfuscated and made available to download soon.
JDate:14-Oct-2015 17:22:07 User:Anne Chambers
lkvidence Added - 106444 01 pocl50909.txt - File will be Obfuscated and made available to download soon.
Date:14-Oct-2015 17:24:36 User:Anne Chambers
lbvidence Added - 110444 01 poci50914.txt - File will be Obfuscated and made available to download soon.
JDate:14-Oct-2015 17:27:02 User:Anne Chambers
Invidence Obfuscated File (CTRPOC) Added - F
JDate:14-Oct-2015 17:27:08 User:Anne Chambers
Ifvidence Obfuscated File (CTRPOC) Added - F.
sible further instance: 106444 poc.log.
Jbate:14-Oct-2015 17:27:17 User:Anne Chambers
Isvidence Obfuscated File (CTRPOC) Added ~
Possible further instanc
Date:15-Oct-2015 08:53:45 User:Shanmukha Bhogireddy
fhe Call record has been assigned to the Team Member: Venkata Peddapothula
JDate:15-Oct-2015 08:56:00 Uscr:Pavan Vejendla
laction placed on Team:xCtr GDC, User:Venkata Peddapothula
Date:48-Oct-2015 10:13:21 User:Venkata Peddapothula
Followed the above steps for reproducing the issue. But not able to reproduce the issue.T can see in the log file that
IBarCode (905002216551) has been used in different sessions 1-12440,1-12441,1~12442,1-12443, which seems strange.Investigation is
lin progress and trying to reproduce the problem
JDate:15-Oct-2015 10:31:05 User:Anne Chambers
IThe Business Impact has been updated:
Isranch has a discrepancy of £24000 which they cannot resolve themselves. 4 other branches have had a similar problem in the last
2 months.
jDate:15-Oct-2015 11:05:18 User:Anne Chambers
[Start of Response]
It just managed to reproduce this on a test system, by logging into a stock unit which required an immediate cash declaration,
then after printing a declaration receipt leaving the counter to timeout and log me off. Then logged back on, Pouch Delivery,
anual entry. After the 2 delivery receipts were printed I pressed Enter which printed the Rem In slip. Then instead of the
Remittances & Transfers Home’ screen being displayed, the Pouch Delivery screen was still showing, with Enter enabled. Pressing
enter again repeated the rem in and slip print.
jbon’t know whether this can be reproduced reliably, will retry.
f the examples we've seen so far, before the multiple rem ins:
2 counters had inactivity logout after cash dec
2 had system logouts due to lack of connectivity when settling TAs
{End of Response]
Response code to call type C as Category 40 -- Pending -- Incident Under Investigation
jDate:15-Oct-2015 11:40:43 Usecr:Steven Porter
ny kind of log-out *should* have resulted in ScriptControllerBLO.resetControler() being called (this listens to log off events),
Iso I'd be interested to understand why that's not being called or why the BLO stack is not being reset as a result of log out in
the cases that Anne outlines.
Date:15-Oct-2015 13:09:25 User:Anne Chambers
It have reproduced the second variant too, by creating a TA, logging on, then removing the network cable before pressing Process
TAs. This caused a System Logout. Then I replaced the cable, logged back on, processed the TA then did the rem in as before.
Date:45-Oct-2015 13:13:33 User:Anne Chambers
[fhe Business Impact has been updated:
Branch has a discrepancy of £24000. 4 other branches have had a similar problem in the last 2 months. 3 of these resolved by
remming out the excess, Since these were all branch-to-branch rems and there is no cross-branch accounting within Horizon, this
POL00029902
POL00029902
[removes the discrepancy.
bate:15-Oct-2015 13:24:14 User:Steven Porter
i've had a further look at the code, and it seems to me that the code does not clean up properly if we are force logged off
turing the post-login-checks. More generally, if the user has been authenticated but not completed the log on process completely
(i.¢. has not yet reached the front office home menu) then force log off can leave the CBA in a bad state.
[fhe issue seems to be around BasicLogOff£BLO and ApplicationHelperBLO. It seems that ApplicationHelperBLO.abandonApplication() has
Ino effect if the user is in the middle of post login checks. Further careful analysis needed to underst.
nd where the issue is.
belts-n-braces change could be to add a call to resetController() when the “log off" event is received in ScriptControllerBLO.
Dat e:15-Oct-2015
Evidence Added -
0:14 Uscr:Steven Porter
t
Dat e:15-Oct-2015
Reference Added:
9:14 User:Anne Chambers
KEL acha62ik
Jat ¢:15-Oct-2015
[Start of Respon:
KEL acha621P raised.
[End of Response}
Response code to call type C as Category 40
Pending -- Incident Under Investigation
jDate:16-Oct-2015 0: 225 User:Venkata Peddapothula
It am able to reproduce the issue based on 2 scenarios mentioned above.
land after applying the code patch issue has been resolved.Tested the above 2 scenarios.
JDate:16-Oct-2015 09:58:42 Uscr:Venkata Peddapothula
[Start of Response]
[End of Response]
Response code to call type C as Category 41 -- Pending -- Product Error Diagnosed
lbate:22-Oct-2015 09:23:27 User:Tony Wicks
[this issue has high visibility in ATOS and Post Office. Consideration was given to producing a Hot Fix possibly for R12.88.
lfowever, due to the impact this would have on other scheduled activities and as the issue can be avoided it was proposed that a
KEL is raised for this and the fix is released within counter release 13.05. I have asked the SSC to produce a KEL. Would you
lease progress this Peak so that Release Management take it to BIF and onto the Peak Targeting Forum for release in R13.05
jbate:27-Oct-2015 11:13:09 Uscr:Steven Porter
the call Target Release has been moved to Proposed For -~ HNG-X 13.05
JDate:28-Oct-2015 13:50:06 Uscr:Ramesh Kalavakolla
SIF Summar
fter completing delivery transaction, user is allowed to press ENTER button multiple times, which leads to print multiple
delivery receipts and also cash settlements were recorded.
by fixing this issue, we can avoid the transaction discrepancies.
Irix is simple and low risk.
please approve for fix.
JDate:28-Oct-2015 13:50:15 Uscr:Ramesh Kalavakolla
ction has been removed from the call
Jbate:28-Oct-2015 13:50:32 Uscr:Ramesh Kalavakolla
lAction placed on Team:BIF
jDate:02-Nov-2015 08:06:55 Uscr:Lorraine Elliott
[the call Target Release has been moved to Targeted At -- HNG-X 13.05
[Date:02-Nov-2015 08:07:07 User:Lorraine Elliott
IBIF approved and targeted as requested
Date: 02-Nov-2015 08:07:10 User:Lorraine Elliott
ction has been removed from the call
POL00029902
POL00029902
[bate:02-Nov-2015 10:35:18 User:Pavan Vejendla
lAction placed on Team:xCtr_GDC, User:Venkata Peddapothula
Jat e:25-Nov-2015 09:32:10 User:Iain Janssens
[the call Target Release has been moved to Proposed For == HNG-X 12.88
jate:26-Nov-2015 09:55:38 User:Vijesh Pandya
IThe call Target Release has been moved to Targeted At -~ HNG-X 12.88
jbat¢:26-Nov-2015 13:16:41 Uscr:Venkata Peddapothula
[DEVELOPMENT IMPACT OF FIX
SPECIFY THE HNG-X PLATFORMS IMPACTE
Product & Product Group. specified?
ves.
TECHNICAL SUMMARY:
this change will affect 1 java class (ScriptControllerBLO. java)
LIS? OF KNOWN DIMENSIONS DESIGN PARTS AFFECTED BY THE CHANGE:
[DEPLOYMENT DETATL:
DEV EFFORT IN MANDAYS:
2 man days for development and testing.
HMPACT ON USER:
Benefit of making the fix.
fter the Rem In slip is printed, the Remittan
3 & Transfers Home screen will display.
IMPACT ON OPERATIONS:
lAfter completing delivery transaction,user is allowed to press ENTER button multiple times, which leads to print multiple
lelivery receipts and also cash settlements were recorded.
HAVE RELEVANT KELS BEEN CREATED OR UPDATED?
ves , acha621P.
HMPACT ON TEST:
Senario 1:
hLogon counter which is required an immediate cash declaration.
2.After printing a cash declaration receipt leave the counter to timeout and logout.
3-Again logon counter
J4.Do the pouch Delivery transactions
b.After the delivery receipts printed,Remittances & Transfers Home's screen should come.Earlier user is able to press the ENTER
button multiple times,which is causing the descripency.
lsenario 2:
ll.Performed the TAs.
2.Logon counter and don't process the TAs, leave the counter to timeout and force logout.
3-Again logon counter.
a.Do the pouch Delivery transactions.
lb.After the delivery receipts printed, Remittances & Transfers Home's screen should come.Earlier user is able to press the ENTER
utton multiple times,which is causing the descripency.
IRISKS (of releasing and of not releasing proposed fix):
lot Releasing the fix:
fter completing delivery transaction,user is allowed to press ENTER button multiple times, which leads to print multiple
lelivery receipts and also cash settlements were recorded.
Releasing the fix:
lafter the Rem In slip is printed, the Remittances & Transfers Home screen will display.
LIST OF LIKELY DELIVERABLES:
ScriptControllerBLO. java
[Date:26-Nov-2015 13:18:57 User:Venkata Peddapothula
POL00029902
POL00029902
FINGX cope FIX
FTX DESCRIPTION
explained Above.
IPROPOS
Ik12.88.
BRANCH
COUNTER JAVA FILES CHANGED
vee.
COUNTER PDL FILES CHANGED
lone.
[COUNTER REFDATA FILES CHANGED
jone.
SHARED CODE FILES CHANGED
BAL, JAVA CODE FILES
lone.
CHANGED
sol. FILES CHANGED
jone.
loTHER FILES CHANGED
lone.
IAPPROPRIATE CODE COMMENTS
ves.
DEPENDENCIES
None.
RELATED PROBLEMS
None.
UNIT TE
A.
STING EVIDENCE
REGRESSION TEST CLASS
a.
BACKWARDS COMPATIBILITY
A.
DEVELOPMENT DOCUMENTATION
None.
REQUIREMENTS DOCUMENTATION
HELP
one.
jbate:26-Nov-2015 13:19:52 Uscr:Venkata Peddapothula
[Start of Response]
[End of Response]
Response code to call type C as Category 46 -- Pending -- Product Error Fixed
[Date:26-Nov-2015 1
Reference Added: Rele.
158 UscriJohn Budworth
Date: 27-Nov-2015
cit Test details
Peak has been verified successfully in CIT environment. Tested both scenarios now, after the receipt is printed control back to
lkemittances & Transfers Home's screen.
8:26 Uscr:Pavan Vejendla
Date:27-Nov-2015 13:38:42 Uscr:Pavan Vejendla
jefect cause updated to 14: Development - Code
jbate:27-Nov-2015 13:40:23 Uscr:Pavan Vejendla
Ineference Added: Product Baseline CTR APP X1288 Ve46
Date:27-Nov-2015 13:40:25 User:Pavan Vejendla
[OP Reference set to: Product Baseline CTR _APP_X1288_v646
POL00029902
POL00029902
Date: 27-Nov-2015 14:36:38 User:Pavan Vejendla
[the Call record has been transferred to the team: Dev-Int-Rel
lUser:Pavan Vejendla Confirmed that this Incident may be passed to the external company with the attached evidence.
JDate:01-Dec-2015 10:13:28 User:Graham Jennings
Delivery rejected due to issues caused we believe by the move to Dimensions 12.
counter Distrib is failing as we get an ERRORLEVEL 16 returned by HashUtil
Failing checksum counts
Date: 09-Dec-2015 15:13:27 User:Rick Carter
[the Call record has been transferred to the team: Live Supp.Test
JDate:09-Dec-2015 15:14:36 User:James Guy
ction has been removed from the call
jDate:09-Dec-2015 15:20:41 User:James Guy
[Start of Response]
completed testing in LST
lkem ins after a interrupted login now work as expected. No duplication.
[End of Response]
Response code to call type C as Category 49 -- Pending -- Fix Available for IndependentTest
jDate:09-Dec-2015 15:20:53 Uscr:James Guy
fhe Call record has been assigned to the Team Member: Release to Live
Joate:14-Jan-2016 10:45:36 User:John Budworth
[Start of Response]
TR_APP_X1288_V646 Released to live via COUNTER APP 77_7.
lkoll Out to live estate commenced overnight Tuesday Jan 12th 2016. About 400 counters outstanding. Routing to call logger for
closure.
[End of Response]
Response code to call type C as Category 60 -- Final -~ S/W Fix Available to Call Logger
kouting to Call Logger following Final Progress update.
Date:14-dan-2016 10:54:50 UsorsAnne Chambers
(Start of Response]
KEL updated. Closing call.
[End of Response]
Response code to call type ¢ as Category 60 -- Final -- S/W Fix Available to Call Logger
touting to Call Logger following Final Progress update.
Jbate:14-Jan-2016 10:54:58 Uscr:Anne Chambers
CALL PCO246997 closed: Category 60 Type C
Root Cause Development - Code
Logger Deleted User -- EDSC
Subject Product General/Other/Misc -- Unknown (version unspecified)
Assignee Deleted User -- EDSC
Last Progress 14-Jan-2016 10:54 -- Anne Chambers