Application developers can specify which ServiceNow page a user sees after submitting a new record using the Record Producer UI by writing a script in the Record Producer's Script field: producer.redirect =
"<URL>";. This script sets the redirect property of the producer object to the URL of the desired page. For example, producer.redirect = "home.do"; will redirect the user to the homepage after submitting the record.
The other options are not valid ways to specify the redirect page for a Record Producer. Reference: Populate record producer data and redirect users

https://developer.servicenow.com/dev.do#!/learn/learning-plans/quebec/servicenow_administrator
/app_store_learnv2_automatingapps_quebec_scheduled_script_execution_scripts The objects that you can use in a Scheduled Script Execution (Scheduled Job) script are GlideSystem and GlideRecord. GlideSystem provides methods for performing system operations, such as logging, running background scripts, or getting system information. GlideRecord provides methods for working with records in the database, such as querying, updating, inserting, or deleting records. The current object is not available in Scheduled Script Execution scripts, as it refers to the current record on a form or list. The GlideUser object is also not available, as it refers to the current user session. Reference: Scheduled Script Execution, GlideSystem, GlideRecord

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 tocustom applications and their components to ensure security and compliance.
Reference: Build Custom Apps in ServiceNow - eBook

In ServiceNow, Application Files are configuration records that define the various components and logic that constitute an application. These include artifacts such as:
Business Rules
Client Scripts
UI Actions
Script Includes
Tables and Fields
Workflows
These artifacts collectively define the functionality and behavior of the application. When an application is developed, ServiceNow automatically creates and manages these Application Files to represent the application's components.
Option C is correct because Application Files are the fundamental building blocks that comprise a ServiceNow application, representing its various components and configurations.
Options A, B, and D are incorrect:
A: XML exports of an Update Set represent changes made to an instance but are not synonymous with Application Files.
B: CSV files are typically used for data import/export and do not represent the configuration components of an application.
D: An XML export of table records pertains to data within a table, not the configuration artifacts that define application behavior.

In ServiceNow, to create a module that directs users to a Record Producer (a simplified form for creating records), you should use the "URL (from Arguments)" Link Type. This configuration allows you to specify a direct link to the Record Producer.
Steps to Configure:
* Navigate to Module Creation:
* Go to the Application Menu where you want to add the module.
* Click on "Edit Application Menu" and then "New Module."
* Set Link Type:
* In the module's configuration, set the Link Type to "URL (from Arguments)."
* Define the URL:
* In the Arguments field, provide the URL to the Record Producer. The URL typically follows this pattern:
arduino
CopyEdit
servicenow_instance_url/com.glideapp.servicecatalog_cat_item_view.do?
sysparm_id=record_producer_sys_id
* Replace servicenow_instance_url with your instance's URL and record_producer_sys_id with the sys_id of the Record Producer.
Explanation of Other Options:
* HTML (from Arguments): Used to display custom HTML content. Not suitable for linking directly to Record Producers.
* Content Page: Used to display predefined content pages within ServiceNow. Not applicable for direct Record Producer links.
* Script (from Arguments): Allows execution of a script to determine the module's behavior. This is more complex and unnecessary for simply linking to a Record Producer.