I'm trying to understand exactly how the dependencyIdField is used. I've read the config docs but it's still un-clear. Is it used as the "lookup" key for both fromEvent and toEvent? Consider the below data structure:
The fromEvent id does not exist as the id on any task, but it does exist in another field alternateId. Can dependencyIdField be used to express a dependency relationship between taskA and taskB by setting it to alternateId?
Yes, that's correct! The example that you shared should work as you described. It's the field that the dependency store will look up in the task model.
I mentioned this to our team to check if we can make the documentation more clear.
I'm afraid, We're not aware of any workaround for it. You'd need to wait for this issue to be fixed!
If we find any workaround for it, we'll let you know.
If you have any other questions, please don't hesitate to reach out.