A page used to be either published or not. A staging page works at its real route but stays out of search engines, so you can send a client the link before the page is public. Move a live page to staging and the live version stays up while you work on it.

Gap could only be set from the Layout panel: type a number, look at the canvas, try again. Now you drag it on the canvas, the way padding already worked. Padding got a fix too, so dragging one side no longer moves the others. Margin handles are gone from the canvas, and margin is still in the properties panel.

A site is usually a handful of pages that link to each other, but moving between them meant going back to the dashboard each time. The Layers tab now starts with the pages in the open page's folder. Also, importing a template puts its pages in their own folder under one route, so the links between them resolve instead of landing on a 404.

Bob checked its work with a single screenshot of the desktop page in light mode, so a dark mode or mobile change could be reported as working when it was not. It can now preview a page in dark mode and at mobile width and read an image block, and it checks a change in the mode you asked for before calling it done.

Real italics on the canvas, colour tokens in the Background field, duplicates that arrive as numbered drafts, and a long tail of keyboard, popover and dialog fixes.

Meet Bob, your AI assistant in Builder. Describe the page you want and Bob builds it, design tokens, scripts and page properties included. It can also create DocTypes and wire them up to the matching forms.

The conversation carries on as you work, so you can ask for changes as you go. To change one section, select it and tell Bob what you want.

Anything sensitive (a new DocType, sample data, edits to the home page or global code, form wiring) waits for your approval first. Every turn leaves a trail you can review, and you can revert the changes from a single turn without touching the rest.

Settings → AI walks you through connecting a provider. There are presets for OpenRouter, Anthropic, OpenAI, ChatGPT through a Codex subscription instead of an API key, and Google Gemini, plus a custom option for any OpenAI-compatible gateway.

Builder Variables is now Builder Tokens, and it holds Font and Dimension tokens alongside colours.

Cropping an image used to mean typing object-position by hand. The image popover is now a compact card with three fit options, Fill & Crop, Fit and Stretch, and for cover fits the preview doubles as a focal-point picker. Drag the dot and the crop updates live on the canvas; a zoom slider crops further around the point you picked. Blocks with a cover background image get the same picker in the Background popover.

The font picker now previews each font in its own typeface, in the dropdown rows, the field itself and the design token rows.

Published status is glanceable, on the dashboard grid cards and next to the page title in the editor toolbar.

Gap can be split per axis, row and column, in both the Flex and Grid panels.

Client scripts now show how many pages use them, and clicking through opens the full list. The colour picker surfaces recently used colours, with the last eight shared across every picker in the tab and the static palette filling the unused slots. The editor is translatable end to end: user-facing strings are wrapped, translations are served through boot data, and 35 language catalogs are synced from Crowdin. We also fixed two memory leaks in the editor and added a way to move large SVGs out of the page.

Starting with v1.31.0, Frappe Builder is distributed under the MIT License, moving away from AGPL-3.0. AGPL's network-copyleft terms made some legal teams wary of embedding or self-hosting Builder. MIT removes that friction, so you can use, embed, and build on Builder with fewer strings attached. Thanks to every contributor who signed off on the relicensing.

Rearranging a layout previously meant dragging items in the layers tree. You can now grab any block directly on the canvas and drop it where you want it. The engine understands flex and grid containers, shows exactly where a block will land, and handles nesting into and out of containers without jitter or layout shift.

The raw styles panel has been replaced with a curated styles editor. Common properties live in organized sections, and a new More Styles section lets you add any CSS property through fuzzy search.

Spacing, border, and radius now use split controls: drag the label to change values, or switch to per-side mode and edit each side individually. Border radius also gets a visual per-corner control and a canvas handle.

Blocks can now be rotated right on the canvas using corner grips, with Shift snapping to 15 degree steps. Selection boxes, resize handles, and spacing handlers all stay aligned to the rotated block, and a Rotation control is available in the style panel.

Previewing a template used to open a new tab. Templates now render as a live preview inside the picker, with desktop, tablet, and mobile toggles so you can check how a template responds before using it. Category filters help you narrow templates down to what you are building.

