Solved

How to display NinTex Widget in SharePoint online modern page

  • 13 March 2019
  • 5 replies
  • 32 views

Badge +3

We have a SharePoint Online classic page.

It contains two pageviewer webparts, one links to 
https://go.promapp.com/<ourCompany>/sharepoint/widget.aspx?notifications=true&logo=true&recent=true&favourites=true&search=true&width=-1
And the other links to
https://go.promapp.com/<ourCompany>/Dashboard/Governance

 

We are transitioning to Modern SharePoint pages for our content (which use the SPFx framework, so we can't use the old webparts).

In modern sharepoint pages the Embed webpart should achieve the same function...... BUT even though we have enabled "Site settings/Html field security" to allow embeds from go.promapp.com the Modern SharePoint pages won't accept the URLs above.

Does anyone at Promapp or in the forum know how to make this work ?

We suspect that there is something on the Promapp end which is causing the modern sharepoint page Embed webpart to fail and not allow the URLs to be used. Possibly too many redirects or some other non-obvious issue.

Your help would be appreciated.

Many thanks

icon

Best answer by jamesRoss 17 March 2019, 22:24

View original

5 replies

For the Promapp pages, you are best to use the iframe to display them on your SharePoint pages.



 



Try the following code:



<iframe width="260" height="190" src="https://go.promapp.com/<yourcompany>/Sharepoint/Widget.aspx?notifications=true&search=true&recent=true&favourites=false" frameborder="0" allowfullscreen></iframe>

Badge +3

Hi @jamesRoss 

Thanks for the post.

I'd tried something similar but your iFrame syntax worked on a SharePoint Online Modern page.

The only thing that might have helped is that the "Site settings/Html field security" for the site collection the page is in may not have had time to synchronise, and it may be that which was causing my issue.

 

Anyway - we've not got a modern sharepoint page with a go.promapp.com iframe in it.

 

Many thanks

Badge +3

We'll we've revisited this again 3 years on.





Same problem , no resolution.





The SharePoint Online Modern page Embed web part rewrites the URL of the iframe from





<iframe width="200" height="394" src="https://au.promapp.com/CompanyName/sharepoint/widget.aspx?logo=true&notifications=true&search=true&recent=true"></iframe>





to





<iframe width="200" height="394" src="https://au.promapp.com/CompanyName/sharepoint/widget.aspx?logo=true&amp;notifications=true&amp;search=true&amp;recent=true"></iframe>





If you attempt to go to



https://au.promapp.com/CompanyName/sharepoint/widget.aspx?logo=true&amp;notifications=true&amp;search=true&amp;recent=true





It only displays the NinTex Promapp logo.





From the ProductTeam it would be great if you changed the code of widget.aspx just a little to interpret this URL (mangled by Microsoft) or gave us another way to pass the same info to the widget.aspx page.



Badge

Similar issues here, can’t get it to work. Logged a case with support and no help yet. Will share if I ever get it solved, please do the same :-)

Badge +3

Hi @TonyaJean @jamesRoss 

One of our Infrastructure guys has looked into why the 

<iframe width="200" height="394" src="https://au.promapp.com/CompanyName/sharepoint/widget.aspx?logo=true&amp;notifications=true&amp;search=true&amp;recent=true"></iframe>

When put into the Embed webpart in a Modern SharePoint page doesn’t work.

What he found was that the SharePoint page iframe goes into a never ending loop going to Authenticate ASPX (you can see this in the Developer mode of Chrome).

More specifically he found that the au.promapp.com site is sending the following http header is set as follows    ‘X-Frame -Options SameOrigin’ . This means if our Iframe was on a page on au.promapp.com it would work fine. He said there used to be 3 x-frame options but that one of them was removed from IIS some time ago meaning now the only options are Deny or SameOrigin. The other option would be for au.promapp.com NOT to send the X-Frame header at all which may or may not solve the problem for us.

 

SO my challenge to the Promapp Product team - recreate this issue, and help us out with a solution.

NOTE this only happens for the /SharePoint/widget.aspx include NOT the other includes with minimode in their urls.

 

Full quote of what my internal infrastructure staff member sent me

Testing has shown the issue relates to a remote server configuration hosted by Promapp. Response headers indicate they have set the 'X-Frame -Options' to 'SameOrigin'. This is a Cross-Origin Resource Sharing(CORS) security mechanism, which explicitly prevents the browser from requesting resources, unless they come from the same origin/domain that tries to load them. This results in a redirect loop when the iframe is embedded in SharePoint, or any externally hosted domain/website.

Reply