Abonnieren

UiPath Orchestrator

Die UiPath-Orchestrator-Anleitung

Working with long-running workflows

Processes that require logical fragmentation or human intervention (validations, approvals, exception handling) such as invoice processing and performance reviews, are handled with a set of instruments in the UiPath suite: a dedicated project template in Studio called Orchestration Process, actions and resource allocation capabilities in Orchestrator.

Sie konfigurieren Ihren Workflow mit einem Paar von Aktivitäten. Der Workflow kann mit den Parametern für die spezifische Ausführung konfiguriert werden, sodass ein angehaltener Auftrag nur fortgesetzt werden kann, wenn bestimmte Anforderungen erfüllt sind. Erst wenn die Anforderungen erfüllt sind, werden Ressourcen für die Wiederaufnahme des Auftrags bereitgestellt, damit kein unnötiger Verbrauch auftritt.

In Orchestrator this is marked by having the job suspended, awaiting for requirements to be met, and then having the job resumed and executed as usual. Depending on which pair you use, completion requirements change, and the Orchestrator response adjusts accordingly.

Jobs

ActivitesUse Case
Start Job and Get Reference
Wait for Job and Resume
Introduce a job condition, such as uploading queue items.

After the main job has been suspended, the auxiliary job gets executed. After this process is complete, the main job is resumed. Depending on how you configured your workflow, the resumed job can make use of the data obtained from the auxiliary process execution.




If your workflow uses the Start Job and Get Reference activity to invoke another workflow, your Robot role should be updated with the following permissions:
View on Processes
View, Edit, Create on Jobs
View on Environments.

Warteschlangen

ActivitiesUse Case
Add Queue Item and Get Reference
Wait for Queue Item and Resume
Introduce a queue condition, such as having queue items processed.

After the main job has been suspended, the queue items need to be processed through the auxiliary job. After this process is complete, the main job is resumed. Depending on how you configured your workflow, the resumed job can make use of the output data obtained from the processed queue item.

Aktionen

Formularaktionen

ActivitiesUse Case
Create Form Task
Wait for Form Task and Resume
Introduce user intervention conditions, found in Orchestrator as actions.

After the job has been suspended, an action is generated in Orchestrator (as configured in Studio).

Only after action completion, is the job resumed.

Form actions need to be completed by the assigned user. User assignment can be handled directly in Orchestrator, or through the Assign Tasks activity.

Externe Aktionen

ActivitiesUse Case
Create External Task
Wait for External Task and Resume
Introduce user intervention conditions, found in Orchestrator as actions.

After the job has been suspended, an action is generated in Orchestrator (as configured in Studio).

Only after task completion, is the job resumed.

External actions can be completed by any user with Edit permissions on Actions, and access to the associated folder.

Dokumentvalidierungsaktionen

ActivitiesUse Case
Create Document Validation Action
Wait for Document Validation Action and Resume
Introduce user intervention conditions, found in Orchestrator as actions.

After the job has been suspended, an action is generated in Orchestrator (as configured in Studio).

Only after task completion, is the job resumed.

Document Validation actions need to be completed by the assigned user. User assignment can be handled directly in Orchestrator, or through the Assign Tasks activity.





In order for the Robot to upload, download and delete data from a storage bucket, it needs to be granted the appropriate permissions. This can be done by updating the Robot role with the following:
To upload document data:
View, Create on Storage Files
View on Storage Buckets

To delete document data after downloading:
View, Delete on Storage Files
View on Storage Buckets

Dauer (Duration)

ActivityUse Case
Resume After DelayIntroduce a time interval as a delay, during which the workflow is suspended.

After the delay has passed, the job is resumed.

Job fragments are not restricted to being executed by the same Robot. They can be executed by any Robot that is available when the job is resumed and ready for execution. This also depends on the execution target configured when defining the job. Details here.

Ich habe meinen Auftrag definiert, um von bestimmten Robotern ausgeführt zu werden, z. B. X, Y und Z. Wenn ich den Auftrag starte, ist nur Z verfügbar, daher wird mein Auftrag von Z ausgeführt, bis er zur Benutzervalidierung angehalten wird. Nachdem er validiert wurde und der Auftrag fortgesetzt wird, ist nur X verfügbar, daher wird der Auftrag von X ausgeführt.

  • Für die Zwecke der Überwachung wird ein solcher Auftrag als einer gezählt, unabhängig davon, ob er fragmentiert oder von verschiedenen Robotern ausgeführt wird.
  • Angehaltene Aufträge können keinen Robotern zugewiesen werden. Dies ist nur mit wiederaufgenommenen möglich.

To check the triggers required for the resumption of a suspended job, check the Triggers tab on the Job Details window.

Aktualisiert vor 6 Monaten


Working with long-running workflows


Auf API-Referenzseiten sind Änderungsvorschläge beschränkt

Sie können nur Änderungen an dem Textkörperinhalt von Markdown, aber nicht an der API-Spezifikation vorschlagen.