Branching based on Extended Property Table

Discussion created by bryanboutz on Mar 27, 2014
Latest reply on May 12, 2014 by MBroadbent-esristaff
I have a workflow that needs to branch based on the value of extended property.  My intent was to use the Workflow Manager ???ReturnValue??? custom step type to read the value using a token and a conditional value path to route accordingly.  The problem is that the field is a date and Workflow Manager can only work with integers for conditional paths.  I don't see a way to use a function on the returned value to convert it into an int.  I'd like to avoid having to deploy a custom developed step to each client,  so I'm looking for a work around.

One option is to add a computed column to the Extended Property table that implements the necessary date to int business logic.  Does anyone know if that will work, or will Workflow Manager expose it as an editable field then get grumpy if someone tries to manually edit it?  If so, then I will probably try to do the same thing using insert and update triggers instead.

This seems like it would be a common problem.  Any other suggestions?