Os detalhes do produto são exibidos em inglês. Traduções em breve.
Fatos rápidos
- Preço
- $499.00 USD
- Versões dynamics_365_business_central
- —
- Tempo de configuração
- 30 min
- Licença
- Uma vez perpétua
- Idiomas
- 11 idiomas
Compra Única
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
Sem pagamento agora. Isto envia um pedido de orçamento à nossa equipe — responderemos por e-mail com preços e próximos passos.
Recursos Principais
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
Sobre este Produto
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.
Por Que Escolher 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.
O que você ganha
- 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
Para quem é isso
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.
Visão geral da instalação
Baixe do ECOSIRE
Compre a licença em ecosire.com e baixe o ZIP do módulo Approvals & Workflow with Teams/Outlook Cards for Business Central no painel da sua conta.
Carregar para Odoo
Extraia o ZIP em sua pasta de complementos personalizados do Odoo no servidor (ou faça upload via Aplicativos > Instalar do arquivo em Odoo.sh/runbot).
Instale o módulo
Ative o modo de desenvolvedor, abra Aplicativos, clique em Atualizar lista de aplicativos, procure por Approvals & Workflow with Teams/Outlook Cards for Business Central e pressione Instalar.
Definir configurações
Abra o novo menu, cole sua chave de licença ECOSIRE, conecte quaisquer credenciais externas (Shopify, Amazon, Stripe, etc.) e salve.
Verifique e entre no ar
Execute o teste de conexão integrado, sincronize seus primeiros 10 registros e agende o cron recorrente. Entre em contato com o suporte se algo falhar.
Como Approvals & Workflow with Teams/Outlook Cards for Business Central se compara
| Critério | ECOSIRE | Construção personalizada | Concorrente | Odoo nativo |
|---|---|---|---|---|
| Multi-level conditional approval matrices (amount/dimension/field-driven) | Incluído | Suporte parcial | Suporte parcial | |
| Approve/reject adaptive cards inside Microsoft Teams and Outlook | Incluído | Suporte parcial | Suporte parcial | |
| Mobile push approvals with full document context | Incluído | Suporte parcial | Incluído | |
| Substitute / out-of-office automatic routing | Incluído | Suporte parcial | Suporte parcial | |
| Tamper-evident audit trail of every action with comments | Incluído | Suporte parcial | Incluído | |
| Built on standard approval tables/event subscribers (upgrade-safe) | Incluído | Não incluído | Incluído | |
| Tailored to your exact org hierarchy and document rules | Incluído | Incluído | Não incluído | |
| Installed, validated, and supported on your tenant by the builder | Incluído | Suporte parcial | Não incluído |
Perguntas frequentes sobre 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.
Módulos Relacionados
ERPNext
Único
2Checkout / Verifone Gateway for ERPNext
A build-to-order 2Checkout (Verifone) payment integration for ERPNext, giving global digital-goods sellers card acceptance, 45+ local payment methods, multi-currency checkout, and reconciled invoices. ECOSIRE scopes, builds, installs, and supports it on your ERPNext v15/v16 instance.
Construído sob encomendaA partir de $199.00
Magento 2
Único
2Checkout / Verifone Gateway for Magento 2
A build-to-order 2Checkout / Verifone payment gateway for Magento 2 and Adobe Commerce: localized checkout in 12 languages, iDEAL, Giropay and regional methods, multi-currency global selling, subscription billing and tax/invoicing automation — engineered, installed and supported by ECOSIRE.
Construído sob encomendaA partir de $199.00
ERPNext
Único
360-Degree Feedback for ERPNext
A build-to-order ERPNext application for anonymous 360-degree reviews — configurable peer, manager, report and self rater groups, weighted competency scoring, and aggregated gap-analysis and heatmap reports. ECOSIRE scopes, builds, installs and supports it on your Frappe/ERPNext v15/v16 instance.
Construído sob encomendaA partir de $249.00
Solicitar orçamento
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