Self Help Extractor

Last modified on 2022/08/09 13:58

Notes

  • The implementation of Self Help Extractor and its configuration for each new Self Help project to be synchronized must be performed by the EasyVista CMC team.
  • From Service Manager Autumn 2020 - Build 125.1 onwards, all of the components required for the configuration of the integration model will be shipped with the standard version in databases 50004 and 50005. You can check the version of your empty database in [EMPTY_DATABASE_VERSION]) in Other Parameters.

Self Help Extractor is a tool for extracting data from Self Help procedures in order to import them to the Service Manager knowledge base using an integration model. You can schedule the integration to update the database on a regular basis.

What is the purpose of Self Help Extractor?

  • Synchronize on a daily basis the Self Help and Service Manager knowledge bases.
  • Ensure that Support team members can access the latest knowledge articles when they run a full text search when resolving a ticket.
  • Ensure that users can access the latest knowledge articles when they run a search on the Self Service portal.

Operating principle

Display Steps
Operating principle.png

In Self Help

  • (1) On the Service Manager server, Self Help Extractor sends a request to Self Help to extract the procedures of a Self Help project.
  • (2) A CSV file containing the Self Help project tree structure and data from procedures will be generated.

In Service Manager

  • (3) The CSV file will automatically be placed in the FTP folder on the Service Manager server.
  • (4) An integration model is run to import data from the CSV file to the Service Manager knowledge base.

Examples

  • Ticket: Run a full text search and access the knowledge base to consult articles containing the keywords, Print PDF. Click a knowledge article to display the procedure imported from Self Help.
             Example - Full-text search.png  Example - Full-text search - SH procedure.png
  • Self Service portal: Access the knowledge base to consult articles containing the keywords, Skype meeting. Click a knowledge article to display the procedure imported from Self Help.
             Example - Apps portal.png  Example - Apps portal - SH procedure.png

Notes

  • Self Help Extractor is not installed by default. You must submit a request asking the EasyVista CMC team to implement this tool.
  • Any new Self Help project to be synchronized must be configured by the EasyVista CMC team. You must provide the information the CMC team will require for its configuration, e.g. domain, project name, theme, FTP folder, extraction frequency, etc.
  • Data in Self Help project folders with no procedures that can be run individually will not be extracted.
  • Data from unpublished procedures will not be extracted.
  • The CSV file will be placed in the folder called Resources/<Account>/Integration. <Account> corresponds to the Service Manager database where the data should be integrated.
  • The name of the file will always be the same. It will be overwritten each time an extraction is run.
  • The integration model should be built using the standard connector called Known errors & Knowledge (Self Help Extractor). Depending on requirements, EasyVista may insert additional fields to integrate data specific to Self Help procedures.

Caution

  • Self Help Extractor extracts data based on the name of the Self Help project. As such, you must inform the EasyVista CMC team of any changes to Self Help Extractor project names so that the configuration of Self Help Extractor can be modified accordingly. If this is not done:
    • Two Self Help projects will be present in the knowledge base.
    • Only those knowledge articles pointing to the new Self Help project name will be synchronized.
    • Users can still consult knowledge articles from the old Self Help project. These articles may not be up-to-date and may contain obsolete links.
  • If you integrated data using the old Self Help project name:
    • In Service Manager, you must remove all knowledge articles pointing to the old Self Help project name.
    • You must provide the new Self Help project name to the EasyVista CMC team.
    • You must run data integration again in Service Manager once the CSV file is generated using the new Self Help project name.

Best Practice

  • Plan sufficient time for publishing procedures before data extraction is run by Self Help Extractor.
  • Set up the Self Help content validation workflow to publish validated procedures only.

Procedure: How to update the Service Manager knowledge base

Prerequisites

1. Provide the EasyVista CMC team with the required information for implementing Self Help Extractor.

  • Domain where the Self Help project to be extracted is found.
  • Exact name of the Self Help project.
  • Data extraction frequency, by default, three times a day.
  • Service Manager database where the data should be integrated.

    example  Production database 50005, test database 40000

  • Theme used to display the Self Help project.
     

Note: If your Service Manager version is earlier than Autumn 2020 - Build 125.1, you must add fields and import the connector as described below. In later versions, these components are implemented in the standard version.

2. Add the fields required by Self Help Extractor in the SD_KNOWN_PROBLEMS table by running the query below.

ALTER TABLE SD_KNOWN_PROBLEMS ADD E_ID_EVSH nvarchar(200)
ALTER TABLE SD_KNOWN_PROBLEMS ADD E_ORIGINE_EVSH nvarchar(200)

3. Import the dedicated connector called Known errors & Knowledge (Self Help Extractor) to Service Manager.

  • Import the downloaded file to Service Manager by selecting Administration > Import / Export > Import in the menu.

 

Step 1: Create the integration model in Service Manager.

     Open url.png See the detailed procedure.
 

1. Select Administration > Integration > Integration models  in the menu.

2. Create the integration model.
         Integration model - Step 1.png

  • Select the type of update you want, i.e. Insertion & Update to create new records in the database and update the existing ones.
  • Select the CSV data type.
  • Select the language of the data in the CSV file.
  • Select the connector called Known errors & Knowledge (Self Help Extractor).
  • Select the Take First Row as Header box to indicate that the first row of the file contains field labels.
  • Select the Create Log box to generate a log file at the end of the processing.
  • Click Upload and select the CSV file generated by Self Help Extractor.
    Note:  The CSV file will be available in the folder called Resources/<Account>/Integration. <Account> corresponds to the Service Manager database where the data should be integrated.
  • Click Next.

3. Map the fields in the CSV file (Source column) with the fields in the connector (Destination column).
         Integration model - Step 2.png

  • Specify a default value for Service Manager fields with no mapped value in the CSV file.
  • Click Next.

4. Specify the properties of the fields. Open url.png See the description.
         Integration model - Step 3.png

Step 2: Run the integration model in Service Manager.

Run an immediate execution for data synchronization.

1. Select Administration > Integration > Integration models in the menu.

2. Click Edit icon.png next to the integration model.

3. Click Next until the last step of the model.

4. Click Execute.

The integration log screen will automatically appear once the processing is completed.

5. Check the records that have been updated.

  • View the details of records by clicking Added / Updated hyperlinks in the Details tab.
  • View errors generated during integration via the Errors tab.

Schedule the data synchronization.

1. Select Administration > Integration > Integration models in the menu.

2. Click Calendar icon.png next to the integration model.
The scheduling information will appear.

3. Select the Enabled box and specify the scheduling information you want.

Note: The .csv file must be available in the Resources/<Account>/Integration folder of the EasyVista web server (<Account> identifies the Service Manager base in which the data will be integrated).

Best Practice icon.png  You should backdate the start date so that the scheduling will run immediately.

4. Click Finish.
The data will be integrated the next time the integration model is running.

5. Correct any errors. You can consult the integration log.

Step 3: Check that the Service Manager knowledge base has been correctly updated.

1. Select Service Operation > Problems & Known Errors > Known Errors or select Service Transition > Knowledge > Knowledge in the menu.

2. Check that the knowledge articles have been correctly updated.

Tags:
Powered by XWiki © EasyVista 2022