https://docs.servicenow.com/bundle/tokyo-platform-administration/page/administer/form-administration/concept/c_FormDesign.html

Comprehensive and Detailed Step-by-Step Explanation:
* Options for Creating Tables in Guided Application Creator:
* Create a table from scratch: This option allows you to define a completely new table with custom fields and configurations.
* Create a table from a template: You can use predefined table templates to speed up table creation. Templates often include pre-configured fields and settings.
* Extend a table: This allows you to create a new table by inheriting fields and functionality from an existing table, enabling reuse and consistency.
* Why Other Options Are Incorrect:
* Option A (Link to external tables): Linking to external tables is not an option provided in the Guided Application Creator; external data is typically accessed through integration methods.
* Option D (Run import jobs): Import jobs are used for data migration, not for table creation in the Guided Application Creator.
* Option E (Upload a spreadsheet): While uploading a spreadsheet can create tables, this is a feature of Import Sets, not the Guided Application Creator.
* Option F (Use API calls): API calls are for integration and not an option for creating tables directly in the Guided Application Creator.
References:
* ServiceNow Developer Documentation on Guided Application Creator.

The application name is not required to link a ServiceNow application to a Git repository. You only need to provide the URL, user name, and password of the Git repository, as well as the branch name and the authentication type. The application name is automatically generated based on the scope name of your application. Reference: [Link an application to a Git repository] Reference: https://docs.servicenow.com/bundle/orlando-application-development/page/build/applications
/task/ t_LinkAnApplicationToSourceControl.html

https://docs.servicenow.com/bundle/tokyo-application-development/page/script/useful-scripts/reference/r_DisplayFieldMessages.html

The Allow configuration Application Access option determines whether users can configure the application tables, such as adding or modifying fields, views, or indexes. The following is true for a table with the Allow configuration option selected:
* Out of scope applications can create Business Rules for the table. This is true because the Allow configuration option grants access to the table configuration to any user who has the admin or personalize_dictionary role, regardless of the application scope. This means that users can create Business Rules, which are server-side scripts that run when a record is displayed, inserted, updated, or deleted, for the table from any application.
The following are not true for a table with the Allow configuration option selected:
* Only the in scope application's scripts can create Business Rules for the table. This is false because the Allow configuration option does not restrict the creation of Business Rules to the in scope application, as explained above.
* Any user with the application's user role can modify the application's scripts. This is false because the Allow configuration option does not grant access to the application scripts, such as client scripts or script includes, to any user who has the application's user role. To modify the application scripts, users need to have the admin role or the application's admin role.
* Out of scope applications can add new tables to the scoped application. This is false because the Allow configuration option does not allow out of scope applications to add new tables to the scoped application. To add new tables to a scoped application, users need to have the admin role or the application's admin role and be in the application scope. References: Application Access, Business Rules Reference: https://community.servicenow.com/community? id=community_QUESTION NO:
&sys_id=1a721819dbfa23409a64e15b8a9619d2