Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: Genesys User on February 02, 2009, 10:05:46 AM
-
Hi Guys,
Just wanted to know if there any standard input for uploading the data in the Genesys Calling List ? I believe we can only upload the data in .rsl or .lst format …But is there any tool that Genesys provides that could enable me convert the data from excel format to an lst or rsl format?
Thanks…
-
Hi,
As I know there isn't such tool - but it is easy to right makro which prepare data from excel sheet to file.
Regards
jbobinsk
-
It would be really great if you can share any such macro code with me ....would make my life much easier
Thanks..
-
Makro should be individual to excel - because the structure of data.
I have very old one which have implemented 6.5 structure of calling list. You should to make small modification to make it work. Of course I have changed description from Polish to English - and I don't know if something is not missing, so you have to debug it a little.
Regards
jbobinsk
-
There are two methods to import calling list records
1. Import function in Outbound Contact Manager (OCM)
2. OCS SDK (separate license and programming effect are required!)
OCM accepts ASCII text file as import calling list records, one record per line. Many mandatory data fields can be omitted; thus, default values will be automatically inserted by OCM.
Below is a list of system fields for Genesys 7.2 OCS
Please verify them with the version you're using.
[font=Courier]
No. Field name Default value Remark
1 record_id N/A Must be omitted; assigned by OCM
2 contact_info None Must be given; the called number
3 contact_info_type Home Phone Possible value are {Business With Extension, Direct Business Phone, E-mail Address, Home Phone, Mobile, Modem, No Contact Type, Pager, Pin Pager, Vacation Phone, Voice Mail}
4 record_type General To be omitted; use default value
5 record_status Ready To be omitted; use default value
6 call_result Unknown Call Result Must be set to 'Ok'
7 attempt 0 To be omitted; use default value
8 dial_sched_time None Omitted
9 call_time None Omitted
10 daily_from 8:00:00 AM Should be set according to application 24-hour format: hh:mm:ss, zero-filled
11 daily_till 6:00:00 PM Should be set according to application 24-hour format: hh:mm:ss, zero-filled
12 tz_dbid PST Must be set to local Time Zone code
13 campaign_id None Omitted
14 agent_id None Omitted
15 chain_id N/A Running number in an import call list per Customer
16 app_id None Omitted
17 chain_n 0 Set to 1 for single contact/customer; Set to 1,2,3,4,... for multiple contacts/customer of the same chain_id
18 email_subject None Omitted
19 email_template_id None Omitted
20 group_id None Omitted
21 media_ref None Omitted
22 switch_id None Omitted
23 treatments None Omitted[/font]
User-defined fields are similar; they may be omitted if they are configured as "optional"
In general, a site-specific conversation program will be programmed to retrieve customer record fields and to generate *.lst file.
Hope it saves your time by combinating above Excel macro file
-
Thanks a lot for sending across the macro ...but I think you have a password set for accessing the macro script ...could you share the password as well
Thanks again ...
-
Sorry - I forgot.
Now you have without password.
regards
jbobinsk
-
thanks a lot ..
-
I've always found it much easier to interact with your calling list database directly rather than using OCM to load data.
Why not simply use a DTS package that takes an Excel file as input and then pumps the records into your DB directly? This would be far more efficient than using OCM and much more customisable.
-
Thats a good idea aswell ... building a dts package to import the data ...Iam also thinking of creating a .net application to do the .lst conversion and also to import it to the calling list db using the sdks