Hi there,
We recently upgraded from 2013 through 2015 to 2016/365.
From going through upgrade issues, I have come across a problem with Actions that we utilized in 2013.
It is a global action, that takes an Entity input argument, as well as some other arguments. It then uses some of the fields from the input Entity argument to pass into various custom workflow activities as part of the Action.
It doesn't seem possible to access the fields from the input Entity anymore, Is this intentional? It doesn't matter whether the Action is global or not - though if it is not a global action, I can access the target Entity, but this is not what we need. It seems like the Entity Process Argument is now completely useless if it cannot be read...?