Jump to: navigation, search

Web Engagement Cluster:pacing:proactiveRatio

(Rpfeiffer used the OptionEdit action.)
Line 10: Line 10:
 
{{DraftOption
 
{{DraftOption
 
|hidden=false
 
|hidden=false
−
|default=0
+
|default=100
−
|valid=
+
|valid=An integer from 0 to 100
−
An integer between 0 and 100
+
|takeseffect=After server restart
−
 
+
|shortdesc=Specifies the minimum percentage of agent resources that are reserved to handle proactive interactions. If <tt>0</tt> is specified, no resources are specifically allocated to handle proactive interactions (note that proactive traffic is still allowed). If <tt>100</tt> is specified, all resources are allocated to handle proactive interactions and no reactive interactions are allowed.
−
|takeseffect=After start/restart
 
−
|shortdesc=Specifies the minimum percentage of agent resources that are reserved to handle proactive interactions. If 0 is specified, no resources are specifically allocated to handle proactive interactions (note that proactive traffic is still allowed). If 100 is specified, all resources are allocated to handle proactive interactions and no reactive interactions are allowed.
 
 
}}
 
}}
 
{{PubExtended}}
 
{{PubExtended}}

Revision as of 20:35, March 22, 2018


View in ref guide.

Edit this option          Publish this option          Clear draft content


Published Option

proactiveRatio

Default Value: 100
Valid Values: An integer from 0 to 100
Changes Take Effect: After server restart


Specifies the minimum percentage of agent resources that are reserved to handle proactive interactions. If 0 is specified, no resources are specifically allocated to handle proactive interactions (note that proactive traffic is still allowed). If 100 is specified, all resources are allocated to handle proactive interactions and no reactive interactions are allowed.

Draft Option

No draft option

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