Ідеї
0
Виконано
decision trees getting cluttered
Assume a simple credit matrix. Based on your income you will get 1 of 3 interest rates.
Income > 10000 goes to the 1st outcome, >8000 the 2nd and > 5000 the third.
In the current version you have to make a tree looking like the left pic in the diagram.
If you attached priorities to a decision you could make it look like the second diagram. Say your income is 9000, you will fail the first check but pass both 2 and 3, however if you have a priority you would pass the income > 8000 check and stop evaluation at that point. Maybe a useful idea? Things like risk pricing models would benefit greatly from this and the designer space would look far less cluttered
Income > 10000 goes to the 1st outcome, >8000 the 2nd and > 5000 the third.
In the current version you have to make a tree looking like the left pic in the diagram.
If you attached priorities to a decision you could make it look like the second diagram. Say your income is 9000, you will fail the first check but pass both 2 and 3, however if you have a priority you would pass the income > 8000 check and stop evaluation at that point. Maybe a useful idea? Things like risk pricing models would benefit greatly from this and the designer space would look far less cluttered
Відповідь
Відповідь
Under review
Without the pictures mentioned I am left to guess.
My guess is you are talking about bundling up individual decisions into a single decision tree activity that would act like a switch.
Is this correct?
My guess is you are talking about bundling up individual decisions into a single decision tree activity that would act like a switch.
Is this correct?
I made a pic forgot to attach but yes you have the right idea. Kinda like the VB.net switch (ps Im not advocating VB.net) :)
Служба підтримки клієнтів працює на UserEcho
My guess is you are talking about bundling up individual decisions into a single decision tree activity that would act like a switch.
Is this correct?