Versions Compared
Version | Old Version 14 | New Version 15 |
---|---|---|
Changes made by | ||
Saved on |
Key
- This line was added.
- This line was removed.
- Formatting was changed.
2.
1. 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 | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||
Following entries can be defined by global settings:
|
ITSM systems configurations
In this step, you’ll configure parameters for external server.
ITSM system
Expand | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||
Following fields can be defined:
|
Work Item
Expand | |||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||
Following fields can be defined:
|
Work item > Fields
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
Following field can be defined:
|
Dev Systems
Info |
---|
|
Optional settings
Expand | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
Following fields can be defined:
|
Settings for TM Workflow Step
In this step the configuration table defines the behaviour for each action.

An action can be defined for a specific Transport level, Project and/or Destination.
Expand | |||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||
Following fields can be defined:
|
2. Activate BADIs on the Development systems
Following BADIs must be activated on the development system(s):
/RTC/TM_IF_BIM_CREATE_REQUEST – After TR creation event (SE01/SE10) - Update ITSM system with TR number
/RTC/TM_IF_BIM_DELETE_REQUEST – After TR deletion event (SE01/SE10) – Update ITSM system deleting the TR number
Steps:
Go to transaction code SE19
Image Removed
Image Added
Mark checkbox ‘Implementation is active’ under ‘Runtime behavior’ (1) and Activate the object (2)
Image Removed
Image Added
3. TM User Exits supported for Jira Plugin
The following TM user exits can be activated, depending on the required integration scenario.
On this page
Activate BADIs on the Development systems
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