APIs to get unsynced beneficiaries and count of unsynced beneficiaries - For CHO mobile application

[shreypatidar-beehyv]

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Type of change

• Bug fix
• New feature
• Enhancement
• Refactoring
• Documentation
• Other ( please specify )

How Has This Been Tested?

-This service has been deployed and tested on Beehyv staging server.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

[drtechie]

@devikasuresh20, @ravishanigarapu can you please review the business logic.
Code wise LGTM.

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[ravishanigarapu]

Why you changed searchByDistrictId endpoint to searchByVillageIdAndLastModifiedDate
because of searchByDistrictId already we are using in WHC API.

[shreypatidar-beehyv]

This is an API that returns the list of beneficiaries based on a list of village IDs and the last sync date time. It is used to sync beneficiaries for the CHO Android mobile application. Since this and the upstream APIs (In HWC-API) using this endpoint were created by our team and required some changes i.e. why did the modifications as well as the name change .
As for the HWC-API, this endpoint has also been updated there in the properties files.

[ravishanigarapu]

looks ok