Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-8089

Job Retry Profile Example

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.8.0, 7.8.0-alpha4
    • None
    • engine
    • None

      There should be an example that shows how a "Job Retry Profile" can be applied to certain job declarations.

      There could be different profiles for different external systems:

      • External System 1 ERP System
      • External System 2 CRM System
      • ...

      A profile defines a default retry time cycle, which should be applied when "talking" with that external system. In case of "External System 1" it could be "R5/PT10M" and in case of "External System 2" it could be "R10/PT5M" etc.

      To avoid to set the retry time cycle and to add a asynchronous continuation (asyncBefore or asyncAfter) flag for each task where the process "talks" with one of the external task, the user can use a property to set a "profile" inside the bpmn model. The property can than be used inside a process engine plugin to set default retry time cycle behavior depending on the given profile.

        This is the controller panel for Smart Panels app

            [CAM-8089] Job Retry Profile Example

            Roman Smirnov created issue -
            Roman Smirnov made changes -
            Rank New: Ranked higher
            Roman Smirnov made changes -
            Rank New: Ranked lower
            Roman Smirnov made changes -
            Description Original: Add an example of different job retry profiles. New: There should be an example that shows how a "Job Retry Profile" can be applied to certain job declarations.
            Roman Smirnov made changes -
            Description Original: There should be an example that shows how a "Job Retry Profile" can be applied to certain job declarations. New: There should be an example that shows how a "Job Retry Profile" can be applied to certain job declarations.

            There could be different profiles for different external systems:
            - External System 1
            - External System 2
            - ...

            A profile defines a default retry time cycle, which should be applied when "talking" with that external system. In case of "External System 1" it could be "R5/PT10M" and in case of "External System 2" it could be "R10/PT5M" etc.

            To avoid to set the retry time cycle and to add a asynchronous continuation (asyncBefore or asyncAfter) flag for each task where the process "talks" with one of the external task, the user can use a property to set a "profile" inside the bpmn model. The property can than be used inside a process engine plugin to set default retry time cycle behavior depending on the given profile.
            Yana Vasileva made changes -
            Status Original: Open [ 1 ] New: In Progress [ 3 ]
            Daniel Meyer made changes -
            Description Original: There should be an example that shows how a "Job Retry Profile" can be applied to certain job declarations.

            There could be different profiles for different external systems:
            - External System 1
            - External System 2
            - ...

            A profile defines a default retry time cycle, which should be applied when "talking" with that external system. In case of "External System 1" it could be "R5/PT10M" and in case of "External System 2" it could be "R10/PT5M" etc.

            To avoid to set the retry time cycle and to add a asynchronous continuation (asyncBefore or asyncAfter) flag for each task where the process "talks" with one of the external task, the user can use a property to set a "profile" inside the bpmn model. The property can than be used inside a process engine plugin to set default retry time cycle behavior depending on the given profile.             		New: There should be an example that shows how a "Job Retry Profile" can be applied to certain job declarations.

            There could be different profiles for different external systems:
            - -External System 1- ERP System
            - -External System 2- CRM System
            - ...

            A profile defines a default retry time cycle, which should be applied when "talking" with that external system. In case of "External System 1" it could be "R5/PT10M" and in case of "External System 2" it could be "R10/PT5M" etc.

            To avoid to set the retry time cycle and to add a asynchronous continuation (asyncBefore or asyncAfter) flag for each task where the process "talks" with one of the external task, the user can use a property to set a "profile" inside the bpmn model. The property can than be used inside a process engine plugin to set default retry time cycle behavior depending on the given profile.
            Yana Vasileva made changes -
            Assignee Original: Yana Vasileva [ yana.vasileva ] New: Anna [ anna.pazola ]
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
            Remaining Estimate New: 0 minutes [ 0 ]
            Original Estimate New: 0 minutes [ 0 ]
            Anna made changes -
            Assignee Original: Anna [ anna.pazola ] New: Yana Vasileva [ yana.vasileva ]
            Resolution Original: Fixed [ 1 ]
            Status Original: Resolved [ 5 ] New: Reopened [ 4 ]
            Yana Vasileva made changes -
            Status Original: Reopened [ 4 ] New: In Progress [ 3 ]

              yana.vasileva Yana Vasileva
              roman.smirnov Roman Smirnov
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: