Hey there!
When working with the object-centric data model in Celonis, it's essential to understand that test (development) and production perspectives are kept entirely separate. The development environment, identifiable by its test: prefix, is designed exclusively for safely validating schema and PQL changes before they impact live content. Views and analyses built on a production perspective will only be affected by changes published to production; a failure in the development environment will not propagate to the live views. Although there is no automatic link between the two, they use the same underlying customer data, which ensures that any tests conducted in the development environment are realistic. This strict separation mandates a best practice where you always validate changes thoroughly in the test environment to prevent untested modifications from disrupting your stable, live applications in production, especially since some critical Celonis apps only function when connected to a production perspective. Hope it helps!