Configuration

Firstly, we need to set up some configurations in the Config.xlsx file located in the Data folder. When you open the Settings tab, you'll find five settings waiting for you:

• CommunicationsMiningProjectName - this is the name of the project containing your dataset.
• CommunicationsMiningDatasetName - this is the name of the dataset containing your stream.
• CommunicationsMiningStreamName - this is the name of your stream.
• RunContinuously - When set to True, this process will not exit when the stream is empty and rather continuously poll, waiting for new communications to be added to the stream. Typically people set this to False and schedule the process to run at a high frequency within Orchestrator.
• PollWaitTime - Only applicable when running Continuously - how long to wait between stream polls, in seconds.

Note: Be sure to use the exact API names for your project, dataset, and stream. Using titles instead will cause the process to fail, so it's important to double-check.

Once you've set up this information in Config.xlsx, the dispatcher framework will be directed to the stream you configured. Next up, you need to define some business logic to determine which communications should be routed to which Orchestrator queues.