Skip to main content

ReportViewer How To's

How to's for the ReportViewer guide.

How to Use ReportViewer?​

How to Use ReportViewer?​

Follow the steps below to add a ReportViewer object to a form and display reports.

Open the Form Design Screen​

  • Open the relevant Form in the development interface.
  • Make sure you are in form design mode.

Add the ReportViewer Object to the Form​

  1. Go to the Toolbox panel.
  2. Locate the ReportViewer object.
  3. Drag and drop it onto the form.

Select the Report​

  • When the ReportViewer is selected, the Property Viewer panel opens.
  • From here, select a report that is defined under the Reports folder in the solution explorer.
  • The selected report will automatically be rendered on the form.

Save and Run the Form​

  • Save the form.
  • When you open the form in the web interface, the selected report will be displayed inside the ReportViewer area.

Usage Scenarios​

  • Displaying process-related reports directly on forms
  • Showing summary reports in admin or management panels
  • Collecting user-specific reports on a single screen

Tips​

  • ReportViewer is very effective in dashboard-like forms.
  • Report performance depends on the query structure of the report itself.
  • Multiple ReportViewer objects can be used on the same form.

Notes​

  • ReportViewer is for display purposes only.
  • Reports cannot be edited through the ReportViewer.
  • Report access permissions are controlled separately at the system level.

What Is ReportViewer?​

What Is ReportViewer?​

ReportViewer is a form object used to display system-defined reports (reports created under the Reports folder) directly on form screens.

With this object, users can review reports directly within the form without navigating to a separate screen, view report outputs, and monitor the information provided by the report in real time.

Main Purposes​

  • Displaying predefined reports on forms
  • Providing users with quick access to report data
  • Presenting process- or form-based reports on a single screen
  • Ensuring centralized and controlled report viewing

Where Is It Used?​

  • Management and analysis screens
  • Displaying process reports directly on forms
  • User-specific report views
  • Dashboards or summary information forms

Key Features​

  • Works integrated with reports under the Reports folder
  • Can be easily added into form design
  • Displays reports without opening an additional page
  • Ideal for read-only report visualization

Notes​

  • ReportViewer displays only predefined reports.
  • Report creation and design are independent of the ReportViewer object.
  • The object is intended solely for viewing purposes and does not include report design capabilities.

How to Use Client Enabled?​

What is Client Enabled?​

Client Enabled is a property that defines whether a form control is active (enabled) on the client side when the form is first loaded.
If it is set to True, the control is immediately usable by the user.
If it is set to False, the control is disabled and cannot be interacted with until a specific condition or rule activates it.

This property is especially useful for controlling the user’s interaction flow and applying dynamic behaviors using the Rule Manager.

What Does It Do?​

The property allows developers to:

  • Control when a form control becomes interactive.
  • Prevent users from entering or changing data until prerequisites are met.
  • Dynamically enable or disable controls based on user input or logic.

Example Scenario — Conditional Activation​

Scenario:
A form contains a checkbox called “I Accept Terms” and a text field called “Signature.”
The goal is to make the “Signature” field inactive until the user checks “I Accept Terms.”

Steps to Implement:​

  1. Select the “Signature” field in the form editor.

  2. In the Properties panel, find the Client Enabled field.

  3. Set the value to False — the field will now be disabled by default when the form loads.

  4. Open the Rule Manager.

  5. Add a new rule:

    Condition:

Action:

  1. Save and publish the form.

Result:​

  • When the form loads, the “Signature” field is disabled.
  • Once the user checks “I Accept Terms,” the field automatically becomes active and editable.

Behavior Summary​

Property StateDescription
TrueThe control is active and ready for user interaction when the form loads.
FalseThe control is disabled at load time and can be enabled dynamically via rules or code.

Notes & Best Practices​

  • Use the Client Enabled property to manage client-side interactivity without requiring server actions.
  • Combine it with Rule Manager to define when and how controls become active.
  • Remember: if server enablement is disabled, the client cannot enable the control even if Client Enabled is set to True.
  • By default, this property is set to True (active).

Summary​

Client Enabled improves form usability by letting developers control when and how users interact with form controls.
It is essential for creating responsive, condition-based form experiences where user actions dynamically change the form’s state.