Version 1.8.2 : Implicit retries countdown

[Noordsestern]

This release contains 1 bugfix and 1 enhancement:

#48 - Exception when setting retry_timeout in Notify Failure

It was not possible to set retry tiemout. This is now fixed

#49 - Implicit Retry Countdown

Prior this release, it was necessary to manage retries counter yourself. Although the algorithm is simple, it was overhead and bulky:

*** Test Case ***
Demo old behaviour
    fetch workload    my topic
    ${process_instance}    get fetch response
    IF    None is not $process_instance['retries']
        ${counted_down_retries}    Evaluate    $process_instance['retries'] - 1
        Notify Failure    retries=${counted_down_retries}
    ELSE
        Notify Failure    retries=1
    END

Now you can always set retries, but only when set for the first time, it is actually interpreted. If the process instance already has retries set, then CamundaLibrary is counting down retries automatically:

*** Test Case ***
Demo new behaviour
    fetch workload    my topic
    Notify Failure    retries=1

    fetch workload    my topic
    # this will now raise an incident, because retries had been set before and are now counted down to 0
    Notify Failure    retries=1

---

This discussion was created from the release Implicit retries countdown.