What’s New¶

First of all, the fix when updating answers for an arbitrary participant. Reviewers of an event may show the answers to the additional questions of any participant from within the list of participants. To do so, they should long-tap a given name and choose to show the answers. From there, they may toggle the form to edit mode and then freely update the answers.

Due to a wrong assumption in the lifecycle of the various pages of the app, the second time you would update (or plan to update) the answer to any question except YES/NO toggle buttons, instead of going back to the summary of answers, you would be back to the list of participants.

This problem is now fixed.

Other Changes¶

The mobile application was presenting additional questions in a different way than the website by hiding, under most circumstances, the actual “question” associated to YES/NO answers. In most cases, this was not a problem at all if the answers were properly crafted, as they should to help get an easy-to-understand summary of answers and proper counting of answers. But in some edge cases, hiding the question would instead hinder answering those additional questions at all.

Such a case would be having two “questions” of type YES/NO answers having both similar allowed “answers”:

1. (Question) Accomodation on Friday

   • (Allowed answer) I need a simple room

   • (Allowed answer) I need a double room

2. (Question) Accomodation on Saturday

   • (Allowed answer) I need a simple room

   • (Allowed answer) I need a double room

Although those questions could have been rephrased or changed to multiple-choice questions, we recognized that the phrasing and expectations were legit and we changed in that context the generic title “Additional Questions” which was used for each group of answers to simply really show the actual question text instead.

In addition, a few bugs have been squashed and minor enhancements integrated:

• the description and beneficiary fields when creating or editing a social activity now properly expand themselves automatically;

• the publish button now visually properly reacts when changing state from “disabled” to “enabled”;

• various internal libraries have been upgraded.