You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to catch referrals that are already appointments. This could happen on the FE or the BE. If we do it on the FE, we should add a step to search for a matching referralId in the upcoming appointments payload. If it happens on the BE, vets-api should send a response that includes the existing appointment ID.
Regardless of who does this work, FE will need to redirect the user to either the appointment detail page or the complete page. Maybe we need some kind of a "you already did this" alert. Work with UX on the details for this scenario.
The text was updated successfully, but these errors were encountered:
We need to catch referrals that are already appointments. This could happen on the FE or the BE. If we do it on the FE, we should add a step to search for a matching
referralId
in the upcoming appointments payload. If it happens on the BE, vets-api should send a response that includes the existing appointment ID.Regardless of who does this work, FE will need to redirect the user to either the appointment detail page or the complete page. Maybe we need some kind of a "you already did this" alert. Work with UX on the details for this scenario.
The text was updated successfully, but these errors were encountered: