This article explains the step-by-step process to create an App Data Function after your form is ready and published.
Note
Make sure your Form is published, and Data Table Functions are already created before proceeding.
1. Before creating an App Data Function, design your required form in the application. Publish the form.
2. Once the form is published, go to App Settings → Events → Data Functions
3. Click on + Add Data Function. This opens the App Data Function configuration screen.
4. Provide a unique name for the Data Function. Using clear names makes maintenance easier. Examples:
5. You must now select:
6. These define when the Data Function should execute.
Example
Leave Application Workflow
- Step 1: Employee submits a leave request
- Step 2: Manager approves or rejects
- Step 3: HR acknowledges
You can trigger different Data Functions at different steps based on the business requirement.
7. Now choose how the data should be captured:
8. Click Next to move to the Conditions and Data Table mapping stage.
9. On the Conditions page, select the Data Table to which the application data should be mapped.
10. The dropdown lists only Data Tables available within the same workspace as the application.
11. Choose the type of operation to perform on the selected data table.
12. After selecting the function type, click on Configure. This opens the Element Mapping screen.
13. Element Mapping creates a direct relationship between:
This ensures:
This section explains how to map individual form fields and grid-based records to their corresponding data table fields, depending on whether the data is captured as a single value or as multiple records.
Used for direct field-to-column mapping.
Example
- Application Field → Employee Name
- Data Table Column → Employee Name
Used when mapping grid/sub-form data.
Example
- Expense Grid → Expense Data Table.
- Each row in the grid becomes a separate record in the table.
Conditions in App Data Functions act as logical rules that define:
They allow you to apply decision-based logic before data is saved into a data table.
Conditions are configured:
They act as a control gate between: Application → Data Function → Data Table
All employee records must be stored in a Master Employee Table. Additionally, department-wise records must also be stored separately.
Conditions Applied:
If Department = Product
If Department = Marketing