Page 1 of 1
Disable buttons on client interface
Posted:
Tue Mar 23, 2010 12:18 pm
by lat3450
How can i disable some buttons on the client interface?
The buttons i want to disable are:
WEB FORM, PARK CALL, TRANSFER - CONF, SEND DTMF.
Thanks guys.
Posted:
Tue Mar 23, 2010 1:56 pm
by shariq
Hire a programmer for customization of the agent interface.
Or you may consult at
http://vicidial.com/consulting/customization.html
Posted:
Tue Mar 23, 2010 2:17 pm
by lat3450
shariq, i'm a programmer buddy. (allthough the word programmer do not make justice to my skill set ;-) )
I was thinking about some options that may exists on the admin interface to do so.
So if you know the code, whay don't you share with all the group what part of vicidial.php to work on.
Any secific function, maybe a reference to a code line, something that can get somebody interested started.
Posted:
Tue Mar 23, 2010 2:28 pm
by shariq
I was thinking about some options that may exists on the admin interface to do so
No built in feature to enable/disable
So if you know the code, whay don't you share with all the group what part of vicidial.php to work on
I dont know, you can search the image file name within the code.
Any secific function, maybe a reference to a code line, something that can get somebody interested started
No specific function, line no. can be change in different versions.
Posted:
Tue Mar 23, 2010 2:40 pm
by lat3450
Thanks for your input.
Posted:
Tue Mar 23, 2010 2:45 pm
by mflorell
There is an option in admin.php to disable the TRANSFER - CONF button.
Posted:
Tue Mar 23, 2010 3:02 pm
by lat3450
Is it the option under User/Vicidial Transfers?
Any recomendation to do the same for other buttons from the code itself?
Posted:
Tue Mar 23, 2010 6:29 pm
by mflorell
We have added similar options for clients that requested them, it's really just a matter of adding the DB field, the option in admin.php and the option in vicidial.php
Posted:
Wed Mar 24, 2010 9:46 am
by shariq
@Matt,
Does it not effect any other area?? It means i can modify any table of vicidial database (by adding more fields in the last) within the same table without any effect on the existing system.
Posted:
Wed Mar 24, 2010 9:55 am
by boybawang
edit vicidial.php to remove those buttons
Posted:
Wed Mar 24, 2010 10:33 am
by boybawang
for send dtmf you need to find this line:
- Code: Select all
<div class="text_input" id="SendDTMFdiv"><span STYLE="background-color: <?php echo $MAIN_COLOR ?>" id="SendDTMF"><a href="#" onclick="SendConfDTMF(session_id);return false;"><IMG SRC="./images/vdc_LB_senddtmf.gif" border=0 alt="Send DTMF" align=bottom></a> <input type=text size=5 name=conf_dtmf class="cust_form" value="" maxlength=50></div></span><BR>
Posted:
Wed Mar 24, 2010 10:36 am
by boybawang
for park call:
- Code: Select all
document.getElementById("ParkControl").innerHTML ="<a href=\"#\" onclick=\"mainxfer_send_redirect('ParK','" + lastcustchannel + "','" + lastcustserverip + "');return false;\"><IMG SRC=\"./images/vdc_LB_parkcall.gif\" border=0 alt=\"Park Call\"></a>";
Posted:
Wed Mar 24, 2010 10:38 am
by boybawang
for web form :
- Code: Select all
document.getElementById("WebFormSpan").innerHTML = "<a href=\"" + TEMP_VDIC_web_form_address + "\" target=\"" + web_form_target + "\" onMouseOver=\"WebFormRefresH();\"><IMG SRC=\"./images/vdc_LB_webform.gif\" border=0 alt=\"Web Form\"></a>\n";
its all in vicidial.php you just have to do a find
Posted:
Wed Mar 24, 2010 11:19 am
by lat3450
boybawang, thanks a lot for the reply, i appreciate it a lot.
I already did it, the best think is to find the ID for the div controls and disable the DIV control itself as you show and also comment out all lines referencing the control ID in the PHP code ( there are several per control) otherwise i get an error.
If anyone is interested in removing some funcionality from the client interface look for this in the code:
WebFormSpan, ParkControl, XferControl, SendDTMFdiv, busycallsdisplay, AgentAlertSpan, VolumeUpSpan, VolumeDownSpan, AgentMuteSpan.
And the comment out the lines referencing to it.
Thanks again.
Posted:
Thu Mar 25, 2010 3:34 pm
by williamconley
would it be easier to just make the item itself invisible or disabled? (style sheet) then it's still there, does not toss an error, and the "on/off" feature will not be as persistent in the damage
Posted:
Thu Mar 25, 2010 3:40 pm
by lat3450
Yes, it can be acomplished that way too!
Posted:
Thu Mar 25, 2010 3:44 pm
by williamconley
if you show the code on the actual agent screen it's fairly easy to "find" the control in question.
then you need merely locate that same control in the agent screen's php file ... and add the appropriate html tag to make it invisible when the page loads. that should have zero effect on the "programming" of the page itself, as the control is still there.
Posted:
Fri Mar 26, 2010 10:34 am
by lat3450
William,
I think this is a good feature to add thru the administration side.
Do you find value on it?
If so, can it be requested?
Re: Disable buttons on client interface
Posted:
Sun Oct 20, 2013 10:31 am
by mav2287
I know this is a very old threat and I'm not sure if anything ever came of this but I to had to hide the webforms and record buttons this weekend. We use force all on recordings so I copied the blank.gif file on top of the other files.
- Code: Select all
cp blank.gif vdc_LB_startrecording.gif
cp blank.gif vdc_LB_startrecording_OFF.gif
cp blank.gif vdc_LB_webform.gif
cp blank.gif vdc_LB_webform_OFF.gif
cp blank.gif vdc_LB_webform_two.gif
cp blank.gifvdc_LB_webform_two_OFF.gif
If it ever gets added to the code I think a hide record button and hide webform button toggle in the campaign settings would be great.
Re: Disable buttons on client interface
Posted:
Sun Oct 20, 2013 8:13 pm
by williamconley
sounds a lot like a feature request. not so much a support request. LOL
perhaps you could consider posting this on the features board as a new post and then post your solution in the Vicidial Issue Tracker (with a link to that post in your features board post ...). In which case you stand a fighting chance it will happen some day in the distant future. Much more likely if you were to create a method to make it a preference yourself and post a diff file against the latest SVN code. Then it may not be so distant.
Or you could sponsor the addition to ensure it actually happens. That works even better.