Superb Chuck - stumbled into the Decision tables space - Flow Designer looks very powerful and, when working with decision tables, it's magic ! Thanks very much.
@@ChuckTomasi I'm on the case, Chuck. The platform is moving so fast it's hard to keep up - but this is definitely something we'll exploit in our Store app !
This was very helpful. However, the main problem I see is why we need to create a whole table to hold the "qualifier" for the condition in our decision table. I understand you can just read off a different table, but making a new table for each qualifier seems kind of redundant. How would you handle multiple qualifiers? For example, if the employee band was between a certain number and the employee age is a certain number? Would you add age to the decision table you made?
You can use any table as the answer table. It doesn't have to be a new table. You could use incident, kb_knowledge, any field that has values can be an answer record. Regarding the multiple qualifiers, it's all in the decisions (related list) to the decision table record. I used one item, the points, but you could easily add the age, team, etc. with the condition builder. Same as any other condition field in the platform.
Hi, a bit late to comment but I hope you might be able to help ;) my flow, exact as your example is I hope , triggers and updates the band just fine from Test but does not trigger on its own when activated. the trigger is simple, points is updated ... I went thru a kb that leads you thru a bevy of sys trigger tables and found what the kb articled called 'success'. Thanks
This is a great video and lesson! My unfortunate issue as of right now, is that when I select my decision table, my choices do not auto populate underneath. I just get an Otherwise automatically and I have to delete that. Unsure as to what I am doing wrong there. Any advice Chuck? Thank you, -Rob
You can use any table as the answer table as long as it contains the "band" (in this case) to set as a value. Normally your employee table is going to be your input (the points) and you'll pull your answers from another table. Your use case may be different.
Hi Chuck, I am currently struggeling with decision table when the input is a list type. So i have a form with 2 list collectors who are getting the choices from the decision input choices so they are always in sync. When adding the list collectors to the decision action in flow designer I already get a table error saying table can't be find. I fixed this by adding lookup records for both inputs. But even without an error it seems the decision action input has no way of handeling lists. Even though you have list as a type of input. Can you help me one this. i even tried creatinng custom tables for both fields but i end up with the same result.
@@ChuckTomasi They are on the catalog item as variable and the choices that are available are comming from the input fields (list type) you can add choices
i made apost on community aswell : community.servicenow.com/community?id=community_question&sys_id=144f09b6db77501466f1d9d968961928&anchor=answer_5f46513e1b3f50508672ea89bd4bcb8f for more info.
You don't create tasks from the decision table. Think of it like a JavaScript "switch" statement. You create tasks BASED ON the results of the decision.
![Lp. Сердце Вселенной #60 РОЖДЕНИЕ ЛОЛОЛОШКИ [Финал] • Майнкрафт](http://i.ytimg.com/vi/YoR0pAV9FVQ/mqdefault.jpg)
Superb Chuck - stumbled into the Decision tables space - Flow Designer looks very powerful and, when working with decision tables, it's magic ! Thanks very much.
Thanks. Don't forget to look at Decision Builder which makes building and maintaining the decision tables even easier!
@@ChuckTomasi I'm on the case, Chuck. The platform is moving so fast it's hard to keep up - but this is definitely something we'll exploit in our Store app !
You're amazing Chuck, very nicely explained. Thanks a lot for all your efforts..!
Thank you. Don't forget to check out the Decision Builder as well. It makes managing the decision tables SOOOOO much easier.
Hi Chuck. Session was too good. Thanks. I will be happy if you post one video based on the decisiontableapi.
Thats simple as brilliant!!! Thanks a lot
This was very helpful. However, the main problem I see is why we need to create a whole table to hold the "qualifier" for the condition in our decision table. I understand you can just read off a different table, but making a new table for each qualifier seems kind of redundant. How would you handle multiple qualifiers?
For example, if the employee band was between a certain number and the employee age is a certain number? Would you add age to the decision table you made?
You can use any table as the answer table. It doesn't have to be a new table. You could use incident, kb_knowledge, any field that has values can be an answer record. Regarding the multiple qualifiers, it's all in the decisions (related list) to the decision table record. I used one item, the points, but you could easily add the age, team, etc. with the condition builder. Same as any other condition field in the platform.
Hi, a bit late to comment but I hope you might be able to help ;) my flow, exact as your example is I hope , triggers and updates the band just fine from Test but does not trigger on its own when activated. the trigger is simple, points is updated ... I went thru a kb that leads you thru a bevy of sys trigger tables and found what the kb articled called 'success'. Thanks
This is a great video and lesson!
My unfortunate issue as of right now, is that when I select my decision table, my choices do not auto populate underneath. I just get an Otherwise automatically and I have to delete that.
Unsure as to what I am doing wrong there. Any advice Chuck?
Thank you,
-Rob
do i have to create the employee band table? can't it read from employee table?
You can use any table as the answer table as long as it contains the "band" (in this case) to set as a value. Normally your employee table is going to be your input (the points) and you'll pull your answers from another table. Your use case may be different.
Hi Chuck,
I am currently struggeling with decision table when the input is a list type. So i have a form with 2 list collectors who are getting the choices from the decision input choices so they are always in sync.
When adding the list collectors to the decision action in flow designer I already get a table error saying table can't be find. I fixed this by adding lookup records for both inputs. But even without an error it seems the decision action input has no way of handeling lists. Even though you have list as a type of input. Can you help me one this. i even tried creatinng custom tables for both fields but i end up with the same result.
Are the list collectors on the form (e.g. a catalog variable) or are they used to create a many-to-many list?
@@ChuckTomasi They are on the catalog item as variable and the choices that are available are comming from the input fields (list type) you can add choices
i made apost on community aswell : community.servicenow.com/community?id=community_question&sys_id=144f09b6db77501466f1d9d968961928&anchor=answer_5f46513e1b3f50508672ea89bd4bcb8f
for more info.
Hi Chuck
How to create tasks from decision table .I need to create tasks one by one.
You don't create tasks from the decision table. Think of it like a JavaScript "switch" statement. You create tasks BASED ON the results of the decision.