View (report component)

The report component type View specifies the framework structure of the reports. You can use the View component, for example, in print reports to define the chapter structure.

Configuration:

Property

Description

Reported objects

This property determines for which objects a view is reported. Reference an attribute or configure a query here. These are evaluated on the context object(s). If neither an attribute is referenced nor a query is configured, the context objects are used.

One chapter per object

If the option is activated, a chapter is created for each reported object. Otherwise, only one chapter is created for all objects of the view.

Main chapter

This option is relevant for print reports.

If the option is activated, a new main chapter is created for the view. A main chapter is a first level chapter (heading 1).

By default, the option is disabled, which causes the view to create subchapters under the chapter of the parent view.

Display

Categories can be referenced under this attribute. This can limit the visibility / execution.

Most application scenarios require category and access control related visibility.

The logic of the evaluation is as follows:

  1. If at least one category is specified, the object must be an instance of that category. Otherwise, no evaluation of the category are carried out

  2. If at least one user group is specified, the current user must be a member of at least one of these user groups

  3. If at least one Access Control List is specified, the user must have the View permission in the Access Control List

  4. If at least one condition component is specified, at least one condition must apply.

If this logic is not sufficient, a differentiated logic can be configured via the condition components.

Layout This shows which layout components are configured under the view. You also have the option here to reference or create layout components via the text box or the buttons to the right of the text box.

Content

This shows which components or attributes are configured under the view that will be evaluated as content in the Portal. You also have the option here to reference or create components or attributes using the text box or the buttons to the right of the text box.

Report empty chapters / views

If this option is activated, the view / chapter is reported even if its content does not provide content for the reported objects. Thus, the (chapter) structure is preserved.

Report working draft

If this option is activated, the content of the View component is always displayed in the working draft in the Portal, regardless of which version is displayed in the Portal.