We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

Unable to attach a configuration item as an affected CI within a flow.

john_wenzel
Giga Contributor

2 hours ago

I am building out tag governance for the first time.  I want to generate a ticket when a policy fails. I also want to include the CI that has the problem in the ticket for tracking purposes but to also ensure I do not create multiple opened tickets for the same problem. 

 

I am first submitting a catalog item request

john_wenzel_0-1784208584203.png

I am then creating a catalog task for the item I just generated. 

john_wenzel_2-1784208728138.png

The affected ci in is not being placed in the record. Google told me to update the record after it was created so I then added an update record step that does the same thing.

john_wenzel_3-1784208857406.png

This was the initial setup from the pill picker

 

john_wenzel_1-1784208668339.png

I have tried the CI itself, the cis name and the sys id. However when the task is generated the CI is not attached. 

john_wenzel_4-1784209156132.png

The attachment in the flow looks proper to me. 

john_wenzel_5-1784209224395.png

Anyone have any thoughts on what I am doing wrong? I would think this should work. 

 

Thanks in advance.  

0 Helpfuls
  • 52 Views
1 REPLY 1

JenniferRah
Mega Sage

2 hours ago

The easiest way to do this is to create a variable in your catalog item for the CI and pass it to that variable when you submit the catalog item. 

 

The catalog task should be created within the flow for the catalog item itself, and you can include the variable in the catalog task or set the CI to the variable value, if you want.

0 Helpfuls