Gwendolyn Goetz

Oh that interesting. I'll leave this open so it can be investigated further.

I enabled the feature flag. It will be enabled after next prod deploy.

Yes, the reason there were three showing up was because there were multiple active drafts for that program. Should be fixed now.

Still no new release yet.

I think that still might result in confusion for the end user seeing localized values in the ui and utc in the export. I think the ui is localizing the...

[Here's the value](https://github.com/civiform/civiform/blob/main/server/conf/application.conf#L600) in the configure I was referring to earlier. That's what is used by the ui.

Thinking about it more if a Civic Entity does span multiple time zones (like a few states do) they still have to pick one when we set up the application.

Thanks for fixing the link contrast @jeanniefu

At least with the current api endpoints I've been given County is not part of the response.

You can take a look at mine both as an example and to let me know if I'm missing anything important. https://github.com/seattle-civiform/civiform-deploy-tf