Outbound7.1 calling list refresh

[bogdan]

Hello,

I want to add&remove data (clients) from the callinglist, but I seem to have a problem with removing... When I delete records from the callinglist (from behind by sql) I can't seem to make the OCS reread the database without unload/load from OCM. I read the documentation but even there I didn't find anything anything about how to recheck the database, or how to decrease the buffer size or something ...

Can someone help me?

Thanks

[cavagnaro]

You shouldn't delete records if they are in a already loaded campaign. Why? Because they could be on OCS memory buffer already and still will be dialed and after the call handling is finished you will still have the record there. If you don't want to call a record for any reason you should use OCS API Events like donotcall.

[bogdan]

I have a very dynamic environment, I can't use this solution in my case ... It's like reinventing the wheel.

[cavagnaro]

There is no other way to let know OCS what happened with the records on its buffer, your method is for Genesys also like reinventing the wheel...I don't see any other solution. Guys any ideas?

[bcyk]

there is no other safe method to remove records from OCS internal buffer except using OCS API event as pointed by cavagnaro
Not sure if there is any function available for this case in OCS SDK

Would following steps help?
    1. Call API to set 'DONOTCALL' or equivalence
      -> to instruct OCS to write records from internal buffer, if any, to database table
      -> such OCS API event in Gensys OCS 7.2 is available for sure; pls check 7.1
    2. delete the set of records using SQL command/procedure after step 1

[Dionysis]

Removing the records is also not good from an SQL perspective.  Having missing records from indexes etc is not generally good practice.

However, you can stop records from dialing using SQL.  It's fairly straight forward, all you need to do is add a line to your SQL:
[code]
where record_status <> 2
[/code]
If a record is retrieved (in the OCS' buffer) when you run a query with this restriction it will not update, so this is not the final solution.

Alternatively, you could filter the records you want removed first, and then remove them through SQL.  This will remove them from the OCS buffer if they are in a retrieved state. 

[bogdan]

OK, not delete the records... how about updating them (by sql) with a another status (or something) to be rejected by the filter and then trigger an action to OCS to recheck only this records? Is this a feature?

[Fra]

What about stopping OCS, running whatever sql you want and restarting OCS?

[Dionysis]

You can do this, however you need to ensure that the records are not retrieved when you update them.

If record_status is =2 then the OCS has the record in memory and your changes will have no effect.

Now, about OCS in general.  Is there any particular reason you are using 7.1?  I recommend upgrading to at least the latest release of 7.2, 7.6 would be better if possible, and ditch 7.1 entirely.  7.2 has a large number of fixes over 7.1.  Things like maintaining the treatment history after campaigns are unloaded, or filters are applied.  This may not sound important, but it destroys any intelligence you put into setting your treatment strategies.  In my opinion, any version of outbound between 5.1 and 7.2 is not worth using.