Form-Based App with Widget Form (Modern)

Background and Setup

This topic applies to the Modern Add an App Experience. For the Classic Add an App Experience, refer to Form-Based App with Widget (Classic).
After you create a form-based app, you cannot change the app to use a different data source. For example, you can not change a form-based app to use a different entity or SharePoint list than the one specified when the app was created. This limitation also applies to cloned apps. That is, you cannot clone a form-based app, and then change the data source in the cloned app.

Configures the type of app to create.

Field Name	Definition
App Type	Function: Specifies the type of app to create. Accepted Values: Processed-Based App - Creates a process-based app. Form-Based App - Creates a form-based app. Default Value: Process-Based App

Configures the basic information for your app.

Field Name	Definition
App Name	Function: Specifies a name for your app. Accepted Values: One line of text that can have spaces. Default Value: None
Language	Function: Specifies the language for your app. Accepted Values: A language from the list. Default Value: None Accepts Process Data Variables: No
Category	Function: Specifies a category for your app. Accepted Values: A category from the list. The category list comes from Tenant Settings > Categories tab. Default Value: None
Description	Function: An optional description for your app. Accepted Values: More than one line of text. Default Value: None

Specifies the type of the form to create.

Field Name	Definition
Widget Form	Function: Specifies whether to create a widget form that can show information on a custom page in Page Builder. Accepted Values: Not Required - Creates a standard form-based app, which can not be used in a widget. Yes, Create Widget Form - Creates a widget form to show information based on lookups. Widget forms can only be used in Page Builder. Default Value: Not Required

Configures the basic settings for a widget form.

Field Name	Definition
Form Name	Function: A name for your form. Accepted Values: One line of text that can have spaces. Default Value: None Accepts Process Data Variables: No Example: Refer to: (Example) Create an eForm to Start the Process (Create Absence Request) (Example) Create an eForm (Set Available Leave Hours) (Example) Create an eForm (Manager Approval)
Description	Function: A description for your form. Accepted Values: More than one line of text. Default Value: None Accepts Process Data Variables: No

Configures the optional features for your form-based app.

Field Name	Definition
Access Tokens	Opens this Screen: The configuration screen for your access token. The specific screen that shows depends on your access token type. For more information, refer to Access Tokens. Function of this Screen: Configures an access token.
Document Repositories	Opens this Screen: The configuration screen for your document repository. The specific screen that shows depends on your document repository type. For more information, refer to Document Repositories. Function of this Screen: Configures your document repository.
Style Sheets	Function: Uploads CSS files to change the look and feel of your eForms.
Groups and Roles	Function: Creates groups and roles for the access rights for an app.
Images	Function: Uploads image files to customize your app.
JavaScript	Function: Uploads JavaScript files to use in eForms.

Configures the permission groups for an app.

Field Name	Definition
App Owners	Opens this Screen: App Owners tab Function: Specifies the users and groups who are App Owners.
App Designers	Opens this Screen: App Designers tab Function: Specifies the users and groups who are App Designers.
App Initiators	Opens this Screen: App Initiators tab Function: Specifies the users and groups who are App Initiators for an app. Limitations: Users and groups can only be assigned to the App Initiators permission group after an app is published.