Access Control scripts are server-side scripts that run when an Access Control rule is evaluated. They can use the gs and current objects to access the GlideSystem and GlideRecord methods, respectively. Some of the useful methods in Access Control scripts are:
* gs.hasRole() - This method checks if the current user has a specified role. It returns true if the user has the role, and false otherwise. For example, gs.hasRole('admin') will return true if the user is an administrator, and false otherwise.
* current.isNewRecord() - This method checks if the current record is a new record that has not been inserted into the database yet. It returns true if the record is new, and false otherwise. For example, current.isNewRecord() will return true if the record is being created, and false if the record is being updated or deleted.
The methods g_user.hasRole() and current.isNew() are not part of the server-side scripting API. They are part of the client-side scripting API, which is used in Client Scripts and UI Policies. They cannot be used in Access Control scripts.
References:
[Access Control scripts]
[GlideSystem methods]
[GlideRecord methods]
Reference:
http://servicenowmypath.blogspot.com/2017/

Flow Designer variables can store record data and complex data using the following data types:
* Integer: A whole number that can be used in mathematical operations.
* Array: A collection of items that can be accessed by their index or iterated over using a For each action.
* String: Any kind of text, such as email addresses or the text contents of a file.
Define and Use Data Types in a Flow (Flow Designer)
Variable data types - Power Automate | Microsoft Learn
Product Documentation | ServiceNow

The welcome screen appears every time a new application is created through the Guided Application Creator.
The welcome screen provides an overview of the steps involved in creating an application, such as defining the app name, scope, and tables, configuring the app user interface, and publishing the app. The other options are not true about the Guided Application Creator. The global scope option is turned off by default, as it is recommended to create applications in their own scope for better security and performance. A scope application user role is not automatically created, as the user can choose to create one or use an existing role for the app access control. Default access controls are not automatically created, as the user can define the read, write, create, and delete permissions for each table in the app. Reference: Guided App Creator