Press Cmd+Shift+D to flip the canvas between light and dark while editing. Published pages now declare their color scheme in the head, so dark pages no longer flash light on load.

You can now invite your collaborators right from Builder.

True italic font faces instead of faux-slanting, a leaner editor bundle through lazy-loading, a read-only mode notice, Esc to cancel a drag, and a batch of copy-paste and autocomplete fixes.

You can now stop new sales documents for a customer until a date you pick. Tick Block Customer on the Settings tab of the Customer and set a Release Date, or leave the date blank to hold them until you clear the check box.

A blocked customer cannot save or submit a Sales Order, Delivery Note, Sales Invoice or POS Invoice. Quotations still work, and so do payments from that customer. The Customer list shows On Hold while the hold is on.

Changing a submitted quotation no longer means cancelling and amending it. Use Create > New Version and you get a draft named <original>-R1, then -R2, and so on, keeping the original name.

Submitting a version marks the others Inactive, and you cannot raise a Sales Order or Sales Invoice from an inactive one. A new version has to keep the company and the party of the original, and Set as Lost on any version marks them all Lost.

A Blanket Order now has a status: Draft, Submitted, Closed or Cancelled. Use Status > Close to stop new orders against it and Status > Re-open to allow them again.

Single rows can be closed too, through Status > Close Items, as long as part of the row's quantity is still unordered. Close every row and the Blanket Order closes itself; reopen one and it reopens. Row colours show where each one stands: green is fully ordered, orange has quantity pending, grey is closed.

A new report shows the stock balance of each item along with the batches and serial numbers actually in stock. It takes the same filters as Stock Balance.

Expand an item to get a row per batch with its opening, in, out and balance quantity and value, and the serial numbers in that batch. The batch quantities add up to the item row. The report does not read Stock Closing Entries, because those do not store serial numbers, and it tells you when one exists.

Three new reports for Subcontracting Inward Orders, the ones where a customer sends you materials to make their goods.

• Subcontracting Inward Order Summary shows ordered, produced, delivered and returned quantities per finished good, plus the customer materials received, consumed and returned.
• Subcontracted Raw Materials To Be Received lists customer materials still pending on open orders.
• Subcontracted Items To Be Delivered lists finished goods you have not delivered yet.

They sit in the Reports group in the Subcontracting sidebar.

Serial number wise valuation used to be implicit. It is now a Use Serial No Wise Valuation check box on the Item, so you can turn it off where you do not need it.

It is worth turning off when the count is large. A telecom company holding millions of SIM cards rarely needs the valuation of each card, and valuing every serial number slows stock reposting badly. With the box cleared, the item falls back to Item and Warehouse wise Moving Average. A company selling a few high value set-top boxes, on the other hand, probably does want each box valued on its own, so it keeps the box ticked.

If serial numbers already exist and the box is cleared, the valuation method is forced to Moving Average. Otherwise you can set FIFO, LIFO, Moving Average or, from v17, Standard Cost.

Note: this is available in version 16.

When the Stock and Account Value Comparison report shows correct Stock Ledger values but wrong GL entries, reposting everything was the only option, and that reposts the Stock Ledger too. There is now a separate button that reposts only the GL entries, which is much faster. It is also the one to use after changing a warehouse's inventory account.

Note: this is available in version 16.

A backdated stock entry makes ERPNext recalculate the stock value of every affected transaction after it. Reposting used to load all of them into memory at once. On a large site that can be a million transactions at roughly 3.5 KB each, which is several GB of RAM, and when the server ran out the operating system killed the job and left stock values wrong.

Reposting now works through 500 ledgers at a time, and leftover data that used to pile up during a repost is cleaned as it goes.

Four new reports show what a party owes you, and what you owe them, across several of your companies at once. The companies do not have to be related.

• Consolidated Accounts Receivable and Consolidated Accounts Payable list each party's open invoices with the company every invoice belongs to. Group the rows by party or by company.
• Consolidated Accounts Receivable Summary and Consolidated Accounts Payable Summary give one row per company per party, then that party's total across them.

