Since the first release of Kapow Katalyst it has been possible to store data in databases. Although the system has proven its worth, a number of problems have become visible over time.
Problems with the old storage system
Storing data in a database required a special DatabaseOutputObject.
The DatabaseOutputObject had a refindKey field; few understood the importance of the refindKey at the time the object was constructed, and once data had been stored, changing the refindKey was a cumbersome process.
You had to register each robot with the RoboManager database, so the robot would have a robotId.
At run-time you had to provide 3 environments, a DatabaseStorageEnvironment, a DatabaseRobotInfoEnvironment and a DatabaseMessageEnvironment.
The Refind Object action was confusing, and error prone to use.
These issues introduced a number of pitfalls, which even experienced users fell into. Most common is probably the duplicate robotId, where an already registered robot was used as a template, but the copy was never re-registered with RoboManager, and suddenly two robots had the same RobotId.