REALTECH SmartChange SP5 HF06

With this feature, a new ITSM type, ADO - Azure DevOps, has been delivered.

Supported actions:

• GET - OFFLINE mode: You can configure the popup to assign a ticket to be displayed at TR creation in SAP. With this release, you can only add the Ticket manually, with no check against the ITSM.
• Automations:
  • Ex. Work Item Update: You can configure an update to the Ticket via the automation work item type, for the following workflow steps:
    • STATUS_SW: TR Status switch within the TM Workflow Monitor
    • MOVE2HIST: TR move to TM History via switcher (end of lifecycle)

With this feature,for the ADO - Azure DevOps ITSM type the following actions are available for automation configuration ( ex. Work Item Update: You can configure an update to the Ticket via the automation work item type, for the following workflow steps)

• LINK_EXT: Create assignment of transport request to ticket (After TR creation)
• RELEASE: Release transport request

Example of configuration:

For the Body of the update web call, the placeholder <TRKORR> has been introduced. In the above example, the custom ADO field Custom.TR will be updated with the current transport request number,

Approve multiple transports or packages.

If the usergroup is not provided then all the usergroups where the current user is authorized will be approved for the specified approval type,

Two additional parameters are added:

• ApproveOneGroup - if the value is true then the “Usrgroup” is ignored and will be approved first usergroup where the current user has authorization.
• IgnoreParams - ignore if the selected transports are in different levels

Call example :

URL: /sap/opu/odata/RTC/TM_GW_SRV/TR_ApproveSet(Trkorr='MT1K900089,MT1K900447')

Body:

{
  "Approve" : "R",
  "ApprovalType" : "C",
  "Usrgroup" : "CONS",
  "ApproveOneGroup" : true,
  "IgnoreParams" : ""
}

With this feature, a new ITSM type is available for the Integration
Framework: DOT4.

For easy configuration, TEMPLATE_ DOT4 is delivered.

The following action is available with this version:

• UPD -> Triggeres the updates to the Smartchange Plugin for the ITSM

With this new feature, you are now able to trigger an update call to the SNOW Incident/Change Request assigned to a transport request when you reject or revoke the reject in TM Monitor. This allows you to see in SNOW if a transport request assigned to an issue has been rejected in the TM workflow.

Prerequisites

TM IF configuration
The following actions have been configured as default for the ITSM type SNOW.

1. UPD/REJECT (Rject TR)
2. UPD/REJECT_REV (Revoke reject TR)

No manual action is needed.

Troubleshooting

If an error occurs during the update calls to the ITSM(s), the calls are saved for later recall via transaction /RTC/TM_IF_MONITOR. The update can be triggered either manually or automatically (job schedule or subsequent update calls triggered by working with the specific transport request in TM Monitor. like approve, import, or switch status).

With this feature, you are now able to configure an ITSM via the TM Integration Framework, although there is no direct connection between the SAP and the ITSM systems. This allows you to logically link a transport request in SAP to an ITSM ticket ID, by manually inputting the Ticket ID. As standard for the integration framework, the popup to assign a ticket ID can be configured to be displayed either at TR creation or at TR release.

Configuration

For easy configuration of an offline ITSM, a new template has been created: TEMPLATE_ OFFLINE_ITSM with a new generic ITSM type: OFFLINE. Server path or RFC destination are not required here.

For the work item GET, the flag ACTIVE must be set to 'X' and the Connection Type must be set to OFFLINE.

One default field “TICKET ID” is defined to be displayed in the popup to assign ticket ID, where you can configure the name of the SAP/TM attribute where it will be saved.

In the “TM Workflow Step” configuration, the new ITSM ID with work item GET can now be assigned to action CREATION.

The new Transport Request Status Switcher service enables users to efficiently move Transport Requests from the queue to signature or current to queue or current to signature in a specific level. By providing an ITSM ID, ITSM Ticket ID, ITSM Ticket GUID, a list of Transport Requests, the desired level, and the current and target statuses, users can automate the process of updating Transport Request statuses.

The service checks if the Transport Requests are in the correct level and status before proceeding with the switch, ignoring those in higher levels or incorrect statuses. If a Transport Request is modifiable or in a lower level, the switcher will not start and will return an error message, ensuring data integrity.

The external user ("ExtUserName" ) if is provided will be displayed in the action log in a second line .

The mandatory fields are:

• “Trkorr” or “ItsmId” and “TicketId”
• “LevelName”
• “StatusFrom”
• “StatusTo”

The parameters with default values :

• "ImportOlderThenMin" : 0 if “StatusFrom” <> 'C' and 1 if “StatusFrom” = “C” 0 is not allowed
• "ChangeMaxRc" : 12
• "ChangeImported" : "A"
• "CheckVirtualSystems" : ""
• "IgnoreLockedSystems"  : "",

Ex.

URI: /sap/opu/odata/RTC/TM_GW_SRV/Start_SwitcherSet

