#[non_exhaustive]pub struct CreateCallAnalyticsCategoryInput { /* private fields */ }Implementations
sourceimpl CreateCallAnalyticsCategoryInput
impl CreateCallAnalyticsCategoryInput
sourcepub async fn make_operation(
&self,
_config: &Config
) -> Result<Operation<CreateCallAnalyticsCategory, AwsResponseRetryClassifier>, BuildError>
pub async fn make_operation(
&self,
_config: &Config
) -> Result<Operation<CreateCallAnalyticsCategory, AwsResponseRetryClassifier>, BuildError>
Consumes the builder and constructs an Operation<CreateCallAnalyticsCategory>
sourcepub fn builder() -> Builder
pub fn builder() -> Builder
Creates a new builder-style object to manufacture CreateCallAnalyticsCategoryInput.
sourceimpl CreateCallAnalyticsCategoryInput
impl CreateCallAnalyticsCategoryInput
sourcepub fn category_name(&self) -> Option<&str>
pub fn category_name(&self) -> Option<&str>
A unique name, chosen by you, for your Call Analytics category. It's helpful to use a detailed naming system that will make sense to you in the future. For example, it's better to use sentiment-positive-last30seconds for a category over a generic name like test-category.
Category names are case sensitive.
sourcepub fn rules(&self) -> Option<&[Rule]>
pub fn rules(&self) -> Option<&[Rule]>
Rules define a Call Analytics category. When creating a new Call Analytics category, you must create between 1 and 20 rules for that category. For each rule, you specify a filter you want applied to the attributes of a call. For example, you can choose a sentiment filter that detects if a customer's sentiment was positive during the last 30 seconds of the call.
Trait Implementations
sourceimpl Clone for CreateCallAnalyticsCategoryInput
impl Clone for CreateCallAnalyticsCategoryInput
sourcefn clone(&self) -> CreateCallAnalyticsCategoryInput
fn clone(&self) -> CreateCallAnalyticsCategoryInput
1.0.0 · sourcefn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more