You must script and configure all required behaviors Provided link has this statement: Extending an existing ServiceNow table means the new table inherits the parent table's columns as well as its business logic.

https://developer.servicenow.com/dev.do#!/learn/learning-plans/quebec/servicenow_administrator/app_store_learnv2_automatingapps_quebec_scheduled_script_execution_scripts

In ServiceNow, a workflow context refers to a specific instance of a workflow execution. When a workflow is initiated-whether by inserting or updating a record, triggering an event, or through scripts-the system creates a workflow context. This context is derived from a particular version of the workflow and is responsible for executing the defined activities and following the specified transitions within that workflow.
Key points about workflow context:
* Instance of Execution: Each time a workflow runs, a new context is created to manage that specific execution instance. This allows multiple instances of the same workflow to operate independently and simultaneously.
* Execution of Activities: The context manages the progression through the workflow's activities, ensuring that each step is executed in the defined order and under the specified conditions.
* Tracking and Management: Workflow contexts enable administrators to monitor the state and progress of workflow executions. They provide visibility into which activities have been completed, which are pending, and any transitions that have occurred.
For example, if a workflow is designed to handle approval processes, each time an approval is initiated, a new workflow context is created to manage that particular approval instance. This context will track the approval's progress, manage notifications, and handle any branching logic defined in the workflow.

Checkbox tooltip: "Show this module when the user has the specified roles. Otherwise the user must have the roles specified by both the application menu and the module." The following is true for the Override application menu roles configuration option when configuring a module:
* Users with the module role but without access to the application menu access the module. This is true because the Override application menu roles option allows users to bypass the application menu role requirement and access the module directly if they have the module role. For example, if a module has the itil role and the Override application menu roles option enabled, and the application menu has the admin role, then a user who has the itil role but not the admin role can still access the module.
The following are not true for the Override application menu roles configuration option when configuring a module:
* Self-Service users can access the module even though they do not have roles. This is false because the Override application menu roles option does not grant access to the module to users who do not have any roles. Self-Service users are users who do not have any roles assigned to them and can only access the Self-Service portal and the Knowledge Base. To access the module, users need to have at least the module role.
* Admin is given access to the module even if Access Controls would ordinarily prevent access. This is false because the Override application menu roles option does not override the Access Control (ACL) rules that apply to the module. Access Control rules are used to restrict the access to the data and functionality of the ServiceNow platform based on the user's roles and conditions. Admin is a role Reference: https://hi.service-now.com/kb_view.do?sysparm_article=KB0716421