One of the key challenges in Automation is providing individuals with a secure environment where they can freely experiment, make mistakes, and unleash their creativity without the fear of negative consequences.
CORTEX, with its innovative sandboxing feature, addresses this challenge by offering developers a private and secure space to explore and develop Automation solutions.
In our video above, we delve deeper into the transformative power of the CORTEX sandbox. Watch Stephen Connor discuss how this secure and private environment allows developers to experiment, test, and refine their Automation solutions without the fear of negative repercussions.
You can also read the full transcript below.
One of the challenges with Automation is letting people experiment play in a secure environment where they know they can do no harm, where they know that nobody else can see the idiotic types of mistakes that they might be making. You know, with CORTEX every developer has a sandbox environment, where they can make changes, they can create Automation, to their heart’s content without that being visible to anybody else. They can save it at any point in time, they can recover at any point in time. But until they commit those changes to the master flow repository, those changes are private to them. And I think that, that gives them a sense of freedom to be able to experiment and make mistakes and improve before they, you know, expose their creativity to the rest of the organisation if you like.
The sandbox also provides them with a runtime environment where they can they can run their Automation flows, totally independent of a production environment. So they know they’re not going to affect production operations. But it can be integrated with live data, if that’s available. And they can validate that the Automation that they’ve defined is working as they expect it to work. We have a fully featured a debugger for them to use. So they can inspect at any point in time, that process of the Automation, the variables that are there, the data that they’re storing, all those sorts of things. And that means that they can confirm that the Automation is working to their requirements before they commit that for other people to be able to use.