unable to launch case using Mashup in Internet Explorer
Hi,
I'm trying to launch case using Mashup in Internet exploerer. It works fine in Chrome and Firefox and fails in IE.
When accessed in IE, I could see recursive requests with 303 response in the fiddler and causing "This page can't be displayed" on the browser. When i cleared browser cache, it worked sometimes but it started failing second time trying to launch.
if we add webhost name to the trusted sites in the IE, it starts working but we can't go with this configuration. Am i missing any configurations on the server/mashup level?
sample script used for validating:
<script src ='http:// Proprietary information hidden:9080/prweb/PRServlet?pyActivity=pzIncludeMashupScripts'></script>
<script>
function preparePegaAParams(gadgetName) {
var pegaAParamObj = {};
pegaAParamObj.UserIdentifier="[email protected]";
pegaAParamObj.Password="aW5zdGFsbA%3D%3D";
pegaAParamObj.pzSkinName="pyEndUser";
return pegaAParamObj;
}
function launchOnlineHelpProcess() {
Hi,
I'm trying to launch case using Mashup in Internet exploerer. It works fine in Chrome and Firefox and fails in IE.
When accessed in IE, I could see recursive requests with 303 response in the fiddler and causing "This page can't be displayed" on the browser. When i cleared browser cache, it worked sometimes but it started failing second time trying to launch.
if we add webhost name to the trusted sites in the IE, it starts working but we can't go with this configuration. Am i missing any configurations on the server/mashup level?
sample script used for validating:
<script src ='http:// Proprietary information hidden:9080/prweb/PRServlet?pyActivity=pzIncludeMashupScripts'></script>
<script>
function preparePegaAParams(gadgetName) {
var pegaAParamObj = {};
pegaAParamObj.UserIdentifier="[email protected]";
pegaAParamObj.Password="aW5zdGFsbA%3D%3D";
pegaAParamObj.pzSkinName="pyEndUser";
return pegaAParamObj;
}
function launchOnlineHelpProcess() {
var PegaAParamObject = null;
PegaAParamObject = preparePegaAParams("PegaGadget");
pega.web.api.doAction("PegaGadget", "createNewWork", "PegaSample-Task", "BasicProcess", PegaAParamObject);
}
</script>
</head>
<body>
<div data-pega-gadgetname ='PegaGadget'
data-pega-action ='createNewWork'
data-pega-action-param-classname ='PegaSample-Task'
data-pega-action-param-flowname ='BasicProcess'
data-pega-action-param-model =''
data-pega-isdeferloaded ='true'
data-pega-applicationname ='PegaRULES'
data-pega-threadname ='STANDARD'
data-pega-systemid ='pega'
data-pega-resizetype ='stretch'
data-pega-url ='http:// Proprietary information hidden:9080/prweb'
data-pega-redirectguests ='true' ></div>
<button onclick="javascript:launchOnlineHelpProcess()" > launch case </input>
Thanks!
***Updated by moderator: Lochan to add Categories; tagged SR Exists***
Pegasystems Inc.
IN
Hi Ravi,
HTTP 303 is a standard HTTP response to redirect the browser to a specific URL. And in the SR tagged I could see that the suggestion was made to use domain instead of IP address and it started working.
JFYI, similar issue was reported for Linkedin integration and we have set the Public Link URL to DNS URL and the built the Call Back URL using
@(Pega-ProCom:PegaProComUtilities).getPublicLinkURL() and parsing pxReqURI off pxThread page.
This resovled the issue and the traffic is correctly redirected back.
Regards,
Sudhish OP