Hi everyone,
I’d like to bring up a topic that I believe many Service Portal developers have faced.
When working with Service Portal widgets, especially when multiple developers are editing the same widget (same scope, same instance), changes become visible immediately to everyone as soon as the widget is saved.
Even when each developer uses their own Update Set, there is no isolation the widget record (sp_widget) is shared.
Is there any recommended way to handle or mitigate this situation?
For example:
- Do you use widget cloning?
- Separate DEV instances?
- Source Control / GitHub in any effective way?
- Or is this mainly handled through team process and coordination?
If you found this response helpful, please mark it as Helpful. If it fully answered your question, consider marking it as Correct. Doing so helps other users find accurate and useful information more easily.
