To see what scripts, reports, and other application artifacts will be in a published application:

Question

Options

• AEnter the name of the Application in the Global search field
• BOpen the list of Update Sets for the instance
• CExamine the Application Files Related List in the application to be published
• DOpen the artifact records individually to verify the value in the Application field

• A
  4% (1)
• B
  88% (22)
• D
  8% (2)

Explanation

Opening the Update Sets list reveals the exact records captured for the application - scripts, reports, UI policies, and other artifacts - because publishing an application in ServiceNow generates an Update Set that acts as the definitive package manifest. That list gives you a concrete, reviewable inventory of everything that will travel with the application when published.

Why the distractors are wrong:

• A (Global search): Searching by application name returns scattered records but provides no structured, publication-specific inventory - you'd miss the packaging context entirely.
• C (Application Files Related List): This shows files associated with the app in Studio, but it reflects the development workspace, not the finalized, packaged state that will actually be published.
• D (Open individual artifact records): Checking the Application field record-by-record is manually intensive and gives no consolidated picture - you'd easily miss artifacts or miscount what's included.

Memory tip: Think of an Update Set as the "shipping label and packing slip" for your application. Before the package leaves the warehouse (your instance), the packing slip (Update Set list) tells you exactly what's inside.

No community discussion yet for this question.