activities
latest
false
- Release Notes
- Overview
- The nature of communications
- The anatomy of an extraction
- General fields
- Automation architecture
- Uploading data to Communications Mining
- Using the Dispatcher Framework
- Activities reference
Communications Mining Activities
Last updated Oct 11, 2024
Automation architecture
Communications Mining provides a list of extractions for you to automate, and the following diagram describes how you actually acquire this list of extractions.
The Communications Mining Stream processes communications and sends them to the Dispatcher. From there, they are routed to
UiPath Orchestrator, which distributes them into several numbered queues, including a Human-in-the-loop (HITL) queue. Each
numbered queue initiates an Automation Process, with the HITL queue generating an Automation Process logic specifically for
HITL.
Working from left to right, the data is first uploaded into Communications Mining, it then progresses through the platform and lands in something called a Stream. A robot then picks up the communication from this stream and dispatches it to an Orchestrator queue for processing. There are three main elements to understand within this architecture:
- How are communications uploaded into the Communications Mining platform?
- How does the Dispatcher process work?
- How do the downstream automations access the needed information?
