This page was last edited on November 30, 2018, at 18:46.
Comments or questions about this documentation? Contact us for support!
Use a Log block to record information about an application. For example, you can log caller-recorded input collected while an application is running or error messages. You can use the Log block for any of the following purposes:
The categories in the Log Level property correspond to the above.
When used for a callflow, the Log block writes the log to the Genesys Voice Platform logs (Media Control Platform) using the VoiceXML <log> tag.
The Log block has the following properties:
The Log block has no page exceptions.
Find this property's details under Common Properties for Callflow Blocks or Common Properties for Workflow blocks.
Find this property's details under Common Properties for Callflow Blocks or Common Properties for Workflow Blocks.
Find this property's details under Common Properties for Callflow Blocks or Common Properties for Workflow Blocks.
For callflows, invalid ECMAScript expressions may raise the following exception events: error.semantic. For workflows, invalid ECMAScript expressions may raise the following exception events:
You can use custom events to define the ECMAScript exception event handling.
Find this property's details under Common Properties for Callflow Blocks or Common Properties for Workflow Blocks.
This property applies to workflows only. It provides meta-data for the logging details.
Find this property's details under Common Properties for Callflow Blocks or Common Properties for Workflow Blocks.
Find this property's details under Common Properties for Callflow Blocks or Common Properties for Workflow Blocks.
Find this property's details under Common Properties for Callflow Blocks or Common Properties for Workflow Blocks.
Starting with 8.1.4, Composer blocks used to build routing applications (with the exception of the Disconnect and EndParallel blocks) add a new ORS Extensions property.