---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Configure the problem form layout

# Configure the problem form layout {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Configure the problem form so the information it collects is
relevant to your organization's processes. You can easily modify the form to show only the
fields, related lists, and other elements that you need.

## Before you begin

Role required: personalize_form

## Procedure

1. Navigate to AllProblemCreate New.
2. In the problem form context menu, select ConfigureForm Layout.
3. Follow the steps in [Configuring the form layout](https://www.servicenow.com/docs/access?context=configure-form-layout&version=australia&pubname=australia-platform-administration&ft:locale=en-US) to perform any of the following layout modifications.  
   Some of these modifications are illustrated in the example.
   * Show or hide fields on a form.
   * Add a related list to a form.The Incidents and Problem Tasks related lists appear by default. Review the available related lists and select appropriate lists. For
     example, if you enable auditing for the Problem table, add the Audit History related list.

   * Add an annotation to a form.
   * Create a form section.
   * Embed a list within a form.This activity allows the embedded list to be used like any other element on the form. In addition, technicians can create records in the list view. Changes made to the contents of the
     embedded list are saved when the form is saved.

   {#configure-problem-form-layout__ul_xnx_4hv_scb}  
   Note:  
   There are other activities described in the form layout topic, but the items listed here are commonly configured during initial setup.
   Figure 1. Problem form layout example

*[\>]: and then