OPAR - OPM Package ARchive

Browseable collection of plugins for the popular ticket system software Znuny and ((OTRS)) Community Edition.


ITSM-CIAttributeCollection

Version
1.7.1
Other Versions
1.9.7, 2.0.1, 2.2.0, 2.4.1, 4.1.2, 5.0.3, 6.0.4,
Uploaded by/on
capeIT on 18 Mar 2011
Framework
2.4.x
Links
Download Website
Description
Additional CI-attributes.

Rate/comment this package

Usage Information

This package provides additional ITSM-CI-attributes for OTRS:ITSM, i.e. ITSMConfigurationManagement. Following you'll find a short documentation on the use and features of this extension.

Why a new attachment storage rather than using VirtualFileSystem

Virtual file system proved to be not suitable, since it builds some sort of directory path out of object-class and id. Thus it would require to know the CIs version ID before it's actually created. If this could be solved somehow, copying a CI with an attachment would also cause a copy of the attachment itself, which is not desirable from our point of view.

(i) Use of the CI-Attribute "CIClassReference"

  • behaves similar to customer user attribute but refers to another config item of some CI-class

  • allows to automatically delete and create links to CIs of a referenced class

  • eases the configuration of assembled config items, which consist (in parts) of other config items without annoying manual link creation

  • attribute definition requires three additional attributes:

            ReferencedCIClassName or ReferencedCIClassID: defines the referenced CI-class
            ReferencedCIClassLinkType: defines the link type which should be used for automatic link creation and deletion, no link will be created if empty
            ReferencedCIClassLinkDirection: set to "Reverse" if you want to create a reverse link for directed link types (will only be relevant if ReferencedCIClassLinkType is set)
  • IMPORTANT NOTE: The "Key" attribute has to be a UNIQUE name within the class definition!

EXAMPLE

   {
       Key        => 'Location',
       Name       => 'Asset Location',
       Searchable => 1,
       Input => {
           Type                           => 'CIClassReference',
           ReferencedCIClassName          => 'Location',
           ReferencedCIClassLinkType      => 'Includes',
           ReferencedCIClassLinkDirection => 'Reverse',
       },
   },

(ii) Use of the CI-Attribute "ServiceReference"

  • allows to automatically delete and create links to Services

  • attribute definition requires two additional attributes:

            ReferencedServiceLinkType: defines the link type which should be used for automatic link creation and deletion, no link will be created if empty
            ReferencedServiceLinkDirection: set to "Reverse" if you want to create a reverse link for directed link types (will only be relevant if ReferencedCIClassLinkType is set)
  • IMPORTANT NOTE: The "Key" attribute has to be a UNIQUE name within the class definition!

EXAMPLE:

   {
       Key        => 'AssignedService',
       Name       => 'Assigned Service',
       Searchable => 1,
       Input => {
           Type                            => 'ServiceReference',
           ReferencedServiceLinkType       => 'RelevantTo',
           RReferencedServiceLinkDirection => 'Normal',
       },
   },
 

(iii) Use of the CI-Attribute "QueueReference"

  • behaves similar to customer user attribute but refers to a queue

EXAMPLE:

   {
       Key        => 'AssignedQueue',
       Name       => 'Assigned Queue',
       Searchable => 1,
       Input => {
           Type => 'QueueReference',
       },
   },

(iv) Use of the CI-Attribute "CIAttachment"

  • allows to add one or more attachments to a ConfigItem

  • see following SysConfig options for further configuration AttachmentStorage::StorageBackendModules AttachmentStorage::DefaultStorageBackendModule Frontend::Module###AgentAttachmentStorage AttachmentStorageFS::StorageDirectory

  • IMPORTANT NOTE: The attributes CountMin and CountMax must always be defined! Otherwise you won't be able to delete attachments from CIs. If you set CountMin => 1, it will be impossible to delete the last attachment (the last n attachments for CountMin => n).

EXAMPLE:

   {
       Key => 'Attachment',
       Name => 'Attachment',
       Searchable => 1,
       Input => {
           Size => 50,
           MaxLength => 50,
           Type  => 'CIAttachment', 
       },
       CountMin => 0,
       CountMax => 1,
   },

COPYRIGHT

Copyright (C) 2006-2011 c.a.p.e. IT GmbH, http://www.cape-it.de/

The following persons have contributed to this extension:

  • Torsten(dot)Thau(at)cape(dash)it(dot)de

  • Martin(dot)Balzarek(at)cape(dash)it(dot)de

  • Frank(dot)Oberender(at)cape(dash)it(dot)de

  • Anna(dot)Litvinova(at)cape(dash)it(dot)de

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 49:

=over should be: '=over' or '=over positive_number'