Pick the companies in the Companies filter; choosing a group company pulls in everything under it. Totals are dropped when the selected companies use different currencies, since unlike currencies cannot be added. The summary reports are in the Registers group in the Accounts sidebar, and each links through to its detailed version.

A BOM is the recipe for a product, and until now it needed the exact quantity of every item. In paint, chemicals and food, people think in percentages instead. Enable Set Component Quantities Based on Percentage on the BOM, enter the percentage against each item, and the system works out the quantities for you. The percentages have to add up to 100.

For a 100 kg batch of paint made of 60% resin, 30% solvent and 10% pigment, you now enter 60, 30 and 10 instead of computing the kilos yourself.

Note: on the develop branch, not backported to v16 or v15.

In process industries the output is not always the grade you planned for. The material is still good and still sellable, but changing the item earlier meant a manual Repack entry that was never linked back to the Work Order, so production reports showed the wrong item as produced.

Submitted Work Orders now have a Change Finished Item button. Pick the replacement from the item's existing Item Alternative setup, enter the quantity, and ERPNext creates a Repack Stock Entry linked to the Work Order, carrying batch and serial numbers across. The Work Order Summary report then shows what was actually produced.

Note: on the develop branch, not backported to v16 or v15.

A steel rod bought in KG under one batch, then cut into pieces counted in Nos, needs a batch number per piece, and a way back to the batch it came from. This used to need a manual Repack entry and custom code at every site.

BOM Operation now has a Batch Split checkbox and a Weight Per Piece field, both carried through to the Work Order and Job Card. On completing the Job Card, ERPNext creates one batch per piece from the item's batch series, stores the original batch in each child's Parent Batch field, and splits the cost by weight. Where the material came from several input batches, each piece is linked to the batch it was actually cut from. A batch split tree report shows the full lineage.

Note: on the develop branch, not backported to v16 or v15.

The same raw material can take 3 days from one supplier and 10 from another, but the Production Plan only ever used a single lead time for the item, which threw off the schedule. A new Item Lead Time Supplier table lets you set the purchase lead time per supplier.

Note: on the develop branch, not backported to v16 or v15.

Service lines on a Sales Order, like Installation Charges or Annual Maintenance, do not need a Delivery Note, but the order would sit in To Deliver long after the work was done and paid for. Selling Settings now has a Skip Delivery Note Creation for Service Items option, so teams that do want a Delivery Note for services can carry on as before.

Note: on the develop branch, not backported to v16 or v15.

Blanket Orders can now be created in the party's own currency, or overridden manually where you need something else.

v16 let you allocate a set percentage of the outgoing raw material cost to a secondary item. That now has two more options: Valuation Rate picks up the secondary item's valuation rate as on the posting date of the transaction, and Manual lets you set the basic rate directly in the transaction.

Users can now restrict certain Items, Customers or Suppliers to a certain selected list of companies. For example: if you restrict an Item to Company A, users who do not have access to Company A would not be able to see or transact with this item.

Note: This feature is currently available only on the develop branch.

Every send now waits a few seconds before it actually goes. Spot a typo, hit Undo, and the message is back in Drafts. You pick the window in Settings, anywhere from 5 to 30 seconds.

If you would rather it went out on Monday morning, schedule it with Cmd+Shift+Enter. Scheduled and in-flight mail shows up in the Outbox, where you can send it now, push it later or cancel it. Once it leaves, the Outbox shows what happened to each recipient.

Compose no longer has to be a modal. Dock it in the corner or minimise it to a title bar, go read the thread you wanted to quote, and your draft stays where you left it.

Type @ in the body to mention a colleague. They are added to the recipients as you type, and removed if you delete the mention.

Collapsed messages are one line each, so an eight message thread fits on one screen. The expanded header says "to Pushkar, Rushabh and 2 others" instead of repeating the whole roster.

Open an email with a calendar invite and a banner shows the event with Yes, No and Maybe right there. Not a participant? Add it to your calendar in one click.

