Added more screen labels for non-form fields

git-svn-id: svn://192.168.202.10@3428 3d104415-ff17-0410-8863-d5cf3c621b8a
2021-04-22 02:26:19 +00:00
parent 160744cf78
commit 5b1a9ff87d
7 changed files with 469 additions and 56 deletions
@@ -1,4 +1,4 @@
-# version: 20210417101401
+# version: 20210421221501
 users-user	User ID	<QXZ>This field is where you put the users ID number, can be up to 8 digits in length, Must be at least 2 characters in length.</QXZ>
 users-pass	Password	<QXZ>This field is where you put the users password. Must be at least 2 characters in length. 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.</QXZ>
 users-force_change_password	Force Change Password	<QXZ>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.</QXZ>
@@ -1138,7 +1138,7 @@ settings-report_default_format	Report Default Format	<QXZ>Determines whether the
 settings-slave_db_server	Slave Database Server	<QXZ>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.</QXZ>
 settings-reports_use_slave_db	Reports to use Slave DB	<QXZ>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.</QXZ>
 settings-custom_reports_use_slave_db	Custom Reports to use Slave DB	<QXZ>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.</QXZ>
-settings-default_field_labels	Default Field Labels	<QXZ>These 19 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. 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.</QXZ>
+settings-default_field_labels	Default Field Labels	<QXZ>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.</QXZ>
 settings-admin_screen_colors	Admin Screen Colors	<QXZ>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</QXZ>
 settings-agent_screen_colors	Agent Screen Colors	<QXZ>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</QXZ>
 settings-agent_chat_screen_colors	Agent Chat Screen Colors	<QXZ>This feature allows you to set the different colors that are used for the users chatting within the internal chat window in the agent screen. These can be defined in the Screen Colors section, and only the five standard and three alternate colors are used. Default is default, for a standard set of eight colors</QXZ>
@@ -1196,7 +1196,7 @@ screen_labels-label_id	Screen Label ID	<QXZ>This field needs to be at least 2 ch
 screen_labels-label_name	Screen Label Name	<QXZ>This is the descriptive name of the screen label entry.</QXZ>
 screen_labels-user_group	Admin User Group	<QXZ>This is the administrative user group for this record, this allows admin viewing of this record restricted by user group. Default is --ALL-- which allows any admin user to view this record.</QXZ>
 screen_labels-label_hide_field_logs	Hide Label in Call Logs	<QXZ>If a label is set to ---HIDE--- then the agent call logs, if enabled on the campaign, will still show the field and data unless this option is set to Y. Default is N.</QXZ>
-screen_labels-default_field_labels	Default Field Labels	<QXZ>These 19 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. 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.</QXZ>
+screen_labels-default_field_labels	Default Field Labels	<QXZ>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.</QXZ>
 screen_labels-active	Active	<QXZ>Set whether the screen label is active or not.</QXZ>
 screen_colors	Screen colors give you the option of setting a different color scheme and logo for the web interface in the System Settings.	<B><QXZ>Screen colors give you the option of setting a different color scheme and logo for the web interface in the System Settings.</QXZ></B>
 screen_colors-colors_id	Screen Colors ID	<QXZ>This field needs to be at least 2 characters in length and no more than 20 characters in length, no spaces or special characters. This is the ID that will be used to identify the screen colors in the system.</QXZ>