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.
Cancelled orders cannot be removed. The menu is inactive. This means that the corresponding budgets in the acquisition cannot be adjusted either. The answer from support to the problem was that the cancellation will be retained if there is still a question about it at some point.
Conversely, however, a cancelled order cannot be reactivated.
stornierte Bestellungen lassen sich nicht entfernen. Das Menu inaktiv. das zieht nach sich, das auch die entsprechenden Budgets in der Erwerbung nicht bereinigt werden können. Die Antwort vom Support auf das Problem war, dass die Stornierung erhalten bleibt, falls es dazu noch eine Frage gibt, irgendwann.
im Umkehrschluss kann aber auch eine stornierte Bestellung nicht wieder aktiviert werden
Hi,
I see, thank you for the explanation. I will discuss it with the developers and try to find the best and less risky solution for keeping a good order in the budgets.
Regards
Magdalena
The main point here is, that we need to be able to delete „old“ budgets, which are not in use anymore. As long as those „old“ budgets are connected with a cancelled or finished order, this is currently not possible.
The budet overview within the Quria configuration will end up very messy if we are not able to delete those old/not needed ones.
Additionally we need to be able to delete cancelled orders as well as to delete finished orders.
This would be needed analogous to functionality „cancel order lines“ but just for already cancelled orders and connected with a new role within acquisition, like „Delete cancelled order lines“ or add this functionality within role „Edit/cancel/delete order lines“.
This is needed to be able to delete budgets, which have for example been used 3 years ago but are now obsolete, and to keep acquisition data a little more clearyly arranged.
Cancelled orders are automatically withdrawn in the budget. What do you mean that you need to adjust?
Are there any practical problems with keeping cancelled orders?
Best regards
Magdalena