Typically, BMC restricts its manuals and related documentation to the tool interaction and rarely enters into the organizations procedures. This can sometimes lead to confusion where some aspects of the applications are bad documented, or it’s difficult to determine which kind of information must be placed in some particular fields. Categorizations is a very good example of this lack of documentation. If asked, BMC answer is that the product is open to any interpretation the organization want to make. That … →
-
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

















The Secret Documents of BMC
This is the first of a series of post I plan to deliver on a monthly basis. I call them, “the Author Comments”. All of them will be my personal opinion regarding some aspects of the market, BMC, companies or other stuff. This month I will express my opinion about the way BMC handles the documentation about its products.