Changing workflow engine properties in alfresco-global.properties

cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Senior Member

Changing workflow engine properties in alfresco-global.properties

Hello Everyone,

Will there be any changes in the functionality of the workflow from user's point of view if I change its engine properties in alfresco-global.properties? Right now I have system.workflow.engine.activiti.enabled=true in my global.properties file.

e.g. 

system.workflow.engine.activiti.enabled=false‍

and

system.workflow.engine.jbpm.enabled=true‍

I would like to know the difference between these two, from the developers or performance point of view.

Thanks in Advance.

Kintu

Regards,
Kintu | ContCentric
2 Replies
Highlighted
Advanced II

Re: Changing workflow engine properties in alfresco-global.properties

Hello.

Well, it all depends on the Alfresco version you are using, as JBPM got removed from version 201605 (aka 5.1.g), as you can see here https://community.alfresco.com/docs/DOC-6297-alfresco-community-edition-201605-ga-release-notes#jive... 

Highlighted
Senior Member

Re: Changing workflow engine properties in alfresco-global.properties

Hi Douglas C. R. Paes,

I am using Alfresco Community 5.0.

I have enabled jbpm engine by following properties in alfreaco-global.properties file.

system.workflow.engine.jbpm.definitions.visible=true
system.workflow.engine.jbpm.enabled=true

but I was getting 'activiti$xxxx' in task id.

Then I disabled activiti engine by following properties

system.workflow.engine.activiti.definitions.visible=false
system.workflow.engine.activiti.enabled=false

And Its giving 'jbpm$xxxx' in task id.

It means just enabling jbpm engine is not enough, in order to make it work; you must disable activiti engine also.

Thanks

Kintu

Regards,
Kintu | ContCentric