---
sourceDocument: Australia Conversational Interfaces
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/conversational-interfaces

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Conversational Interfaces

ft:clusterId :

    - convint

bundleId :

    - convint

workflow :

    - Platform


---

# Create the Asset Refresh topic in Virtual Agent Designer

# Create the Asset Refresh topic in Virtual Agent Designer {#ariaid-title1}

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

Create the topic in Virtual Agent Designer using topic blocks that come with the ITSM Virtual Agent Conversations plugin. When the user receives a notification that it's time to upgrade, they will be directed to this topic.

## Antes de Iniciar

Install the following applications:

* Glide Virtual Agent plugin (com.glide.cs.chatbot)

  You must have a subscription for Virtual Agent before you can activate the Glide Virtual Agent plugin.
* [Enable Natural Language Understanding (NLU)](https://servicenow-prod.fluidtopics.net/La4Q6KqoDw2XufrUntqemg "Configure Natural Language Understanding (NLU) in Virtual Agent to identify the NLU service provider for your instance. You can also specify the languages of NLU models used during conversation design, based on the languages supported by your NLU provider and the ServiceNow AI Platform."), if not already enabled (recommended).
* [ITSM Virtual Agent Conversations](https://www.servicenow.com/docs/access?context=setup-itsm-virtual-agent&version=australia&pubname=australia-it-service-management&ft:locale=en-US) (available in the ServiceNow® Store)

  If this application is already installed, check the ServiceNow Store for an updated version before you begin.
{#create-example-conv-asset-refresh__ul_pwl_zcf_lxb}

Determine the application scope for your Virtual Agent topic and actionable notification. They don't have to reside in the same application scope, but it can be easier to maintain if they do.  
Publish the following ITSM Virtual Agent components. If you're using an application scope other than ITSM Virtual Agent Conversations, you should duplicate and publish these topic blocks in the scope you intend to use. To do this, change your application scope, and then duplicate the topic blocks in Virtual Agent Designer.

* Create Incident topic block
* Request Catalog Item topic block
* AI Search topic block
* Search Catalog Item topic block
{#create-example-conv-asset-refresh__ul_z2l_tqf_lxb}

Role required: virtual_agent_admin or admin

## Por Que e Quando Desempenhar Esta Tarefa

For more information about building topics and the Virtual Agent Designer interface, see the following topics:

* [Getting started with Virtual Agent Designer](https://servicenow-prod.fluidtopics.net/LFLe6_UjplHp0awSmAloFw "The Virtual Agent Designer is a diagram tool for creating and managing assets, which are blueprints for conversations between a Virtual Agent and a user. You can design topics that help your users resolve common work issues or guide them through self-service tasks.")
* [Create a Virtual Agent topic](https://servicenow-prod.fluidtopics.net/3WNRx~5BPFnCGPdkHMS0yQ "Use Virtual Agent Designer to create and modify Virtual Agent topics (conversations). Build your topic to meet a specific objective or goal, such as fulfilling a user's request or helping a user complete a task.")
* [Assistant Designer controls](https://servicenow-prod.fluidtopics.net/qCibIs6dKLfp_LIzM7JRTA "A Virtual Agent topic consists of a collection of controls within a topic flow. Use these controls to collect, process, and present information to your users. Controls can also read, create, and update records on your instance.")
* [Assistant Designer interface reference](https://servicenow-prod.fluidtopics.net/4OPqZ8HPdyHnqB1l9igs~Q "The Assistant Designer interface lets you create, modify, test, publish, and localize topics, topic blocks, and custom controls.")
{#create-example-conv-asset-refresh__ul_b2q_br1_txb}  
Dica:  
Look through existing conversations to ensure you are not duplicating effort, and familiarize yourself with Virtual Agent and the flow of topics. Additionally, it may be helpful to outline the flow of a conversation before building it in Virtual Agent Designer.

## Procedimento

1. Navigate to AllConversational InterfacesVirtual AgentDesigner.
2. On the Topics page, select Create.  
   ![Virtual Agent Designer +Create tile on the landing page.]()
3. On the Create a topic form, set up your topic.
   1. Enter a name, such as <kbd class="ph userinput">Asset Refresh</kbd>.
   2. If NLU is enabled, select an existing model, or create a new one.
   3. Select or create an intent for the NLU model.  

      For descriptions of all field values, see [Create a topic form](https://servicenow-prod.fluidtopics.net/ooBDNRzXp1rA0hsw2HdIgQ "The Create a topic form is used to set the properties for a new conversational topic for Virtual Agent.").
   4. Select Create.

   {#create-example-conv-asset-refresh__substeps_s3d_y4f_lxb}  
   The Flow tab appears with Start and End nodes. For an overview of this screen and its components, see [Topic Flow tab](https://servicenow-prod.fluidtopics.net/03AGq_Tfh6oUokZUUtryMA "Use the topic Flow tab to build the conversation flow. Use the controls for user inputs, bot responses, and utilities to define the flow.").
4. Create your initial message to greet the user.
   1. From the Components area, drag a Text bot response node onto the canvas.
   2. Select the node to view the properties palette.
   3. Enter a name for the node and the response you want to display to the user.  
   {#create-example-conv-asset-refresh__substeps_xn1_bsf_lxb}
5. Ask the user if they want to proceed with the asset refresh.
   1. From the Components area, drag a Static choice input node onto the canvas.
   2. In the properties palette, enter the following information:  
      * A unique name, such as <kbd class="ph userinput">Continue or Defer</kbd>.
      * A text prompt, such as <kbd class="ph userinput">What would you like to do next? Learn more, or continue with the upgrade?</kbd>
      * In the Choices area, provide a text prompt for each choice and a value for that choice, so you can refer to it later on.For example, your choices might be <kbd class="ph userinput">Learn more</kbd> and
        <kbd class="ph userinput">Continue with upgrade</kbd>. The values should make sense as variable names. For example, <kbd class="ph userinput">info</kbd> and <kbd class="ph userinput">upgrade</kbd>.

      {#create-example-conv-asset-refresh__ul_tmz_d5f_lxb}

   {#create-example-conv-asset-refresh__substeps_ody_htf_lxb}  
6. Add a Decision utility to handle the user's choice.
   1. From the Components area, drag a Decision utility onto the canvas.
   2. Select the plus icon to add a second branch.
   3. Name each branch to correspond with the decisions (info and upgrade).  
   4. For each branch, select it and then use the Branch Condition area to indicate which option the branch will follow.  
   {#create-example-conv-asset-refresh__substeps_fzc_vng_lxb}
7. For the upgrade branch, add a Lookup utility node to confirm that the user still has the asset.
   1. From the Components area, drag a Lookup utility onto the canvas.  
   2. In the properties palette, specify the following information:  
      * A unique name, such as <kbd class="ph userinput">Asset Lookup</kbd>.
      * The table name: Asset \[alm_asset\]
      * In the Condition builder, select Assigned to, and then dot-walk to Input Variables \> User. Select and to include State \> is \> In maintenance.

        The asset state will tie into the notification you send the user for this asset refresh.

      {#create-example-conv-asset-refresh__ul_x1m_pgj_mxb}
   {#create-example-conv-asset-refresh__substeps_i2h_wqg_lxb}
8. Ask the user if they still have the asset.
   1. From the Components area, drag a Boolean input node onto the canvas.  
      The Boolean node automatically asks if you want to add a Decision utility with two paths. Select Yes. A Decision node appears in the flow with values of true and false. Both are already mapped to the Boolean node.
   2. Add a user prompt.  
      Use dot-walking to refer to the asset found by the Asset Lookup node.

   {#create-example-conv-asset-refresh__substeps_o4p_xhj_mxb}
9. If the user still has the asset (the Boolean response is true), we want to search for it in the catalog.
   1. From the Components area, drag the Topic Block utility onto the Asset Check true branch on the canvas.
   2. In the properties palette, select Search Catalog Item for the Topic block.
   3. Under Input mapping, use dot-walking to specify the query_term parameter from the Asset Lookup node (Input Variables \> Asset Lookup \> Display name).

   {#create-example-conv-asset-refresh__substeps_jpl_dlj_mxb}  
   The catalog search will provide these output variables by default, shown under Output mapping.

10. Request the upgraded item.
    1. From the Components area, drag the Topic Block utility onto the canvas beneath the Search Catalog Item topic block.
    2. In the properties palette, select Request Catalog Item for the Topic block.
    3. In the Input mapping area, use dot-walking to specify the catalog_item_id that the previous topic block returned.  

    {#create-example-conv-asset-refresh__substeps_sy5_v3h_4xb}  
    This topic block returns output variables as well. The user will be able to select variables for their new device, as well. You can configure these variables in [Service Catalog](https://www.servicenow.com/docs/access?context=service-catalog&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US).
11. Ask the user to confirm their choice of device.
    1. From the Components area, drag the Card bot response node onto the canvas beneath the Request Catalog Item topic block.
    2. In the properties palette, specify the following information:  
       * A unique name, such as <kbd class="ph userinput">Device Request Record</kbd>.
       * Card type: Record
       * Populate this card by referencing: Table
       * Table name: Requested Item \[sc_req_item\]
       * In the Condition builder, add Sys ID is Input Variables\>Record_id.

       * In the fields area, select the record columns to display in the card to the user.

         For example, specify Number, Short description, and
         Estimated delivery.
       {#create-example-conv-asset-refresh__ul_gzm_xkh_4xb}
    {#create-example-conv-asset-refresh__substeps_o4z_hkh_4xb}
12. Drag this flow's arrow to the End node to complete this part of the workflow.  
13. Select Save.

## O que Fazer Depois

[Create the Open Incident workflow in the Asset Refresh topic](https://servicenow-prod.fluidtopics.net/~52IuFiXPp84_EVjOYyjyg "Each Decision branch introduces additional workflows. After creating our main Asset Refresh workflow, we need to ensure that the user can get help if something goes wrong. In this example, we will help the user create an incident.")
**Conceitos relacionados**   

* [Maximizing code reuse with topic blocks](https://servicenow-prod.fluidtopics.net/LFM13XCCkrrHsi3iGAUp7Q "Topic blocks are reusable components that you can create to run common tasks and conversational elements in Virtual Agent conversations. Topic blocks simplify the topic authoring and maintenance process by enabling you to reuse standard procedures or actions across conversation topics.")