Reflecting Changes to Dynamic Artifact Types Back to Development System

If you modify dynamic artifact types on production or test systems, you should always ensure that these modifications are reflected back to the development system.

Various 'Dynamic' development artifacts exist in the application that can be modified at runtime on a production or test system (e.g., codetables, workflows, etc.). Runtime changes to these artifacts should always be synchronized back to the development codebase so that concurrent development changes can be integrated with these runtime changes prior to deployment.

Concurrent changes to these artifacts may happen during routine project milestone development, or when taking on Service Packs or doing Major/Minor version upgrades. In every case, there must be one central place where concurrent changes are merged together and validated and this is the development codebase. The System of Record for these artifacts is the development codebase.