Jameson/CT-1815

[Jameson13B]

https://mxcom.atlassian.net/browse/CT-1815

Changes

• Added the Mobile Back Button to the Connect widget for integration on VerifyExistingMember and Search steps.

Testing instructions

*This change is high impact. Manually test this throughly with a variety of settings/conditions.

• Test with mobile button on/off, agg and verification mode, etc.

With mobile back button

Without mobile back button

[platypus801]

looks good!

[mwclemy]

Is the requirement to show the back button only on the VerifyExistingMember and Search steps when show_back_button is true? I’m seeing it appear on other screens, like Connecting and MFA, where it normally shouldn’t.

[platypus801]

yes it only needs to be available on the those first screens so the user can go back a step into the mobile app where they entered the flow from; i'm not super we ever pass in institutionID or memberID, but theoretically those should have back buttons that go to the previous mobile screen (mobile will control that)

[Jameson13B]

I didn't consider the returning user flow where we start mid widget flow. Thanks a ton for catching that, I have it all updated to be specific to our first step of SEARCH or VERIFY_EXISTING_MEMBER. Ready for another review.

[codingLogan]

Testing Connect with back button enabled

• ✅ Agg mode, back button renders and sends message, before and after connection attempts
• Agg mode with a MBR guid
  • ✅ Back immediately
  • ❔ Back after connection attempt, if the user attempts and enters incorrect credentials the locatio history clears, and back goes to the search screen. (not sure if we want to handle this right now, we could improve this in the future if needed)
  • ✅ Back after successful connection
• Agg mode with an institution guid
  • ✅ Back immediately
  • ❔ Back after connection attempt, if the user attempts and enters incorrect credentials the locatio history clears, and back goes to the search screen. (not sure if we want to handle this right now, we could improve this in the future if needed)
  • ✅ Back after successful connection
• ✅ Verify mode, back button renders and sends message. If the user moves to the Search page, Search then has the new back button and messaged (rather than the existing member screen)
• Verify mode with a MBR guid
  • ✅ Back immediately
  • ❓ Back after connection attempt
  • ✅ Back after successful connection
• Verify mode with an institution guid
  • ✅ Back immediately
  • ❔ Back after connection attempt, if the user attempts and enters incorrect credentials the locatio history clears, and back goes to the search screen. (not sure if we want to handle this right now, we could improve this in the future if needed)
  • ✅ Back after successful connection

[github-actions]

🎉 This PR is included in version 2.14.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