1
Improving QueueMetrics / Feature request: QM sanitize input for addmember, removemember, etc.
« on: January 20, 2010, 15:40:43 »
Hi all,
First of all, my apologies if this is already a feature, or if it has already been requested.
it would be benficial for us to have input sanitized when an agent adds themselves to a queue or puts themselves on break.
For example, if an agent adds themselves to a member, they have to put in something like 749@770 so if there was another field in configuration.properties where we could add a regular expression that would filter all data entered into "add member", "remove member", "pause" and "unpause" it would help keep the data going into queuemetrics accurate?
something like
addmember.regexp=7\d{1,2}+@7\d{1,2} ;;allows only something like "749@770"
addmember.regexp.errormsg="format incorrect, use AGENT@EXTENSION: example 749@770" ;;the error message shown if fail filter
removemember.regexp=7\d{1,2}+@7\d{1,2} ;;allows only something like "749@770"
removemember.regexp.errormsg="format incorrect, use AGENT@EXTENSION: example 749@770" ;;the error message shown if fail filter
pauseagent.regexp=7\d{1,2} ;;allows only something like "749"
pauseagent.regexp.errormsg="format incorrect, use AGENT NUMBER: example 749" ;;the error message shown if fail filter
unpauseagent.regexp=7\d{1,2} ;;allows only something like "749"
unpauseagent.regexp.errormsg="format incorrect, use AGENT NUMBER: example 749" ;;the error message shown if fail filter
if the input did not pass this regexp test, it would fail
Just a thought.
Cheers
First of all, my apologies if this is already a feature, or if it has already been requested.
it would be benficial for us to have input sanitized when an agent adds themselves to a queue or puts themselves on break.
For example, if an agent adds themselves to a member, they have to put in something like 749@770 so if there was another field in configuration.properties where we could add a regular expression that would filter all data entered into "add member", "remove member", "pause" and "unpause" it would help keep the data going into queuemetrics accurate?
something like
addmember.regexp=7\d{1,2}+@7\d{1,2} ;;allows only something like "749@770"
addmember.regexp.errormsg="format incorrect, use AGENT@EXTENSION: example 749@770" ;;the error message shown if fail filter
removemember.regexp=7\d{1,2}+@7\d{1,2} ;;allows only something like "749@770"
removemember.regexp.errormsg="format incorrect, use AGENT@EXTENSION: example 749@770" ;;the error message shown if fail filter
pauseagent.regexp=7\d{1,2} ;;allows only something like "749"
pauseagent.regexp.errormsg="format incorrect, use AGENT NUMBER: example 749" ;;the error message shown if fail filter
unpauseagent.regexp=7\d{1,2} ;;allows only something like "749"
unpauseagent.regexp.errormsg="format incorrect, use AGENT NUMBER: example 749" ;;the error message shown if fail filter
if the input did not pass this regexp test, it would fail
Just a thought.
Cheers