SCS 8 first teaser

I’m on the team working on SCS 8, and although we are not even half way done, I’m really excited about our new features. At this point I will only talk about features that we’ve already implemented, so this is in no way the final list of features.

Let’s first take it one step back. SCS 7.0 and 7.1 took SCS in a different direction. We added Host Based Configuration, so we can definitely say that configuration has never been simpler. We also removed the use of a database, and so we got ourselves one lean-and-mean configuration machine.

In SCS 8 we’re going to enjoy the best of all worlds, with an option to work with a database, but users will also have an option to work without one (as in SCS 7), so for any of you who have learned to enjoy SCS 7 – don’t worry, we’re not going to ruin anything.

So what are we adding? Well, a lot of our time so far was in database-related infrastructure. The database gives us the power to do many things down the road, and one thing we've already done is maintain a list of AMT systems configured by the SCS service (RCS) and store their password.

But even though the database takes up most of our time, we also have new features that are relevant also for users who choose not to use the database component.
We expanded the options (which we began in SCS 7) to have post configuration scripts in various flows, and these scripts can be placed either on the Configurator or RCS side. One usage we envision for these scripts is to allow ITs and ISVs to have any operation done by SCS to then be updated in whatever other application they use.
Another cool feature is what my team refers to as “auto-maintenance”. Using a new command in our local agent (the Configurator), users can do maintenance without having to worry about what it is that needs maintenance – the Configurator will simply do all the required maintenance operations (and not do anything that is not needed).

So… still half a year away from our final release, and already I think we’ve got a winner.

Para obtener información más completa sobre las optimizaciones del compilador, consulte nuestro Aviso de optimización.