" /> Update "retrieved records" - Genesys CTI User Forum
« previous next »
Pages: [1]   Go Down

Author Topic: Update "retrieved records"  (Read 3102 times)

toumtoum7

  • Guest
Update "retrieved records"
« on: November 22, 2007, 04:29:00 PM »
Advertisement
Hi all,

When I start a campaign with OCM, some records (20) of the calling list take the record_status=retrieved. That's ok. :)

My question is how can I really update one record of the calling list ? Indeed, when I update the table (oracle) of the calling list, the record takes the new value. But when I stop and unload the campaign, the record takes the old value... Is anybody know where Genesys load this 20 records in his memory ?  ???

Thanks,

toumtoum
Logged
Marked as best answer by on May 05, 2025, 03:22:54 AM

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Update "retrieved records"
« Reply #1 on: November 22, 2007, 05:44:03 PM »
  • Undo Best Answer
    • It's a store procedure the one that handles this, now it is strongly restricted NOT NO MODIFY records when campaign is loaded. One basic reason is that agent is maybe with the call and any update he may do will be rejected, also on the final result you will never know if that call was called or not.
    Logged

    toumtoum7

    • Guest
    Re: Update "retrieved records"
    « Reply #2 on: November 23, 2007, 01:34:58 PM »
    thanks cavagnaro for your reply,
    do you know where can i find this store procedure ?

    ++
    toumtoum
    Logged

    bcyk

    • Guest
    Re: Update "retrieved records"
    « Reply #3 on: November 27, 2007, 04:17:26 AM »
    Please never try to change calling list records in database table or in storage procedure; otherwise, high possibility of duplicated calls issue.

    These retrieved records are in OCServer memory space!

    Genesys OCS 6.5 and above include an enriched set of OCS API protocols using Key/Value pairs in EventUserUser. One of API protocols is to update retrieved records via OCServer itself. OCServer receives valid third-pary request and it searches records in memory and then database table for proper updating.

    A common required function is to remove "Opt-out" (Do-Not-Call) records in active campaigns; thus, programming is required!


    regards
    Logged
    Pages: [1]   Go Up
    « previous next »