EN | FR | DE | IT | NL
previous | next | index
search

Version 11.0.0

Release Date

July, 20th 2024

Compatibility

Android 5.1 (Lollipop), Android 6 (Marshmallow), Android 7 and 7.1 (Nougat), Android 8 and 8.1 (Oreo), Android 9.0 (Pie), Android 10.0, Android 11.0 (R), Android 12.0 (S), Android 13.0 (Tiramisu), Android 14.0 (Upside Down Cake)

The handling of events and registrations has been significantly improved in this release. We have added a new feature to mark questions as “required” and have enhanced the switch used to answer YES/NO questions. We have also fixed a few bugs and made minor enhancements.

What’s New

We have added a new feature to mark questions as “required” and have enhanced the switch used to answer YES/NO questions.

In addition, club administrators may now create so-called “closed events”, which are only visible to members explicitly invited to the event. This feature is particularly useful for preparation meetings or other events that are not supposed to be visible to all members of the club (or some higher level) but should count towards the member’s participation in the club’s activities.

Finally, the list of awards for a member has been slightly enhanced to be more appealing to the eye.

Events

We have refined the YES/NO switch since our last improvements in version 6.3.0.

In fact, the switch supports an intermediate state for making it clear that the user has not yet made a decision:

Additional questions (before)

But over the years (version 6.3 dates back from end of 2019), we have received feedback that the switch was not intuitive enough for some members and that they did not really grasp the concept of toggling between “on” and “off” to answer “yes” or “no” to a given question.

We thought about it and came up with a slightly enhanced version of the switch to better depict the concept of answering “yes” or “no” to a question by borrowing the same visual feedback when attending (or not) an event in the list of upcoming activities:

Additional questions (after)

As you see, the orange background is now slightly darker to be more pleasing to the eye and to match the “orange” we use in other parts of the app. And the “on” and “off” states are now visually reinforced by a green/red mark on the left.

We feel that this change shall make it easier for everyone, including those who never had any issue with the switch, to understand the concept behind it without cluttering the user interface with additional text or icons.

Required Answer

We discussed above the enhancement with the switch, which is used with questions that require a YES/NO answer and we correctly mark the question as “answered” when the user has made an explicit decision.

But many organizers complained that they had to deal with members who did not answer other questions, although they considered them as mandatory. Indeed, until today, we only considered the YES/NO questions as mandatory, but not the others.

We have now added a new feature to mark a question as “required” when the organizer considers it as mandatory. The user will then be visually requested to answer the question to change the background color of the question from orange to “normal” (white/gray depending on the theme):

Required answers for new types of questions

An answer is now mandatory if:

  • the question is a YES/NO question (aka “checkbox”);

  • the question is a multiple choice question (aka “radio button”);

  • the question is either a single line of text or a numeric field and is marked as “required” by the organizer.

Note

If a numeric answer is required, the user will be requested to enter a number that is greater than zero. Organizers should thus avoid marking a numeric field as “required” if they are not sure that the answer will be greater than zero.

It is important to remember that members will be able to confirm their participation in an event without having answered all the required questions.

However, the application will display various warning messages and visual marks to indicate that certain questions have not yet been answered. We see this as a compromise between the organizer’s desire to have all the questions answered and the user’s desire to confirm their participation in an event without being obliged to answer all the questions at once, particularly when there are a large number of questions (such as for a National Convention), and the user does not have all the information needed to answer them immediately, or needs to consult someone else before answering them.

Sending a Message

We introduced a way to send a message to all participants of an event in Version 10.3.0. This feature has been enhanced in this release to allow the organizer to send a message to members who declined the invitation, as well as to those who have not yet answered the invitation.

Note

The event organisers (a.k.a. “reviewers”) may send a message to all participants. Sending to non-participants and those who have not yet answered is only possible if the event is targeting up to 200 participants.

This business logic is in place to avoid spamming all members with messages that are not relevant to them and would be considered as intrusive. It may change anytime in the future.

Creating Closed Events (Invitation Only)

Since version 8.4.0, the CLBM may create events from within the mobile application.

With this release, we have added a new feature to create “closed events”, which are only visible to members explicitly invited to the event. This feature is particularly useful for preparation meetings or other events that are not supposed to be visible to all members of the club (or some higher level) but should count towards the member’s participation in the club’s activities.

In fact, in order to be able (in the future) to compute some statistics about the participation of members in the club’s activities, it is important that all events are recorded in the system, even if they are not visible to all members.

When creating a new event, the organizer may now choose a special target audience “Closed event (invitation only)”:

Special target audience for closed events

Needless to say that when creating a closed event, other target audiences cannot be selected, and the organizer must then invite the members to the event manually.

Cancelling an Invitation

You know that you may invite other members or external guests to an event. But what if you invited someone by mistake, or for any reason you want to cancel the invitation?

You may now cancel an invitation by long-tapping the participant in the list of participants and selecting “Delete invitation”. The participant will then be removed from the list of participants and since canceling an invitation is no small thing, an email will be sent to inform them about the cancellation.

Profile Page

Starting with version 10.2.0, we have introduced a new design for the list of awards, separating Melvin Jones from all other awards.

This did not affect many members, but for those who have received many awards, and particularly the same award multiple times, the list of awards could become quite long and difficult to read.

Those “other” awards are now grouped by award type, and each award type shows the list of years when the award was received.

On the left side, you see the list of awards before the change, and on the right side, you see the list of awards after the change:

List of awards grouped by award type

This makes the list of awards much more readable and more appealing to the eye while conveying the same information as before.

Lions History

The Lions History of a member now features the corresponding motto, if any:

Motto displayed in the Lions History

Hint

Please note that the motto was already displayed when you long tapped a given function, such as “Club President”, in a committee and selected “Show list of…” (introduced back in version 8.3.0).

Other Changes

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

  • showing an event will warn you if it is booked out;

  • it could happen that an event was marked as not completely answered in the list of upcoming activities, although all questions had been answered. This should no longer happen;

  • it was found that the application would not display pending operations in the dashboard (such as confirming the modification of one’s email address) if there were no SMS messages to display as well (which is in fact most of the time the case). This problem has now been resolved;

  • the API now returns up to 200 potential participants without answer (80 was the previous limit);

  • experimental support for “Branch Clubs” has been added;

  • various internal libraries have been upgraded.

Note

Using iOS? Please see corresponding release notes.

Documentation created using Sphinx 4.3.2 and integrated in TYPO3 with restdoc.