OPAR - OTRS Package ARchive

Browseable collection of plugins for the popular OTRS software.


ServiceImportExport

Version
4.0.1
Other Versions
1.0.3, 1.1.0, 1.2.1, 1.3.4, 5.0.0,
Uploaded by/on
capeIT on 09 Feb 2016
Framework
4.0.x
Links
Download Website
Description
Provides ImportExportBackend for Service, SLA and Service2CustomerUsers.

Rate/comment this package

General

This package provides an CSV-based import/export backend for items described in following sections.

Of course, you may created your own import-/export mappings. To ease the use and in order to provide an initial functionality mappings are automatically created upon re-/installation of this package. Therefore it's checked if mappings with the given default names are already available. If so, no new mapping will be created. If not, a default mapping will be created. Before actually using these default mappings, please check their configurations.

Service-Import/Export

  • default mapping name "Service (auto-created map)"

  • Default Validity

      If no valid information is provided in import data, this valid information is used

  • Default Servicetype

      Depending on availability of GeneralCatalog class "ITSM::Service::Type" you may define an default Service-Type for a service to be imported (if not specified in provided data)

  • Default Criticality

      Depending on availability of GeneralCatalog class "ITSM::Core::Criticality" you may define an default criticality for a service to be imported (if not specified in provided data)

  • CSV-Row with Service-ID

      The field "ServiceID" is used as identifier for existing entries. If a Service with the given ID already exists it will be updated. Otherwise a new Service will be created. You can change the default mapping configuration and choose the "Full service name" as identifier. Note: Only "ServiceID" or "Full service name" can be used as identifier, because other fields don't have unique values. So, please do not set the check box "Identifier" for other fields - it will have no effect.

SLA-Import/Export

  • default mapping name "SLA (auto-created map)"

  • Default Validity

      If no valid information is provided in import data, this valid information is used

  • Default-SLA-Type

      Depending on availability of GeneralCatalog class "ITSM::SLA::Type" you may define an default SLA-Type for a service to be imported (if not specified in provided data)

  • Number of assigned services:

      An SLA may be assigned to many services, for a start it is assumed that 50 services is enough. if you require more AssignedServices you can increase this number in the mapping configuration. It limits the number of "AssignedService" selection in step 4 of the mapping configuration.

      The field "SLA Name" is used as identifier for existing entries. If an SLA with the given Name already exists it will be updated. Otherwise a new SLA will be created. You can change the default mapping configuration and choose the "SLA ID" as identifier. Note: Only "SLA Name" or "SLA ID" can be used as identifier, because other fields don't have unique values. So, please do not set the check box "Identifier" for other fields - it will have no effect.

Service2CustomerUser-Import/Export

  • default mapping name "Service2CustomerUser (auto-created map)"

This software comes with ABSOLUTELY NO WARRANTY. For details, see the enclosed file COPYING for license information (AGPL). If you did not receive this file, see http://www.gnu.org/licenses/agpl.txt.

POD ERRORS

Hey! The above document had some coding errors, which are explained below:

Around line 21:

'=item' outside of any '=over'

Around line 65:

'=item' outside of any '=over'

Comments

tto on 18 Mar 2011 about version 1.0.0

i) GENERAL This package provides an CSV-based import/export backend for items described in following sections. Of course, you may created your own import-/export mappings. To ease the use and in order to provide an initial functionality mappings are automatically created upon re-/installation of this package. Therefore it's checked if mappings with the given default names are already available. If so, no new mapping will be created. If not, a default mapping will be created. Before actually using these default mappings, please check their configurations. Some notes about general options "Export with labels": If enabled, the first line of the export file will contain some sort of headline containing the OTRS-internal key. Which may not be the perfect label but helps to understand. The first line of an import file is skipped if it contains only values which are used as OTRS-internal keys. Thus you may import this file without any problems. "DefaultValid": If no valid-information is contained in your import, this value is used instead. (ii) Service-Import/Export - default mapping name "Service (auto-created map)" - depending on availability of GeneralCatalog class "ITSM::Service::Type" you may define an default Service-Type for a service to be imported (if not specified in provided data) - depending on availability of GeneralCatalog class "ITSM::Core::Criticality" you may define an default criticality for a service to be imported (if not specified in provided data) - if the ServiceID is specified, you may update the name of the service, if not the ServiceName is used as identifier (iii) SLA-Import/Export - default mapping name "SLA (auto-created map)" - depending on availability of GeneralCatalog class "ITSM::SLA::Type" you may configure a default SLA-type - Important configuration params => number of assigned services: An SLA may be assigned to many services, for a start it is assumed that 50 services is enough. if you require more AssignedServices you can increase this number in the mapping configuration. It limits the number of "AssignedService" selection in step 4 of the mapping configuration. (iv) Service2CustomerUser-Import/Export - default mapping name "Service2CustomerUser (auto-created map)"