Drop a thread onto a folder in the sidebar to move it. Select a few and drag them together.

TLS reports sit beside DMARC reports in the dashboard, and the members list shows how much storage each person is using.

Your inbox now has a bouncer. First-time senders wait at the door until you let them in or turn them away, one click each, with no filters to write. You can screen whole domains, admins can set org-wide rules, and it is on by default for personal accounts.

Search across all your accounts at once, with a quick-filter bar, removable filter chips, autocomplete for operators and contacts, and highlighted matches. There is also a Filter messages like this action, one click from any mail.

Mail is now an installable app on your phone, with a bottom tab bar, swipe between threads, slide-up compose and the full settings. iOS launch screens included, because details matter.

Upcoming events now live in the Mail sidebar, and clicking one opens the event details right there. No hopping over to Calendar just to check when that meeting is.

The admin dashboard was rebuilt: proper detail pages for members, groups and mailing lists with inline editing, richer invites covering quotas, groups, locale and time zone, DKIM management, logs, DMARC reports, and an audit trail of admin actions.

One unified inbox across every account you have. Scroll forever, open threads in place, and read mail from any account without switching. Chatty senders get stacked, so one newsletter cannot bury everything else.

Archive, trash, junk, move: actions happen instantly now, and every one of them comes with an undo. Fat-finger away.

Contacts import and export cleanly now, as .vcf files or straight over JMAP. Moving in, or out, no longer means retyping your address book.

Auto attendance always waited until the next day to mark someone Absent, even when their shift had ended hours earlier. Shift Type now has an Absent Buffer (Days) field. Set it to 0 to mark Absent the same day, or higher if your team needs longer to sort out missed check-ins. It defaults to 1, so nothing changes until you change it. Same-day marking needs Automatically update Last Sync of Checkin switched on.

When someone took a half day leave and checked in for the other half, auto attendance could mark that half day Absent before the shift had even ended. Their check-ins then arrived too late to change it and the day stayed Absent. Half days are now closed only once the shift is over.

Daily Work Summary is gone from develop, along with Daily Work Summary Group, the Team Updates page and the Daily Work Summary Replies report. v16 shows a deprecation notice in all of them, so it will not be part of the next major release.

The salary slip formats HR shipped were all built in the Print Format Builder, which cannot express a net pay band, a year-to-date column or an attendance breakdown. Three new formats, written as Jinja, cover the layouts people were rebuilding by hand anyway.

Employer Contribution salary components passed no accounting entry at all. They now get their own Journal Entry.

India Payroll can now file Form 24Q from inside the system. Every deduction already sits on the salary slip, so the return builds itself from payroll, reconciles against the challans you deposited, and goes to the department through the Sandbox API. No exports, no separate return preparation utility, no re-keying deductee data.

Set up in two places. Enter the deductor details once on the Company: TAN, deductor type and the person responsible for deduction. Then turn on TDS Return Filing under the India Payroll tab of Payroll Settings. Sites on Frappe Cloud get Sandbox credentials provisioned; any other site adds its own API key and secret. A Sandbox test mode lets you dry-run the whole thing before a live filing.

Challans as documents. Record each TDS deposit as a TDS Challan with its BSR code, serial number, deposit date and amount breakup. The challan works out which salary month it pays for, so deductees map to challans without manual matching.

One click from salary slips to deductees. Create a TDS Return for the company, financial year and quarter. The deductor block fills itself from the Company and its linked address and contacts. Hit Fetch from Payroll and every submitted salary slip with income tax deducted becomes a deductee row, one per employee per month, with PAN, amount paid, tax deducted and the matching challan. Rows stay editable for the odd correction. Totals for amount paid, tax deducted and tax deposited sit side by side, and the return will not proceed if deducted exceeds deposited.

A four step, audited pipeline. Each step runs as a background job and is logged on the return.

