errorqueen · IT Systems Manager · ✭✭✭✭✭

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?

Might have just found the answer. Testing it now but by creating a group that runs concurrently, that could potentially run the tasks for each group on their own. If I'm wrong, let me know. 

I knew it was an obvious answer. Thank you so much! That worked!

I don't believe there is a way to do that but what you could do is, on the Service portal, make "Related Assets" visible. This way, on the form/ticket, the IT service desk can easily add the assets and it provides a search field with check boxes for all current assets. These will then be attached to the form/ticket in the…

I haven't tested it so not sure if it completely works, but I was thinking what you could do is create an automation rule. The automation rule would need several conditions so that it is specific enough to only affect a certain subset of tickets with approvals needed. And it will need a Time-Based Condition. You would also…

That would be the case, yes, if people are submitting tickets from a "New Ticket" or blank ticket form. The last option only works if you specify in the automation rule the category and subcategory of tickets each group of CC'd agents is assigned to. This would be configured in Setup>Service Desk>Categories. 

I might have figured out a different route that allows automation. First, you would create custom Field. I just did a mock one called "Contract Group". Then, you would create a custom form on "Contracts" and have the login to show the "Contract Group" when it is Maintenance. Then you would also add that field to show on…

Here is my suggestion. If you haven't already done this, I would put all of the Agent Users you are wanting these notifications to be sent to in a group. There are a couple ways you could do this. You could create an automation rule to send an email with the updates from the incident every time the incident is updated and…