Extensibility overview for Microsoft Dynamics AX for Retail - Part II
Agenda
Extensible Omni-Channel Retail
Commerce runtime
Commerce Runtime
CRT internals
Extensibility
Commerce Runtime (CRT) Architecture
Retail server
Retail Server (RS)
Retail Server architecture
Retail Proxy
Modern POS
Extensibility Scenarios
Modern POS Architecture
Modern POS Solution: Core
Modern POS Solution: App
Look and Feel Extensibility (View)
Entities extensibility
Entities extensibility
Existing workflow changes
Operations and Activities
Adding New Functionality
Demo Scenario
Architecture
High level flow
Modern POS Changes
Demo
Questions
Additional Retail Sessions
Retail Hands on Lab Training
3.45M
Category: marketingmarketing

Extensibility overview for Microsoft Dynamics AX for Retail

1.

2. Extensibility overview for Microsoft Dynamics AX for Retail - Part II

3. Agenda

Commerce Runtime extensibility
Retail Server extensibility
Modern POS extensibility
Demo

4. Extensible Omni-Channel Retail

Social
Modern POS
CMS
POS UI
ODATA/REST
E-Commerce
E-POS
Retail Server
Commerce Data Exchange
AX for Retail
Product Catalog
Omni Channel
Enrichment
Call Center
Merchandizing
Pricing
Promotions
Targeting
Customer
Accounts
Loyalty
Management
BI / Data Mining
Transaction
history
Store operations
Fulfillment
Replenishment

5. Commerce runtime

6. Commerce Runtime

7. CRT internals

8. Extensibility

Managed Extensibility Framework

9. Commerce Runtime (CRT) Architecture

Commerce
Runtime
Workflows
Data Services
Desktop
SQL Server
Data Access
SQL
Express+
Messages
Plugins
Data Services
Common
Commerce
Entities
Plugins
Windows Phone
Data Services
Non-Desktop
Sqlite
Data Access
Sqlite
Messages
Commerce Frameworks
Client APIs
Platform Agnostic
(Portable)
Shared Across All Platforms
Platform Specific
(Portable)
Shared Across Windows
Phone and Non-Windows
Platform Specific
(Full .NET)
Windows Pro Only
Platform Specific
(Native to Target)
Specific Platform Only

10. Retail server

11. Retail Server (RS)

12. Retail Server architecture

IIS
Retail Server
OData Web APIs
Authenticati
on Module
Redirector
Controller
Commerce Runtime (CRT)

13. Retail Proxy

MOBILE POS
IIS
Retail Server
OData Web APIs
Mobile POS
Retail Proxy
Local embedded
Commerce Runtime (CRT)
Authenticati
on Module
Redirector
Controller
Commerce Runtime (CRT)
• Retail proxy abstracts the
interface between Retail server
and Commerce Runtime
• Handles Local, Remote
• Local context -> CRT
• Remote context -> Retail
Server
• All the clients use proxy API to
interact with the server
• Cross – platform – available
both in Java script as well as C#

14. Modern POS

15. Extensibility Scenarios

16. Modern POS Architecture

Loc
TypeScript,
resjson
Views – HTML5/CSS/JS
[platform specific views]
Platform
dependent
View-Controllers - TypeScript, WinJS, DevExpress, jQuery, jqGrid, KnockoutJS
[platform specific UI code behind]
Platform
independent
View-Models - TypeScript
[common binding properties]
Operations - TypeScript
[WorkFlows]
Device Manager - TypeScript
[peripherals interface]
Models – TypeScript (entities)
Data Manager Interface TypeScript
Devices (PointOfService)
ODATA Client – TypeScript,
DataJS
Cache - TypeScript
(SQLite)
HTTP/HTTPS
ODATA v3
Retail Server (C#)
CRT (C#)
1

17. Modern POS Solution: Core

Core
Operations
Activities
Entities
Managers
Peripherals
• Workflow
• Extensive use of
activities
• “Abstract” classes
• No implementation
• Data contract
• Can have a
response handler
• Data model only
• CommerceTypes:
Retail Server
entities
• Data managers
• CommerceContext:
Retail Server API
• Peripheral interface

18. Modern POS Solution: App

App
Views
Controls
Activities
Peripherals
• HTML pages
• ViewControllers
• HTML pages
• Code behind
• Activities
implementation
• Native access to
peripherals

19. Look and Feel Extensibility (View)

20. Entities extensibility

21. Entities extensibility

22. Existing workflow changes

23. Operations and Activities

24. Adding New Functionality

25. Demo Scenario

26. Architecture

Retailer B
Loyalty
Service
Channel Db
Retail Server
Retailer A

27. High level flow

28. Modern POS Changes

Loc
TypeScript,
resjson
Views – HTML5/CSS/JS
[platform specific views]
Platform
dependent
View-Controllers - TypeScript, WinJS, DevExpress, jQuery, jqGrid, KnockoutJS
[platform specific UI code behind]
Platform
independent
View-Models - TypeScript
[common binding properties,]
Operations - TypeScript
[WorkFlows]
Device Manager - TypeScript
[peripherals interface]
Models – TypeScript (entities)
Data Manager Interface TypeScript
Devices (PointOfService)
ODATA Client – TypeScript,
DataJS
Cache - TypeScript
(SQLite)
HTTP/HTTPS
ODATA v3
Retail Server (C#)
CRT (C#)
1
English     Русский Rules