• Validate runs Sandbox's potential-notice check and shows any issues before you commit anything.
• Generate TXT produces the return file in the department's format.
• Generate FVU validates the TXT against the CSI file and returns the FVU along with Form 27A, both previewable and printable from the return. The CSI file is fetched with an OTP sent to the deductor's TRACES-registered mobile.
• E-File submits the FVU and writes back the token number, provisional receipt number and filing date.

Submitting the document locks the filed return. Revised returns work too: pick Revised and enter the previous receipt number.

Form 16 without the scramble. Once the Q4 return is filed, Create Form 16 generates a record for every employee in the annual annexure. Part B is built from the employee's salary data and Part A is requested from TRACES using the deductor's TRACES login stored in Payroll Settings. Both PDFs attach to the Form 16 record, ready to share.

Ready for the new Income-tax Act. Returns for periods under the Income-tax Act 2025 are generated in the new Form 138 layout automatically, so the same flow carries over when the switch happens.

TDS filing ships with the India Payroll app for Frappe HR. Enable it from Payroll Settings, record your challans, and file your next quarter from payroll.

The single-button checkin from the PWA is now on desk too, and you can keep adding checkins for other employees straight from the form.

Newly onboarded employees need a pile of masters assigned to them, some of them are mandatory. The Employee master now has a quick action menu for exactly that, so HR managers no longer have to leave the employee document to do it.

Employer contribution components now appear on the salary slip, below earnings and deductions, so statutory amounts like the employer's share of ESI and EPF are visible rather than implied.

Holiday counts came out too low whenever a date range crossed a month boundary and the same day-of-month appeared in both months (the 15th of January and the 15th of February counted once between them), so real holidays were being skipped.

In the summarised view, the second half of a Half Day was always counted as Present regardless of what it actually was, so employees marked absent for that half never showed up under Total Absent. Every Half Day was also counted as 0.5 leave even when no leave was taken, so half-days coming from checkins were shown as leave instead of present. All three are fixed.

Picking a perfectly valid Employee Advance on an Expense Claim could throw "advance does not belong to this employee". The real cause was either a currency mismatch between the advance and the claim, or an advance linked to a non-Receivable account, but the message never said so. It now names the actual reason, and the same checks run on save rather than only at selection.

Clicking Create Interview on a Job Applicant previously navigated away to a blank Interview form, breaking the recruitment workflow. This has been replaced with a Schedule Interview dialog that collects the interview type, date, time, and interviewers in one place without leaving the form. Interviewers are now auto-populated from the selected Interview Type.

A Send Offer Letter action has been added to Job Offer, sending a personalized offer letter email to the candidate from the Hiring Sender Email configured in HR Settings, keeping hiring communication separate from the default service email. The button relabels to Resend Offer Letter after the first send, and a default offer letter email template is included and can be customized before sending.

A Send Confirmation action has similarly been added to the Interview form, sending a confirmation email to the candidate and all interviewers and relabeling to Resend Confirmation after the first send. A Schedule & Notify option on the Schedule Interview dialog allows the confirmation email to be sent immediately upon scheduling. This can be toggled on or off from HR Settings, where the template is also customizable. Interview and feedback reminder emails have been improved as well, with feedback reminders now sending an in-app notification to pending interviewers.

The job application web form now displays the job opening's title instead of its raw ID when a candidate navigates from a job listing. A new Prevent Duplicate Applicant option has also been added on Job Opening, blocking the same email address from applying to the same position more than once.

Other fixes

• Half-Yearly Earned Leave Allocation: fixed incorrect allocation dates and leave amounts for half-yearly earned leave schedules based on an employee's joining date. #4847
• Salary Slip Default Amount: fixed Default Amount for formula-based salary components getting incorrectly prorated whenever payment days differed from total working days. #4888
• PWA: fixed link fields clearing, blank Employee Number and Reports To fields on the Profile page, and the checkin button defaulting to "IN" before the last checkin loaded.
• Leave Overlap Validation: fixed a gap where a full-day plus a half-day leave on the same date could both be approved. #4789. Contributed by Girish Raghav
• Roster API: fixed cancelled Shift Assignments silently blocking new shift creation for adjacent date ranges. #4980. Contributed by Pratheep S

