Work Order form Best Practice and Classic views
BMC Service Request Management provides the classic view and the best practices view the Work Order form. The system administrator configures the view that users see.
If there is a difference between how you do something in the Best Practice view and how you do it in the Classic View, only the required procedure for the Best Practice view is described.
Classic view
The Classic view is provided for customers who are upgrading from earlier versions of the application and who are not yet ready to adopt the Best Practice view.
Best Practice view
The Best Practice view is an improved version of the Work Order form. In this view, the fields most commonly used for resolving and for updating work orders are immediately visible. You can access additional, less frequently used functionality from the tabbed sections of the form or from the links in the navigation pane.
Best practice
Important
In this table, the Navigation pane links are not mentioned if they are available from the Navigation pane in both views, even if the link is accessed from a different group on the Navigation pane.
Benefits to the Best Practice view of the Work Order Request form
Feature | Classic view | Best Practice view | Benefits of Best Practice view |
---|---|---|---|
Customer Information | Fields on the Requester tab:
A menu enables you to select company | Fields on the Main view:
| In the Best Practice view, the fields are displayed in the order in which the information is obtained, which helps you to complete the fields in the correct order. It also reduces the time needed to register a work order, because there is no need to open multiple tabs to complete the registration. |
Contact information (Requested by) | Fields on the Requester tab:
| Field on the Main view:
| The fields appear in the order in which the information is obtained. |
Notes (Detailed Description) | Field on the Main view:
| Field on the Main view:
| The fields are displayed in the order in which the information is obtained. |
Template | Available as a link under the Functions menu on left side of the view. | Field on the Main view:
| In the Best Practice view, templates are available from a field on the Main view to encourage the use of this feature. Using templates reduces registration time and the average incident handling time. After the customer describes the issue, the user can determine whether a relevant template is available. |
Summary | Field on the Main view:
| Field on the Main view:
| Fields are displayed in the order in which the information is obtained. |
Work Order Type | Field on the Main view:
| Field on the Main view:
| Fields are displayed in the order in which the information is obtained. |
Request Manager | Fields on the Assignment tab:
| Field on the Main view:
| Fields are displayed in the order in which the information is obtained. |
Service | Field on the Categorization tab:
| Field on the Main view:
| This field was moved to the Main view, because the information it contains is considered key information. |
Request Assignee | Fields on the Assignment tab:
| Field on the Main view:
| Fields are displayed in the order in which the information is obtained. |
Status | Fields on the Main view:
| Fields on the Main view:
| Fields are displayed in the order in which the information is obtained. |
Priority | Field on the Main view:
| Field on the Main view:
| Fields are displayed in the order in which the information is obtained. |
Work Info | Fields and table on the Work Info tab:
| Fields and table on the Work Detail tab (displayed initially):
Additional fields hidden in More Details expand area:
| Key work order request information includes Work Info entries. |
Operational Categorization | Fields on the Categorization tab:
| Fields on the Categorization tab (if configured to be displayed):
Type-ahead is available for all fields. | Research suggested that most of BMC's customers use the operational categorization fields only sporadically. This means that even when the fields are completed, they cannot be used for reporting, because they are not consistently completed. |
Product Categorization | Fields on the Categorization tab:
| Fields on the Categorization tab (if configured to be displayed):
Note: Type-ahead is available for all fields. Auto-complete and pre-fill are available for Product Name. | These fields were moved to the Categorization tab, because using the CMDB is a better way to perform grouping, trending, and assignment. This, and wanting to reduce the registration time of new incident request records, means that now the product categorization can automatically be completed based on the product categorization of the related service. |
Tasks | Tables on the Tasks tab | Tables on the Tasks tab | Space available on the screen to display tasks is bigger, leading to improved usability. |
Relationships | Table on the Relationships tab | Table and fields on the Relationship tab | The Object menu and Search Text field in Create Relationships area simplifies creation of relationships to CIs, work orders, and so on, and reduces the number of windows that open. |
Date/System | Available on the Date/System tab | Available on Date/System tab | Blank |
Comments
Log in or register to comment.