You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/resources/control-flow/user-interactivity/forms/form-actions/reset-form-field.md
+4-64Lines changed: 4 additions & 64 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,73 +8,13 @@ sidebar_position: 1
8
8
---
9
9
# Reset Form Field [Action]
10
10
11
-
This action allows you to reset a value for the Form widgets. This is helpful in clearing out any previously entered data and allows users to start fresh.
11
+
The **Reset Form Field**action allows you to reset values in form widgets. This is especially useful for clearing previously entered data and giving users a clean slate.
12
12
13
-
For example, If a form has been successfully submitted, it may make sense to clear out the form fields so that the user can enter new data if they want to submit the form again.
13
+
For example, after a form is successfully submitted, you can use this action to clear the input fields—making it easy for users to enter new information for another submission.
14
14
15
-
<div style={{
16
-
position: 'relative',
17
-
paddingBottom: 'calc(56.67989417989418% + 41px)', // Keeps the aspect ratio and additional padding
Follow the steps below to add this action to any widget.
44
-
45
-
1. Select the **Widget** (e.g., Button, etc.) on which you want to add the action.
46
-
2. Select **Actions** from the properties panel, If it's the first action, click **+ Add Action** button. Otherwise, click the "**+**" button below the previous action tile (inside *Action Flow Editor*) and select **Add Action**.
47
-
3. Search the **Reset Form Field** (under *State Management*) action and select the widget you would like to reset.
48
-
49
-
You can reset the same types of widgets in a single action only. e.g., multiple *TextField* widgets.
50
-
51
-
<div style={{
52
-
position: 'relative',
53
-
paddingBottom: 'calc(56.67989417989418% + 41px)', // Keeps the aspect ratio and additional padding
Copy file name to clipboardExpand all lines: docs/resources/control-flow/user-interactivity/forms/form-actions/set-form-field.md
+34-65Lines changed: 34 additions & 65 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,73 +8,42 @@ sidebar_position: 0
8
8
---
9
9
# Set Form Field [Action]
10
10
11
-
This action allows you to set a value for the Form widgets. For example, you could use this action to auto-populate a form based on a user's previous submission.
12
-
13
-
You could also dynamically update a dropdown menu based on a user's previous selection, such as showing relevant cities based on a selected country.
14
-
15
-
<div style={{
16
-
position: 'relative',
17
-
paddingBottom: 'calc(56.67989417989418% + 41px)', // Keeps the aspect ratio and additional padding
The **Set Form Field** action allows you to programmatically populate or update the value of any input widget—like a TextField, Dropdown, or other form elements—at runtime. This is especially useful when you want to quickly fill or modify user input fields based on user preferences (e.g., saved addresses) or pre-stored information.
40
12
41
-
## Adding Set Form Field action
42
-
43
-
Follow the steps below to add this action to any widget.
44
-
45
-
1. Select the **Widget** (e.g., Button, etc.) on which you want to add the action.
46
-
2. Select **Actions** from the properties panel. If it's the first action, click the **+ Add Action** button. Otherwise, click the "**+**" button below the previous action tile (inside *Action Flow Editor*) and select **Add Action**.
47
-
3. Search the **Set Form Field** (under *State Management*) action and select the widget you would like to set.
48
-
4. Now, you can set its value directly or from a variable.
49
-
50
-
<div style={{
51
-
position: 'relative',
52
-
paddingBottom: 'calc(56.67989417989418% + 41px)', // Keeps the aspect ratio and additional padding
-**Use Saved Address:** If a user toggles "Use Saved Address," you might set the Full Name, Street Address, City, and ZIP Code fields to values pulled from a user profile or database.
16
+
-**Edit Existing Data:** When navigating to an "Edit Profile" page, you can auto-populate the TextFields with the current user info so they only change what’s needed.
17
+
-**Auto select Country/State Dropdown:** Automatically select the user's country and state based on location services or their account settings.
18
+
19
+
:::
20
+
21
+
While adding the Set Form Field action, select the target widget (e.g., `TextField`) and assign a value—this could come from a variable like `fullName` in your backend, app state, or page parameters.
If you need to update several widgets (such as a TextField and a Dropdown), use a separate Set Form Field action for each and specify the appropriate value.
You can also set additional preferences like whether the field should be focused and how the cursor should behave using the **Focus Field When Set** option. When you enable the option, it automatically sets the focus on the field once its value is assigned.
32
+
33
+
This is helpful in scenarios such as an “Edit Full Name” switch—when turned on, the field preloads the existing name and positions the cursor for immediate editing.
34
+
35
+
36
+
When **Focus Field When Set** is enabled, you can set one of the following **Cursor Position**:
37
+
38
+
-**End**: Places the cursor at the end of the newly filled text, letting the user continue typing from the last character.
39
+
-**Start**: Positions the cursor at the beginning of the text.
40
+
-**Highlight**: Selects (highlights) the entire text, letting the user immediately overwrite it.
41
+
-**Preserve**: Maintains the cursor location as it was (if any), which is useful when the user is already typing and only part of the text has changed.
Copy file name to clipboardExpand all lines: docs/testing-deployment-publishing/branching-collaboration/branching.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ Branching creates a separate copy of your work, so you can add new features with
14
14
Suppose you have an eCommerce app and you want to add a new feature, such as a product recommendation system. Instead of incorporating it directly into your `main` branch and potentially causing problems, you can create a branch to work on this new feature in isolation. Once it's complete, you can integrate it back into the `main` branch.
15
15
16
16
:::info
17
-
This feature is only available for Pro, Teams and Enterprise users.
17
+
While all users can access the branching menu and create commits, only **Pro**, **Teams**, and **Enterprise** plans support creating new branches.
@@ -13,40 +13,10 @@ In this section, we discuss the important concepts of saving and versioning in y
13
13
14
14
## Versions
15
15
16
-
Versions enable you to save specific named states of your project. This function is particularly useful for recovery purposes. If you accidentally delete a page or component or change settings, you can easily revert to a saved version.
17
-
18
-
### Saving a version
19
-
20
-
Saving the latest changes will store the current state of your app in the version control. In the future, if anything goes wrong, you can restore your app to the currently saved state.
21
-
22
-
Ideally, you should save the version whenever you accomplish something important, for example, after finishing a page, adding configuration, etc.
23
-
24
-
<div style={{
25
-
position: 'relative',
26
-
paddingBottom: 'calc(56.67989417989418% + 41px)', // Keeps the aspect ratio and additional padding
You can no longer create new versions in FlutterFlow. However, any previously created versions will remain accessible. Moving forward, we recommend using [**Commits**](#commits), which provides a more robust way to track changes and manage your project history.
0 commit comments