State Transition Event
Purpose: State Transition event used to describe the transition of a state. |
Description
Combines state event resources to describe the completion of a given state and the start of a new state in a single request, rather than issuing separate start and end requests.
Resource
Important
When your application deals with this resource, parts of the from and to fields are shared. See below.Field | Type | Mandatory | Description |
---|---|---|---|
service_id | integer | yes | The unique ID of the related service. |
from | hash | yes | The hash of the following fields describing the state from which the service is transitioning:
Refer to Configuration Options for more details on Business Attribute mapping.
|
to | hash | yes | The hash of the following fields, which describe the state into which the service is transitioning:
|
The following fields apply both to the state to complete and the state to start: | |||
session_id | string | no | The ID of the related session, for instance, the orchestration session, or any other business session. |
interaction_id | string | no | The ID of the related Genesys interaction. This ID can be used by other Genesys reporting products such as Stat Server, URS, Composer, and GVP. |
application_type | long or string | no | The unique ID associated with the type or class of application issuing the service event. May be used to group related applications, potentially across resource types. |
application_id | integer | no | The unique ID (such as Genesys DB ID) for the application issuing the service event, such as a GVP VoiceXML application or an Orchestration SCXML application. |
resource_type | long or string | no | The unique ID associated with the type or class<ref name="business"/> of resource which provides the service (for example, GVP, Agent Desktop, or Orchestration). |
resource_id | integer | no | The unique DB ID for the specific resource which provides the service. For instance:
|
media_type | long or string | no | The media type applicable to the given service/state/task, for instance, email, voice, chat, etc. |
timestamp | date/time | no | The UTC time at which the event was raised, with a precision of milliseconds, using the ISO 8601 representation : [YYYY]-[MM]-[DD]T[HH]:[mm]:[ss].[SSS]Z . If the application does not specify this timestamp, the server does it when the event is processed.
|
<extension> | Any JSON type | no | State attached data as key-value pairs. You can add as many key-value pairs as needed. |
Related Operations
This page was last edited on April 27, 2017, at 10:18.
Comments or questions about this documentation? Contact us for support!