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

IAC "getGadgetData" action does not work

SA-12708

Summary



When getGadgetData is called to retrieve the operator ID inside another activity, the getGadgetData call never happens.


Error Messages



Not Applicable


Steps to Reproduce



Use "getGadgetData" action.

For example:

var opName = pega.web.api.doAction("CreateWork", "getGadgetData", ".pxCreateOpName");

Root Cause



The PegaInternetApplicationComposer.js file should not be used when testing gadgets within PRPC portals. The PegaInternetApplicationComposer.js is a static content bundle made up of the following Rule-File-Text Javascript files:

pega_yui_utilities
pega_yui_extensions
pega_tools_hashtable
SafeURL
PegaCompositeGadgetMgr
pega_ui_property



When imbedding gadgets into PRPC portals for testing include only the PegaCompositeGadgetMgr, the rest are already present.

<pega:static type="script" app="webwb" >
  <pega:file name="PegaCompositeGadgetMgr.js" />
</pega:static> 

 

Resolution



Change gadget code to only include PegaCompositeGadgetMgr.js. This resolves the issue with getGadgetData.

Note: Remember that getGadgetData requires the usage of Data Fields.
Suggest Edit

Published August 12, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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