Hi everyone,
currently if an Error in CMDBuild occurs everything I see is a Java Traceback of the error with no closer reference to what exactly went wrong, which data was it trying to access or process, how to fix it or what exactly is the issue.
This ties in with the larger issue of inexistant failure-state handling. Should I try to remove a Domain or Class from the Database that still has a connection to something else or a table that still holds data, I can only see an error Message when I try to remove it. A better way to handle such state would be to ask the user if he'd like to remove conflicting Datasets beforehand or if he'd like to cancel his action.
This is not to say that I don't want to see a Java traceback for my errors but they should actually be part of the "Advanced Error Information" as it may help getting a problem solved once a user has to ask the community for help.
Thanks,
Andreas,
Dear Andreas,
we are already aware of what you are saying. We have already planned a complete review of errors management and related notifications. Your suggestion is very important for us.
Best regards.
-- Davide Pavan
Previously Andreas Marschke wrote:
Hi everyone,
currently if an Error in CMDBuild occurs everything I see is a Java Traceback of the error with no closer reference to what exactly went wrong, which data was it trying to access or process, how to fix it or what exactly is the issue.
This ties in with the larger issue of inexistant failure-state handling. Should I try to remove a Domain or Class from the Database that still has a connection to something else or a table that still holds data, I can only see an error Message when I try to remove it. A better way to handle such state would be to ask the user if he'd like to remove conflicting Datasets beforehand or if he'd like to cancel his action.
This is not to say that I don't want to see a Java traceback for my errors but they should actually be part of the "Advanced Error Information" as it may help getting a problem solved once a user has to ask the community for help.
Thanks,
Andreas,
Hey!
Thanks for the heads up. Hope to see it soon.
Cheers,
Andreas Marschke.
Previously Tecnoteca wrote:
Dear Andreas,
we are already aware of what you are saying. We have already planned a complete review of errors management and related notifications. Your suggestion is very important for us.
Best regards.
-- Davide Pavan
Previously Andreas Marschke wrote:
Hi everyone,
currently if an Error in CMDBuild occurs everything I see is a Java Traceback of the error with no closer reference to what exactly went wrong, which data was it trying to access or process, how to fix it or what exactly is the issue.
This ties in with the larger issue of inexistant failure-state handling. Should I try to remove a Domain or Class from the Database that still has a connection to something else or a table that still holds data, I can only see an error Message when I try to remove it. A better way to handle such state would be to ask the user if he'd like to remove conflicting Datasets beforehand or if he'd like to cancel his action.
This is not to say that I don't want to see a Java traceback for my errors but they should actually be part of the "Advanced Error Information" as it may help getting a problem solved once a user has to ask the community for help.
Thanks,
Andreas,