I’m a new genesys users and administrator. I try to search forum but i didint find an answer. where can i change this priorities permanently? In every campaigns in OCM priorities is set:
Record Type Priority N records
General 2 2
Campaign Rescheduled 1 2
Campaign CallBack 1 2
when i change it in OCM it is only work until i didnt restart the campaigns.
These options must be configured in the Outbound section of the Application, Campaign or Campaign Group objects. Wherever these options are configured, they apply to Campaign Group objects.
Priorities set at the Campaign Group level have the most precedence while those set at the Application level have the least. In addition:
Values set at the Application level are applicable for all Campaign Groups.
Values set at the Campaign level should be applicable for all Campaign Groups created for the given Campaign.
The priorities set by the options are displayed as a grid in Genesys Administrator at Operations > Outbound Contact > Dialing Sessions > Priorities
The options are a fairly new addition to OCS, though they were configurable globally in the OCM object previously. They are documented in the current Outbound Deployment Guide on the Genesys Support site. Are you using an out of date document?
i have a one more question: I added these options but they do not change in OCM. In addition, I have two campaigns that have different value in “priority” and “n records” but i dont see this value in Configuration Menager (There are no such functions at all)
Is there a specific reason you want to change this? Be very careful changing these priorities, it can cause other issues you’re not expecting.
It’s very common to end up with a buffer of only Campaign Callbacks and Rescheduled Records which are not actually due to dial yet (especially using the default settings), meaning your OCS will not dial because from it’s perspective, it has no data, even though you might have a list full of untouched records.
These priorities work in conjunction with the optimal and minimum buffer values in the campaign group, and the “n records” represents the number of records retrieved each time the buffer is filled. So if you have a large number as the first priority and a small difference between optimal and minimum buffer sizes, you will only get the first priority records retrieved. Which will lead to very slow dialling.
We have a calling list with dialing filter set: Start_Date >= 2017-07-17 order by attempt asc, Start_Date desc. Without changing the priority and N_records options as i mentioned before, dialing filter did not working properly.
