Expected attribute loopCounter for StandardLoopCharacteristics about bpmn-elements HOT 7 CLOSED

That has been named index (0-based) in the implementation. Since the aim is to be BPMN2 compliant, I will add it in a future release. Thank you for making me aware.

from bpmn-elements.

Hello! I thought it already was BPMN 2.0 compliant, do you have a roadmap or a list of what's missing?

from bpmn-elements.

IMHO the project has BPMN2.0 core support. But 100% BPMN2.0 is hard to reach, especially since I'm doing this on my limited free time. Feel free to contribute if you are missing something.

from bpmn-elements.

I will gladly contribute, thank you. In fact, I was thinking to fork your project, but I have probably one question before starting. I have seen that also making a valid expression like
${content.index} < 10

does not work, because the expression is correctly resolved (0 < 10) but not evaluated. Since I am still not deeply into the mechanisms of bpmn-engine I prefer to ask. Would it be better to add a "evaluateExpression" that calculate the final result, using it only for loopCharacteristics, or can I edit the "resolveExpression" function to implement this behaviour?
Or am I missing something?

from bpmn-elements.

The builtin expression parser is basic RegEx and rather stupid. It's mainly there for reference.

You can configure your own expression handler in enviroment.expressions or use the excellent community expression handler by aircall (#23)

from bpmn-elements.

Can I close this issue or do we require the property to exist?

from bpmn-elements.

Hi! Yes, I'll close the issue myself. Thank you for your help!

from bpmn-elements.