Why Joget Increment Process ID with Every Deploy?

Confluence User - 03 Apr, 2018

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?

process;process-design;process-id;deploy

5


04 Apr, 2018
confluenceUser
confluenceUser

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.

04 Apr, 2018
confluenceUser
1
confluenceUser

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

04 Apr, 2018
confluenceUser
confluenceUser

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

04 Apr, 2018
confluenceUser
confluenceUser

Hi Mustapha,

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

Cheers

Hugo

04 Apr, 2018
confluenceUser
confluenceUser
RELATED QUESTIONS

Your answer


To answer a question you'll need an account.

Print