UI Builder Variant Simultaneous edit

[cmcgrath]

Based on how Save behaves, I am suspicious/concerned that only one user can be editing a specific page variant in UI Builder at a time, because it does a <complete> save of all components each time. 
If I open previously saved version Y and make edits at the same time that my teammate is making edits, the second save would overwrite the first, correct?

- Can anyone confirm whether or not this is the case, and if there's any way to warn a user before they open/save?

[Johns Marokky · Accepted solution]

Hi @cmcgrath,

Yes, you are correct. Whoever is clicking save their updates would be saved.

Only 1 Person should work on each variant in UI Builder at a time.

It's always better to maintain a group chat for developers who work on the same variant and mention a message in the group chat that they are going to make changes in the particular variant.

If you feel like multiple developers are dependent on the same variant, then we can take the duplicate of that particular variant and push it to a test page where developers can develop and keep it ready. Once the developer who is working on main variant is complete then the other developers can develop it easily and faster.

Mark helpful it helps in solving your query.

Regards,

Johns

[Johns Marokky · Accepted solution]

Hi @cmcgrath,

Yes, you are correct. Whoever is clicking save their updates would be saved.

Only 1 Person should work on each variant in UI Builder at a time.

It's always better to maintain a group chat for developers who work on the same variant and mention a message in the group chat that they are going to make changes in the particular variant.

If you feel like multiple developers are dependent on the same variant, then we can take the duplicate of that particular variant and push it to a test page where developers can develop and keep it ready. Once the developer who is working on main variant is complete then the other developers can develop it easily and faster.

Mark helpful it helps in solving your query.

Regards,

Johns

[cmcgrath]

Appreciate the confirmation @Johns Marokky  (and seconded by @Brad Tilton ) - if not the answer 🙂

For anyone else who finds this and can't rely on manual team reach-outs, please upvote my Idea on the SN Portal to improve this experience!

https://support.servicenow.com/now?id=view_idea&sysparm_idea_id=4397087b930a6550f2167de86cba1058&sys...

[cmcgrath]

Thanks for the confirmation @Johns Marokky (and @Brad Tilton ) - if not as strong thanks for the result 😉
Having to rely on a manual communication isn't great for our team -- for anyone else who finds this thread and agrees, please take a look and upvote my Idea here: https://support.servicenow.com/ideas?id=view_idea&sysparm_idea_id=4397087b930a6550f2167de86cba1058&s...

[Brad Tilton · Accepted solution]

Yes, the current paradigm is that there should be one developer working on any one variant at a time. On the back end, all of the component layout, page state, data resources, etc. are housed in one sys_ux_macroponent record that represents the page. It does have a versions related list if you need to revert to a previous version of the page.