FUJ00171931
FUJ00171931
Peak Incident Management System
Call Reference PC0275890 Call Logger Jon Hulme -- Bus Apps Des
Release Targeted At -- HNG-X 69.20 Top Ref ~ PC0277791
Call Type Internal Development Incidents/Defects Priority D -- Non-Urgent
Contact Jon Hulme Call Status Closed -- Build Fix Available to Call Logger
Target Date 30/12/2018 Effort (Man Days) 0
Summary Cash Variance Screen Misleading
All References Type Value
Jira CBB-3266
Clone Call PC0277791
Product Baseline HNGA PACKAGE CBA 6920 D165
Impact
SI eee User Date
Jon Hulme 20-Dec-2018 11:27:32
Clerks may be confused as to their financial cash position in the stock unit, albiet unlikely to happen very
often since it is a concurrency issue.
Progress Narrative
fate: 20-Dec-2018 11:26:24 User:don Hulme
kaLL c0275890 opened
‘ash Variance Screen Misleading
call Type:t
call Priorit:
ffarget Rele. NG-X 68.20
Routed to:Bus Apps Des ~ Jon Hulme
D
bate: 20-Dec-2018 11:26:24 User:Jon Hulme
[Start of Response]
consider the following scenario:
h) You are attached to a shared stock unit.
2)Press Back Office, Weekly Accounting, Cash Variance.
3) This displays a screen showing the latest declaration(s) for the currently attached stock unit.
4) Press Enter.
5) The difference between the latest declaration(s) and the system derived figure is displayed.
[this also happens if you press the Variance button when making a cash declaration on the Print/Preview Declared Cash screen.
this all works fine, but the issue is that if there is a delay between steps 4) and 5) above then another user may make a new
}declaration/overwrite a declaration for that stock unit. When you press Enter at step 5) the code uses the latest declaration.
[this may be confusing because the clerk assumes it is using the declarations shown on the screen.
the counter should warn the clerk that one or declarations have changed, and the declaration list screen should be redisplayed
ith the updated declaration details.
It am awaiting confirmation of this change from POL.
[End of Response]
Response code to call Internal Development Incidents/Defects (1) as Potential Problem Identified(38)
jDate:20-Dec-2018 11:27:04 User:Jon Hulme
new Business Impact has been adde:
clerks may be confused as to their financial cash position in the stock unit.
bate:20-Dec-2018 11:27:32 User:Jon Hulme
[fhe Business Impact has been update
clerks may be confused as to their financial cash position in the stock unit, albiet unlikely to happen very often since it is a
Jconcurrency issue.
jbate:11-dan-2019 12:12:45 User:Jon Hulme
lAgreed with POL and Steve Bansal that this needs to follow the normal route for incident handling. BIF will need input from POL
jas to whether they agree that this should be fix as proposed.
Jbate:11-Jan-2019 12:12:58 User:Jon Hulme
[the Call record has been transferred to the team: xCtr_GDC
FUJ00171931
FUJ00171931
[Date:2i-an-2019 11:47:33 UscriRamesh Kalavakolla
[fhe Call record has been assigned to the Team Member: Ankit Pai
bate:21-Jan-2019 14:02:37 User:Ankit Pai
Start of Response]
lanalysis is in progress.
[End of Response]
Response code to call type I as Category 40 -- Pending -- Incident Under Investigation
Jate:24-Jan-2019 07:03:38 User:Ankit Pai
Reference Added: Jira CBB-3266
jbate:04-Feb-2019 11:26:11 Uscr:Ankit Pai
je have received the inputs from architect.
le are working on the fix as suggested.
jDate:04-Feb-2019 11:26:36 Uscr:Ankit Pai
[fhe Call record has been assigned to the Team Member: Vipin John
JDate:41-Feb-2019 12:35:15 User:Vipin John
started working on this Peak. Cash declaration pop up is coming at the right place now. Need to work on the comments that has
been provided by Jon
ht) By simply re-displaying the cash declaration Li
leclaration list screen.
{fo fix this you need to tag the screen using ADCController.addfag, and then just before you re-display the new sc
cid of the old one via ADCController.clearPreviousScreen (tag) -
2) Message Text
3) type to = ?cash? hard coded string -
tt screen, the clerk
can still press Prev and return to the old cash
een version get
[thanks
ipin
JDate:11-Peb-2019 13:02:25 User:Ramesh Kalavakolia
(Start of Response]
{End of Response]
lesponse code to call type I as Category 41 -- Pending -- Product Error Diagnosed
[Date:12-Feb-2019 11:39:38 User:Harishkumar Malayil
Hi Jon,
can you please confirm whether you received necessary input from POL to take this Peak to BIF as per your comment.
jbate:11-Jan-2019 12:12:45 User:
\lon Hulme
lAgreed with POL and Steve Bansal that this needs to follow the normal route for incident handling. BIF will need input from POL
las to whether they agree that this should be fix as proposed.
jDate:12-Feb-2019 11:40:11 Uscr:Harishkumar Malayil
ii Vipin,
could you please provide business impact in the below format, so that the Peak can be assessed by BIF.
problem Statement ( Underlying cause of problem):
Risk of not fixing:
Benefit of fixing:
lasM Utilization
pacity:
[Date:15-Feb-2019 1:
Hi Vipin,
User:Harishkumar Malayil
Its there is any update on this Peak? Are you able to provide business impact yet.
Date: 20-Feb-2019 06:09:47 User: Vipin John
Problem Statement ( Underlying cause of problem): Cash variance does not show correct cash position if any other user declared
leash between the time the latest cash declaration screen and discrepancy screen is displayed.
Risk of not fixing: This will be misleading to the clerk as the declaration shown on screen is different from the discrepancy.
FUJ00171931
FUJ00171931
[Benefit of fixing: The clerk will be warned that the one or more declarations have been changed and the latest declaration screen
vill be re displayed with correct values.
IASM Utilization Capacity: 3 man days
oate:21-Feb-2019 11:25:13 User:Maciej Frontezak
ction placed on Team:BIF
[Date:27-Feb-2019 14:25:31 User:Steven Porter
the call Target Release has been moved to Proposed For -- HNG-X 69.20
jbate:27-Feb-2019 1.
Ss disc
6:14 User:Steven Porter
sed with Jon Hulme, this is a candidate for
it is an BUM-related PEAK.
Date: 28-Feb-2019 10:48:34 User:Raj Bains
[the call Target Release has been moved to Targeted At -- HNG-X 69.20
[Date:28-Feb-2019 10:49:00 User:Raj Bains
las per PIF meeting on 28/2/2019 this has been targeted at R69.20
[Date:28-Feb-2019 10:49:02 Uscr:Raj ae
ction has been removed from the
JDate:05-Mar-2019 0°
[Start of Response]
8:18 Uscr:Ramesh Kalavakolla
[End of Response]
Response code to call type [ as Category 76 ~~ Pending ~~ Fix
largeted awaiting Release
[Date:12-Mar-2019 09:20:10 Uscr:Ramesh Kalavakolla
[fhe Call record has been transferred to the team: xCtr REL GDC
fhe Call record has been assigned to the Team Member: Krishna Prabhu
IDate:14-Mar-2019 08:45:55 User:Praveen Chall. a
Hh. Logged in counter A with the POID user GDqmecvy
b. Navigated to BackOf£ice-->WeeklyAccounting-->cashVariance
lb. Displayed the latest declarations with the currently attached stock unit
la. Lock Counter A .
Ib: Logged in to counter A with the poid user Gndaum(the same Stock Unit attached to Godan!
6. Go to BackOffice and perform fresh declarations <
a
a
. BackOffice-->WeeklyAccount ing-->CashVariance
: Displayed the latest declarations
9. Lock Counter B
HO.Unlock Counter A and navigate to Cash Variance screen
ie Displayed message’Cash Declaration Changed MSG40051"
icked 6n continue
Ts Gash Garcnce Gctaen displayed the existing declarations and also fresh declaration that was made in Counter B
lorking as expected.
Attached the evidence.
status of the peak/jira can be changed to closed.
Date:14-Mar-2019 0
Evidence Added - cit
7:19 User:Praveen Challa
lDate:26-Mar-2019 07:23:06 User:Krishna Prabhu
the Call record has been assigned to the Team Member: Praveen Challa
jDate:26-Mar-2019 15:05:01 Uscr:Dimensions Automated User
Reference Added: Product Baseline HNGA PACKAGE CBA 6920 D165
Date: 26-Mar-2019 1:
Defect
3:57 Uscr:Praveen Challa
e updated to 13: Development - Build Scripts
Date: 26-Mar-2019 15:34:01 User:Praveen Challa
lbefect cause updated to 14: Development ~ Code
FUJ00171931
FUJ00171931
[Date:26-Mar-2019 15:34:18 Uscr:Praveen Challa
[the Call record has been transferred to the team: Dev-Int-Rel
lUser:Praveen Challa Confirmed that this Incident may be passed to the external company with the attached evidence.
Date: 27-Mar-2019 08:49:36 User:Geoff Inglis
the Call record has been assigned to the Team Member: PIT Automated User
bate:27-Mar-2019 08:51:27 User:Geoff Inglis
routing to SVI test as integration have nothing to process here.
e Call record has been transferred to the team: ITU System Validation & Integration
he Call record has been assigned to the Team Member: Unassigned
[bate
call has been cloned to Cal
T-Apr-2019 16:14:30 User:Paul Bott
:PC0277791 by User:Paul Bott
Date:26-Apr-2019 12:32:15 User:Paul Bott
[Start of Response]
retested and passed
(End of Response]
response code to call type I as Category 61 -- Final -- Build Fix Available to Call Logger
kouting to Call Logger following Final Progress update.
jbate:30-Apr-2019 12:59:14 User:Jon Hulme
CALL PCO275890 closed: Category 61 Type I
Root Cause Development - Code
Logger Jon Hulme -- Bus _Apps_Des
Subject Product HNG-X Counter -- Application Service (version unspecified)
Assignee Jon Hulme -- Bus Apps Des
Last Progress 30-Apr-2019 12:59 -- Jon Hulme