Hi,

You can pass the parameters as 'Contact name' by using PegaA_params="{ContactName:'ParamValue'}" in your gadget in div tag and use the 'ContactName' parameter as filter in the section which you want to display in external web app.

Thanks,

Habeeb Baig

You can use web mash up formerly known as IAC.

Please refer https://pdn.pega.com/embedding-application-pega-gadget-using-pega-web-mashup

OK, It seems that mash up is the way to go. Let say I have a gadget that is included in a mashup that is displayed inside a div tag, and the gadget displays information based on the parameter that is passed from the user. I assume that I can use the PegaA_params to pass that parameter. Now how do I know the correct name of the parameter to pass?

Thanks,

Henri

You should consider parameters as static, are you expecting dynamic parameters from other application?

I am expecting one parameter from the other application, which is in this particular case a contact name that needs to be inputted to the Pega Gadget. Then I would expect that the output would be shown on the PEGA gadget.

Typically when you click on button in your web application, you can design a javascript function in your system to collect input parameters and you can them as arg in below format:

function paramObjectToPegaApp() {
    var pegaAParamObj = {};
    pegaAParamObj.inputKey1="someValue1";
    pegaAParamObj.ContactName="someValueFromWebApplication"; //if needed fill these input fields by making calls to other systems 
    pegaAParamObj.AccountNumber="someAccoutNumber";
    return pegaAParamObj;
}

Later you can use

  var PegaAParamObject = paramObjectToPegaApp();  
  pega.web.api.doAction("GadgetName", "createNewWork (or appropriate action)", "PegaSample-CustomerRequest", "pyStartCase", PegaAParamObject);

There are huge enhancments/things are not explored in mashup. I would suggest to spend going through below link which will help you in building your requirements in correct way.

https://collaborate.pega.com/discussion/pega-web-mashup-iac-and-browser-backforward-navigation-button-behavior

Thank you,

That makes a lot of sense. Please pardon my lack of knowledge on Pega.

pega.web.api.doAction("GadgetName", "createNewWork (or appropriate action)", "PegaSample-CustomerRequest", "pyStartCase", PegaAParamObject);

What would be the action if we want to display the result of a query based on the input on PegaAParamObject. The html addition is the following:

<script src ='PegaInternetApplicationComposer.js'></script>
<div data-pega-gadgetname ='PegaGadget'
data-pega-action = 'display'
data-pega-action-harnessName='SFAPortalContacts'
data-pega-className='PegaCRM-Portal-SFA-SalesRep'
data-pega-applicationname ='GISFW'
data-pega-threadname ='STANDARD'
data-pega-systemid ='pega'
data-pega-portalName = 'SFASalesRep_Web'
data-pega-event-onload = "init"
data-pega-url ="http://x.x.x.x/prweb/[email protected]&action=display&harnessName=SFAPortalContacts&className=PegaCRM-Portal-SFA-SalesRep&readOnly=true&label=SFAPortalThread&tabIndex=2&portalThreadName=STANDARD&portalName=SFASalesRep_Web&amp;" ></div>

And the gadget displays like the attached .png file.

Thank you again.