Jump to: navigation, search
(Update with the copy of version: draft)
(Update with the copy of version: draft)
Line 3: Line 3:
  
  
The Genesys Co-browse DOM Restrictions Editor makes it easier for you to hide sensitive customer data from agents and restrict control of elements in a co-browse session. The Editor handles most of the configuration complexity behind the scenes and allows you to focus on your restrictions. You can implement two types:
+
The Genesys Co-browse DOM (Document Object Model) Restrictions Editor makes it easier for you to hide sensitive customer data from agents and restrict control of elements in a co-browse session. The Editor handles most of the configuration complexity behind the scenes and allows you to focus on your restrictions. You can implement two types:
  
 
*'''DOM control'''—the agent sees the content but won't be able to interact with it. For example, clicking a button or a link won't work for the agent, even when Co-browse is in Write Mode. The agent will see a green border surrounding content with DOM control.
 
*'''DOM control'''—the agent sees the content but won't be able to interact with it. For example, clicking a button or a link won't work for the agent, even when Co-browse is in Write Mode. The agent will see a green border surrounding content with DOM control.
Line 17: Line 17:
 
*view a list of existing restrictions.
 
*view a list of existing restrictions.
 
*logically group your restrictions.
 
*logically group your restrictions.
*apply a restriction to the current web page to all web pages.
+
*apply a restriction to all web pages, or to the page or set of pages that match the regular expression.
 
*view all restrictions on the current web page.
 
*view all restrictions on the current web page.
 +
 +
 +
To allow users to log into the DOM Restrictions Editor, add them to the '''<Tenant name> Administrators''' Access Group.
  
 
{{CloudStep_Stack
 
{{CloudStep_Stack
 
|title=  
 
|title=  
 
|text=
 
|text=
 +
  
 
Watch the video tutorial on how to use the DOM Restrictions Editor.  
 
Watch the video tutorial on how to use the DOM Restrictions Editor.  

Revision as of 16:47, May 15, 2019

Genesys Co-browse DOM Restrictions Editor

The Genesys Co-browse DOM (Document Object Model) Restrictions Editor makes it easier for you to hide sensitive customer data from agents and restrict control of elements in a co-browse session. The Editor handles most of the configuration complexity behind the scenes and allows you to focus on your restrictions. You can implement two types:

  • DOM control—the agent sees the content but won't be able to interact with it. For example, clicking a button or a link won't work for the agent, even when Co-browse is in Write Mode. The agent will see a green border surrounding content with DOM control.
  • Data masking—the agent sees masked content as asterisks (******) instead of characters, and masked images will be grayed out. The agent will see a purple border surrounding masked characters and images.
Important
Since masked content is also DOM controlled (non-interactive), the DOM Restrictions Editor shows Data Masking as DOM Control and Data Masking.

With the DOM Restrictions Editor, you can easily

  • create, edit, or delete a restriction.
  • have an optional description.
  • view a list of existing restrictions.
  • logically group your restrictions.
  • apply a restriction to all web pages, or to the page or set of pages that match the regular expression.
  • view all restrictions on the current web page.


To allow users to log into the DOM Restrictions Editor, add them to the <Tenant name> Administrators Access Group.


Watch the video tutorial on how to use the DOM Restrictions Editor.

Comments or questions about this documentation? Contact us for support!