Overview

This feature is designed to streamline the process of selecting and integrating assets directly from a Digital Asset Manager (DAM) into a form or user interface (UI). Here's a more detailed breakdown of how it works: 

• Asset Selection from DAM: This feature enables users to select assets directly from a Digital Asset Manager (DAM), a centralized platform for managing digital content. Instead of uploading assets manually, users can browse and choose assets from the library.

• Text or Rich Text Format: The selection process works with text or rich text fields, where users can include multimedia (images, videos, links) in their content without switching interfaces.

• Asset Selection Interface: When users click on an asset selection option, a pop-up allows them to filter or search for assets by categories, tags, or file types, streamlining the selection process.

• Direct Integration into Form/UI: After selection, the asset is automatically inserted into the text or rich text field or integrated into the form/UI, enabling real-time asset inclusion.

• Efficiency and Consistency: This feature enhances efficiency by using centralized assets from the DAM, ensuring consistency and eliminating the need for manual uploads or formatting.

​

Key Benefits

• Time Savings: Reduces the need for manual uploads and asset management by integrating DAM assets directly into forms or UI. 

• Consistency: Ensures that the correct and standardized assets are used across various forms or content without needing to search multiple places. 

• Seamless User Experience: Makes it easier for users to integrate rich media into their input, enhancing content quality with minimal effort. 

​

Example Use Case

• Marketing Team: A marketing team uses this feature to quickly select product images, logos, or promotional materials stored in their DAM and insert them directly into email templates or website content forms. 

• Content Management: A content writer can select relevant images or videos from a DAM and embed them directly into a blog post or article without leaving the content editor. 

​

Various Fields in Asset

• Asset Types

  1. Text: 

     • Definition: A simple text asset consists of plain text without any formatting, such as bold, italics, or different font styles. It is typically used for short, straightforward content like titles, labels, or descriptions. 

     • Example: "Welcome to Our Website" (plain text, no formatting) 

  2. Rich Text: 

     • Definition: A rich text asset allows for text formatting, including bold, italics, underline, different font sizes, colors, and the inclusion of images or hyperlinks. It provides more flexibility for creating visually appealing and styled content. 

     • Example: "Welcome to Our Website! Explore our new features here" (formatted with HTML tags or through a rich text editor).

  3. Dynamic Asset:

     • Definition: A Dynamic Asset allows you to load and display content based on a variable Asset ID, enabling personalized asset rendering in real time. At times, when you do not have a fixed asset and neither Text nor Rich Text options are suitable, because the asset may change based on certain conditions, you can select Dynamic Asset from the Asset Type dropdown. Once selected, you must provide the Asset ID in the Dynamic Asset field. This ID can be stored in a variable and selected using the source selector. Refer to the screenshot below.

     • Example: If you are running 10 different campaigns and want to send emails to customers based on the campaign selected, each campaign may require a unique email template. In this case, you can pass the corresponding template ID dynamically. Based on the selected campaign, the Guided Workflow will automatically pick the right template, and a preview of the corresponding email will be shown to the agent on the Guided Workflow screen.

       ​

       ​

       ​

​

​

• Asset: If you click on Asset, a window will pop up and you can choose from Digital Asset Manager (DAM) as shown below:

  ​

  ​

  ​

• Visibility Conditions: A rule or set of rules that determine whether a specific element, field, or component is visible to users on screen. These conditions are typically based on factors such as user roles, permissions, field values, or contextual data. Visibility conditions ensure that users only see relevant information, improving usability and security. 

  • Example  

    • Condition: Display a "Priority Escalation" section if the "Ticket Priority" is set to "High." 

    • Implementation: Visibility Condition: Ticket_Priority == 'High' 

    • Result: The "Priority Escalation" section appears only for high-priority tickets. 

• Make Text Copiable: This will allow the end user to copy the text of the HTML code.