业务逻辑

You'll need to set up all your business logic in the GetDestinationQueue workflow, which you can find in the Framework folder. This page takes one input—the Communications Mining StreamResult that's currently being processed—and produces two outputs: the Destination Queue Name and the Destination Queue Folder.

It's your responsibility to set up the business logic on this page to assign the correct values to the two outputs, tailored to your specific use case.

The Communications Mining StreamResult type has a number of functions to make this easy to do. The following operations are the most common. See Automating with UiPath Communications Mining - Helper functions for a full list.

• in_Communication.Prediction.ContainsLabelExtraction("Address Change") - use this syntax to see if an extraction has been made for the given label.
• in_Communication.Prediction.GetLabelExtraction("Address Change") - use this syntax to retrieve a list of label extractions that have been made for the given label. The results will be in theLabelExtraction type, which also includes a set of helper functions that you can use.
• in_Communication.Prediction.ContainsGeneralField("policy-number") - use this syntax to check if a given general field has been predicted for the current communication.
• in_Communication.Prediction.GetGeneralFields("policy-number").FieldValue = "123" - use this syntax to check if a general field has a specific value.

The LabelExtraction type that is returned when you use the GetLabelExtraction function allows you to inspect the information for the given extraction:

• LabelExtraction.OccuranceConfidence.HasExceededThreshold("stream") - use this syntax to check if the given extraction has exceeded that threshold that you have configured in your stream.
• LabelExtraction.FieldExists("policy-number") - use this syntax to check if a field has been predicted for the given extraction
• LabelExtraction.GetFieldValue("policy-number") - use this syntax to get the value of a field that has been predicted for the given extraction.

Use these helper functions along with your own business logic to decide which communications should be added to which queues within Orchestrator. Based on this decision, set the two outputs: Destination Queue Name and Destination Queue Folder.