@SalvadorC94 Can you confirm that this is not related to Mobile Client, rather the use of the ordinary platform portals, forced to load in desktop mode, on a mobile browser?
The steps you followed from the other forum posts show that you are forcing the requestor to by a desktop one and disabling the flags that relate to mobile. It might be a case of some css / html piece not being supported by the mobile browser, requiring a mobile-specific equivalent, but the page code falls into “desktop” conditions because of forced requestor values.
A Pega Web Mashup can be embedded as a gadget on the pages of a Pega composite application and run on a browser. It supports the rendering of user interfaces in the HTML5 document type, which is compatible with modern web browsers.
A Pega Platform application that is embedded on your company web pages as a gadget, without using a portal rule. Pega composite applications do not support all operations that are normally allowed in Pega Platform applications. You can use Pega Web Mashup to build and test a Pega composite application.
Can you show a screenshot of what you mean when you say ’ the dropdowns won’t work on the mobile device.’
Indeed, it is not related to mobile client, but rather forcing it via modifying the requestor when the harness loads.
I didn’t invest more time on the approach described on the other post hence I didn’t do all the debugging part since that approach is not a best practice and may lead to a lot of underlying issues, I instead did the following:
I circumstanced sections inside the harnesses related to mobile to modify the look and feel of the mashup when it loads the case, and from the sections inside the harness I added all the theme I was needing, that way I don’t force anything on Pega, and it works properly.