- Getting Started
- Demo apps
- How To
- Notifications
- Using VB Expressions
- Designing your App
- Designing your app with Autopilot
- Events and Rules
- Rule: If-Then-Else
- Rule: Open a Page
- Rule: Open URL
- Rule: Close Pop-Over/Bottom Sheet
- Rule: Log Message
- Rule: Show Message
- Rule: Show/Hide Spinner
- Rule: Set Value
- Rule: Start Process
- Rule: Reset Values
- Rule: Upload File to Storage Bucket
- Rule: Download File From Storage Bucket
- Rule: Create Entity Record
- Rule: Update Entity Record
- Rule: Delete Entity Record
- Rule: Add to Queue
- Rule: Trigger workflow
- Rule: Submit Action
- Leveraging RPA in your App
- Leveraging Entities in Your App
- Leveraging Queues in Your App
- Leveraging Media in your app
- Leveraging Actions in your app
- Leveraging Connections in your apps
- Apps in Studio Web
- Application Lifecycle Management (ALM)
- UiPath First-Party Apps
- Basic Troubleshooting Guide
Rule: Submit action
Properties and configuration options for the Submit Action rule, which saves and submits user input from a form to a defined action in Action Center.
Use the Submit Action rule to save and submit the changes made by a user upon completing a form or a certain UI interaction.
This rule becomes available for selection only after you add an action definition to your app.
Action schema
This section displays the name of the action definition used in your app.
As only one action definition per app is allowed, this field is automatically filled in.
Input override
In this section you can set values for the input arguments of the action.
Clicking the Input Override field opens the Resources panel, which displays the available input or input/output parameters of the selected action.
Select the parameters, and set them to the values of your app input controls.
Action properties, whether they are input or input/output parameters, can be accessed using the following syntax:
ActionProperties.<action_property_name>
The value expression of an app control has the following syntax:
<Apps_MainPage_name>.<input_control_name>.value
For example: You have the "name" input parameter in your "Voting App" action. You have a text control in your app called "text1". To bind the input parameter to the control value in Apps:
- Select the "name" input parameter from the Resources panel. It should populate the field with the following expression:
ActionProperties.Voting_app.nameActionProperties.Voting_app.name - In the Enter value field, set the following value to the "name" parameter:
MainPage.text1.ValueMainPage.text1.Value
You can add many input overrides as the number of your action input parameters.
You should apply the input override for all action parameters you want to temporarily save, or send while submitting the action.
Action outcome
In this section, you can configure the outcome for completing the action.
The outcome options are defined in the definition schema of your action.
On error
In this section, you can define rules to be executed when submitting the action encounters an error.
For example: To track the failure, you can add a Show Message rule. You can then specify the title, message, and type of the error.
Rule output properties
- Error - references the error message shown if the job fails.
Troubleshooting
Users can submit the form without filling in required fields
Marking a field as required does not block the Submit Action rule. This applies to the Required property of an input control and to required properties in the action definition. The button stays available until you configure its Disabled property.
The following example uses a form with Name and Comment textboxes on MainPage. The button that runs the Submit Action rule stays disabled until users fill in both textboxes.
- Set the Required property of the
NameandCommenttextboxes toTrue. - Add both textboxes to a Container control, for example
Container1. - Select the button that runs the Submit Action rule.
- In the Disabled property, enter the following expression:
Not MainPage.Container1.IsValidNot MainPage.Container1.IsValid
The container is valid only when every control inside it is valid, so the button becomes available once users fill in both textboxes.
To check individual controls instead of a container, combine them with OrElse. OrElse stops at the first invalid control and skips the rest:
(Not MainPage.Name.IsValid) OrElse (Not MainPage.Comment.IsValid)
(Not MainPage.Name.IsValid) OrElse (Not MainPage.Comment.IsValid)
The submit button stays disabled after users fill in the form
The expression in the Disabled property of the button still evaluates to true. Check the following causes:
| Cause | Resolution |
|---|---|
The expression is missing Not. The button is disabled while Disabled is true, so MainPage.Container1.IsValid disables the button once the form becomes valid. | Add Not before the check, for example Not MainPage.Container1.IsValid. |
| The expression references the wrong container or control. | Check that each name in the expression matches the container or the controls users fill in. |
| A control inside the container, or a control in the expression, is still invalid. One invalid control keeps the expression true. | Check that every control has a value that passes its validation. |