a. To replace outdated, inadequate, custom business applications and processes b. To extend service delivery and management to all enterprise departments c. To allow users full access to all ServiceNow tables, records, and fields d. To extend the value of ServiceNow
Correct Answer: D
The correct combination of statements is a, b, and d. These are possible reasons to build custom applications on ServiceNow: To replace outdated, inadequate, custom business applications and processes. Building custom applications on ServiceNow can help digitize and automate manual or legacy processes that are not covered by existing ServiceNow solutions. This can improve efficiency, data quality, user experience, and innovation. To extend service delivery and management to all enterprise departments. Building custom applications on ServiceNow can help provide consistent and scalable services across different functions and teams in the organization. This can enhance collaboration, visibility, productivity, and customer satisfaction. To extend the value of ServiceNow. Building custom applications on ServiceNow can help leverage the capabilities and benefits of the Now Platform, such as low-code development tools, workflow automation engine, AI-powered insights, security operations, etc. This can increase agility, resilience, performance, and value. The statement c is not a valid reason to build custom applications on ServiceNow: To allow users full access to all ServiceNow tables, records, and fields. Building custom applications on ServiceNow does not imply granting users full access to all data and objects in ServiceNow. Access control rules still apply to custom applications and their components to ensure security and compliance. Reference: Build Custom Apps in ServiceNow - eBook
Question 92
Identify characteristic(s) of a Record Producer. Choose 3 answers
Correct Answer: A,C,E
A Record Producer is a type of service catalog item that allows users to create records on a specified table. A Record Producer has the following characteristics: Graphics can be included on the user interface: You can add images, icons, or banners to the Record Producer to make it more appealing and informative for the user. You can also use HTML and CSS to customize the layout and style of the Record Producer. You can script behaviors of fields in the user interface: You can use Client Scripts and UI Policies to control the behavior and appearance of the fields on the Record Producer. For example, you can use Client Scripts to validate the field inputs, perform calculations, or populate default values. You can also use UI Policies to show or hide fields, make fields mandatory or read-only, or set field values based on conditions. Each field prompts the user with a question rather than a field label: You can use the Variable Question field to define the question that prompts the user for the field value. The question can be more descriptive and user-friendly than the field label. For example, you can use the question "What is the name of the project?" instead of the field label "Name". The other statements are not true for Record Producers. Record Producers do not always insert records into the Requested Item [sc_req_item] table. They can insert records into any table that is specified in the Record Producer properties. Record Producers also do not have to be scripted. They can use the default script that maps the variable values to the record fields, or they can use a custom script that defines the logic for creating the record. Reference: [Record Producers] [Record Producer properties] [Record Producer scripts]
Question 93
Tables that extend a table do what?
Correct Answer: D
Tables that extend a table inherit the parent's fields. Extending a table means creating a child table that shares the same columns and business logic as the parent table. For example, the Incident table extends the Task table, which means that all fields defined on the Task table are also available on the Incident table. Extending a table allows for reusing existing fields and behaviors without duplicating them on multiple tables. Reference: Table extension and classes
Question 94
Which of the following are configured in an Email Notification? a) Who will receive the notification. b) What content will be in the notification. c) When to send the notification. d) How to send the notification.
Correct Answer: A
https://docs.servicenow.com/bundle/tokyo-servicenow-platform/page/administer/notification/task/t_CreateANotification.html Reference: An Email Notification is a record that defines the content and conditions for sending an email message from the ServiceNow platform. The following are configured in an Email Notification: Who will receive the notification. This is specified by the Recipients related list, which can include users, groups, email addresses, or scripts that return email addresses. What content will be in the notification. This is specified by the Subject and Message HTML fields, which can include variables, scripts, or templates to dynamically generate the email content. When to send the notification. This is specified by the When to send tab, which defines the conditions and events that trigger the email notification. The following is not configured in an Email Notification: How to send the notification. This is not a configuration option for an Email Notification. The platform uses the SMTP protocol to send email messages, and the email properties control the email server settings and behavior. References: Email Notifications, Get Started with Notifications
Question 95
When configuring the content of an Email Notification, which syntax should be used to reference the properties of an event triggering the Notification?
