Which one of the following is NOT a method used for logging messages in a server-side script for a privately- scoped application?
Answer(s): A
gs.print() and gs.log() are older and not available in scoped applications, whereas gs.debug(), gs.info(), gs.warn(), gs.error() work in both scoped applications and global are therefore are more versatile going forward in future versions.
https://community.servicenow.com/community? id=community_QUESTION NO :&sys_id=bd71cb29db98dbc01dcaf3231f9619c6
If the Create module field is selected when creating a table, what is the new module's default behavior?
Answer(s): D
When creating a table, the Create module field allows you to automatically create a module for the table in the application menu. The default behavior of the new module is to display a list of all records from the table. This can be changed later by editing the module properties and specifying a different link type, such as form, URL, or script.
Create a tableModule properties
How must Application Access be configured to prevent all other private application scopes from creating configuration records on an application's data tables?
Application Access is a feature that allows you to control the access level of other application scopes to your application's data tables. By setting the Accessible from field value to This application scope only, you can restrict the access to your data tables to only your application scope. This means that other application scopes cannot create, read, write, or delete records on your data tables, unless they have explicit permissions through Access Controls or other means.
Application Access[Application scope]https://developer.servicenow.com/dev.do#!/learn/learning- plans/rome/new_to_servicenow/app_store_learnv2_securingapps_rome_application_access https://docs.servicenow.com/bundle/rome-application-development/page/build/applications/concept/c_ExampleDenyingAllDesignAccess.html
What are some of the benefits of extending an existing table such as the Task table when creating a new application?a) You can repurpose existing fields by simply changing the label.b) Use existing fields with no modifications.c) Existing logic from the parent table will be automatically applied to the new table. d) All of the parent table records are copied to the new table.
Extending an existing table such as the Task table when creating a new application has several benefits, such as:You can repurpose existing fields by simply changing the label. For example, you can change the Short description field to Summary or Title for your new table. You can use existing fields with no modifications. For example, you can use the Assigned to, Priority, and State fields for your new table without changing anything. Existing logic from the parent table will be automatically applied to the new table. For example, you can inherit the Business Rules, Client Scripts, and UI Policies from the Task table for your new table. The only option that is not true is d) All of the parent table records are copied to the new table. Extending a table does not copy any records from the parent table to the new table. It only creates a new table that inherits the fields and logic from the parent table.
[Extend a table][Task table]
When configuring an Access Control which has no condition or script, which one of the following statements is NOT true?
Access Controls are rules that define who can access what data and how they can access it. When configuring an Access Control, you can specify the table, operation, and role for the rule. You can also add a condition or a script to further refine the rule. If you do not add a condition or a script, the rule will apply to all records and fields on the table.The statements A, B, and C are true for Access Controls that have no condition or script. For example:table.* will grant access to every field in a record. This means that the user can view and edit all the fields on the record, regardless of their role or any other criteria. table.None will grant access to every record on the table. This means that the user can view and edit all the records on the table, regardless of their role or any other criteria. table.field will grant access to a specific field in a record. This means that the user can view and edit only that field on the record, regardless of their role or any other criteria. The statement D is not true for Access Controls that have no condition or script. table.id will not grant access to a specific record on the table. This is because the id is not a field name, but a unique identifier for the record. To grant access to a specific record on the table, you need to add a condition or a script that matches the id of the record.
[Access Control rules][Create an Access Control rule]
Post your Comments and Discuss ServiceNow CAD exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the CAD content, but please register or login to continue.