WHAT:
A design object whose design is locked, is obviously under construction. But it is used in any db refresh process although it is under construction !
WHY:
if a incomplete design object gets used to refresh another DB it can cause problems as unfinished design/code may get used in productive DB and can cause havoc.
SOLUTION:
Add code in those routines involved in the REFRSH DESIGN process that ignore Desing Elements that are locked for design changes.
ADDENDUM:
If design elements are under development, are therefore locked and then are transferred to a productive DB and overwrite existing working design elements, it would casue trouble. The produktive design elements should remain in the productive DB. Thats exactly what I would like.
If the design elements have not yet been in the DB, then they have no business being there because they are not ready.
MORE INFO :
https://support.hcl-software.com/community?id=community_question&sys_id=90219c7afb64ee145d73f0bd5eefdcc3
I ask that HCL doesn't implement this for the following reasons:
Design locking is there to lock design elements, not control inheritance.
An "incomplete design object" shouldn't be in a live template. If the design element were in a test template then you may still want your test DBs to inherit from it.
If someone creates a new DB, or replaces a DB design, from a template with design elements locked then that DB would have missing design element's and will not work.