The text system is no longer delivered as a BC set. Rather, it is contained in the installation transport and is available in all clients of the system after the update.

When sending e-mails, the "Reply To" address is now filled with the content of the e-mail field from the xSuite user administration (transaction /WMD/XF_USR_ADMIN).

This new behavior is particularly interesting for xSuite Web users without an SAP account, since their e-mails were previously sent in the name of a general background user, such that a reply e-mail could not be sent directly to the agent.

The internal storage of the text log was changed to enable a timeline view in xSuite Web and in SAP Fiori. New text-log entries are no longer attached to the existing standard text. Instead, each log entry generates its own new standard text. New entries are stored with a process ID and a sequential number. The date, time and user are stored in the header data for the text.

When reading the texts, all entries are sorted by date and returned together with their header data as a table. For the SAP GUI display, all new entries are converted to the old format and separated as one entry by text lines with the separator line defined in customizing.

The modules /WMD/XF_WEB_SAVE_LONGTEXT and /WMD/XF_WEB_GET_LONGTEXT were created for web access. The text protocol and all its entries can be queried directly via the process ID.

To enable the development of completely customer-specific applications based on the xSuite framework, the following tables have been converted to e-tables, allowing entries to be maintained in the customer namespace:

The values of domain /WMD/XFAPPL can now be maintained using system table /WMD/WF_XF_APPL with delivery class "E" (transaction SE11).

The method /WMD/CL_XF_BC_ROLE_SH → FACTORY has been adjusted such that the object key required there is determined using table /WMD/WF_XF_APPL.

Background: During RFC communication, ABAP programs call remote functions on RFC servers. During synchronous RFC calls, the server can start communication back to the caller (callback). To do this, the RFC connection that is already open is used in the context of the calling user. Further logon data is not required. These RFC callbacks can pose a security risk if RFC communication takes place from a system with high protection requirements to a less trustworthy system.

The new enhanced xSuite parameter XF_RFC_CALLBACK_PROTECTION_ON can be used to control whether RFC callbacks are allowed.

Callback protection is switched off in the standard system.

The new expression object KOSTL_VUSER can be used in xSuite agent determination to read the agent of a workflow task from the cost center master record. In this case, the SAP user entered in the VERAK_USER field is used as the agent of the workflow task. If this field is not maintained, the system will continue with the next step of agent determination. The expression object can be used in the following xSuite applications: