-
Notifications
You must be signed in to change notification settings - Fork 2
Behaviours
Lydia Gray edited this page Nov 28, 2023
·
12 revisions
- GoToPage
- GoToExternalPage
- SubmitAndPay
- SubmitAndRedirect
- SubmitForm
- SubmitAndEmail
- SubmitWithoutSubmission
A behaviour is what tells the form what to do after the form data is submitted. In the page section of a form you can specify none, one, or multiple behaviours.
behaviours : []
A behaviour is structured in the following way:
BehaviourType: Enumerator Conditions: List BehaviourRelated info such as webservice url and gottoPage
BehaviourType is an enum. The values are given below:
namespace form_builder.Enum
{
public enum EBehaviourType
{
Unknown,
GoToPage,
SubmitForm,
GoToExternalPage,
SubmitAndPay,
SubmitAndRedirect,
SubmitAndEmail,
SubmitWithoutSubmission
}
}
If all the conditions are true the behaviour is acted upon. If any conditions are not true, it goes to the next behaviour. There should be a default behaviour with no conditions at the end of the list which is called when none of the conditions of the previous behaviour are true.
- Availability
- Actions
- Behaviours
- Breadcrumbs
-
Conditions
- String Conditions
- Date Conditions
- Integer Conditions
- File Upload Conditions
- Custom validation
-
Elements
- AddAnother
- Address
- Button
- Booking
- Checkbox
- Date Input
- Date Picker
- Declaration
- Document Download
- Document Upload
- File Upload
- H1-H6
- HR
- Image
- Inline Alert
- Link
- Map
- Multiple File Upload
- OrderedList
- Organisation
- P
- Radio
- Select
- Street
- Summary
- Success page
- Textarea
- Textbox
- Time input
- Unordered List
- Uploaded files summary
- Warning
- EnabledFor
- Feedback form
- File uploads
- Form Schema
- Header
- Inbound Values
- Integrating with PowerAutomate/0365
- Lookup
- Page
- Payment & Payment calculations
- Preview data structure
- Render conditions
- Reusable elements
- Structure tests
- Success page
- Tag parsers
- Target mapping
- Validators