Subflow Element Limitation: Trigger a Process Under Different App

 
1
0
-1

We have tens of processes and apps to implement for our company. Those apps need to intercommunicate with ease. We currently examine carefully the possibility of adopting Joget for the company.

So far, we are happy with the system. However, we've found a major limitation: the subflow node can only start a process under the same app, as stated in the documentation.

We have a critical need for subflow concept between apps. I think the current implementation of subflow will make our life a lot more complicated.

Any suggestions to get over this issue without a hitch?

 

    CommentAdd your comment...

    1 answer

    1.  
      3
      2
      1

      Hi,

      Have you considered triggering a process from another app via JSON API or beanshell tool as part of the process flow?

      1. Mustapha Hadid

        Yes, I thought of BeanShell tool, but I miss the JSON API one. Thanks, Eric.

      2. Mustapha Hadid

        If I may ask, is it possible to develop a modified version of the subflow element and add that element into Joget process builder?

      3. Walter

        It is based on this wflow-wfengine module here which can be replaced with another workflow engine if you really want to but I think there's simply too much effort needed to justify this. I would recommend the use of JSON API or WorkflowManager class as mentioned by Eric above.

      4. Walter

        Forgot to add link - https://github.com/jogetworkflow/jw-community/tree/6.0-SNAPSHOT/wflow-wfengine

      5. Mustapha Hadid

        Thanks Walter!

      CommentAdd your comment...