Sounds good to me then. +1 On Mon, Sep 3, 2018, 4:32 PM Nicolas Malin <nicolas.ma...@nereide.fr> wrote:
> Yeah thanks all for your constructive return :) > > I saw two specific features: commission invoicing and batch payment. As > Sharan spot it, all functional process are present on the accounting > component, I have the feeling that we are all agree on this idea with a > attention to doesn't lost important part possibly hidden on AP/AR. > > Taher, I have two reasons to don't just delete them: > * The code current works and seem to be easy to maintain > * Load in official plugins an example on business screen who simplify > generic screen with potential problem that can be raise by the split :) > > I will try to split it. > Thanks > > Nicolas > > > On 03/09/2018 13:07, Taher Alkhateeb wrote: > > Very interesting thoughts Sharan, Jacopo and everyone. > > > > Thinking about this some more, and given that -- as I understood it -- > > the AP and AR are really nothing more than specialized filtration > > screens of the general purpose screens in the accounting webapp, then > > why not delete them? Are people depending on these screens? Is it > > worth writing and maintaining a plugin for it? > > On Mon, Sep 3, 2018 at 12:27 PM Sharan Foga <sha...@apache.org> wrote: > >> > >> > >> On 2018/09/03 08:11:26, Jacopo Cappellato < > jacopo.cappell...@hotwaxsystems.com> wrote: > >>> On Sat, Sep 1, 2018 at 2:09 PM Nicolas Malin <nicolas.ma...@nereide.fr > > > >>> 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. > >> I thought the batch payment was one of the options for the Payment > Group which is on the main accounting menu so any processing can be done > from there too. > >> > >> Thanks > >> Sharan > >> > >>> > >>>> 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 > >>>> > >>>> > >
