@enlightX > Speaking about entries encoding, the most advanced tool in SAP, Dynamics Nav, > Sage and other famous softwares is "Recurring Entries". > OpenERP already provides this feature, but it's still basic and maybe useles. > With recurring entries, accountants manage about the 80% of their job, at > least in small and mid-sized company. >
This one of the features we miss a lot! The most known accounting software on Spain, ContaPlus (known just because it was one of the first, so it is used to train people on the universities) have had this feature for a long time, so every other Spanish accounting software has copied it... They even usually come with lots of templates for the common operations: want to register a leasing? you have a template for it! just fill up the asked variables and its done! (here is an example in spanish: http://www.ciberconta.unizar.es/leccion/contaplus/predefinidos.htm) Most companies have external accountants that just prepare the recurring entries to hide all the complexity, so the company workers are able to enter the data with a few clics and without knowing anything about accounts. That means that the accountant only needs to visit the company once per fiscal period: just to check out the entries done by the users, and enter any complex entry that was not covered by the templates. > We at Domsense started the development of Report OpenOffice last year (now > maintained by KNDATI guys + other contributors. PS: Thanks!) just because we > spent more than 2 days to create a complex invoice template for a customer. > Really too much. Similiary, we at Pexego had to develop a custom "OpenOffice Reports" module (pxgo_openoffice_reports on the extra-addons) because we found the same problems when working with RML (by the way, we have some extra features that could be merged into report_openoffice some day): - As Nhomar says, OpenERP's RML is not complete, missing some core features. For example in OpenERP's RML is not possible to show the invoice totals in a fixed position on the footer because the PTO (please-turn-over) feature of RML is missing (see bug https://bugs.launchpad.net/openobject-server/+bug/509266 BTW, a patch has been available for a year). - RML is not user intuitive, you need a developer to do even small changes: -> The user wants to put some string in bold red? => it requires at least some HTML knowledge to understand that #FF0000 is a color! -> Want to make the table borders ticker? => have any of you messed with blockTableStyle/lineStyle? It looks like a battleship game replay! -> To do a conditional structure (the every day "if then else") you have to mess with an unintuitive "removeParentNode", how many final users do even know what a node is? So, a final user won't be able to create easily a "Christmas letter for all our customers" with RML, but with OpenOffice (+Relatorio) it is possible! The developer just has to explain to them how to use some basic placeholders (like ${partner.name} being the name of the partner) the first time, then the final users will be able to edit the letter every year by themselves using colorful fonts, images or whatever they like... > In most cases, default account reports still end in a timeout error. > ... > Another topic directly related: PrintJob (Thanks to Pegueroles SCP & NaN). > Great addon! it saved our life a lot of times! > OpenERP has always had a problem a big problem with the way the server and clients comunicate: it is completly synchronous! Hasn't "AJAX" (Asynchronous JavaScript And XML) shown us the way to go? With operations that take a while, not just reports, but wizards too the OpenERP clients "just wait" for the server to reply, and if it takes too much, they timeout and show an error. That is crazy! the user will usually try again, and again stressing the server even more (the first report might still be running). Why don't we have "background tasks" or a callback-like feature on OpenObject yet? The most common needs would be so easy to cover (just add to wizard forms the option to refresh themselves every X seconds and that's enought!*) that I think it is stupid that we are still missing them! Come on, every desktop program is able to show a progress bar when it is doing long number-crunching operations! * On the Spanish localization we implemented several wizards like this: The main thread (the one launched by the client) runs a wizard action of type "choice". The first time it is called, it spawns a background task to do the job. If the task takes more than 20 seconds the choice action returns a "Job in progress (X%). Continue waiting? Work in Background? Cancel?" view so the user is informed of the progress. This way this wizards never time-out. But the user still has to clic the "continue waiting" for the choice action to be called again cause there is no auto-refresh option for the wizard forms! ------------------------ Borja López Soilán Pexego - www.pexego.es -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=61208#61208 -------------------- m2f --------------------
_______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
