When an operator executes the review-pass or review-reject scripts, they log an analytics event. This PR updates those analytics events to be attributed to the SP that was associated with the initial profile creation.
📜 Testing Plan
Provide a checklist of steps to confirm the changes.
[ ] Start from an SP and go through IdV. Intend to commit fraud so that you get caught and put into the fraud review queue.
[ ] Verify that the "Fraud: Profile review rejected" event logged includes the properties.service_provider key, set to the SP you were originally going through IdV for.
[ ] Repeat this process, but this time approve your fraud review request: bin/action-account review-pass $(bin/rails runner 'puts User.last.uuid'
[ ] Verify that the "Fraud: Profile review passed" event logged includes the properties.service_provider key, set to the SP you were originally going through IdV for.
🎫 Ticket
Link to the relevant ticket: LG-14673
🛠 Summary of changes
When an operator executes the
review-passorreview-rejectscripts, they log an analytics event. This PR updates those analytics events to be attributed to the SP that was associated with the initial profile creation.📜 Testing Plan
Provide a checklist of steps to confirm the changes.
bin/action-account review-reject $(bin/rails runner 'puts User.last.uuid')properties.service_providerkey, set to the SP you were originally going through IdV for.bin/action-account review-pass $(bin/rails runner 'puts User.last.uuid'properties.service_providerkey, set to the SP you were originally going through IdV for.