InServiceNow Knowledge Management, thepublishing and retiring process for knowledge articlesis managed throughWorkflows. These workflows define the steps an article must go through before it is published, updated, or retired.
Submission:
A user creates a knowledge article and submits it for approval.
Approval Process:
Based on the workflow, an article may require manager or SME (Subject Matter Expert) approval.
Publishing:
Once approved, the article ispublishedand made available in the Knowledge Base.
Updating & Versioning:
If edits are needed, the article enters adraft or reviewstate.
Retirement:
When an article is no longer needed, it follows the workflow toretire or archiveit.
Knowledge Approval Publish(requires approval before publishing)
Knowledge Instant Publish(automatically publishes the article)
Knowledge Retire(handles retiring or archiving articles)
A: Approval Policies(Incorrect)
ServiceNow does not use a separate "Approval Policy" for knowledge articles; approvals are managed within the workflow.
B: Approval Definitions(Incorrect)
There is no such specific feature in ServiceNow. Approvals are configured within workflows, not separate definitions.
C: Workflow Designer(Incorrect)
TheWorkflow Designeris a tool used tocreate workflows, but it does not control the publishing process directly. The workflows themselves do.
E: State Lifecycle(Incorrect)
While knowledge articleshave a lifecycle (Draft # Review # Published # Retired), this is controlledby workflows, not by an independent "State Lifecycle" feature.
Knowledge Workflows Overview:https://docs.servicenow.com/bundle/rome-servicenow-platform/page
/product/knowledge-management/reference/r_KnowledgeWorkflows.html
ServiceNow Knowledge Management Process:https://docs.servicenow.com/en-US/bundle/utah-it-service- management/page/product/knowledge-management/concept/knowledge-management-overview.html How Workflows Control Knowledge Article Publishing & Retiring:Common Knowledge Workflows in ServiceNow:Explanation of Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

When an item isordered from the Service Catalog, two main records are created in ServiceNow:
sc_req_item(Requested Item - RITM)
Representseach individual itemin the order.
Tracks the approval process, fulfillment, and delivery for that specific item.
sc_task(Service Catalog Task - SCTASK)
Used toassign workto different fulfillment teams (e.g., IT, HR).
A singlesc_req_itemmay generate multiplesc_taskrecords.
A user orders aMacBook Profrom the Service Catalog.
ARequest (REQ#)is created.
ARequested Item (RITM#)is generated to track the MacBook order.
One or moreService Catalog Tasks (SCTASK#)are created for fulfillment (e.g., Procurement, Shipping).
C: A change record
Change records (chg_request) are created only if thecatalog item is linked to Change Management, which is not always the case.
D: An Incident record
Incidents (incident) are created forissues or break/fix cases, not for service requests.
E: A problem record
Problem records (problem) are used forroot cause analysis, not service catalog requests.
Reference:ServiceNow CSA Documentation - Service Catalog & Request Fulfillment ServiceNow Product Documentation - Request, RITM, and SCTASK Relationships(https://docs.servicenow.
com)
Final answer: A, B (A record ofsc_task, A record ofsc_req_itemtable)

Reference: https://docs.servicenow.com/bundle/rome-now-intelligence/page/use/reporting/concept
/c_HowToAccessRelatedTables.html

In ServiceNow, role-based access control (RBAC) determines what a user can see and do within the platform.
If a user can see an application and its module but encounters a blank page when attempting to create a new record, the most likely reason is insufficient permissions.
Understanding the Issue:
The usercan see the application and module, which indicates they have at leastreadaccess.
The blank page appears when they attempt to create a new record, which suggests a lack ofwriteaccess.
Role-Based Access Control in ServiceNow:
Every table in ServiceNow can haveACLs (Access Control Rules)that define what users can do based on their roles.
If a user hasonly read accessto the Inventory table (x_inventory), they can view records butcannot create new ones.
AwriteorcreateACL is required to allow the user to insert new records into the table.
Why Other Answers Are Incorrect:
A: Create New module has a broken link# If the module had a broken link, the user would likely get an error or a "Page not found" message rather than a blank page.
B: Known intermittent issue with U115# No such known issue exists in official CSA documentation.
C: User should be using Chrome instead of Explorer for their browser# While browser compatibility issues can exist, they do not typically result in a blank page specifically when trying to create a new record.
E: User session has timed out# If the session had expired, the user would be redirected to the login page rather than seeing a blank page.
Best Practice Solution:
Verify the ACLson the Inventory table (x_inventory) to check if the user haswriteandcreatepermissions.
Check the roles assignedto the user underUser Administration # Usersand ensure they have the appropriate roles for Inventory management.
Review the Application Menu and Module settingsto confirm proper configuration.
Reference:
ServiceNow System Security: Access Control Rules
ServiceNow Role-Based Permissions Model (CSA Official Documentation)
ServiceNow Docs: Understanding Access Control Rules