Skip to main content
natasav
Known Participant
Oct 28, 2026 4:53 PM UTC
Question

Substitution of check-in and check-out on Tempo

Hello,

we are designing in SAIL interface for document harmonization, and we would like to find something similar to check-in and check-out from apps folder portal.

Any suggestion will be much appreciated.

BR,Natasa  

10 replies

mathieud0001
mathieud0001
Genius
Oct 28, 2026 9:14 PM UTC

Not sure if the check out / check is something you want to replicate but if you really want to replicate it, you would need to store documents in a database and have checkOutDateTime, checkOutUser fields. Otherwise you could also try to leverage baked in checkin/checkout from other CMSs (i.e. Sharepoint).

natasavAuthor
Known Participant
Oct 28, 2026 9:31 PM UTC

Well we use it for hamonization of documents and check in and check out is control to each user to hramonized the last version of the document.All of the application with function of harmonization are still on apps but we need to move them on Tempo.Any other sugesstion is more than wellcome.

mathieud0001
mathieud0001
Genius
Oct 28, 2026 9:41 PM UTC

Just checked and Appian actually has lock/unlock Smart Services

    muhammedk
    Participating Frequently
    Oct 29, 2026 12:32 PM UTC

    Hi everyone,

    We're migrating an existing Appian app, from “Apps” to a “Tempo” version, and the client needs several document-level actions that were available in the older folder-based UI but don't appear to have a direct OOB equivalent in Tempo:

    Actions needed (the ones that they actually used):

    1. Download selected item(s) as a ZIP archive
    2. Check out a file (lock it to the user)
    3. Check in a new version (release the lock)
    4. Upload a new version of the selected file
    5. Delete selected item(s)

    The Display requirements also include (for the Basic User viewing the Requests Dashboard/Task):

    • Who has the document locked
    • When it was locked
    • Current version number
    • List of all uploaded versions (with the ability to download an older version)
    • Ability to rename the unlocked document

    Could anyone point us to the right functions, patterns, or confirm whether we'll need a custom plugin (e.g., for ZIP packaging and version enumeration)? Any best-practice guidance on implementing the check-out lock would be greatly appreciated.

    stefanhelzle0001
    stefanhelzle0001
    Brainy
    Oct 29, 2026 1:14 PM UTC

    Create a record type “Document”, create a process model for each “Action” and add it to the record as Record Actions.

    It’s been a while since I saw the old Appian UI ...

      muhammedk
      Participating Frequently
      Oct 29, 2026 2:16 PM UTC

      For instance, lockedBy (along with pendingApproval, approved, and changesRequireApproval) is probably a legacy property whose reliability is not guaranteed.

      Are all of these functions present in the Tempo version? More specifically, regarding:

      • Download selected item(s) as a ZIP,
      • Who has the document locked
      • When it was locked
      • List of all uploaded versions (with the ability to download an older version),
      • Renaming the unlocked document.
      mathieud0001
      mathieud0001
      Genius
      Oct 29, 2026 9:28 PM UTC

      Tempo does not provide any of this OOTB AFAIK. It works differently than the old Appian Portal (if that’s what you are referring to)

      And Tempo isn’t really used that much for new sites anymore. We use sites now.

      muhammedk
      Participating Frequently
      Oct 30, 2026 7:23 AM UTC

      "the old /apps environment" -> "Apps" (our internal way of calling it shortly)

      "the modern /sites environment" -> "Tempo" (our internal way of calling it shortly)

      Yes, we do use "Sites". I'll refer it as Sites in the future to avoid any confusion.

       

      So regarding the first two function, we found a possible solution

      • Download selected item(s) as a ZIP,
      • Who has the document locked
        • Probably document(documentId, "lockedBy"), although this is legacy, not guaranteed to stick around, and not recommended for new builds
      • When it was locked
      • List of all uploaded versions (with the ability to download an older version),
      • Renaming the unlocked document.

      How would you suggest we approach implementing this to achieve the desired scenarios?

      Terms & ConditionsAccessibility statement