Breaking changes
Background
When changing from Workflow Manager to ZerFlow most things will work just as you expect, and in most cases a lot better, so the upgrade will be largely seamless. There are a few excpetions though where ZerFlow engine behaves slightly different from Workflow Manager and we will list all things you need to consider when upgrading and what you need to do in order for your services to work just like before.
| Old behaviour | New behaviour | Required action |
|---|---|---|
| DateTime variables are no different than String variables | DateTime variables in ZerFlow are handled according to ISO 8601 (YYYY-MM-DDTHH:MM:SSZ) | If you're using string methods when converting/transforming datetime values these could yield unexpected behaviour. You might have to replace them with DateTime manipulation methods |
| - | New network ports utilized by ZerFlow | Port for Zervicepoint Zebra API and ZerFlow Workflow API needs to be excluded from firewalls and the like |
| Activities inside Parallel branches are executed non-deterministic | ZerFlow tries to execute 1 activity from each branch before moving to the next activity in the first branch and repeats this pattern. If however there's an activity with child activities (sequence, conditional sequence, while, etc.) the order becomes a bit more unpredictable | Keep being cautious when using parallels if the order of activities matter and refrain from sharing variables between branches in the same parallel |
| Zervicepoint utilizes a V8 engine to execute JavaScript | Code activity has been updated with a new V8 engine. Also moved all interpretation and execution of JavaScript to ZerFlow (utilizing the updated V8 engine) | Make sure to double check if services using code activities still behaves as expected. The upgrade of the V8 engine could lead to small but significant changes to how JavaScript used to be interpreted before |