From 6baafb24c24c370b96fb547600dfb5702ac2a77f Mon Sep 17 00:00:00 2001 From: mattf Date: Wed, 11 Oct 2023 19:41:12 +0000 Subject: [PATCH] Retiring the terms master/slave on admin screens git-svn-id: svn://192.168.202.10@3764 3d104415-ff17-0410-8863-d5cf3c621b8a --- agc_2-X/trunk/www/vicidial/admin.php | 6 +++--- agc_2-X/trunk/www/vicidial/help_documentation.txt | 10 +++++----- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/agc_2-X/trunk/www/vicidial/admin.php b/agc_2-X/trunk/www/vicidial/admin.php index 84d1807d..78deb196 100644 --- a/agc_2-X/trunk/www/vicidial/admin.php +++ b/agc_2-X/trunk/www/vicidial/admin.php @@ -44339,9 +44339,9 @@ if ($ADD==311111111111111) echo ""._QXZ("Report Default Format").": $NWB#settings-report_default_format$NWE\n"; - echo ""._QXZ("Slave Database Server").": $NWB#settings-slave_db_server$NWE\n"; + echo ""._QXZ("Secondary Database Server").": $NWB#settings-slave_db_server$NWE\n"; - echo ""._QXZ("Reports to use Slave DB").": \n"; $Vreports_ARY = explode(',',$Vreports); $Vreports_ct = count($Vreports_ARY); @@ -44361,7 +44361,7 @@ if ($ADD==311111111111111) $custom_rslt=mysql_to_mysqli($custom_stmt, $link); if (mysqli_num_rows($custom_rslt)>0) { - echo ""._QXZ("Custom Reports to use Slave DB").": \n"; echo "\n"; $allowed_rpt_stmt="SELECT allowed_custom_reports from vicidial_user_groups where user_group='$LOGuser_group'"; $allowed_rpt_rslt=mysql_to_mysqli($allowed_rpt_stmt, $link); diff --git a/agc_2-X/trunk/www/vicidial/help_documentation.txt b/agc_2-X/trunk/www/vicidial/help_documentation.txt index 8eddc39c..ec185c0e 100644 --- a/agc_2-X/trunk/www/vicidial/help_documentation.txt +++ b/agc_2-X/trunk/www/vicidial/help_documentation.txt @@ -1,4 +1,4 @@ -# version: 20230927090101 +# version: 20231011152901 users-user User ID This field is where you put the users ID number, can be up to 20 digits in length, Must be at least 2 characters in length. We strongly recommend not reusing user accounts for different users, for reporting accuracy. To disable a user account, set the Active option to -N-. users-pass Password This field is where you put the users password. Must be at least 2 characters in length, unless the User Password Minimum Length system setting is enabled, which will require a longer password. Only letters and numbers are allowed in user passwords. A medium strength user password will be at least 10 characters in length, and a strong user password will be at least 20 characters in length and have letters as well as at least one number. It is recommended that you use a longer password if possible, stringing together several unrelated words with no spaces, and a number somewhere in the string. The maximum size of a password is 100 characters. users-force_change_password Force Change Password If this option is set to Y then the user will be prompted to change their password the next time they log in to the administration webpage or the agent screen. Default is N. @@ -1224,9 +1224,9 @@ settings-default_phone_registration_password Default Phone Registration Password settings-default_phone_login_password Default Phone Login Password This is the default phone web login password used when new phones are added to the system. Default is test. settings-default_server_password Default Server Password This is the default server password used when new servers are added to the system. Default is test. settings-report_default_format Report Default Format Determines whether the reports will default to display in text or html format. Default is TEXT. -settings-slave_db_server Slave Database Server If you have a MySQL slave database server then enter the local IP address for that server here. This option is currently only used by the selected reports in the next option and has nothing to do with automatically configuring MySQL master-slave replication. Default is empty for disabled. -settings-reports_use_slave_db Reports to use Slave DB This option allows you to select the reports that you want to have use the MySQL slave database as defined in the option above instead of the master database that your live system is running on. You must set up the MySQL slave replication before you can enable this option. Default is empty for disabled. -settings-custom_reports_use_slave_db Custom Reports to use Slave DB This option allows you to select the custom reports that you want to have use the MySQL slave database as defined in the option above instead of the master database that your live system is running on. You must set up the MySQL slave replication before you can enable this option. Default is empty for disabled. +settings-slave_db_server Secondary Database Server If you have a MySQL secondary, or replicating, database server then enter the local IP address for that server here. This option is currently only used by the selected reports in the next option and has nothing to do with automatically configuring MySQL primary-secondary replication. Default is empty for disabled. +settings-reports_use_slave_db Reports to use Secondary DB This option allows you to select the reports that you want to have use the MySQL secondary database as defined in the option above instead of the master database that your live system is running on. You must set up the MySQL secondary replication before you can enable this option. Default is empty for disabled. +settings-custom_reports_use_slave_db Custom Reports to use Secondary DB This option allows you to select the custom reports that you want to have use the MySQL secondary database as defined in the option above instead of the master database that your live system is running on. You must set up the MySQL secondary replication before you can enable this option. Default is empty for disabled. settings-default_field_labels Default Field Labels These fields allow you to set the name as it will appear in the agent interface as well as the administrative modify lead page. Default is empty which will use the hard-coded defaults in the agent interface. For the first 19 fields, which are form entry fields, you can also set a label to ---HIDE--- to hide both the label and the field. Another option for most fields is ---READONLY--- which will display but not allow an agent to modify the field. One more option for most fields is ---REQUIRED--- which will force an agent to populate that field on all calls before being able to hang up and disposition each call. For the REQUIRED option to work, the campaign must have Allow Required Fields enabled. settings-admin_screen_colors Admin Screen Colors This feature allows you to set different color schemes and logo for the administrative web screens. These can be defined in the Screen Colors section. Default is default, for the standard blue screen colors settings-agent_screen_colors Agent Screen Colors This feature allows you to set different color schemes and logo for the agent screen. These can be defined in the Screen Colors section. Default is default, for the standard blue screen colors @@ -1444,7 +1444,7 @@ alt_multi_urls Alternate Multi URLs This page allows you to define Alternat amm_multi AM Message Wildcards This page allows you to define Am Message Wildcards that will check lead data from the defined lead fields for matches in the defined order specified on this page. For example, if you add a wildcard with the word -vacation- tied to the vendor_lead_code field, and the lead being played a message has -vacation- in that field, then it will hear the message defined in that AM Message Wildcard record. If you want to delete a wildcard, it must first be set to not active, then you can click on the DELETE link below the SUBMIT button for that wildcard entry user_list_new_limits User List New Lead Limits If the system setting for New Leads Per List Limit is enabled, then this page allows for the setting of per-user per-list new lead limit overrides to those List limits. This feature will only work properly if the campaign is set to either the MANUAL or INBOUND_MAN Dial Method and No Hopper dialing is enabled. user_inbound_calls_today User Inbound Calls Today This page will show you the User Inbound Calls Today, the Max Limits and the Call Credits for all users in the system. If one of the limits is reached, you will see notes showing you which one was reached. -custom_reports_admin-report_name Report Name The report name that the report will be referred to as in the system for purposes of user group access and slave server use in the system settings. The report name may not be the same as any other custom report, nor may it be the same name as one of the standard system reports. +custom_reports_admin-report_name Report Name The report name that the report will be referred to as in the system for purposes of user group access and secondary server use in the system settings. The report name may not be the same as any other custom report, nor may it be the same name as one of the standard system reports. custom_reports_admin-domain Domain The domain that the report is located at. This will be combined with the path name to make a complete URL to use as a link from the reports page. You may leave this blank when the report is located on the same server as the web admin and just use the path name field to make a local URL. custom_reports_admin-path_name Path name The path on the domain where the report is located. When the domain is blank it is assumed that the report is housed on the local web server. custom_reports_admin-constants Preset constants Here is where a user can define a preset value to pass to the report when it is accessed from the custom report link. This is useful if the user is viewing a report that accepts multiple variables that change the report output and there is a certain set of report parameters the user frequently uses and they wish to save time by coming to the report with those values already set.
Variable name -The enters the variable name here. Names allow alphanumeric characters, underscores, and to a limited extent brackets. Brackets are used to pass an array to the report and should be placed at the end of the variable name, such as 'var_name[]'. The interface will condense brackets by removing any characters within a pair of them, and will also remove unmatched brackets.
Value -Then, the user enters a variable value in the 'Value' field, either by selecting a pre-defined variable value or a custom value. With the exception of 'datetime' and 'filedatetime', all pre-defined variables are dates in yyyy-mm-dd format. The predefined values are: 'today' for today's date, 'yesterday' for yesterday's date, 'datetime' which is a timestamp in the format of 'yyyy-mm-dd hh:ii:ss', 'filedatetime' which is an all-numeric timestamp in the format 'yyyymmddhhiiss', and 6/7/8/13/14/15/30days, all of which are the date 6/7/etc days ago. If the user would like to define their own value for the variable, they can set the value to 'Custom Value', then fill out the custom value in the field to the right. Click 'ADD' to add the variable name/value pair to the presets to include in the report. Values will be URL-encoded prior to being entered in the database.