LG-16305: Update Actual Proofing Rate in DIVR#12248
Merged
Conversation
The actual proofing rate reported in the DIVR is calculated as the number of successfully verified users divided by the number of users who submit images for doc auth. Previously, this only included users who submit images to TrueID but now that we have started using Socure, we need to include Socure submissions as well. changelog: Internal, Reporting, Include Socure submissions in actual proofing rate.
shanechesnutt-ft
approved these changes
Jun 11, 2025
Contributor
There was a problem hiding this comment.
Looks good to me!! @AShukla-GSA and I ran through the test plan. Nice work! 👍🏻
jmdembe
pushed a commit
that referenced
this pull request
Jun 12, 2025
The actual proofing rate reported in the DIVR is calculated as the number of successfully verified users divided by the number of users who submit images for doc auth. Previously, this only included users who submit images to TrueID but now that we have started using Socure, we need to include Socure submissions as well. changelog: Internal, Reporting, Include Socure submissions in actual proofing rate.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🎫 Ticket
Link to the relevant ticket:
LG-16305
🛠 Summary of changes
The actual proofing rate reported in the DIVR is calculated as the number of successfully verified users divided by the number of users who submit images for doc auth. Previously, this only included users who submit images to TrueID but now that we have started using Socure, we need to include Socure submissions as well.
📜 Testing Plan
Provide a checklist of steps to confirm the changes.
lib/reporting/identity_verification_report.rbinto the rails console to update the report code.Sample output: