Section I – SCXML > SCXML > Session Initiation         Bottom of Page
Genesys 8.1
SCXML Technical Reference
< SCXML Document Retrieval            Runtime >

Session Initiation

There are several types of SCXML session initiation and the orchestration applications and logic must be tailored based on the type of "initiation." In other words, the orchestration application or logic must be aware of how it was initiated and be programmed to handle it. A developer could create two different orchestration logic "front end" applications and then have a common orchestration logic module to do the logic that is common to both. For example:

Trigger-Oriented SCXML Document

<scxml name="trigger initiated" initialstate="triggerState">
	<state id="triggerState">
	<datamodel>
		<data id="param1" _type="parameter"/>
		<data id="param2" _type="parameter"/>
		...
	</datamodel>
	<onentry>
		<!--- Do some core initialization processing--->
	</onentry>
	<transition event="trigger.event" target="commonState">
		<!--- prepare for common state processing set param data model --->
	</transition>
	
	</state>
	<state id="commonStateT" src="commonStateURL">
	...
	</state>

</scxml>

<invoke> or <session:start>–Oriented SCXML Document

<scxml name="started logic" initialstate="startState">
	<state id="startState">
	<datamodel>
		<data id="param1" _type="parameter"/>
		<data id="param2" _type="parameter"/>
		...
	</datamodel>
	<onentry>
		<!--- Do some core initialization processing--->
	</onentry>
	<transition target="commonState"/>
	
	</state>
	<state id="commonStateS" src="commonStateURL">
	...
	</state>

</scxml>

The following are the different types of session initiation that are supported by the orchestration platform.

Session Parameters

For details on defining, passing, resolving, and potentially returning session parameters, see the Session Parameterization section.




Section I – SCXML > SCXML > Session Initiation         Top of Page
Genesys 8.1
SCXML Technical Reference
< SCXML Document Retrieval            Runtime >