I posted the other day about some date comparison headaches we ran into in Flow on a current project where things either weren't matching up or were erroring out in flow logic. I decided to dig a little more at some of these comparisons with various date Output variable types in the system to see how the flow would react. The documentation didn't give me a lot to go off of for what the usage was for some of the less prominent types.
So, here's the starting point. I set my Flow Action to return a bunch of dates the same way, and then point each of them at an output variable of a different type. I'm trying to just generate a new GlideDate push it into each output variable, then I can do comparisons in the Flow on each type.
Running this just as a test from the Action put the same value into each of the different output variables.
Next for good measure, I stuck a toString() on the end of all of the variable assignment calls and ran the Action Test again. The result was the same, with all the outputs set the same way across the board.
So now that we see how the action handles each out type, we can feed them into our Flow as inputs
