" /> OCS List Formats - Genesys CTI User Forum

Author Topic: OCS List Formats  (Read 3980 times)

Mark Newcomb

  • Guest
OCS List Formats
« on: January 01, 1970, 12:00:00 AM »
Advertisement
I am having some trouble moving my 5.1 suite outbound lists into a 6.1 OCS solution. I can see that there are some changes in the underlying data......

DIAL_SCHED_TIME and CALL_TIME have swapped around in 6.1
New columns TZ_DBID, CAMPAIGN_ID, CHAIN_ID, CHAIN_N in 6.1
Removed columns MAX_ATTEMPTS, TZ_OFFSET, ORIGINATION (were in 5.1)

Has anyone tried to do this before? If so how did you do it! I have had two thoughts so far for our old lists (there will only be a few during the upgrade process).......either use of a database view to confuse OCS into thinking it is a 6.1 list OR writing a script to create a new table in the correct format.......

Does anyone else have any thoughts on this?
Mark

Craig

  • Guest
OCS List Formats
« Reply #1 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • I would create new lists in the 6.0 format and import the data.
    For each records ensure that the following fields are setup :


    record_id= [incrementing number starting from 1]
    tz_dbid=0
    campaign_id=[campaign DBID e.g. 101 for first campaign created]
    chain_id= [same as record_id]
    chain_n=0

    Lome

    • Guest
    OCS List Formats
    « Reply #2 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • With a lot of effort I was able to copy the current list in Excel, add the necessary fields, then export it into another Excel and then have OCS read it.

    Where exactly did you get stuck?

    Mark Newcomb

    • Guest
    OCS List Formats
    « Reply #3 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • I havn't got stuck just trying to see if anyone had any other bright ideas....... basically the majority of our lists are autopopulated by other systems. Ensuring that all of these systems are 6.1 compliant prior to upgrading our sites would be a huge task hence our attempts to confuse OCS. I think we will try the database view first off.........