Open piers-sinclair opened 3 years ago
5. Was this error visible to developers? E.g. with raygun or app insights?
Done - As per my conversation with Lu, these exceptions are not logged to either ray gun or app insights.
Added - 6. Update SSW.People and/or SSW.Website to log errors when they occur.
Just an idea - maybe you could consider making a flow with an HTTP Trigger to post the form results to. The flow can handle putting it into CRM asynchronously and any other logic required. Any errors will be logged and easy to fix/replay. Would take about 10 minutes to set up.
Some updated information. The problematic code is shown in the below image:
Figure: The API call that fails when the user tries to book a meeting.
Additionally, there is a field which should be populated but isn't called Lead Source Web Page (SSW Website). This field is new and has been added to the website but not to SSW.People
Figure: The problematic field
Finally, The location field should be mandatory but is not.
Hi Team,
The form has been fixed but a bigger issue still remains.
Hey @wicksipedia
@wicksipedia @adamcogan @bradystroud @christianmorfordwaitessw Hi Team,
UX when booking initial meetings should be improved, this may be an issue with the SSW.Website instead of SSW.People. However, we are not sure.
Figure: The issue which prompted this review of the UX.