Body:

{
"Trkorr" : "MDQK900052",
"ItsmId" : " ",
"TicketId" : "",
"TicketGuid" : "",
"LevelName" : "DEVELOPMENT",
"StatusFrom" : "Q",
"StatusTo" : "S",
"ImportOlderThenMin" : 0,
"ChangeMaxRc" : 12,
"ChangeImported" : "A",
"CheckVirtualSystems" : "",
"IgnoreLockedSystems"  : "",
"ExtUserName" : "External User"
}

When the odata for the approval is called and ExternalUser is provided, this will be displayed in the transport action log.

Ex.

HTTP Method PUT

URI: /sap/opu/odata/RTC/TM_GW_SRV/TR_ApproveSet(Trkorr='MDQK900250')

Body

In the latest version, the OData Service has been improved to update the attributes based on the transport status. Consequently, if the transport is modifiable (not yet released), the SAP attribute will be updated; otherwise, the TM attribute will be updated.

Example:
URL: /sap/opu/odata/RTC/TM_GW_SRV/TR_AttributeSet(Trkorr='MT1901890')

Body:

Odata to create ToC for original transports.

If the ticket information are provided the selected transport will be checked if they belong to the ticket (if no transport is specified then all modifiable transports for the ticket will be selected)

Call example:

URL: /sap/opu/odata/RTC/TM_GW_SRV/TOC_StartSet

HTTP Method: POST

Body:

In this release, we have enhanced the functionality of the TM Attributes screen. Now, users can easily access and view descriptions associated with TM Attributes directly from the assignment screen.

The "Description" column is populated with the attribute descriptions defined in the "Defined TM Attributes" screen.

In response to user feedback, the TM attribute length has been extended from 150 characters to a maximum of 255 characters. This enhancement allows users to store more comprehensive information, such as SharePoint documentation links, within the TM attributes.

Additionally, the TM maintenance popup window has been enlarged to provide a more user-friendly experience when working with TM attributes. While the popup window is not dynamically resizable due to system limitations, the increased size offers improved visibility and ease of use for managing TM attributes.

The Transport Management Workflow Monitor now includes functionality to delete and add modifiable transport requests. Users can remove transport requests from the monitor using the new "Delete" button. If the transport request is assigned to any projects or destinations, a confirmation popup will appear, informing the user that the transport request and its associated assignments will be deleted. Upon confirmation, the entries will be removed from the Workflow Monitor, and a log entry will be created to record the deletion.

Additionally, users can now add modifiable transport requests to the Workflow Monitor using the new "Add" button. Clicking this button will display a popup where users can enter the transport request number. The system will validate if the transport request is modifiable in the development system. If it is modifiable, the addition will proceed; otherwise, an error message will be displayed, indicating that the transport request is no longer modifiable.

In the previous version, when releasing a transport request and only one project and destination are retrieved and in the transaction /RTC/TM_BADI the option :

is set, an additional button “Create new package” is displayed.This button shouldn’t be displayed on Project and Destination screen.

The program has been corrected.

In the previous version, customizing tables /RTC/LIB_D_TABUC and /RTC/LIB_D_LAT generated an excessive number of changelog entries, even when no actual changes were made to the table content. This resulted in a significant accumulation of unnecessary changelog entries, leading to increased storage consumption and potential performance issues.

The Function Module /rtc/tm_rfc_log was not automatically deleting logs as intended, leading to potential log buildup and reduced system performance over time.

The program has been corrected.

In previous versions, when entering the “Customer UserExit configuration” tab in TM Global Settings a second time, a previous empty container remained on top and the screens were not displayed correctly because of it. The latest update solves this issue.

The program has been corrected.

In the previous versions, when a license expired during a Proof of Concept (POC), the transports could no longer be released, even if the user was not part of the POC user list in the TM BADI configuration. In the latest version, an expired license will no longer restricts the BADI configuration.

The program has been corrected.

TM-Attribute of type file allows uploading files to a transport. In the previous version, attempting to access a file from an older transport in the TM-History could in some cases show an RFC error.

In the previous versions, when trying to create a ToC for a Repair Task, a message appears that the task has not been released, even though it has. This issue has been resolved with the latest update.

The program has been corrected.

In the previous version, the system incorrectly allowed the creation and release of transport requests without assigning a project or destination. This led to the generation of a transport of copies (ToC) even when the transport request lacked the necessary project and destination information.

An error will displayed if one of the transports doesn’t have a project or destination assigned
The program has been corrected.

n the previous version, when transport requests were released from one system to another, the author ID was populated correctly, but the corresponding author name was not displayed in the Workflow Monitor. This resulted in blank author names being shown alongside the author IDs, even when the user data was properly maintained in the relevant system. This issue has been resolved with the latest update.

The program has been corrected.

Following an update to SP5 HF5, users encountered an issue where attempting to add a Transport Request would not succeed.

The program has been corrected.