Components installed with Engagement Messenger

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Components installed with Engagement Messenger

    The Engagement Messenger application installs various components essential for its functionality, including user roles, tables, and properties. Understanding these components helps customers configure and manage the application effectively.

    Show full answer Show less

    Key Features

    • Roles Installed:
      • Engagement Messenger Admin: Allows creation and editing of configurations for Embedded Messenger modules.
      • Engagement Messenger Read: Grants permission to view existing configurations for Embedded Messenger modules.
    • Tables Installed:
      • Chat Feature Instance: Stores configuration details for the chat feature.
      • Engagement Messenger Module: Contains a list of all messenger modules.
      • Feature: Defines messenger features.
      • Feature Instance: Details of feature instances for the messenger modules.
      • Greeting, Knowledge, and Search Feature Instances: Store configuration details for their respective features.
    • Properties Installed:
      • com.glide.cs.embed.cspframeancestors: Configures frame-ancestors policy for hosting Engagement Messenger.
      • glide.authenticate.multisso.enabled: Enables multiple provider Single Sign-On (SSO).
      • glide.ui.sessiontimeout: Sets user session timeout.
      • sncustomerservice.emails.customportal: Redirects notification emails to the exact request record for customer support.
      • sncsmec.proactiveinactivitytime: Defines the inactivity period to trigger proactive assistance.
      • glide.knowman.serviceportal.usenumberedurl: Displays article links with sysparmnumber for specified portal records.
    • Plugins Installed:
      • Customer Service (com.sncustomerservice)
      • Integration - Multiple Provider Single Sign-On Installer (com.snc.integration.sso.multi.installer)

    Key Outcomes

    By activating the Engagement Messenger application, customers can efficiently manage user roles, configure various features, and enhance customer interactions through streamlined notifications and proactive support measures. This ultimately leads to improved service delivery and customer satisfaction.

    Several types of components are installed with activation of the Engagement Messenger application, including plugins, tables, and user roles.

    Roles installed

    Table 1. Roles installed with the activation of the Engagement Messenger application
    Role title [name] Description Contains roles
    Engagement Messenger admin

    [sn_csm_ec.ec_admin]

    		 Creates and edits configurations for Embedded Messenger modules
    • sn_csm_ec.ec_read
    • snc_platform_rest_api_access
    • virtual_agent_admin
    • image_admin
    • sp_admin
    • ais_admin
    • catalog_builder_editor
    Engagement Messenger read

    [sn_csm_ec.ec_read]

    		 Can view existing configurations for Embedded Messenger modules None

    Tables installed

    Table 2. Tables added with the activation of the Engagement Messenger application
    Table Description
    Chat Feature Instance

    [sn_csm_ec_chat_instance]

    		 Stores configuration details of the Chat feature of the messenger modules.
    Engagement Messenger Module

    [sn_csm_ec_engmnt_center_module]

    		 Stores the list of all messenger modules.
    Feature

    [sn_csm_ec_feature]

    		 Stores the feature definitions for the messenger.

    Every feature instance of a messenger module is created from its feature definition.
    Feature Instance

    [sn_csm_ec_feature_instance]

    		 Stores the details of feature instances of the messenger module.
    Greeting Feature Instance

    [sn_csm_ec_greeting_instance]

    		 Stores configuration details of the Greeting feature of the messenger modules.
    Knowledge Feature Instance

    [sn_csm_ec_knowledge_instance]

    		 Stores configuration details of the Knowledge feature of the messenger modules.
    Search Feature Instance

    [sn_csm_ec_search_instance]

    		 Stores configuration details of the Search feature of the messenger modules.

    Properties installed with Engagement Messenger

    Table 3. Engagement Messenger properties
    Property Description
    com.glide.cs.embed.csp_frame_ancestors After activating the Glide Virtual Agent plugin (com.glide.cs.chatbot), you must use the com.glide.cs.embed.csp_frame_ancestors system property to enable the configuration of the frame-ancestors policy for the website where you want to host Engagement Messenger.

    Set the value of the com.glide.cs.embed.csp_frame_ancestors system property 'self' <your website URL>. For example, 'self' https://www.example.com

    • Type: string
    • Value: self
    • Location: System Properties
    glide.authenticate.multisso.enabled Set the glide.authenticate.multisso.enabled system property to true to enable multiple provider SSO.
    • Type: true | false
    • Value: self
    • Location: System Properties
    Note:
    If you want to enable only a guest user experience for your customer service portal, you can ignore this configuration.
    User session time-out glide.ui.session_timeout Set a user session timeout value for the glide.ui.session_timeout system property to a value that is greater than or equal to your website time-out.
    • Type: integer
    • Value: 30
    • Location: System Properties
    Note:
    If you want to enable only a guest user experience for your customer service portal, you can ignore this configuration.
    sn_customerservice.emails.customportal

    Set the URL of your third-party customer support portal so that the notification emails that your customers get contain URLs that redirect them to the exact request record that they submitted.

    These notification emails are sent in scenarios such as submitting a case, requesting a service, requesting a field technician, or booking a walk-up appointment.

    • Type: string
    • Value: None
    • Location: System Properties
    For example, if your customer support portal is https://www.example.com/support, then set the property value to https://www.example.com/support.
    sn_csm_ec.proactive_inactivity_time Set the inactive period (in seconds) to trigger proactive help in Engagement Messenger.
    • Type: integer
    • Value: 2
    • Location: System Properties
    glide.knowman.serviceportal.use_numbered_url The property contains a comma-separated list of service portal record sys_ids. For any portal record specified in this property, the article link will be displayed with the sysparm_number URL parameter instead of sys_kb_id.
    • Type: string
    • Value: None
    • Location: System Properties

    Plugins installed

    • Customer Service (com.sn_customerservice)
    • Integration - Multiple Provider Single Sign-On Installer (com.snc.integration.sso.multi.installer)