Struct NewSessionDetails

#[non_exhaustive]
pub struct NewSessionDetails {
    pub supported_messaging_content_types: Option<Vec<String>>,
    pub participant_details: Option<ParticipantDetails>,
    pub attributes: Option<HashMap<String, String>>,
    pub streaming_configuration: Option<ChatStreamingConfiguration>,
}

Payload of chat properties to apply when starting a new contact.

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

supported_messaging_content_types: Option<Vec<String>>

The supported chat message content types. Supported types are text/plain, text/markdown, application/json, application/vnd.amazonaws.connect.message.interactive, and application/vnd.amazonaws.connect.message.interactive.response.

Content types must always contain text/plain. You can then put any other supported type in the list. For example, all the following lists are valid because they contain text/plain: \[text/plain, text/markdown, application/json\], \[text/markdown, text/plain\], \[text/plain, application/json, application/vnd.amazonaws.connect.message.interactive.response\].

participant_details: Option<ParticipantDetails>

The customer's details.

attributes: Option<HashMap<String, String>>

A custom key-value pair using an attribute map. The attributes are standard Amazon Connect attributes. They can be accessed in flows just like any other contact attributes.

There can be up to 32,768 UTF-8 bytes across all key-value pairs per contact. Attribute keys can include only alphanumeric, dash, and underscore characters.

streaming_configuration: Option<ChatStreamingConfiguration>

The streaming configuration, such as the Amazon SNS streaming endpoint.

Implementations

impl NewSessionDetails

pub fn supported_messaging_content_types(&self) -> &[String]

The supported chat message content types. Supported types are text/plain, text/markdown, application/json, application/vnd.amazonaws.connect.message.interactive, and application/vnd.amazonaws.connect.message.interactive.response.

Content types must always contain text/plain. You can then put any other supported type in the list. For example, all the following lists are valid because they contain text/plain: \[text/plain, text/markdown, application/json\], \[text/markdown, text/plain\], \[text/plain, application/json, application/vnd.amazonaws.connect.message.interactive.response\].

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .supported_messaging_content_types.is_none().

pub fn participant_details(&self) -> Option<&ParticipantDetails>

The customer's details.

pub fn attributes(&self) -> Option<&HashMap<String, String>>

A custom key-value pair using an attribute map. The attributes are standard Amazon Connect attributes. They can be accessed in flows just like any other contact attributes.

There can be up to 32,768 UTF-8 bytes across all key-value pairs per contact. Attribute keys can include only alphanumeric, dash, and underscore characters.

pub fn streaming_configuration(&self) -> Option<&ChatStreamingConfiguration>

The streaming configuration, such as the Amazon SNS streaming endpoint.

impl NewSessionDetails

pub fn builder() -> NewSessionDetailsBuilder

Creates a new builder-style object to manufacture NewSessionDetails.

Trait Implementations

impl Clone for NewSessionDetails

fn clone(&self) -> NewSessionDetails

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for NewSessionDetails

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl PartialEq for NewSessionDetails

fn eq(&self, other: &NewSessionDetails) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl StructuralPartialEq for NewSessionDetails