nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

How task properties are pushed back to process instance

tiennd

Hi,
According to a wiki article, after each task is ended, it's properties are pushed back to process properties. Where this action is performed in alfresco code?
Another question is: task properties and process properties are stored only in JBPM storage or also in alfresco repository?

Thank you,

Find more posts tagged with

Comments

davidc

According to a wiki article, after each task is ended, it's properties are pushed back to process properties. Where this action is performed in alfresco code?

This is behaviour of JBPM - I think it's in TaskController.java. If you wish to override this behaviour, you can use the <taskcontroller> element in your process definition, or provide your own task controller java plug-in.

Another question is: task properties and process properties are stored only in JBPM storage or also in alfresco repository?

They are stored in the JBPM storage. However, Alfresco repository items are stored as references in JBPM e.g. the workflow package is a container in the Alfresco Repository, but held as a reference to it in JBPM.