[Question] Best practices to prevent regression when multiple developers edit the same UI Page

[ソフィア平]

I am currently working in a multi-developer environment utilizing a build agent for automated deployments. We are facing the following issue, and I would love to hear your insights and best practices.

1. Regression (overwritten changes) when multiple developers edit the same UI Page We have a scenario where multiple developers need to modify the same UI Page (sys_ui_page). In each developer's environment, checkpoints (Update Sets) are created and then automatically applied via our build agent. However, we are experiencing an issue where the Update Set applied last completely overwrites the entire record, causing the previously applied changes from other developers to be lost (regression).

I understand that even if developers edit completely different fields within the same record (e.g., one edits the HTML field and another edits the Client script field), the entire XML payload of the record is captured in the Update Set, which leads to the overwrite.

How do you handle these collisions and prevent regression in your environments under similar setups? Any advice on workarounds or best practices would be greatly appreciated.

Thanks in advance!

[ソフィア平 · Accepted solution]

毎回新規のチャットで更新することでこの問題を解決できたように思えます

おそらくページの情報ではなく自身のチャット履歴の情報を読み取っているため

他人の新しい更新を古いチャットの情報で上書きしてしまっていたのだと思います

新規チャットで更新をかけることで過去チャットの内容で上書きすることなく

変更点だけを更新することができると思います