We have developed screens in ThingWorx in server side, when we connect the VPN and open the runtime link in our local machine. We see the mismatch of timezone. We saw that this issue prevails in Thingworx. We also came across a jira ticket. Can you please send us the solution link to that jira ticket.
What do you expect? the article you posted it's clear:
Yes this is a big limitation on ThingWorx and I've already pointed it out 5 years ago, but for what states on this article you posted doesn't seems that they want to solve it. It's totally doable, actually we already solved customizing all TW standard Widgets with a bindable property named "TimeZone" and just touching some bits here and there, but they aren't for the labour...
Just my two cents,
Try to get the time into sting value and bind it on runtime on Mashup if you are showing it on Grid or Label you won't have any issue. If you are binding it to calendar the browser itself will convert it according to local time zone.
If you feel your question has been answered, please mark the appropriate reply as the Accepted Solution for the benefit of others on the community.