Gordon ThomsonOct 06 — 2 mins read
When we start a development cycle, we set out with a basic goal: to make things better for our customers. To do this, we take an approach that considers the application as a whole and not just the feature or improvement we’re working on.
To help us achieve this, we keep a few things in mind as we approach the planning and execution of the work, some of which include:
It was during a recent planning session we discovered an issue with the way dropdown options were being handled. I’ll outline the problem, the solution and the outcome below. Suffice to say, SUMAC® is better off after our investigations!
For a small number of members, the details stored in their profiles did not reflect the current state of the form: that is, dropdown fields in the signup form had been modified and the member data hadn’t, creating a discrepancy. This would result in the validation being triggered when member data was being updated, as shown below:
The solution required us to gather enough information to ensure that any changes we were going to make wouldn’t cause any further issues. Once we were satisfied, we implemented a “middleman” which would be triggered by any updates to the signup form and then head off to ensure the member data reflected the changes.
For all members, any changes to the signup form will correctly show on their member profiles.