Why Joget Increment Process ID with Every Deploy?

 
3
2
1

We have an issue with process/start/(*:processDefId) web API endpoint. The endpoint requires processDefId. processDefId includes process version -- for example, expense-claim#1#process-name. Process version is incremented with every deploy.

We have a couple of systems that make use of that endpoint, and I need a proper way to update process design without incrementing its version.

Any thoughts?

    CommentAdd your comment...

    3 answers

    1.  
      4
      3
      2

      Hi Eric,

      You can actually use the keyword "latest" to replace the numeric value for process version. This will automatically obtain the latest published process version.

      curl --request POST --url 'http://localhost:8080/jw/web/json/workflow/process/start/expenseclaim:latest:process1?j_username=cat&j_password=password'

      Cheers

      Hugo

      1. Eric

        Hi Hugo, That’s amazing - I should have just tried it I guess. Is it part of the knowledge base? Might be good to add in the docs if it’s not already there. Cheers, Eric

      2. Hugo

        Hi Eric, Yes, I have just updated https://dev.joget.org/community/display/KBv6/JSON+API#JSONAPI-web/json/workflow/process/start/(*:processDefId) Thanks.

      CommentAdd your comment...
    2.  
      2
      1
      0

      Hi Mustapha,

      Please see Version Control#UpdatingProcessVersion. Process version will change on every process design update.

      Cheers

      Hugo

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

        I came across the same issue but wasn’t able to find a solution other than a workaround to determine the defid. Would be great if the url had „latest“ instead of a number as an option.

          CommentAdd your comment...