A build-to-order Frappe app that upgrades ERPNext Kanban and List views with Link-field columns, swimlanes, WIP limits, inline card editing, per-user saved presets and conditional coloring. ECOSIRE scopes, builds, installs and supports it for your exact DocTypes. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $99.00 USD; request a quote for a scoped proposal.

A build-to-order Frappe app that upgrades ERPNext Kanban and List views with Link-field columns, swimlanes, WIP limits, inline card editing, per-user saved presets and conditional coloring. ECOSIRE scopes, builds, installs and supports it for your exact DocTypes.
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
Teams that run their work inside ERPNext quickly hit the ceiling of the stock board. Frappe's native Kanban only groups cards by a single Select field, so a sales pipeline keyed on a Link-to-Territory, a project board grouped by assigned engineer, or a support queue split by priority all force you to bolt a throwaway Select field onto the DocType and keep it in sync by hand. There are no swimlanes, no WIP limits, no inline card editing, and every user is stuck with whatever list filters and columns the last person left behind. The result is that project and sales teams either export to a spreadsheet or buy a separate board tool, and ERPNext stops being the single source of truth.
Kanban columns generated directly from `Link` fields (e.g. Customer Group, Project, Sales Person) — not just the native single `Select` field
Horizontal swimlanes as a second grouping dimension, so a board can split by stage across columns and by owner across rows
Per-column WIP limits with visual over-limit warnings to enforce flow discipline
Inline card editing that patches individual fields via the Frappe REST API without opening the full form
Card drag-and-drop routed through a whitelisted server method so moves fire `validate` / `on_update` `doc_events` and never bypass business logic
Conditional row and card coloring driven by field-value rules (overdue dates, value thresholds, priority) you define
Enhanced Kanban & List Views closes that gap as a proper Frappe app (its own module, installable with bench get-app / bench install-app) rather than a fragile customization. We add a configurable board layer that can build Kanban columns directly from Link fields — grouping a Sales Order board by Customer Group, a Task board by Project, or a Lead board by Sales Person — resolving the linked records through the Frappe ORM and honoring the same read permissions and role profiles the rest of ERPNext uses. On top of columns we add horizontal swimlanes (a second grouping dimension), per-column WIP limits with visual over-limit warnings, and conditional row and card coloring driven by field-value rules you define (for example, overdue delivery dates in red, high-value deals in green).
Technically, moves and edits are transactional. Dragging a card writes through a whitelisted server method (@frappe.whitelist()) that runs standard document validation and hooks.py doc_events (validate, on_update), so a board move can't bypass your business logic — it triggers the same workflow state changes, notifications and permission checks as editing the form. Inline card editing uses the Frappe REST API and client scripts to patch individual fields without opening the full form. Saved view presets — the exact columns, filters, sort order, board grouping, swimlane and color rules — are stored per user in a custom DocType, so each person keeps their own working views while shared team presets stay stable. Where a board needs periodic recalculation (aging counters, stale-card flags), we wire a scheduler_events job. Everything is built and tested against Frappe/ERPNext v15 and v16.
Because this is build-to-order, nothing is a generic download. On a short scoping call we confirm which DocTypes get boards, which Link fields drive columns and swimlanes, your WIP and coloring rules, and the permission model. We then build your version of the app, test it on a staging bench, run UAT with your team, and deploy to production with a rollback plan. Typical delivery is 2 to 4 weeks from confirmed scope depending on how many DocTypes and rules are in play. You receive the full source code and git repository, so you are never locked to us.
Runs multiple client or internal projects in ERPNext and wants a Task board grouped by Project or assignee, with swimlanes per team and WIP limits to stop overloading engineers — without exporting to a separate board tool.
Manages a pipeline of Leads and Opportunities and needs columns driven by the Sales Person or Territory `Link` field, conditional coloring for stale or high-value deals, and inline stage moves that still fire the real ERPNext workflow.
Triages Issues, Material Requests or service jobs and wants a color-coded queue with per-user saved filters, so each agent keeps their own view while the shared board stays consistent.
Owns the instance and needs a clean, permission-respecting Frappe app — no core patching, proper `doc_events`, v15/v16 compatibility and the source in git — rather than a brittle in-house customization.
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 Enhanced Kanban & List Views for ERPNext 应用程序 ZIP。
将 ZIP 解压到您的 bench 的 apps 文件夹中,或者使用解压缩的应用程序的路径运行“bench get-app”。
运行 `bench --site SITE_NAME install-app APP_NAME`,然后运行 `bench migrate` 以安装 Enhanced Kanban & List Views for ERPNext 并应用其架构。
打开您站点上的 ECOSIRE 许可证设置并激活您的许可证密钥。需要免费的 ecosire_connect 和 ecosire_license_client 应用程序。
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Kanban grouping source | Any `Link` field (Project, Customer Group, Sales Person) plus swimlanes | Whatever you build in-house | Usually the native single `Select` field only | |
| WIP limits | Per-column limits with over-limit warnings | Possible but must be coded from scratch | Rarely included | |
| Inline card editing | Patch fields via REST API without opening the form | DIY client scripting | Limited or full-form only | |
| Conditional coloring | Rule-based row/card colors you define | Hand-coded per board | Basic indicator colors at best | |
| Saved presets | Per-user + shared presets in a custom DocType | Build your own storage model | Often global, not per-user | |
| Business-logic safety | Moves fire `validate`/`on_update` `doc_events` | Depends on your implementation quality | Varies; may bypass workflow | |
| Fit to your DocTypes | Scoped and built for your exact DocTypes | Fully bespoke but you carry the effort | Generic, configure to fit | |
| Ownership & support | Full source, git handover, support window | You own it and maintain it entirely | Vendor-controlled, subscription-tied |
Because this is build-to-order, we build your version after a scoping call rather than shipping a generic download. Typical delivery is 2 to 4 weeks from confirmed scope, depending on how many DocTypes get boards and how complex your swimlane, WIP and coloring rules are. We confirm a firm timeline once scope is signed off.
No. There is no instant download. ECOSIRE builds, installs and supports your version against your specific DocTypes and `Link` fields, then hands over the full source and git repository. You get code tailored to your instance, not a one-size-fits-all listing.
We build and test against Frappe/ERPNext v15 and v16. During scoping we confirm your exact version and bench setup so the app is packaged and tested to match it.
Yes. Drag-and-drop moves and inline edits go through whitelisted server methods that run standard document validation and `hooks.py` `doc_events` (`validate`, `on_update`), and cards only appear if the user can read the underlying document. Board actions honor your workflow states, role profiles and user permissions exactly as the form would.
Every engagement includes a post-go-live support window for defect fixes and configuration tweaks. Because you receive the full git repository, your team can extend the app yourselves, and we can also quote a maintenance retainer to keep it aligned with future ERPNext releases.
We prefer to drive columns from your existing `Link` fields. Where a new grouping or flag field is genuinely needed we add it as a Custom Field or through fixtures, packaged in the app so it survives `bench migrate` and version upgrades — no manual patching of core DocTypes.
Yes. Saved view presets — columns, filters, sort order, board grouping, swimlanes and color rules — are stored per user in a dedicated custom DocType. Individuals keep their own working views while shared team presets stay stable for everyone.
A build-to-order Frappe app that upgrades ERPNext Kanban and List views with Link-field columns, swimlanes, WIP limits, inline card editing, per-user saved presets and conditional coloring. ECOSIRE scopes, builds, installs and supports it for your exact DocTypes.