Open devarajd94 opened 2 weeks ago
Hi @atulgupta2024 @subhashini-egov , this is happening because sometimes indexer not able to enrich advocate details with latest process instance history , because it searched through workflow service (database search) and the workflow data is not persisted yet cc: @Ramu-kandimalla @anirudh-0
I have raised a ticket with Digit Team to address this issue, we will do lawyer data dump in production it wont be an issue
we can temporarily fix this issue from backend for training purposes if required
Please provide your inputs as well @subhashini-egov @atulgupta2024
@subhashini-egov has already suggested ---
enrich workflow and mdms in advocate service and push to Kafka topic. Remove the enrichment config in indexer. This will work.
as a temporary stop gap, please create a script that calls that calls the advocate/update API and marks the registration as approved, to by pass the Nyay mitra approving the request
@Ramu-kandimalla @manimaarans
Hi @atulgupta2024 We have already uploaded 75% of advocate data in to production system we will complete the rest 25% also once we got the details from high court @suresh12
@subhashini-egov @atulgupta2024 @suresh12 Please consider this request as a high we will be address this item once production is stable
@Ramu-kandimalla I am fine with that. Are the advocates trying to register into the system, those whose data we could not upload or are they new advocates?
If we get new advocates who are trying to register on the site, we will keep hitting this issue.
Hi @rajeshcherukumalli
Tested in UAT
Nyay mitra is receiving all advocate requests in request section.
TEST SCENARIOS
- Parallel filed All Advocate Requests are being received by Nyay-Mitra.
Refer screenshot
Please test and close @Taherabharmal @devarajd94 @ansh-egov
A high number of lawyer registration requests are not reaching NyayMitra. They are unable to re-register as their Bar Id is already stored.