Registering a New Problem (i)
Another thing you concluded during your request review is that a problem should be registered for request #704220. Even though the incident was resolved successfully, its root cause was clearly not removed. Because the entire service was down, you are anxious to find out what caused this incident so that something can be done to ensure that the incident does not recur.
Open a new problem for request #704220. Do this as follows:
- Select the request in the “Requests for Problem Identification” view,
- Click on the Actions button in the toolbar, and
- Select the option “Relate to New Problem…” from the Actions menu.
This causes a new browser tab to open with a new problem record. Most fields of this problem are automatically populated. In the Note field you can add the following information:
When the MaxInQueue hangs, users who are not already logged in will not be able to access the Expense Reporting application. They will not even be able to open the login screen.
Because request #704220 already specifies a workaround that appears to work well, you can check the Known Error box and fill out the following in the Workaround field:
Manually flush the MaxInQueue on the server. This can only be done by a specialist from the Application Development team.
Do not save the new problem yet. The next exercise needs to be completed first.