Plum DEV Documentation
voicexml:properties:logging

Table of Contents

logging

Default Value: enable

Determines whether the platform should enable or disable logging information within the scope of where the logging property is used to be shown within the call logs. The logging property can also be used to make any form item results, transfer details and variable elements (e.g. <var>, <assign>, <param>) private. The values that can be used to this property are: “enable”, “disable”, and “private”.

Example

<?php
header("Content-type: text/xml");
echo("<?xml version=\"1.0\"?>\n");
?>
<vxml version="2.0">
  <form id="firstform">
    <field name="myfield1" type="digits?length=5">
      <property name="logging" value="private"/>
        <prompt>
          Say or enter a five digit number.
        </prompt>
      <filled>
        <prompt>
          You entered <value expr="myfield1"/>.
        </prompt>
        <goto nextitem="myfield2"/>
      </filled>
    </field>
    <field name="myfield2" type="digits?length=6">
      <property name="logging" value="disable"/>
        <prompt>
          Say or enter a six digit number.
        </prompt>
      <filled>
        <prompt>
          You entered <value expr="myfield2"/>.
        </prompt>
        <goto next="#secondform"/>
      </filled>
    </field>
  </form>

  <form id="secondform">
    <field name="myfield3" type="digits?length=7">
      <prompt>
        Say or enter a seven digit number.
      </prompt>
      <filled>
        <prompt>
          You entered <value expr="myfield3"/>.
        </prompt>
      </filled>
    </field>
  </form>
</vxml>

Explanation

From this example, logging would be private for the field-level element, myfield1, in the call logs. The TTS prompts and any input entered by the user would be marked with <private> in the call logs. Logging would be completely disabled for the field-level element, myfield2, in the call logs. However, you would see the other field and form elements within the call logs for the rest of the application.

Notes

This property can be implemented at the field-level, form-level, page-level, and root-level scope of your application.