PieChart How To's

How to's for the PieChart guide.

What Is PieChart?

What Is PieChart?

PieChart is a chart object used on a form to display the ratios and distributions of data using a circular (pie) chart structure.
Each slice represents the percentage or proportional value of a data item within the total.

With this object, users can understand the overall distribution of data at a glance, instead of analyzing complex tables.

What Is It Used For?

• Displaying the percentage distribution of data
• Performing comparative ratio analyses
• Providing clear and easy-to-understand visualizations
• Enriching dashboard and reporting screens

Usage Areas

• Sales distributions
• Department-based ratios
• Status / state analyses
• Category-based data comparisons
• KPI and summary reporting screens

Key Features

• Circular (pie) chart structure
• Separate slice representation for each data item
• Color-distinguished segments
• Tooltip and label support
• Dynamic structure bound to a data source

Notes

• PieChart is a chart type that is used on its own.
• It cannot be used together with other chart types (Bar, Line, etc.) within the same Chart Items.
• It does not have X / Y axes and works entirely on a ratio-based model.

---

How to Use PieChart?

How to Use PieChart?

The following steps explain how to use the PieChart object on a form.

Add the PieChart Object to the Form

1. Open the form design screen
2. Go to the Toolbox panel
3. Locate the PieChart object
4. Add it to the form using drag and drop

Define the Data Source

1. Click the PieChart object
2. Open the Properties panel
3. Select an appropriate data source from the DataSource field
4. Make sure the query result of the data source contains fields suitable for charting

Add PieChart Items (PieChart Types)

1. Click the PieChart Items field
2. Click the Add button
3. Select the chart type you want to use:
   • Bar PieChart
   • Line PieChart
   • Area PieChart
   • Pie PieChart
   • Scatter PieChart
   • Spline PieChart

Note: Pie PieChart cannot be used together with other chart types.

Map the Fields

After adding a chart:

• Argument Field → Category field
• Value Field → Numeric value field
• Color → PieChart color

Map these fields according to your data source.

Configure Visual Settings

• Customize colors
• Configure axes (X / Y)
• If needed, change axes using the Rotate Enabled option
• Enable the Data Loading feature during loading

Save and Test

1. After completing the configuration, click Save
2. Run the form
3. Verify that the chart visualizes the data correctly

Usage Tips

• For large data sets, Data Loading and Cache Settings are recommended
• On dashboard screens, Pie PieChart is ideal for summaries, while Bar/Line PieCharts are suitable for details
• Consider performance when increasing the number of charts

---

What Is PieChart?

What Is PieChart?

PieChart is a form object used to represent results obtained from a data source using graphical visuals (bar, line, pie, etc.) on a form.
With this object, end users can access information more quickly through meaningful and summarized visuals instead of raw tabular data.

The PieChart object is especially preferred in:

• Reporting screens
• Dashboard designs
• Decision support systems

What Is It Used For?

• Summarizing large data sets
• Easily displaying trends and comparisons
• Helping users understand data at a glance
• Making numerical data easier to interpret through visualization

Key Features

• Support for multiple chart types (Bar, Line, Area, Pie, Scatter, etc.)
• Ability to connect to data sources
• Color, axis, and format customizations
• Dynamic and interactive charts
• A structure compatible with dashboards and reporting screens

Where Is It Used?

• Sales reports
• Performance indicators
• Process statistics
• User behavior analytics
• Management dashboards

---

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:

6. 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 State	Description
True	The control is active and ready for user interaction when the form loads.
False	The 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.