Conversation
changelog: Internal, IdV GPO Flow, Read from gpo_verification_pending_at column
| def pending_profile | ||
| profiles.gpo_verification_pending.order(created_at: :desc).first | ||
| gpo_verification_pending_profile | ||
| end |
There was a problem hiding this comment.
should we remove this method? or just alias it?
There was a problem hiding this comment.
I was inbetween removing this method or keeping it. I was thinking of keeping it for if we have any other reasons to have a pending_profile in the future.
| end | ||
|
|
||
| def pending_profile | ||
| profiles.gpo_verification_pending.order(created_at: :desc).first |
There was a problem hiding this comment.
also are we going to backfill this data? do we need to have "double-read" paths to make sure older records get handled correctly here?
There was a problem hiding this comment.
I've already done the backfill. In ROLL-0008
| profile.update!( | ||
| active: false, | ||
| deactivation_reason: :verification_cancelled, | ||
| gpo_verification_pending_at: nil, |
There was a problem hiding this comment.
Do we want to set anything to do with the fraud timestamps here as well? Or are we keeping whatever is there, even if the user cancels?
There was a problem hiding this comment.
That's a good question that i'll find the answer to.
3 participants
🎫 Ticket
LG-9535
🛠 Summary of changes
We now read from the new
gpo_verification_pending_atcolumn for deactivation reasons instead of the old enum.📜 Testing Plan
Provide a checklist of steps to confirm the changes.