Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Disabling the Augmented Agent Assistant for an individual screen

Updated on July 14, 2020

Business needs sometimes demand the disabling of the Augmented Agent Assistant component for individual screens. To disable the component on a per-screen basis, enable the HideCSRAssistant data transform on the flow action, which disables the CSR Assistant.

Before you begin: Ensure that you unlock the ruleset that you want to edit. If you do not unlock the ruleset, you cannot save the data transform. Either check the ruleset out to a branch, or save the ruleset as an unlocked ruleset version for editing. You can also use Private edit to create a private copy for editing.
To disable the Augmented Agent Assistant feature for individual screens, complete the following steps:
  1. In the navigation pane of Dev Studio, on the App tab, click Classes to view a list of classes.
  2. For the required class, click the Expand to show child rows icon to expand the class.
  3. Expand the Process category, and then expand the Flow Action category.
  4. To open the screen on which you want to disable the Assistant, click the required flow action.
    Displaying required flow action
    Displaying required flow action
  5. On the Action tab, in the Pre-processing or Post-processing section, in the Apply data transform autocomplete box, select .HideCSRAssistant.
  6. This data transform hides the Assistant for all screens in the flow from this point onward.
  7. Optional: To enable the Assistant for subsequent screens in the same flow, repeat steps 1 to 6 and select the .ShowCSRAssistant data transform.
  8. Click Save.
  • Previous topic Disabling the Augmented Agent Assistant for a service case
  • Next topic Using Augmented Agent during the live chat

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us