Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
A complete cloud platform for an app or your entire digital business
Detect and predict anomalies by automating machine learning to achieve higher asset uptime and maximized yield
Automate decision processes with a no-code business rules engine
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Personalize and optimize the customer experience across digital touchpoints
Build, protect and deploy apps across any platform and mobile device
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
After a trigger call to a REST integration link, I am receiving new record information that contains DateTime info in ISO format (MM:DD:YYYYTHH:MM:SSZ).
When I issue rbv_api.createObject call with this value in the record array, an error is thrown indicating only that the array cannot be read (this is very misleading).
As a work-around, I have created a conversion function in the trigger that calls new Date(), gets the TimeZone offset from UTC via getTimezoneOffiset(), and returns the adjusted date to be inserted into the record array.
What is the recommended approach to converting this date into a usable value with the API?
Specifically, how do convert the date to a UTC value to avoid the potential time zone issue without having to include a copy of this function in virtually every integration link response trigger?
Development team is investigating this issue, we will update you shortly.