Contributors mailing list archives

contributors@odoo-community.org

Avatar

Re: Decision tree to solve issues

by
xavier
- 10/12/2021 18:12:22
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

Reference