https://docs.servicenow.com/bundle/paris-servicenow-platform/page/administer/flow-designer/concept/spokes.ht A spoke is a scoped application containing Flow Designer content dedicated to a particular application or record type. Flow Designer provides a set of core actions to automate Now Platform processes. You can add application-specific core actions by activating the associated spoke.

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]

"If there are no spreadsheets or existing tables to use for your application, you can create and customize a new table." see this quote in link below:
https://docs.servicenow.com/bundle/tokyo-application-development/page/build/app-engine-studio/task/create-tab Also see:
https://docs.servicenow.com/bundle/tokyo-application-development/page/build/guided-app-creator/task/gac-crea Also, no search results if search on "Now Experience Table Creator".

Explanation
Explanation/Reference: https://community.servicenow.com/community?
id=community_article&sys_id=d2dce665dbd0dbc01dcaf3231f9619fe

https://www.servicenow.com/community/it-service-management-forum/email-notification/m-p/695221 Reference:
When configuring the content of an Email Notification, the following syntax should be used to reference the properties of an event triggering the Notification:
event.<propertyname>.ThisisthecorrectsyntaxtoaccessthepropertiesoftheeventrecordthattriggeredtheEmailNotification,suchasevent.name,event.parm1,orevent.parm2.Forexample,{event.parm1} will display the value of the first parameter of the event.
The following syntaxes are not correct for referencing the properties of an event triggering the Notification:
current.<propertyname>.Thisisthesyntaxtoaccessthepropertiesofthecurrentrecordthatisassociatedwiththeevent,suchascurrent.number,current.shortdescription,orcurrent.state.Forexample,{current.short_description} will display the short description of the current record.
${property name>.getDisplayValue()}. This is the syntax to access the display value of a property of the current record, such as current.state.getDisplayValue(), current.assigned_to.getDisplayValue(), or current.category.getDisplayValue(). For example, current.state.getDisplayValue() will display the state of the current record in a human-readable format, such as New, In Progress, or Closed.
${gs.<property name>}. This is the syntax to access the properties of the GlideSystem (gs) object, which provides methods for performing system operations, such as gs.now(), gs.getUserID(), or gs.getProperty(). For example, gs.now() will display the current date and time of the system. References: Email Notifications, Email Notification Variables