In O11, Site Properties stopped runaway timers instantly. In ODC, Settings are cached per transaction. This means toggling your killswitch while a timer is running does absolutely nothing. It’s basically the software equivalent of the “Close Door” button in an elevator—mostly there for emotional support. 😅
Data migration. Just saying the words makes some of us break out in a cold sweat! 😅
We’ve all been there: staring at a screen for hours, watching that progress bar crawl. So, when we kicked off our latest OutSystems ODC project, we knew we were in for the classic challenge—migrating data from an existing application that was about to be officially retired.
So, how did we tackle it?
We combined Data Fabric (in a way you might not expect) with Parallel Workflows to orchestrate the whole move. The best part? Running tasks in parallel is so much faster than waiting for one step to finish before starting the next!
If you’re curious about how we used workflows to speed up the process and (most importantly) validate the results, check out the full blog!
On this rainy Friday I got behind my laptop to build a REST API in ODC.
Building a REST API is quite straightforward. But how do you arrange authentication? The simplest method, which you also know from O11, is basic authentication. You then arrange the login in the OnAuthentication callback of the REST API using an OutSystems server action. You also have that choice in ODC, but there is a catch.