If these problems were solved then we would have all the time to invest in a new GUI. ![]() After a few months when he needs to do the same thing again he has to start again almost from scratch. ![]() The SugarCRM developer documentation is only a high level description of most parts so any developer, in order to achieve something, he has to spend hours, days or weeks studying the code trying to understand how it works. The documentation, specially the develolper documentation should carefully describe all the possibilities that the system offers, including all the flows and the possible variables, the functions that may be used, their parameters, their output, etcs, with a few (complete examples). It is based by examples and the provided examples are very incomplete. Again, SugarCRM hasn’t left anything complete. My last priority would be a “professional” developers’ documentation. Permissions issues have to be resolved for once and for all with automatic php / os scripts that take care for them without any human intervention (if not providing some input to a script to be run at the beginning of the install procedure). I would rather invest in this instead of redesigning for the fourth time the GUI. Too much effort is wasted on a very well known issue because new (even old) users are unaware of the evil lying behind wrong permissions. The forum has hundreds or even thousands of posts due to permissions. There are also other categories of issues, that are also an inheritance from SugarCRM. SalesAgility has invested heavily into these issues but we are still fighting every month with releases that fix pending issues or, much worse, issues that reappear. The issues falling into this category include several parts of the project: from email, to search, enhancing the capabilities of studio, making campaigns better, increasing the number of variables that may be set via the Admin part without having to edit code and much more. In this category there are some bigger issues that have been inherited from SugarCRM as well as other things. ![]() Some other may cause serious problems to a number of companies using SuiteCRM. Some of the issues are little bugs but they are not resolved. Since SuiteCRM started there have been at least three major redesigns of the GUI.Īt the same time there are hundreds of problems that still need to be solved for once and for all. IMHO: I believe that the priority of all development efforts should go elsewhere before tackling a new GUI.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |