---
schema_version: "1"
id: 6eac1257a8128d857c6f05b7aedb506f44555f0cc290ff314f3bb139020659ff
title: VPL Console Action (Managed Package)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/comms_t_vpl_console_action_71118.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.comms_t_vpl_console_action_71118.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 15a387268f776c24696e9060a894044aa159f32b344c843b260b2fcdd1176de1
description: "This custom metadata type is used to manage the actions displayed in the Actions menu on the agent console and the subscriber workflows displayed in the customer portal. All the records in this custom metadata type have a similar set of fields. Here's how this custom metadata type is structured:"
products:
  - Communications
release: "264"
---
# VPL Console Action (Managed Package)

This custom metadata type is used to manage the actions displayed in the **Actions** menu on the agent console and the subscriber workflows displayed in the customer portal. All the records in this custom metadata type have a similar set of fields. Here's how this custom metadata type is structured:

![Managed Package Icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-communications-264-0-0-production-enus/444efb86-ea1e-477e-afbc-56eaac192eaf/communications/images/media_package_icon.png) _This feature is part of the Communications Cloud managed package._

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
      <colgroup>
        <col>
        <col>
      </colgroup>
      <thead class="slds-text-title_caps ">
        <tr class="">
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d10295e49">
            <p style="margin-bottom:0;">Field Name</p>
          </th>
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d10295e55">
            <p style="margin-bottom:0;">Description</p>
          </th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="Field Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d10295e49 ">
            <p style="margin-bottom:0;">Action Category</p>
          </td>

          <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d10295e55 ">
            <p style="margin-bottom:0;">Specifies the subheading under which an action is displayed on
              the agent console. The values used by default are
              <strong class="uicontrol">Service</strong>, <strong class="uicontrol">Plan</strong>,
              <strong class="uicontrol">SIM</strong>, and <strong class="uicontrol">Number</strong>. If any
              text is entered here that doesn't correspond to an existing category,
              a new category is created.
            </p>
          </td>

        </tr>
        <tr class="">
          <td data-label="Field Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d10295e49 ">
            <p style="margin-bottom:0;">Action Context</p>
          </td>

          <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d10295e55 ">
            <p style="margin-bottom:0;">Specifies if the action should be displayed in the
              <strong class="uicontrol">Actions</strong> menu of the subscription card or in the
              <strong class="uicontrol">Actions</strong> menu of the account on the agent
              console. This field can contain only one value, either
              <kbd>Account</kbd> or
              <kbd>Subscription</kbd>. For actions that must be listed
              in both <strong class="uicontrol">Actions</strong> menus, you'll find two records,
              one for the account and another for the subscription.
            </p>
          </td>

        </tr>
        <tr class="">
          <td data-label="Field Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d10295e49 ">
            <p style="margin-bottom:0;">Applicable Journey</p>
          </td>

          <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d10295e55 ">
            <p style="margin-bottom:0;">Specifies that the action is valid for prepaid journeys. Enter
              <kbd>Prepaid</kbd>.
            </p>
          </td>

        </tr>
        <tr class="">
          <td data-label="Field Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d10295e49 ">
            <p style="margin-bottom:0;">Applicable View</p>
          </td>

          <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d10295e55 ">
            <p style="margin-bottom:0;">Specifies if the action should be displayed on the agent
              console, the customer portal, or both. Valid values are:
              <kbd>Community</kbd>, <kbd>Console</kbd>.
              Both values can be specified, separated by a comma.
            </p>
          </td>

        </tr>
        <tr class="">
          <td data-label="Field Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d10295e49 ">
            <p style="margin-bottom:0;">OmniScript Display Name</p>
          </td>

          <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d10295e55 ">
            <p style="margin-bottom:0;">Contains the text that is displayed on the agent console or in
              the customer portal. This is usually the workflow name. For example:
              Manage features.</p>
          </td>

        </tr>
        <tr class="">
          <td data-label="Field Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d10295e49 ">
            <p style="margin-bottom:0;">OmniScript URL</p>
          </td>

          <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d10295e55 ">
            <p>Provides the URL for the OmniScript that should be launched by
              this action. To specify the URL of an OmniScript in the appropriate
              format:</p>
            <ol>
              <li>
                <p>Go to the OmniScript that you want to link to.</p>
              </li>

              <li>
                <p>In the Actions menu, click <strong class="uicontrol">How To
                    Launch</strong>.</p>
              </li>

              <li>
                <p>In the Lightning section, copy the link.</p>
                <p>For example:</p>
                <p>
                  <code>https://marketing-industry-80291.lightning.force.com/lightning/cmp/vlocity_cmt__vlocityLWCOmniWrapper?c__target=c:vplActivateDeactivateServiceEnglish&amp;c__layout=lightning&amp;c__tabIcon=custom:custom18&amp;c__tabLabel=Manage
                                    Features</code>
                </p>
              </li>

              <li>
                <p>Delete the initial part of the URL, upto and including
                  <code>vlocityLWCOmniWrapper?</code>.
                </p>
              </li>

              <li>
                <p>Append <code>&amp;c__ContextId=</code> at the end.</p>
              </li>

            </ol>
            <p>The resulting string has the OmniScript URL in the
              appropriate format. For
              example:</p>
            <p style="margin-bottom:0;">
              <code>c__target=c:vplActivateDeactivateServiceEnglish&amp;c__layout=lightning&amp;c__tabIcon=custom:custom18&amp;c__tabLabel=Manage
                                features&amp;c__ContextId=</code>
            </p>
          </td>

        </tr>
      </tbody>
    </table>

The VPL Console Action custom metadata consists of the following records:

- Buy\_add\_ons
- Buy\_add\_ons\_subscription
- Cash\_top\_up\_subscription
- Manage\_features\_subscription
- Manage\_features
- Manage\_lost\_or\_stolen\_device
- Manage\_lost\_or\_stolen\_device\_subscription
- Number\_change\_request\_subscription
- Number\_change\_request
- Request\_SIM\_replacement\_subscription
- Request\_SIM\_replacement
- Request\_SIM\_Unlock\_Code
- Request\_SIM\_unlock\_code\_subscription
- Top\_up\_via\_voucher
- Top\_up\_via\_voucher\_subscription