DISABLED LOCKED RULE? applyRequestSmartTicketSuggest is not a good rule microfocus
is there anyway to disable this rule "applyRequestSmartTicketSuggest"?
its located in the Request -> after applying updates
This is very bad design..., many customers i work with prefer to leave the offering blank in many cases. Especially with the email integration.
Is there a application setting I can turn off or you need to patch this ASAP...
is that configured on a per module basis?
I looked into the smart ticket application setting and recommend the customer disables that.
I will update you if this is the fix for our problem.
Thanks for the suggestion!
As discussed through a different channel, it is not a bad design problem.
The offering doesn't just get assigned randomly, it is based on explicitly configure the smart ticketing feature:
- Smart Ticket flag enabled: to categorize tickets according to ticket display label and description.
- If the above is enabled, additionally Smart Ticket training must be done with a resultant taxonomy tree. If that is empty, the rule will still be executed but no data in the ticket will be updated.
For more details about how to configure the feature, please follow the documentation:
or take a look at one of our Practitioner Forum session:
Sep 16th, 2018: Technical Drill-down: Machine Learning (the topic itself starts around minute 31 into the recording)
thank you for the links. Perhaps that practitioner forum link should be included on the smart analytics doc.
The customer did not give me all the details so I did not understand why the rule was working as it was.
It all makes sense after I learned everything involved.
I am also looking for more details around the "Activate auto-assignment" checkbox in the smart ticket task.
There are no details about this setting on the docs, and i would like to know more.
I also was confused by some ambiguity in the articles:
"With Smart Ticket enabled, Smart Analytics can intelligently populates the fields defined in smart ticket"
"Smart Analytics can intelligently populates the fields defined in smart ticket tasks. There are no smart ticket tasks created by default, so no fields are filled"
I don't really see the need for the smart ticket app setting if the whole functionality hinges on a smart ticket task to actually populate anything. Maybe add a note to that appsettings doc that the ticket task is needed?