topic Re: Participant expression syntax in Alfresco Archive

Participant expression syntax

lsmall — Wed, 06 Aug 2014 13:05:47 GMT

Activiti supports both the standard participant XML (humanPerformer and potentialOwner) as well as activiti extension attributes (assignee, candidate users, candidate groups, etc.). We prefer to use the more standard syntax with the addition of the custom resource feature. This way, the same formal

Re: Participant expression syntax

frederikherema1 — Wed, 06 Aug 2014 14:45:28 GMT

Lori,

I'm interested in the way you're going to implement this. Currenlty, it's handled by the PotentialOwnerParser, a child parser of the UserTaskXMLParser. In case you extend the UserTaskXMLConverter and add your custom parser that handles "potentialOwner" element, you can support any format you want. Not sure if shipping a JSON-based parser by default would be a good improvement, as the format you're describing is pretty usecase-specific… Unless I'm missing something, off course

Re: Participant expression syntax

lsmall — Wed, 06 Aug 2014 15:11:59 GMT

I have already extended the UserTaskXMLConverter to only use the extended participant syntax (instead of the Activiti attribute extensions). We will likely extend it further to parse JSON, but just wanted to know if you saw any benefit to adding it to the code base.