ServiceNow CAD - Certified Application Developer - ServiceNow

"Restricted caller access [sys_restricted_caller_access] records track cross-scope applications or scripts that request access to an application, application resource, or event in the Now Platform." <<== this is the third sentence down in the following link: https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/concept/restricted-caller-access-privilege.html

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.

Configuring the label of a field in a child table changes the label only on that table, not on the base table or the parent table. The base table is the table that contains the common fields for all the extended tables, and the parent table is the table that is directly extended by the child table. The label of a field on the base table or the parent table can be different from the label on the child table. References: [ServiceNow Docs - Table extension], [ServiceNow Community - How to change field label in child table]

"A table that extends another table is called a child class, and the table it extends is the parent class" - this is about halfway down in this link below: https://docs.servicenow.com/en-US/bundle/tokyo-platform-administration/page/administer/table-administration/concept/table-extension-and-classes.html

In ServiceNow, when an event is generated using the gs.eventQueue() method, the system can respond in several ways:

B. Email Notification: Events can trigger email notifications. By associating an event with a notification, the system can send emails to specified recipients when the event occurs.

E. Script Action: Script Actions are server-side scripts that execute in response to events. They allow developers to define custom behaviors that should occur when specific events are fired.

The other options are not appropriate responses to events generated by gs.eventQueue():

A. UI Policy: UI Policies are used to dynamically change the behavior of fields on forms in the user interface and are not triggered by events.

C. Client Script: Client Scripts run on the client side (in the user's browser) and are not directly triggered by server-side events.

D. Scheduled Script Execution (Scheduled Job): Scheduled Jobs are scripts that run at specified times or intervals and are not triggered by events.

For more detailed information, refer to the official ServiceNow documentation on Responding to Events.

Administrators can grant non-admin users the ability to develop global applications. Delegated Development is for the scoped applications only