Agent Only Callback Campaign Lock - not locking campaign_id

[linuxknight]

Greetings, we are using a recent svn build VERSION: 2.2.0-183 BUILD: 90511-0910 where we had paid for this requested feature.

It works great and has the desired behavior except for one minor problem.

When an agent enters the manual callbacks, dispositions it again as a callback it rewrites the campaign_id field to the currently logged in campaign.

Is it a trivial matter to keep this field locked once its been set in a particular campaign?

[mflorell]

That's not really a trivial matter to keep the campaign_id locked, and why would you want to do that really? That creates all sorts of issues with agent time acounting and campaign stats.

Locking the campaign_id in this manner mean some of the call logging as written just wouldn't work, because it depends on the campaign_id being that of the agent's currently logged in campaign.