What’s new? v4.87 — Paste a screenshot and it survives export

Images pasted into the editor reach the PDF and Word intact, one document can live in several projects, and CRM documents stop floating around.

v4.87.1 — The CRM tagging script no longer fails where there is nothing to sort

A small fix with nothing visible: this version changes no screen.

4.87.0 ships a one-time script that the administrator runs when updating, so that CRM documents that already existed get tagged and show up in the network folder next to the new ones. Running it on all ten installations revealed something the review had missed: where the CRM plugin is installed but has never been used, the script ended with a technical error instead of saying there is nothing to tag. It happened in four out of ten.

Nothing was broken, but an error where the right answer is “nothing to do” reads as if something went wrong, and that makes people retry or call. Now it says so plainly and finishes cleanly.

v4.87.0 — Paste a screenshot and it survives export; one document can belong to several projects

Pasting an image into the editor

Ctrl+V inside the document editor embeds the screenshot; you can also drag it in or upload it with a button. The interesting part was not the pasting but making sure the image survives export.

The PDF is built in a browser with the network blocked, for security, and Word only understands embedded images. An image saved as an address looks perfect on screen and silently disappears from the file you send the client. Here the image is resolved on the server before rendering, so it comes out inside both the PDF and the Word file.

The screenshot is stored encrypted, like the rest of the case file, and does not show up as one more document: not in the list, search or folders, and it is not synced to the cloud. It is content embedded in the body of another document.

One document in several projects

The case that calls for it: a development project and its later maintenance share a contract and a specification. The system always allowed it internally, but it could not be done from the document’s detail view, and there was a trap: the view showed the associated projects right under a control that only accepted one, and saving left the document in that one. Changing the title of a shared document silently removed it from the second project. We measured beforehand that no document was in more than one project, so no harm was done. Now there is a single control, with a search box to add and an × to remove.

CRM documents stop floating around

A file attached to an opportunity or a prospect landed in “General”, mixed with everything else and with nothing saying which opportunity it belonged to: in a real instance that was 61 of the 131 documents in that folder. Now they are born tagged with the name of their opportunity or prospect, and appear grouped in the tags view and in the network folder. If the opportunity is renamed, the tag follows; if the document is unlinked, the tag is removed.

A document now has its own address

It was the only thing in the system without a URL. That explained why links to documents already emitted by the assistant and the desktop apps landed on the list without opening anything. Now they open the document, including those already written in earlier conversations.

The release closes with a small, annoying fix: deleting several documents at once got stuck if one of the requests failed, and the cards of what was already deleted took five seconds to disappear, exactly the gap in which you press again.

documents editor CRM projects release

← Back to the index