No matter if you change a form/list, create a new entity or implement a time cockpit action, everything is stored in your isolated database. The formal description and implementation of all your customizations resides in the time cockpit database. Copying the database is sufficient, because time cockpit facilitates a datamodel/metadata-driven approach. When we create a sandbox for a customer, we create a snapshot of the customer's time cockpit database. It lets you run your untested customizations in a separate environment. It is often used to execute untested code, or untrusted programs from unverified third parties, suppliers, untrusted users and untrusted websites."īasically, this is also what a time cockpit sandbox is. "In computer security, a sandbox is a security mechanism for separating running programs. Wikipedia defines a sandbox as the following: It safes you from negatively influencing your production time cockpit during the development of your customizations. In a sandbox you can try out your customizations before deploying them to the actual production system. Your production system does not get cluttered with unnecessary customizations.Ī sandbox is a snapshot of your production time cockpit environment. If you are happy with the solution in the sandbox, you can migrate only the things that solves your problem and that have proved useful. In a sandbox you can do what a sandbox is intended for: Build things, crush them, and start over again. Sometimes you want to try something to evaluate different approaches. At the beginning, you might not know how your customizations will look like in the end.
Chances are that you do not get it right the first time and thus hinder your employees to track their time.
0 kommentar(er)
