Les détails du produit sont affichés en anglais. Traductions à venir.
Faits en bref
- Prix
- $499.00 USD
- Versions dynamics_365_business_central
- —
- Temps d'installation
- 30 minutes
- Licence
- Perpétuel unique
- Langues
- 11 langues
Achat unique
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
Aucun paiement maintenant. Ceci envoie une demande de devis à notre équipe — nous vous recontacterons par e-mail avec les tarifs et les prochaines étapes.
Fonctionnalités clés
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
À propos de ce produit
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.
Pourquoi choisir 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.
Ce que vous obtenez
- 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
Pour qui c'est
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.
Aperçu de l'installation
Télécharger depuis ECOSIRE
Achetez la licence sur ecosire.com et téléchargez le module ZIP Approvals & Workflow with Teams/Outlook Cards for Business Central depuis le tableau de bord de votre compte.
Télécharger sur Odoo
Extrayez le ZIP dans votre dossier de modules complémentaires personnalisés Odoo sur le serveur (ou téléchargez-le via Applications > Installer à partir du fichier sur Odoo.sh / runbot).
Installer le module
Activez le mode développeur, ouvrez les applications, cliquez sur Mettre à jour la liste des applications, recherchez Approvals & Workflow with Teams/Outlook Cards for Business Central et appuyez sur Installer.
Configurer les paramètres
Ouvrez le nouveau menu, collez votre clé de licence ECOSIRE, connectez toutes les informations d'identification externes (Shopify, Amazon, Stripe, etc.) et enregistrez.
Vérifier et mettre en ligne
Exécutez le test de connexion intégré, synchronisez vos 10 premiers enregistrements et planifiez le cron récurrent. Contactez le support si quelque chose échoue.
Comment Approvals & Workflow with Teams/Outlook Cards for Business Central se compare
| Critère | ÉCOSIRE | Construction personnalisée | Concurrent | Odoo natif |
|---|---|---|---|---|
| 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 |
Foire aux questions sur 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.
Pourquoi les clients font confiance à ECOSIRE
SOC 2 aligné
Conforme au RGPD
Paiement sécurisé Stripe
Remboursement sous 30 jours
Mises à jour à vie
Licence LGPL-3.0
Modules associés
Demander un devis
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