errorqueen · IT Systems Manager · ✭✭✭✭✭

Another great monthly mission! All green this month!

Were all winners announced?

Congratulations @"BaldFeegle" !

Thank you! Excited to join the MVP crew!

Thank you for this reminder!

All green! Thanks for the Monday fun!

Congrats to the winners!

I second this!!

Loved this! Thanks for the fun and listening to our vents!

All green this month! Woohoo! Thanks for a fun mission!

Congrats @"PaulyG70" ! 

That was great! Thank you so much to Chrystal and the presenters. Super helpful thoughts and information to bring back to my company as we work on decision-making with AI.

Congratulations everyone!

Congrats to all of the winners!

True. But what happens when company requirements restrict information we can give so much that it basically does nothing for us? How can we manipulate AI to fit within company guidelines while still providing it enough information to work the way it is intended.

@"amore1329" Thank you for your help!

I agree. The problem we are finding, or at least from my perspective, is that there is no consistency or clear understanding from decision makers and it seems a lot more of wanting to have the next thing vs. assessing the AI, whatever it is, and how it can effectively work within our company.

I see them now. Congratulations to all the winners for this month! Great job everyone!

.-.. . - .----. ... / --. --- -.-.-- -.-.--

We have the same issue and concern. The other concern is how many people are using AI in the company that we just simply don't know about. 

Happy Birthday THWACK!

Agreed! Completely fitting for this time of year!

That was fun! Thanks for the "hunt" to make this Monday a bit more eggselent 

Awesome! I haven't tested it yet but I have it set up so I am glad you can confirm it for me. 

I'll give an example of one I have done. I created a custom field that asks whether the staff member has restarted their computer and I added it to a form I also created in regard to this. Then, I went to "Dynamic Form Rules" and created a rule with the scope "Incidents" that has the condition to show the field given…

The scope needs to be set for the custom field. You can do this via a dynamic form rule. There may be another way to set the scope but that is what I do. Once the scope is set there, the custom field will appear in the Automation rules once the corresponding scope is selected.

Awesome! Glad you got it fixed!

Can you send a screenshot of what you are trying to do?

When you created the field, did you set it to be visible in service catalog or global?

What does the error say?