Every view has been redrawn with flat event pills and no shadows. Overlapping events are separated by a thin ring rather than a drop shadow, and titles wrap instead of clipping. The Month grid no longer hides events behind an "n more" button: weeks grow to fit their busiest day.

A fourth view alongside Day, Week and Month: the next three months as a list, with empty days left out. Each row says what the event is doing that day, like "From 6 pm" or "Day 2/3", and fades once it has ended. It opens on today.

Month, week, day and agenda views built for a phone, with events opening as sheets. Mail and Calendar are now one installable app, with a switcher to move between them.

Search events from the command palette by title, description, location or attendee, and filter by calendar, organizer or date range. Results are ordered by how close they are to today.

Change a recurring event and Calendar asks how far the change should reach: just this one, this and following, or the whole series. The same question comes up for moving, deleting and RSVPing.

Save an event as a draft and nobody gets an invite until you send it. Events you have declined stay visible but stop taking up room in the grid.

Create calendars, rename them, pick a colour, set a default, and choose which calendar an event belongs to.

Press ? to see them all. E creates an event, T goes to today, and D, W, M and A switch views.

The event modal and the detail panel were rebuilt from the ground up, repeat settings got a tidy home of their own, and every event now has a URL you can share.

Invitation emails were redesigned with proper RSVP links, the RSVP confirmation page got a facelift, organizers are notified when someone responds, and cancelling an event now actually tells your guests.

Attach a Meet link to any existing event. The meeting row is front and centre now.

The community's most requested feature is here. You can record your meetings, and the recordings show up in your Drive.

Pin the messages that matter in a call and they stay pinned until the call ends.

We gave Meet a fresh coat of paint and made it more aligned with our Espresso design system. We also tweaked quite a bit of things to ensure that the calls will be snappier than ever.

If you think you need even more secure calls, you can toggle End-to-end encrypted calls on and every frame of video or audio, chats and polls will only be accessible to the participants of the call.

Now you can schedule calls either from Calendar or from Meet's homepage with your team. The upcoming meetings will show up in home page for you to join.

If you want to know how Meet is performing and to do a deep dive into what's happening underneath, toggle this on.

Administrators get more control over the portal from one place, including languages, system timezone and text direction, badge assignments, and the Google API and Calendar integration.

Programming Exercises, Assignments and Quizzes have a cleaner assessment screen, with more room for the question, the answer and the feedback.

