Using Decision Table to set Ticket Choice Fields

EricG
Kilo Sage

I've created a Decision table to set RITM Ticket Values and Approval Groups depending on the Catalog item.

 

I'm attempting to create "Generic" flows, so that we can easily update any business changes.  E.G. Assignment Group, instructions, etc...

 

I can get most fields to set, except for RITM Category.  This is a custom field (u_category) based on same values as Task and Incided.

EricG_0-1714571586156.png

I can set these values via scripts with no issue, however, the flow is erroring.

EricG_1-1714571644003.png

The decision table has Category, Subcategory, assignment group, and some others.

Both Category and Subcategory are Choice values referencing the same values as the RITM.

I can pill drop u_subcategory but not u_category.

 

Anyone know how to fix.

11 REPLIES 11

Did you test it in decision builder via test button?

Yes - and this is what I got. As expected.

EricG2_0-1714656534855.png

 

Eckhard
Tera Contributor

Dear Tera,
I believe I have the same issue.
In my decision table I have as input a refernece to the sc_req_item table and in the conditions I want to check for a value in a custom field (u_number), but this field is not visible.
Every other field like short_description etc. is there but not the custom field.
Did you find a solutino for your issue?

Many thanks

Best regards

Eckhard

nataliya_b
Tera Guru

maybe as a workaround

in the flow, create flow variable with type string and assign value from your pillar to this variable

after, pass this variable to decision table.

 

Did category worked if you use script inside the flow? Did I get it right?

Thanks.  Let me try that.  

Just to confirm (as i'm the only one here and very distracted).
1. Add a variable to my FLOW
2. Populate this variable from my Decision Table results.

3. Use this populated field to update the ticket.

 

Am I correct?