Adds the two screenshots the embed page was missing, both captured from a Viya deployment with Data Controller embedded as a data-driven content object: - three report parameters (SOME_CHAR, SOME_DROPDOWN, SOME_NUM) reaching one object, with the combined FILTER line and the single matching row in the editor - the object's Options pane, showing the URL as a Web Content property rather than a data source Also documents two things that make an embedded object look broken when the deployment is fine: the URL is an object property and the object needs no data assigned, and an unlicensed / not yet accepted deployment shows its licensing screen inside the object. The debugging section now says the parameter label in the postMessage payload is the key va_parmap matches.
157 KiB
1920x1100px
157 KiB
1920x1100px