2024.11.05 version update-new aggregate table launch

Ability	Free Edition	Light edition	Professional Edition	Exclusive Edition
Aggregate table	Not supported	10/organization	20/organization	50/organization Aggregate tables are not supported for applications with dedicated storage enabled.

Features

YIDA aggregate table is a computing table formed by aggregation of multiple forms. It has the characteristics of real-time computing and real-time verification, and supports application of other functional modules (forms, reports, Portal data cards, etc.) use.

Usage scenarios

Aggregate tables are applicable to purchase, sale, deposit, reservation, CRM wallet management,Business scenarios such as project cost management, commission calculation, and leave days calculation.

Business logic involves:Input (eg. Warehousing, recharge, holiday days, etc.), sales (eg. Outbound, consumption, leave, etc.), storage (eg. Remaining inventory, balance, remaining holiday days, etc.)For scenarios, aggregate tables are suitable.

• Purchase, sale and storage scenarios

Manufacturing industry, retail industry, construction industry and other industries that involve physical inventory management need a set of inventory management system to realize the whole process management of outbound, warehousing, allocation and inventory, accurately control the inventory data of the enterprise, and reasonably arrange the sales plan, purchase plan and production plan based on the inventory data. Use aggregate tables to calculate the real-time inventory of products through outbound business forms, and perform real-time inventory when inbound and outbound business forms are submitted or approved.Verification,If the outbound quantity is greater than the remaining inventory quantity, the verification does not allow overselling.

• CRM wallet management

The wallet balance of a member account is generally composed of recharge and consumption records. The aggregate table is used to calculate the real-time balance, and then the available consumption quota is verified. When the consumption amount is greater than the wallet balance, unable to submit a consumption order

• Grab an appointment scene

In some event ticketing, restaurant reservation, venue reservation, and product snap-up scenarios, overselling may occur due to high concurrency. Use the aggregation table to set the verification condition,The number of appointments (purchases) is less than or equal to 1.

Create an aggregate table

1. LoginYIDA Workbench, select the application that you want to create an aggregate table, and enter the application building background.
2. Click+No., SelectCreate an aggregate table.

3. Aggregate the calculation results of a table, consisting of column titles and indicators.

Select a data source

1. The data source is the source form for aggregate calculation. If you want to calculate real-time inventory, the data source is the inbound and outbound form.
2. ClickConfigure a data source, select form, and clickOK.

Description:

• You can select the common form and flow chart of the current application.
• You can select a single form or multiple forms.

Configure Association

1. When the data source is multiple forms, you can use the same field in multiple forms as the Association condition to aggregate data of multiple forms;
2. ClickAssociation, select the associated fields in the data source form to form an association group. You can add multiple association groups to an aggregate table.

Instructions

• Field type: you can select single-line text, Button Radio, drop-down Radio, serial number, member, department, value, and date components as associated fields.,Field types in other formats are not supported.
• Date component: when the date component is selected as the matching condition, pay attention to the date precision of the form submission. Date systems with different precision will judge different field values, for example, at 00:00:00 on September 9, 2024 and September 9, 2024, different fields will be determined.

Configure column title

1. By default, the associated field is generated as a column header, and the column header name is the associated field name of the first data source by default.
2. ClickColumn title> Edit
   
   , you can modify the display name of the column title.

Description:

• If the associated field is deleted, the column header field is deleted synchronously.
• If the column header field of a data is null, the data is filtered out and not displayed in the aggregate table.
• When the radio component is used as an associated field: the values of the associated fields are matched and displayed according to the option values of the radio component.
• When members and departments are associated fields: The association is matched by member and Department ID and displayed by member and department name. If the display values of multiple forms are different, it is displayed based on the displayed value of the first data source form.

Configure metric calculation

1. ClickIndicators>Add an item.
2. SettingsIndicator name, use formula to calculateIndicator results, clickOK.

• Indicator name: The name is finally displayed in the aggregate table as a column title.
• Formula calculation: by using mathematical operators (+Add,-Minus,*Multiply,/Except) summary metrics.
• Decimal places: you can set the number of decimal places, thousandths, and percentage display.

Description:

• Metrics refer to words in the data source form.Segment, passingOperationFor the data obtained later, only summary indicators are currently supported.
• The formula operator of the indicator only supports addition, subtraction, multiplication and division between fields, and the indicator can only add numeric fields.
• If only a specific numeric field is filled in the formula, it represents the aggregate calculation of the field.
• When the field involved in the calculation is empty, use 0 for calculation.

Configure filter conditions

1. ClickFilter, select the fields to be filtered, and clickFilter.
2. In the dialog box that appears, set filter conditions and clickOK.

