What’s new? v4.81 Improved files

The network folder stops showing projects twice The case file gets organized inside, and you can browse by client

Discover the improvements we’ve added in each release to make Iurefficient a more powerful, intelligent, and secure tool for your professional practice.

v4.81.1 — The network folder stops showing projects twice

Projects live inside their client, and no longer outside it too. The previous release added the per-client view and left the loose project list where it was, so when you opened the network folder the same projects appeared in two places. For browsing, that makes no difference; for a program that copies to disk, two paths are two files, and every document was downloaded twice. Now the flat list is no longer offered: all the projects are still there, inside their client, which is where they belong — and none is left out, because a project without a client can’t be created.

If you already had it mounted, your mount won’t break. That path keeps working exactly the same; the only change is that it’s no longer shown when you open the network folder. With this, syncing means mounting the clients folder: the root is still not the place to sync from, because “Views (browse only)” shows those same documents organized by tag and by task.

A document that’s in two projects shows up in both, and that’s on purpose. It isn’t a copy: it’s the same document seen from each case file, just like on the Documents screen. If those projects belong to different clients, it also appears under both clients, and editing it through either path writes to the same file.

And each folder now says whether it accepts a file being dropped into it. The diagnostics in some sync programs concluded that nothing could be uploaded to the network folder, even though it could: they asked about the folder, and the answer only existed for the file, which wasn’t there yet.

Updating doesn’t change any data. The only thing that changes is the shape of the tree: if you sync from the root, you should point it to the clients folder.

v4.81.0 — The case file gets organized inside, and you can browse by client

A document you can’t see can no longer be modified. This is the most important part of this release, and it has nothing to do with folders. When someone opened another person’s document, the system answered “access denied,” as it should; but when they changed 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 access and put it into another one, in a single operation. Deleting it had the same gap. Now all three paths check the same thing, and the destination too: a project or client you can’t reach is rejected, and you’re told which one.

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

The client joins the network folder tree. Alongside the usual project list, there’s now a per-client view, with its projects inside. They’re two paths to the same material: if you think by client, you go in through one; if you think by case file, through the other. The trade-off has to be spelled out: to sync, 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 deep. 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 limit isn’t a whim: any deeper, and 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 you 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. This 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 used to show the derivative’s name and now shows the original, with the derivative on its own row.

← Back to the index