Periodical deadline / best practice?

 
1
0
-1

Hey there,

I need to implement a "periodical" deadline on an activity "incubation" of my process. It is used to increment a field in a table (time passed in this activity) and as a reminder for the user to check something and if OK then complete the activity.

To do this I implemented a synchronous Deadline "Update" that leads to an "Test" tool (Beanshell tool) then the tool links back to my same first activity "Incubation".

Everything works fine. My counter is incremented every x minutes. But, I have an issue with the Process Status Formatter in my Datalists. Indeed, as soon as my record has triggered the "update" deadline for the first time, and gone through the "test" tool the Process Status Formatter gets somewhat disturbed. 

   

                    Before                                                   After

I also tried with an "asynchronous" deadline but then the Deadline is only triggered once.

Any insight on the topic?

Thank you very much,

Baptiste

    CommentAdd your comment...

    4 answers

    1.  
      1
      0
      -1

      This issue seems to be fixed on latest Joget v6 update.

        CommentAdd your comment...
      1.  
        1
        0
        -1

        As I am still looking into this issue, I have new information that may help to resolve it.

        I do not think the issue is related to the "deadline" aspect of my problem. Indeed, I have another "loop" in my process at the activity "Reception", if my workflow Variable "receptionConformity" is not how it should be then I stay in reception:

        And when my record follows the [otherwise] loop, the Process Status Formatter is disturbed as in the OP. 

        Update: Also, even if I delete the [otherwise] loop which seems useless then the issue persists. 

        Update2: When loading the datalist which displays the disturbed Process Status Formatter, Google Chrome's console reads : 

        processStatusList.js:380 Uncaught RangeError: Maximum call stack size exceeded
        at findLoopPaths (processStatusList.js:380)
        at findLoopPaths (processStatusList.js:386)
        at findLoopPaths (processStatusList.js:386)
        at findLoopPaths (processStatusList.js:386)
        at findLoopPaths (processStatusList.js:386)
        at findLoopPaths (processStatusList.js:386)
        at findLoopPaths (processStatusList.js:386)
        at findLoopPaths (processStatusList.js:386)
        at findLoopPaths (processStatusList.js:386)
        at findLoopPaths (processStatusList.js:386)

        Please also find attached a version of my app in development which is a data entry tool for a microbiology lab.

        APP_1-1-20190122160641.jwa

         

         

          CommentAdd your comment...
        1.  
          1
          0
          -1

          Hi Justin,

          Thank you for your effectiveness.

          All the best

          Baptiste

            CommentAdd your comment...
          1.  
            1
            0
            -1

            Hi there,

            The issue above has been confirmed and has been reported to the dev team. 

            Have a good day!

              CommentAdd your comment...