LG-10576 Add threatmetrix_session_id to idv_session#9046
Merged
soniaconnolly merged 1 commit intomainfrom Aug 21, 2023
Merged
Conversation
We are moving data from flow_session to idv_session. Now that both the unsupervised and in person Ssn steps are out of the Flow State Machine, we can move threatmetrix_session_id to idv_session. This PR adds it to idv_session, and a followup PR for the next deploy will remove it from flow_session. [skip changelog]
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
LG-10576
🛠 Summary of changes
We are moving data from flow_session to idv_session. Now that both the unsupervised and in person Ssn steps are out of the Flow State Machine, we can move threatmetrix_session_id to idv_session. This PR adds it to idv_session, and a followup PR for the next deploy will remove it from flow_session.
📜 Testing Plan
Provide a checklist of steps to confirm the changes.
lexisnexis_threatmetrix_mock_enabled: truein local application.yml and restart server