Axiell Quria Ideas
Welcome to the Ideas Portal for Quria users!
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.
Welcome to the Ideas Portal for Quria users!
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.
I have been told by my German Axiell colleagues that it is forbidden to send invoices to children. if this also goes for the "hälsningsfras", I do not know. I will check if I can find out.
I will forward your suggestions to the client, and we will see what kind of answer I get.
I understand what the customer is expecting. But I want to know what is the practical problem with the current solution? Is it a real problem that causes trouble or is it just "not what the customer expects"? If the customers suffers badly from not getting the guarantor information in the messages I would recommend them to remove the variable for name and replace it with "Dear Library visitor" or "This is a message from {{LibraryName}}"
//Magdalena
Client is expecting to be able tu use somthing similar to
Dear {{PatronFirstName}} {{PatronLastName}} {{GuarantorStart}} (guarantor for {{Child}}){{GuarantorEnd}}
in notifications.
But since there is no Patron for the Guarantor, the message ends up with Dear (child's name). This was not what the client exepected, the help was not specific enough to explain this.
Help will be changed, but an equivalent for the "Guarantor name (if no connection)" is desirable.
What is the practical problem with the current solution?
Depending on how the guarantor has been entered for the young patron, there are three different options for how notifications will be sent to guarantors:
The young patron is connected to an adult patron that is registered in Quria: notifications will be sent to the name and contact details registered for the guarantor.
A guarantor name has been added: notifications will be sent to the name of the guarantor but to the contact details registered for the young patron.
No guarantor is associated: notifications will be sent to the contact details registered for the young patron, but with the addition “To the guarantor of”.
//Magdalena