产品详细信息以英文显示。翻译即将推出。
速览
- 价格
- $499.00 USD
- dynamics_365_business_central 版本
- —
- 设置时间
- 30分钟
- 许可证
- 一次永久
- 语言
- 11 语言
一次性购买
Approvals & Workflow with Teams/Outlook Cards for Business Central
A multi-level, conditional approval engine for Dynamics 365 Business Central that pushes approve/reject adaptive cards into Microsoft Teams and Outlook — surpassing native BC workflow with substitute routing, mobile push, and a tamper-evident audit trail. Built and installed by ECOSIRE as a per-tenant AL extension on your tenant.
$499.00USD
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
核心功能
Multi-level conditional approval matrices keyed on document type, amount thresholds, dimensions, vendor/customer, or any custom field
Approve/reject adaptive cards delivered into Microsoft Teams chats and Outlook inboxes — act without opening the BC web client
Responses flow back through the Business Central REST/OData v4 API and update the standard Approval Entry record
Substitute and out-of-office routing that auto-reassigns pending approvals to a delegate
Mobile push approvals via the Teams app — decide from a phone with full document context on the card
Tamper-evident audit trail of every request, approval, rejection, delegation, and escalation with user, timestamp, and comment
Job Queue-driven escalations and reminders on a configurable schedule (e.g., escalate after 48h)
Built as table/page extensions and event subscribers on the standard approval codeunits — extends BC, never forks it
Amount- and dimension-based parallel or sequential approval chains with quorum rules
Optional Power Platform / Dataverse integration for environments standardized on Teams + Power Automate
Per-tenant extension install with scoped permission sets so only authorized users manage workflow setup
Configurable card content — document lines, attachments link, and approver comments captured back into BC
关于此产品
Native Business Central approvals are limited: a fixed approver hierarchy, email notifications that bounce you back into the web client, and little room for conditional logic without code. This ECOSIRE extension replaces that with a real workflow engine — and lets people approve where they already work.
为什么选择 Approvals & Workflow with Teams/Outlook Cards for Business Central
Multi-level conditional approval matrices keyed on document type, amount thresholds, dimensions, vendor/customer, or any custom field
Approve/reject adaptive cards delivered into Microsoft Teams chats and Outlook inboxes — act without opening the BC web client
Responses flow back through the Business Central REST/OData v4 API and update the standard Approval Entry record
Substitute and out-of-office routing that auto-reassigns pending approvals to a delegate
Mobile push approvals via the Teams app — decide from a phone with full document context on the card
Tamper-evident audit trail of every request, approval, rejection, delegation, and escalation with user, timestamp, and comment
What it does. We build a per-tenant AL extension that adds conditional, multi-level approval matrices on top of the standard Approval Entry and Workflow tables. Routing is driven by document type, amount thresholds, dimensions, vendor/customer, or any field you choose — implemented with table extensions, page extensions, and event subscribers on the standard approval codeunits (so we extend BC, never fork it). When a document enters approval, the engine calls out through an Azure-hosted relay to post an adaptive card into the approver's Microsoft Teams chat and Outlook inbox. They approve or reject inline; the response flows back via the BC REST/OData v4 API and updates the approval entry — no need to open the web client.
Beyond native. Substitute / out-of-office routing reassigns pending approvals automatically. Mobile push lands through the Teams app. Every action — request, approve, reject, delegate, escalate — is written to a tamper-evident audit log with user, timestamp, and comment. A Job Queue entry handles escalations and reminders on a schedule you set.
How we deliver. This is build-to-order. After purchase, ECOSIRE scopes your approval rules, builds the extension, installs it as a per-tenant extension (or via your Power Platform / Dataverse environment where Teams integration warrants it), assigns the required permission sets, and validates end-to-end on your tenant — sandbox first, then production. You get the source, the documentation, and ongoing support. No AppSource listing, no instant download — a working extension on your environment.
你得到什么
- A per-tenant AL extension (.app) built to your approval rules, installed on your sandbox then production Business Central environment
- Azure-hosted relay/gateway configuration that bridges BC and the Teams/Outlook adaptive-card channels
- Configured multi-level approval matrices matching your document types, thresholds, and org hierarchy
- Permission sets scoped to workflow administrators and approvers, assigned in your environment
- Job Queue entries for escalation and reminder scheduling
- Full AL source code, a deployment runbook, and admin/approver documentation
- End-to-end validation sign-off (sandbox + production) and a post-go-live support window
这是给谁的
Finance Controller / CFO
Needs enforceable spending controls — multi-level sign-off on purchase orders and invoices by amount and cost center — without chasing approvers through email. Wants an audit trail that survives a financial audit.
Business Central Administrator / IT Manager
Owns the BC tenant and wants approvals extended cleanly via a supported per-tenant extension with scoped permission sets, not brittle customizations that break on the next Microsoft release wave.
Operations / Procurement Manager
Approves dozens of documents a week and lives in Teams and Outlook. Wants to approve or reject inline from an adaptive card on desktop or mobile, with substitute routing so nothing stalls during leave.
安装概述
从ECOSIRE下载
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 Approvals & Workflow with Teams/Outlook Cards for Business Central 模块 ZIP。
上传至Odoo
将 ZIP 解压到服务器上的 Odoo 自定义插件文件夹中（或通过“应用程序”>“从 Odoo.sh / runbot 上的文件安装”上传）。
安装模块
激活开发者模式，打开应用程序，单击更新应用程序列表，搜索 Approvals & Workflow with Teams/Outlook Cards for Business Central，然后按安装。
配置设置
打开新菜单，粘贴您的 ECOSIRE 许可证密钥，连接任何外部凭据（Shopify、Amazon、Stripe 等），然后保存。
验证并上线
运行内置连接测试，同步前 10 条记录，并安排定期 cron。如果出现任何问题，请联系支持人员。
Approvals & Workflow with Teams/Outlook Cards for Business Central 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Multi-level conditional approval matrices (amount/dimension/field-driven) | 包含 | 部分支持 | 部分支持 | |
| Approve/reject adaptive cards inside Microsoft Teams and Outlook | 包含 | 部分支持 | 部分支持 | |
| Mobile push approvals with full document context | 包含 | 部分支持 | 包含 | |
| Substitute / out-of-office automatic routing | 包含 | 部分支持 | 部分支持 | |
| Tamper-evident audit trail of every action with comments | 包含 | 部分支持 | 包含 | |
| Built on standard approval tables/event subscribers (upgrade-safe) | 包含 | 不包括在内 | 包含 | |
| Tailored to your exact org hierarchy and document rules | 包含 | 包含 | 不包括在内 | |
| Installed, validated, and supported on your tenant by the builder | 包含 | 部分支持 | 不包括在内 |
关于Approvals & Workflow with Teams/Outlook Cards for Business Central的常见问题
How long until the extension is live on our environment?
Typical delivery is 2–4 weeks from when we finalize your approval rules. We start with a short scoping call to map document types, thresholds, and your org hierarchy, build the AL extension, install and test it on your sandbox, then deploy to production with you. Complex matrices or Dataverse/Power Platform integration can extend the timeline; we confirm a firm date after scoping.
This is build-to-order — there's no AppSource download, right?
Correct. We do not publish this to AppSource for instant install. ECOSIRE builds it specifically for your tenant and installs it as a per-tenant extension on your Business Central environment. You receive the compiled .app, the full AL source, and documentation — it runs on your tenant, configured to your rules.
What about ongoing support and Microsoft update waves?
Each build includes a post-go-live support window for fixes and tuning. Because we build on standard approval tables and event subscribers rather than modifying base objects, the extension is resilient across BC update waves; we offer an ongoing maintenance option that retests and recompiles your extension against each major Business Central release.
Where does the Teams/Outlook delivery actually happen — does data leave Business Central?
Adaptive cards are delivered through an Azure-hosted relay we configure for your tenant. The card carries the document summary needed to decide; approval responses return through the BC REST/OData v4 API to update the Approval Entry. We scope exactly what fields appear on the card and can keep the relay within your own Azure subscription if your security policy requires it.
Can it handle parallel approvers and out-of-office cover?
Yes. Matrices support sequential and parallel chains with quorum rules (e.g., any two of three), and substitute routing automatically reassigns a pending approval to a designated delegate when an approver is marked out-of-office, with the original and the delegate both recorded in the audit trail.
相关模块
申请报价
Approvals & Workflow with Teams/Outlook Cards for Business Central
A multi-level, conditional approval engine for Dynamics 365 Business Central that pushes approve/reject adaptive cards into Microsoft Teams and Outlook — surpassing native BC workflow with substitute routing, mobile push, and a tamper-evident audit trail. Built and installed by ECOSIRE as a per-tenant AL extension on your tenant.
- Multi-level conditional approval matrices keyed on document type, amount thresholds, dimensions, vendor/customer, or any custom field
- Approve/reject adaptive cards delivered into Microsoft Teams chats and Outlook inboxes — act without opening the BC web client
- Responses flow back through the Business Central REST/OData v4 API and update the standard Approval Entry record
- Substitute and out-of-office routing that auto-reassigns pending approvals to a delegate