• Type: Feature Request
• Resolution: None
• Priority: L3 - Default
• Fix Version/s: None
• Affects Version/s: None
• Component/s: bpmn model api, camunda modeler, engine
• Labels:

  None

This is the controller panel for Smart Panels app

[CAM-13705] Define the retry time cycle for all tasks of BPMN process

Heiko Nolte created issue - 07/Jul/21 8:53 AM

Collapse comment: Heiko Nolte added a comment - 07/Jul/21 8:58 AM

Heiko Nolte added a comment - 07/Jul/21 8:58 AM

We would like to define the Retry Time Cycle for all tasks of a certain BPMN process. Currently we have only discovered to set the Retry Time Cycle per task or globally for all BPMN processes of the Camunda engine via a property. 

Expand comment: Heiko Nolte added a comment - 07/Jul/21 8:58 AM

Heiko Nolte added a comment - 07/Jul/21 8:58 AM We would like to define the Retry Time Cycle for all tasks of a certain BPMN process. Currently we have only discovered to set the Retry Time Cycle per task or globally for all BPMN processes of the Camunda engine via a property. 

Heiko Nolte made changes - 07/Jul/21 8:58 AM

Component/s		New: bpmn model api [ 12250 ]
Component/s		New: camunda modeler [ 13350 ]
Component/s		New: engine [ 11656 ]
Description	Original: h4. Environment (Required on creation): h4. Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket): h4. Steps to reproduce (Required on creation): h4. Observed Behavior (Required on creation): h4. Expected behavior (Required on creation): h4. Root Cause (Required on prioritization): h4. Solution Ideas (Optional): h4. Hints (Optional):	New: h4. Environment (Required on creation): We would like to define the Retry Time Cycle for all tasks of a certain BPMN process. Currently we have only discovered to set the Retry Time Cycle per task or globally for all BPMN processes of the Camunda engine via a property. h4.
Summary	Original: We need a way to define the retry time cycle for tasks	New: Define the retry time cycle for all tasks of BPMN process

Heiko Nolte made changes - 07/Jul/21 8:58 AM

Mentioned Roles

Heiko Nolte made changes - 07/Jul/21 8:58 AM

Mentioned Groups

Heiko Nolte made changes - 07/Jul/21 8:58 AM

Mentioned Roles

Heiko Nolte made changes - 07/Jul/21 8:58 AM

Mentioned Groups

Collapse comment: Agnes Kelemen added a comment - 07/Jul/21 3:14 PM

Agnes Kelemen added a comment - 07/Jul/21 3:14 PM

Hallo heiko.nolte@hdi.de,

Danke für deine Anfrage.

Ich glaube dieses Ticket sollte unter unserem "SUPPORT" Projekt laufen, damit es laut euren vertraglichen SLAs bearbeitet wird.

Da du derzeit nur einen lesenden Zugriff zu Jira hast, müsste ich jemanden mit Full access als Reporter hinterlegen. 

tino.reichardt@hdi.de und michael.pechtold@hdi.de kann ich einen von euch beiden als Reporter für dieses Ticket nehmen, damit ihr dann die Kommunikation übernehmen könnt?

Besten Dank im Voraus!

Schöne Grüße,

Agnes

 

Agnes Kelemen

Customer Success Manager

Expand comment: Agnes Kelemen added a comment - 07/Jul/21 3:14 PM

Agnes Kelemen added a comment - 07/Jul/21 3:14 PM Hallo heiko.nolte@hdi.de , Danke für deine Anfrage. Ich glaube dieses Ticket sollte unter unserem "SUPPORT" Projekt laufen, damit es laut euren vertraglichen SLAs bearbeitet wird. Da du derzeit nur einen lesenden Zugriff zu Jira hast, müsste ich jemanden mit Full access als Reporter hinterlegen.  tino.reichardt@hdi.de  und michael.pechtold@hdi.de  kann ich einen von euch beiden als Reporter für dieses Ticket nehmen, damit ihr dann die Kommunikation übernehmen könnt? Besten Dank im Voraus! Schöne Grüße, Agnes   Agnes Kelemen Customer Success Manager

Agnes Kelemen made changes - 07/Jul/21 3:14 PM

Mentioned Roles

Agnes Kelemen made changes - 07/Jul/21 3:14 PM

Mentioned Groups

Load more newer events