REALTECH SmartChange SP4 HF05

New BAdI to prefilter the Project/Destination at release

The BAdI /RTC/TM_IF_BD_FILTER_PJ_DEST can be implemented for custom filtering the Project and Destination of a transport request when it is released or added to TM. Examples of how to use the BAdI can be found in the example class /RTC/TM_CL_CUST_FILTER_PJ_EX.

BAdI, Project Administration

SC-1247

Consideration of SmartChange Integration when creating a transport request with transaction SLXT

With this feature, new transport requests created with the translation export transaction SLXT are handled in the same way as if they were called from the Transport Organizer. This particularly affects system environments that use the TM Integration Framework to link ITSM tickets with transport requests.
enhancement.
In the context of this development, the BAdIs /RTC/BD_SC_TM_SL_SAP (enhancement spot /RTC/ES_SC_TM_SL_SAP) and /RTC/BD_CP_CREATE_REQUEST (enahncement spot /RTC/ES_CP_CREATE_REQUEST) were added, which are called after the transport request has been created. Enhancement implementation /RTC/TM_IF_EHI_CREATE_TR_AFTER, specific to the integration framework, was also adjusted to trigger BAdI /RTC/TM_IF_BD_CREATE_REQUEST ( enhancement spot /RTC/TM_IF_ES_CREATE_REQUEST) when called from SLXT.

BAdI, Integration Framework

SC-1260

Filter the Project/Destination at release by CTS Project

This feature enables the display of project and destinations routes depending on CTS projects when releasing transport requests.
In the project administration, several CTS projects can be assigned to one TM project. The assignment is made in change mode by right-clicking on the TM project and selecting the context menu “CTS project”.

If one or more CTS projects are assigned to a TM project, these TM projects are only displayed for transport requests that are also assigned to the same CTS project. TM projects without a CTS project will be displayed always.

Configuration, Project Administration

SC-1246

Bring direct TM Attribute Search back into selection screen.

To ensure efficient filtering for TM attributes, in a first step with Service Pack SP03, the selection option for filtering TM attributes was changed so that it is possible to search for several TM attributes at the same time, as well as only for values with the corresponding TM attribute names.

On the one hand this means flexibility and accuracy in the search, but on the other hand the customer's wish was for a simpler input. In response to this wish, the "Quick filter" for TM attributes has now been introduced in a second step.

TM attributes can be defined as “Quick filter” in the Project Administration .

TM attributes defined as quick filters are then displayed as a separate field in the selection screen of the TM Workflow Monitor.

This enables a quick search for TM attributes. The flexible search is still possible via the “Free TM Attributes selection” button.

As default is allowed up to 14 attributes to be added as “Quick filter”. If more than 14 attributes are necessary, the transaction /RTC/TM_GEN_QFILTER can be used to generate necessary attributes in the selection screen.
The label on selection screen will be the first 20 characters from the TM attribute description.

TM Attribute, UI

SC-1273

Double click on the modifiable requests in the TM Workflow Monitor shows details screen

With this feature by double clicking on a transport request in the node “Modifiable requests”, a details screen appears. This contains a request header, with transport request details and an attribute tab with the SAP attributes.

UI, Workflow Monitor

SC-1252

Synchronization Managment log extended with new column to display the Rollout Transport

With this feature, a new column with the Rollout Transport was added to the SA_log.

Synchronization, UI

SC-1013

Keep defined tasklist filter for the runtime session

When defining filter options in the tasklist and jumping to Workbench or Customizing views the filter previously defined when returning to the tasklist gets lost and needs to be defined again.

With this feature the Filter will be kept saved at the runtime session, to be set again when returning to the tasklist screen.

Tasklist, UI

SC-1238

After ticket selection the assignment popup of the integration is wrongly displayed again

The scenario is reproduced when in the GET filter query for ITSM types JIRA or SOLMAN an 'OR' condition is used, making the result of the web call more than one issue.

The program has been corrected.

Integration Framework, Jira_App

SC-1280

Jira Issue not updated when creating TR from Jira

When creating an SAP transport request from Jira, the transport request is created successfully and it is visible in the SmartChange Pannel. After refreshing the page, the TR disappears from the Jira issue.

The program has been corrected. The ITSM name saved in the Jira configuration is handled as upper case in SAP, in order to match the ITSM name saved in the SAP configuration.

Integration Framework, Jira_App

SC-1284

Missing the short text for Special Aspects when release request

If TM is configured to display special aspects at release time, then the short text is not displayed for the transport request.

The program has been corrected.

UI

SC-1212

Empty tab displayed in TM Monitor

An empty tab is displayed in TM Monitor when the “Exported requests” node exists and for defined filter criteria, no data is found in the “Exported requests” node.

The program has been corrected.

UI, Workflow Monitor

SC-1287

Saved TM-Workflowmonitor-Layouts lost after Implementation of HF2-HF4

The layouts saved before SP4 HF4 are not accessible because a handle was added to the layout.

A new transaction /RTC/SC_COPY_ALV_LAY was created to allow the copy of the layout from no handle to the handle 'LEV'.

At ‘Program name’ should fill /RTC/SAPLTM_WF.

Press F8.

A popup window will be displayed with all available layouts.

Select the layouts where the column ‘HD’ is empty and press Enter. The selected layouts will be moved to handle ‘LEV’.

Workflow Monitor

SC-1286