Launching Desktop Assistant

[former_member107258]

Hello,

I have a desktop assistant subtype group and I am adding the groups called application names I have desktop assistant learning contents for. Under these groups, there are desktop assistant learning contents. This is how my desktop assistant hierarchy is. But when I added new contents under existing groups, it didn't show the new contents. I needed to click on Desktop Assistant link text in Manager to download new .senl desktop assistant file. Do I need to download it everytime when I add a new content?

Thank you.

[DirkManuel]

The structure of the DA Group does not matter at all. Content is displayed by context.

Make sure you actually generate your DA. You can test it from Producer.

You do need the SEN Launcher, but assuming you are a cloud implementation, don't use the Start Link from Producer (or Manager, I think). I believe the link you need ends in .inav, but I'm away from my PC at the moment so I can't check.

[DirkManuel]

The start link should be something like:

https://client.enable-now.cloud.sap/wa/{workarea}/~tag/published/group/GR_XXXXXXXX/.inav

where GR_XXXXXXX is the UID of the DA Group

[former_member107258]

Okay I used the program that downloads when clicking on this starting link, everytime I generated DA from producer, it reflects to that downloaded program. Thank you so much.

[ShaneLipke]

Hi Dilara,

Yes if you add new content to the DA you need to generate the DA files again, as mentioned by Dirk, and should then test locally using Producer. Once you are comfortable that the new content is appearing, you should synchronise the new content and generated DA files to Manager and ensure that the content is published. If end users are accessing DA they will not initially see the new content until they restart DA or refresh the DA cache. The reason for this is that details of the new content are stored in a file that is created each time that you generate the DA files and this new version of the file must be downloaded to the end users PCs. This occurs when starting DA or refreshing the DA cache.

Regards
Shane

[former_member107258]

Hi,

I understand, thank you so much for your answer.

Kind regards.