Currently, the SmartScore feature allows for multiple scores to be configured. If multiple scores are activated, they process across all tickets in the system. For some, this can lead to very busy ticket history views, as well as lengthy Auto-Processing or Process Automation Rules with various scores to select from.
If we could within the SmartScore, select which Registration Codes this Score will apply to, then our processing power would be limited to only those tickets with the preferred Reg Code(s), and visibility could be limited to only those who need it.
I.E. if a division of an organization is using SmartScore for Risk Management on their gas tickets only, then a water or electric division of the organization screening tickets would not see the SmartScore when evaluating or researching tickets.
I.E. A nationwide utility has a score that creates actions specifically for Georgia Large Project tickets (Georgia requires specific Large Project responses), meaning the remaining codes in the other states would not need to be SmartScore'd, conserving processing power.
Currently, the SmartScore feature allows for multiple scores to be configured. If multiple scores are activated, they process across all tickets in the system. For some, this can lead to very busy ticket history views, as well as lengthy Auto-Processing or Process Automation Rules with various scores to select from.
If we could within the SmartScore, select which Registration Codes this Score will apply to, then our processing power would be limited to only those tickets with the preferred Reg Code(s), and visibility could be limited to only those who need it.
0 Votes
0 Comments
Login or Sign up to post a comment