226 DAVOX Upload

Processes a DAVOX upload file.

The program prompts for the following:

• Client string password
• DAVOX upload filename; the file must reside in the data directory (/opt/msi/vNNa/env/environment/data)

For each record in the file, the program creates a new lease-level record in the mjl (Lease Notebook) table. The following items are used in creating the notebook record:

• The lease on the Davox upload record will be stored in the lease notebook record(mjl.app_lse_s).
• The date/time of the most recent call on the upload record, index 0 of the V21_RECORD's, result_table, fields: date/time, will be stored in the date/time entered of the lease notebook record(mjl.dt_ent_s).
• The status of the most recent call on the upload record, index 0 of the V21_RECORD's, result_table, field: status, will be used to lookup the LeasePak collection status code(RCO table). The collection status table will be used to determine other lease notebook field defaults. Using the Davox code/LPUX collection status table mapping below, the process will read the RCO table. If the Davox status does not have a corresponding LPUX collection status then the 'E' collection status will be used. The following items will be used to populate the lease level notebook table:
  • The lease level notebook record, follow-up date field, (mjl.dt_fol_s), will be calculated by taking today's date and adding the value stored in the rco.def_fol_mins_l.
  • The lease level notebook record, note type field, (mjl.note_type_s), will be populated using the value stored in the rco.def_note_type_s.
  • The lease level notebook record, collection status field, (mjl.col_stat_s), will be populated using the mapped collection status.
  • The lease level notebook record, note title field, (mjl.note_title_s), will be populated using the description value in the RCC table of the collection status code.
• The date/status/time of the of the upload record, index 1-4 of the V21_RECORD's, result_table, fields: date, status/time, will be stored in the info1_s field of the lease notebook record (mjl.info1_s). Each of these fields will be tagged with appropriate labels for readability purposes.
• All of the Davox upload record phone numbers will also be stored in the info1_s field of the lease notebook record (mjl.info1_s). Each of these fields will be tagged with appropriate labels for readability purposes.
• The following fields on the lease notebook record will have the following defaults:
  • mjl.prcs_s = 'N'
  • mjl.prio_c = '4'
  • mjl.to_s = 'DVX'
  • mjl.from_s = 'DVX'
  • mjl.info_s = NULL
  • mjl.private_c = 'Y'
  • mjl.lse_acc_s = 'D'
  • ntbk_rsn_s = ''
  • mjl.info2_s = NULL
  • mjl.info3_s = NULL
  • mjl.info4_s = NULL

Davox Code/LeasePak Collection Status Mapping

DAVOX Code	Description	LeasePak Collection Status
b	Busy	B
f	No Answer	A
g	High and Dry	A
h	No Dialtone	B
I	AMD	D2
j	Rescheduled	B
k	Called party hung up on hold	B
l	Called party hung up on message	D2
m	Called party hung up on BK message	D2
n	Invalid Phone #	14
o	All numbers invalid	14
p	Dropped from hold message	B
q	Modem/Fax	A
r	AMD Detected-End	D2
s	AMD Detected-left message	D2
t	Dial faulted	A
Undefined	Undefined status	E

This is the current layout of the Davox file upload record:

/*------------------------------------------------------!
!   V271 UPLOAD RECORD                                  !
!------------------------------------------------------*/
typedef struct _result_record {
        char    date_s          [6];            /* In MMDDYY format */
        char    username_s      [8];
        char    code_s          [2];
        char    time_s          [4];            /* In HHMM format   */
} RESULT_REC;

typedef struct _v271_record  {
        RESULT_REC  result_table     [5];
        char        portfolio_s      [2];
        char        company_s        [2];
        char        region_s         [2];
        char        office_s         [3];
        char        acct_num_s       [10];
        char        cust_res_phone_s [14];   /* In AREACODE+PREFIX+SUFFIX+EXTENSION */
        char        cust_empl_phone_s[14];   /* In AREACODE+PREFIX+SUFFIX+EXTENSION */
        char        coby_res_phone_s [14];   /* In AREACODE+PREFIX+SUFFIX+EXTENSION */
        char        coby_empl_phone_s[14];   /* In AREACODE+PREFIX+SUFFIX+EXTENSION */
        char        comment1_s       [75];
        char        comment2_s       [75];
        char        important_note1_s[75];
        char        important_note2_s[75];
} V271_RECORD;
	

Back to Utilities Menu

LeasePak  Documentation Suite

©  by NetSol Technologies Inc. All rights reserved.

The information contained in this document is the property of NetSol Technologies Inc. Use of the information contained herein is restricted. Conditions of use are subject to change without notice. NetSol Technologies Inc. assumes no liability for any inaccuracy that may appear in this document; the contents of this document do not constitute a promise or warranty. The software described in this document is furnished under license and may be used or copied only in accordance with the terms of said license. Unauthorized use, alteration, or reproduction of this document without the written consent of NetSol Technologies Inc. is prohibited.

Your document is loading...

This message should disappear within 5-15 seconds, depending on the size of the document and the speed of your connection to the Documentation Suite.

If you can still see this message after 20 seconds, try clicking the Refresh or Reload button on your Web browser.

If your document still does not load, refer to Document Load Troubleshooting for instructions on how to fix possible problems with either your Documentation Suite installation or Web browser setup.

If you do not have read access to the parent docsuite directory, you will not be able to load the Document Load Troubleshooting document. In this case, contact your network administrator for assistance.