website logo
⌘K
Explore our documentation
Contact APIANT support
What is APIANT?
Automation Editor
Key Concepts
Account Management
Managing Automations
App Connections
Building Automations
Alert Mappings
Troubleshooting
CRMConnect: Mindbody → HubSpot
CRMConnect: DonorPerfect → HubSpot
CRMConnect: DonorPerfect → ActiveCampaign
MailConnect: DonorPerfect → Mailchimp
ShopConnect
ShopConnect Settings
Sync Products
Manually sync Mindbody services/pricing options to Shopify
How to tag products in Shopify to prevent sync during sales sent to Mindbody
Retrying orders from Shopify → Mindbody
Manually pushing Mindbody orders to Shopify
Mindbody Pricing Discontinuation: Integration with Shopify
Guide to manually syncing Mindbody Packages with Shopify Products
Features that are not supported in ShopConnect
Automation Alert Reports
Linked Accounts
ZoomConnect
New features in version 4
Settings
General
Email & SMS
BOTs
MINDBODY
Zoom
ZoomConnect Mindbody Appointments - Setup and requirements
Troubleshooting
Assembly Editor
Key Concepts
Account Management
API Key Management
Managing Content
Building Assemblies
API Integrations
Other Assembly Types
Keyvalue Storage
Assembly development cycle
APIANT for Integrators
Help Forum
Automation Templates
Development Server
Module IDE
Shared App Connections
Tenants and Linked Accounts
APIANT Inline
Supported functionality
Embed Inline
Sandbox
Docs powered by
Archbee
Automation Editor
...
Building Automations
Forms Overview

Form Apps

5min

An automation can display multiple forms to an end user during the same session. From the point of view of the end user, each form appears as an app screen.

The system can also show one or more waiting messages with a spinning animation icon if the automation needs to perform long-running processing before the next form screen can be displayed.

In this manner, the automation can use conditional logic and show different form screens depending on choices the end user made.

Form actions are found under the System Utility category:

Document image


In the Human Interaction app:

Document image

Document image


See the preceding documentation sections under Forms Overview for a review on how to build a form.

To indicate that the automation will display another form after the current form is submitted, enter 'next' as the form submission message here by clicking on the background of the form designer (the outer edge of the designer will be highlighted):

Document image


After the form is submitted, the automation will typically do some processing and possibly decide which form should next be shown.

If the automation's processing will take a long time, the Human Interaction "display form waiting message" can be used to show progress to the end user. Here in this example, waiting messages are shown and pause actions are used to simulate long-running processing:

Document image


This is what a message looks like to the end user:

Document image


After processing the submitted info is complete, the automation can use additional "create a form" and "await form submission" actions to display a new form screen to the end user:

Document image


The "form submission message" for the last form can not be 'next'. It should be the final message to display to the end user indicating that they are finished using your form "app".

As an example of what form app functionality can look like to end users, the screen video below shows two forms within a much larger sequence of over a dozen forms. In the example, an incorrect value is entered and then an error form is displayed. Then the previous form is display again.

Document image




Updated 03 Mar 2023
Did this page help you?
PREVIOUS
Dynamic Lists
NEXT
Embedded Forms
Docs powered by
Archbee
Docs powered by
Archbee