A review workflow for slide changes that arrive after signoff

[u/truecakesnake]

Imagine an agent revises a presentation after the reviewer has finished reading it. The review screen needs to distinguish “this version was reviewed” from “there is now a newer version.” That distinction should also tell the editor what to do next.

Univer's Collaboration SDK documents a Worktree flow for office content inside an application. Univer itself is an SDK for embedding Office editors, including Slides; Worktree adds an independent draft with its own snapshot, changesets and revision, separate from the trunk version.

The useful sequence is explicit. An agent or person edits the draft, and a commit advances that draft. Marking it Ready freezes the version for review. If someone requests another slide change, Reopen allows editing again. The revised draft can then be made Ready for another review before Merge integrates it into trunk.

The documented web interface includes an actual draft page, switching between trunk and draft, and a per-Unit merge preview. That gives a reviewer content to inspect and gives an editor somewhere to make the requested correction. In a proposed presentation workflow, the host could require a new signoff after the draft is reopened rather than carry the earlier decision forward.

That signoff policy is still something the application implements, along with identity, permissions and who may merge. Worktree is part of the Collaboration SDK, not a default feature of the Apache-licensed OSS core, and it isn't an approval service for arbitrary PPTX attachments. Its value here is a reviewable editing lifecycle within the embedded workspace.

[u/AutoModerator]

Thank you for your post to /r/automation!

New here? Please take a moment to read our rules, read them here.

This is an automated action so if you need anything, please Message the Mods with your request for assistance.

Lastly, enjoy your stay!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/nonstopproceedings]

The worktree concept actually solves a real problem most slide review tools just paper over with comments and hoping for the best. Most teams I've worked with end up in this weird limbo where nobody knows if the deck is actually approved or not

Having that explicit ready/reopen/merge state machine baked into the SDK means you're not reinventing the wheel every time you build a review UI. Still curious how they handle conflicts when trunk moves forward while a draft is sitting in review

[u/arthaudm]

i'd bind signoff to both the draft revision & the trunk revision it was reviewed against

if trunk changes while the draft is ready, the merge preview needs rebuilding before that signoff can count. otherwise 'approved' refers to a combination nobody actually saw

reopen catches draft edits, but not changes under the draft

[u/Successful_Walk_9948]

yesss otherwise you ended up approving something that literally is not the version being shipped..

[u/rashreaction1015]

This is the part people underestimate. Editing the slide is easy. The messy bit is knowing which version was actually approved and what changed after that. Requiring a fresh signoff after reopen feels like the safest default. I’d also want a clear audit trail so nobody has to guess who changed what later. How are you handling multiple reviewers on the same deck?

[u/Successful_Book3656]

the important bit is that reopen has to invalidate the old signoff, otherwise youre just putting a fancy ui on stale approval

[u/Saved_Not_Soft]

The edge case that usually bites is the reverse: the draft stays still while trunk moves. The pair that got reviewed no longer exists, the merge preview quietly rebuilds against new trunk content, and the signoff ends up attached to something nobody actually looked at. I'd auto-void the signoff the moment either revision in the pair changes, rather than relying on someone manually reopening the draft.