Introduction

The Order History Microservice is used to transfer order information from Microsoft Dynamics 365 to Intershop Commerce Management (ICM).

This document provides important product information, including version information and dependencies. It also outlines the basic setup and configuration steps.

References

• Overview - Microservices
• Overview - Service Registration and Discovery

Version Information and Dependencies

The source code can be downloaded from https://repository.intershop.de//mvn-orderhistory-releases/.

Setup

The order history connector is implemented as Microservice.

To familiarize yourself with the concepts, please refer to Overview - Microservices and Overview - Service Registration and Discovery.

Setup instructions can be found at Cookbook - Microservice Deployment (valid to 7.10) and Cookbook - Eureka Deployment and ICM Configuration (valid to 7.10).

Configuration

Following configuration data has to be provided to Order History Microservice. Currently the properties have to be specified in a file that is within the Java classpath of the Microservice.

Azure Active Directory Credentials Configuration

Configuration for getting an access token from Azure Active Directory (AAD) necessary for OData access to Microsoft Dynamics 365 for Finance and Operations:

# Azure Active Directory credentials
intershop.orderhistory.azure.resource=
intershop.orderhistory.azure.tenant=
intershop.orderhistory.azure.clientID=
intershop.orderhistory.azure.clientSecret=
intershop.orderhistory.azure.token.requestURL=
intershop.orderhistory.azure.token.minimumTTL=

Concurrency Configuration

Configuration for the number of threads used to process requests from ICM:

# Concurrency configuration
#intershop.orderhistory.threadPool.size=

Payment Methods Mapping Configuration

How the methods of payment in Microsoft Dynamics 365 are mapped to Intershop payment methods can be extended and adjusted in the file environment.properties.

Configuration for mapping of ICM payment methods to related ones specified in Microsoft Dynamics 365 for Finance and Operation's Contoso demo:

# Payment method mapping configuration
# pattern: intershop.orderhistory.mapping.payment.method.<dyn365-name>=<icm-name>

intershop.orderhistory.mapping.payment.method.ELECTRONIC=ISH_INVOICE
intershop.orderhistory.mapping.payment.method.CASH_DELIV=ISH_CASH_ON_DELIVERY
intershop.orderhistory.mapping.payment.method.CASH_ADV=ISH_CASH_IN_ADVANC

Managed Service Configuration

In order to connect the Order History Microservice with the ICM, a managed order history service has to be configured.

To create a service configuration (set technical configuration):

1. Go to the Commerce Management application: Sales Organization | Services.
2. Create a new service configuration for the order history service (and enable sharing).
3. Set the order history service specific settings:

   • Microservice URI e.g., Eureka service URI 'service://orderHistory'.

     
     

Feature Overview

All orders of a customer will be displayed in the order list in the My Account section.

Limitations

• Standard Microsoft Dynamics 365 is used for the mapping.
• All users of a customers can see all orders of the customer in the My Account section. No user order list view is available.
• Order details will not be displayed in the My Account section.
• Order Totals cannot currently be displayed without executing a job in the Dynamics back-office first (job "Calculate sales totals"). Before this job is triggered, all totals will be displayed as 0.

Known Issues

Changelog

Version 2.0.0

• Renaming of several attributes of resource objects in ICM backend API.

Version 1.0.0

• Initial version