Last modified by Aurelie Bertrand on 2026/06/22 14:22
Hide last authors
Aurelie Bertrand 42.1 1 * [[Embedding a dashboard in a web page>>doc:Digdash.webIntegration.DD_web_integration.embed_dashboard.WebHome]]
2 * [[Embedding a portlet (graph or other element) in a web page>>doc:Digdash.webIntegration.DD_web_integration.embed_portlet.WebHome]]
3 * [[Configuring a multi-domain integration>>doc:.cross-domain.WebHome]]
jhurst 1.1 4
baudard 1.2 5 (% class="box infomessage" %)
6 (((
Aurelie Bertrand 42.1 7 💡 To ensure that DigDash objects (dashboards, pages, Flows, etc.) integrate correctly, HTML pages must be**hosted and served via a web server**.
8
9 If DigDash objects are embedded in a page hosted on a domain or server other than DigDash’s, specific configurations (CORS) are required. See the page [[Configuring a multi-domain integration>>doc:.cross-domain.WebHome]] for further details.
baudard 1.2 10 )))
11
Aurelie Bertrand 42.1 12 DigDash makes it easy to integrate its [[dashboards >>doc:Digdash.webIntegration.DD_web_integration.embed_dashboard.WebHome]]or objects [[(charts, filters, comments, etc.)>>doc:Digdash.webIntegration.DD_web_integration.embed_portlet.WebHome]] into an existing web page. Depending on the level of customisation required and the context of use, several methods are available:
jhurst 1.1 13
Aurelie Bertrand 42.1 14 * **Via iFrame**: this method involves inserting a complete DigDash dashboard or a chart into an <iframe> tag. Other types of objects (filters, comments, legends, etc.) cannot be embedded.
15 This is a simple solution to implement, ideal for quickly displaying standalone content. The dashboard or page is completely separate from the rest of the site, which reduces the risk of style conflicts with the parent page. However, it offers little flexibility or interactivity.\\
Aurelie Bertrand 18.1 16 * (((
Aurelie Bertrand 42.1 17 **Via embedded JavaScript**: this method allows you to insert a dashboard or specific elements (such as a chart, a filter or a legend) directly into the structure of the web page itself. It offers greater flexibility and interactivity but may present risks of style or script conflicts with the parent page. This can be achieved:
jhurst 1.1 18
Aurelie Bertrand 42.1 19 * by using **custom HTML tags** (<dd-portlet>, <dd-dashboard>) — a simple solution that requires no JavaScript code; suitable for simple pages or where JavaScript is not permitted.
20 * or via **JavaScript scripts**, for more refined and dynamic integration (filtering, interactions between components, conditional display, etc.).
Aurelie Bertrand 18.1 21 )))
jhurst 1.1 22
23 (% class="box" %)
24 (((
Aurelie Bertrand 42.1 25 ℹ**iFramemode: Security constraints**
26 \\Some browsers, such as Chrome, may refuse to pass on cookies from a page embedded via an iframe if that iframe is not on the same domain as the page embedding it. An error then appears in the browser console, regarding a //SameSite //attribute //that //is not defined.
27 The//SameSite// attribute cannot be set on an unsecured cookie. Therefore, the cookie must also have a //Secure //attribute //to //allow //SameSite=None// to be set. And the //Secure// attribute can only be set if the connection is via HTTPS.
28 Consequently, embedding a dashboard page or a viewflow page as an iframe –**if the iframe and the page embedding it are on different domains** – requires the use of an HTTPS connection and the configuration of cookies.
jhurst 1.1 29
Aurelie Bertrand 42.1 30 The following Mozilla document explains this restriction: [[https:~~/~~/developer.mozilla.org/fr/docs/Web/HTTP/Headers/Set-Cookie/SameSite>>url:https://developer.mozilla.org/fr/docs/Web/HTTP/Headers/Set-Cookie/SameSite]]
jhurst 1.1 31 )))
Aurelie Bertrand 23.1 32
33 {{ddchildren}}{{/ddchildren}}