What’s new? v4.49 – Alerts on time and “Case or project?”

Discover the improvements we’ve added in each release to make Iurefficient a more powerful, smarter and more secure tool for your professional practice. v4.49.1 — Reminders go off on time, and plugins can actually be used “Remind me to contact them Wednesday at 10” responded “An unexpected error occurred.” The assistant was doing its part right:…

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

v4.49.1 — Reminders go off on time, and plugins can actually be used

“Remind me to contact them Wednesday at 10” responded “An unexpected error occurred.” The assistant was doing its part right: it knows the firm’s time zone and wrote the time using it. It was the server that couldn’t read it —it only understood times in UTC— and the alarm was never created. When the reminder was recurring it was created, but with the time shifted: “every Friday at 10:00” was saved as 10:00 UTC, that is, going off at 4 in the morning in Mexico. Now the time you enter is your firm’s time, for daily, weekly, monthly and cron-expression reminders. Alarms you created before keep the shifted time: it’s a good idea to open them and save them again.

Granting access to a plugin is now enough to use it. Checking someone under a plugin’s “User access” did nothing if that person wasn’t an administrator: they’d get to the screen and everything responded “permission denied,” citing permissions that don’t exist in any installation of the system. The same happened in CRM, Tax, Billing, Tickets, Inventory, Human Resources, Collaboration and Portal. Anyone without explicit access to the plugin still can’t get in, and permissions in the rest of the system don’t change.

Includes everything from 4.49.0. No migrations; update backend and frontend together.

v4.49.0 — Your firm no longer has to read “case” if it works by projects

The word you chose in Settings is now used throughout the application. Each instance decides what its unit of work is called —case, project, matter, opportunity— but that choice only reached the screens that asked for it explicitly. Everywhere else, the word came hard-coded: a law firm read “Project Roles” in its settings and a consulting firm, “Case Documents.” That no longer happens anywhere: menu, search, dashboards, lists, forms, Gantt, settings, reports and plugin panels speak your language. The texts in both languages were reviewed against the three most common ways of working, one by one.

Your clients’ portal now speaks two languages —and with your words. Until now the external portal was written in fixed Spanish. Now it’s translated and, in addition, uses your firm’s terminology: whoever comes in from outside sees the same thing you see, in the language you set for them when you invited them.

Help does too. The in-app guides —including the security one— stop talking about “cases” to those who work by projects.

And so do emails and notices. Notifications sent by email and those in the bell use your word, in the recipient’s language.

Spreadsheets can once again be queried in natural language. If you asked about the numbers in a table you had uploaded, the system answered as if the project didn’t have any: files are stored encrypted and that particular query read them without decrypting, so no sheet ever reached the data engine.

No migrations; update backend and frontend together. The terminology you already had configured is respected as is: there’s nothing to re-enter.

← Back to the index