State Field When Creating Catalog Tasks from Workflows/Flows

[jmiskey]

We have experienced some strange behavior as we start using Flow Designer more and more and Workflow Editor less and less (note that we just converted from Tokyo to Vancouver, but this appears to be happening in both versions).

When we create new Catalog Tasks in Workflow Editor, it correctly creates them with a State of "Open", even though we do not explicitly set this value; it just defaults to that value.  However, when we try to create a Catalog Task using Flow Designer, it seems to create the new Catalog Task with a State of "Pending", and we aren't sure why it does this differently.

We know we can get around this by explicitly setting the State field to "Open" in the Catalog Task creation Action, but we are curious as to why it uses "Pending" as the default value. 

- Is there some setting somewhere that controls this? 

- Why does it do it differently than Workflow Editor?

If there is some default setting which we can control, we would prefer to update this to ensure the value gets set properly.

Thanks

[jmiskey · Accepted solution]

OK, I think I found the issue!  It looks like there was a Dictionary Override on the State field for Catalog Task set to "-5" ("Pending").  I changed it to "1", and everything worked as expected.  

The odd thing about that is it looks like that was set in place in 2015, and it only seems to be affecting Catalog Tasks created in Flow Designer and not Catalog Tasks created in Workflow Editor.