-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
High
-
None
-
Affects Version/s: None
-
AMRIT Sprint 21, AMRIT Sprint 22, AMRIT Sprint 23, AMRIT Sprint 24, AMRIT Sprint 26, AMRIT Sprint 27, AMRIT Sprint 28, AMRIT Sprint 29, AMRIT Sprint 30, AMRIT Sprint 31, AMRIT Sprint 32, AMRIT Sprint 34, AMRIT Sprint 35, AMRIT Sprint 36
-
It was impacting the DHIS2 project progress
-
104
-
Prod
Hi Avinash,
We have identified some cases of Beneficiary registration ID's null under Calltype as Valid for 104 services. Please find the below query and screenshot for your reference.
Query:
select t.CreatedDate,t.CreatedBy,t.BenCallID,t.BeneficiaryRegID,t.CallTime,t.CallEndTime,m.CallGroupType,m.CallType from t_bencall t
inner join m_calltype m on m.CallTypeID=t.CallTypeID
where m.CallGroupType in ('Valid')and t.createddate>= '2024-06-01'and t.BeneficiaryRegID is null order by t.CreatedDate desc;
Description
- Steps to Reproduce:
- Open the application in the browser view.
- Navigate to the login page.
- 104 user Enter valid username and password.
- after call landed information given and close the call.
- Expected Result:
HAO screen 104 call landed information given and close the call and in db beneficiary id is not saving. - Actual Result:
HAO screen 104 call landed information given and close the call and in db beneficiary id should print/save. - Observed Environment: Production
Environment
- URL: http://192.168.20.5:8080/104-ui/
- Browser: Chrom
1.
|
104 Beneficiaryregid null under t_bencall for Validcase(Need to check Callclosure API Logic) |
|
Ready for Development | Ravi Shanigarapu |
|