Description:

• Filtering is used to filter data that meets the criteria in a data source and is used for aggregation.
• You can use form business fields and form system fields to filter.
• Flow chart. You can filter by approval results. Only approval results can be selected.The last approval node of the main branch of the process, select node approval commentsAgree"

Configure submit verification rules

1. ClickSubmit verification>Add an item.
2. Configure the submission verification rule for the indicator value.
3. ClickOKComplete the configuration. Submit verification is usually used with metrics to block form submission or logical validation.

Instructions

• Only supported before verifying the formula>,<,=,! =,> =,<=.
• The prompt text for unsatisfied verification can be customized. The maximum number of text is 50.
• You can use variables as indicator fields or numbers.

Publish aggregate tables

1. After the configuration is completed, you can preview the data on the right side of the page.

2. Click in the upper-right cornerSave and publishButton to complete the release.

3. After publishing, you can view the calculation results of the aggregate table.

4. If the release is abnormal due to network exceptions and computing timeout during the release process, a job notification will be sent to an application administrator;

Set permissions on aggregate tables

Aggregate tables support custom permission settings. By default, all members can view all data. Administrators can modify visible members and use aggregate table fields to set data that meets the filtering criteria;

• Permission member: you can select members, roles, and departments under the organization.

• Data range: Use the column field conditions of the aggregate table to determine.

Limits

• Aggregate table dimensions

• A single aggregate table can be configured with up to 10 data sources, 10 associations, and 20 metrics.
• A single data source (form) supports up to 10 filter conditions.
• A single data source (form) can use up to 10 fields to participate in metric calculation.

• Application Dimension

• For applications with dedicated storage enabled, aggregate tables are not supported.

Use aggregate tables

Use aggregate tables in other applications

Aggregate the calculation results of tables. You can use them in forms, reports, and automation.

Usage Channel	Description	Schematic diagram
Data Linkage	Aggregate tables can be linked to data in forms. Conditional rule, optional aggregate table title field on the right Linkage rule, the calculated metric field of the aggregate table on the right
Associated form	Aggregate tables support data Association in association forms.
Report	You can directly select an aggregate table as the data source in the report.
Data Card	In the data card, you can directly select an aggregate table as the data source.
Integration automation/business rules	Integrate automation and business rules to query Aggregated table data Note: you cannot directly modify or delete aggregate table data.
Open API	You can use Open API to query the results of an aggregate table.

View data operation logs

To facilitate administrators to view the calculation and change source of aggregate table result data, the platform provides the change log function of data. You can view the change log of data in the change log operation column of aggregate table.

Precautions

• Filter and verify aggregate tables:If the aggregate table is configured with filter conditions, the submit verification is onlyData that meets the filter criteriaIt takes effect. Data that does not meet the filter criteria will not be submitted for verification;
• Aggregate table publishing:After the aggregate table is published, if the column titles and indicators of the aggregate table are used in fields such as forms or reports, if the aggregate table is modified and republished (modify or delete associations, indicators, etc.), an error may be reported in the form or report where the aggregate table is used. Note that you can modify the build configuration of the reference aggregate table synchronously.
• Several ways to operate data source forms: When you add, delete, and modify data from a data source form through batch import, batch update, batch deletion, automated flow, business rules, and Open API, the update of the aggregate table calculation results is triggered.

• Deleting data from the data source form by deleting new data in this batch in the import record will not trigger the verification judgment of the aggregate table.
  
• By integrating automation and business rules, the data of the data source form will not trigger the verification judgment of the aggregate table.
• OpenApi whether verification is triggered when you operate the data in the data source form depends on the interface parameter configuration. Parameter description:
  

• Use hidden fields in Metrics: if a hidden numeric component is used in metric calculation, always submit is enabled for the component ".
  
• Precision of date component: when the date component is selected as the matching condition, pay attention to the date precision of the form submission. Date systems with different precision will judge different field values, for example, at 00:00:00, September 9, 2024 and September 9, 2024, it will be judged as unequal values.
  
• Option Class component: if the associated field uses an option Field, the associated field is matched and displayed by the option value (not the displayed value).
  

FAQ

• Q: If the aggregate table is published incorrectly, please improve the indicator configuration ".

A:For aggregate table publishing, you must configure calculation metrics.

• Q: When an aggregate table is published, an error is reported: Publishing failed: Only some data sources are used in the metric. Data cannot be aggregated properly. Delete unnecessary data sources or modify metric calculation ".

A: The reason for this problem is that only some data source forms are used in the calculation of indicators. Some data source forms do not need to participate in the calculation of indicators, but association relationships are configured, delete unnecessary data source forms