SFUMIADocumentation
Private test version

Guide

Save, version and publish

Choose how to keep work or make a result available.

Updated
In this guide

Keep the current result

Saving keeps your current work. You can generate and keep an AI result without making a version or publishing it. Sending a result back to a studio requires your reservation and current service validation.

Create a version or publish

Create a version to retain an identifiable state of the work. Publishing is a separate decision that makes a result available through the project’s intended workflow.

Saving or synchronising does not imply publication. Check the node, result and project permissions before publishing.

Three separate actionsChoose according to what you want to keep or share.
  • Save

    Keep the current work.

  • Create a version

    Keep an identifiable state to return to.

  • Publish

    Choose a reference for the pipeline.

Keep a recovery backup

Shared projects and private service data serve different purposes. Copying an active database does not by itself make a consistent backup. Use the backup process intended for your installation.

After a disconnection, keep your private working copy. Reconnect and check the studio state before sending shared changes. Reconnection must not publish anything automatically.

What the following nodes read

A downstream node reads the upstream node’s result according to that node’s state. It is not recalculated automatically: run it again to take a new publication into account.

Upstream node stateWhat the following node reads
Never versioned or publishedThe file chosen in « OUTPUT FILES ».
Versioned, never publishedStill the file chosen in « OUTPUT FILES »: a version alone does not change the rest of the pipeline.
PublishedOnly the publication, even if other versions are created later without being published.
« Publish manquant : republiez le node »

This message appears when a following node must read the publication of a published node and that publication’s file is missing. SFUMIA never replaces it with the working output. Republish the upstream node with « Créer et publier », or a version from its history with « Publier cette version », then run the following nodes again.

Lock before versioning or publishing

In a studio, « + Version » and « Créer et publier » require the node to be locked in your name: without this lock, these buttons stay inactive in « VERSIONS / PUBLICATION ». The « ↑ Publier » button on the card publishes the latest existing version; it does not offer to lock the node.

  1. Lock the node: « 🔒 Verrouiller » in its properties, the 🔓 badge on its card or the L key.
  2. In « VERSIONS / PUBLICATION », enter a comment if needed, then choose « + Version » or « Créer et publier ».
  3. For a publication, read the confirmation, then validate. Then run again the following nodes that must take it into account.
Publish a scene in Local mode

A scene switched to « 💻 Local » stays local and locked after its publication. SFUMIA says so: « La publication reste locale et le node verrouillé : elle devient visible aux autres postes après le retour au réseau. » Returning to the network remains an explicit action.

Available features depend on your version and installation.

Search the guides

Type a word or choose a guide.

Language

العربيةবাংলাEnglishEspañolFrançaisहिन्दीBahasa IndonesiaPortuguêsاردو简体中文

Change theme