Salesforce Mashup
We are doing a POC to demonstrate Salesforce Pega mashup. We have 2 ids - one is pega operator id for mashup and the other is the salesforce id to login to salesforce portal.The mashup is working only if we create an operator id in Pega for each of the salesforce id created. The WO submitted through salesforce also has the Salesforce operator id as pxCreateOperator. Please help me in understanding what is wrong at my end.
Thanks in advance.
IndhuS
***Edited by Moderator, Maryrita: moved to Product Support from PegaBuzz***
Pegasystems Inc.
IN
Hello IndhuS,
I understand that you have Salesforce ID and Pega ID. You are able to work with mashup only when you have the salesforce ID exist in Pega Operator ID list. Now, you have the problem if a work object is created in salesforce then the respective pxCreateOperator property is holding the salesforce ID instead of Pega ID. is my understanding correct ? if no, Please elaborate the problem you are facing.
If yes, what is the design approach you followed to create a work object in pega from sales force.
Thank you,
Bank of America
US
Hi Cherb,
I have a same type of issue. In our application we have a web mashup where we expose the application to the internet users in a tab of a webpage. Users don't require to have operator ids in pega to access the application and we have a single static operator id configured in in IAC gateway for web users. All the cases get created through mashup would have that static operator id as the pxCreateOperator. We want to do the same with Salesforce. We used the pega Salesforce extender to mashup pega application. However unlike web mash up, it is not working unless if we create the salesforce operator ids in pega(with the same name). I am wondering is this how pega salseforce extender is designed or are we doing something wrong. We would like if we not have to create salseforce ids in pega.
Thanks
Pegasystems Inc.
US
Just curious, are you guys following the new way of integration as described here: https://docs-previous.pega.com/installing-and-configuring-pega-extender-salesforcecom
Pegasystems Inc.
US
The PRPC Process Extender for SFDC by default sends the UserIdentifier parameter using the users SFDC user id.
The new way to include PRPC 7.2.2 within SFDC, the link that Kevin Posted, is far more flexible and will allow you to specify a user id within a parameter attribute:
data-pega-action-param-parameters="{UserIdentifier:'[email protected]'}"