Section I – SCXML > SCXML Extensions > Session Parameterization         Bottom of Page
Genesys 8.1
SCXML Technical Reference
                        SCXML Element Extensions >

Session Parameterization

Session Initiation Parameters

Session parameterization provides the ability to allow an orchestration application to define a set of parameters that are to be provided to the session when it is started.

Those parameters needed by the application will be defined in the SCXML document using the SCXML <data> element and Genesys-specific extension attributes. These parameter elements are used to define the following:

For details on these SCXML extensions to the <data> element, see the <data> section.

The actual values of these defined parameters come from various sources, depending on how the session is initiated. These parameter values are provide once when the session is initated and if updated during the execution of the session (for example, the use of <assign>) will not be synchronized with their data sources unless the session takes an explicit action (for example, <fetch>).

The following describe the different methods of supplying the parameters to an initated session. They can be used in combination to pass the necessary parameters to the initated session:

Known Session Parameters

The following parameters are defined and known parameters that can be defined and used by the orchestration application.

Server Parameters

The following is the definition of the parameters that are available from provisioning on the server addresses used by this application. It is the responsibility of the developer to add the following global <datamodel> in order to access these parameters. If they are not defined, then they will not be available to the session.

<datamodel>
	<data id="_statserver"/>
	<data id="_outbserver"/>
	<data id="_outbserver_s"/>
	<data id="_tserver"/>
	<data id="_ixnserver"/>
	<data id="_classserver"/>
	<data id="_cvserver"/>
</datamodel>

Name

Access

Type

Default Value

Valid Values

Description

_data._statserver

<data id="_statserver"/>

read only

URI

none

Any valid HTTP or HTTPS URI schema which has the host and port for the server.

This is the statserver that can be used by the application. The value is provided by the provisioning system. Note: this statserver address could also be pulled from the location of the <data> "src" attribute using a valid HTTP or HTTPS URI scheme. For example, <data id="_statserver" src= http://somehost/someappl />

_data._outbserver

<data id="_outbserver"/>

read only

URI

none

Any valid HTTP or HTTPS URI schema which has the host and port for the server.

This is the primary outbound server that can be used by the application. The value is provided by the provisioning system. Note: this outbound server address could also be pulled from the location of the <data> "src" attribute using a valid HTTP or HTTPS URI scheme. For example, <data id="_outbserver" src= http://somehost/someappl />

_data._outbserver_s

<data id="_outbserver_s"/>

read only

URI

none

Any valid HTTP or HTTPS URI schema which has the host and port for the server.

This is the secondary or backup outbound server that can be used by the application. The value is provided by the provisioning system. Note: this outbound server address could also be pulled from the location of the <data> "src" attribute using a valid HTTP or HTTPS URI scheme. For example, <data id="_outbserver_s" src= http://somehost/someappl />

_data._tserver

<data id="_tserver"/>

read only

URI

none

Any valid HTTP or HTTPS URI schema which has the host and port for the server.

This is the telephony server that can be used by the application for voice and chat interactions. The value is provided by the provisioning system. Note: this telephony server address could also be pulled from the location of the <data> "src" attribute using a valid HTTP or HTTPS URI scheme. For example, <data id="_t-bserver" src= http://somehost/someappl />

_data._ixnserver

<data id="_ixnserver"/>

read only

URI

none

Any valid HTTP or HTTPS URI schema which has the host and port for the server.

This is the message-based media (interaction) server that can be used by the application. The value is provided by the provisioning system. Note: this message-based media (interaction) server address could also be pulled from the location of the <data> "src" attribute using a valid HTTP or HTTPS URI scheme. For example, <data id="_ixnserver" src= http://somehost/someappl />

_data._classserver

<data id="_classserver"/>

read only

URI

none

Any valid HTTP or HTTPS URI schema which has the host and port for the server.

This is the classification server that can be used by the application. The value is provided by the provisioning system. Note: this classification server address could also be pulled from the location of the <data> "src" attribute using a valid HTTP or HTTPS URI scheme. For example, <data id="_classserver" src= http://somehost/someappl />

_data._cvserver

<data id="_cvserver"/>

read only

URI

none

Any valid HTTP or HTTPS URI schema which has the host and port for the server.

This is the Context Services server that can be used by the application. The value is provided by the provisioning system. Note: this Context Services server address could also be pulled from the location of the <data> "src" attribute using a valid HTTP or HTTPS URI scheme. For example, <data id="_cvserver" src= http://somehost/someappl />




Section I – SCXML > SCXML Extensions > Session Parameterization         Top of Page
Genesys 8.1
SCXML Technical Reference
                        SCXML Element Extensions >