We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.

    • 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

            Loading...

              • 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

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

                          Created:
                          Updated:
                          Resolved:

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

                                Created:
                                Updated:
                                Resolved: