The solutions make up a knowledge database for a customer support service.

Each solution file describes the "tricks", ideas, procedures applied by a technician during the resolution of a problem or customer help request.

A solution record is generally created at the closing of a service request. In fact, some automated processes are designed to facilitate the creation of this record.
You can also create a solution record directly from the Solution function. In this case, you need to enter all the characteristics in the record.

Each solution can be the object of a search in the database for each word that it contains, on associated key words, on its skills group, on the user creating it, etc.

Each solution record can be associated with other records in a neighboring domain.

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

Header

Tab General

Tab Solution

Use this tab to enter a summary description of the solution within a limit of 235 characters. If the description exceeds 235 characters, an icon is displayed on the right of the text box. Click this icon to write and/or browse a summary description.

Tab Keywords

You can search for solutions based on the words used in the problem and solution descriptions. But this type of search can pose performance problems in very large databases.

Thus, to guarantee excellent performance in very large knowledge databases, it is necessary to enter several keywords for each record that describe the heart of the problem and the solution.

Duplicate entry control :

In order to maximize the search success conditions, all the keywords entered are converted into uppercase characters. In this way there will only be a single version of each word.

Despite this precaution, it is possible that the same word is entered with different spelling (singular and plural).
It is thus recommended to click Existing keywords from the Actions icon, just after entering a word in the field and just before the validation of its content: a window displays the list of neighbor words. You can thus check if an equivalent word has been entered (e.g. in the singular form). In this case, it is recommended to select the keyword equivalent that has already been defined to reduce the risk of "false" duplicates.

The keyword list is automatically increased as and when new keywords are entered.

Automatic extraction of keywords:

The entry of keywords, which are added as a complement to the solution text, may contain errors.

To avoid this, you can define a list of relevant keywords in miscellaneous table 451: keywords will be automatically extracted each time a solution is written.

Tab Associated Solutions

Use this tab to combine solution records:

  • relative to a similar application field for the current solution,
  • sharing specific characteristics with the current solution.

This association is used to navigate between solutions. This navigation type ensures a perfect limit for a specific application field.

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

This keyword has already been entered for this solution.

This message appears when the user attempts to enter the same keywords twice in the keyword grid associated with a solution.

This solution record has already been entered.

This message appears when the user attempts to associate the same solution more than once with the current solution.

You cannot associate a solution with itself.

This message appears when the user attempts to enter the current solution code in the associated solutions grid.

Tables used

SEEREFERTTO Refer to documentation Implementation