activities
latest
false
- リリース ノート
- 概要
- The nature of communications
- The anatomy of an extraction
- 一般フィールド
- Automation architecture
- Uploading data to Communications Mining
- Using the Dispatcher Framework
- アクティビティ リファレンス
重要 :
このコンテンツの一部は機械翻訳によって処理されており、完全な翻訳を保証するものではありません。
Communications Mining アクティビティ
Last updated 2024年10月11日
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?
