This is an honest question. What was the logic behind a comments mechanism in the various pages in ERPNext? I understand that adding some additional context is always helpful but I just can’t think why doing it with comments would be helpful.
Keep in mind any organisation is going to have a mix of people with different skills, knowledge and insights etc. So how do we prevent a junior person from adding irrelevant comments? I just think it’s the kind of feature that not everyone would want to use but there’s not an easy way (without custom scripts) to disable it globally.
A bit of freedom allows more transparency, giving insight into the social behavior of the commentators, enabling useful feedback, without which it’s much more difficult to change and advance.
You can turn off the whole timeline, including comments, for individual Users by editing their User document. The field is called timeline, and it’s in the “Settings” tab under “Form Settings”.
Thanks that’s very helpful but appears to have the drawback of not being able to see the activity history. I would open a feature request but I’m not sure if it’ll get any attention. Good to see there are at least a few people viewing this thread so perhaps over time it will gain traction at which point it might be worth adding it to github as a feature request.
It sounds like you have some very specific parameters here. You’ve said you’re trying to avoid custom scripts, but custom scripts really are the easy solution here. What you’re describing can be done with 2-3 lines of python in a validate hook.
That’s part of the design. Frappe has always been framework-first, which means covering some common use-cases but focusing on giving users the ability to customize workflows to their own needs.
@peterg I genuinely appreciate the advice and guidance thank you very much. A script is most likely how I’ll end up solving this problem however I just don’t think a feature like this should require custom scripts to disable globally. I was wondering if anyone else felt the same way.
Happy to elaborate on my thinking if anyone would like more context or insight.
however I just don’t think a feature like this should require custom scripts to disable globally
One person’s undesired feature is another’s mandatory, cannot-live-without feature.
By design, Frappe Framework (and ERPNext too) is a generalist. It provides a wide variety of tools and gizmos. The target audience is both everyone, and no one.
If we asked the forum members for which feature(s) they feel are unnecessary and get in the way, and should have the ability to Enable/Disable? We’d get about 10,000 answers. Adding many hundreds (if not more) configurable buttons. Making the code incredibly difficult, if not impossible, to manage.
Instead, the framework gives us scripts, so we can each tailor the application to our own needs.