Programming Exercises now feel much closer to a real coding environment, with the familiar keyboard shortcuts, including ⌘ + ` to open the console.

Every page in Learning now has a mobile screen of its own, so course creators and students get the same experience on a phone as they do on a laptop.

You can now require students to work through a course in the order you set it. Toggle it on in the course settings.

Use Frappe Learning with Raven with ease with the new integration; it automatically adds people from various batches or courses depending on your rules.

Which ticket fields a customer can see or change is now decided by Frappe's permission levels, the same ones you set in Role Permissions. Customers could previously see or change some fields simply because the portal page left them unguarded. The rules are now checked on the server, so they hold for the portal and the API alike.

• Three groups of fields. Level 0, such as subject, description and status, is shared with customers. Level 7, such as team, priority and ticket type, can be read by customers but changed only by agents. Level 8 is agents only, and customers never see it.
• Internal fields stay internal. The portal, the REST API, list views and reports all leave out any field the user cannot read. To hide a custom field from customers, set its level to 8 in Customize Form.
• Templates say who sees each field. A Visible to column, set to Everyone or Agents, replaces the old Hide from customer check box. Existing templates are converted for you.
• You choose what customers can change later. After raising a ticket, a customer can change only the fields you mark Editable after creation on the template. They can always close the ticket and rate it.

For admins: existing sites pick up the new rules when they update, and agent managers see a notice in Helpdesk until they dismiss it. If you have server scripts, form scripts or custom roles on HD Ticket, check them before updating. Scripts running Before Insert, bots that are not agents, and custom staff roles are the usual things to fix. The migration guide lists what to check and how to test, and there is more on permission levels in the docs.

Working alongside our own support engineers, we noticed how much of a ticket is the same few moves every time: reply, escalate to the right team, add a comment for context, change the status.

Saved Replies can now carry Actions. Attach a set of actions to a saved reply and they run when the agent sends it, so the repetitive part happens on its own and agents spend their time on the customer instead.

A new Ticket Analytics tab gives agents the whole lifecycle of a ticket in one view: the timeline, response and wait times, the agents involved, SLA details and key metrics. Working out where the time went no longer means reading the entire conversation from the top.

If you've spent a full day in Helpdesk, you know the feeling: you open a ticket and your eyes have to go on a small journey. SLA at the top. Ticket information on the right. Feedback all the way at the bottom. All of the information feels scattered.

• The information was scattered. Everything you needed was there, just never in the same place. You learned the layout by muscle memory rather than by reading it.
• Space was going to waste. The old right panel was boxy. Every section carried its own borders and padding, and those pixels added up to a panel that showed less than it could.
• SLA had no context. A due date on its own doesn't tell you much. Was it met? Missed? Did the agent reply in time?

The new side panel fixes all three.

Contextual SLA fields

Instead of a bare timestamp, you now see the story of the SLA: whether it succeeded or failed, and more importantly, when the agent actually replied.

Priority with levels

We've added levels to priority, so you can tell tickets apart without stopping to read each label.

Tags

Analysis used to mean guessing at patterns. Tags let you name them. Group tickets by whatever matters to you: a recurring bug, a product area, a customer segment. When a customer creates a ticket for the first time, it gets a First Ticket tag automatically. The dashboard now has two new charts showing how tags break down and what they're costing you.

Contextual Cmd K

Cmd K used to only get you somewhere. Now it opens with whatever is on your screen. On a ticket, the ticket's own actions come first: change the status, set a priority, assign an agent, add a tag, merge a ticket, without touching the mouse.

Saved replies work directly from here. Type sr, pick one, and it opens the Email Editor with the reply already rendered into it, customer name and ticket fields filled in. The replies you use most float to the top as "Frequently Used". On the ticket list, you can apply filters or jump to views from here.

This one came out of my own experience using Helpdesk.

I spend part of my day answering tickets, and the same thing kept happening. I reply to a ticket, move on, and twenty minutes later I think: wait, which one did I just reply to? I tag a colleague on something, get pulled into a call, and by the time I am back I have lost the thread.

Every one of those ended the same way. Go to the ticket list, apply a filter or two, sort by modified, scroll until something looks familiar. It works, but it is a lot of steps for a question as small as "where was I?"

So the Home page now has My Recent Activity. It is a list of the tickets you have touched, most recent first, and it tells you what you did to each one: replied, commented, assigned, or just viewed.

Stop chasing routine follow-up work by hand. Tell Frappe CRM when something should happen and what should happen next, and it runs in the background for every matching lead or deal, with no code to write.

• Follow up on time. Send a welcome email to every new lead, or remind the owner when a prospect has not replied in three days.
• Keep deals moving. Convert a lead to a deal once it is Qualified, route new deals to the right rep by territory or value, or move a deal's stage when a condition is met.
• Score leads automatically. Add points when a prospect replies, subtract them when a task goes overdue, and mark leads Hot, Warm or Cold.
• Keep your team in the loop. Notify the owner when a deal is won or lost, or alert a manager when a high value deal changes stage.
• Connect your other tools. Call a webhook to push a won deal to billing, or create a record in any other DocType.

You can test an automation on a real record before turning it on. Test runs roll back every change, so nothing is saved and no webhook fires.

Find it under Settings → Automation & Rules → Workflow Automations, and the docs walk through the rest.

Press ⌘K, or Ctrl+K, anywhere in Frappe CRM to find a record, change its status or jump to a settings page without touching the mouse.

• Find any record by typing. Search leads, deals, contacts and organizations by name, email, phone or company.
• Act on the record you are viewing. On a lead or deal, change the status, assign it, add a comment or send an email template in a couple of keystrokes.
• Filter lists instantly. From any list view, filter by any field or switch views without opening a menu.
• See what is due. Open the palette for your upcoming tasks, SLA deadlines and recently viewed records.

Building a web form for CRM used to mean switching to the Desk and using the framework's generic Web Form builder. Not any more.

If you capture leads or deals from your website, you can now build the form inside Frappe CRM itself. Go to Settings → Forms → New, map the form to a Lead or Deal, and the fields come in automatically.

Select, delete, drag and reorder the fields, and preview the form exactly as your visitors will see it. Individual fields can be made mandatory or read-only, and more.

The Settings tab covers the success message, the submit button label and the rest of the form's behaviour. The Share tab gives you a link to send out or an iframe to embed. Once published, anything a visitor submits lands in CRM as a Lead or a Deal.

ERPNext integration now supports turning off bi-directional sync. When it is off, CRM Product is not synced back to the ERPNext master, but the ERPNext master is still synced to CRM Product.

We have also added logs where users can see synced Products and Items. Clicking an Item or Product opens it in desk view.

Previously, the salesperson had to manually fill the data which was in the lead while converting it into a deal. This increased chances of mistakes and created unnecessary friction in conversion. Now, in the lead-to-deal conversion form, fields from the lead are autofilled with the already available lead data.

v3.13 can copy a v2 dashboard into a new v3 workbook: queries, charts, filters, layout. Open Settings → Migrate from v2, scan, pick the dashboards you want, and migrate.

v2 is left untouched. It is a copy, not a move, so both apps keep working and you can put them side by side and compare.

Every query gets verified, not just converted. After migrating, Insights runs the query v2's own way and the v3 way, diffs the results, and gives you a verdict per dashboard, saying what it had to change. We ran it on Frappe's own v2 database: 115 of 118 dashboards came over with nothing dropped, and the three that did not were already broken in v2.

If you are still on v2

v2 will be removed in a future release, and a site with unmigrated dashboards will not upgrade past that point. There is no date yet, but migrating the dashboards you actually use keeps your upgrade path open.

Reference lines can follow the data. A reference line used to sit at a number you typed in, and went stale the moment you changed a filter. It can now be the average, median, min or max of what is plotted, so it moves with the data.

Percent measures. Mark a measure as Percent on a number card or a table, and a ratio like sum(x) / sum(y) shows as 42% instead of 0.42.

Pre-built dashboards you import into a workbook in a couple of clicks. It ships four for ERPNext, and the mechanism underneath is a hook, so any app can ship its own dashboards the same way.

The four that ship:

• Receivables, Payables & Cash: AR/AP ageing, collections worklist, cash-flow view
• Sales Performance: revenue trend with MoM KPIs, top customers/items, quotation→order funnel
• Purchasing Overview: spend trend, spend by item group, top suppliers, PO status mix
• Inventory Health: stock value by warehouse/item group, movement, reorder alerts

Importing gives you your own copy to edit. Imported dashboards are shared org-wide for viewing.

Check out this post to know how to ship a template along with your app.

Frappe Wiki now has built-in page view analytics. There is a nice overview dashboard that will help you visualise the numbers and trends. Just enable view tracking from the settings page, no third party plugin required!

Because.. why not? Quickly get around the Wiki dashboard and carry out actions like creating pages and changing theme.

A new way to create an internal link between pages. Even if you change the route of the linked page, the links won't get broken.

Contributed by Gajendra Nishad

A Notification can now take its subject and message from an Email Template instead of having the text typed into the notification itself. The template is read every time the notification goes out, so editing the template updates every notification that uses it. Fix a typo once and it is fixed everywhere.

bench migrate --skip-failing keeps going when a patch fails and marks it skipped. That is fine for most patches, but some of them move data, and skipping those quietly leaves the site wrong.

Apps can now list the patches that must never be skipped:

never_skip_patches = ["app.patches.v16_0.critical_data_fix"]

If one of those fails, the migration stops.