FUJ00171923
FUJ00171923
Peak Incident Management System
Call Reference PC0275906 Call Logger Jon Hulme -- Bus Apps Des
Release Targeted At -- HNG-X 69.20 Top Ref HNGA PACKAGE CBA 6920 D165
Call Type Internal Development Incidents/Defects Priority D -- Non-Urgent
Contact Jon Hulme Call Status Closed -- Build Fix Available to Call Logger
Target Date 31/12/2018 Effort (Man Days) 0
Summary Attach user to stock unit omits logged on user name if check fails in data centre
All References Type Value
Jira CBB-3285
Product Baseline HNGA_ PACKAGE CBA 6920 D165
Collections I Name User Date
BIFApproved Raj Bains 30-Jan-2019 10:12:04
Impact
Si ee ‘ User Date
Unknown 22-Jan-2019 09:37:06
Problem Statement ( Underlying cause of problem):
We have done a EUM CP(CP2144) few months back which introduced this functionality of concurrent
logon. As this is a new feature there are some business scenarios we didn?t took into account last time and
that?s how we got this bug. Now we have identified a few bugs in concurrent logon scenarios and we will
also be doing ?CP2368 EUM Balancing Enhancements? in a few days to address all the design issues.
A bug in 7BAD123BLO Attach User To Stock Unit.pdl? was causing the issue. Previously we were not
passing the ?attachedUser? from the pdl to the message fragment in the business scenario and due to this
placeholder variable in the message fragment could not be resolved during execution of the business
scenario.
Risk of not fixing: If we don?t fix this issue then the message we are getting during business scenario
doesn?t make any sense as we are not getting any value for placeholder variable.
Benefit of fixing: MSG30002 makes sense because placeholder is now being replaced with actual value.
ASM Utilization Capacity: 1
Progress Narrative
fbate:21-Dec-2018 09:37:36 User:Jon Hulme
CALL PC0275906 open:
Details entered are
summary :At
call Type:
call Priority:D
ch user to stock unit omits logged on user name if check fails in data centre
G-X 68.20
pps_Des - Jon Hulme
Date:21-Dec-2018 09:37:36 User:Jon Hulme
[Start of Response]
hen the clerk choses a user to change the stock unit they are attached to, the counter performs a check to see if that user is
logged on, and gives an error message (MSG30002) if they are, showing in the message the user name that is already logged on.
Inf that check passes, the clerk choses the stock unit to attach to and calls the data centre to action this. The data centre
performs the performs various checks. In particular, if the user to be attached is not the current user, a check is made that the
t logged on.
luser is
Inf the final check fails, MSG30002 is again displayed by the counter, but in this case there is a bug that it does not display
ut instead display the substituion variable name with percent delimiters.
Response code to call Internal Development Incidents/Defects(I) as Potential Problem Identified (38)
JDate:24-Dec-2018 09:38:35 Uscr:Jon Hulme
[the Call record has been transferred to the team: xCtr_GDC
FUJ00171923
FUJ00171923
fDate:02-Jan-2019 08:44:29 Uscr:Ramesh Kalavakolla
lthe Call record has been assigned to the Team Member: Shweta Patil
lbate:02-dan-2019 08:47:02 User:Shweta Patil
the Call record has been assigned to the Team Member: Abhijit Banarjee
Jbate:11-Jan-2019 11:45:36 User:Jon Hulme
ffo recreate the issue, perform the following steps.
sy Horizon User below I mean one which is not a EUM user, i.e. does not have a POID.
h. Login to counter 1 as Horizon user A.
2. Click Back Office, Admin, Attach User
3. Choose Horizon user B, Enter
4. Login to counter 2 as Horizon user B.
5. Return to counter 1.
6. Choose a different stock unit to the one User B is currently attached to, Enter
I7. You get message MSG30002 without the user id.
jate:12-an-2019 15:51:20 Uscr:Ramesh Kalavakolla
[thank you Jon for your help. Now Abhijit was able to reproduce the issue with the steps you provided.
jDate:15-Jan-2019 13:26:54 User:Abhijit Banarjee
evidence Added
bate:15-dan-2019 1
[Start of Response]
[there was a bug in the "BAD123BLO Attach User To Stock Unit.pdl" which was causing the issue. Fixed that and attached the code
patch on the peak.
{End of Response]
esponse code to call type I as Category 46 -- Pending -- Product Error Fixed
9:30 User:Abhijit Banarjee
pate:22-Jan-2019 09:36:48 User :Maciej Frontezak
problem Statement ( Underlying cause of problem):
le have done a EUM CP(CP2144) few months back which introduced this functionality of concurrent logon. As this is a new feature
there are some business scenarios we didn?t took into account last time and that?s how we got this bug. Now we have identified a
few bugs in concurrent logon scenarios and we will also be doing ?CP2368 EUM Balancing Enhancements? in a few days to address all
the design issues.
lA bug in ?BAD123BLO Attach User To Stock Unit.pdl? was causing the issue. Previously we were not passing the ?attachedUser? from
the pdl to the message fragment in the business scenario and due to this placeholder variable in the message fragment could not
pe resolved during execution of the business s:
nario.
Risk of not fixing: If we don?t fix this issue then the message we are getting during business scenario doesn?t make any sense as
fe are not getting any value for placeholder variable.
Benefit of fixing: MSG30002 makes sense because placeholder is now being replaced with actual value.
SM Utilization Capacity: 1
lbate:22-Jan-2019 09:37:06 User:Maciej Frontezak
lA new Business Impact has been adde
Problem Statement ( Underlying cause of problem):
we have done a BUM CP(CP2144) few months back which introduced this functionality of concurrent logon. As this is a new feature
there are some business scenarios we didn?t took into account last time and that?s how we got this bug. Now we have identified a
few bugs in concurrent logon scenarios and we will also be doing ?CP2368 EUM Balancing Enhancements? in a few days to address all
the des
gn issues.
lA bug in ?BAD123BL0 Attach User To Stock Unit.pdl? was causing the issue. Previously we were not passing the ?attachedUser? from
the pdi to the message fragment in the business scenario and due to this placeholder variable in the message fragment could not
Ibe resolved during execution of the business scenario.
Ikisk of not fixing: If we don?t fix this issue then the message we are getting during business scenario doesn?t make any sense as
lwe are not getting any value for placeholder variable.
enefit of fixing: MSG30002 makes sense because placeholder is now being replaced with actual value,
lASM Utilization Capacity: 1
Date:29-Jan-2019 12:48:45 User:Maciej Frontczak
lAction placed on Team:BIF
[Date :30-Jan-2019 10:12:20 User:Raj Bains
IBIF approved on 30/01/2019, to be taken to the customer
FUJ00171923
FUJ00171923
[Jate:30-San-2019 10:12:22 Uscr:Raj Bains
ction has been removed from the call
bate:31-Jan-2019 09:50:09 User:Maciej Frontezak
leroblem Statement ( Underlying cause of problem): Following the EUM investigation, it has been found that if the check fails on
loc level when user is trying to change the stock unit they are attached to the error message they are getting is missing their
name.
such scenario in unlikely but possible.
hen the clerk choses a user to change the stock unit they are attached to, the counter performs a check to see if that user is
hogged on, and gives an error message (MSG30002) if they are, showing in the message the user name that is already logged on.
I'f that check passes, the clerk choses the stock unit to attach to and calls the Data Centre to action this. The Data Centre
jperforms various checks, in particular, if the user to be attached is not the current user, a check is made that the user is not
flogged on.
Ite the final check fails, MSG30002 is displayed by the counter, but in this case there is a bug that it does not display the user
Iname but instead display the substituion variable name with percent delimiters.
Risk of not fixing: If this is not fixed then the message we are getting during business scenario doesn't make much sense.
Benefit of fixing. MSG30002 explains what the problem is because placeholder is now being replaced with actual user name.
ASM Utilisation Capacity: 1
jbate:31-Jan-2019 12:14:45 User:Macie}j Frontezak
Action placed on Team:PTF
bate:07-Feb-2019 10:55:07 User:dubita Gurung
lAwaiting confirmation on how BUM fix is going to be progressed.
JDate:07-Feb-2019 10:55:31 User:Jubita Gurung
fo be left on PTF stack.
jDate:14-Feb-2019 11:52:55 User:Gimey johnbasco
Jira CBB-3285
JDate:21-Feb-2019 10:37:59 User:Jubita Gurung
the call Target Release has been moved to Targeted At -- HNG-X 19
IDate:21-Feb-2019 10:38:07 User:Jubita Gurung
targeted to R19.20 as per 21/02/2019 PTF meeting.
jbate:21-Feb-2019 10:38:10 Uscr:Jdubita Gurung
Action has been removed from the call
oate:21-Feb-2019 15:57:55 User:Jubita Gurung
etargeting it to R69.20 as its a Counter Change.
jbate:21-Feb-2019 15:58:11 User:Jubita Gurung
[the call Target Release has been moved to Targeted At -- HNG-X 69.20
Date:25-Feb-2019 14:53:49 Uscr:Ramesh Kalavakolia
[Start of Response]
[End of Response]
Response code to call type I as Category 76 -- Pending -- Fix Targeted awaiting Release
Jbate:06-Mar-2019 04:59:15 User:Abhijit Banarjee
[fhe Call record has been assigned to the Team Member: Pavan Vejendla
loate:12-Mar-2019 09:16:54 Uscr:Ramesh Kalavakolla
the Call record has been transferred fo the team: xCtr REL GDC
he Call record has been assigned to the Team Member: Pavan Vejendla
Date:26-Mar-2019 13:03:59 Uscr:Praveen Challa
h. Logged into counter 1 as Horizon user CCT{GRO}
2. Clicked on Back Office --> Admin --> Attach User
3. Selected Horizon user CC Enter
FUJ00171923
FUJ00171923
fi. Login to counter 2 as Horizon user (con
IS. Returned to counter 1.
6. Tried to select a different stock unit to the one User CCI{GA
7. Displayed message ‘User Account Legged On MSG30002" — cCigR
is currently attached
is already logged in
jDat¢:26-Mar-2019 15:05:01 User:Dimensions Automated User
Reference Added: Product Baseline HNGA PACKAGE CBA 6920 D165
JDate:26-Mar-2019 15:31:30 User:Praveen Challa
Pefect cause updated to 14: Development ~ Code
JDate:26-Mar-2019 15:32:09 User: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.
JDate:27-Mar-2019 08:49:36 Uscr:Geoff Inglis
[the Call record has been assigned to the Team Member: PIT Automated User
Jbate:27-Mar-2019 08:51:27 Uscr:Geoff Inglis
outing to SVI test as integration have nothing to process here.
fhe Call record has been transferred to the team: ITU System Validation & Integration
[fhe Call record has been assigned to the Team Member: Unassigned
bate: 26-Apr-2019 12:34:26 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
outing to Call Logger following Final Progress update.
jbate:30-Apr-2019 12:59:41 User:Jon Hulme
CALL PCO275906 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