Usecase Design Console (UCD Console)
The use case design console (also known as the UCD console) is the primary area where conversation design is done for a particular skill or tenant. Users can create new skills, intents, entities and finally the dialog nodes to handle user utterances and customize conversational experience.
This console helps to configure the usecases to interact with the customers in a useful way by addressing their queries and providing suitable responses.
- Go to Admin Dashboard Console under BigFix AEX Cognitive Consoles and click on Usecase Design Console.
- The Usecase Design Console appears.
- Select SKILLS tab. Two buttons are available under this tab:
- Create Skill
- Import and Create Skill
- Click on CREATE SKILL button under SKILLS tab to create a new skill.
- The CREATE SKILL form appears:
- The following fields need to be populated:
- Skill Name: Enter the name of the new skill.
- Description: Provide brief description about the skill.
- Language: Select the preferred Language from the drop-down.
- Click on Add button.
- The new skill will be created and will be visible under the
SKILLS tab.
- Click on OPEN THIS on the newly added skill.
- The following screen appears with new tabs under the newly
added skill:
- Click on IMPORT AND CREATE SKILL button under the SKILLS tab to create a new skill with the existing intents, entities and dialog nodes.
- It prompts you to Import the JSON file.
- Click on BROWSE button and select a JSON file that you want to upload.
- Click on IMPORT FILE.
- Once the file is imported a success message appears and the imported intents, entities and dialog nodes become visible under INTENT, ENTITY and DIALOG NODES tabs respectively.
- Click on OPEN THIS button present on each skill to open an existing skill.
- To view the entities, intents and dialog nodes associated with the skill click on ENTITY, INTENT and DIALOG NODES respectively.
- The Kebab menu (the three dots menu) present on each skill allows you to open a menu with additional options. The following options are available:
- Export: Allows to download the JSON file associated with a particular skill.
- Import: Allows to import the existing intents, entities, and dialog nodes for a particular skill. Follow the steps explained above ( Step 11 to Step 13 ) to perform the import action.
- MULTISKILL on Usecase design enables switching between the multiple skills. The console facilitates user to be able to add skills which he chooses to switch between and choose a default skill for the conversation. The Multi Skill Orchestration includes the default method, waterfall method, broadcast method and the conductor-follower method. In default method there are option to select the skill while in other methods the transition between skills would be automated.
- Below is an explanation of how each method of skill orchestration differs and is similar to the others:
- Default Model:
- This is the already existing (and till now the only) method in multi skill functionality. Here we get options to select multiple skills in the use case design console and associate a button name to it and select one default skill among the selected skill.
- In the chat window we get the options to choose from the skill that we saved in UCD multi skill and further communication continues with the selected skill.
- Waterfall Model:
- It is a priority-based method i.e., the skill with highest priority would be checked first. If it provides the correct answer (doesn’t reaches to the Anything else node) then BigFix AEX does not go to the subsequent skills.
- If execution reaches to the last skill and still reaches Anything else of the last skill, the message associated with that node would be returned. On the Use Case Design Console, the user selects the skills and their priorities.
- Broadcast Model:
- This method is based on the Highest confidence score of skill i.e., BigFix AEX checks all the skill at once and provides response from the skill that has the highest confidence score.
- In this method, we select a default skill, and that skill provides us with the welcome message, also in cases where we don’t get appropriate response, we will have Anything else node message from this skill.
- On Use Case Design Console, the user selects the skills and chooses one default skill.
- Conductor-Follower Model:
- In the Conductor-Follower method, there are 2 types of skill selection,
- conductor skill: In this skill, the user adds 1 skill.
- follower skill: In this skill, the user has multiple categories to add.
- The conductor skill acts as a default skill and is responsible for the transition of skill i.e., based on the user’s query, the conductor skill selects a follower skill for further communication.
- The conductor skill, based on specific conditions, sends the id of the selected follower skill as part of intent and this id in turn is used to call the skill for further communication.
Multiskill Configuration – Default Model
- Perform the following steps for MULTISKILL configuration using the Default Model:
- Go to the BigFix AEX Tenant and open use case design Console.
- After Opening the use cases design Console, you can find the Multi skill button. Click Multiskill.
In the Usecase Design console the MULTISKILL feature is visible only if the instance is enabled with the multi skill configuration.
- The Multi Skill Configuration page appears. The page lists all the available models. Select the model and the console displays the corresponding options based on the selection.
- Select the Default Model and click ‘Continue’.
If user selects the None option in the Multi skill Configuration page, by default, it takes the default model for the skills to be mapped for the tenant.
- In Default Model, populate the Skills field by using the Choose A Skill drop-down. Multiple skills can be added in the Skills field. Enter the Button Name for the skill. Select the Default Skill by clicking Choose Your Option drop-down.
The Button Name must be unique in the default model.
- Click Save to configure the multi skill.
- The following confirmation message appears:
- Click Ok to save the configuration. The following success message appears:
- To delete a skill in the default model, click on the delete icon corresponding to the skill to be deleted.
- The following confirmation message appears. Click Ok to confirm the action.
Multiskill Configuration – Waterfall Model
- Perform the following steps for MULTISKILL configuration using the Waterfall Model:
- In the Multi Skill Configuration page, select Waterfall Model and click Continue.
- In the Waterfall Multi Skill Configuration, Select Skills by using the Choose a Skill drop-down.
- In the waterfall model, user has the options to move the skill up and down. To move a skill up, click the Move up arrow and to move a skill down, click the Move down arrow .
- Click Save to configure the multi skill.
- The following confirmation message appears:
- Click Ok to save the configuration. The following success message appears:
- To delete a skill in the waterfall model, click on the delete icon corresponding to the skill to be deleted.
- The following confirmation message appears. Click Ok to confirm the action.
Multiskill Configuration – Broadcast Model
- Perform the following steps for MULTISKILL configuration using the Broadcast Model:
- In the Multi Skill Configuration page, select Broadcast Model and click Continue.
- In Broadcast Multi Skill Configuration, select Skills using the Choose a Skill drop-down. Select the Default Skill by clicking Choose your option drop-down.
- Click Save to configure the multi skill.
- The following confirmation message appears:
- Click Ok to save the configuration. The following success message appears:
- To delete a skill in the broadcast model, click on the delete icon corresponding to the skill to be deleted.
- The following confirmation message appears. Click Ok to confirm the action.
Multiskill Configuration – Conductor-Follower Model
- Perform the following steps for MULTISKILL configuration using the Conductor-Follower Model:
- In the Multi Skill Configuration page, select Conductor-Follower Model and click Continue.
- In Conductor-Follower Multi Skill Configuration, select one Conductor Skill by using the Conductor Skill drop-down. Then add one or multiple Follower Skills by using Choose a Skill drop-down. Enter an Intent Name for the skill.
- In the Conductor-Follower model skill, the intent names displayed in the following figures are added:
- Click Save to configure the multi skill.
- The following confirmation message appears:
- To delete a skill in the Conductor Follower model, click on the delete icon corresponding to the skill to be deleted.
- In Conductor Follower model, we must add the Intent value while adding the Context Variable.
- The Skill Intent Name must be unique in the Conductor Follower Model.
- A skill that is configured in Multiskill, cannot be deleted from the tenant workspace. The user must delete the skill from Multiskill configuration to delete it from the tenant workspace.
- There must be at least one skill in the Multiskill configuration.
- The skill name must be unique in all the models.
- There must be Intent Value added while adding the Context variable in all the Multiskill models.
- Once the Multiskill configuration is done, select INTENT tab. If none of the skills is selected, then a pop up will be displayed saying select a skill.
- Progress bar for loading the intents associated with the skill is visible as shown in the above figure.
- If intents are present, the list of intents will be populated in the intent table. Refer the following figure:
- To add new intent, perform the following steps:
- Click on ADD Intent button under the Intent tab. The Add Intent screen appears:
- The intent name can contain letters (in Unicode), numbers, underscores, hyphens, and periods. The name cannot consist of ‘..’ or any other string of only periods. Intent names cannot contain spaces and must not exceed 128 characters.
- A success message appears and the intent value appears in the intent table.
- To delete an intent, click on the delete icon corresponding to the intent that you want to delete.
- For handling utterances and intent recognition, variations provide a robust mechanism to train and recognize user conversations in natural language. Variations should be added so the intent recognition system can generalize. New Variations can also be added to an intent by performing the below steps:
- Click on any value of an intent from the intent table under INTENT tab. A slide navigation slides in containing the Intent name at the top.
- Add a new variation and submit it by clicking on Add button.
- The newly added variation appears in the variation table as sown below.
- You can delete the variation by clicking the delete icon corresponding to the variation.
- Intents can also be edited from the main intent page, click on edit icon for which the entity name user wants to edit it.
- A modal will open to edit the intent name, where you can make changes as needed.
- Now, select the ENTITY tab. If none of the skill is selected, then a pop up will be displayed saying select a skill.
- If the entities are present, the list of entities will be populated in the entity table.
- The following columns are available:
- Entity Name: Displays the list of Entities.
- Fuzzy Match: Contains the toggle buttons that display the status of fuzzy logic of the entity.
- Modified: displays the time when the property of the entity was last changed.
- Action: contains the delete icon to delete the corresponding entity.
- Perform the following steps to add Entity.
- Click on ADD Entity button present under ENTITY tab. The Add Entity screen appears:
- The entity name can contain letters (in Unicode), numbers,
underscores, and hyphens. Do not include spaces in the name. The
name cannot be longer than 64 characters. The name cannot be
prefixed with ‘sys-’ as it is reserved for system
entities.
- Add the Entity by clicking on ADD button. A success message appears:
- The newly added Entity appears in the Entity table.
- Values can be added to an Entity by performing the following steps:
- Click on a value of an entity in entity table under the ENTITY tab. A side navigation slides in containing the entity name at the top.
- Add a new entity value and submit it by clicking on Add button present there.
- Select the type from the dropdown. Two types are available:
- Pattern option allows to put regular expressions for values.
- Synonym option allows to match the text itself.
- The newly added entity value appears in the entity value table.
- To delete an entity value, click on delete icon corresponding to the entity value that you want to delete.
- Take the following steps to add synonyms to the Entity:
- Click on any value of an entity in entity value table to add synonyms to it. A side navigation slides in containing the entity name at the top.
- Add a new synonym and submit it by clicking on Add button.
- The newly added synonym value appears in the entity value table.
- To delete a synonym, click on delete icon corresponding the synonym that you want to delete.
- Entity names can be edited by clicking on edit icon for which the entity name user wants to edit.
- A dialog box will open to edit the entity name:
- Perform the following steps to enable system entities:
- Pre-built entities allow users to extract and work on commonly used language references, such as dates, numbers, etc.
- Click on the System Entities button under the ENTITY tab.
- A window appears showing the available system entities. The console provides several system entities, which are common entities that you can use for any application. Enabling a system entity makes it possible to quickly populate your skill with training data that is common to many use cases.
- Click on the toggle of any system entity to enable it. For example, the @sys-number system entity matches any numerical value, including whole numbers, decimal fractions, or even numbers written out as words.
- You can now use the enabled entities in you dialog nodes directly.
- Contextual Entities can also be used with UCD console; these entities allow BigFix AEX to detect user context from the utterance. Contextual entities provide a faster way of recognizing newer entities without explicitly creating them every time.
- The value which is annotated in a variation of the intent will reflect in an entity by yellow color.
- Select DIALOG NODE tab. If none of the skill is selected, then a pop up will be displayed saying select a skill.
- The dialog node’s id and description (optional) appear on
the card.
- While adding the Context variable, skill_change should be in true condition.
- While configuring the Anything else node, the anything_else condition must be ‘True’.
-
- To add new nodes, click on ADD NODE button under the DIALOG NODES tab.
- To see the child nodes associated with the Node, click on Expand More.
- The associated child nodes open.
- On clicking of Expand Less, the child nodes collapse.
- The following actions can be performed on each available node by clicking on the kebab menu (three dots menu) placed on each node:
- Add Child Node: A new node will be added as child
- Add Node Above: A new node will be added above the node.
- Add Node Below: A new node will be added below the node
- Delete: Deletes the Node
- Move: Move within Nodes
- Moving a dialog node that you have created can be moved anywhere in the dialog tree. You might want to move a previously created node to another area of the flow to change the conversation. You can move nodes to become siblings or peers in another branch.
- On the node if you want to move, click 3 dots icon, and then select Move.
- Select a target node that is in the tree near where you want to move this node. where user will find three options i.e., As child node, below node and above node as shown in fig.
- Jump to: Jumps to the following options as defined:
- Response
- Assistant Recognize
- Wait for User Input
- Jump to: In order to perform “Jump to” on a node, click on type of Jump to selector i.e. Wait for User Input, Assistance Recognize, or Response. Select destination node by clicking on moving point (MP icon )
- The source node of Jump to option will be labeled with Jump to (destination node id) after a pop-up message stating that Jump to has been applied successfully on Watson.
- To delete the ‘Jump to’, click on delete icon present next to Jump to (destination node id) label.
- Once Jump to has been initiated but needed to be cancelled before selecting a destination node; in that case click on cross icon present on the right bottom of the console.
- By clicking on Open placed on each node, you can view the form where you can perform multiple actions like view or modify the settings of the node, add context, and add Response etc.
- Click on the setting icon to check the settings of form. The following screen appears:
- To set digressions, click on that toggle button of digression and to set multi condition response, click on toggle button of MCR.
- If MCR is enabled, the form shows the fields specific to MCR
form.
When dialog node form is opened for first time, it shows standard form with fields and buttons i.e., node name, condition, add context and response type.
- Enter Node Name and Condition.
- Click on ADD CONTEXT and ADD RESPONSE to add new context and response respectively. Refer the image below to understand how to add conditions, context variables and Responses.
- The Intent name must be prefixed with # and the Entity name must be prefixed with @ to match the condition. You can also use logical operators such as &&, || and! in conditions. To save any entity/intent matched as a context variable use the format given in the picture above.
- The name of context variable can contain any upper and lowercase alphabetic characters, numeric characters (0-9), and underscores. You can include other characters, such as periods and hyphens, in the name. However, if you do so, then you must specify the shorthand syntax $(variable-name) every time you subsequently reference the variable.
- The value of context variable can be any text that you want, but if you want to capture an intent/entity from user input, use the following expression syntax to capture it:
- <?@entity_name?>.
- Clicking anywhere in the form submits the fields.
- Addition or deletion will be enabled once the fields are submitted successfully. You can add more responses by clicking on the ADD RESPONSE button:
- If there is more than one response in a dialog you can choose one of the three settings that the console provides.
- Sequential: The system returns the first response variation the first time the dialog node is triggered, the second response variation the second time the node is triggered, and so on, in the same order as you define the variations in the node.
- Random: The system randomly selects a text string from the variations list the first time the dialog node is triggered, and randomly selects another variation the next time, but without repeating the same text string consecutively.
- Multiline: When the response is shown to the user, both response variations are displayed, one on each line. For example, if you have 3 response variations: Hi, Hi there, and Hi there friend. The multiline response would be as follows:
- Hi
- Hi there
- Hi there friend.
- When MCR is enabled, the MCR form is displayed with fields and button i.e., node Title, Condition and an “ADD MULTICONDITION” button. The pop-up message will be displayed stating that MCR is enabled. By default, the ADD MULTICONDITION button is disabled. Perform the following steps to configure multicondition:
- The values are fetched and auto populated in the respective fields and ADD MULTICONDITION button will be enabled.
- Click on ADD MULTICONDITION button to add new multiconditions.
- All these fields on MCR form get submitted on focus out. Addition or deletion options are enabled once the fields are submitted successfully.
- Click on edit icon associated with each multicondition to add other values to that multicondition. A screen appears with fields i.e., Condition, Add Context, Response Type with a Submit button.
- The condition field inside the edit screen will have same value as the multicondition which can be edited.
- Click on ADD CONTEXT and ADD RESPONSE to add new context and response of the multicondition respectively.
- All these fields on MCR modal form will get submitted by clicking on the Submit button below.
- A success message appears once the form is submitted successfully. Addition, Deletion or Edit of new multicondition will be enabled once the edited details are submitted successfully.
- Close the form by clicking outside of the form.
- You can chat and test the use cases configured if they are responding as per the requirement or not. Perform the following steps to do so:
- Click on TRY IT on the UCD Console under Dialog Nodes tab. A chat console appears.
- The Try it out panel slides in as shown in the following image. Use the text area at the bottom to enter your query and click on TEST to send it.
- The response looks like follows:
- Here you can see the console detected the entity @sys-person:Lisa. Click on the blue location pin to open the dialog node that was triggered by your input.
- Click on the CLEAR button on the top to remove any previous chat from the Try it out panel.
- Click on the MANAGE CONTEXT button to create or make changes to context variables.
- Enter the variable name for context and then click on the plus (+) icon to add value as desired.
- If any intents are matched, it will show up as follows. Here the intent #turn_off is detected:
- Clicking on the eye icon opens the list where it shows all the intents and the confidence score of the intent for the input query.
- The Analyse feature lets the user upload the usecases and its variations and verify what is the predicted intent and usecase for them.
- The ANALYSE button is present under Intent, Entity and Dialog Nodes tab as shown in below figure:
- When ANALYSE button is clicked the following screen pops up:
- Clicking on DOWNLOAD SAMPLE CSV downloads a csv file which is a reference template to upload the usecase variations file.
- Once the file is uploaded the READ button gets enabled.
- When we click on Read button, the data is uploaded from the csv file to the table on the screen and the RUN TEST button gets enabled. Refer the below screenshots:
- If the CSV is in improper format the following error alert appears as shown in the figure below:
- When there is no data in the csv file and it is uploaded, the Read button gets disabled, and the table shows the text “No data uploaded”.
- Once the rows from CSV are read and the data on the screen is uploaded and displayed, the RUN TEST button is enabled. On the click of RUN TEST button, the analysis of variations for all the data rows starts.
- The screen displays the progress of the analysis for all the rows of the table and the RUN TEST button is disabled. Once it’s completed the progress bar disappears.
- On the upload of a different file the READ button gets enabled.
The WYSIWYG (What You See Is What You Get) editor in the Use Case Design Console provides a low-code approach to building conversations and dialogues for BigFix AEX. This provides a simpler point and click editable view to create rich HTML and plain text BigFix AEX responses, which are the same as what the end user would see when using BigFix AEX. This reduces the need for cognitive SMEs to write HTML tags explicitly and makes the use case/response creation easy.
The WYSIWYG editor is the default setting for the Use Case Design console and does not need any configuration. The following part of this section highlights the key functionalities of the editor:The default editor, present in the earlier versions as shown in the below figure, has been replaced by the new WYSIWYG editor.
Since 6.0, the default editor for any node in the use case design console looks like the following figure (opens in the side navigation bar):
The following are the Key items in the new response panel:
- Node Title & Settings (Gear icon )
- Context Variables
- Select Response Type
Node title
Node Title can be edited to provide a meaningful node name
Clicking on the gear icon on the right side of the node title displays the following options:
- Multi Condition Response (MCR)
- Digressions
MCR - On enabling (MCR) Multi Condition Response toggle, the editor changes to a multi-condition editor.
It allows users to add multiple conditions by clicking on the “Add Multi Condition” button. Here, the response editor is similar to the early versions.
MCR nodes can be moved up and down by clicking on the Up/Down arrow buttons corresponding to the node that you want to move.
The following actions can be taken on each condition:
- Edit: Each condition can be edited by using the edit icon corresponding to the condition to be edited. You can edit the condition to provide a response and context variables.
- Jump: Each condition can be edited for a jump using the jump button corresponding to the condition to which you want to apply this option. Clicking on the Jump button displays three conditions: assistant recognize, wait for user input and response. On selection of the appropriate condition, the use case design console shows flags on the available nodes on the Landing Node screen. Clicking on any of the flags attaches that node to the jump.
- You can also cancel the jump using the close button on the Landing Node screen.
- Delete: Clicking on Delete icon deletes the corresponding condition.
Digressions - Digressions can also be enabled using the same gear icon for context switching use cases.
Context variables
Context variables are present in a collapsible and can be added based on requirement. More variables can be added by using the Add Context button.
Select Response Type
SME can select the different type of response which is sent by the current node to the BigFix AEX UI to the end user. The following responses can be configured using the correct radio button:
- Sequential
- Multiline
- Random
Sequential: Responses are displayed in sequence in the BigFix AEX response in the same chat block
Multiline: Responses are shown in ordered or unordered sequence in the BigFix AEX response; however they are in separate chat blocks.
- To use multiline, enable the multiline flag as true.
- Also use <OL> tag to set sequence of responses
Random: Responses are shown randomly from the list of responses when a node is executed. Response blocks can be added by using the + icon below the response type radio button. On adding a new response, the editor changes the focus to the latest response.
Focus can be changed to any other response block by clicking on the number.
Each response block, when added, has the four following response types:
- Text
- HTML Editor (Default)
- API Rule
- Webhook
Text (HTML Tags & Plain Text, Adaptive Card JSON):
HTML Editor: Each response block, when added, has the HTML editor type as its default response type.
Refer to Capabilities of Default HTML Editor section to understand the basic capabilities of HTML editor response type.
API Rule: API rule provides a simpler way to call Openwhisk functions or integration actions directly from the use case design editor.
The following salient points are relevant:
- A drop-down list of existing rules in the current tenants is shown.
- An appropriate rule can be selected, and relevant parameters can be passed along with values.
- The added parameters are passed to the selected rule.
Webhook: Webhooks provide a quick way to call API services with relevant headers and body parameters to fetch a response.
- Multiple webhooks can be added to the same response editor with new responses in the same node.
- Webhook requests can be GET or POST.
- Response should be JSON only
- Required parameters can be added based on the API service.
- It is recommended to check headers and authentication using a service like POSTMAN so the correct values are passed in the Webhook response.
- Text and HTML response blocks have a limit of 4096 characters as the response created in the editor is saved in Watson and sent to the user when a node is executed.
- For HTML editor (default type) responses, the 4096 character limit is calculated based on the raw HTML text, which might have several more characters than the characters visible in the view.
- When the character limit exceeds 4096, the entire editor response is automatically changed to an SOP and saved, however these technicalities are abstracted from the user creating the response.
- Response Type can be changed to other types as well, but the change will delete all the data from the current type, and you will encounter a warning before making the change.
A response block can also be deleted using the delete button . This action deletes the current block on focus and returns focus to the previous block. If there is only one response and that it deleted, a new first block is auto added.
Capabilities of Default HTML Editor:
The following pointers outline the basic capabilities of the default HTML editor response type.
- The editor contains a components bar which can be added to the response based on the requirement.
- The buttons represent basic HTML pre-built components, which in the background add the requisite HTML code. This allows the response creator or the cognitive SME to focus on the user experience and doesn’t require knowledge of HTML scripting.
- The components when clicked, are added to the response section, as shown in the example below, where a table is added below a paragraph section.
HTML Editor Components
Editor components are self-explanatory; these components are listed as follows in the same order as in the screenshot above:
Heading
Subheading
Paragraph
Unordered list
Ordered list
Card: The Card component provides a pre-built HTML component that contains a title, body, and a button bar.
- More cards can be added to a carousel by clicking the button. This adds cards in a sequence, next to the current card. The focus also changes to the latest card in the carousel.
- With the addition of new cards, navigation icons are also added to the UI to move between the cards.
- Any card can be deleted by using the delete icon at the bottom of the card.
Table
Image
- When a user clicks on the Image component, a dialog box appears where a public image URL must be provided for the image to be displayed in the image card.
- On providing the right URL, the picture would be rendered inside the image panel.
Translation
- This option uses BigFix AEX’s fast translation capabilities to translate text in over 51 languages at once, right from the use case design console’s HTML editor.
- Multilingual connector for the current tenant must be activated before use of this feature.
- This functionality can be used only once for the current set of text. If the text needs to be changed, the current node needs to be deleted and re-created for the translation to be triggered again.
- This is not the most ideal functionality for translation (since automated translation always has lower accuracy than manual), however for quick use case implementation in different languages this capability should be used, language should always be validated by a language SME.
- Not all 51 languages are available on the chat console. However, they are currently being converted and saved as a knowledge repository in the backend.
- To use this functionality, after a response block is suitable for translation, the user needs to click on the translate component button and wait for the window to confirm the translation is done. In the following image, the translation component is translating the statement “This is a test paragraph for translation.”
- Once the translation is complete, you will see the following dialog box confirm the translation of all 51 languages, except any failures, which are also listed.
- Translation of all successful languages can be accessed using the drop-down which is populated post translation, like in the following screenshot:
- On clicking the required language, the translation appears in the same response block. We have selected Dutch from the drop-down in this example for our original text.
- The response for failed languages will be a default “No translation” when selected from the drop-down. For example, the failed translation into the Hebrew language.
Component Properties
Each component, when added to the response, shows options which are applicable to it on click, a list of all these options is as the following ( they will change based on every component ):
Insert Image:
- This option adds an image inline or as a new block. Insert an image inline based on the component.
- For cards, images are always inserted inside the body of the card, above the card title, the Upload Image dialog box does not show an inline option.
- For other components, the Upload Image dialog box displays the option of inserting an image inline.
- Otherwise, all the images are inserted inline by default.
Insert Link:
- This option inserts a hyperlink in the response, which is added inline wherever the cursor is clicked. There are two types of links:
- Generic redirection link
- Custom link (which is of MCT input URL type) can be used when redirection and submission to BigFix AEX are to be done.
Insert Button:
- This option inserts an MCT input button at the required location:
- In case of cards, a button is added to the bottom button bar
- In case of other components, a button is added at the cursor location
- Name of the button can be changed by clicking on the button
Bold:
- Makes the select text bold
Italic:
- Makes the selected text italic
Underline:
- Underlines the selected text
Move Up:
- Moves the component under focus (current component) above the previous component
Move Down:
- Moves the component under focus (current component) below the previous component
Delete:
- Delete the current component from the response
Row Header: (Available only in the Table Component)
- Makes the top row (row header) of the current table bold.
Column Header: (Available only in Table Component)
- Makes the first column (column header) of a table bold
Add Column: (Available only in Table Component)
- Adds a new column to the right for the current table
Add Row: (Available only in Table Component)
- Adds a new row to the bottom of the current table
Delete Column: (Available only in Table Component)
- Deletes the current column (where the cursor is present) from the current table
Delete Row: (Available only in Table Component)
- Deletes the current row (where the cursor is present) from the current table
Some examples of different options based on the component can be seen in the screenshots below:
A new component is always added to the end of the current response by default; however, it can be moved up or down using the appropriate action.
Finally, at the end you may see an option to assistant response:
- Wait for Reply
- Skip User Input