Versions Compared

Version Old Version 9 New Version 10
Changes made by

Maria Hald

Maria Hald

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

TM IF Configuration cockpit

The configuration cockpit (transaction /RTC/TM_IF_CONFIG) needs to be run on the TM Server only.
A default configuration is provided for activating a JIRA ITSM system, under following names:

  • TEMPLATE_ JIRA CLOUD

  • TEMPLATE_ JIRA SERVER

Calling transaction /RTC/TM_IF_CONFIG

TM Workflow step configuration

For an easy configuration, these entries can be copied changing the Server ID and setting the proper RFC destination.

Global activation settings

General settings for activating the TM Integration Framework.

Expand
titleTechnical details

Following entries can be defined by global settings:

Technical name

Field name

Value

Optional

SWITCH_OFF

'X' = TM Integration framework is inactive

Switch off the Integration Framework.
(‘X’ -> switched off)

ITSM_ATTR

Name of TR attribute for storing the ITSM server id

Name of the SAP Transport Request Attribute  

The SAP Transport Request attributes must exist on the Development systems (TCode SE03).

TITLE1

Title for pop up

Customized texts for the popup title

X

POPUP_TEXT

Name of Long Text (SO10) to be displayed in the popup

Name of a Smartform Text Module to be additionally displayed on the popup, as information

X

TR_TYPE

 

'A' = All, ' ' = Customizing and Workbench

Possible values:

  • 'A' : All type of transport requests;

  • ' ': Customizing and Workbench.

 This setting applies only to APPROVAL event. Define it as ‘A’ if Transport of Copies should also have a Ticket ID assigned.

If the entry is not defined, ‘ ‘ is considered as default value.

X

MOD_GET

Name of the function module for getting data

Name of customer function module to fetch the Ticket information from the ITSM System

X

MOD_SCREEN

Function module which contains the (individual) screen.

Feature not implemented in this version.

Name of the individual customer function module, which calls an individual screen.

X

ITSM systems configurations

In this step, you’ll configure parameters for external server.

  • ITSM system

Expand
titleTechnical details

Following fields can be defined:

Technical name

Field name

Value

Mandatory

SERV_ID

Server ID

Unique identifier for ITSM system.

ACTIVE

Active

‘X’ – ITSM is actively used by the Integration Framework

SERV_DESC

Server Description

Description of ITSM system (used in the popup_to_assign)

SERV_PATH

Server Path

Path of the external server (used in RFC destination).

SERV_RFC

RFC Destination

Name of the RFC destination of type G (HTTP Connection to External Server)

X

ITSM_TYPE

ITSM Type

Supported ITSM types:

  • JIRA (both On Premise and On Cloud)

  • SNOW (Service Now)

  • POLARION

X

  • Work Item

Expand
titleTechnical details

Following fields can be defined:

Technical name

Field name

Value

SERV_ID

Server ID

Unique identifier for ITSM system.

ITEM_TYPE

Item type

Identifier for Work Item Type for ITSM system (Ex. Incidents, Change Requests…)

Or for Web Call Resource name (ex. Search for Issues, Update Issue)

ITEM_DESC

Item description

Description of Work Item Type/ Web call resource

ITEM_PATH

Item path

Technical table path of the Work Items/web call resource name

*SUB_ITEM_PATH

Sub-item path

Technical URL used in order to get fieldnames and descriptions via Web Service call for the Work Item from Service Now ‘sys_dictionary’ table

Ex. ‘/api/now/table/sys_dictionary?sysparm_query=name=task&sysparm_fields=column_label,element’

*SNOW specific field.

ACTIVE

Active

Defines a Work Item type as Active (the one used for the integration for the Assign Ticket ID actions)

Note

Only one Work Item Type must be active.
Otherwise, the interface will pick up the first active item type. 

  • Work item > Fields

    Image Added
Expand
titleTechnical details

Technical name

Field name

Value

SERV_ID

Server ID

Unique identifier for ITSM system.

ITEM_TYPE

Item type

Identifier for Work Item Type for ITSM system

FIELD_NAME

Field Name

Technical name of the field used internally

Note

Technical restriction:

  • Can contain only ‘A’-‘Z’, ‘0’-‘9’,’_’,’-‘

  • Max length 30 char

FIELD_DESC

Field Description

Field label/description used for UI – F4 popup_to_assign

FIELD_PATH

Field Path

Path of the value in the response JSON format of the web call

Used separator: ‘/’

FIELD_ALIAS

Field Alias

Object name used in the web call for restricting the result of the web call to the relevant information 

Note

 Jira: The “FIELDS” param (which can be specified multiple times) gives a comma-separated list of fields to include in the response. This can be used to retrieve a subset of fields.

 

ACTIVE

Active

Active flag

IS_UNIQUE

Uniquie

Defines a field as unique identifier of the Work item type (internal generated value in Service Now)

Note

Restriction:
It MUST always be defined and active.

Info

Service Now
SYS_ID is the unique identifier for all work items in Service Now.

Info

NOTE 
It is recommend to store also the Unique identifier in a TM attribute. The number of the Work Item may not uniquely identify it in Service Now. (but even if it does not have an TM attribute assigned, it must still be defined).

IS_UI_ID

UI ID

Defines a field as Ticket ID (external value displayed in Service Now, which identifies a Work Item). 

Note

Restriction:
It MUST always be defined and active.

Info

Service Now
NUMBER is the displayed value for all work items in Service Now

ATTR_NAME

Attribute

TM/SAP attribute name for storing the value of the field assigned to a TR.

POS

Position

Position for display of the field in the selection POPUP (POPUP for assigning a Work Item to a Transport Request).

Note

 Restrictions:

SYS_ID must always have position 0.
NUMBER must always have position 1.
All active fields must have a position number assigned (>1).

On this page

  1. TM IF Configuration cockpit

  2. Activate BADIs on the Development systems

  3. TM User Exits supported for Jira Plugin

    • Assign Ticket ID

      • BADI_CHECK_BEFORE_CREATION -> Action CREATION

    • Update Ticket ID

      • BADI /RTC/TM_IF_BD_CREATE_REQUEST -> Action LINK_TO_EXT

      • BADI /RTC/TM_IF_BD_DELETE_REQUEST -> Action DELETE_TR

      • BADI_FEEDBACK_AFTER_EXPORT-> Action RELEASE

      • AFTER_ADD2_WF -> No action (Must be activated in TM if either CREATION/AFTER_WF_A are activated)

      • ACTION_LOG -> Action APPROVAL

      • AFTER_IMPORT -> Action IMPORT