Hi, 

Please share us pega version used ?

Thanks.

Hi Community,

Any updates on whether the mashup Java scripts in 7.3.1 collide with popular JS frameworks?

Cheers Lars 

A web mashup requires a JavaScript file to be served in the host document. This JS provides all the mashup management functionality.

1. An activity "pzIncludeMashupScritps" is created. The mashup HTML snippet has a <script> tag whose src points to pzIncludeMashupScritps activity. 
2. This activity reads the content of a Rule-File-Text "pzPega_webMashup.js" and returns the content to the client.

The webMashup JS looks in the DOM for DIVs with class="pega-mashup". For each such DIV, it creates an IFRAME element and appends it as a child to that DIV. 
The src of the IFRAME is constructed from the attributes on the DIV. 
(Further functionality e.g., resize logic will be added into this JS file)

Rules Involved

Rule-Obj-Activity "pzIncludeMashupScritps"
Rule-File-Text    "pzPega_webMashup.js"
Rule-Obj-Activity "pzAddPortalLayouts"

1) Is the observation correct that the Pega JS may collide with JS on the main document?

Ans:   which part of pzPega_webMashup.js your thinking that it’s colliding with other JS?

2) Is there a way to just include the iframe w/o any loading script?

 Ans:  I don’t think so we can achieve this requirement in Mashup right now .

Thanks,

Arun

Hi Arun,

Thanks for looking into the matter. Indeed, the mashup loading activity assembles like half a dozen JS files and the answer to the HTTP request has got a size of ~200kB JS code.

Customer claims that within his own (complex) web UI, the "$" variable gets modified by Pega mashup and the document loading event gets modified (not sure if this is body.onload()). Hence the customer refuses to include the mashup snippet and wants a clear separation of applications by embedding only an iframe w/o any script around it.

It is quite difficult to validate the statements as the JS code is obfuscated/compressed. Certainly, there is a "$(root)." fragment in the JS code and there is a "D.onload=function()" - whatever object "D" represents at this point at runtime...

So is it possible that the mashup JS interferes with other JS frameworks at certain points?

Cheers Lars

Thanks for the comment! Unfortunately, we already tried with an iframe inside an inframe and it does not work, the layout control gets lost. In addition, it creates more deployment/maintenance effort as the outer iframe have to come from some extra WAR. Hence this situation challenges the Pega position that mashup is an easy and recommended way to bring cases into other applications.

I cannot easily reproduce the error as I don't have access to the respective environment. Customer was given the snippet and replied in a bigger meeting rather angrily that the outer mashup JS interferes with their JS. Customer insisted that only a plain iframe snippet w/o outer JS would be acceptable. Changing code at the outer, consuming application is not possible either as this is kind of a "given product" as well.

So if the mashup actually uses JQuery and JQuery is a widely spread framework, what is Pega's plan to cope with version differences? In the "Java part" for example, Pega repackages public framework/helper JARs with a com.pega prefix for differentiating classes from class loaders perspective.

In-order for mashup to load in the host page, it is required to have some pega bootstrapping JS loaded in the host document upfront which will do the job of parsing the host document for mashup snippets and accordingly rendering mashup gadgets (creating iframe etc...).