| Anchor | ||||
|---|---|---|---|---|
|
The following guide is adapted from ASIMUT Support’s article on what’s new in ASIMUT version 3.4.
This new version Version 3.4 is already in placelive in our environment.
Some article content has been removed from this guide.
For the full article content see the original release notes linked to below.
The article guide has the following sections:
COMMON INTERFACE (AVAILABLE TO STUDENTS AND MOST STAFF)
- Common interface: User experience improvements
- Common interface: Bug fixes
ADVANCED INTERFACE (AVAILABLE TO POWER USERS AND ADMIN STAFF ONLY)
...
Booking rules
- Advanced interface:
...
User experience improvements
- Advanced interface:
...
Event request functionality
- Advanced interface: Bug fixes
RELEASE NOTES
- Original v3.4 release notes
Common interface
The common interface is available to students and most staff.
It’s also available to Power Users and Administrators.
...
In-person UX testing with music academy students, making sure that the zooming and scrolling behavior is smooth enough to please those who need it the most.
"Onboarding" feature, which makes students and teachers aware of the new functionality.
The onboarding notification will fly up the screen on a touch device when the user opens a location chart.
The notification will reappear until the user clicks the button "Ok, do not show again"
...
Quick-start the booking process
...
Whether a user is allowed to book a location or not depends on many factors. Which category they are allowed to book in can be one of them, especially if you make use of the new booking rule option (explained in the section "Restrict in which categories a location can be booked").
In the past, when they could choose between different booking categories, and they clicked on the one they were not allowed to use in this situation, it meant going back and starting anew. There are many clicks to be saved here.
Indicators show them already in the category menu whether they can proceed with a booking. It will give them a stop sign if they cannot use the category in the location at all, and it will give them a warning sign if they would need to adjust some parameters before saving.
...
Menu improvements
Students and teachers will see slight changes in their menus for clearer naming.
...
At the same time, the logged-in user's name does not appear in the menu anymore.
...
...
Here a few examples of how other quotas will display:
weekly quota
daily quota
no quota set
...
My recommended locations
Another change in the name of clearer communication is the renaming of "Please book primarily here" to "My recommended locations", which appears when a user is encouraged to book certain locations as part of
the booking rules.
...
...
| Anchor | ||||
|---|---|---|---|---|
|
Bug fixes
...
When a user wanted to book an event that would start close to midnight, they might have experienced that they could not save the booking. This will not be an issue anymore.
Advanced interface
The advanced interface is available to Power Users and Administrators only.
...
ASIMUT offers a wide range of options for setting up the framework in which you can allow your students and teachers to book locations on their own. This self-service reduces your workload and empowers your users. The new feature we present below can simultaneously reduce complexity and increase flexibility in setting up booking rules.
| Anchor | ||||
|---|---|---|---|---|
|
Restrict in which categories a location can be booked
Locations should be booked for the right purpose. The purpose of a booking is signaled by the booking's category. So under specific circumstances, you might want to implement a rule like "Bookings in location 605 must be bookings for groups, not individuals".
...
You will of course see all the selected categories as checked when opening the category selector again.
| Anchor | ||||
|---|---|---|---|---|
|
User experience improvements
...
The keyboard shortcuts work of course regardless of whether the buttons show.
| Anchor | ||||
|---|---|---|---|---|
|
Event request functionality
...
For more information on how the feature works and how you can implement it, please see the article "Event requests".
| Anchor | ||||
|---|---|---|---|---|
|
Bug fixes
...
When you delete a category, you are asked which other category its events should be moved to. We use this information now to replace the default category of Advanced Users who happened to have the category you delete as their default category for bookings in the Advanced Interface.
| Anchor | ||||
|---|---|---|---|---|
|
The original release notes for v3.4 can be found here
| View file | ||
|---|---|---|
|