Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Pega Out-Of-The-Box Buttons Not Displaying In Pega Mobile 4.2



The harness Submit / Cancel buttons are not showing / appearing when accessing the system via a mobile device.

Error Messages

No errors.

Steps to Reproduce

Log into application (with Pega Mobile installed) using a mobile device, and create a new case.

Root Cause

An application specific verison of the desktop perform harness had been saved into the application specific classes.

The perform harness has desktop and mobile specific versions.  The desktop version does not use the harness footer buttons which are used by the mobile version.

The standard Work- perform harnesses are in the rulesets:

Pega-Mobile_mobile    this is the mobile specific version including the buttons:

Pega-EndUserUI          this is the desktop version without harness footer buttons.

When you have not saved a custom perform harness into your application ruleset then then logging into the desktop will rule resolve to the desktop version (since the _mobile rulesets do not get included for a desktop user), and the mobile version will be rule resolved for the mobile user (since _mobile rulesets are automatically added to a mobile user profile).  

If you save a version of the desktop harness into your application class structure then this will rule resolve above both of the out of the box harnesses for desktop and mobile users, and the buttons will not be displayed (since they do not exist on the desktop version of the harness).


The possible solutions to this are:
  • Delete the application specific perform harness and use the standard Work- ones.  These are already developed to support mobile.
  • If you need a custom perform harness for the application the you need to also need to have a mobile version of your perform harness at the same level as the desktop version including the buttons.  This can be included in one of two ways:

1.    Save the mobile version into you application specific ruleset which would be <Application Ruleset Name>_mobile.  Appending "_mobile" to an existing ruleset name will mean that ruleset will be automatically included in a mobile users stack when they log in without it having to be added to the application / access group (similar to how localization works).  Information about creating and configuring a mobile specific ruleset is detailed in the following PDN article.

2.    If you do not have a mobile specific ruleset or feel that creating one is not nessasary (if you do not have or will not have many rules that require mobile specialization for example) then you can circumstance the perfrom harness for mobile instead.  There are some notes on this in the above article.  We would suggest circumstancing on the property pxRequestor.PxDeviceType and testing for a value of either phone or tablet.


Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us