Overhaul of Campaign Imported in INVADE CATI Manager

Owned by Scott D Child
Oct 19, 2020
1 min read

Depending on how the end user imported data into the INVADE CATI Manager the saved and subsequent started campaign could overwrite base setting. These have been created to encourage good practice for utilising the INVADE Dallier engine at peak performance.

In summary an option to load campaign parameters from CampaignMeta (if exists) ignoring whatever is saved in file based campaign params files. Default is false as INVADE WebConsole (file based campaign params) should take precedence all the time

New parameters are tested as follows

  • Create a campaign in Cati Manager,

  • set CampaignParamsFromCampaignMeta to true in invade-genghis6.config under DiallerAsm

  • start campaign with specific dial method i.e. Predictive

  • Check Webconsole if dial method is still Predictive

  • Stop campaign

  • Start campaign again

  • Check Webconsole if dial method is still Predictive

Second scenario

  • change CampaignParamsFromCampaignMeta to false

  • start campaign

  • change campaign dial method in webconsole, commit & save

  • stop campaign

  • start campaign

  • check that dial method is the one you set in webconsole and not in Cati Manager

 .