What’s new? v4.81.0 — The case file gets organized on the inside

A document you can’t see can no longer be modified. It’s the most important thing in this release and it has nothing to do with folders.

v4.81.0 — The case file gets organized on the inside, and you can go in by client

A document you can’t see can no longer be modified. It’s the most important thing in this release and it has nothing to do with folders. When opening someone else’s document the system responded “access denied,” as it should; but when changing it, it said yes. Someone who couldn’t read it could rename it, change its owner and —most importantly— take it out of the case file of the person who did have it and put it into another, in a single operation. Deleting it had the same gap. Now all three paths check the same thing, and so does the destination: a project or client you don’t have access to is rejected, and you’re told which one.

And you can now change a document’s client. That link was only created when uploading the file, so once saved there was no way to reassign it from any screen, and trying gave an error. It wasn’t that it failed: that half had never been written.

The client enters the network folder tree. Alongside the usual project list there’s now a view by client, with their projects inside. They’re two paths to the same material: whoever thinks by client goes in through one, whoever thinks by case file through the other. The flip side has to be said: to sync, you mount one of the two, never the root — from the root every document would be downloaded twice, because it can be reached from both places. For browsing, the root is no problem at all.

Your own folders inside the project. “Contracts,” “Invoices,” “Correspondence,” up to three levels. They’re created from the Documents screen and look the same from the network folder. Deleting a folder never deletes documents: whatever is inside moves up to the project root and you’re told how many, because a document lives in the case file and the folder only says where you stored it. The three-level cap isn’t a whim: below that, the path no longer fits in Windows Explorer.

Tags are still there and don’t compete with folders. A document is in one folder and carries many tags: the folder answers “where did I store it?” and the tag answers “what’s pending signature across all case files?”.

A branch for browsing by tag and by task. It’s called “Views (browse only)” and the name is the warning: looking at them is ideal —there the tag is the folder, so nothing gets lost—, but syncing them would download a document with three tags three times, and editing one copy would leave the others outdated on your own disk.

A transcription no longer passes itself off as its audio. The network folder showed “salida.mp3” and when opened it delivered 48 KB of text —the transcription— instead of the 62 MB of audio; the same happened with the PDF produced by applying OCR to a photo. It happened because the transcription was saved as if it were “the newest version” of the audio, and a version replaces the original. Now both files are shown, each with its own name and content, without losing the link between them.

Updating doesn’t create any folder in any project: you have to create them by hand. The only thing that changes on its own: where there was a transcription or an OCR PDF, the document list showed the name of the derivative and now shows the original, with the derivative on its own row.

← Back to the index