Web Assistant

[former_member747491]

Hey,

as a company, we are trying figure out how to implement and run correctly web assistant. So far, we have followed this manual https://help.sap.com/doc/74bfd245cde048458458f6df5d5cb567/2011/en-US/Web_Assistant_Integration_Guide... - 3.2 Configuration without SAP Web Dispatcher

But we havent solved few items yet

Does it require SSO configuration in order to work correctly?

• we set within transaction /n/ui2/flp_cus_conf) following parameters- attachment (1)
• web assistant showing this message after we open Fiori Launchpad - attachment (2)
• after "Add Standard" is chosen - attachment (3)
• we still dont have all options available in our web assistant - attachment (4)
• what we think we should have as available additional options based on pictures in manuals - attachment (5)

Thanks for your help!

1.png 2.png 3.png 4.png 5.jpg

[Thomas_NOVO]

Hi Kristina

Logon into Manager in a other tab, with the same credentials does not help. It still cannot create any Object.

How do I manage, that SAP Companion is showing me a logon screen for the Manager?

Thanks Thomas

[KristinaKunad]

Hi Thomas,

sorry for the delay - I hope I can now answer your questions:

- Why we can't find the Plugin Parameters with **SEN** and why not the one without the **2**?

• The parameters available in the plugin were put there by the application team and have probably not been updated to the SEN versions.
• dataUrlWPB is used for the custom content scenario, dataUrlWPB2 is used for the extended content scenario

- Does it make a difference if we use **WPB** instead of **SEN**?

• No. WPB parameters are the older names, you can use either one for now. It's better to use the SEN ones, though, to be future-proof.

- Has it the same effect if I use the Parameters as PropertyID and in the ID "PARAMETERS"?

• I am not sure where you would use PropertyID, so I would go with PARAMETERS.

- Why does the disableManualLogin and newWindowSAML Property have no effect?

• You write that there is no SSO configured. Then apparently there is also no SAML call, and also there is no use for these parameters. They are only necessary and applicable when SSO is set up.
• The only way to use Web Assistant without SSO that I know is to open a separate tab, sign in to Manager manually there, and then open Web Assistant in another tab.
• You can request a support ask an expert session if you would like to find out more about the non-SSO options.

- Is there really no possibility to start with WebAssistant without SSO activated?

• See above

I hope that this helps!

Take care,

Kristina

[Thomas_NOVO]

Hi Kristina

Many thanks for these detailed explanation.

Unfortunately it also does not help to login in Manager in the same browser on a separate tab.

Therefore I would like to do a expert session to understand better and to have my setup checked by an expert.

How do I proceed for that?

Thanks Thomas

[KristinaKunad]

Hi Thomas,

sorry to hear that the separate tab doesn't work, that's strange.

Please check the knowledge base article 2651981 (Link) for instructions about the Ask an Expert session.

Take care,

Kristina

[ankur_bijalwan]

Hey Kristina,

I am facing similar issues. Could you please let me know if both Fiori and Manager need to logged in using same user ID or different IDs can also work? I have an login created for Manager with my employee ID as login and I am accessing Fiori using a test ID.

Thanks,

Ankur

[KristinaKunad]

Hi Ankur,

the Fiori Launchpad and the Manager don't need to use the same user ID necessarily. If you are using some sort of broker for the SSO, like the SAP Identity Authentication Service, then that should take care of the different IDs. The Manager needs to be connected to the SAP IAS to draw the right user. If you only have a manual user in the Manager, then you need to sign in separately and in a manual window which is not what we want.

If the issues persist feel free to open a support ticket to have someone take a look at your configuration.

Take care,

Kristina

[KristinaKunad]

Hi Lukas,

yes, SSO is a requirement for Web Assistant (see prerequisites here). To your other points:

• The parameter for version is 2020.latest in your screenshot, but you have the rest of the parameters set to use the extended scenario. Please note this from the manual: Using latest works only for the standard content scenario! Use numeric format for other scenarios. So you need to change this to the numeric value.
• This message is linked to your version parameter.
• Make sure that your user has access to the workarea Tutorials_SAP. This needs to be the extended workarea, not the connected one.
• If there are no Guided Tours, the icon will not be visible. Same for What's New content. Not all modules have Guided Tours and Context Help available.
• You are missing the editing button? If yes, you need an additional parameter: editor=true Or you can add this as a URL parameter (see manual here😞 &help-editor=true . Again, make sure you have the correct permissions for this workarea.

I hope this helps - please mark the question as answered if it does. Don't hesitate to reach out to your CEE if you are a SAP Enable Now Cloud customer to schedule a 1:1 meeting.

Take care,

Kristina

[Thomas_NOVO]

Hi Kristina

I have a similar problem. But I am not sure if simply the SSO (which we don't have) could solve the problem. Because I read from mike about the parameters and played around with parameters SAML, newWindowSAML and disableManualLogin to workaround with a kind of manual login. But none of them makes a difference. I still get the in EXT scenario the Standard UACP content only and in SEN scenario the same messages as @Lukas.

I even tried a SEN scenario with a extended workarea with standard content published (but not fetched) in it. WebAssistant cannot find any content and if I try to add I get the message "creation failed".

But I am also very confused about the parameters. Sometimes it is talked about **WPB** Parameters like dataUrlWPB2 in others documents parameters are with **SEN** like dataUrlSEN2. The same for SERVICE_LAYER_VERSION.

Apart of the confusion in naming I can only find the parameter dataUrlWPB2 but not dataUrlWPB!

To check if this has influence I started to mingle around with the technical names of the parameters direct in the property ID "PARAMETERS". But either with **SEN** or **WPB** and with the **2** and without I get the same results and only UACP scenario is working or the EXT but with standard UACP content.

Please can you clarify:

- Why we can't find the Plugin Parameters with **SEN** and why not the one without the **2**?

- Does it make a difference if we use **WPB** instead of **SEN**?

- Has it the same effect if I use the Parameters as PropertyID and in the ID "PARAMETERS"?

- Why does the disableManualLogin and newWindowSAML Property have no effect?

- Is there really no possibility to start with WebAssistant without SSO activated?
SSO is often not available at the time we start to implement SEN at customer (often we start with local users), so Manual Login becomes crucial for the project timeline of implementation.

Thanks for your help and answer!
Thomas