Skip to Content

Contributors

  • Re: Odoo 14 bank statement reconciliation
    Hi Jordi,


    Our accountant freakouts everytime this kind of thing happens. For our accounting standard, journal entries must not change once posted.
    I was learning from Odoo that, many countries don't take it seriously like we do. But this just make Odoo looks bad for auditors.

    On Thu, Nov 25, 2021 at 2:16 PM Jordi Ballester Alomar <jordi.ballester@forgeflow.com> wrote:
    Hello,

    I hope this email finds you well. Today I was stuck with the way Odoo handles the bank statement reconciliation in v14 and saw Frederic's tweet from a year ago: https://twitter.com/Frederic_C2C/status/1313521444106706944

    What really stuck me is not the use of a suspense account during the bank reconciliation, but the fact that once the bank statement line journal entry has been posted to a suspense account, the posted journal entry is modified once you have matched that statement line with an invoice. Changing a posted journal entry??

    What do you think?

    --
    Jordi Ballester Alomar 
    CEO & Founder  
    Spain: (+34) 629 53 07 07 | USA: (+1) 646 980 46 59 | Denmark: (+45) 78 78 21 89


          

    The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future.

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Kitti Upariphutthiphong - 02:45 - 17 Dec 2021
  • Re: Move purchase_request* and purchase_work_acceptance*
    +1 to split purchase_workflow.



    Le mar. 14 déc. 2021 à 11:52, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
    +1, although maybe others can be more useful, like OCA/tier-validation, that groups better other functional areas.

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --
    Raphaël Reverdy
    Mobile +33 6 38 02 03 93
    Fixe +33 4 82 53 84 60

    by Raphaël Reverdy - 09:10 - 17 Dec 2021
  • Does OCA's runbot use OCB ?
    Title says all. Can someone answer this question to complete the OCB faq 
    on the wiki ?
    https://github.com/OCA/OCB/wiki/FAQ
    
    
    -- 
    Librement,
    Xavier Brochard (zeroheure) xavier@alternatif.org
    La liberté est à l'homme ce que les ailes sont à l'oiseau (Jean-Pierre 
    Rosnay)
    

    by xavier - 10:20 - 15 Dec 2021
  • Re: stock_inventory repository
    The way they refactor it can work out of the box.

    But, I suspect from that version, a bunch of modules will come. As Lois said, a way to group things to do (not simply through the quant tree), ...

    Ok, let's wait for now first contribution and decide after.

    On Tue, Dec 14, 2021 at 4:46 PM Cyril VINH-TUNG <cyril@invitu.com> wrote:
    Dear all

    Odoo did a video that explains inventory adjustments in v15

    https://youtu.be/GP3bmOrYnTg

    -- 

    Best Regards/Cordialement
    --------------------------------
    Cyril VINH-TUNG
    INVITU Computer & Network Engineering
    BP 32 - 98713 Papeete - French Polynesia
    Tél: +689 40 46 11 99 contact@invitu.com www.invitu.com

    P Please consider the environment before printing this e-mail!

       

    Le mar. 14 déc. 2021 à 03:06, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
    Indeed checking quickly in runbot, I see no way of telling "I want to make an inventory of this location (and children)" now, so a module that restores this concept (through a model called `stock.inventory` or whatever), and then present the stock.quant view filtered by that criteria may be enough, and mount the rest over this base.

    Regards.

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --

    Denis Roussel
    Software Engineer
    T    : +32 2 888 31 49
    M : +32 472 22 00 57


    Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
    Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
    Zone industrielle 22 | L-8287 Kehlen | Luxembourg

    by Denis Roussel - 05:11 - 14 Dec 2021
  • Re: stock_inventory repository
    Dear all

    Odoo did a video that explains inventory adjustments in v15

    https://youtu.be/GP3bmOrYnTg

    -- 

    Best Regards/Cordialement
    --------------------------------
    Cyril VINH-TUNG
    INVITU Computer & Network Engineering
    BP 32 - 98713 Papeete - French Polynesia
    Tél: +689 40 46 11 99 contact@invitu.com www.invitu.com

    P Please consider the environment before printing this e-mail!

       

    Le mar. 14 déc. 2021 à 03:06, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
    Indeed checking quickly in runbot, I see no way of telling "I want to make an inventory of this location (and children)" now, so a module that restores this concept (through a model called `stock.inventory` or whatever), and then present the stock.quant view filtered by that criteria may be enough, and mount the rest over this base.

    Regards.

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Cyril VINH-TUNG - 04:46 - 14 Dec 2021
  • Re: stock_inventory repository
    I agree with you both, I also thought that the new behavior is not usable for large warehouses (cannot really filter, assign work, keep record of operators work...). Also using stock.move.line as history of past inventories seems an over simplification.

    For reference, the change was done here: https://github.com/odoo/odoo/pull/68409. They state that they include cycle counts, bulk assignment... but I could not do that on a quick test. I will have a look in detail in the next days, but it seems that maintaining stock.inventory in the OCA is a good idea.

    Regards,

    El mar, 14 dic 2021 a las 14:06, Pedro M. Baeza (Tecnativa) (<pedro.baeza@tecnativa.com>) escribió:
    Indeed checking quickly in runbot, I see no way of telling "I want to make an inventory of this location (and children)" now, so a module that restores this concept (through a model called `stock.inventory` or whatever), and then present the stock.quant view filtered by that criteria may be enough, and mount the rest over this base.

    Regards.

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --
    Lois Rilo Antelo
    Odoo consultant at ForgeFlow S.L.

    by Lois Rilo Antelo - 02:41 - 14 Dec 2021
  • Re: stock_inventory repository
    Indeed checking quickly in runbot, I see no way of telling "I want to make an inventory of this location (and children)" now, so a module that restores this concept (through a model called `stock.inventory` or whatever), and then present the stock.quant view filtered by that criteria may be enough, and mount the rest over this base.

    Regards.

    by Pedro M. Baeza - 02:06 - 14 Dec 2021
  • Re: stock_inventory repository
    I think about your cycle_count module(s), inventory_preparation_* modules that are mostly used (as migrated to every version) and to avoid breaking changes (as it is a drawback when you are in a migration process).

    @Pedro This has been triggered by Sylvain Legal there https://github.com/OCA/stock-logistics-warehouse/issues/1328 and seems to be legit.

    On Tue, Dec 14, 2021 at 1:42 PM Lois Rilo Antelo <lois.rilo@forgeflow.com> wrote:
    Hi,

    I have seen that change but still haven't analyzed what should be the way to go... are you suggesting that OCA keeps the stock.inventory model and migrate all those modules on top of that?

    Regards,

    El mar, 14 dic 2021 a las 11:16, Francesco Apruzzese (<cescoap@gmail.com>) escribió:
    +1

    Il giorno mar 14 dic 2021 alle ore 11:12 Roussel, Denis <denis.roussel@acsone.eu> ha scritto:
    Hi all,

    As Odoo removed inventory model in v15 and as there are a bunch of modules for inventory in stock-logistics-warehouse repo, I request the creation of stock-inventory repository.


    Thanks

    --

    Denis Roussel
    Software Engineer
    T    : +32 2 888 31 49
    M : +32 472 22 00 57


    Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
    Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
    Zone industrielle 22 | L-8287 Kehlen | Luxembourg

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --

    Francesco Apruzzese

    Profilo professionale: http://it.linkedin.com/in/francescoapruzzese

    Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
    This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.

    Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente.

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --
    Lois Rilo Antelo
    Odoo consultant at ForgeFlow S.L.

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --

    Denis Roussel
    Software Engineer
    T    : +32 2 888 31 49
    M : +32 472 22 00 57


    Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
    Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
    Zone industrielle 22 | L-8287 Kehlen | Luxembourg

    by Denis Roussel - 01:51 - 14 Dec 2021
  • Re: stock_inventory repository
    If there's a way to populate a general inventory the same as before (although different models), I wouldn't see any reason to keep the model. All of this talking also from not analyzing the features.

    Regards.

    by Pedro M. Baeza - 01:45 - 14 Dec 2021
  • Re: stock_inventory repository
    Hi,

    I have seen that change but still haven't analyzed what should be the way to go... are you suggesting that OCA keeps the stock.inventory model and migrate all those modules on top of that?

    Regards,

    El mar, 14 dic 2021 a las 11:16, Francesco Apruzzese (<cescoap@gmail.com>) escribió:
    +1

    Il giorno mar 14 dic 2021 alle ore 11:12 Roussel, Denis <denis.roussel@acsone.eu> ha scritto:
    Hi all,

    As Odoo removed inventory model in v15 and as there are a bunch of modules for inventory in stock-logistics-warehouse repo, I request the creation of stock-inventory repository.


    Thanks

    --

    Denis Roussel
    Software Engineer
    T    : +32 2 888 31 49
    M : +32 472 22 00 57


    Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
    Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
    Zone industrielle 22 | L-8287 Kehlen | Luxembourg

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --

    Francesco Apruzzese

    Profilo professionale: http://it.linkedin.com/in/francescoapruzzese

    Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
    This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.

    Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente.

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --
    Lois Rilo Antelo
    Odoo consultant at ForgeFlow S.L.

    by Lois Rilo Antelo - 01:41 - 14 Dec 2021
  • Re: Move purchase_request* and purchase_work_acceptance*
    +1, although maybe others can be more useful, like OCA/tier-validation, that groups better other functional areas.


    by Pedro M. Baeza - 11:51 - 14 Dec 2021
  • Re: How to use oca-ci
    Hi Ronald,

    I personally never tried to use it for local development. I occasionally ran it locally, mainly to prepare automated tests of the image themselves.

    The steps are basically those done by the OCA GitHub action (example here).

    I'll be happy to give guidance and answer questions by anyone who wants to explore this and document it further.

    Best regards,

    -sbi

    On Thu, Dec 9, 2021 at 8:51 AM Ronald Portier <ronald@therp.nl> wrote:
    Hi,
    
    
    I just read the README.md of the https://github.com/OCA/oca-ci project,
    
    
    Does anyone have experience using this to develop and test locally?
    
    
    I am probably not that smart, but I miss in the README.md information to
    get started or how tu use this.
    
    
    Kind regards,
    
    
    Ronald
    
    
    

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Stéphane Bidoul - 11:46 - 14 Dec 2021
  • Re: stock_inventory repository
    +1

    Il giorno mar 14 dic 2021 alle ore 11:12 Roussel, Denis <denis.roussel@acsone.eu> ha scritto:
    Hi all,

    As Odoo removed inventory model in v15 and as there are a bunch of modules for inventory in stock-logistics-warehouse repo, I request the creation of stock-inventory repository.


    Thanks

    --

    Denis Roussel
    Software Engineer
    T    : +32 2 888 31 49
    M : +32 472 22 00 57


    Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
    Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
    Zone industrielle 22 | L-8287 Kehlen | Luxembourg

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --

    Francesco Apruzzese

    Profilo professionale: http://it.linkedin.com/in/francescoapruzzese

    Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
    This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.

    Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente.


    by Francesco Apruzzese - 11:16 - 14 Dec 2021
  • stock_inventory repository
    Hi all,

    As Odoo removed inventory model in v15 and as there are a bunch of modules for inventory in stock-logistics-warehouse repo, I request the creation of stock-inventory repository.


    Thanks

    --

    Denis Roussel
    Software Engineer
    T    : +32 2 888 31 49
    M : +32 472 22 00 57


    Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
    Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
    Zone industrielle 22 | L-8287 Kehlen | Luxembourg

    by Denis Roussel - 11:11 - 14 Dec 2021
  • Move purchase_request* and purchase_work_acceptance*
    Hi all,

    To reduce purchase-workflow repository size, I would suggest to create two new repositories in order to speed up tests.

    Thanks
    --

    Denis Roussel
    Software Engineer
    T    : +32 2 888 31 49
    M : +32 472 22 00 57


    Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
    Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
    Zone industrielle 22 | L-8287 Kehlen | Luxembourg

    by Denis Roussel - 09:35 - 14 Dec 2021
  • Re: Odoo 14 bank statement reconciliation

    Hi all,

    for Germany the law isn't that clear either. As I read it, the change to the journal would be ok if after the obviously 'marginal' change of the journal entry, its previous content and the fact that it had been changed is recorded and reviewable. Infact I didn't check it with regard to the new v14 suspense logic myself but I thing by standard means Odoo does not specifically record changes to journals at, all be they posted or not. I am interested what German accounting experts think about this.

    Best Frederik

    Am 11. Dezember 2021 14:17:19 MEZ schrieb "Pedro M. Baeza (Tecnativa)" <pedro.baeza@tecnativa.com>:
    I have been checking this and the safeguard that Odoo has put is that you can't lock a period without reconciling all the pending statement lines prior to that date. Is it illegal to change a posted journal entry? France regulation doesn't seem to have problems, as the inalterability is for sale journals.

    So in the end, it seems it's a weird operation, but not bad at all for avoiding a lot of temporary journal entries feeding and clearing the suspense account.

    Regards.

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    --
    Dr.-Ing. Frederik Kramer
    Geschäftsführer
            
    initOS GmbH
    An der Eisenbahn 1
    21224 Rosengarten
            
    Phone:  +49 4105 56156-12
    Fax:    +49 4105 56156-10
    Mobil:  +49 179 3901819
            
    Email: frederik.kramer@initos.com
    Web:   www.initos.com
            
    Geschäftsführung:
    Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

    Sitz der Gesellschaft: Rosengarten – Klecken
    Amtsgericht Tostedt, HRB 205226
    Steuer-Nr: 15/200/53247
    USt-IdNr.: DE815580155

    by Frederik Kramer - 03:51 - 11 Dec 2021
  • Re: Odoo 14 bank statement reconciliation
    I have been checking this and the safeguard that Odoo has put is that you can't lock a period without reconciling all the pending statement lines prior to that date. Is it illegal to change a posted journal entry? France regulation doesn't seem to have problems, as the inalterability is for sale journals.

    So in the end, it seems it's a weird operation, but not bad at all for avoiding a lot of temporary journal entries feeding and clearing the suspense account.

    Regards.

    by Pedro M. Baeza - 02:16 - 11 Dec 2021
  • Re: Decision tree to solve issues
    Check out the mermaid widget in web repo.

    Also In odoo a decision tree is a multi step wizard. I could see how to do that with some very fancy context passing to a generic wizard.

    On Sat, 11 Dec 2021, 7:17 am Xavier Brochard, <xavier@alternatif.org> wrote:
    This sound very much like reverting a task with dependencies :
    
    To work the printer need
    ->to be turned on
    -->green light
    --->paper
    --->toner
    -> to be online
    -->network cable plugged in
    -->no paper jam
    etc.
    
    ---
    Librement,
    Xavier Brochard xavier@alternatif.org
    La liberté est à l'homme ce que les ailes sont à l'oiseau (Jean-Pierre 
    Rosnay)
    
    Le 10.12.2021 17:57, Tom a écrit :
    
    
    > Hi Pierre
    
    
    > 
    
    
    > Thanks!
    
    
    > 
    
    
    > What I'm looking for is more something on the lines of:
    
    
    > 
    
    
    > - There is a decision.tree model eg "How to fix your printer"
    
    
    > - It can have decision.tree.node children such as "Is it turned on?"
    
    
    > - Each question node has a set of conditions as to which next node it
    
    
    > jumps to like: condition1,node1,condition2,node2...
    
    
    > - If there are no conditions on a node anymore then this is an end
    
    
    > node saying like "Your printer is irrefutably broken. Please send it
    
    
    > back."
    
    
    > 
    
    
    > Kind of like a "Choose your own adventure" book.
    
    
    > 
    
    
    > -Tom
    
    
    > 
    
    
    > 
    
    
    > Dec 10, 2021 17:32:12 Pierre Verkest <pierreverkest84@gmail.com>:
    
    
    > 
    
    
    > 
    
    
    > Hi,
    
    
    > 
    
    
    > 
    
    
    > At anybox the project management was(/is ?) based on top of such idea
    
    
    > where we could import mindmap as project starting point. Module is
    
    
    > called anytracker and available on github here:
    
    
    > https://github.com/anybox/anytracker [1] .
    
    
    > 
    
    
    > 
    
    
    > A project is an anytracker.ticket without parent
    
    
    > A task is an anytracker.ticket without child
    
    
    > A node becomes a node when a child appears !
    
    
    > 
    
    
    > After a while we add the concept of anytracker.bouquet which is a
    
    
    > couple of anytracker.ticket which could be a milestone, a release or
    
    
    > whatever that has some sense to group together without changing the
    
    
    > ticket tree !
    
    
    > 
    
    
    > hope that helps
    
    
    > 
    
    
    > 
    
    
    > 
    
    
    > 
    
    
    > 
    
    
    > Le ven. 10 déc. 2021 à 15:17, Tom Blauwendraat < tom@sunflowerweb.nl
    
    
    > [2] > a écrit :
    
    
    > 
    
    
    > 
    
    
    > Hi all,
    
    
    > I think anyone knows about decision trees, if even as jokes:
    
    
    > 
    
    
    > A customer wants something like this, not the visualisation per-se,
    
    
    > but to be able to have users click through it whenever they have an
    
    
    > issue.
    
    
    > I can imagine modeling something like this, but doesnt it already 
    
    
    > exist?
    
    
    > I guess the Odoo "Survey" modules can do part of it, but i don't know
    
    
    > if they support structuring the survey as a tree.
    
    
    > Any ideas?
    
    
    > Tom
    
    
    > 
    
    
    > _______________________________________________ Mailing-List:
    
    
    > https://odoo-community.org/groups/contributors-15 [3]  Post to:
    
    
    > mailto: contributors@odoo-community.org [4]  Unsubscribe:
    
    
    > https://odoo-community.org/groups?unsubscribe [5]
    
    
    > 
    
    
    > 
    
    
    > --
    
    
    > 
    
    
    > Pierre
    
    
    > 
    
    
    > 
    
    
    > _______________________________________________ Mailing-List:
    
    
    > https://odoo-community.org/groups/contributors-15 [6]  Post to:
    
    
    > mailto:contributors@odoo-community.org Unsubscribe:
    
    
    > https://odoo-community.org/groups?unsubscribe [7]
    
    
    > 
    
    
    > 
    
    
    > 
    
    
    > _______________________________________________
    
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15 [8]
    
    
    > Post to: mailto:contributors@odoo-community.org
    
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe [9]
    
    
    > 
    
    
    > 
    
    
    > 
    
    
    > [1] https://github.com/anybox/anytracker
    
    
    > [2] mailto:tom@sunflowerweb.nl
    
    
    > [3] https://odoo-community.org/groups/contributors-15
    
    
    > [4] mailto:contributors@odoo-community.org
    
    
    > [5] https://odoo-community.org/groups?unsubscribe
    
    
    > [6] https://odoo-community.org/groups/contributors-15
    
    
    > [7] https://odoo-community.org/groups?unsubscribe
    
    
    > [8] https://odoo-community.org/groups/contributors-15
    
    
    > [9] https://odoo-community.org/groups?unsubscribe
    

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Graeme Gellatly - 08:25 - 10 Dec 2021
  • Re: Decision tree to solve issues
    This sound very much like reverting a task with dependencies :
    
    To work the printer need
    ->to be turned on
    -->green light
    --->paper
    --->toner
    -> to be online
    -->network cable plugged in
    -->no paper jam
    etc.
    
    ---
    Librement,
    Xavier Brochard xavier@alternatif.org
    La liberté est à l'homme ce que les ailes sont à l'oiseau (Jean-Pierre 
    Rosnay)
    
    Le 10.12.2021 17:57, Tom a écrit :
    
    > Hi Pierre
    
    > 
    
    > Thanks!
    
    > 
    
    > What I'm looking for is more something on the lines of:
    
    > 
    
    > - There is a decision.tree model eg "How to fix your printer"
    
    > - It can have decision.tree.node children such as "Is it turned on?"
    
    > - Each question node has a set of conditions as to which next node it
    
    > jumps to like: condition1,node1,condition2,node2...
    
    > - If there are no conditions on a node anymore then this is an end
    
    > node saying like "Your printer is irrefutably broken. Please send it
    
    > back."
    
    > 
    
    > Kind of like a "Choose your own adventure" book.
    
    > 
    
    > -Tom
    
    > 
    
    > 
    
    > Dec 10, 2021 17:32:12 Pierre Verkest <pierreverkest84@gmail.com>:
    
    > 
    
    > 
    
    > Hi,
    
    > 
    
    > 
    
    > At anybox the project management was(/is ?) based on top of such idea
    
    > where we could import mindmap as project starting point. Module is
    
    > called anytracker and available on github here:
    
    > https://github.com/anybox/anytracker [1] .
    
    > 
    
    > 
    
    > A project is an anytracker.ticket without parent
    
    > A task is an anytracker.ticket without child
    
    > A node becomes a node when a child appears !
    
    > 
    
    > After a while we add the concept of anytracker.bouquet which is a
    
    > couple of anytracker.ticket which could be a milestone, a release or
    
    > whatever that has some sense to group together without changing the
    
    > ticket tree !
    
    > 
    
    > hope that helps
    
    > 
    
    > 
    
    > 
    
    > 
    
    > 
    
    > Le ven. 10 déc. 2021 à 15:17, Tom Blauwendraat < tom@sunflowerweb.nl
    
    > [2] > a écrit :
    
    > 
    
    > 
    
    > Hi all,
    
    > I think anyone knows about decision trees, if even as jokes:
    
    > 
    
    > A customer wants something like this, not the visualisation per-se,
    
    > but to be able to have users click through it whenever they have an
    
    > issue.
    
    > I can imagine modeling something like this, but doesnt it already 
    
    > exist?
    
    > I guess the Odoo "Survey" modules can do part of it, but i don't know
    
    > if they support structuring the survey as a tree.
    
    > Any ideas?
    
    > Tom
    
    > 
    
    > _______________________________________________ Mailing-List:
    
    > https://odoo-community.org/groups/contributors-15 [3]  Post to:
    
    > mailto: contributors@odoo-community.org [4]  Unsubscribe:
    
    > https://odoo-community.org/groups?unsubscribe [5]
    
    > 
    
    > 
    
    > --
    
    > 
    
    > Pierre
    
    > 
    
    > 
    
    > _______________________________________________ Mailing-List:
    
    > https://odoo-community.org/groups/contributors-15 [6]  Post to:
    
    > mailto:contributors@odoo-community.org Unsubscribe:
    
    > https://odoo-community.org/groups?unsubscribe [7]
    
    > 
    
    > 
    
    > 
    
    > _______________________________________________
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15 [8]
    
    > Post to: mailto:contributors@odoo-community.org
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe [9]
    
    > 
    
    > 
    
    > 
    
    > [1] https://github.com/anybox/anytracker
    
    > [2] mailto:tom@sunflowerweb.nl
    
    > [3] https://odoo-community.org/groups/contributors-15
    
    > [4] mailto:contributors@odoo-community.org
    
    > [5] https://odoo-community.org/groups?unsubscribe
    
    > [6] https://odoo-community.org/groups/contributors-15
    
    > [7] https://odoo-community.org/groups?unsubscribe
    
    > [8] https://odoo-community.org/groups/contributors-15
    
    > [9] https://odoo-community.org/groups?unsubscribe
    

    by xavier - 07:16 - 10 Dec 2021
  • Re: Decision tree to solve issues
    hum... ok so not sure that's helps that much then even you could reproduce the tree using title as answer node description as question that would probably not suit as usage...

    Le ven. 10 déc. 2021 à 17:57, Tom <tom@sunflowerweb.nl> a écrit :
    Hi Pierre

    Thanks!

    What I'm looking for is more something on the lines of:

    - There is a decision.tree model eg "How to fix your printer"
    - It can have decision.tree.node children such as "Is it turned on?"
    - Each question node has a set of conditions as to which next node it jumps to like: condition1,node1,condition2,node2...
    - If there are no conditions on a node anymore then this is an end node saying like "Your printer is irrefutably broken. Please send it back."

    Kind of like a "Choose your own adventure" book.

    -Tom

    Dec 10, 2021 17:32:12 Pierre Verkest <pierreverkest84@gmail.com>:

    Hi,

    At anybox the project management was(/is ?) based on top of such idea where we could import mindmap as project starting point. Module is called anytracker and available on github here: https://github.com/anybox/anytracker.

    A project is an anytracker.ticket without parent
    A task is an anytracker.ticket without child
    A node becomes a node when a child appears !

    After a while we add the concept of anytracker.bouquet which is a couple of anytracker.ticket which could be a milestone, a release or whatever that has some sense to group together without changing the ticket tree !

    hope that helps



    Le ven. 10 déc. 2021 à 15:17, Tom Blauwendraat <tom@sunflowerweb.nl> a écrit :

    Hi all,

    I think anyone knows about decision trees, if even as jokes:

    A customer wants something like this, not the visualisation per-se, but to be able to have users click through it whenever they have an issue.

    I can imagine modeling something like this, but doesnt it already exist?

    I guess the Odoo "Survey" modules can do part of it, but i don't know if they support structuring the survey as a tree.

    Any ideas?

    Tom

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --
    Pierre

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --
    Pierre

    by Pierre Verkest - 06:31 - 10 Dec 2021