Ran into a late night deployment issue whereby I was trying to deploy an updated process map to an existing environment that had new StringTable entries to go with it. I was under the impression that just deploying the map would automatically create everything for me...but it didn't. Within the K2 Workspace/Management area you can't manually add new entries but you can manually add new Environment Library items. Turns out, in order to deploy new StringTable entries to an existing map, you need to perform the following:
Manually add the entries to the Environment Library in K2...
So I was debugging some code I had written to perform a move/copy of a document within SharePoint and noticed none of the columns that were setup in SharePoint as DateTime were getting populated. Long story short, it turned out that our Upload Web Service is expecting metadata of a DateTime type to be in the UTC format (yyyy'-'MM'-'ddTHH':'mm':'ss'Z') which is a cross between the "s" and "u" built-in .Net DateTime.ToString() formatters. So I used:
[DateTimeObject].ToString("s") + "Z"