I recently developed a customization that lets us group our legacy system (imported) ticket history with new v.12 ticket history in criteria builder. It replaces the Ticket History Title/Production/Prod Season criteria items with new ones that serve essentially the same functionality, but use a different view of the ticket history table for detail and different reference tables.
Is there a reason I shouldn't just inactivate the original criteria items and replace them with my own?
Thanks,
-Nick Reilingh
Nick,
There really isn't any reason to avoid doing this. I would suggest two things to do before diving in to the deep end.
1) Check in T_LIST for any lists which use the existing criteria
select * from T_LIST (nolock) where criteria like '%keyword_no%###%'
In this case ### is your keyword number. I'd contact any users that have active lists with those keywords and let them know what's happening.
2) Since you can't inactivate keywords and deleting them can have unexpected consequences, create a control group that only administrators have access to and move the original keywords to that control group.
Other than that, there shouldn't be any problem with adding your new keywords.
Happy hunting!
Thanks! We're a brand new implementation, so I've got no existing lists to speak of (yet).
For "inactivating", I was going to take a page out of the V12 ticket history install script and assign them to the "Inactive" TR_KEYWORD_CATEGORY, which keeps them in the table but prevents them from showing up in the system table display or in criteria builder.