Applications → Working with Forms → Customizing Forms → Managing Form Behavior → Using Form Widgets → Using the Embedded Report Widget
The Embedded Report widget shows an SBM report on a transition or state form. Because the report is embedded, users can view relevant information without having to navigate away from the form. For example, when the Embedded Report widget is based on a relational field, fields in a related item can be displayed in the widget.
Defined in SBM Composer as an application report run against a primary or auxiliary table.
Defined in SBM Composer as a report of related items based on specific relational fields.
For details on configuring reports for the widget, refer to Embedded Report Configuration Dialog Box.
When you embed a report defined in Serena Work Center or the SBM User Workspace, you should use a special report URL that contains a report reference name. This preserves the report URL if the process app is promoted to another environment (such as a production environment).
If you do not use the report reference name, the report URL will contain a report ID and field IDs (for Query at Runtime fields). Report IDs and QAR field IDs change when a process app is promoted to another environment, so the report will not work in the new environment.
To reference a report:
"&HasRuntimeParams=1&F_TS_CONTACT="...and bind form field values to the query-at-runtime parameters.
For example, if you added the Contact field to the form, you could bind the value of that field to the &F_TS_CONTACT= parameter, and the report on the form would show all the defects for this contact.
"&HasRuntimeParams=1&F_TS_CONTACT="...and not bind form field values to the query-at-runtime parameters.
In this example, the report engine runs the report as if no value was selected in the query-at-runtime parameter for the report, and that part of the report query is ignored when building the report.
Copyright © 2007–2015 Serena Software, Inc. All rights reserved.