Question
Rulesware LLC
SV
Last activity: 13 Feb 2024 11:10 EST
Dropdowns not working on Pega Web Mashup when accessing via mobile device.
We have a Pega Web Mashup that is configured to load as if you were opening the mashup in Desktop always following these guides:
Disable mobile view | Support Center (pega.com)
Disable mobile view (Part 2) | Support Center (pega.com)
(We need to avoid showing mobile devices specifics as part of our requirement)
If I do what those articles explain, the dropdowns won't work on the mobile device.
Is there an alternative to only load Desktop but the controls to behave like in mobile?
(Pega version 8.6.3)
Accepted Solution
Updated: 13 Feb 2024 11:10 EST
Rulesware LLC
SV
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.
Thanks for the help!
Updated: 6 Feb 2024 5:07 EST
Pegasystems Inc.
GB
@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.'
Did you carry out any debugging?
Pega web mashups for embedding traditional UI in external web pages
@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.'
Did you carry out any debugging?
Pega web mashups for embedding traditional UI in external web pages
Mashup issues with collapsible controls
Glossary: P > Glossary for Pega Web Mashup:
P > Pega composite application
Can you confirm that you went through the Checklist for logging accessibility issues ?
@Sam Alexander would you be able to offer any insight here?
Accepted Solution
Updated: 13 Feb 2024 11:10 EST
Rulesware LLC
SV
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.
Thanks for the help!