Pega platform 24.1.3, original mashup from 7.2, embedding via iframe in Salesforce CRM

User Experience
, , , ,
1

Hi, We have an existing Pega Mashup script embedded as an iframe in a Salesforce CRM app. The original mashup was created with Pega 7.2; our current Pega platform is 24.1.3. Using the Designer Studio, we generated a new Web Mashup via “Create new channel interface” in the 24.1.3 environment.

The generated mashup script looks almost identical to the old script except for the presence of a data-pega-channelID attribute (the old script didn’t include it). To minimize changes, I took the new script’s data-pega-channelID attribute and added it into our existing iframe script. We plan to promote this change to all environments and set the data-pega-channelID value as an environment-specific variable (i.e., generate the new channel ID in each environment and update only that attribute per env).

Question is by adding just the data-pega-channelID attribute to the old mashup script, have we effectively moved to the “new” mashup version created in 24.1.3, or is a full script replacement required to be considered upgraded? Thanks!

2

@Jey2705

To be considered upgraded, you should replace the old mashup embed with the full script generated from the Web Mashup channel interface, not just add data-pega-channelID. That attribute only points the embed to a specific channel configuration; it does not update the rest of the bootstrapping code, supported attributes, or any newer runtime expectations. So adding data-pega-channelID to the 7.2-era iframe may work in some cases, but it is still the legacy embed and won’t reliably reflect the 24.1.3-generated mashup behavior. Generate the mashup code in each environment in Pega, deploy that exact code into your Salesforce iframe, and then parameterize only the environment-specific values (including the Channel ID) within the new script

3

Thanks @Sairohith for your response. Appreciate it!