Hi All I really like the idea of making AR and AP plugins. I’ve taken a quick look and from what I can see all of the functionality in them are just specialised filters of what is already available in the accounting menu.
It looks like our accounting module was originally created with all possible accounting functions combined into one module so we have GL, AR, AP etc already all included as part of accounting. Many users are used to having an accounting module with the accounting functions broken down into specialist submodules and if people can’t see or find them easily they don’t think they exist so I can understand why the AR and AP applications were added. That being said – why keep this type of duplication in our framework? I think this is something that could be optional and so more useful as a plugin. Having different implementations of base functionality is exactly where the plugins could help us give users what they are looking. Thanks Sharan On 2018/09/03 08:11:26, Jacopo Cappellato <[email protected]> wrote: > On Sat, Sep 1, 2018 at 2:09 PM Nicolas Malin <[email protected]> > wrote: > > > Hello, > > > > After analyze the webapp accounting AR and accounting AP, I didn't see > > any logic to keep them on the functional framework. The main webapp is > > accounting, AP/AR are a business orientation that we can load at demand > > through plugins. > > > > Your opinion ? > > > > As far as I remember, the AP/AR web applications were created as a > specialized versions of the user interfaces for some business processes > (account receivables and account payables related tasks) that were already > available in the more general "accounting" web application. I like the idea > to move them to plugins but, as mentioned by Taher, we should also verify > if there are specific features that are available only in the AP/AR version > and not in the "accounting" application: if we find some, then we should > migrate the basic artifacts to the main "accounting" app and then move the > specialized screens to plugins. I think such cases will be rare but one > possible candidate is the "batch payment" functionality of the AR app. > > > > > > PS: In the same idea we can move on separate plugin all thirdparty > > accounting element to slimdown the accounting component and must harness > > the plugin system :) > > > > +1 > > Jacopo > > > > > > Nicolas > > > > >
