Jameson/CT-1659

[Jameson13B]

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

Changes

• Added new InstitutionDisabled view/step that renders when institution.is_disabled_by_client is true.

Testing instructions

*You will need to block an institution for your test client in Batcave.

• Load a member that is connected to an institution with is_disabled_by_client.
  • Ensure the new view renders and functions as expected.
• Load Connect with an institution guid/code with is_disabled_by_client.
  • Ensure the new view renders and functions as expected.
• Run all tests available.

[mwclemy]

This doesn’t seem fully ready for testing yet. The institution search request is the only one returning the is_disabled_by_client flag as true. When selecting an institution that should have the flag set to true, it flips to false for some reason. I’d assume the endpoints that request a specific institution by guid aren’t populating the flag correctly yet.

[mwclemy]

One thing I noticed: When you click on an already connected institution with the is_disabled_by_client flag set to true from the list of existing connections in verification, it throws this error:

I wonder if this will be resolved once the flag is populated on the member and we’re redirecting the user to the InstitutionDisabled screen when the flag is true, but I wanted to flag it as something we’ll need to make sure works correctly.

[codingLogan]

In my companion MR for the Connections widget, I added some hard-coded values that should limit this new blocked experience to the specific Chase Bank members that we're concerned about. While it is gross... this will make it less likely to disrupt more users than we intend to, like what happened to Regions recently... They block themselves, and their existing members might be impacted with a message they shouldn't need to see 😓 .

https://gitlab.com/mxtechnologies/mx/connect-widget/-/blob/7dcc8bd37089841c8efeb24b8d8292f4e3a41a40/src/connections/institutionBlocks/institutionBlocks.ts

In the near future we'll need to make this more dynamic so the backend provides us a message and a list of what institutions are blocked. Once we have that fully fleshed out, we can take out the hard-coding guid and name. (I'm not sure when this will be, or if it is even being discussed, but this means we're limited to only being worried about Chase Bank for existing members)

[emilysallstrom]

Nice work!

[github-actions]

🎉 This PR is included in version 2.3.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