EWM and Personas : Menu ID and Slipstream versus EWM_Mobgui

[Emmanuel_Miret1]

Hello Community,

I have a question.

We are currently upgrading from S/4 2019 Personas SP16 to S/4 2023 on prem with Personas SP18.

I have 2 questions:

1. I've tested the new feature to color a specific button on EWM RF menu described in chapter 5.1.1 in the PDF .

It's working fine but I tried to search in scripting if I could find the MENU ID to trigger a script based on menu item. I couldn't find it. I'm currently using the text of the button:

2. Slipstream versus EWM_Mobgui

All my end-users are on S/4 2019 working with Slipstream without any problem.

We are upgrading to S/4 2023, do I have to move to EWM_mobgui or stay on SE engine?

I couldn't find any feature comparison between the 2 version. And when I testing ewm_mobgui, I don't see any benefit compare to SE. (I do understand that's an improvement compared to old ITS mobile).

Thanks and best regards,

Emmanuel.

[Tamas_Hoznek · Accepted solution]

The menu ID is not an exposed control property accessible for the scripting Inspector. It is built behind the scenes by the RFUI-specific Personas coding, using the control ID and the button's dynamically changing function (the command that is sent to the screen processing when pressing the button). This is done to create a unique identifier for the flavor change list.

As for having to migrate your flavors from SE to mobgui, the general answer in my opinion is no. If they work fine as they are and your users are happy with them, I see no reason to change the status quo.

[Emmanuel_Miret1 · Accepted solution]

Thanks Tamas for the asnwer.

About SE vs EWM_Mobgui, could we have a feature comparison?

Thanks,

Emmanuel.

[Tamas_Hoznek · Accepted solution]

From Personas point of view, mobgui is essentially webgui, so for the most part, this should still apply: https://community.sap.com/t5/technology-blogs-by-sap/choosing-slipstream-engine-or-sap-gui-for-html-...