I want an automation rule for incident tickets, to set a field "Customer Facing" as "Yes" if any one of the selected objects in another field - "Impacted Services" - has the "Customer Facing" attribute set to Yes in Insight.
1. User selects objects A, B and C in field "Impacted Services"
2. A object and B object have attribute "Customer Facing" value of "No", but C has value "Yes"
3. Automation rule sets "Customer facing" to "Yes" because at least one of the objects selected has a value of "Yes" for that attribute
Thank you for any assistance.
Hi @Jeanne Schock and welcome to the community!
You would do something like this:
{{issue.Impacted Services.Customer Facing}} = Yes
Thank you. This makes sense. It is not working however. Could you review please? Much appreciated.
Name of Field: High-Level Services
Name of Object Type: High Level Service
Name of Attribute: Student Impact
I have:
{{issue.High Level Service.Student Impact}} = Yes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you please share a screen shot of the rule's audit log? This will help us identify where the rule is failing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So, it looks like the smart value is not returning anything. Looking back at your initial description, the insight field name appears to be Impacted Services. So your smart value should look like this:
{{issue.Impacted Services.Student Impact}}
Try adding a Log Action just above your Lookup Objects with this info:
{{issue.Impacted Services}} | {{issue.Impacted Services.Student Impact}}
This should return the object key(s) for the selected Impacted Services and the Student Impact attribute. If you see something there, then the lookup Objects should work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you. The log results correctly display the object keys and attribute value of Yes or No. The schema name is "Test". But Look up object still throws errors.
Log
TEST-76, TEST-77, TEST-82, TEST-90 | Yes, Yes, No, No
Lookup Objects:
Could not retrieve objects from custom smart value query:
{"errorMessages":["IQL \"Yes, Yes, No, No = Yes and objectSchemaId == 11\" has invalid syntax at position 3 with error message \"extraneous input ',' expecting {OPERATOR, REFERENCE_OPERATOR, IS_OPERATOR, ' '}\""],"errors":{}}
Log Action:
{{issue.High-Level Services}} | {{issue.High-Level Services.Student Impact}}
Lookup Objects:
{{issue.High-Level Services.Student Impact}} = Yes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok - I think I see what needs to be tweaked with the lookup objects action:
"High Level Service" IN ({{issue.Impacted Services}}) AND "Customer Impact" = Yes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Mark. Could you explain how this lookup is supposed to behave so that I understand how it works. And it's getting very confusing between the names of fields/attributes/object type. I'm having a hard time following the components of this string. Thank you.
"(name of object type?)" IN ({{issue.(field name?)}}) AND "(object attribute)" = Yes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No problem...
So as I type this out, I'm realizing it should probably be:
Key IN ({{issue.Impacted Services}}) AND "Customer Impact" = Yes
Sorry for the extra back and forth... Day job keeping most of my attention
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you that did it. Sometimes having to explain in English really helps sort it out. Thanks so much, this is my first adventure in using Insight for Incident automation. It's really powerful.
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.