- Introduction
- Démarrage
- Modélisation du processus avec BPMN
- Compréhension de la modélisation des processus
- Ouverture du canevas de modélisation
- Modéliser votre processus
- Alignement et connexion des éléments BPMN
- Autopilot pour Maestro (aperçu)
- Référentiel de processus
- Modélisation des processus avec la gestion des incidents
- Concevoir un schéma d'entité de cas persistant
- Définition des clés de cas (système vs. externe)
- Établissement des contrats d'E/S et de réécriture de la tâche
- Règles de sortie et fin de l’étape précoce
- Modélisation des étapes primaires et secondaires
- Déclencher un cas à partir de Data Fabric
- Implémentation des personas et des autorisations au niveau de l'étape
- Définition des SLA et des règles d'escalade automatisées
- Configuration d'une boucle de retraitement (renouvellement)
- Gestion des instances de cas en cours : suspendre, migrer et réessayer
- Dictionnaire des composants de gestion des incidents Maestro
- Modélisation des processus avec Flow
- Implémentation des processus
- Débogage
- Simulation
- Publication et mise à niveau des processus agentiques
- Scénarios de mise en œuvre courants
- Extraire et valider des documents
- Opérations de processus
- Surveillance des processus
- Optimisation des processus
- Informations de référence
Queue task activities in Maestro BPMN processes: required fields for creating, updating, and resolving Orchestrator queue items, organized by activity.
Queue task activities create, update, and resolve Orchestrator queue items from a task in a Maestro BPMN process. Queue activities are accessed from the Action dropdown in a task's Properties panel. Queue activities are available in the following task types — refer to Tasks for the full list:
- Service tasks
- User tasks
- Send tasks
- Receive tasks
- Business rule tasks
- Script tasks
Queue item lifecycle
| État (State) | How it's reached |
|---|---|
| Nouveau | The item is added to the queue. |
| InProgress | A queue trigger starts a process instance for the item and sets it to InProgress. |
| Successful / Failed | The process sets the final state with Set transaction status. |
| Abandonné | Automatic, if an item stays InProgress for 24 hours without reaching a final state. If retry is configured on the queue, Orchestrator clones the item and re-queues it. |
One queue item starts exactly one Maestro BPMN process instance. A single instance consuming multiple items in a loop isn't supported in this release.
Create queue items
Adds a new item to an Orchestrator queue with New status.
| Champ | Requis | Description |
|---|---|---|
| Queue name | Oui (Yes) | The Orchestrator queue to add the item to. |
| Chemin d'accès au dossier | Oui (Yes) | The Orchestrator folder that contains the queue. |
| Priorité (Priority) | Non (No) | The processing priority of the item. |
| Échéance (Deadline) | Non (No) | The date and time by which the item must be processed. |
| Différer la date | Non (No) | The earliest date and time the item becomes available for processing. |
| Custom data | Non (No) | Additional data attached to the item, available to the robot or process that processes it. |
Create and wait for queue items
Adds an item to a queue and waits for the item to reach a final state before continuing the process. Uses the same fields as Create queue items.
Bulk add queue items
Adds multiple items to a queue in a single batch, up to 15,000 items per call.
| Champ | Requis | Description |
|---|---|---|
| Queue name | Oui (Yes) | The Orchestrator queue to add items to. |
| Chemin d'accès au dossier | Oui (Yes) | The Orchestrator folder that contains the queue. |
| Eléments | Oui (Yes) | The list of items to add, up to 15,000 per call. |
| Commit type | Oui (Yes) | AllOrNothing rejects the entire batch if any item fails validation. ProcessAllIndependently adds all valid items and reports failures individually. |
When commit type is ProcessAllIndependently, the activity returns the list of items that failed to be added.
Delete queue items
Removes items with New status from a specified queue.
| Champ | Requis | Description |
|---|---|---|
| Queue name | Oui (Yes) | The Orchestrator queue to remove items from. |
| Chemin d'accès au dossier | Oui (Yes) | The Orchestrator folder that contains the queue. |
| Eléments | Oui (Yes) | The items to remove. Only items with New status can be removed. |
Postpone transaction item
Sets a defer date, and optionally a due date, for an in-progress transaction item, and returns the item to New status.
| Champ | Requis | Description |
|---|---|---|
| Defer date | Oui (Yes) | The earliest date and time the item becomes available for processing again. |
| Date dʹéchéance | Non (No) | The deadline by which the item must be processed. |
Postpone transaction item isn't retried automatically when the underlying call fails with a 4xx error.
Set transaction progress
Updates an InProgress transaction item with a custom status string. The status is visible in Orchestrator.
| Champ | Requis | Description |
|---|---|---|
| Progression (Progress) | Oui (Yes) | A custom text string describing the current processing state of the item. |
Set transaction status
Sets the final state of a transaction item to Successful or Failed.
| Champ | Requis | Description |
|---|---|---|
| État (Status) | Oui (Yes) | Successful or Failed. |
| Error type | Conditionnel | Required when status is Failed. BusinessException or ApplicationException. |
| Raison de l'erreur | Conditionnel | Required when status is Failed. A short description of the error. |
| Détails de l’erreur | Non (No) | Additional error information. |
Maestro automatically retries the task unless the underlying call fails with a 4xx error. On failure, the task returns the error code OrchestratorSetTransactionResultFailed.
For the trigger that starts a process from a queue item, refer to Events. For more information about tasks, refer to Tasks in BPMN modeling.