---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/application-development

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Tutorial part 3: Expand to a departmental solution

# ServiceNow Studio tutorial part 3: Expand to a departmental solution {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

Your first request-fulfill workflow is the first step toward full automation-not just a standalone process. To maximize its impact, take a strategic approach to scaling workflow automation, improving efficiency, and streamlining
service delivery to enhance and support the initial workflow.

This expansion transforms the initial request process into a fully scalable departmental solution. Here are key workflows that can complement and expand your automation
efforts.

## Add additional workflows {#sns-z-tutorial-expand-departmental-solution__section_lvh_nny_vfc}

By expanding your workflows strategically, you create a seamless, efficient service experience, reducing manual effort and ensuring consistent service delivery across your organization. Follow the steps from the marketing design
request to configure workflows for inquiries and issues.

1. Create tables. Both tables should start from a blank table and extend the Task table the same way as the Marketing Design Request table.
   1. Table label: Marketing Inquiry
   2. Auto-number: Selected
   3. Prefix: MKTINQ
   4. Permissions: Same as the Marketing Design Request table

   {#sns-z-tutorial-expand-departmental-solution__ol_vpg_gwf_bgc}

   1. Table label: Marketing Issue
   2. Auto-number: Selected
   3. Prefix: MKTISS
   4. Permissions: Same as the Marketing Design Request table

   {#sns-z-tutorial-expand-departmental-solution__ol_zj5_jwf_bgc}

2. Add fields to your tables.
   1. Label: <kbd class="ph userinput">Inquiry summary</kbd>
   2. Type: <kbd class="ph userinput">String</kbd>
   3. Max length: <kbd class="ph userinput">160</kbd>

   {#sns-z-tutorial-expand-departmental-solution__ol_b1q_tbg_bgc}

   1. Label: <kbd class="ph userinput">Issue summary</kbd>
   2. Type: <kbd class="ph userinput">String</kbd>
   3. Max length: <kbd class="ph userinput">160</kbd>

   {#sns-z-tutorial-expand-departmental-solution__ol_ltd_1cg_bgc}

3. Configure the form.
   1. Remove the same fields from the form as you did for the Marketing Design Request form.
      * Configuration item
      * Parent
      * Active
      * Short description
      {#sns-z-tutorial-expand-departmental-solution__ul_yy2_t5f_bgc}
   2. Add the Inquiry summary field above the Description field.

   3. Add the Issue summary field above the Description field, and replace the Priority field with the Impact field.

   {#sns-z-tutorial-expand-departmental-solution__ol_rf3_s5f_bgc}
4. Create the record producer.
   1. Catalog: <kbd class="ph userinput">Service Catalog</kbd>
   2. Category: <kbd class="ph userinput">Departmental Services</kbd>
   3. Add the following questions for inquiries and issues:
      * Inquiry/Issue summary (Single line)
      * Description (Multi-line)
        * Item name: <kbd class="ph userinput">Marketing Inquiry</kbd>
        * Destination (record submission table): <kbd class="ph userinput">Marketing Inquiry</kbd>

        * Item name: <kbd class="ph userinput">Marketing Issue</kbd>
        * Destination (record submission table): <kbd class="ph userinput">Marketing Issue</kbd>

        * Configure the Impact question the same way that you configured the Media type in the previous record producer, using the following choices:
          1. Display name: <kbd class="ph userinput">High</kbd>, Value: <kbd class="ph userinput">1</kbd>
          2. Display name: <kbd class="ph userinput">Medium</kbd>, Value: <kbd class="ph userinput">2</kbd>
          3. Display name: <kbd class="ph userinput">Low</kbd>, Value: <kbd class="ph userinput">3</kbd>
          {#sns-z-tutorial-expand-departmental-solution__ol_ivm_ztg_bgc}
        {#sns-z-tutorial-expand-departmental-solution__ul_jx5_bqg_bgc}
      {#sns-z-tutorial-expand-departmental-solution__ul_eyr_v5f_bgc}
   4. Select Map to specified field on table, and fill in the Table, Question, and Name fields.  
      Nota:  
      Name should be all lowercase with underscores instead of spaces.
   {#sns-z-tutorial-expand-departmental-solution__ol_dyr_v5f_bgc}
5. Submit both record producers when complete.
{#sns-z-tutorial-expand-departmental-solution__ol_c1d_xsf_bgc}
* **[Create the Marketing department taxonomy](https://servicenow-prod.fluidtopics.net/O2i0rEJtNZuo7Q_yhyQY7w)**   
  Create a marketing department taxonomy on the ServiceNow AI Platform.
* **[Add departmental workflows to your workspace](https://servicenow-prod.fluidtopics.net/BE4vaeUK20fnb5sYY3YXig)**   
  A well-structured workspace improves task visibility, reduces response times, and ensures that fulfillers have all the necessary tools and information in one place. By using Workspaces, departments can standardize processes, reduce manual effort, and improve collaboration---leading to better service delivery, higher productivity, and organization-wide operational improvements.