Mike S1
Tera Contributor

Onto the testing portion. Now that we have the setup done, here's how the flow runs stacked up. This was done by just triggering the main flow to generate a new date/time then compare that Flow Variable one by one against the values returned by the action. The first testing pass through was a disaster. Only Date 1 and 6 successfully completed a comparison, and the comparison on Date 6 didn't evaluate properly:

 

Date 1 - Type: Date

MikeS1_0-1758904976770.png

 

Date 6 - Type: Integer Date

MikeS1_1-1758904976772.png

 

The compares for Dates 2-5 came back with comparison issues either for parsing the value that was returned or a mismatch in the types that were being compared.

 

Date 2 - Type: Basic Date/Time

MikeS1_2-1758904976772.png

 

Date 3 - Type: Date/Time

MikeS1_3-1758904976772.png

 

Date 4  - Type: Other Date

MikeS1_4-1758904976772.png

 

Date 5 - Type: Due Date

MikeS1_5-1758904976772.png

 

However, the follow-up test was the fix for all of these problems. It was adding the toString() function to each output variable in the Action:

MikeS1_8-1758905174129.png

 

Doing that produced successful results across the board.

 

MikeS1_6-1758904976772.png

 

MikeS1_7-1758904976772.png

 

So the results of this test were that casting the date values out of the Action as strings allowed all the tests to process successfully and seemed to override whatever type the output variable was set to. It even fixed the test for date 6 which flipped the result from false to true.