Axiell wants to get our customers to be involved in the roadmaps suggesting ideas for features or functions. Unfortunately we cannot develope each and every function suggested but we want to make sure that you have your say. Add your ideas, and opinions to Axiell's roadmap for Quria, creating new features that yours and other libraries would benefit from. You can also vote for other peoples suggestions as well.
In order to make this portal more useful for all the contributors and for us that work with your ideas, we kindly ask you to write in English.
Please note: If you have an error or a misbehaving function, please contact your local Support for the best possible service. If you are not sure what forum that is the most appropriate for your issue, please choose local support as a first step.
How it works:
The ideas are read and reviewed on a regular basis, by product manager and/or local representative. Your ideas will then be available for others to see, vote on and discuss. We encourage discussions between the idea contributors.
Successful ideas will the be prioritzed within our backlog.
What does the status mean?
Under investigation - often there needs to be a discussion between developers and system specialists before we can say if something can be developed, how and when.
Planned - this suggestion or need will be fufilled in some way in a forseable future.
Future consideration - this status means that we think that it's good idea with no technical obstacles but it's not decided if it can be prioritized and put on the roadmap.
No action - in some cases it is impossible to meet some requirements for technical or other reasons, and sometimes there is another alternative way to solve the need.
Right to reject and close
We reserve the right to reject ideas, and also close issues after 3 months if we don't receive an answer to our follow up questions.
Es gibt bei uns häufig den Fall, dass Kunden verschiedene Sperren haben. Bei den Zahlungserinnerungen ist das dann problematisch, da die Mahnstelle hier mit den Kunden schon zu den Versäumnissen persönlich in Kontakt steht. Wenn dann noch automatisierte Zahlungserinnerungen zugestellt werden, sorgt, dass bei den Kunden zu sehr großer Verwirrung. Wir müssen aufgrund dessen leider komplett auf die Funktion der Zahlungserinnerung verzichten.
Es wäre gut, wenn das Personal vorübergehend die „Teilnahme“ eines Kunden an der Zahlungserinnerung aussetzen könnte (zum Beispiel über ein Häkchen im Benutzerkonto) .
We often have the case that customers have different blocks. This is problematic in the case of payment reminders, as the dunning office is already in personal contact with the customers about the defaults. If automated payment reminders are then sent, this causes a great deal of confusion among customers. Because of this, we unfortunately have to completely abandon the payment reminder function.
It would be good if the staff could temporarily suspend a customer's "participation" in the payment reminder (for example, via a tick in the user account).
Conclusion after meeting:
Our suggestion is that you create a special patron category and create rules that prevents this category to get reminders after the first one. Please evaluate this suggestion and come back if you are not satisfied.
Regards
Magdalena
Hi!
I am not sure that I understand the user case, but we can maybe talk about it when I visit you in September?
Best regards
Magdalena