I’m convinced that the case sensitiveness of Remedy is one of its major flaws. It can look like a minor issue, but believe me when I say that it can be the greatest source of incidences for your Remedy support team. Also for other languages that uses accents, the accent insesitiveness is a must, when sorting elements. So, changing your ARS instance to Case insensitiveness must be an objective. To have a Case Insensitive or Accent Insensitive instance of ARS is not difficult, but it isn’t straightforward. The best solution is to have the full text search enabled, but this is an extra cost in licenses. Sometimes you don’t have these licenses (or you don’t have enough for everybody), so another strategy is needed. Remedy bases all its comparisons and sorts in the database engine, so if we change the database engine, we change Remedy. That means that we must achieve that any ORDER BY or WHERE clause to be case insensitive. The solution then implies case insensitive sessions and indexes. If you control both, then you control your case sensitiveness. … Read the complete post
-
Recent Posts
Recent Comments
- Jose Huerta on Adding custom permission groups to ITSM foundation
- namrata kulkarni on Adding custom permission groups to ITSM foundation
- Jose Huerta on Product Categorization in BMC Remedy
- Lloyd on Product Categorization in BMC Remedy
- Major Incidents | Designing the Priority | The Remedy for IT on BMC Remedy Action Request System Vs OTRS
@TheRemedyForIT
Tags
ARS ARS Config BMC Case insensitive Case sensitive Categorization Certification Change Management Development Documentation Escalation Filter Free Tool Functions Funny Incident Management Indicator ITIL ITSM Config Joke KPI License login Mid-tier Oracle OTRS Permission Groups Problem Management Process engeeniering Product Categorization RAD Rapid Application Development Request Id Scheduling Service Service Support SLA Sort Status Support Group Table Field Three layers User Groups User Management WWRUG


























