The following table summarizes the differences between an Actionable and Static Service Catalog:
| |
Actionable (Software based) |
Static (Document or Web Pages) |
| Role-driven |
Included, connected to your existing Active Directory (or LDAP) for role-specific and customized catalogs |
Typically a global catalog without role specifics. Makes it much more difficult to find info and may present sensitive or irrelevant info to users. |
| Ease of Use and Usability |
Fully searchable, categorized, easily navigable for maximum ease of use. Users able to find relevant information quickly |
Limited or no search capabilities, difficult to navigate and find relevant info |
| Real-time ordering |
Users able to order requestable services via shopping cart |
Not applicable |
| Real-time order/request status |
Users able to track order and request status in real-time |
Not applicable |
| Workflow capabilities |
Service ordering and fulfillment workflows can be designed and automated |
Not applicable |
| Integration with back-end systems |
Out of the box integration with existing tools such as Help Desk, HRMS, CRM, and ERP |
Not applicable |
| WYSWIG Editing |
Button-click editing of content for easy management |
Not applicable |
Case Study:
Case Study:
Case Study: