topic Re: Maintaining state of object in activiti workflow in Alfresco Archive

Maintaining state of object in activiti workflow

vndube — Fri, 01 Mar 2013 05:35:52 GMT

Hi,We have requirement of workflow where it needs to pass through Create/Edit, QC and Approve steps. When a creator creates a product, based on workflow definition it has to go to QC/Reviewers and then accordingly it will be forwarded to approvers. Once an approver approves the product then only the

Re: Maintaining state of object in activiti workflow

frederikherema1 — Fri, 01 Mar 2013 09:16:15 GMT

How are you planning on storing the object in Activiti? Are you planning on using 500 variables, each representing a product-attribute? This would require 500 variables to be fetched, which isn't really a big amount for activiti, you can rest assure. Another approach is to add the product as a Serializable variable. This way, activiti only needs to store and fetch one variable. Every change you make to the variable from within the process, will be stored automatically in activiti, transparently.

Re: Maintaining state of object in activiti workflow

vndube — Fri, 01 Mar 2013 11:21:04 GMT

Planned to store in Serialized form.

We are looking at other aspect like if it (product object) contains more than 500 attributes. How will it be feasible and efficient storing this kind of object in activiti workflow.

Thanks

Re: Maintaining state of object in activiti workflow

frederikherema1 — Mon, 04 Mar 2013 09:56:57 GMT

Serializable object is just stored as a byte array. The serializable is only fetched when needed and cached during the same Activiti contexts, so the overhead is minimal. The size of the serializable depends on the number for attributes, but I'm guessing 500 attributes will mean only o couple of Kb's, so that's perfectly fine performance-wise.

Re: Maintaining state of object in activiti workflow

vndube — Mon, 04 Mar 2013 11:04:19 GMT

Thanks for your response