DataImporter - Import Request Activities

Table of contents

Overview

This import type allows to import the activities related to requests. During the original request import, only the resolution activity is imported. Use this import type, if activities from another system need to be kept. 

References

 

What you need to know:

The reference template files (.xlsx et .xml) to prepare imports are included in the Requests.zip file.

Required Fields

  • Number - Whole number
    • Represents the number of the request (incident or SR) associated to the activity
    • The number used can be the one from Octopus or the one from the source system, if requests were imported from another system
    • For more details, refer to the Request identification method
  • Date – Date and Time
    • Represents the activity date. The date must be greater than or equal to the opening date and less than or equal to the resolution date
    • The date format must be compatible with the server settings; YYYY-MM-DD
  • User
    • Octopus assignee who entered the activity

Optional Fields

  • Type
    • Represents the activity type already defined in Octopus
    • The activity type is configurable from the Tools > Reference data management... > General > Activity types menu
    • If this field is mandatory in Octopus, it will be mandatory during import
  • WorkBreakdown - Text (5000)
    • Represents the description of the work done
    • If this field is mandatory in Octopus, it will be mandatory during import
NOTE: More than one activity can be added at a time by placing them on separate lines. Each new line with the same request number will be a new activity.
  • Effort
    • Represents the effort of the work done for each activity
    • Format HH:MM:SS (in Excel the column must be in text format). For example, for one hour and a half, write 01:30 in the column
    • If this field is mandatory in Octopus, it will be mandatory during import
  • OnSiteVisit - Boolean
    • Check box type field to specify if the technician had to go on site to execute the activity
    • Accepted values are: 1 or 0, True or False, Yes or No
    • If non specified, the default value is no.

Configuration File (XML)

The declaration of the source is done by indicating the IncidentActivity value in the <Content> tag.

NOTE: The XML file used as this example is for an import done from Excel 2007 or 2010. To explain the tags used in all types and to find out more about the types of files, please refer to the XML Configuration File article
<?xml version="1.0" encoding="utf-8" ?>

<Sources>

   <Source Name="RequestActivity">

      <ConnectionString>Provider=Microsoft.ACE.OLEDB.12.0;Data Source=c:\Import\IT Requests.xlsx;Extended Properties="Excel 12.0 Xml;HDR=YES";</ConnectionString>

      <ViewName>[ImportActivity$]</ViewName>

      <Content>IncidentActivity</Content>

      <IncidentIdentificationMethod>ByImportedIncidentID</IncidentIdentificationMethod>

   </Source>

</Sources>

Information on Additional Tags

To import incident templates and SR types, the XML file can contain one additional tag. This tag is not mandatory and if it's not specified, the default value will be used. 

Request Identification Method

In the XML file to import request activities, it is possible to specify how the request will be found, either by the incident/SR number or by the imported request number.

Permitted values for the IncidentIdentificationMethod tag:

  • ByIncidentID: Octopus incident/SR number
  • ByImportedIncidentID (Default value): Imported source request number.

So, if you import requests from an external source and after you import activities, the system can use the number from the external system.

X
Help us improve our articles








Help us improve our articles